[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[wtp-pmc] Vex Editor for Mylyn Docs project

Thanks Dave,

I think in general the steps are 1) get WTP's PMC approval for you to formally propose the move. I'll put it on the agenda for an upcoming PMC meeting. I think we could go with what you have said in the attached notes. (that is, we can take that as your request to the wtp-pmc, instead of you preparing a separate note, so I have taken the liberty of CC'ing wtp-pmc).  I don't anticipate any issues or questions ... but, need to discuss with PMC.   I think your attached notes logically maps out the reasons and anticipated benefits and there are no components, adopters, or groups in WTP that this move would effect directly (Let me know if I've missed anything).   Though of course we'd be sad to see you go.

If or when approved by WTP PMC, then 2) you'd prepare the move review materials for community review and comment. And that's where Wayne should be more involved, with timing, scheduling, etc. (IMHO, instead of having 3 reviews in the next nine months, you could probably just have two: combine your graduation review and move review into one review, if you are ready to graduate soon, or have the move review soon and then combine the graduation review with your release review next June ... but,  not sure what your thinking or timing is there ... and not sure it matters too much.)

I'll let you know after our PMC meeting if there are questions or conclusions.

PMC members, here is a link to Mylyn's (Application Lifecycle Tools) Charter for your convenience:  http://wiki.eclipse.org/Mylyn/Charter

Thanks again,

From:        David Carver <d_a_carver@xxxxxxxxx>
To:        Mik Kersten <mik@xxxxxxxxxxx>
Cc:        Wayne Beaton <wayne@xxxxxxxxxxx>, Mylyn developer discussions <mylyn-dev@xxxxxxxxxxx>, Florian Thienel <florian@xxxxxxxxxxxxxxxxxxx>, Igor Jacy Lino Campista <icampista@xxxxxx>, Holger Voormann <eclipse@xxxxxxxxxxx>, David M Williams/Raleigh/IBM@IBMUS
Date:        10/14/2010 02:38 PM
Subject:        Re: [mylyn-dev] Vex Editor for Mylyn Docs project

Added David Williams to the list as well.    David just to bring you up to speed, with the formation of the new Mylyn Documentation project, the existing wtp Vex committers have agreed that the best place for Vex long term is the new project.   This has to do with making sure we are targeting the plugin and development to the audience that will be using it most.  Mainly those having to maintain documentation and generate it into multiple formats.  The Documentation projects goals and Vex's scope line up nicely for this.

Wayne let me know what we need to do since, Vex is an Incubator component in the WTP Incubator to get the move review scheduled.


On 10/14/2010 10:25 AM, Mik Kersten wrote:

Hi Wayne,
On the Mylyn call today there was unanimous support for moving Vex to the Mylyn/Docs project.  David Carver will reach out to you about next steps on discussing a move review.
Dr. Mik Kersten
Tasktop CEO, Mylyn Lead, http://twitter.com/mik_kersten
From: David Carver [mailto:d_a_carver@xxxxxxxxx]
October-13-10 7:08 AM
Mylyn developer discussions
Mik Kersten; Florian Thienel; Igor Jacy Lino Campista; Holger Voormann
Re: [mylyn-dev] Vex Editor for Mylyn Docs project

I'll be on Thursday's call.

As for some screen shots see:


As well, I've attached a screen shot showing Vex with a DocBook document in the Vex Document perspective.


On 10/12/2010 08:55 PM, Mik Kersten wrote:

Could we add this to this Thursday's meeting agenda and have some of the
Vex folks join?
Also, could someone post links to some recent Vex screenshots?
Dr. Mik Kersten
Tasktop CEO, Mylyn Lead, http://twitter.com/mik_kersten
-----Original Message-----
From: mylyn-dev-bounces@xxxxxxxxxxx [mailto:mylyn-dev-
bounces@xxxxxxxxxxx] On Behalf Of David Carver
Sent: October-08-10 9:25 AM
To: mylyn-dev@xxxxxxxxxxx
Cc: Igor Jacy Lino Campista; Florian Thienel; Holger Voormann
Subject: [mylyn-dev] Vex Editor for Mylyn Docs project
  I've talked briefly about this with a couple of Vex committers.  And
Mik suggested I bring this up on the mylyn-dev mailing list as well.
I've copied the existing Vex committers on this message as well.   The
Vex project is a Visual Editor for XML documents.  In particularl
document oriented XML files like DocBook, XHTML, DITA, etc.   It can be
used to allow a WYSIWYG editing experience with out having to know the
underlying tags.   DocBook is one of it's main uses, and it also support
DITA out of the box as well.  It uses CSS stylesheets to help control
the rendering.    It fits in the same category as Mylyn WikiText editor,
as it allows for a Single Sourcing method to documentation.  The
files produced are strictly XML, and can be checked into a source code
system, allowing multiple people to collaborate on the files.
Vex has been a WTP Incubator project for several years, and slowly has
grown a dedicated committer base.   The project is shooting for a Spring
graduation, but with the advent of the new Mylyn top level project, and
overal scope of Vex, I would suggest that the Documentation sub
project might actually be a better place for the Vex project itself.
It seems to fit more into the scope there, as we Web Tools while it
the XML projects, Vex itself is more about enabling the collaboration
generation of documentation, and the people that are typically
interested in
Vex are those working on documentation or articles for publication (i.e.
articles, books, etc).
Here are some relevant links:
The CI Build and FindBugs reports can be found on hudson:
There is a P2 update site that can be used to install the latest
versions as well,
archived from the vex CI build.
mylyn-dev mailing list
mylyn-dev mailing list