Closed (fixed)
Project:
Drupal.org site moderators
Component:
Other
Priority:
Normal
Category:
Task
Assigned:
Unassigned
Reporter:
Created:
29 Jan 2016 at 00:14 UTC
Updated:
30 Dec 2023 at 22:11 UTC
Jump to comment: Most recent
Drupal.org projects (webmasters) reads, in part:
A project with issue tracker that you can use to report spam, broken links, or user account problems on Drupal.org website.
"Webmasters" vs. "Infrastructure"
If you want to report a problem with the Apache and MySQL installation on drupal.org, the Mailman mailing lists, the Git repositories, and the various Drupal installations on the drupal.org domain, please use the Drupal.org infrastructure project instead.
There's no mention of where to file an issue with how the dashboard is working or how revisions tracking is working. People seem to be filing them in webmasters, but I don't get that from the introduction and originally considered filing #2658508: Credited organization repeatedly marked as updated under Drupal.org infrastructure.
In fact, I'm seeing dashboard issues variously filed under both webmasters and infrastructure. Presumably one of those is correct, but there's no guidance on the page as to which project to use for filing.
It would be better if the page text read something like one of the following:
If Drupal.org webmasters is the correct project for the dashboard and similar issues:
A project with issue tracker that you can use to report spam; broken links; user account problems; or problems displaying lists, revisions, or other reports on Drupal.org website.
If Drupal.org infrastructure is the correct project for the dashboard and similar issues:
If you want to report a problem with the Apache and MySQL installation on drupal.org; the Mailman mailing lists; the Git repositories; and the various Drupal installations on the drupal.org domain; or problems displaying lists, revisions, or other reports on Drupal.org website, please use the Drupal.org infrastructure project instead.
Comments
Comment #2
charles belovComment #3
charles belovComment #4
avpadernoI am moving the issue, since editing the description for an issue queue is not done from documentation maintainers.
Comment #5
avpadernoIn short, for what I can understand, the Drupal.org Webmasters queue is for all the issues that can be handled changing the settings from the Drupal UI; the Drupal.org Infrastructure queue is for issues that require, for example, SSH access.
I am not sure it is possible to make an exhaustive list that makes clear when to use one or the other issue queue, also because users are not probably aware of which settings are available through the Drupal core modules, or third-party ones.
Comment #6
avpadernoActually, there is also other issue queues for which a report could be opened: the ones for the custom modules used from Drupal.org. If the settings, or the user interface are provided from one of those modules, it's not the webmasters or the infrastructure queue to use.
It's a little complicated to describe which issues the webmasters queue covers, but we don't also pretend the users know exactly which queue to use. If they posted the issue in the wrong queue, the issue will be moved in the correct one.
Comment #7
avpadernoTo make a concrete example, #2933527: Issue status update email links to comments do not work for multiple page issues was open for the webmasters queue, but it could be an issue report for Drupal itself, or one of the custom modules used on Drupal.org.
It's quite hard to make a description that covers all the possible cases, and using the most generic description would not help much. I think we can just give directions to make users understand what this queue is for, but not avoid the users will post an issue here instead of the correct queue.
Comment #8
avpadernoAnd to answer to the two cases shown in the OP (how the dashboard is working and how revisions tracking is working), those could be issues to post for the module implementing them, which could also mean Drupal core, if the functionality is not being altered by a specific module.
I would rather not add a note like If the issue is caused from a plain Drupal installation, then post the issue on the Drupal core queue.
Comment #9
avpadernoI am setting this issue as fixed per my previous comments.
Comment #11
avpaderno