Good to see you can make progress now,
now that Indigo is out. (And you are wise to hurry, before Juno cranks
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!
Florian Thienel <florian@xxxxxxxxxxx>
WTP Incubator Dev list
Wayne Beaton <wayne@xxxxxxxxxxx>
06/27/2011 03:00 AM
Move Vex to Mylyn Docs
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.