Re: [xwiki-devs] [xwiki-users] [Proposal] XWiki Enterprise 2.0 Roadmap
Hi Richard, On Jun 16, 2009, at 9:31 AM, goldring, richard wrote:
Hi,
Maybe not in the next build, but:
* more wysiwyg page layout tools (instead of hand coding css) would be good to enable users to rapidly and quickly knock up good looking pages,
I think this could be solved with the new 2.0 macros we're planning to add: - http://jira.xwiki.org/jira/browse/XWIKI-2965 - http://jira.xwiki.org/jira/browse/XWIKI-2963 - http://jira.xwiki.org/jira/browse/XWIKI-2966 - http://jira.xwiki.org/jira/browse/XWIKI-1689 WDYT?
* also better table creating/editing (resizing, etc) and formatting (grid lines hidden/shown) would also be good.
ok
* facility to email in content (text, images, rich text, word/open docs, etc) to automatically create wiki pages would be good (think can do in Confluence?)
Yes that would be handy. Actually I thought that we had done this at some point but maybe it was only done on some specific instance and not in the core.
* some sort of automated work flow facility
This would need to be discussed more since this is too generic and the needs might be various. Right now there are 2 solutions for simple workflows: - use spaces with permissions and some velocity to move pages from one space to another - add a Status object to pages and use HQL (or XWQL) to perform queries based on the status
* some sort of dashboard/home page mashups for users to provide user customised access to wiki content
You mean ability to insert widgets? Meaning that it's the user that chooses the widgets he'd like to see. Something like http://incubator.myxwiki.org/xwiki/bin/view/Gadgets/WebHome maybe? Now you mention "wiki content". Do you have ideas about content widgets you'd like to see? Thanks -Vincent
Regards,
Richard
-----Original Message----- From: [email protected] [mailto:[email protected]]On Behalf Of Guillaume Lerouge Sent: 15 June 2009 16:45 To: XWiki Users; XWiki Developers Subject: [xwiki-users] [Proposal] XWiki Enterprise 2.0 Roadmap
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 - WYSIWYG editor (Marius, Anca) - Fix bugs - Implement search in the link insertion dialog box - Improve the macro insertion dialog box - CAPTCHA integration (Jérôme) - Clustering (Thomas) - Write a clustering component based on XWiki events - Activity Stream integration (JV) - 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?) - Rewrite XWiki's Lucene Search backend (Sergiu?) - Improve XWiki's default skin (Laurent?)
*Tasks that will have to be postponed to the next release cycle:*
- Application Manager - Document Type Manager - Invitation Manager
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
Thanks in advance for your feedback.
Guillaume, on behalf of the XWiki Development Team
On Jun 16, 2009, at 10:15 AM, Vincent Massol wrote:
Hi Richard,
On Jun 16, 2009, at 9:31 AM, goldring, richard wrote:
Hi,
Maybe not in the next build, but:
* more wysiwyg page layout tools (instead of hand coding css) would be good to enable users to rapidly and quickly knock up good looking pages,
I think this could be solved with the new 2.0 macros we're planning to add: - http://jira.xwiki.org/jira/browse/XWIKI-2965 - http://jira.xwiki.org/jira/browse/XWIKI-2963 - http://jira.xwiki.org/jira/browse/XWIKI-2966 - http://jira.xwiki.org/jira/browse/XWIKI-1689
WDYT?
* also better table creating/editing (resizing, etc) and formatting (grid lines hidden/shown) would also be good.
ok
* facility to email in content (text, images, rich text, word/open docs, etc) to automatically create wiki pages would be good (think can do in Confluence?)
Yes that would be handy. Actually I thought that we had done this at some point but maybe it was only done on some specific instance and not in the core.
* some sort of automated work flow facility
This would need to be discussed more since this is too generic and the needs might be various. Right now there are 2 solutions for simple workflows: - use spaces with permissions and some velocity to move pages from one space to another - add a Status object to pages and use HQL (or XWQL) to perform queries based on the status
* some sort of dashboard/home page mashups for users to provide user customised access to wiki content
You mean ability to insert widgets? Meaning that it's the user that chooses the widgets he'd like to see.
Something like http://incubator.myxwiki.org/xwiki/bin/view/Gadgets/WebHome maybe?
Now you mention "wiki content". Do you have ideas about content widgets you'd like to see?
Also we already have a displayPanel macro that could be used: http://code.xwiki.org/xwiki/bin/view/Macros/DisplayPanelLayoutMacro Thanks -Vincent
Thanks -Vincent
Regards,
Richard
-----Original Message----- From: [email protected] [mailto:[email protected]]On Behalf Of Guillaume Lerouge Sent: 15 June 2009 16:45 To: XWiki Users; XWiki Developers Subject: [xwiki-users] [Proposal] XWiki Enterprise 2.0 Roadmap
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 - WYSIWYG editor (Marius, Anca) - Fix bugs - Implement search in the link insertion dialog box - Improve the macro insertion dialog box - CAPTCHA integration (Jérôme) - Clustering (Thomas) - Write a clustering component based on XWiki events - Activity Stream integration (JV) - 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?) - Rewrite XWiki's Lucene Search backend (Sergiu?) - Improve XWiki's default skin (Laurent?)
*Tasks that will have to be postponed to the next release cycle:*
- Application Manager - Document Type Manager - Invitation Manager
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
Thanks in advance for your feedback.
Guillaume, on behalf of the XWiki Development Team
Forwarding the email I received from Len Wanger (Len, I hope you don't mind by the way) since I think he missed the reply-to-all button ;-) See my questions below: -----------8<----------- Thanks for soliciting feedback. I don’t understand most of the tasks listed well enough to comment. There are a handful of things that I think would be very helpful: - Improve WYSIWYG editor speed. I am running into speed problems in the WYSISYG editor. When I type there is often 10-15 seconds of lag between when I type a key and when it shows up on the screen. This makes it very difficult to edit large sections of text. -> Which browser are you using? We'd be glad to try fixing those speed issues but we need to know more about your environment first. - Internet Explorer 8 testing. - Documentation – update and beef up the documentation (all 3 sections - user, admin, and developer.) some items that would be very useful to integrate in although may be post-2.0: - Add a tree for picking documents in import and export. For instance it would be very helpful to be able to specify to import an individual space. There may be an add-in for this, but it would be useful to have in the main build. -> That would be a part of the Application Manager I think. - A skin for mobile usage. With the proliferation of small-screen devices (MIDs, iPhones, Android phones, etc.), it would be useful to have a format to view XWiki content on these devices (CSS entry?). -> We started working on an iPhone skin but it's not ready for production yet. That's an area where I'd be glad to see community members come up with prototypes as it's obviously going to be an area where a lot of innovation can be expected in the coming years. Plus we always want to clean and integrate existing patches, so it will push us towards that goal ;-) - Long-term I think it would be interesting to add work flow functionality to XWiki. The ability to define rules-based workflow and notify users of items requiring their attention would be very interesting. -> See Vincent's answer to Richard remark about workflow earlier in the thread. The good news is that I’m a very happy XWiki user. The system has been very stable for me and I’m very happy with the continued development on the project. The new WYSIWYG editor, new WIKI syntax, and WebDAV have been great additions! -> Great news, thanks for the feedback :-) Regards, Len Wanger ----------->8----------------- Guillaume On Tue, Jun 16, 2009 at 10:57 AM, Vincent Massol <[email protected]> wrote:
On Jun 16, 2009, at 10:15 AM, Vincent Massol wrote:
Hi Richard,
On Jun 16, 2009, at 9:31 AM, goldring, richard wrote:
Hi,
Maybe not in the next build, but:
* more wysiwyg page layout tools (instead of hand coding css) would be good to enable users to rapidly and quickly knock up good looking pages,
I think this could be solved with the new 2.0 macros we're planning to add: - http://jira.xwiki.org/jira/browse/XWIKI-2965 - http://jira.xwiki.org/jira/browse/XWIKI-2963 - http://jira.xwiki.org/jira/browse/XWIKI-2966 - http://jira.xwiki.org/jira/browse/XWIKI-1689
WDYT?
* also better table creating/editing (resizing, etc) and formatting (grid lines hidden/shown) would also be good.
ok
* facility to email in content (text, images, rich text, word/open docs, etc) to automatically create wiki pages would be good (think can do in Confluence?)
Yes that would be handy. Actually I thought that we had done this at some point but maybe it was only done on some specific instance and not in the core.
* some sort of automated work flow facility
This would need to be discussed more since this is too generic and the needs might be various. Right now there are 2 solutions for simple workflows: - use spaces with permissions and some velocity to move pages from one space to another - add a Status object to pages and use HQL (or XWQL) to perform queries based on the status
* some sort of dashboard/home page mashups for users to provide user customised access to wiki content
You mean ability to insert widgets? Meaning that it's the user that chooses the widgets he'd like to see.
Something like http://incubator.myxwiki.org/xwiki/bin/view/Gadgets/WebHome maybe?
Now you mention "wiki content". Do you have ideas about content widgets you'd like to see?
Also we already have a displayPanel macro that could be used: http://code.xwiki.org/xwiki/bin/view/Macros/DisplayPanelLayoutMacro
Thanks -Vincent
Thanks -Vincent
Regards,
Richard
-----Original Message----- From: [email protected] [mailto:[email protected]]On Behalf Of Guillaume Lerouge Sent: 15 June 2009 16:45 To: XWiki Users; XWiki Developers Subject: [xwiki-users] [Proposal] XWiki Enterprise 2.0 Roadmap
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 - WYSIWYG editor (Marius, Anca) - Fix bugs - Implement search in the link insertion dialog box - Improve the macro insertion dialog box - CAPTCHA integration (Jérôme) - Clustering (Thomas) - Write a clustering component based on XWiki events - Activity Stream integration (JV) - 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?) - Rewrite XWiki's Lucene Search backend (Sergiu?) - Improve XWiki's default skin (Laurent?)
*Tasks that will have to be postponed to the next release cycle:*
- Application Manager - Document Type Manager - Invitation Manager
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
Thanks in advance for your feedback.
Guillaume, on behalf of the XWiki Development Team
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
-- Guillaume Lerouge Product Manager - XWiki Skype: wikibc Twitter: glerouge http://guillaumelerouge.com/
Hi XWikiers, thanks for the feedback :-) Here's the updated tasklist (I've probably added too much stuff, we might need to remove some parts in the course of the roadmap): *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 - Documentation - If possible: i18n - If possible: externalize the rendering module - WYSIWYG editor (Marius, Anca) - Fix bugs - Implement search in the link insertion dialog box - Improve the macro insertion dialog box - - i18n - Documentation (User/Admin/Dev Guide) - Implement categories/libraries for Macros - I'm not sure we want to make the WYSIWYG work in Safari & Opera by ourselves. Based on customer & user feedback we might need to focus on making it work in IE8 first. - If possible: externalize the WYSIWYG editor -> that would make it easier for people from outside the XWiki community to add support for Safari, Chrome & Opera - CAPTCHA integration (Jérôme) - Clustering (Thomas) - Write a clustering component based on XWiki events - Overhaul of the notifications system in XWiki (JV) - Activity Stream integration - 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 - Improve XWiki's default skin (Laurent) - If possible: make sure the skin works fine in IE8 - Architectural Improvements (Vincent) - Migrate all XWiki Enterprise pages to use the XWiki 2.0 syntax (Collective effort) *Tasks with nobody planned to work on as of today:* - Rewrite XWiki's Lucene Search backend (Sergiu?) *Tasks that will have to be postponed to the next release cycle:* - Application Manager - Document Type Manager - Invitation Manager *Ideas to keep in mind for later:* - Mobile skin - Embedded SMTP server to handle email-to-wiki-page conversions / imports - Some kind of workflow thing -> actually as Vincent pointed it out above I'm not sure we'll ever build a full-fledged workflow application in XWiki but there are 2 things that can be done: - Integrate XWiki with an external workflow engine such as Bonita - Make it possible to define a set of global rules for queries at the wiki level (something similar to what we're going to do to support hidden docs, having 2 APIs depending on whether we want to display technical documents or not) but more discussion is needed on that topic and to be honest I don't fully grasp it yet :-) 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 Keep the feedback coming ;-) Guillaume -- Guillaume Lerouge Product Manager - XWiki Skype: wikibc Twitter: glerouge http://guillaumelerouge.com/
On Jun 16, 2009, at 12:33 PM, Guillaume Lerouge wrote:
Hi XWikiers,
thanks for the feedback :-)
Here's the updated tasklist (I've probably added too much stuff, we might need to remove some parts in the course of the roadmap):
*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 - Documentation
What do you have in mind re doc? (I've added quite a bunch already re rendering).
- If possible: i18n - If possible: externalize the rendering module
This is already well in progress (I've worked on this and I'll continue doing it slowly).
- WYSIWYG editor (Marius, Anca) - Fix bugs - Implement search in the link insertion dialog box - Improve the macro insertion dialog box - - i18n - Documentation (User/Admin/Dev Guide) - Implement categories/libraries for Macros
This is also in the rendering.
- I'm not sure we want to make the WYSIWYG work in Safari & Opera by ourselves. Based on customer & user feedback we might need to focus on making it work in IE8 first.
+1 for IE8 and postponing safari/opera to later or letting contributors do it if someone is interested. Thanks -Vincent
- If possible: externalize the WYSIWYG editor -> that would make it easier for people from outside the XWiki community to add support for Safari, Chrome & Opera - CAPTCHA integration (Jérôme) - Clustering (Thomas) - Write a clustering component based on XWiki events - Overhaul of the notifications system in XWiki (JV) - Activity Stream integration - 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 - Improve XWiki's default skin (Laurent) - If possible: make sure the skin works fine in IE8 - Architectural Improvements (Vincent) - Migrate all XWiki Enterprise pages to use the XWiki 2.0 syntax (Collective effort)
*Tasks with nobody planned to work on as of today:*
- Rewrite XWiki's Lucene Search backend (Sergiu?)
*Tasks that will have to be postponed to the next release cycle:*
- Application Manager - Document Type Manager - Invitation Manager
*Ideas to keep in mind for later:*
- Mobile skin - Embedded SMTP server to handle email-to-wiki-page conversions / imports - Some kind of workflow thing -> actually as Vincent pointed it out above I'm not sure we'll ever build a full-fledged workflow application in XWiki but there are 2 things that can be done: - Integrate XWiki with an external workflow engine such as Bonita - Make it possible to define a set of global rules for queries at the wiki level (something similar to what we're going to do to support hidden docs, having 2 APIs depending on whether we want to display technical documents or not) but more discussion is needed on that topic and to be honest I don't fully grasp it yet :-)
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
Keep the feedback coming ;-)
Guillaume
- I'm not sure we want to make the WYSIWYG work in Safari & Opera by ourselves. Based on customer & user feedback we might need to focus on making it work in IE8 first.
+1 for IE8 and postponing safari/opera to later or letting contributors do it if someone is interested.
-0. IE anything is becoming extinct, while Safari is rising. And it would be much easier to make it work in Safari than in IE, since it should be compatible with Firefox for the most parts. The same is true for Chrome and Opera. Still, I would really like to see contributors work on this. -- Sergiu Dumitriu http://purl.org/net/sergiu/
Guillaume Lerouge wrote:
Hi XWikiers,
thanks for the feedback :-)
Here's the updated tasklist (I've probably added too much stuff, we might need to remove some parts in the course of the roadmap):
*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 - Documentation - If possible: i18n - If possible: externalize the rendering module - WYSIWYG editor (Marius, Anca) - Fix bugs - Implement search in the link insertion dialog box - Improve the macro insertion dialog box - - i18n - Documentation (User/Admin/Dev Guide) - Implement categories/libraries for Macros - I'm not sure we want to make the WYSIWYG work in Safari & Opera by ourselves. Based on customer & user feedback we might need to focus on making it work in IE8 first.
Although I don't like it, I understand the need. I just hope they didn't changed too much at JS and CSS level from IE7 to IE8.
- If possible: externalize the WYSIWYG editor -> that would make it easier for people from outside the XWiki community to add support for Safari, Chrome & Opera
We can start by splitting the WYSIWYG in multiple reusable modules. Thanks, Marius
- CAPTCHA integration (Jérôme) - Clustering (Thomas) - Write a clustering component based on XWiki events - Overhaul of the notifications system in XWiki (JV) - Activity Stream integration - 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 - Improve XWiki's default skin (Laurent) - If possible: make sure the skin works fine in IE8 - Architectural Improvements (Vincent) - Migrate all XWiki Enterprise pages to use the XWiki 2.0 syntax (Collective effort)
*Tasks with nobody planned to work on as of today:*
- Rewrite XWiki's Lucene Search backend (Sergiu?)
*Tasks that will have to be postponed to the next release cycle:*
- Application Manager - Document Type Manager - Invitation Manager
*Ideas to keep in mind for later:*
- Mobile skin - Embedded SMTP server to handle email-to-wiki-page conversions / imports - Some kind of workflow thing -> actually as Vincent pointed it out above I'm not sure we'll ever build a full-fledged workflow application in XWiki but there are 2 things that can be done: - Integrate XWiki with an external workflow engine such as Bonita - Make it possible to define a set of global rules for queries at the wiki level (something similar to what we're going to do to support hidden docs, having 2 APIs depending on whether we want to display technical documents or not) but more discussion is needed on that topic and to be honest I don't fully grasp it yet :-)
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
Keep the feedback coming ;-)
Guillaume
Marius Dumitru Florea wrote:
- If possible: externalize the WYSIWYG editor -> that would make it easier for people from outside the XWiki community to add support for Safari, Chrome & Opera
We can start by splitting the WYSIWYG in multiple reusable modules.
Speaking of this, Cristina needed to use the serverside cleaner/converter packages for XOO, which is hard right now (unpack the war and copy the jar from WEB-INF/lib). Could you move those in a distinct jar? -- Sergiu Dumitriu http://purl.org/net/sergiu/
Sergiu Dumitriu wrote:
Marius Dumitru Florea wrote:
- If possible: externalize the WYSIWYG editor -> that would make it easier for people from outside the XWiki community to add support for Safari, Chrome & Opera
We can start by splitting the WYSIWYG in multiple reusable modules.
Speaking of this, Cristina needed to use the serverside cleaner/converter packages for XOO, which is hard right now (unpack the war and copy the jar from WEB-INF/lib). Could you move those in a distinct jar?
Yes.
participants (4)
-
Guillaume Lerouge -
Marius Dumitru Florea -
Sergiu Dumitriu -
Vincent Massol