Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [wtp-incubator-dev] Move Vex to Mylyn Docs

Good to see you can make progress now, now that Indigo is out. (And you are wise to hurry, before Juno cranks up :)

You may want to get Wayne's advice on namespace. I'm assuming Vex will be its own project? If so, it may deserve its own namespace in the third position, that is, org.eclipse.vex..... The reason naming is done this way, is that if a project moves from one project to another, there's no reason so change package names (Vex serving as a good example of where that would have been handy) ... though we in WTP do not set a good example ... but, that's the idea, I believe.

Also, as the transfer happens, be sure to be explicit about which committers are transferring _out_ of WTP Incubator. Of the 4 you name, I know David Carver would not, but off the top of my head believe the other 3 should be removed from WTP Incubator committer lists (Vex being the only thing they work on?). Additionally, if I recall correctly, I think Ed Burnette was brought in with Vex, but since he's not been able to participate, probably good time to remove him from the committer lists also.

Thanks ... and good luck!

From:        Florian Thienel <florian@xxxxxxxxxxx>
To:        WTP Incubator Dev list <wtp-incubator-dev@xxxxxxxxxxx>, mylyn-docs-dev@xxxxxxxxxxx
Cc:        Wayne Beaton <wayne@xxxxxxxxxxx>
Date:        06/27/2011 03:00 AM
Subject:        [wtp-incubator-dev] Move Vex to Mylyn Docs
Sent by:        wtp-incubator-dev-bounces@xxxxxxxxxxx

Hi WTP Incubator and Mylyn Docs developers,

Some month ago there was a proposal to move Vex out of the WTP incubator
into the Mylyn Docs project:

The Visual Editor for XML (Vex) is an WYSIWYM(ean) editor for XML
documents, i.e. text documents plus some semantics. Because the main
purpose of Vex is not to edit configuration files or deployment
descriptors etc. or not to edit web pages (although you could use XHTML
as your underlying schema) but to edit documentation, e.g. DITA and
DocBook files. So we thought Vex would much better fit into the Mylyn
Docs project than in the Web Tools Platform.

You can find more information about Vex in the wiki:

Since all the restructuring and the Indigo release is done, we would
start the move with a little introduction of the project and the
committers. There are currently four:
- David Carver
- Igor Campista
- Holger Voormann
- and me Florian Thienel
which are working only in their free time (unfortunately, no company
involved yet). Vex is still in incubation and we are still working on
some of the basic features.

So far so good: we suggest to move Vex from o.e.wst.xml.vex(.*) to
o.e.mylyn.vex(.*). The code should go from
to, but there
needs also some restructuring done to match the directory structure of

What do you think?

Best Regards,

wtp-incubator-dev mailing list

Back to the top