[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [orion-dev] Have request for allowing eslint to be used ?
|
https://bugs.eclipse.org/bugs/show_bug.cgi?id=467903
I have opened a bug to weigh the pros/cons of requesting such an exception.
Curtis
![Inactive hide details for "Max Rydahl Andersen" ---05/21/2015 10:17:18 AM---On 21 May 2015, at 16:02, Curtis Windatt wrote: > h]()
"Max Rydahl Andersen" ---05/21/2015 10:17:18 AM---On 21 May 2015, at 16:02, Curtis Windatt wrote: > https://dev.eclipse.org/ipzilla/show_bug.cgi?id=84
From: "Max Rydahl Andersen" <manderse@xxxxxxxxxx>
To: "Orion developer discussions" <orion-dev@xxxxxxxxxxx>
Date: 05/21/2015 10:17 AM
Subject: Re: [orion-dev] Have request for allowing eslint to be used ?
Sent by: orion-dev-bounces@xxxxxxxxxxx
On 21 May 2015, at 16:02, Curtis Windatt wrote:
> https://dev.eclipse.org/ipzilla/show_bug.cgi?id=8420
>
> We have requested the EMO to allow usage of the existing ESLint rules.
> The
> project added a Contributor License Agreement which was necessary to
> allow
> Orion to consume newer versions of ESLint. However, the CLA does not
> apply
> retroactively, so the existing rules can not be accepted. The only
> way EMO
> will change this decision is if the ESLint project lead performs a
> provenance exercise, contacting all previous authors of the code
> (which are
> numerous).
I'm asking since just yesterday the Eclipse Board approved usage of
moment.js
and Bootstrap UI by the openK project.
These libraries had similar issues afaics, thus I was wondering if
orion project could try pursue this with libraries like eslint where
it obviously (at least to me ;) looks like life would be easier if we
could update more actively to the upstream versions.
The process for this is that the project (in this case Orion) ask the
EMO
to request approval for an exception from the board.
This is described in Exhibit C on the IP Policy here:
https://eclipse.org/org/documents/2010.12.08.Implementing.the.IP.Policy.pdf
> The project lead has stated that they do not have time to
> perform such an exercise.
>
> In the code we have attempted to keep the names and behaviour of rules
> inline with ESLint so should they become available in the future the
> change
> will be as seamless as possible. Most of the rule information is
> captured
> at: https://wiki.eclipse.org/Orion/ESLint
Yes, and its this that seems like unnecessary churn/differences compared
if Orion could just use eslint, correct ?
/max
> Curtis
>
>
>
> From: "Max Rydahl Andersen" <manderse@xxxxxxxxxx>
> To: "Orion developer discussions" <orion-dev@xxxxxxxxxxx>
> Date: 05/21/2015 06:23 AM
> Subject: [orion-dev] Have request for allowing eslint to be used ?
> Sent by: orion-dev-bounces@xxxxxxxxxxx
>
>
>
> Hi,
>
> I was wondering if the orion project have considered submitting a
> request to the EMO and eventually
> Bored to allow using ESlint despite the (IMO minor) IP issues with
> respect to non-explicit CLA in the past ?
>
> That seem to be something that could simplify the codebase and keeping
> faster uptodate with
> updates to the rules instead of manually maintaining them ?
>
> /max
> http://about.me/maxandersen
> _______________________________________________
> orion-dev mailing list
> orion-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe
> from this list, visit
> https://dev.eclipse.org/mailman/listinfo/orion-dev
>
> _______________________________________________
> orion-dev mailing list
> orion-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or
> unsubscribe from this list, visit
> https://dev.eclipse.org/mailman/listinfo/orion-dev
/max
http://about.me/maxandersen
_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/orion-dev
