Re: [cross-project-issues-dev] Updated Eclipse licenses ?

2020-09-02 Thread Jonah Graham 
Hi Ralph,

I have put together a minimal commit that uses the standard license
feature: https://git.eclipse.org/r/c/bpmn2/org.eclipse.bpmn2/+/168696

Please review and merge.

Jonah

~~~
Jonah Graham
Kichwa Coders
www.kichwacoders.com


On Wed, 2 Sep 2020 at 17:38, Ralph Soika  wrote:

> Hello,
>
> sorry to bother you again, but I think I need you help.
> I overtook the projects:
>
>-  mdt-bpmn2 
>- "Eclipse Business Process Model and Notation (BPMN2)"
>-  soa-bepl  -
>"Eclipse BPEL Designer"
>
> a view weeks ago. I tried to prepare an updated version for both projects
> fixing some minor technical issues with the code compatibility in
> Eclipse-2020-09.
>
> Now Ed Merks recognized that the license information in the
> feature.xml/features.properties are in a bad shape.
>
> I tried to fix it but - as Ed told me - with no success (Bug 566499
> ). I do not think
> that I am in a position to fix this in a way that fulfills all the
> requirements form the Eclipse Foundation. The license text was initial
> created 9 and 10 years ago and was never changed by anybody.
> The initial contribution for mdt-bpmn2 project was form RedHat.
>
> Can some one help me to edit these two files in a way that those files
> meet the requirements form the Eclipse foundation?
> I already have updated the license.html files to the latest Version 2.0 of
> the Eclipse Public License.
> And I thought that it should be fine if I add the text version of this
> license directly into the features.xml file. (initial the license text was
> part of the features.properties file). But as Ed told me this is not
> accepted.
>
> Attached in this e-mail I send you the files, so that someone can take a
> look into it. Again, if this were a purely technical problem, I would like
> to solve it myself. However, as this is a legal problem, I do not dare to
> make any further changes here by myself.
>
>
> Thanks for your help in advance
>
> Best regards
> Ralph
>
>
>
>
> On 01.09.20 23:23, Wayne Beaton wrote:
>
> Right. I forgot about the Eclipse License Feature.
>
> FWIW, I've opened a bug
>  to add this to the
> Eclipse Project Handbook.
>
> Should (or do) we have this captured in the simultaneous release
> documentation?
>
> Wayne
>
> On Tue, Sep 1, 2020 at 5:18 PM Matthias Sohn 
> wrote:
>
>> On Tue, Sep 1, 2020 at 10:52 PM Ralph Soika 
>> wrote:
>>
>>> Hi,
>>>
>>> in our projects (soa-bpmn, soa-bepl, mdt-bpmn2) the eclipse license text
>>> seems to be outdated (it is still from the year 2011).
>>>
>>> Can someone please point me to a page or another eclipse project, where
>>> I can see the correct Eclipse license text, so that I can copy the text
>>> into my features.properties and license.html artifacts. Especially the text
>>> for the feature.properties has a curious formatting. So I am looking for a
>>> features.properties file where I can copy this formatting to avoid breaking
>>> the text formatting at some line where I should not do so.
>>>
>> we use the eclipse license feature [1] e.g. here in the egit feature [2].
>> The version of the license feature is defined in the target platform we
>> use [3].
>> In feature.properties we use [4]. If there is a new version of the
>> license we
>> update the version of the license feature we include in the target
>> platform.
>>
>> [1]
>> https://git.eclipse.org/r/plugins/gitiles/cbi/org.eclipse.license/+/refs/heads/master
>> [2]
>> https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit-feature/feature.xml#8
>> [3]
>> https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit.target/egit-4.16-staging.target#25
>> [4]
>> https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit-feature/feature.properties#22
>>
>>
>> -Matthias
>> ___
>> cross-project-issues-dev mailing list
>> cross-project-issues-dev@eclipse.org
>> To unsubscribe from this list, visit
>> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>>
>
>
> --
>
> Wayne Beaton
>
> Director of Open Source Projects | Eclipse Foundation, Inc.
>
> Join us at our virtual event: EclipseCon 2020
>  - October 20-22
>
> ___
> cross-project-issues-dev mailing listcross-project-issues-...@eclipse.org
> To unsubscribe from this list, visit 
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>
> --
>
> *Imixs Software Solutions GmbH*
> *Web:* www.imixs.com *Phone:* +49 (0)89-452136 16
> *Office:* Agnes-Pockels-Bogen 1, 80992 München
> Registergericht: Amtsgericht Muenchen, HRB 136045
> Geschaeftsführer: Gaby Heinle u. Ralph Soika
>
> *Imixs* is an open source company, read more:

