duketown wrote:
Are the ideas that you put down here for a company that has paid employees (I don't know about Linux but Microsoft certainly is paying the developers) (I was typing this before you replied stating the type of work you are doing). I have not read any material of anyone being paid for their work at/with CMSMS. Bearing that in mind I totally agree with calguy1000 to release whenever appropriate. Would this be in some sequence/cycle then this would benefit the developers, since they know in advance when they are expected to upgrade their module(s).
Well... my current day job as a web developer mostly involves CMSMS.... but to develop websites with. To do that, I have been writing modules, and fixing modules to provide the functionality our websites need. My primary responsibility is not to fix and maintain CMS Made Simple.... therefore, any issues that come up with the core, and modules get fixed and released on an 'as needed' basis. I try to refrain from modifying the core, unless there are no choices, or no realistic ones anyways.
Regarding fixed schedules or beta programs.... We've done things like this in the past. We hoped to get module developers to update their modules, and to allow others to test for us to hopefully identify any bugs before the final release. The conclusion by myself and others on the dev team is 'it doesn't work'. Everybody here has their own schedules, their own lives, and their own priorities.... Very few users test, and most module developers (including myself) are too busy doing other things to worry about catching up on their modules until such time as a personal need arrives, or somebody is willing to pay a bit of money to get the developer to adjust his priorities.
calcuy1000: as you know I'm currently working Lahuindai to prepare Shop Made Simple. Next to this 2 modules for my own interrest that I want to share later on. I don't have much time leftover, but I volunteer to help you on modules that you wrote.
Yes duketown, and I was hoping to chat with you in irc about your modules, as Ted and I are doing a similar effort... I don't see a big problem in duplicating effort (it gives users more choices)... but it'd be nice to compare notes, etc.
And as far as volunteering for help on my modules.... I could keep you busy.... got any priorities in mind?
As far as cleaning up the 'broken' modules, etc. no, nobody has had time. Our Q/A team lead left, and the documentation and website teams have been very busy with their personal priorities.... Hopefully this'll clear up in the next month or so.
As I said... we need volunteers... I think that there are two paths for volunteers, starting out on support/documentation/testing/translation..... or development. if starting on the development branch we usually ask people to submit patches to the core or to various modules for review before getting commit access.
.