On Tue, Dec 30, 2008 at 6:13 PM, Vincent Massol
<vincent(a)massol.net>
wrote:
Hi devs,
This is not a priority (we need to finish our first stable release of
the WYSIWYG editor first) but I wanted to propose 2 things and
start a
discussion on it:
* That we make our new GWT WYSIWYG editor a top level project (i.e.
with a separate jira, separate wiki like
http://wysiwyg.xwiki.org
with
a better name, etc)
* Make it usable by someone who is not using XWiki
The rationale is:
* If we want our editor to become strong and compete with the likes
of
FCKEditor/TinyMCE we need to open it up to others and for that we
need
to:
- advertise it (hence the
http://wysiwyg.xwiki.org that would lists
all features same as
http://www.fckeditor.net/)
- make it be usable easily and thus without dragging xwiki
dependencies
+1
Other options:
1) Don't do anything. Cons: we won't get enough help and it'll be
hard
to compete with other editors. They'll have more features/less bugs
and we'll have a hard time keeping up. In addition it's possible
someone else creates a new GWT WYSIWYG editor and it would be better
if we could all join force on that and using what we have started
2) Externalize it on some forge other than the xwiki forge. This is
nice from a marketing point of view (i.e. easier to show it as a pure
wysiwyg editor) but it has some drawbacks:
- further from the xwiki community and thus harder for us to maintain
it there
- doesn't strengthen our xwiki project
2) would be great and I guess it would be a natural long-term
evolution if the
wysiwyg.xwiki.org project succeed in gathering a
strong community.
Maybe but not sure. The point is to host it on our forge since we have
a forge... Why would we want to host somewhere else where we have a
less good quality of service, where we don't control the tools, etc? :)
Unless we join a community related to WYSIWYG or GWT and not a forge
(SourceForge vs Apache Software Foundation for ex).
Thanks
-Vincent