[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
RE: [wtp-incubator-dev] More on XSL Graduation ...
|
There is another alternative that you guys should consider before deciding
to stay with the current plan of merging into the Source Editing project.
You could convert XSL Tools component into an XSL Tools project (under the
root WTP project) and then graduate that project. Shouldn't take much longer
than what you are currently considering doing, but you would end up with an
easily identifying entity at Eclipse which will make it easier for potential
contributors to find you and join the effort. Then, if you eventually create
a broader-scope XML Tools project, the XSL Tools can become its sub-project
(a simple move that's easy from process and technical standpoint since code
and community is already contained in a well-defined project).
- Konstantin
-----Original Message-----
From: wtp-incubator-dev-bounces@xxxxxxxxxxx
[mailto:wtp-incubator-dev-bounces@xxxxxxxxxxx] On Behalf Of David Carver
Sent: Thursday, February 19, 2009 6:44 AM
To: WTP Incubator Dev list
Subject: Re: [wtp-incubator-dev] More on XSL Graduation ...
Agreed....XSL Tools graduation plans should go on as they are currently
planned too. The XML Development Tools is a long term thing, and will
take a while to get going, if it even ever gets off the ground.
Dave
Doug Satchwell wrote:
> I too think that having an XML Tools project is a good idea. However, it
would be really quite a massive undertaking - it would need to be discussed
as some sort of high-level strategic review for Eclipse. I'm not saying it
can't be done, its just going to take a lot of time and careful
consideration. Its not going to happen any time soon.
>
> I would definitely like to see XSL Tools graduate within Source Editing
before any discussions about having an XML Tools project. Graduating would
mean we can get this project out to the big wide world as part of the
standard Eclipse packages. After years of hard work, we have developed some
quality code. What XSL Tools needs right now is more widespread adoption -
incubators are great but many people just won't bother with them, either
because they don't know they are there or because of bad previous
experiences of using non-production ready incubating plugins.
>
> Graduation would be official confirmation that this code is good enough
for the real world, and ultimately would lend more weight to the idea of
having a separate XML Tools project.
>
> Doug.
>
>
>
> ----- Original Message ----
>
>> From: David Carver <d_a_carver@xxxxxxxxx>
>> To: WTP Incubator Dev list <wtp-incubator-dev@xxxxxxxxxxx>
>> Sent: Thursday, 19 February, 2009 5:33:09
>> Subject: Re: [wtp-incubator-dev] More on XSL Graduation ...
>>
>> Konstantin Komissarchik wrote:
>>
>>>> While I agree, I also view the WTP Incubator as it's own project, and
the XSL
>>>>
>> Tools as a sub project within that project.
>>
>>>>
>>>>
>>> Have to be carefully transposing personal views onto technical terms
with
>>> specific definitions in the process. :)
>>> Right now XSL Tools is a component, not a project. That has particular
>>> implications from process standpoint. Until recently, it was not
possible to
>>> have arbitrary nesting of projects, so components were frequently
created
>>> when a project would have been more appropriate. Since the process
change,
>>> I've seen more and more projects converting components into projects.
>>>
>>>
>> Ooops..semantics. :) Yes it's a component in name only. :)
>>
>>
>>>
>>>
>>>> In some ways, this is why I would eventually like to see a true XML
>>>>
>> Development Tools project either in WTP or housed in the Technology
>>
>>>>
>>>>
>>> project.
>>>
>>> I would agree with that. The large potential scope of XML development
tools
>>> functional area, the pace of growth of activity in this area and the
>>> importance of positioning Eclipse as a viable player in this area all
argue
>>> for a dedicated project. So, why don't you propose the XML Tools project
>>> (with XSL Tools as the initial component) right now? It doesn't make
much
>>> sense to move this code first into source editing while planning on
moving
>>> it again later. In fact, if you were feeling really aggressive, you
could
>>> even use the new project to stake out org.eclipse.xml namespace.
>>>
>>>
>> Aww....you walked right into it.
>>
>> http://wiki.eclipse.org/XML_Development_Tools_Proposal
>>
>>
>>> If you do end up proposing a separate project, I would recommend
starting it
>>> out as WTP sub-project while you have dependencies on parts of WTP. One
of
>>> the things that would hopefully happen once there is a dedicated XML
tools
>>> component is that some of the existing pieces from other WTP projects
(XML
>>> editor, XSD support, etc.) would eventually find their way into it. If
that
>>> happens and interest in this area keeps growing like it has been so far,
I
>>> can see this project moving to the Tools project or even becoming a
>>> top-level project in an extreme case. Technology project would not be
the
>>> right place as it's an incubator for emerging projects rather than a
place
>>> where mature projects can remain indefinitely.
>>>
>>>
>> See above. Tools would work as well. Anyways, if anybody is interested,
update
>> the wiki page.
>>
>>
>> _______________________________________________
>> wtp-incubator-dev mailing list
>> wtp-incubator-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
>>
>
>
>
>
>
> _______________________________________________
> wtp-incubator-dev mailing list
> wtp-incubator-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
>
>
_______________________________________________
wtp-incubator-dev mailing list
wtp-incubator-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-incubator-dev
No virus found in this incoming message.
Checked by AVG - www.avg.com
Version: 8.0.237 / Virus Database: 270.10.25/1957 - Release Date: 02/17/09
07:07:00
