Quote:
please please be patient.
everyone knows lack of our project.
skalpa is on the way to push XOOPS at a higher level.
he needs some quite area, to make our next version, more documented, more stable. Of course we want to share, but from now time is on work table, to make sharing possible.
he has worked these last weeks very hard, believe me.
I let him benefits to announce by himself what has been made and how things will go, he will do that in next few days.
thanks for your comments. you're right, but XOOPS needs to be pushed at a higher level, we need to communicate better, but this can be done only on a good core basis.
Of course, we can be patient. But if you mean by a "good core basis" a good source code, I'm not sure what you mean. You can communicate regardless of how good is your core. The communication issues won't go away, even the Skalpa comes with a major breakthrough in the code area.
It seems to me that it would be beneficial to reevaluate the current community processes. I would recommend to look at the more established and successful OpenSource project to find out what works and what doesn't, and what from the best practices could be applied to XOOPS community.
If Skalpa is working on the code, it doesn't prevent other people to publish the structure of the teams, to show who is on which team, and what are they responsible for. With a more transparent structure, it will be easier to understand how XOOPS works, who to contact, etc.
I would also like to see that we stop with any critical comments which could be read as personal attacks. I can see that some of the people here are frustrated, but if we care about this project, let's be civilized and professional. Let's raise issues (sometimes again and again), but let's not attack each other.
The Core Team is doing a great job overall, but as with every project, there are areas for improvement, and opportunity for them to learn on how to manage "Open Source projects", and not only code releases. This includes communication, processes for better community involvement, etc. Yes, it might require extra work in a unfamiliar teritory for some of them, but that's also part of growing - you either are willing to do it yourself, or you engage people who can do do it for you. If communication is a problem, get somebody who is good in communication. After all, we all want XOOPS to succeed, and the day has only 24 hour