Re: [cross-project-issues-dev] Updated Eclipse licenses ?

2020-09-02 Thread Ralph Soika 

Hello,

sorry to bother you again, but I think I need you help.
I overtook the projects:

 * mdt-bpmn2 
   - "Eclipse Business Process Model and Notation (BPMN2)"
 * soa-bepl  - "Eclipse
   BPEL Designer"

a view weeks ago. I tried to prepare an updated version for both 
projects fixing some minor technical issues with the code compatibility 
in Eclipse-2020-09.


Now Ed Merks recognized that the license information in the 
feature.xml/features.properties are in a bad shape.


I tried to fix it but - as Ed told me - with no success (Bug 566499 
). I do not think 
that I am in a position to fix this in a way that fulfills all the 
requirements form the Eclipse Foundation. The license text was initial 
created 9 and 10 years ago and was never changed by anybody.

The initial contribution for mdt-bpmn2 project was form RedHat.

Can some one help me to edit these two files in a way that those files 
meet the requirements form the Eclipse foundation?
I already have updated the license.html files to the latest Version 2.0 
of the Eclipse Public License.
And I thought that it should be fine if I add the text version of this 
license directly into the features.xml file. (initial the license text 
was part of the features.properties file). But as Ed told me this is not 
accepted.


Attached in this e-mail I send you the files, so that someone can take a 
look into it. Again, if this were a purely technical problem, I would 
like to solve it myself. However, as this is a legal problem, I do not 
dare to make any further changes here by myself.



Thanks for your help in advance

Best regards
Ralph




On 01.09.20 23:23, Wayne Beaton wrote:

Right. I forgot about the Eclipse License Feature.

FWIW, I've opened a bug 
 to add this to 
the Eclipse Project Handbook.


Should (or do) we have this captured in the simultaneous release 
documentation?


Wayne

On Tue, Sep 1, 2020 at 5:18 PM Matthias Sohn > wrote:


On Tue, Sep 1, 2020 at 10:52 PM Ralph Soika mailto:ralph.so...@imixs.com>> wrote:

Hi,

in our projects (soa-bpmn, soa-bepl, mdt-bpmn2) the eclipse
license text seems to be outdated (it is still from the year
2011).

Can someone please point me to a page or another eclipse
project, where I can see the correct Eclipse license text, so
that I can copy the text into my features.properties and
license.html artifacts. Especially the text for the
feature.properties has a curious formatting. So I am looking
for a features.properties file where I can copy this
formatting to avoid breaking the text formatting at some line
where I should not do so.

we use the eclipse license feature [1] e.g. here in the egit
feature [2].
The version of the license feature is defined in the target
platform we use [3].
In feature.properties we use [4]. If there is a new version of the
license we
update the version of the license feature we include in the target
platform.

[1]

https://git.eclipse.org/r/plugins/gitiles/cbi/org.eclipse.license/+/refs/heads/master
[2]

https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit-feature/feature.xml#8
[3]

https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit.target/egit-4.16-staging.target#25
[4]

https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit-feature/feature.properties#22


-Matthias
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org

To unsubscribe from this list, visit
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev



--

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Join us at our virtual event: EclipseCon 2020 
- October 20-22



___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

--

*Imixs Software Solutions GmbH*
*Web:* www.imixs.com  *Phone:* +49 (0)89-452136 16
*Office:* Agnes-Pockels-Bogen 1, 80992 München
Registergericht: Amtsgericht Muenchen, HRB 136045
Geschaeftsführer: Gaby Heinle u. Ralph Soika

*Imixs* is an open source company, read more: www.imixs.org 



###
# Copyright (c) 2011, 2012, 2013, 2014 Red Hat, Inc. 
# All rights reserved. 
# This program is

Re: [cross-project-issues-dev] Updated Eclipse licenses ?

2020-09-01 Thread Wayne Beaton 
Right. I forgot about the Eclipse License Feature.

FWIW, I've opened a bug
 to add this to the
Eclipse Project Handbook.

Should (or do) we have this captured in the simultaneous release
documentation?

Wayne

On Tue, Sep 1, 2020 at 5:18 PM Matthias Sohn 
wrote:

