Jonathan Kamens wrote:
Kobus Myburgh writes:
However, we have a third custom module which I'm not sure yet whether I'm going to try to contribute to the community. It's called "school_directory", and it provides a browseable, searchable directory of a school's parents, students and staff, including photos for parents and staff. I'm not sure it's in a contributable state because
This would be very useful to me :-) Even in it's "rough around the edges" state. I am maintaining 2 schools' sites and at the moment we use the plain ole members module to give us some idea of the users on the site. I would love to see this!
I'm happy to share the code; I just need to figure out the appropriate way to do that. This raises in my mind a question that can probably be answered by the people on this list.... In general, how "solid" should a contributed module be before it's put in the repository and advertised?
It shouldn't have parse errors... ;) You can indicate on the project page that the module might be only alpha or beta quality. In this case it is a good idea to not branch it for the current stable branch (DRUPAL-4-6 nowadays) even if it is supposed to work with it. You should probably not commit modules that you don't have any intention on making it usable. Just hoping for patches usually won't help. Cheers, Gerhard