Igor,
Help is always needed and welcomed. I would recommend first
subscribing the the wtp-incubator-dev mailing list, which I've cc'd on
this email. Next you can get the latest code by importing the Team
Project set file from the Continuous Integration build that runs on the
Hudson server:
https://build.eclipse.org/hudson/view/WTP/job/cbi-wtp-inc.vex/
You can also get the latest P2 zip repository from there as well. A
good place to start with contributions is to look at the existing open
bug list, and attach some patches. Good quality patches with JUnits
will really get some attention. For a list of open bugs follow the
link below:
https://bugs.eclipse.org/bugs/buglist.cgi?query_format=advanced;bug_status=UNCONFIRMED;bug_status=NEW;bug_status=ASSIGNED;bug_status=REOPENED;component=wtp.inc.vex;product=WTP%20Incubator;classification=WebTools
The DocBook side has been tested pretty well, but we definitely need
some skills and attention on the Dita side of things. In addition,
there are a couple of big items that still need to be worked out. We
need a good integrated Multipage Source editor. Having some good EMF
skills would definitely help us on that front to get an EMF2DOM adaptor
working correctly for Vex. We also still need good namespace support
as well as an interface into to use XSDs for the validators instead of
solely relying on DTDs. Vex also could use some love with displaying
images, which it currently does not do.
More information on How to Contribute can be found on the Vex wiki.
http://wiki.eclipse.org/Vex
I've copied Holger Voormann and Florian Thienel on this as well, the
two main committers to the project.
Dave
On 04/26/2010 03:42 PM, Igor Jacy Lino Campista wrote:
Hi David,
Is help needed ?
I have been an Eclipse & EMF evangelist since some 5 years. I have
done a lot of EMF modelling and also Eclipse plugins development.
I'm very very interested in the VEX project and I'm very happy to find
out today that it was contributed to the Eclipse Foundation. (found it
by accident)
My involvement with DITA is since 2.5 years ago (I went to the
EclipseCon 2008 and the Eclipse Europa Submit 2007) and have been
following ever since.
I successfully introduced DITA to my project and also have been an
evangelist
to the customer documentation team. (I work for Nokia Siemens Networks).
I'm looking to be a contributor and committer to the VEX project.
The truth is that I wanted to start such a project and as well
contribute it to Eclipse if it ends up successful and feature rich.
There is another open source editor DITA OP eclipse-based but with
license LGPL, and not as powerful or generic as VEX is. I wanted to
make a partnership with the author to improve it and eventually make
EPL and contribute it but he was not really interested and so I decided
to start from scratch. (See attached email)
Cheers,
Igor
-------- Original Message --------
Hi Igor,
> Besides the bugfixes, I basically want to change the architecture of OP to increase the capabilities and features. Tough cookie.
As I told you, the way to collaborate to an open-source project is
well known and you are welcome to submit patches :)
I am also well versed in model driven architecture, I also created a
model-driven Eclipse IDE for the previous company I was working for.
As you did, I saw the potential of using such a power tool for some
parts of the code. However it would have been much more work to put
such an infrastructure in place than to write the code for the first
release. Besides, for a model-driven infrastructure you need templates
and the first step is often to have a working implementation that you
can use as a base for your templates.
I am a practical guy, and right now revising the architecture doesn't
seem to help much about the main goals of the project (as I see them)
which are new features, adoption and assembling the community, but you
are free as to what kind of work you'd like to contribute to the
project :)
> I have seen that the license is GPL, this I think that can create acceptance problems, or in bigger perspective, if the project gets big enough, with such license I cannot be part of a high level project in Eclipse Foundation. Lets say, the documentation project. (which could be a good big goal to achieve)
> Would it be a posibility to use EPL (Eclipse Public License) ?
I won't change the license, not right now anyway. However the fact
that you are contributing to a GPL project won't hinder your ability
to contribute to an EPL project. Only Eclipse Foundation employees
have restrictions about contributing to or using GPL projects as part
of their Foundation work (which is stupid, if you want my opinion)
I thank you for your interest in the project and I look forward at you
future contributions.
Regards,
Claude
On 20.03.2010 14:39, Igor Jacy Lino Campista wrote:
Hi Claude,
Besides the bugfixes, I basically want to change the architecture of OP
to increase the capabilities and features. Tough cookie.
I have seen that the license is GPL, this I think that can create
acceptance problems, or in bigger perspective, if the project gets big
enough, with such license I cannot be part of a high level project in
Eclipse Foundation. Lets say, the documentation project. (which could
be a good big goal to achieve)
Would it be a posibility to use EPL (Eclipse Public License) ?
The first thing I would like to do is to make the project model-driven.
I checked the code and I think lots of work were done. (I assume it
took quite a bit of effort) I think we can reduce drastically the
amount of code that is manually created and also maintained. While at
the same time create infrastructure to easily create from scratch a new
version for DITA 1.3 and over.
As a reference, I attach some slides of one of my projects done some
years ago. It's eclipse-based Visual Editor test automation related.
It has been granted permission to be open source, but had not the time
to do it.
It has about 53000 lines of code, and was done by me with about 1 and
half months effort done during spare time (in a time-frame of 6 months).
-Igor
On 20.03.2010 13:00, Claude Vedovini wrote:
Hi Igor,
Sure you can contribute, this an open source project so it's rather
easy, you only need to checkout the code and then submit patches to the
ticketing system. I will then review and integrate them.
You can first have a look at the bug tracker here: https://sourceforge.net/tracker/?group_id=228491&atid=1074048
The most problematic issues being the problems with Galileo, plugin
dependencies and validation not working, I suspect the problem with
validation might be related to the plugin dependency as well.
What do you think?
Regards,
Claude
On 20 March 2010 11:06, Igor Jacy Lino
Campista <icampista@xxxxxx> wrote:
Hi Claude,
Actually I'm very interested in doing a big project in the few spare
time that I have, and I find very attractive to do open source DITA
tooling based on Eclipse.
I have many years of Eclipse development background and I think I can
work on some fancy ideas in DITA OP.
I'm more like a model-driven guy, and also like to do UI details.
What do you think could we get some to work together? (assuming both of
us have few time available)
Cheers,
Igor
On 03.03.2010 23:15, Claude Vedovini wrote:
Thanks for the info Igor I'll check that anytime soon.
About the Mylyn dependency, there is no direct dependency over Mylyn, I
guess this is inherited from some other plugin since Gallileo. I'll
check that as well :/
Thanks for the support,
Claude
--- In dita-users@xxxxxxxxxxxxxxx,
Igor
Jacy
Lino
Campista
<icampista@...> wrote:
>
> Hi Claude,
>
> Nice to see you around! ;-) (and eventually back :) )
> Just rechecking my observation, I just now downloaded an fresh
Eclipse
> Galileo SR2 and installed the nightly build.
>
> The DITA schema validation is not working (in the trunk/nightly
> version, M2 version is fine). For example if you add the tag
> <inexistentinDITA/> you won't get any error.
> Malformed XML is validated though. So <p2><p/> would
give you an error.
>
> One extra comment, is there a reason why Mylyn is a required
> prerequisite bundle? (I used actually in a different context).
Maybe
> is part of some functionality, but perhaps that could be decoupled
and,
> lets say, make it an optional feature. Just my impression.
>
> Cheers,
> Igor
>
>
> On 03.03.2010 21:28, Claude Vedovini wrote:
> >
> > Hi,
> >
> > I am the guy behind the dita-op, I'd be happy to help :)
> >
> > Normally you should be able to install the nightly build
fairly easily
> > with the latest Eclipse (see
> > http://www.dita-op.org/documentation/downloading-the-editor/#d3e449a1310
> > <http://www.dita-op.org/documentation/downloading-the-editor/#d3e449a1310>).
> > The build has a ditamap editor which only misses a gui for
reltables.
> > And I as far as know validation and code completion are
working.
> >
> > Like Igor said the project is a bit stale right now, due to
me being
> > over occupied since last august. I should be able to dedicate
more
> > time this year and release the M3.
> >
> > Regards,
> > Claude
> >
> > --- In dita-users@xxxxxxxxxxxxxxx
> > <mailto:dita-users%40yahoogroups.com>,
"nigelfrance"
<nparker@>
wrote:
> > >
> > > Hi,
> > > Is anyone out there using DITA Open Platform (an
Eclipse-based DITA
> > authoring tool)? I have downloaded and installed it but I
don't think
> > I have it working as expected. Would appreciate a bit of help.
> > >
> >
> >
>
|
