Good to see things are back on track... and under concern.

Quote:

+1

Same here, and reported. They are currently checking this problem (phew, I'm not the only one ).

oooooh

I would like to propose my candidature as "module development member".

I think I can say I'm a module developper, while I'm not basically a real coder. As part of an independant module development team (along with Blueteen and DuGris), I think I can bring some experience in this area.

Quote:

Quote:

Do you really think that our decision has been taken lightly? As stated in the article, it's now more than 1 full year we are waiting for something... unfortunatly uselessly.

Do you really think that each and every members of the frxoops.com team hasn't made his best to make changes, to contribute or to help with the core development?

We came to the conclusion that we couldn't trust the core development team anymore. We do think we have the responsability to guide our french speaking community (wherever they decide to follow us or not), and expose our points of views. Giving a head on Xoops-Cube sounds to us, actually, the best choice... if we want our project to simply survive.

The lack of publication about a new XOOPS version for month now is worrying some members of our french community, and the french speaking XOOPS Team has decided to share his thoughs about it.

Facts

At the beginning of the year 2006, Skalpa, a frenchie, has taken the leading of the XOOPS Core development, with our support.

Article :http://www.frxoops.org/modules/news/article.php?storyid=938

We have met him at spring 2006, in Auvergne (just in the middle of France), so we could have more lights on the roadmap he had published on january. The result of this meeting can be read in this article:http://www.frxoops.org/modules/news/article.php?storyid=962

Next to this, two new versions labeled 2.3.0a1 et 2.3.0a2 have been published on the svn (http://xoops.svn.sourceforge.net/viewvc/xoops/XoopsCore/releases/) along with two new 2.2.5 Release Candidate versions.

Since then, no more communications have been realised, and the questions which have been asked about this subject on the xoops.org website have got no official replies or have been censored.

Causes

We admit that in the person of Skalpa, we have certain competences and high qualities regarding the goals we have to reach, code purity to be used, along with security concerns. Although, regarding project mangement and communication, the deception was even greater, which is not without consequences about the current situation.

Of course, we have to admit the chalenge was not easy to face, as the final objective was to publish à 2.3.0 which could, starting from intermediate versions, ensure an ascending compatibility with existing versions, while the amount of developpers was to start "from scratch again" with php5 only, even with we had to create migration scripts.

En now?

We have to relativise things : a website may normally work with a 2.0.16 version, and our concern is more to be attentive about the futur and study possible solutions.

In our forums (french ones) some have proposed the possibility to realise à 2.0.17 fr version. The idea is interesting, but we don't have today enough competencies in numbers and qualities allowing to produce reliable code in object coding. Even more, walking on a 2.0.17 would be a short term view and woul not allow to take in account the most important evolutions.

We have been announced the release in a short term of a new version which would merge the 2.0.16 and 2.2.5 versions, but we don't see anything on the svn. As for the date, we have been told "very soon"!!! (not everyone has the same timing notion).

A japanese guy (Minahito) and some other xoops.org members have created XOOPS Cube for month now. We could summarize this solution defining XOOPS Cube has a web application base, allowing, through XOOPS Legacy, to emulate XOOPS (most of XOOPS modules would work with XoopsCube). It's ready for php6, uses design patterns(http://fr.wikipedia.org/wiki/Motif_de_conception) and has naming rules, along with an extension system preventing the core hacking.

Conclusion

While we are waiting for an hypothetical official version, we will in a few week, open our website a XOOPS Cube oriented place where we could let you know about our first analysis, propose support for this version. As we want to publish a french documentation, we are looking for english-french translators.

The French Speaking XOOPS Team (www.frxoops.org)
Original message can be found here

I'm still developping for Xoops. I even recently (along with Blueteen) started the development of new modules.

Although, we currently stoped our efforts...

Why? Because we are not sure all the efforts we are putting in a module development (which means hours and days of hard work) may find any core area in the end of the day.

To be honest with the community, I don't see the point with developping modules (except for my own needs) for a community and a project without any clear futur... and which lack of communication from its upper layer. We hear rumors from the forums, but no clear sights from the core development team.

Now, tell me why we, module developpers, should carry on with our respective project.

Don't get me wrong. I'm a gret fan, contributor and supporter of Xoops. I'm on this project almost since the beginning (as user first, as contributor later).

Prove me I'm not wrong.

:-/