In which way the issue queue for coverage applications is different from other project queues

The issue queue used for coverage applications is different from the issue queues for contributed modules.

• It is not for support requests on the project used for the application, including questions asking when there will a stable release for the project, or when the project will be covered by the security policy advisory.
  Those issues must be created in the project issue queue.
• It is not for reporting bugs in the project code.
  Except in very limited cases, for example a PHP file where function is misspelled, bugs should be reported in the project issue queue.
• It is not for providing patches to apply to the files in the project used for the application.
  Reviewers just report what needs to be changed in the project files, letting the applicant do those changes.
• It is not for asking reviewers to review a project whose project owner or any of the project maintainers are already able to opt projects into security advisory coverage.
• It is not for asking changes on the workflow used to approve coverage applications.
• The status of an application is changed from Active to Needs review only from the applicant.
  If the applicant does not change the status from Active to Needs review, it probably means the applicant is not paying attention to the application. If that is the case, changing the status from Active to Needs review, and doing a review, is pointless, as the applicant would not notice the review, nor change the project files as reported.