[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [mdt-papyrus.dev] EPL v2 for SysML 1.4 ?

Hi

If you just do long search and replaces, the migration is mindless, so doing all at once is easy, although doing it in steps is not particularly problematic. BUT

If you rebase an EPL 1.0 WIP branch onto an EPL 2.0 master, you increase the rebase conflicts. I was surprised how much pain this caused me. I recommend maximizing what is on master before doing one total change.

ÂÂÂ Regards

ÂÂÂ ÂÂÂ Ed Willink


On 27/06/2018 11:40, MAGGI Benoit wrote:

Hi,

Â

@QuentinÂ: I disagree, I think that having one component undergo the license migration will help to debunk the subject.

The license migration for the main repo will be a lot safer if we already did it once with SysML 1.4.

Â

/Benoit

Â

DeÂ: mdt-papyrus.dev-bounces@xxxxxxxxxxx <mdt-papyrus.dev-bounces@xxxxxxxxxxx> De la part de LE MENEZ Quentin
EnvoyÃÂ: mercredi 27 juin 2018 11:34
ÃÂ: Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
ObjetÂ: [PROVENANCE INTERNET] Re: [mdt-papyrus.dev] EPL v2 for SysML 1.4 ?

Â

Hi,

Â

+1 for changing into Eclipse Papyrus J

Â

Weâll be waiting for the committee approval for migrating the main repository and this will be the first to undergo the migration. As for the auxiliary repositories they should be treated afterwards as needed on a case by case review until we have a satisfactory state across the board.

Â

Cheers,

Quentin

Â

DeÂ: mdt-papyrus.dev-bounces@xxxxxxxxxxx <mdt-papyrus.dev-bounces@xxxxxxxxxxx> De la part de TESSIER Patrick
EnvoyÃÂ: mercredi 27 juin 2018 11:09
ÃÂ: Papyrus Project list <mdt-papyrus.dev@xxxxxxxxxxx>
ObjetÂ: [PROVENANCE INTERNET] Re: [mdt-papyrus.dev] EPL v2 for SysML 1.4 ?

Â

Hello Benoit,

Ok for Eclipse Papyrus.

Â

For papyrus we received the request to switch to EPL2 for the next version during the review.

Before going to EPL2, I will inform our CEA committee.

Each module of papyrus will change the license little by little.

Patrick

Â

DeÂ: mdt-papyrus.dev-bounces@xxxxxxxxxxx [mailto:mdt-papyrus.dev-bounces@xxxxxxxxxxx] De la part de MAGGI Benoit
EnvoyÃÂ: mercredi 27 juin 2018 09:00
ÃÂ: Papyrus Project list <
mdt-papyrus.dev@xxxxxxxxxxx>
ObjetÂ: [PROVENANCE INTERNET] Re: [mdt-papyrus.dev] EPL v2 for SysML 1.4 ?

Â

Hi,

Â

Thanks for all the answers.

Â

âEclipse Papyrusâ is ok for me.

Does anyone have an objection?

Â

I agree that moving everything to EPL2 in on go would be the best but due to the size of the project and the number of plugin, I donât think itâs possible. But if we agree on the new license then we can

-ÂÂÂÂÂÂÂÂÂ Change license for all incoming component release

-ÂÂÂÂÂÂÂÂÂ Change the license in Papyrus core/toolsmith for September

Â

Can anyone confirm that there isnât any fishing dual licensing stuff ?

Â

Regards,

/Benoit

Â

Â

Â

DeÂ: mdt-papyrus.dev-bounces@xxxxxxxxxxx <mdt-papyrus.dev-bounces@xxxxxxxxxxx> De la part de Ed Willink
EnvoyÃÂ: mardi 26 juin 2018 22:07
ÃÂ:
mdt-papyrus.dev@xxxxxxxxxxx
ObjetÂ: Re: [mdt-papyrus.dev] EPL v2 for SysML 1.4 ?

Â

Hi

I recall that once upon a time "Eclipse Modeling Project" was very strongly recommended, but recent practice has changed; Eclipse Xtext, Eclipse Mylyn, Eclipse DLTK. I've migrated to Eclipse OCL, Eclipse QVTd. So I suggest Eclipse Papyrus. "Project" is bloat.

Regards

Ed Willink

Â

On 26/06/2018 14:38, Camille Letavernier wrote:

Hi,

Â

I've no opinion for the license part; but projects should follow the Eclipse <ProjectName> pattern [1]. So it would be either Eclipse Modeling (Project) or Eclipse Papyrus (Project). Note that this is decided at the PMC level [2], which is probably why we're using Eclipse Modeling Project.

Â

The provider name should be the full project name. If the name does not already do so, then prefix it with the name of the forge, e.g. "Eclipse EGit", "Eclipse SWTBot", or "LocationTech uDig".

Â

Every plug-in and feature must specify a descriptive provider-name (for features), or Bundle-Vendor header (for plug-ins), as determined by the project's PMC (e.g. "Eclipse Modeling Project" rather than "Eclipse.org")

Â

Cheers,
Camille

Â

On Tue, Jun 26, 2018 at 2:05 PM MAGGI Benoit <Benoit.MAGGI@xxxxxx> wrote:

Hi,

Â

Eclipse public license v1.0 is now deprecated (see [1]), and itâs recommended to move to EPL v2.

In my understanding when simply moving from EPLv1 to EPLv2 there is no legal complexity

and headers and other files should be updated accordingly (See [2]).

Â

Following Photon train release, I will publish a SysML 1.4 version compatible with Papyrus 4.0.0 (Photon)

This version will be number 1.3.0 and I want to take this opportunity Âto update the license.

Â

I created a dedicated bug [3] and also a patch [4]

Â

Any comments ? It would be nice if someone can check the patch.

Â

Related points:

-ÂÂÂÂÂÂÂÂÂ I discovered the shared license concept in feature. (It would be nice to use it in Papyrus core)

-ÂÂÂÂÂÂÂÂÂ Can we agree to change the name of Bundle-Vendor from Eclipse Modeling Project to (one of them)

oÂÂ Eclipse Papyrus Project

oÂÂ Papyrus Project

oÂÂ Eclipse.org Papyrus

oÂÂ (this are patterns used by other projects but Iâm open to anything containing âPapyrusâ)

oÂÂ => The main reason is to remove Papyrus prefix from the name of the plugins (should improve the clarity)

Â

Regards,

Benoit

Â

1Â: https://www.eclipse.org/legal/epl-2.0/faq.php#h.60mjudroo8e5

2Â: https://www.eclipse.org/legal/epl-2.0/faq.php#h.tci84nlsqpgw

3Â:https://bugs.eclipse.org/bugs/show_bug.cgi?id=536295

4Â:https://git.eclipse.org/r/#/c/125024/

Â

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev


Â

--

Camille Letavernier

Senior Software Engineer EclipseSource France

Phone: +33 1 85 41 09 21

EclipseSource France SAS

Palaiseau-Entreprises

7 rue de la Croix Martre

91120 Palaiseau

General Manager: Remi Schnekenburger

Registered Office:Â7 rue de la Croix Martre, 91120 Palaiseau, France

Commercial RegisterÂ824 977 516ÂÂR.C.S.ÂEVRY

Â

_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

Â

Â

Image supprimÃe par l'expÃditeur.

Virus-free. www.avast.com

Â



_______________________________________________
mdt-papyrus.dev mailing list
mdt-papyrus.dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/mdt-papyrus.dev

JPEG image