Welcome to the brainstorming group for the 2014 Drupal.org roadmap! This group is to help the Drupal.org Software Working Group gather community input into the 2014 budget and plans for Drupal.org improvements. Please read the announcement for more background/details.
Latest ideas Most popular Recent Comments
To participate:
- Review the list of submitted proposals and "vote up" and/or comment on ones that speak to you.
- If you don't see your idea reflected, propose your own ideas using the idea template.
- While we want to hear about everything that's on your mind, we're especially interested in small, but impactful ideas.
- Proposals are wiki pages, so feel free to provide additional details in other peoples' proposals; think of them as "issue summaries" for ideas, so keep them neutral.
Voting/feedback will considered until 00:00 GMT on September 6, 2013, in order to give us ample time to make a proposal (which the results here will be a part of) for the Drupal Association Board Retreat prior to DrupalCon Prague. Thanks for participating!
Reputation/expertise system
What's your idea?
Currently we recognize only the contributions we can count automatically - code commits, documentation edits. We want to encourage and recognize other types of contributions as well. Idea is to implement reputation system which will allow people to add reputation points to other users via widgets on comments in issue queues, forums, doc pages, g.d.o posts, etc.
For more information see: https://groups.drupal.org/node/225824
What are the benefits?
Read moreShow user pictures on Drupal.org
Last updated by Sushil Kumar Sharma on Mon, 2013-11-18 10:54
What's your idea?
Add user pictures to posts and comments on drupal.org
What are the benefits?
Drupal is a community of people, it would be nice to expose this more. Bringing people to the surface would remind each other that we are human. The issue queue is a stressful place, we should be building relationships not breaking them down.
It would also increase recognition at Drupal meet ups, camps, and drupalcons.
What are the risks?
I'm not sure. Increased bandwidth? We would need to ensure images are cached.
Read moreEnforce Sandboxing Until Stable Release
What's your idea?
There are a number of projects that have NO release, NO activity and are years old that should either be moved to a sandbox, or outright deleted. These were created pre-sandbox days, although some have been created recently.
Read moreExplicit issue relationships
What's your idea?
This is contingent on us remaining on Project* for issue management, but if we move to something else (GitHub, GitLab, Phabricator, etc.) consider this a "I really really wish whatever we move to had this feature" consideration. (I know GitHub does not.)
It is increasingly common for issues to relate to one another. One may block another, one may be a spinoff of another, one may be a planned follow-up, etc.
Read moreAllow users to bookmark/favourite issues
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
Read moreMake popular projects easier to find from the header-search box
What's your idea?
Make popular projects easier to find from the header-search box. We could add a facet to solr for project usage and adjust that up as a relevancy factor so that items with high usage are higher in search results. When someone filters the facets to Projects we could also ignore whatever sort they have used so far and change it to be by install count.
What are the benefits?
Read moreBetter navigation for community documentation
What's your idea?
Sidebar navigation which expands/contracts without the need to reload page each time. https://drupal.org/node/1289090
What are the benefits?
Better user experience when browsing Drupal.org documentation and other content.
What are the risks?
How can we measure the impact of this idea? (metrics)
Who directly benefits from / will use this improvement? (target audiences)
Anyone browsing documentation and non docs book pages content on Drupal.org, e.g. press-releases.
Read moreImprove the module search (like old drupalmodules.com)
Last updated by Anonymous on Mon, 2013-08-26 20:34
What's your idea?
Make a quick search for a specific functionality easier by improving the search process for modules. The way drupalmodules.org has worked is a good example, with keywords and without a search button.
What are the benefits?
Drupalmodules.org is not maintained and outdated. It worked perfect for a lot of people, because it was a very fast way to find your module, only typing one or two keywords.
It is a difficult and time consuming proces to find the module, that gives you the functionality you want, in the current drupal.org module search.
Read moreSwitch to Drupal 8 for d.o. and g.d.o.
What's your idea?
To show the worls that Drupal 8 is the best there is, we should switch as soon as possible, preferably before Drupal 8 is released.
What are the benefits?
Show everybody that Drupal 8 is a good and flexible system. "Eat your own dog food"
What are the risks?
Probably lack of resources
How can we measure the impact of this idea? (metrics)
Who directly benefits from / will use this improvement? (target audiences)
The world, our community
Read moreSupport Composer on testbot and packaging
What's your idea?
I can't believe I didn't think to mention this one already...
Drupal 8 is making extensive use of 3rd party components, pulled in via Composer from Packagist.org. This is good.
Drupal 8 is checking all 3rd party components into our main repository, including the generated Composer files. This is bad. It's directly contrary to all Composer best practices, and makes any attempt to update our dependencies consist of 500 KB patches at least. This is not how it should work.
Why are we still doing that? Well, because
Read moreManagement tools for large initiatives
What's your idea?
The issue queue is not a PM tool. With more and more big initiatives around (e.g. Drupal core initiatives and others) we need better tools to manage their processes.
What are the benefits?
Possibility to efficiently manage large initiatives on Drupal.org. Without the need to use external PM tools, and without the need to use book pages or issues which are not suited for this purpose.
What are the risks?
How can we measure the impact of this idea? (metrics)
Read moreAdd Review points to user profile
Respect the Reviewer
As a core contributor it is great when contributor's name is added to commit message. But a contribute is never possible without a master reviewer. What is reviewer getting out contributing to a project?
In the issue queue a lot of issues get stuck at community need review (CNR). When you start contributing more and more it gets harder to find a reviewer.
If community wants to encourage contributors to review more and patches we should respect and honor the reviewers. We should pay them back.
What's your idea?
Read moreForce full-project application review for ALL projects, not one time only per user.
What's your idea?
Force full project review for ALL projects, not one time only per user.
Today if a user gets a project approved to be a full project the user gets a role which can promote ANY project in the future without review.
This should be changed force reviewing ALL new projects, instead of giving this role to the user.
Read moreImprove code navigation and readability on api.drupal.org (UI/UX, accessibility)
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.
Read moreOAuth authentication server for community sites
What's your idea?
Set up a community OAuth server that not only manages all the login to all the *.d.o server, but also allow third parties to authenticate against it. Particularly community oriented sites such as http://www.drupal8multilingual.org/ would greatly benefit from this.
The same server can then also be used for improved and centralized management of user profiles etc.
What are the benefits?
Read moreCreate Powerful and Relevant Drupal.org Search
What's your idea?
We have to create drupal.org search more powerful and relavant.
I have noticed when we search for module - Google search result is more accurate than drupal.org website inbuild search.
For Example - Lets serch for Insert Module - In drupal.org, you can see many insert modules are coming, but only "Insert" module is coming after many modules. But in Google, the first one is only "Insert" module.
Now, if you click on modules tab, we are seeing sort by Relevance. Now change it to sort by Most Installed. Still the insert module is not coming in the first.
Read moreAjaxify Drupal.org form submissions
What's your idea?
I think we should aim to AJAXify as many form submissions as possible. Right now Drupal.org has some great functionality, but not so much in interactivity. The Form API provides an excellent AJAX framework that can be used to AJAXify pretty much every form on the system.
What are the benefits?
Improved user experience, less load on the server due to less full page loads, and a better example of what is possible with Drupal.
What are the risks?
I can't think of any. Maybe someone else can.
Read moreRefresh Data on CertifiedToRock.com
What's your idea?
Refresh the data on CertifiedToRock.com so that recent contributors are better represented.
What are the benefits?
CTR could be a valid source for considering Drupal developers but due to the data being outdated it can not be used as a reliable source. With updated data current developers will be better represented and it could encourage new developers to contribute.
What are the risks?
A single refresh will not be useful. If the data goes stale again it will hurt new developers more than it will help.
Read moreProject Hierarchy For Contributed Sub-Modules
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.
Read moreProject 'Health Check' metrics, with auto 'Get involved' engagment
Last updated by jim kirkpatrick on Sat, 2013-09-07 18:00
What's your idea?
To put a block/pane on every project page on D.org that provides an at-a-glance summary of how 'healthy' the project is. This would replace/extend the 'Statistics' block presently implemented and provide a clear, colourful overview of how 'healthy' -- in terms of bugs, issue activity, maintainers and installs -- the project is.
Ideally, to have the 'at-a-glance' properties, these would be clearly rendered to be 'good', 'ok' or 'bad' somehow, and compared to a standard/good practice set of metrics.
Read more