Quote:
I can see a big issue in 2.6.0 way of development.
In the previous versions we missed even one core content module but Now there is three content modules: page, publisher and news.
You've jumped to conclusions too fast!
But I very much appreciate your feedback and keeping eye on the development, as it helps us to make sure that we don't miss anything.
Quote:
Having a simple content module like "page" and an advance one like "publisher" is more than enough for the next version of a CMS that didnt have any in the prev versions.
There are no decisions right now on "content" modules. Trabis just asked to add more modules from the "Basic Modules Pack" (BMP) to the core, so we can test them and make sure that whatever changes we make to the Core, we can see the impact on the "module conversion" to XOOPS 2.6.0 architecture. Ultimately, we would like to have all modules from the "Basic Module Pack" to run on XOOPS 2.6.0.
So what I am doing right now is to test/modify all the modules from "Basic Module Pack" so we can move all of them to "Final" status on XOOPS 2.5.5.
Once this is done, we'll be copying them to the Trunk on XOOPS 2.6.0 SVN, so the Core Team can test/modify them (or modify the Core as needed) so all the modules run on XOOPS 2.6.0. As we all know, many modules have been developed by different people in different years for different XOOPS versions, using different ways to provide similar functionality. So we need to test many modules to make sure that everything works as it should be and we don't miss anything.
As a result of all the testing we'll have a clearly defined and tested "conversion guidelines" for all XOOPS modules.
As a second stage, I hope, we'll be able to start consolidating some of the modules (like News, Article, Publisher, AMS, etc.), and refactor all modules so they are using "standard plugins" (like rating or search). This will simplify their "maintenance" in the future, and will speed up development of new modules.
While this means a lot of work, it will create a solid foundation for all future modules, and will ensure a clear migration path for the most important existing modules from XOOPS 2.5.5 to XOOPS 2.6.0.
Quote:
Now there are more than twenty modules in 2.6.0
Do you really want to support 20 core modules in 2.6.0 final version?
Some of the modules/extensions is just a functionality extracted from the Core, so it should be still supported by the Core Team.
Ultimately, I believe that XOOPS will need to define the "Basic Module Pack", and support it as a collaboration between the Core Team and the Modules Team. And we'll need more help with it, so anybody who can help us, please join the Core Team or Modules Team.
I hope, this will make more sense now for you.
