[
Date Prev][Date Next][
Thread Prev][Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [technology-projects] [lyo-dev] Request to move eclipse/Lyo sample code to GitHub
|
Hello,
I would just like to point out that moving projects under the Eclipse organisation on Github does not imply loss of license checks from Eclipse IP team.
I have just filed https://bugs.eclipse.org/bugs/show_bug.cgi?id=518773 to move lyo.rio repository to Github to allow for easier work on Lyo 3. Eclipse Lyo team will handle the CQ burden on the pull requests, while the barrier for contribution would fall significantly (only a signed ECA & Signed-off-by line).
-Andrew.
On 2017-05-11, 20:07, lyo-dev-bounces@xxxxxxxxxxx on behalf of Jim Ruehlin <lyo-dev-bounces@xxxxxxxxxxx on behalf of jruehlin@xxxxxxxxxx> wrote:
Technically this would be valuable. But we need to consider that the advantage of downloading from Eclipse is the license validation that protects both Eclipse and the company doing the downloading. Code in GitHub would not go through the CQ
process and we could offer no guarantees of license conformity. The overhead of Eclipse is a pain, but it does provide a high level of legal protection to the user. And it reduces the overhead for organizations consuming the code because they don't need to
do their own license checks.
At the lest we'd probably need a disclaimer that the code is not reviewed as it is on Eclipse, and a link back to Eclipse so the user could download reviewed code.
We'd probably also need a process where we could harvest GitHub code into Eclipse Lyo. But I fear that it would be impossible to provide the certification of originality you need for Eclipse code. Unless we can be sure we could do this, any Lyo
code contributed via GitHub wouldn't be able to be incorporated into Lyo. The contributor would need to re-contribute via the Eclipse contribution mechanism.
That said, Eclipse may have some administration method that can accept GitHub code that I'm not aware of. It needs to be researched before we use GitHub as a contribution mechanism.
- Jim
Jim Ruehlin
________________________________________
Mobile: 1-949-545-8912
E-mail: jruehlin@xxxxxxxxxx
Technical Blog:
jazzpractices.wordpress.com <mailto:jruehlin@xxxxxxxxxx>
Chat: jruehlin@xxxxxxxxxx jruehlin jruehlin@xxxxxxxxx
Find me on: <http://jazzpractices.wordpress.com> <http://www.linkedin.com/pub/jim-ruehlin/3/287/507> <http://plus.google.com/+jimruehlin> and
within IBM on: <http://w3.ibm.com/connections/profiles/html/profileView.do?key=f37d4274-c549-4f88-b374-8ea23ae9b5ac&;>
600 Anton Blvd
Costa Mesa, CA 92626-7221
United States
----- Original message -----
From: "Jim Amsden" <jamsden@xxxxxxxxxx>
Sent by: lyo-dev-bounces@xxxxxxxxxxx
To: technology-projects@xxxxxxxxxxx
Cc: Lyo project developer discussions <lyo-dev@xxxxxxxxxxx>
Subject: [lyo-dev] Request to move eclipse/Lyo sample code to GitHub
Date: Thu, May 11, 2017 10:26 AM
The eclipse/Lyo dev team has been discussing the possibility of moving sample code from eclipse to GitHub. The OASIS OSLC Core and Change and Configuration Management TC have also expressed an interest in this initiative. The
motivation of this would be to:
1. better separate sample code from the eclipse/Lyo OSLC4J SDK
2. better decouple development for and with OSLC
3. simplify the process overhead for maintaining sample code
4. encourage broader OSLC community participation by reducing the process overhead for sample contribution
I would like to see if there would be PMC and possible EMO support for this initiative, and would like to understand the implications in terms of forking, IP and licensing. Or perhaps the PMC would have other recommendations
on how to address the motivation.
Jim Amsden, Senior Technical Staff Member
OSLC and Linked Lifecycle Data
919-525-6575
_______________________________________________
lyo-dev mailing list
lyo-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/lyo-dev
