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] Odd bugzilla access issues for anonymous access

2020-09-02 Thread Denis Roy 
I've just responded on the bug a minute ago :)

Denis


On 2020-09-02 3:58 p.m., Thomas Watson wrote:
> FYI - I'm seeing odd behavior for recently opened bugzilla issues that
> do not allow them to be read without being logged into bugzilla.  I
> opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=566622
>  
> NOTE: You must be logged into bugzilla to read the details of the bug!!
>
> Tom
>  
>
>
> ___
> 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
-- 

*Denis Roy*

*Director, IT Services | **Eclipse Foundation, Inc.*

/Eclipse Foundation/ /: The Platform for Open
Innovation and Collaboration/

Twitter: @droy_eclipse

___
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] Odd bugzilla access issues for anonymous access

2020-09-02 Thread Thomas Watson 
FYI - I'm seeing odd behavior for recently opened bugzilla issues that do not allow them to be read without being logged into bugzilla.  I opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=566622
 
NOTE: You must be logged into bugzilla to read the details of the bug!!
Tom 

___
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] Upcoming changes in Docker pull rates policy

2020-09-02 Thread Denis Roy 
Greetings,

Please be aware of Upcoming changes in Docker pull rates policy. The
build team will need a stratgy for all Jiro instances that run on the
Eclipse build farm

Follow along at https://eclip.se/566581


Denis

-- 

*Denis Roy*

/Eclipse Foundation/ /: The Platform for Open
Innovation and Collaboration/

Twitter: @droy_eclipse

___
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] Simultaneous Release Page 2020-09

2020-09-02 Thread Thomas Watson 
+1
Tom 
 
 
- Original message -From: Martin Lippert Sent by: cross-project-issues-dev-boun...@eclipse.orgTo: Cross project issues Cc:Subject: [EXTERNAL] Re: [cross-project-issues-dev] Simultaneous Release Page 2020-09Date: Wed, Sep 2, 2020 4:13 AM +1
 
Cheers
Martin
 
 
 
Am 28.08.2020 um 18:43 schrieb Wayne Beaton : 

It's not really up to me. 
 
I suppose that we could think of Eclipse JustJ as something that the package project pulls in, but it should IMHO have a proper place in the simultaneous release. It serves us well to include it (and not including it will lead to weird "what does it mean to be in the simultaneous release then anyway" sorts of discussions). FWIW (and more for other random observers, because I know that you know this), there's no rule that says that participating projects must contribute bits for the shared p2 repository.
 
So... since we're well past M1, I'll need Planning Council approval to add it. Can I get a couple of +1s from Planning Council members on this thread please?
 
For completeness, +1 from me (and as assumed +1 from Ed).
 
Wayne
  

On Fri, Aug 28, 2020 at 12:11 AM Ed Merks  wrote:
Wayne,
You may wish to add JustJ:
  https://projects.eclipse.org/projects/technology.justj/releases/1.0
While it is not in the release train p2 repo, it is incorporated into the Eclipse Installer and into three of the EPP packages.
Regards,Ed 
On 27.08.2020 20:50, Wayne Beaton wrote:
I've created the tracking page for 2020-09. Please have a look to ensure that I've correctly recorded your project's participation correctly.

 
In particular, please make sure that I have the version right. If I've made a mistake... please first make sure that you've created a release record for the right version and then let me know to update the tracking page to point to that version.
 
If you are contributing a new major or minor release and have not engaged in a release review since September 16/2019, then you need to submit your IP Log and connect with EMO ASAP to initiate the release review process. Note that you only need to submit your IP Log for review if you are required to engage in a release review. There's more information in the handbook.
 
Based on messages on this list, both Eclipse Corrosion, Eclipse EMFStore, and Eclipse Tools for Cloud Foundry (CFT) have dropped out, so they've been removed from the list. 
 
AFAICT, the corrosion.aggrcon file still exists and is not disabled. Also, since CFT has dropped out, its aggrcon file should also be removed (not just disabled). Can somebody take care of that, please?
 
Thanks for all your efforts.
 
