Skip to main content

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

Wayne, my initial understanding of this, was this was a move of the Vex component from the WTP Incubator, to being under a component under the Mylyn Docs project.   We started a propsoal at one time, and then you said one wasn't needed just a move.


On 06/27/2011 02:08 PM, Wayne Beaton wrote:
As I look harder at this, I don't think a restructuring review is sufficient. We really are creating a new project, not chopping up an existing one (if we were splitting the incubator into two siblings, then a restructuring would make sense). We'll need to have a well-defined scope and all the things that come with being a project.

In the meantime, you can (with the permission of the project leadership, of course) split out the Vex code into its own Git repository within the WTP incubator. When the review is complete and the new project is provisioned, we can move that Git repository.

Does this make sense?

Can I recommend that we move this discussion to Bug 328390? The thought of joining yet another mailing list...


On 06/27/2011 01:39 PM, David Carver wrote:
Wayne, to help this out, we can move just the Vex code after it has been renamed, into it's own Git repository and out of the WTP Incubator.  This way it'll only contain the pieces that are necessary for the Vex project itself.


On 06/27/2011 11:00 AM, David M Williams wrote:
Posting on Wayne's behalf, as requested.

----- Forwarded by David M Williams/Raleigh/IBM on 06/27/2011 10:58 AM -----

From:         Wayne Beaton <wayne@xxxxxxxxxxx>
To:         David M Williams/Raleigh/IBM@IBMUS
Cc:         florian@xxxxxxxxxxx
Date:         06/27/2011 10:48 AM
Subject:         Re: [wtp-incubator-dev] 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.

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


Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton

Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton
wtp-incubator-dev mailing list

Wayne Beaton
The Eclipse Foundation
Twitter: @waynebeaton

Back to the top