Medium difficulty

What's your idea?

Keep the current drupal.org theme, but make it responsive and more readable on a wide array of devices.

What are the benefits?

What's your idea?

Replace portions of drupal.org's repository-related code with components from the Phabricator project (http://phabricator.org/), specifically Differential (a code review tool), Diffusion (a repository browser), Arcanist (a CLI interface for the above), and Conduit (an HTTP JSON API for script integration).

What are the benefits?

What's your idea?

Allow to bookmark/favorite issues without abusing the Assigned field or issue tags.

For contributors that are involved in a large amount of issues, the ones you want to keep track of quickly get pushed out of your lists by comments in other issues and it gets hard to keep track of ones that are more important to you or ones that you want to come back to in the near future.

A related issue for this is https://drupal.org/node/1621714

What's your idea?

Instead of moving all projects to github, we might consider using a self hosted GitLab, see also Move Git repositories to Github

What are the benefits?

Since GitLab is very similar to github adoption will be straightforward, but it also allows us to completely control the environment (community edition is open source w/300+ contributors).

Build-in features:
- hosted on our own servers
- better git viewer
- integrated dreditor (comment on line level)
- inline editing of all files

What's your idea?

Implement a hierarchy of modules. For example, allow a module maintainer to specify that the module is designed specifically for xyz module. Let's take the Commerce module as an example. There are countless modules for the Commerce project, but trying to find and filter for the modules that only work with and were specifically designed around Commerce, is near impossible and extremely time consuming. The most efficient solution is for the Commerce Guys to create their own website and list all of the modules that are designed around it, at which point they point back to D.O. That is only one of a handful of projects which takes this approach. What about the countless other modules that have no central point of interest? That leaves us as users with the only option of pouring over the countless unorganized list of modules on D.O.

What's your idea?

http://drupal.stackexchange.com/

Instead of further using the support forums on drupal.org we should point people to a place where they are more likely to get an answer, which is currently Drupal Answers. This is easy to implement: just close down the forums on drupal.org, update the documentation and create some pages that point to and explain Drupal Answers.

See also a related, opposing idea, Dedicated support system

What's your idea?

Make it easier for users of api.drupal.org to view and navigate the code of core files and classes by changing the clickable "View source" text to a widget that more obviously indicates its functionality and implement an IDE-like structure navigation pane that lists the components of a file or class and auto-scrolls to their source when clicked.

What's your idea?

'Topic' page aggregates all activity across d.o, which was tagged with this specific topic. For more information see: https://groups.drupal.org/node/144584

What are the benefits?

• a way for people to identify their expertise
• a way to aggregate content of interest to that topic from across Drupal.org
• a way to see what is happening around specific topic right now, where and who is active

What's your idea?

When commit is made, which is referencing specific issue, post a comment on that issue to notify people about the commit.
Some more info here: http://drupal.org/node/493074

What are the benefits?

Issue queue users will know when there was actually a commit for specific issue.
Also finding the 'fix' for an issue will be easier, just click the commit link and you see what needed to bge changed.

What are the risks?

How can we measure the impact of this idea? (metrics)

More comments in the issue database.

What's your idea?

This will make possible new Drupal module, which allows to browser Drupal.org modules and themes from inside Drupal installation. Future plan is to make this module part of Drupal core.

What are the benefits?

Drupal users will be able to browse Drupal.org projects (modules/themes) from within their Drupal installations. There are no visual or functional changes for Drupal.org itself.

What are the risks?

Possible performance-related impact on Drupal.org.

How can we measure the impact of this idea? (metrics)