> On Tue, Sep 1, 2020 at 10:52 PM Ralph Soika  wrote:
>
>> Hi,
>>
>> in our projects (soa-bpmn, soa-bepl, mdt-bpmn2) the eclipse license text
>> seems to be outdated (it is still from the year 2011).
>>
>> Can someone please point me to a page or another eclipse project, where I
>> can see the correct Eclipse license text, so that I can copy the text into
>> my features.properties and license.html artifacts. Especially the text for
>> the feature.properties has a curious formatting. So I am looking for a
>> features.properties file where I can copy this formatting to avoid breaking
>> the text formatting at some line where I should not do so.
>>
>> we use the eclipse license feature [1] e.g. here in the egit feature [2].
> The version of the license feature is defined in the target platform we
> use [3].
> In feature.properties we use [4]. If there is a new version of the license
> we
> update the version of the license feature we include in the target
> platform.
>
> [1]
> https://git.eclipse.org/r/plugins/gitiles/cbi/org.eclipse.license/+/refs/heads/master
> [2]
> https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit-feature/feature.xml#8
> [3]
> https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit.target/egit-4.16-staging.target#25
> [4]
> https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit-feature/feature.properties#22
>
>
> -Matthias
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>


-- 

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Join us at our virtual event: EclipseCon 2020
 - October 20-22
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Updated Eclipse licenses ?

2020-09-01 Thread Matthias Sohn 
On Tue, Sep 1, 2020 at 10:52 PM Ralph Soika  wrote:

> Hi,
>
> in our projects (soa-bpmn, soa-bepl, mdt-bpmn2) the eclipse license text
> seems to be outdated (it is still from the year 2011).
>
> Can someone please point me to a page or another eclipse project, where I
> can see the correct Eclipse license text, so that I can copy the text into
> my features.properties and license.html artifacts. Especially the text for
> the feature.properties has a curious formatting. So I am looking for a
> features.properties file where I can copy this formatting to avoid breaking
> the text formatting at some line where I should not do so.
>
> we use the eclipse license feature [1] e.g. here in the egit feature [2].
The version of the license feature is defined in the target platform we use
[3].
In feature.properties we use [4]. If there is a new version of the license
we
update the version of the license feature we include in the target platform.

[1]
https://git.eclipse.org/r/plugins/gitiles/cbi/org.eclipse.license/+/refs/heads/master
[2]
https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit-feature/feature.xml#8
[3]
https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit.target/egit-4.16-staging.target#25
[4]
https://git.eclipse.org/r/plugins/gitiles/egit/egit/+/refs/heads/master/org.eclipse.egit-feature/feature.properties#22


-Matthias
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

Re: [cross-project-issues-dev] Updated Eclipse licenses ?

2020-09-01 Thread Wayne Beaton 
There's pointers in the handbook section on the topic.

https://www.eclipse.org/projects/handbook/#legaldoc-plugins

There's also a pointer in the simultaneous release participation
requirements

.

I assume/hope that you're updating to EPL-2.0 while you're at it. Please
send a note to e...@eclipse.org to inform them of the change so that we can
update the project's metadata.

HTH,

Wayne

On Tue, Sep 1, 2020 at 4:52 PM Ralph Soika  wrote:

> Hi,
>
> in our projects (soa-bpmn, soa-bepl, mdt-bpmn2) the eclipse license text
> seems to be outdated (it is still from the year 2011).
>
> Can someone please point me to a page or another eclipse project, where I
> can see the correct Eclipse license text, so that I can copy the text into
> my features.properties and license.html artifacts. Especially the text for
> the feature.properties has a curious formatting. So I am looking for a
> features.properties file where I can copy this formatting to avoid breaking
> the text formatting at some line where I should not do so.
>
> Thanks for help
>
> Ralph
>
>
>
>
> --
>
> *Imixs Software Solutions GmbH*
> *Web:* www.imixs.com *Phone:* +49 (0)89-452136 16
> *Office:* Agnes-Pockels-Bogen 1, 80992 München
> Registergericht: Amtsgericht Muenchen, HRB 136045
> Geschaeftsführer: Gaby Heinle u. Ralph Soika
>
> *Imixs* is an open source company, read more: www.imixs.org
> ___
> cross-project-issues-dev mailing list
> cross-project-issues-dev@eclipse.org
> To unsubscribe from this list, visit
> https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
>


-- 

Wayne Beaton

Director of Open Source Projects | Eclipse Foundation, Inc.

Join us at our virtual event: EclipseCon 2020
 - October 20-22
___
cross-project-issues-dev mailing list
cross-project-issues-dev@eclipse.org
To unsubscribe from this list, visit 
https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev

[cross-project-issues-dev] Updated Eclipse licenses ?

2020-09-01 Thread Ralph Soika 

Hi,

in our projects (soa-bpmn, soa-bepl, mdt-bpmn2) the eclipse license text 
seems to be outdated (it is still from the year 2011).


Can someone please point me to a page or another eclipse project, where 
I can see the correct Eclipse license text, so that I can copy the text 
into my features.properties and license.html artifacts. Especially the 
text for the feature.properties has a curious formatting. So I am 
looking for a features.properties file where I can copy this formatting 
to avoid breaking the text formatting at some line where I should not do 
so.


Thanks for help

