1
I've been working with XOOPS since 2003, and have been a software developer since the '70s.
For the past 1-1/2 years, I've been employed full-time by a company at which my job is to develop new XOOPS modules, and modify the core when required, to meet the requirements of the clients. I'm working with both XOOPS 2.2.5-RC2 and XOOPS 2.0.16. In addition to core hacks, I've written 10-12 modules; they haven't been published publicly.
Ideally, I'd like to work on core maintenance/development that fits both my customers needs and the XOOPS project's needs.
If it were up to me, I would first meet with the other developers to define goals, i.e., the team's direction. Then the goals would be translated into specific action items which could be assigned to individuals or small groups. But if the team leader has another approach in mind, I'm open to ideas.
I also think that the development process should be more visible. That is, the developers should communicate primarily in a publicly-readable venue (forum, mailing list, etc.). This would make it possible for additional people to help out, since they would be able to see what's going on and what needs to be done.
Dave Lerner (Dave_L)