Re: [orion-dev] Orion license

[John Arthorne <John_Arthorne@xxxxxxxxxx>]

Don't worry, I wouldn't dream of coming
up with a new format. It's worth thinking about what legal info should
appear at the root of eclipse.org git repositories since this seems to
be a common convention, but I'll bring that topic up in another venue.
Something more like the Eclipse SUA might be the right answer here.

John




From:      
 Mike Milinkovich <mike.milinkovich@xxxxxxxxxxx>
To:      
 John Arthorne/Ottawa/IBM@IBMCA,

Cc:      
 Orion developer discussions
<orion-dev@xxxxxxxxxxx>
Date:      
 04/12/2013 09:33 AM
Subject:    
   Re: [orion-dev]
Orion license

---

John,

I am pretty sure that the file header format that you
chose is consistent with other dual-licensed projects. It is JGit which
is the outlier, as it is our only BSD-only project. 

Regarding your mention of a LICENSE.md: if by that you
mean a copy of the text of either the EPL or the SUA in Markdown, please
don't. Or at least please don't without the full involvement of the EMO.
We have to sign off on any new formats of the license materials, because
lawyers say that that formatting matters. Apparently their ability to parse
white space is not as good as ours :)

If anyone thinks that Markdown versions of our licensing
materials are necessary, please open a bug and assign it to me. 

Mike Milinkovich
+1.613.220.3223
mike.milinkovich@xxxxxxxxxxx

On 2013-04-12, at 9:12 AM, John Arthorne <John_Arthorne@xxxxxxxxxx>
wrote:

Since we are dual-licensed, it wasn't
practical to include the entire EDL text in each header. You can copy the
template from an existing orion client source file, or there is one documented
here: 

http://wiki.eclipse.org/Orion/Coding_conventions#Copyrights

The license information is included in the README.md at the root of each
repository. I suppose we could also have a LICENSE.md but I hate duplicating
the information in various places. I actually think the info in README.md
needs a bit of work, since there are always various exceptions documented
in about.html, etc. It should probably say license is EPL+EDL unless stated
otherwise in the source file or something to that effect.


John 




From:        Matthias
Sohn <matthias.sohn@xxxxxxxxx>
To:        Mike
Milinkovich <mike.milinkovich@xxxxxxxxxxx>,
Orion developer discussions <orion-dev@xxxxxxxxxxx>,
Date:        04/10/2013
06:39 PM 
Subject:        Re:
[orion-dev] Orion license 
Sent by:        orion-dev-bounces@xxxxxxxxxxx

---

On Thu, Apr 11, 2013 at 12:28 AM, Mike Milinkovich <mike.milinkovich@xxxxxxxxxxx>
wrote: 
Matthias,

 

As I recall, the client side has been dual licensed and there are discussions about dual licensing the server going forward.

 

But your comment that the orion.client sources indicate EPL only seems incorrect. From my orionhub account, I can quickly see that the fileheader in org.eclipse.orion.client.editor/web/orion/textview/textView.js is as follows. It clearly states that the file is dual licensed (emphasis mine). I’m not sure why your experience is different.

yes, this helps.  

I didn't spot this small addition in the client sources which are indeed mentioning EDL
and providing a link to the full license text.

I was expecting to see the explicit EDL header as we were told to use in JGit sources
which are EDL only. This looks very different since it's a lot longer.

I'll adapt the license header for the client part of my first contribution [1] accordingly ;-)

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=399023

--
Matthias
_______________________________________________
orion-dev mailing list
orion-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orion-dev