Hi Guys
I don't want to be difficult but is having all these modules as one project really a good idea? Doesn't this make releasing new versions very difficult? I'm pretty sure there are modules in the contrib project that is production ready, but the project as a whole cannot get out of "dev" because some other modules are holding it back.
May I suggest that for drupal 7 all modules get a separate project page? It just makes everything easier. For example, if I subscribe to the issue queue of the 1 module I use I don't have to get the issues of all the other modules that I don't use. Updates can roll out quicker and if there is a security problem it doesn't have to affect all the modules as a whole, just the one module
Thank you for your consideration.
Comments
Comment #1
nightowl77 commentedFixed title: this -> these
Comment #2
kbahey commentedI agree it is suboptimal.
It was a good idea at the time, because we did not know what we know now. And it also still has its uses: for example, when someone says "here is a userpoints module that I wrote, but I can't/won't have the time to maintain it." Where do we dump these? If no one knows they exist, they may not get patches or future upgrades.
Putting each module in its separate project is not an option unless a few people volunteer to take each a few modules and make them into separate projects. I can't overnight maintain 7 more modules.
The other option is to get a few people to help as co-maintainers for this project. Any volunteers?
Comment #3
berdirWell, as kbahey said, it is a collection of modules which aren't really maintained. That will slightly change in D7 as it will only contain working, tested modules from the very beginning.
Nothing that can be fixed imho, but you are welcome to talk to us if you want to move one of the modules into a separate project.