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!
Idea template
Please use the following template when proposing ideas for the 2014 Drupal.org roadmap:
<h2>What's your idea?</h2>
<h2>What are the benefits?</h2>
<h2>What are the risks?</h2>
<h2>How can we measure the impact of this idea? (metrics)</h2>
<h2>Who directly benefits from / will use this improvement? (target audiences)</h2>
<h2>Are additional resources available for discovery/implementation? (volunteer effort, financial backing, etc.)</h2>Move 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 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 moreImplement edit-in-browser and pull requests on Drupal.org
What's your idea?
Pull requests implemented in drupal.org and the ability to edit files in browsers.
There is a similar proposal: Move Git repositories to Github
What are the benefits?
Reduces barrier to entry for contributions
A short story
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
Display 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 moreBack-link commit messages on issues
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.
Read moreReviews and ratings for projects
What's your idea?
Add possibility to write a review about project (module/theme) on Drupal.org. Add possibility to rate projects and to filter projects by rating/number of reviews.
For more info see: https://drupal.org/node/1580230
What are the benefits?
Drupal.org has huge number of modules and themes available for download, often it is hard to choose which ones of them to use when building Drupal site.
The goal is to help site builders determine quality of projects on drupal.org site by adding various indicators to project (module/theme) pages.
Read more"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 browser server (search for and install modules/themes from Drupal itself)
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)
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 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 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 moreMake drupal.org maintainable via more automated tests and better staging environments
What's your idea?
I've been pushing for years to get Drupal's infrastructure on a path to more automation. It would be helpful to have:
<
ul>
Improved notifications system
What's your idea?
Currently we have email notifications for issue queue only. There is so much more people want to be notified about: comments on case studies, documentation edits, new releases of projects, comments on a.d.o blog posts, comments on forum posts.
What are the benefits?
People can find out in time when something they are interested in has changed or there are new comments. E.g. case study authors can know when someone commented on their case study and reply in time.
What are the risks?
Read moreImprove code review tools
What's your idea?
Code review is an essential part of the contribution process. At the moment we have a sub-standard tool for doing this, which is not easily accessible to everyone (requires a user script installed to the browser). This would greatly improve code quality.
Currently, a javascript Browser plugin, Dreditor provides some of this functionality, but at a very basic level.
Open source tools that could be used include Phabricator http://phabricator.org/#differential
Github pull requests provide this capability.
What are the benefits?
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.
What are the risks?
Read moreProject page and project listings redesign
What's your idea?
Redesign project pages and project listings to better showcase what the projects are about, make it easier to filter them and find fitting ones. Particularly themes.
What are the benefits?
Better display for module and themes, makes it easier to choose the one user needs.
What are the risks?
How can we measure the impact of this idea? (metrics)
Who directly benefits from / will use this improvement? (target audiences)
Site builders.
Read moreMake 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 moreDedicated support system
What's your idea?
Build a dedicated support system on D.o, Q/A style. Linked to projects, with possibility to convert issues and forum topics into 'questions' (and back), vote for 'best answer' etc.
See also a related, opposing idea,
Redirect Drupal support forums to Stackexchange Drupal Answers