Contrib developers often need some help figuring out the best way to maintain their modules, both strategically and tactically.
This can include (but is not limited to)
- git best practices in contrib (branch naming? How to commit patches? How to commit my own work?)
- How to manage the issue queue
- How to deal with difficult people in the issue queue.
When we reach consensus and develop some quality material, it can move over to the Best Practices section of the Handbook (under Start a new project).
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?
