Considerations for roadmap for X2? Lets Discuss

We have had a bunch of ideas in the 2.6 Branch Thread but I think it is time to start discussing what MAIN focus we want to see for the next versions. How far do we want to take X2 before we have gone far enough and want to get more serious about a true X3. We have failed twice now to come up with a true upgrade path and should start considering the direction we want to go. (Failures were Xoops Sphere and Xoops Engine).

From what I understand currently we have plans for the next two versions at this point in time.

2.5.2 - Bug fix release - Bugs are being worked on as we read this and should hopefully be done soon. They are working hard to make sure as many bugs as possible are squashed. The latest version should be available via SVN but is a work in progress.

2.5.3 - Maintenance/Update release (Might be jumping the gun here.) This version will bring updates to many of the "features" in xoops. Getting rid of any of the depreciated code that may still exist and updating "modules" or "systems" that are used to make Xoops make its magic such as Smarty to 3.x or phpmailer etc. I would also assume this release would squash any bugs that were missed in 2.5.2 if any were found.

After this currently the map is open as far as I know. So we should consider where we want to go from here. A wishlist for 2.6 is being compiled from the thread for things looking to add in 2.6 and hopefully something will be brought up soon about this. (In other words make sure to make your suggestions if you have something different than what has already been suggested in that thread.)

Re: Considerations for roadmap for X2? Lets Discuss

While there have been many good ideas made to add to the X2 Branch some will take major rewriting of the core and others may be better served in the next step. I believe if we are going to plan out a road map we should set goals for the different branch steps. Due to the fact we are trying to update such outdated code I believe we are better served with rapid changes in branch steps with major additions added to each step.

With this in mind I propose something along these lines...

2.6 - Major overhaul of core functions to bring them up to date and to prepare for future updates to the core. We should make some major structural changes to the core in preparation to make the core lighter and more flexible. By this, I think we build an object library system for core and add on libraries. They make use of the autoload feature of PHP5. With the advent of Libraries we then Depreciate the use of frameworks. This is when we add "Plug in" support to the core. Plug ins would be lightweight applications that don't have a user side to them but can be used by admins or are a universal add on that modules can make use of. We would also make changes to the core to support Multi Site and Multi database (PDO). If there is an easy way to make the core better SEO then we do this here as well as clean up the "URL" if possible. We also look at incorporating some sort of CSS/HTML5 framework into the core as well to make templating and theming easier across the board and pull all of the hard coded CSS styles out of the core. Because of the complexity of the changes I think we stop there.

2.7 - This is where we start adding alot of the "features" mentioned in the 2.6 Branch thread. By this time a vast majority of things will have been changed and need to be updated. I think this is also where we start converting some of the core applications to plugins and get them out of the core code. I also think we can start pulling some of the core objects out of the core and place them in the library as well. This branch should focus on making Modules easier and help make the interface the same across the board.


Who's Online

137 user(s) are online (104 user(s) are browsing Support Forums)

Members: 0

Guests: 137



Goal: $100.00
Due Date: May 31
Gross Amount: $0.00
Net Balance: $0.00
Left to go: $100.00
Make donations with PayPal!

Latest GitHub Commits