2
We have a saying in Spanish (no idea if English)
"el que mucho abarca poco aprieta"
This stands for:
If you try o grab a big lot, probably you will squeeze very little.
NOTE: (this is the worst translation ever)
I have been working a lot trying to define the scope of our job. Specially because I am workin also in th smoketests.
I found two things.
We can work on the past (things already done)
We can work on the future (Recomendations for things to come)
No sense to evaluate modules that at glance, would not pass our very nice standards.
None have a good readme, non are easy to use (like the system itsef), none are good enough to meet our dreams of what a module should be.
I think our group shoul concentrate on future issues, learning from the past but not trying to correct or even evaluate. (That is left to other teams).
We need to set up our goal in somthing like "The XOOPS User Standard Interfase". That is an Ideal standard but we have to set some core rules (like jens readmes sugestions).
We can present the interfases as "examples" to the cores team and look for their feedback. Alsa we can present the excel spreadsheets as "examples" of our concerns.
If the core team consider that our effort goes in a good direction, then we can "make a full fetured effort".
I saw something about great Ideas for version 3. We shoul point to have the XOOPS standard interfece gidelines working poiinting there.
I aggree with all the points that Daddytsu is considering. Count on me. Just want to make sure we are pointing on the same direction.
What do you think?