Re: [polarsys-iwg] Eclipse Tool Stack Interchange Format v0.1

[Jed Anderson <jed@xxxxxxxxxxxx>]

Mike: Thanks for your help, we'll release v0.2 under the EPL shortly.

Dominique: Donat Csikos and I have a proposed talk at EclipseCon
France ( http://www.eclipsecon.org/france2013/sessions/how-cern-scaled-eclipse-lhc
).  If the talk is accepted, I will be there and will be happy to
discuss this further.  If it's not accepted, we may have to discuss
this online.

Pascal: The goal of this format is not about driving installers,
although that is one application.  The goal of the specification is to
provide a transparent format which allows humans and tools to pass
around tool stacks and to provide a stable format across
install/provision/SMS technologies so that the descriptions of your
tool stack is independent of the implementation of the tools which
work on the tool stack. We feel this separation is necessary in order
to provide the ecosystem with the building blocks to solve some of the
problems our customers have such as vendor dependence and long term
support.

Cheers,
jkca
Genuitec, LLC

On Tue, Apr 16, 2013 at 11:15 AM, Pascal Rapicault
<pascal.rapicault@xxxxxxxxxxxx> wrote:
> To be clear, is this about driving an installer, providing a descriptor to build an eclipse downloads, etc...
>
>
> -----Original Message-----
> From: polarsys-iwg-bounces@xxxxxxxxxxx [mailto:polarsys-iwg-bounces@xxxxxxxxxxx] On Behalf Of Pascal Rapicault
> Sent: April-16-13 11:27 AM
> To: Polarsys IWG
> Subject: Re: [polarsys-iwg] Eclipse Tool Stack Interchange Format v0.1
>
> I have not been part of the EclipseCon workshop, so I would be curious to know what is the goal of this format?
>
> -----Original Message-----
> From: polarsys-iwg-bounces@xxxxxxxxxxx [mailto:polarsys-iwg-bounces@xxxxxxxxxxx] On Behalf Of Jed Anderson
> Sent: April-15-13 2:46 PM
> To: Polarsys IWG
> Subject: Re: [polarsys-iwg] Eclipse Tool Stack Interchange Format v0.1
>
> Having spent some time with Buckminster, it's clear there is some overlap.  However, like Tim said, there should be.  The goal is to create a common format for modeling and exchanging tool stacks.
>
> Aside from Erdal's comment, we haven't heard anything regarding the ETSIF.  Does anybody else out there have opinions in this space?  Is this format something applicable to your work?
>
> Cheers,
> Jed Anderson
> Genuitec, LLC
>
> On Mon, Apr 15, 2013 at 11:30 AM, Jed Anderson <jedkcanderson@xxxxxxxxx> wrote:
>> Having spent some time with Buckminster, it's clear there is some
>> overlap.  However, like Tim said, there should be.  The goal is to
>> create a common format for modeling tool stacks.
>>
>> Aside from Erdal's comment, we haven't heard anything regarding the
>> ETSIF.  Does anybody else out there have opinions in this space?  Is
>> this format something applicable to your work?
>>
>> Cheers,
>> Jed Anderson
>> Genuitec, LLC
>>
>> On Sat, Apr 6, 2013 at 1:52 PM, Tim Webb <tim@xxxxxxxxxxxx> wrote:
>>> Erdal,
>>>
>>> That is exactly the challenge that we all face.  There are many tools
>>> that each have their own ways of modeling Eclipse stacks whether p2,
>>> maven, buckminster, epp or others.  The interchange format's
>>> objective is to provide a level of normalization across various tools
>>> with the ability to transform easily.
>>>
>>> For context, could you share a link to a single file that could
>>> instantiate an Eclipse IDE and speak to the applicability for
>>> existing and new tools to support that format?
>>>
>>> The cross-implementation aspect of the specification is key to us as
>>> it provides a foundation for flexible migration between tool delivery
>>> platforms over an extended period of time -- potentially measured in decades.
>>>
>>> Could you see a relatively easy transform from this kind of format
>>> and buckminster?  Certainly for our own solutions, while this is
>>> different than our own formats, we do see an ease with transforming
>>> from this generic representation.
>>>
>>> Thanks!
>>>
>>> Tim
>>>
>>>
>>> On Saturday, April 6, 2013, Erdal Karaca wrote:
>>>>
>>>> I think there is much overlap between Eclipse Buckminster (see [1])
>>>> and your suggestion.
>>>>
>>>> [1] http://eclipse.org/buckminster/
>>>>
>>>>
>>>> 2013/4/5 Jed Anderson <jed@xxxxxxxxxxxx>
>>>>>
>>>>> Hi Everybody,
>>>>>
>>>>> It was great to get to meet most of you last week at EclipseCon.  I
>>>>> was encouraged by the feeling of comradery within the group and
>>>>> look forward to the next time we can talk face to face.
>>>>>
>>>>> Following up on the idea I talked about during the BOF, Tim and I
>>>>> have put together the beginning of a file format specification for
>>>>> describing Eclipse-based development environments.  We'd like to
>>>>> hear feedback from the working group on the applicability, design,
>>>>> and implications of the format.
>>>>>
>>>>> Clearly, this is a work in progress as large sections are missing
>>>>> or need flushing out.  Although it is derived from our combined
>>>>> knowledge of writing Eclipse delivery platforms, we do not believe
>>>>> we are the only authority on this matter.  We feel strongly that
>>>>> the more feedback and discussion that goes into this specification,
>>>>> the better it will serve all of us.
>>>>>
>>>>> To that end, please take some time to read the specification
>>>>> document and example XML and provide comments.  We intend to
>>>>> include the example XML as an exemplary part of the specification,
>>>>> but find it more legible in an XML editor so for the time we will
>>>>> include it as a separate attachment.
>>>>>
>>>>> Cheers,
>>>>> Jed Anderson
>>>>> Genuitec, LLC
>>>>>
>>>>> _______________________________________________
>>>>> polarsys-iwg mailing list
>>>>> polarsys-iwg@xxxxxxxxxxx
>>>>> http://dev.eclipse.org/mailman/listinfo/polarsys-iwg
>>>>>
>>>>
>>>
>>>
>>> --
>>>
>>> Cheers,
>>> Tim
>>>
>>>
>>> Timothy R. Webb
>>> Genuitec, LLC
>>> www.genuitec.com/sdc
>>> www.linkedin.com/in/trwebb
>>>
>>>
>>> _______________________________________________
>>> polarsys-iwg mailing list
>>> polarsys-iwg@xxxxxxxxxxx
>>> http://dev.eclipse.org/mailman/listinfo/polarsys-iwg
>>>
> _______________________________________________
> polarsys-iwg mailing list
> polarsys-iwg@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/polarsys-iwg
> _______________________________________________
> polarsys-iwg mailing list
> polarsys-iwg@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/polarsys-iwg
> _______________________________________________
> polarsys-iwg mailing list
> polarsys-iwg@xxxxxxxxxxx
> http://dev.eclipse.org/mailman/listinfo/polarsys-iwg