26 Jun
2009
26 Jun
'09
4:23 p.m.
Vincent Massol wrote:
On Jun 15, 2009, at 5:44 PM, Guillaume Lerouge wrote:
I think we should also make sure all document syntax combinations work as
expected -- rendered, edited wiki, edited wysiwyg, used as default (xhtml/1.0
seems to be buggy, at least: cannot switch to it an empty document, generates
errors when using as default -- i'll report the discovered issues soon). Or at
least we should have a list of known issues.
Happy coding,
Anca
Hi XWiki Devs & Users,
here's the current proposal for the XWiki Enterprise 2.0 roadmap.
Please
give us your feedback about it and tell us whether you think we missed
anything important. Please note that this roadmap covers the next 3
months
of development work. Improvements not included here will be
discussed at the
beginning of the next roadmap (in September 2009).
Shout if you think we forgot something ;-)
The list of tasks is divided in 3 parts: tasks we have already
planned to
have people working on, tasks that we would like to complete during
the
course of the release but have nobody planning to work on yet and
tasks that
will have to be postponed until the next release cycle.
*Tasks with people already planned to work on:*
- Rendering (Thomas)
- Fix bugs
- Make sure the XWiki 2.0 syntax doesn't move any more once XE
2.0 is
out
I think we also need to have a XE XAR fully converted to 2.0 syntax.
Thomas could be in charge but he'll need help from others. I'll help
but if others can help that would be great. - WYSIWYG editor (Marius, Anca)
- Fix bugs
- Implement search in the link insertion dialog box
- Improve the macro insertion dialog box
Implement categories in Macros
What about externalizing the WYSIWYG editor so that:
1) it can be used outside of XWiki
2) we can get help developing it (for ex for Safari, Opera, Chrome,
etc support)
- CAPTCHA integration (Jérôme)
- Clustering (Thomas)
- Write a clustering component based on XWiki events
- Activity Stream integration (JV)
Note that I view this as overhaul of the notifications system in
XWiki. It would great to have a grand view of the whole domain and
what needs to be done, even if the only thing we implement in that
version is the rewrite of the watchlist using the Activity Stream.
- Watchlist (JV)
- Rewrite the watchlist feature based on the activity stream
- Make the watchlist work in XEM
- Macros (Asiri)
- Write the velocity macro bridge
- Write a number of velocity macros
- UI Improvements (Caty)
- Blog
- User Profile
- Architectural Improvements (Vincent)
*Tasks with nobody planned to work on as of today:*
- Migrate all XWiki Enterprise pages to use the XWiki 2.0 syntax
(Collective effort?)
Ah yes, see above.
- Rewrite XWiki's Lucene Search backend
(Sergiu?)
This is key. We really need someone to work on this.
- Improve XWiki's default skin (Laurent?)
Why is there a question mark? Didn't we get commitment from Laurent to
work on it?
*Tasks that will have to be postponed to the next
release cycle:*
- Application Manager
- Document Type Manager
- Invitation Manager
I agree it's best to focus on consolidating (fixing + improving)
existing feature rather than add new ones since we want a strong and
stable 2.0.
IMO the main focus of 2.0 remains the consolidation of the new
rendering/new wysiwyg so that Syntax 2.0 is the default and can be
used in all situations easily.
The current roadmap dates are the following:
- XE 2.0 M1: June 22
- XE 2.0 M2: July 13
- XE 2.0 M3: August 3
- XE 2.0 RC: August 17
- XE 2.0: August 31
+1
Thanks
-Vincent
Thanks in advance for your feedback.
Guillaume, on behalf of the XWiki Development Team
_______________________________________________
devs mailing list
devs(a)xwiki.org
http://lists.xwiki.org/mailman/listinfo/devs