Drupal Answers is a question and answer site for Drupal developers and administrators. It only takes a minute to sign up.
Sign up to join this community
What is the best place to make a feature request about the drupal.org website?
I probably spent an hour searching. There is/was the redesign project, there is the drupal.org issue queue but I was refused access.
FYI - I'd simply like to suggest that project owners have a tab for "roadmap" or "project Future". Sure, the summary page can include that but often it is crammed with things and maintainers forget to talk about what plans they have, what they need, etc.
Generally speaking, the correct place to post feature requests for Drupal.org is the Drupal.org customization project issue queue.
However, you also wrote:
FYI - I'd simply like to suggest that project owners have a tab for "roadmap" or "project Future".
If you just want to suggest that project owners publish a "roadmap", you can add that suggestion to the community documentation. It is a wiki so you don't request anything - you just do it (like I just did).
If you want to actually modify the project page layout by having a feature where project owner's may add an addtional tab for "Roadmap" to the page summary, you request this in the Project module's issue queue
Finally, I shall not suggest you use the Webmasters issue queue for any type of feature requests. The Drupal.org webmasters issue queue is for reporting spam, broken links, or user account problems at Drupal.org - and that is about it. My experience is that nothing much happens to feature requests posted there, even if the request just involves flipping a trivial setting in a module already installed. The webmasters obviously have the power to do this, but they do not make decisions about such things. They usually move feature requests to the Drupal.org customization project, and bug reports to the Infrastructure project.
There are indeed quite a few "projects" on Drupal.org that might be a candidate for suggesting such feature request. My best bet for you would be the "projects" Project or Project Issue Tracking.
However, are you sure you want to suggest such feature? Things like "roadmap" are typically located already in either of these areas on drupal.org (related to a specific module and/or distribution):
The technique that I believe works best so far, is what I've started to use in (eg) the Charts module. I.e using issues such as Charts 7.x-2.0 Release and Charts 7.x-3.x Release. These are "parent" issues to which other issues are referring to as their "parent" issue. Combined with the status (color) of each child issue you then also get an idea of the progress of such release. Checkout those parent issues to see that technique at work.
If such feature ever gets requested/implemented, I'd assume/expect it to be another field without the "Resources" section when you edit the project page of a module, where today you can already enter links to Demos, Screenshots, Community docu, etc). These links, if provided, are then shown within the "Resources" block when viewing the project pages.
I will answer this question basing on what I learned in the period I was site maintainer on drupal.org. My answer doesn't reflect in any way what the current site-maintainers think, or the thought of the maintainers of any module.
The first project queue one would think is the one for the Project module since Drupal.org is effectively using that module, but I think it's improbable the current maintainer would plan to add such feature, if that is not generic enough to be applied to other sites as well. The answer is probably going to be something on the lines of "If you want to implement that feature, you can implement it in a custom module."
Drupal.org does use custom modules to implement those features that are not currently used in any module, or to alter how some of the features are implemented in existing modules.
If the feature request involves writing code, then the project queue for Drupal.org customization project is the best choice. In this case, I would also provide a patch for such feature to be implemented.
If the feature request is about a module to enable, I would use the Drupal.org site-maintainer project queue, since some of the site-maintainers have the permission to enable modules on Drupal.org.
In both the cases, be ready to convince other users this is really necessary. In the case of custom code, it is much preferable to be ready to provide a patch for one of the custom modules used on Drupal.org, if one of the maintainers find the feature request interesting.
