Welcome
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!
Drupal.org 2014 roadmap brainstorming
Make the Bluecheese repo public
What's your idea?
The Bluecheese repo is not hosted as a public project on drupal.org. The original motivation behind that was to protect the branding elements of Drupal.org. This private repository adds an extremely high barrier to contribution.
I think it's possible to make the Bluecheese repo public, allowing members of the community to contribute easily, by moving the drupal.org branded elements (the logo) outside of the theme.
What are the benefits?
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 moreImprove the module search (like old drupalmodules.com)
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 moreMake the Drupal.org theme responsive
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?
Read moreOpt-in Release Management Scheme for Contrib
What's your idea?
Lets put a good looking badge on project pages who's maintainers are doing a stellar job with release management. They need to be given the cred they deserve and users will be able to find their projects more easily too.
The #D7CX pledge, http://cyrve.com/d7cx, for modules to be ready for Drupal 7 was quite a success in the sense that a lot of contrib maintainers signed up to it. Unfortunately only a fraction of those projects where ready when Drupal 7 launched, despite the long delay.
Read moreImplement select Phabricator components on Drupal.org
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?
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 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 moreIRC Integration
What's your idea?
Create an IRC client to be used on Drupal.org, giving users the ability to participate on IRC directly on Drupal.org.
What are the benefits?
Opens up IRC to users who may not know how to access IRC, or even know that it exists. We could maybe set up a way of syncing Drupal.org usernames with IRC.
What are the risks?
Overrun of users on IRC channels.
How can we measure the impact of this idea? (metrics)
Analytics on the embedded chat page.
Who directly benefits from / will use this improvement? (target audiences)
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 moreUse GitLab for all projects
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
"Need Maintainers" page
What's your idea?
Add a "Need Maintainers" page on drupal.org. This page would consist of two parts: First part would be written by the drupal core team, and would highlight core components that need maintainers/coordinators; Second part would contain a list of contrib modules that have a "seeking maintainer" status.
What are the benefits?
This would help fill in the gaps, as people join and leave the drupal community. Right now, this information is broadcast through announcements or posts that reach drupal planet, and then go out of sight, and can easily be missed. Directing volunteer developers to contrib modules that need maintainers helps their progress, makes contrib more reliable, and makes a drupal 8 port more likely.
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 moreDisplay core commits on user's profile page
What's your idea?
For anyone who hasn't contributed to any modules or themes but has just participated in Drupal core, their profile page looks pretty empty and it doesn't show any mention about their involvement in core.
I agree with xjm here and quoting again:
A Drupalist's d.o profile is essentially his or her résumé.
What are the benefits?
Attract and motivate more contributors to core.
Who directly benefits from / will use this improvement? (target audiences)
Read moreA proper UX strategy
What's your idea?
The community is doing an amazing work maintaining, improving and adding to the *.d.o infrastructure. But it is very much feature focused and where features often are looked at and implemented in isolation and from a technical point of view.
*.d.o has, according to https://drupal.org/home, a cool million users. To provide a great UX for all of them and where they can focus on getting things done is without a doubt a challenge. A challenge I feel isn't really being taken completely serious.
Read moreRedirect Drupal support forums to Stackexchange Drupal Answers
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
Read moreMove Git repositories to Github
Know something about Github or Drupal.org? Please help flesh out the Drupal.org vs. Github feature list!
August 27: Here's an attempt at summarizing the high-points of discussion/research so far.
What's your idea?
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 moreAutomatically name patches and create interdiffs
What's your idea?
Automate patch naming during the upload process so that users wishing to contribute a patch may upload a file of any name and it will automatically be rewritten and saved to Drupal.org servers following the correct convention.
Read moreNew, redesigned drupal.org theme
Last updated by webchick on Sat, 2013-08-24 06:24
What's your idea?
Redesign drupal.org's theme to be more modern and cater to mobile devices.
What are the benefits?
Drupal.org becomes responsive out of the box with an opportunity to 'refresh' the way the website looks. Perhaps a 'flat design' or some friendlier UI re-arranging. Most developers don't seem to care, but a fresh face could attract new people and make Drupal more appealing by showcasing how beautiful a theme can be in Drupal. It would be a good opportunity to put a new face out before Drupal 8 is released.