Wastelands
At Drupalcon Boston I proposed the idea of a repository for code that was unfit for inclusion into the main Drupal.org module repository. This is because companies create this sort of code all the time and have no where to put it. Sometimes this code may overlap in undesirable ways with existing modules, other times this code may simply perform a very SMALL use case of what could potentially be a larger group of needs.
When I proposed this to the Dev Seed developers they seemed to like the idea, however no one had the time to create the site. This same proposal was put forth at Drupalcon Szeged by another individual, and again after speaking with a few of the other Drupal companies the general response to this idea was that it might be a good one.
I've committed to creating this site, however we need a group to help focus on exactly the features needed to make it useful. This will include feature definitions and wireframes to make this as smooth and easy a site to implement as possible. My hope is that other developers and especially the Drupal related companies will join this group so that we can create a truly useful repository from which fully developed modules might eventually join the main Drupal repository.
WOW! I'm not alone here anymore!
HAHA, welcome everyone, been a while since I checked this group. So, here's the basic need to get us going. I'd really like to put our heads together and start to put a list of features that would be needed for this sort of thing, together. Let's get it started, and we'll see where it goes from there.
Obviously we need some serious taxonomy controls to help make code easier to find and categorize. I'd like to start off by asking what sort of scheme you all think might work best here.
Eclipse
Wastelands: Let's start thinking about use cases and spec
So I'm at DrupalCamp UK and the topic of this site has come up again.
Lots of developers mention cool modules they've written in-house but aren't releasing because they're too specific to their projects or too raw for a release.
A space where these could be released without too much expectation would mean the next person who needs this feature doesn't reinvent the wheel, but instead can give some time to pushing the code a little more towards being generic and ready for release.
So let's think about use cases for the Wastelands and the spec we'd need.
Turn it more positive : what about a "Recycling drupal code factory" ?
I think there is a huge potential in this idea.
There are lot of modules on d.o that are not maintened, and lot more code never published.
A true "recycling drupal code factory" could have several benefits :
To allow the drupal community to better understand the general needs behind lots of "custom modules", reuse some code but also some conception work.
For the beginners users of d.o, a smaller list of contributed modules really maintened instead of a large list of 2000 modules with lot of weird modules would be a huge time saving.
repo
So I came here expecting a list of a bunch of modules that has been tossed out as incomplete/un-generalized. Found nothing but a poll. Hrm.
So the thought then is, how do I get a list of modules that are categorized in a way that I know that they either a) need work or b) are specific to a private company's needs but released for other to at least peruse/hack/learn from/or throw away?
I don't think we can actually just list them here...
I don't think that we should really just throw them up on d.o (read: http://drupal.org/node/307211)...
Do you collect code scripts?
