----- Forwarded by David
M Williams/Raleigh/IBM on 06/27/2011 10:58 AM -----
Wayne Beaton <wayne@xxxxxxxxxxx>
David M Williams/Raleigh/IBM@IBMUS
06/27/2011 10:48 AM
Move Vex to Mylyn Docs
Hi David, and Florian.
I'm not subscribed to the two mailing lists. Can you post this on my behalf?
On 06/27/2011 10:41 AM, Wayne Beaton wrote:
I would prefer (and strongly recommend) to stick with
the "flat" namespace (org.eclipse.vex) as David suggests.
>From a process POV, we need to schedule a restructuring review. Before
that can happen, we'll need to have IP Log approval for the code that needs
to move; please submit that at your earliest convenience and we can go
about scheduling the review.
Note that we'll need a very concise document that describes what needs
to move from where to where to make this work. FWIW, I have used a
bug comment for this purpose in the past.
On 06/27/2011 09:42 AM, David M Williams wrote:
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.
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.