Project quality indicators
Ratings, reviews, and statistics/metrics for projects on Drupal.org to help determine their quality.
This is an experiment to collect feedback on improvements to Drupal.org that the community would like to see happen, or like to help with. The Drupal Association will use this feedback, along with priorities from our sponsors and the Drupal.org infrastructure team, to determine development priorities as part of our 2012 strategic objectives to make Drupal.org awesome!
169 votes
I disagreeRatings, reviews, and statistics/metrics for projects on Drupal.org to help determine their quality.
118 votes
I disagreeWith Drupal 8 due out in a year and a bit, it's high time to get our flagship site onto the latest stable version—Drupal 7!
98 votes
I disagreeIf commits reference a given issue, cross-post them to the issue so they're visible in the comment stream.
96 votes
I disagreeOur current http://drupal.org/cases section is very sad. We should make it show off how awesome Drupal can be with pictures, how-tos, case studies, and more!
95 votes
I disagreeDrupal.org is a bit painful to browse on a mobile device. It'd be cool if it used responsive design to show off what Drupal can do!
89 votes
I disagreeMove from forum discussions to Q&A format, with ability to vote up/down comments. Ability to seamlessly move from a support request to issue and back would be hugely beneficial.
85 votes
I disagreeBefore posting new projects, issues, forum topics, etc. show user a list of things with similar titles/descriptions and prompt user to confirm their submission isn't a duplicate.
78 votes
I disagreeIn addition to running patches against automated tests, test them for performance as well so regressions are caught before commit!
77 votes
I disagreeThe goal of this sub-project is to build an expertise/reputation system which will: a. expose all the different types of contributions (including non-code ones, which can't be measured by simply counting data in database) b. expose field of expertise of individuals, to make it easier to understand "who is who", who is active in which field, whose opinion is backed up by expertise in this specific field c. encourage more ...more »
The goal of this sub-project is to build an expertise/reputation system which will:
a. expose all the different types of contributions (including non-code ones, which can't be measured by simply counting data in database)
b. expose field of expertise of individuals, to make it easier to understand "who is who", who is active in which field, whose opinion is backed up by expertise in this specific field
c. encourage more contributions, especially non-code ones, by recognizing them, showing that community values them, giving feedback to the new contributors when their contribution is useful and motivating them to continue
« less full details »
76 votes
I disagreeWe are not just blue nicknames on a screen. Show our community our faces :)
74 votes
I disagreeIntegrate some kind of donation framework into Drupal.org to allow people to donate to maintainers of projects to help show their appreciation.
65 votes
I disagreeIn addition to the community-managed documentation, the documentation team also wants to have a more curated documentation area, where we can have better control over the quality of the docs, as well as of what merits inclusion.
64 votes
I disagreeProvide the ability to create first-class forks / sandboxes of parent projects and perform pull requests, tightly integrated with the canonical project/repository.
63 votes
I disagreeIt's hard for new contributors to find a suitable issue to get involved. Starting with a "Novice" issue always makes sense to understand how the process works, but what do you do after you crossed that line?
Let's add a new, optional "Difficulty" property to all d.o issues:
- novice
- beginner
- intermediate
- advanced
- expert
- ninjutsu
59 votes
I disagreeMove job postings out of groups.drupal.org and onto drupal.org, and improve the listings with ties back to companies and locations + featured listings to help fund d.o development.
55 votes
I disagreeThe initiative to Improve Community, Support and Getting-involved Landing pages will help direct people to the areas most relevant and useful to meet their goals, such as: Community: "Where is everybody? I want to meet people and participate, learn and share." Get involved (or getting involved): "How can I help? I need specific guidance on how I can be an effective contributor. " Support: "I need help! Where can I find ...more »
The initiative to Improve Community, Support and Getting-involved Landing pages will help direct people to the areas most relevant and useful to meet their goals, such as:
Community: "Where is everybody? I want to meet people and participate, learn and share."
Get involved (or getting involved): "How can I help? I need specific guidance on how I can be an effective contributor. "
Support: "I need help! Where can I find answers to my questions?"
« less full details »
50 votes
I disagreeAdd a big visible DOWNLOAD BUTTON on d org homepage
- users are always groping for it
- all similar sites have this
48 votes
I disagreeDespite the awesome "Follow" button that was added to the top of issues, I still see a lot of people posting "subscribe" or "+1" in the issue queues. I think there are two reasons for this: 1) If you aren't logged in, you don't see the Follow button 2) It only appears at the top of the issue, but people are going to be most tempted to "subscribe" when they have read to the bottom of the thread and determined that the ...more »
Despite the awesome "Follow" button that was added to the top of issues, I still see a lot of people posting "subscribe" or "+1" in the issue queues. I think there are two reasons for this:
1) If you aren't logged in, you don't see the Follow button
2) It only appears at the top of the issue, but people are going to be most tempted to "subscribe" when they have read to the bottom of the thread and determined that the conversation is incomplete and they want to get updates.
The fixes I'd suggest:
1) The Follow button appears to anonymous users, but takes you to the login page.
2) The Follow button appears at both the top and bottom of the issue. The one at the bottom should be positioned above/below/inside the comment form, wherever it is most likely to catch the eye of someone about to post a quick "subscribe" comment.
3) Comment validation should include a check for basic "subscribe" posts, and the error should remind people to click the Follow button.
« less full details »
48 votes
I disagreeIn the same way in our Drupal Installation we can see what modules are required for a specific module and what module use a specific module. Could be good idea put couple blocks in a project page to show how modules are tied, because can provide to site builder an idea how strong are modules and how get examples about how to integrate this module in a custom implementation. For instance in services module/project page, ...more »
In the same way in our Drupal Installation we can see what modules are required for a specific module and what module use a specific module.
Could be good idea put couple blocks in a project page to show how modules are tied, because can provide to site builder an idea how strong are modules and how get examples about how to integrate this module in a custom implementation.
For instance in services module/project page, could be good idea check in what way services module is implemented by other modules.
« less full details »
44 votes
I disagreeShow upcoming events in your area, show what events people are going to on their profile, show a map of events around the world, etc.
43 votes
I disagreeSection : http://drupal.org/project/themes
Add/Update fields (essential) :
1. Demo (link or screenshots)*
2. Tags (for filter or search)*
+ Display section, more like a gallery.
I'm sure, this will attract new users to have a try on drupal CMS. And of course will also appeal to designers to contribute more themes to the community.
42 votes
I disagreeThe http://drupal.org/project/project_browser module allows browsing themes and modules from within your Drupal site. In order to use the module, we require server changes to Drupal.org.
40 votes
I disagreeThis already exists (community) but it would be cool to formalize it a bit more. Proteges get a list of issues based on the 'level' they choose. They get a mentor to help them try and solve that issue. Mentors would volunteer to help new contributors. and choose a 'level' they were willing to support. Proteges would become active contributors quicker and hopefully become mentors themselves. By using the mentoring ...more »
This already exists (community) but it would be cool to formalize it a bit more.
Proteges get a list of issues based on the 'level' they choose. They get a mentor to help them try and solve that issue.
Mentors would volunteer to help new contributors. and choose a 'level' they were willing to support.
Proteges would become active contributors quicker and hopefully become mentors themselves.
By using the mentoring system per issue, Mentors wouldn't get burnt out and proteges wouldn't become too reliant on one person.
I think it is very important to focus on all levels of contributors. Docs, New people, Intermediate programmers etc.
« less full details »
40 votes
I disagreeProblem:
Our issue guidelines for Drupal core (and other projects) explicitly state that users should submit steps to reproduce. However, many people overlook this.
Solution:
Improve the form UX. When an issue is filed as a bug report, a field or template for steps to reproduce is automatically displayed.
36 votes
I disagreeAllow modules, themes, sandboxes, etc to act more like 'Groups' in which an issue queue is only one aspect of them. Modules could have discussions, wiki pages, events, and could help potentially help tie in the work being done with initiative pages. Functionality like maintainers being able to send out e-mail announcements (i.e. Broadcast) to people 'subscribed' to a module with security releases or major features. This ...more »
Allow modules, themes, sandboxes, etc to act more like 'Groups' in which an issue queue is only one aspect of them. Modules could have discussions, wiki pages, events, and could help potentially help tie in the work being done with initiative pages. Functionality like maintainers being able to send out e-mail announcements (i.e. Broadcast) to people 'subscribed' to a module with security releases or major features.
This is similar to http://drupal-association.ideascale.com/a/dtd/Topic-Pages/100212-18300 in that I would hope the work there could also be applied for individual projects.
« less full details »
Social Web