44
It is my humble
opinion that most projects that fails are unfocused. So I think it is important to limit the task from the start and make it very clear what the goals are. I prefer to start with few and easy to reach goals and then maybe expand them later on.
1. So I suggest that we concentrate on modules and leave themes for later on or for someone else to deal with. We should also select a small number of modules at first and expand later on.
2. We should focus on behavior of the modules. That is how predictable they are to use and how well they fit to XOOPS standard behavior and use standard XOOPS features like notification, themes, templates, installation and so on
3. It is important that the code is well documented and follows XOOPS standard with encapsulated and documented variables, function calls and so on.
4. Maybe we are fooling ourself if we believe that this is mostly objective work and that our results will be figures and graphs. I dont mind subjectiveness if it is based on something I can grasp and understand. In the end the result maybe will be some kind of modules we recommend and recommendation to the developers for what we like in modules.
This is just my humble opinions (once more
) and I can of course be persuaded to think otherwise.
regards/falke