Wayne
--
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-dev@eclipse.orgTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev___cross-project-issues-dev mailing listcross-project-issues-dev@eclipse.orgTo 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-dev@eclipse.orgTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
___cross-project-issues-dev mailing listcross-project-issues-dev@eclipse.orgTo unsubscribe from this list, visit https://www.eclipse.org/mailman/listinfo/cross-project-issues-dev
 

___
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] Simultaneous Release Page 2020-09

2020-09-02 Thread Martin Lippert 
+1

Cheers
Martin



> Am 28.08.2020 um 18:43 schrieb Wayne Beaton 
> :
> 
> It's not really up to me. 
> 
> I suppose that we could think of Eclipse JustJ as something that the package 
> project pulls in, but it should IMHO have a proper place in the simultaneous 
> release. It serves us well to include it (and not including it will lead to 
> weird "what does it mean to be in the simultaneous release then anyway" sorts 
> of discussions). FWIW (and more for other random observers, because I know 
> that you know this), there's no rule that says that participating projects 
> must contribute bits for the shared p2 repository.
> 
> So... since we're well past M1, I'll need Planning Council approval to add 
> it. Can I get a couple of +1s from Planning Council members on this thread 
> please?
> 
> For completeness, +1 from me (and as assumed +1 from Ed).
> 
> Wayne
> 
> 
> On Fri, Aug 28, 2020 at 12:11 AM Ed Merks  > wrote:
> Wayne,
> 
> You may wish to add JustJ:
> 
>   https://projects.eclipse.org/projects/technology.justj/releases/1.0 
> 
> While it is not in the release train p2 repo, it is incorporated into the 
> Eclipse Installer and into three of the EPP packages.
> 
> Regards,
> Ed
> 
> 
> On 27.08.2020 20:50, Wayne Beaton wrote:
>> I've created the tracking page for 2020-09 
>> . Please have a look to 
>> ensure that I've correctly recorded your project's participation correctly.
>> 
>> In particular, please make sure that I have the version right. If I've made 
>> a mistake... please first make sure that you've created a release record for 
>> the right version and then let me know to update the tracking page to point 
>> to that version.
>> 
>> If you are contributing a new major or minor release and have not engaged in 
>> a release review since September 16/2019, then you need to submit your IP 
>> Log and connect with EMO ASAP to initiate the release review process. Note 
>> that you only need to submit your IP Log for review if you are required to 
>> engage in a release review. There's more information in the handbook 
>> .
>> 
>> Based on messages on this list, both Eclipse Corrosion, Eclipse EMFStore, 
>> and Eclipse Tools for Cloud Foundry (CFT) have dropped out, so they've been 
>> removed from the list. 
>> 
>> AFAICT, the corrosion.aggrcon file still exists and is not disabled. Also, 
>> since CFT has dropped out, its aggrcon file should also be removed (not just 
>> disabled). Can somebody take care of that, please?
>> 
>> Thanks for all your efforts.
>> 
>> Wayne
>> -- 
>> 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 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 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] Simultaneous Release Page 2020-09

2020-09-02 Thread Mélanie Bats 

Hi,

Le 28/08/2020 à 18:43, Wayne Beaton a écrit :

So... since we're well past M1, I'll need Planning Council approval to 
add it. Can I get a couple of +1s from Planning Council members on this 
thread please?


For completeness, +1 from me (and as assumed +1 from Ed).


+1

Best regards,
--
Mélanie Bats
CTO
+33 7 87 69 42 84
+33 5 34 57 16 29
@melaniebats

*Obeo*
25 Boulevard Victor Hugo - Colomiers - France
http://www.obeo.fr
___
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] Corrosion dropping from SimRel

2020-09-02 Thread Mickael Istria 
On Tue, Sep 1, 2020 at 7:53 PM Wayne Beaton <
wayne.bea...@eclipse-foundation.org> wrote:

> Independent of this, according to my records, Eclipse Corrosion is overdue
> for a Release Review. Please initiate one immediately.
>

I've created
https://projects.eclipse.org/projects/tools.corrosion/releases/0.4.3
Cheers,
___
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