Ralph




--

*Imixs Software Solutions GmbH*
*Web:* www.imixs.com  *Phone:* +49 (0)89-452136 16
*Office:* Agnes-Pockels-Bogen 1, 80992 München
Registergericht: Amtsgericht Muenchen, HRB 136045
Geschaeftsführer: Gaby Heinle u. Ralph Soika

*Imixs* is an open source company, read more: www.imixs.org 



###
# Copyright (c) 2011, 2012, 2013, 2014 Red Hat, Inc. 
# All rights reserved. 
# This program is made available under the terms of the 
# Eclipse Public License v1.0 which accompanies this distribution, 
# and is available at http://www.eclipse.org/legal/epl-v10.html 
#
# Contributors: 
# Red Hat, Inc. - initial API and implementation 
###
copyright=Copyright (c) 2011-2016 Red Hat, Inc. and others. \
All rights reserved. This program and the accompanying materials \
are made available under the terms of the Eclipse Public License v1.0 \
which accompanies this distribution, and is available at

providerName=Eclipse.org

# "licenseURL" property - URL of the "Feature License"
# do not translate value - just change to point to a locale-specific HTML page
licenseURL=license.html

# "license" property - text of the "Feature Update License"
# should be plain text version of license agreement pointed to be "licenseURL"
license=\
Eclipse Foundation Software User Agreement\n\
February 1, 2011\n\
\n\
Usage Of Content\n\
\n\
THE ECLIPSE FOUNDATION MAKES AVAILABLE SOFTWARE, DOCUMENTATION, INFORMATION 
AND/OR\n\
OTHER MATERIALS FOR OPEN SOURCE PROJECTS (COLLECTIVELY "CONTENT").\n\
USE OF THE CONTENT IS GOVERNED BY THE TERMS AND CONDITIONS OF THIS\n\
AGREEMENT AND/OR THE TERMS AND CONDITIONS OF LICENSE AGREEMENTS OR\n\
NOTICES INDICATED OR REFERENCED BELOW.  BY USING THE CONTENT, YOU\n\
AGREE THAT YOUR USE OF THE CONTENT IS GOVERNED BY THIS AGREEMENT\n\
AND/OR THE TERMS AND CONDITIONS OF ANY APPLICABLE LICENSE AGREEMENTS\n\
OR NOTICES INDICATED OR REFERENCED BELOW.  IF YOU DO NOT AGREE TO THE\n\
TERMS AND CONDITIONS OF THIS AGREEMENT AND THE TERMS AND CONDITIONS\n\
OF ANY APPLICABLE LICENSE AGREEMENTS OR NOTICES INDICATED OR REFERENCED\n\
BELOW, THEN YOU MAY NOT USE THE CONTENT.\n\
\n\
Applicable Licenses\n\
\n\
Unless otherwise indicated, all Content made available by the\n\
Eclipse Foundation is provided to you under the terms and conditions of\n\
the Eclipse Public License Version 1.0 ("EPL"). A copy of the EPL is\n\
provided with this Content and is also available at 
http://www.eclipse.org/legal/epl-v10.html.\n\
For purposes of the EPL, "Program" will mean the Content.\n\
\n\
Content includes, but is not limited to, source code, object code,\n\
documentation and other files maintained in the Eclipse Foundation source 
code\n\
repository ("Repository") in software modules ("Modules") and made available\n\
as downloadable archives ("Downloads").\n\
\n\
   - Content may be structured and packaged into modules to facilitate 
delivering,\n\
 extending, and upgrading the Content. Typical modules may include 
plug-ins ("Plug-ins"),\n\
 plug-in fragments ("Fragments"), and features ("Features").\n\
   - Each Plug-in or Fragment may be packaged as a sub-directory or JAR 
(Java(TM) ARchive)\n\
 in a directory named "plugins".\n\
   - A Feature is a bundle of one or more Plug-ins and/or Fragments and 
associated material.\n\
 Each Feature may be packaged as a sub-directory in a directory named 
"features".\n\
 Within a Feature, files named "feature.xml" may contain a list of the 
names and version\n\
 numbers of the Plug-ins and/or Fragments associated with that 
Feature.\n\
   - Features may also include other Features ("Included Features"). Within 
a Feature, files\n\
 named "feature.xml" may contain a list of the names and version 
numbers of Included Features.\n\
\n\
The terms and conditions governing Plug-ins and Fragments should be\n\
contained in files named "about.html" ("Abouts"). The terms and\n\
conditions governing Features and Included Features should be contained\n\
in files named "license.html" ("Feature Licenses"). Abouts and Feature\n\
Licenses may be located in any directory of a Download or Module\n\
including, but not limited to the following locations:\n\
\n\