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 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 moreImprove issue management interface
What's your idea?
Move issue management tasks from comments to the issue summary and (optionally) make them editable in-line. Add a "last-update" widget to the issue metadata area that contains "revision-like" information about who/what/when/why the metadata was changed.
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 moreTopic pages
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
Back-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 morePrevent duplicate postings (for issue queue, forums, etc.)
What's your idea?
Automated system which suggest already existing similar posts when you are entering the title of new post. An alternate approach would be to improve Drupal.org search so that people could find related posts before creating a new one.
What are the benefits?
There are lots of duplicates everywhere: issue queues, forums. This will be a huge improvement and also a must-have for dedicated support system if we were to create one on Drupal.org
What are the risks?
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 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 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
What are the benefits?
Read moreJobs section
What's your idea?
Currently jobs are being published on g.d.o, all over the place, and it’s not useful for anyone. We need a specific section for job postings on D.o, in the Marketplace. With possibility to filter jobs, subscribe to specific type of jobs etc.
What are the benefits?
Dedicated place for people to post job announcement and look for Drupal jobs. Close to Drupal services listing. Better user experience than g.d.o/jobs. Potential revenue source, which will help make Drupal.org sustainable.
What are the risks?
Read moreImproved 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 moreReputation/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 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 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 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 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 more- « first
- ‹ previous
- 1
- 2
- 3
