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)
How many people(sites) use this module.
Who directly benefits from / will use this improvement? (target audiences)
Drupal site builders and administrators.
Are additional resources available for discovery/implementation? (volunteer effort, financial backing, etc.)
The module is basically ready, it needs security and performance review
https://drupal.org/node/1243332
Comments
UX studies have confirmed
UX studies have confirmed that the lack of an in-app project browser in Drupal is a major impediment to new users. This is an extremely important issue to focus on. Once we have project browser information available from D.O, we can get traction on the contrib side and make progress towards introducing a browser in to the next version of core. I can't support this enough!
I agree that this is a major
I agree that this is a major UX issue and would really help to push Drupal into the hands of the more mainstream, novice users. I built the Project Browser contrib module (https://drupal.org/project/project_browser) as well as the server module (https://drupal.org/project/project_browser_server) and pushed for inclusion in Drupal 8 Core, but there we weren't able to get the server module up on D.O in time to see much progress. I was also finishing my school finals during that time and so wasn't able to spend as much time as I had hoped on it. I'm still very interested in seeing this see the light of day, and will again pledge my support to getting this done!
Could we maybe get this tried
Could we maybe get this tried out in some of the major Drupal distributions, and see if it actually gets a lot of use among site builders ? That might get it enough attention that running the server module on d.o would get support.
That's a catch 22
That's a catch 22 unfortunately, since the module won't work if the server module isn't on d.o
Expanded the title...
I expanded the title slightly here, as I'm not sure people outside of the implementation issue for this would know what this meant at a glance.
I wish I could upvote this
I wish I could upvote this more. It would be a huge step forward in my opinion. I think there was also a suggestion on here for a module rating system that would be cool to see integrated with this.
wildkatana What were some of the barriers you were up against other than time? Could you list them in the summary under risks?