Would it make sense to prioritize the roadmap?

BIG Roadmap:
* Resource installer — an internal installer for system updates, snippets, chunks, modules and plugins
* Module packager — helps devlopers package all their snippets, plugins, pages, chunks and snippets for distribution
* Export improvements — complete static site export with images and other linked files including any css or js files
* Web user roles — more granular role-based permissions for your custom we applications
* Manager improvements — skin your entire manager from editing just the CSS and image files
* Resource library — MODx-approved modules, plugins, templates and snippets.
* Sub-sites — manage multiple websites by creating "virtual" sub-sites within the manager
* TV2 & TVO — Object-Oriented TVs no longer linked to specific templates
* Improved Caching — near-static speed for fully cached pages and developer friendly caching flags where appropriate
* Recycle Bin — nothing’s gone until you really mean it, including users/groups, snippets, pages, or anything else in MODx
* Publishing workflow — restrict publishing by user roles with automatic notifications during each stage.
* Document versioning with rollbacks — wish you had a previous version of a page? Now you can.
* Front-end editing module — no need to go to the manager for simple site changes
* Improved Defaults — a more complete set of Manager and Web user roles, updated snippets, chunks and templates will be ship as standard

It is great to see all of these plan features but I think it would be helpful to have a prioritize roadmap.

For example:
3.4:
* Resource installer — an internal installer for system updates, snippets, chunks, modules and plugins
* Module packager — helps devlopers package all their snippets, plugins, pages, chunks and snippets for distribution
3.5
* Manager improvements — skin your entire manager from editing just the CSS and image files
* Resource library — MODx-approved modules, plugins, templates and snippets.
3.6
* Export improvements — complete static site export with images and other linked files including any css or js files
* Web user roles — more granular role-based permissions for your custom we applications
3.7
* Sub-sites — manage multiple websites by creating "virtual" sub-sites within the manager
* TV2 & TVO — Object-Oriented TVs no longer linked to specific templates
3.8
* Improved Caching — near-static speed for fully cached pages and developer friendly caching flags where appropriate
* Recycle Bin — nothing’s gone until you really mean it, including users/groups, snippets, pages, or anything else in MODx
3.9
* Publishing workflow — restrict publishing by user roles with automatic notifications during each stage.
* Document versioning with rollbacks — wish you had a previous version of a page? Now you can.
4.0
* Front-end editing module — no need to go to the manager for simple site changes
* Improved Defaults — a more complete set of Manager and Web user roles, updated snippets, chunks and templates will be ship as standard
1.0 release???
* Usabilities improvement for the mass???

What do you think?

Thanks

I just dug this post up, It deserves a *bump*

Losts of very nice ideas here ! From a marketing standpoint revisionning and workflow would most definitely be huge "pros" agains the competition. That’s from the end user point of view. Module packager and resource library would be nice to attract plugin/snippet/module writers...

As far as the question of prioritizing is concerned, I would say yes it makes sense to prioritize, yes.

Ehmmm... Is there any plan to look under the hood of my sub site shack. Maybe it can be integrated for future release? It’s not fully tested yet, but I’m using it for my production website. So far I haven’t have any problem, except for the <base href="" /> tag. If you set the page to cache, then if you open the page from the primary domain, instead of from the subsite domain, than the primary domain is the one that is going to be cached. I also didn’t set www handler, so www.domain.com and domain.com is different, I use htaccess to direct those, but it’s really going to be easy to modify the code to support mirroring www.

That’s the thread
http://modxcms.com/forums/index.php/topic,2059.0.html

I’m not to for sure what type of subsites feature that MODx aiming for, but so far this is what I think will be better fit to the people.

I’m accepting any suggestions or domments.

Regards,

Prioritization makes a lot of sense. Priority #1 is putting the int’l install issues to bed once and for all!

Quote from: rthrash at Jan 14, 2006, 03:04 PM

Prioritization makes a lot of sense. Priority #1 is putting the int’l install issues to bed once and for all!

About this last item, nobody answered the message about the setup.sql fix that I relayed from mvt91 (a french user, non-english speaking that sent me a PM) :
http://modxcms.com/forums/index.php/topic,2281.0.html

Does this help in any way ?

About the install : has Susan’s fix of MySQL error been added to 0.9.1 ?

David, both of those in one form or another should make it into 0.9.2.

Okay Ryan, cool news