Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.For every project on Drupal.org, there are two tags under the "Project information" heading known as "Maintenance status" and "Development status".
If a user clicks on these to learn more, he/she is taken to the tag's taxonomy term page. There are 5 "maintenance" terms and 4 "development terms".
However, of these 9 terms, only 3 have tag description. Not having a tag description is unhelpful to a user that is browsing a project and want to find out what a specific status term entails.
There is, however, a community wiki page - https://drupal.org/node/1066982 where a description of all the relevant terms can be found.
As an aside, I will say that I think that the explanation of the meaning of these tags should be considered official documentation and should not be subject to arbitrary changes. Therefore, I don't think this information belongs on a wiki page.
However, as a stopgap soluntion, to make sure users browsing project pages at Drupal.org have access to the documentation that expands the meaning of the status tags, all 9 tags should be given a "tag description" that contains a link to the community wiki page.
After this stopgap solution is in place, here is the tasks I think should be carried out:
- All nine project status tags should be given an official tag description (e.g. the current community wiki text can be adopted as the official version).
- (TheDrupal.org customizations team should create a view that lists the official project status tag descriptions. This is suggested in the related issue.)
- The link on http://drupal.org/node/314492 to these definitions should link to this this view (an any other that currently points to https://drupal.org/node/1066982).
- Node https://drupal.org/node/1066982 should have the defintions removed, and instead refer users to the view suggested in point #2 above.
A separate request for the non-webmaster task (task #2) is in the Drupal.org customizations issue queue.
This request, posted to the webmasters' issue queue, is only for the tasks numbered #1, #3, and #4 above.
Comments
Comment #1
gisleMade quotes blockquotes.
Comment #2
dddave CreditAttribution: dddave commentedWe usually don't mirror issues in different queues.
Comment #3
gisleIt is not a duplicate or mirror issue.
I've posted two different issues where two sets of people are involved, and the second issue depends on the first.
Oh well, at least I tried ...
Comment #4
dddave CreditAttribution: dddave commentedAh. I did not get it right then. Sorry.
Comment #5
gisleThanks for re-activating.
To me, this looks like adding the missing tag is a very trivial thing to do. Step #1 should take at the most five minutes for someone with the required access level. Doing it will not break anything, as it is just a matter of adding the six missing tag descriptions and editing the three tag descriptions that provides too little guidance.
What are the required decision making steps here? (I guess I am trying to learn how things are "done" on this community website.)
Is there some sort of protocol I need to follow to get an issue like this one reviewed (and accepted or rejected)?
Or is just a matter of leaning back and wait until somebody with the required decision making power notices the issue and either decides to do something with it, or dismisses it with a "Closed (Won't fix)"-notice?
Comment #6
dddave CreditAttribution: dddave commentedWe need some status descriptions to fill in the blanks, don't we? Any proposals?
This issue might get picked up during DrupalCon sprinting but even if not I'll make sure it won't sink down afterwards. I guess most people with the necessary permissions are in Austin at the moment so there might be not much movement for the next days.
Comment #7
gisleI've updated the community wiki with the text think should be used as official status tag descriptions.
The wiki is editable by anyone. Feel free to edit if you think the proposed tag descriptions can be improved.
Comment #8
gisleSome details about what is expected of co-maintainer applicants added to proposed tag-description for "Seeking co-maintainer(s)".
Comment #9
gisleFixed typo in title.
Comment #10
gisleFixed another typo.
Comment #11
gisleSuggested a stopgap solution in issue summary. Making these edits to the tag descriptions should be uncontroversial, and should not take more than five minutes for someone with the required access.
Comment #12
drummDidn’t catch this issue until now, it was done recently. The current descriptions are in the issue summary of #2277829: Project status tags are not well documented.