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!
Subscribe with RSS 
Recent comments
It really would be great!
It really would be great!
I agree!
I consider this an essential feature. Having a search for "Views" actually display the Views module in the search results should be white-hot on this list.
Utilizing search is one of the areas a new user will first encounter Drupal's abilities and to have ApacheSolr simply not work is an embarrassment.
This idea has been
This idea has been implemented as a part of Drupal.org Drupal 7 upgrade, see this blog post for more information: https://association.drupal.org/node/17983
The difference is only that when someone changes metadata of the issue, we do generate a comment automatically to notify others about the change.
Yes. A redesign + responsive
Yes. A redesign + responsive theme. I figure with the pending release of Drupal 8 it is a good opportunity to reface and modernize the site (since other UX ideas are posted). I gravitated toward Foundation just to float the idea out there.
My +1 to moving source code to GitHub
Use the Issue Queue of Drupal.org to handle issues, and code with lots of patches attached in comments is just primitive. GitHub have much more productive tools to handle cummunity contributed softwares stuffs than what d.o has today, and we believe it should be used by the Drupal community.
Contributions authorships are also other thing that sucks in d.o, since authored commits are made by tagging the user with an @username tag. I know there are ways to made the commit with authorship information, but hey, there are GitHub which already have it implemented and lot of graphs of comminity contributions. Why not use it?
Drupal community must focus in the Drupal platform development itself, and leveraging resources like GitHub to streamline the contributions to the Drupal core. If we can save time and money by avoiding to build a big source code hosting solution, so I really believe we SHOULD do it.
In what way? Seems like it
In what way? Seems like it would go with this idea:
https://groups.drupal.org/node/312823
Yes please. The old forum is
Yes please. The old forum is a cesspool.
It will be included, this is
It will be included, this is what "with possibility to convert issues and forum topics into 'questions'" in the description is about. I'll add "and back" as well.
IMO Bluecheese is already
IMO Bluecheese is already amazing.
Pricing!
Github: Free, unless we want private repos (Bluecheese?)
GHE: Not possible, per https://enterprise.github.com/faq#faq-7. Also very expensive. ($5000/yr for 20 accounts)
GitLab: Free for "CE", paid for "EE". Open source.
I think GitHub is a great
I think GitHub is a great service. GitHub also offers an API, so we can still create d.o project pages, based on the data in GitHub. There is already a Drupal mirror on GitHub (github.com/drupal/drupal), so 1) you can see what the code browser is like and 2) we might consider accepting GitHub PRs for a while, just to see what happens.
Yes
What? There are Drupal forums? Just kidding, but yeah SE is so much user friendly both for persons looking for answers and persons helping.
Plus, the reputation system kind of pushes forward to help too!
Rephrase the title and add link to similar proposal
@webchick
I've almost voted in this proposal thinking it was the same thing. I guess many people did vote on it when they first read "pull requests".
Maybe rephrase the title to something like "Implement pull requests in drupal.org" AND include a note on top of the issue description linking to the similar proposal. Of course, linking back from the other proposal. In addition, explain the differences: one is for implementing in d.o, the other is to make PR in Github.
Issues in d.o?
I'm really up for hosting repositories on GH or any other provider that offers similar quality of services.
Though, I'm not sold d.o is good for issue discussion. Discussion viewing code as in GH is a great feature.
Great idea
Huge +1 as well. Their SEO ranking is just overwhelming.
Releases can be centralized
Releases can be centralized in d.o, even using GH for hosting repositories.
Move Git repositories to Github
see https://groups.drupal.org/node/313068
Agreed
Seems like a goo idea, I get most of my answers from there already....
Already happened…
As klausi mentioned, the SEO of SE is so good that when I Google search for Drupal problems, I usually get SE answers. And the Drupal community on SE is so good that the answers I find are correct!
I'm in favor of closing the forums on d.o and directing people to SE. :-)
yes
For me this is a no brainer, although I have to admit I do not really use the d.o. support forums and I'm using SE once in a while.