Repos being created with wrong license?

36 views
Skip to first unread message

John D. Ament

unread,
Apr 26, 2017, 9:27:27 AM4/26/17
to MicroProfile
I just noticed that the Health Check repo is up, however its marked with an EPL. Is that an infra thing, or should they be creating our repos with the Apache license?


John

Werner Keil

unread,
Apr 26, 2017, 12:45:26 PM4/26/17
to MicroProfile
Sure nothing was forgotten in the Bugzilla ticket?

Werner

Werner Keil

unread,
Apr 26, 2017, 12:53:31 PM4/26/17
to MicroProfile
The license certainly was not mentioned in https://bugs.eclipse.org/bugs/show_bug.cgi?id=515731

Guess every project that deviates from the default license should do that....

Ondrej Mihályi

unread,
Apr 26, 2017, 4:24:52 PM4/26/17
to MicroProfile
I guess Eclipse used a standard template for a new repo.

We should change it to use our agreed standard, it's just a matter of committing these changes:
 - LICENSE file - Apache v2
 - NOTICE file - listing all contributors
 - each file should have a standard header

See the License section in the Wiki: https://wiki.eclipse.org/ContributingGuidelines
See the config repo for an example: https://github.com/eclipse/microprofile-config

--Ondrej

Dňa streda, 26. apríla 2017 18:53:31 UTC+2 Werner Keil napísal(-a):

Emily Jiang

unread,
Apr 26, 2017, 4:53:54 PM4/26/17
to MicroProfile
I submitted a bugzilla for creating microprofile-fault-tolerance repo with the comment to say using Apache v2 license. Let's wait and see whether this is sufficient .

Emily

Werner Keil

unread,
Apr 27, 2017, 9:35:37 AM4/27/17
to MicroProfile
Ondrey, 

It seems you or whoever created the page https://wiki.eclipse.org/ContributingGuidelines did it on the wrong level of the Eclipse Wiki.
The page is totally specific to MicroProfile, yet its URL makes the impression it was a Contribution Guideline for EVERY Eclipse project.


Werner

Heiko Braun

unread,
Apr 27, 2017, 3:34:52 PM4/27/17
to MicroProfile
I did request the repository, but wan't aware that we need to request a specific License. To be honest, I expected an empty repository. 
Can we simply replace that license file, or does it require more ceremony?

Mark Struberg

unread,
Apr 28, 2017, 3:23:35 AM4/28/17
to MicroProfile
Is the repo already filled and where did the sources came from? And what license did the actual sources use?
The license of the original sources is the binding one.

Heiko Braun

unread,
Apr 28, 2017, 10:34:23 AM4/28/17
to MicroProfile
When the Support from Eclipse created the repo it contained an EPL. Lust the LICENSE file, nothing more. I am going to replace it with the ASL one.

Werner Keil

unread,
Apr 28, 2017, 7:36:14 PM4/28/17
to MicroProfile
I suppose there is no derived work here that would already have a license, otherwise these licenses should also be mentioned or an appropriate NOTICE file point to where these came from.

I fixed Ondrej's mishap in the Wiki
And asked the Webmasters to delete the old empty one on the top level.

Kevin Sutter

unread,
May 2, 2017, 11:58:44 AM5/2/17
to MicroProfile
+1
Reply all
Reply to author
Forward
0 new messages