Hi Peter
If your model works directly with the Product, the flexibility of the
Permissive license can be the stronger choice.
I do not believe that a lot of people understand this.
Can you elaborate on this point? I don't really see how using a
copyleftless license is better when your busines
Hello Everyone
This email is to tell you about ASF participation at FOSDEM. The event
will be held in Brussels on 4^th & 5^th February 2017 and we are hoping
that many people from our ASF projects will be there.
https://fosdem.org/2017/
Attending FOSDEM is completely free and the ASF will ag
See this mail: http://legal-discuss.markmail.org/thread/mleqsm636zf5fqia
2017-01-12 6:18 GMT+09:00 Dave :
> On 11.01.2017 09:44, Patricia Shanahan wrote:
> > On 1/10/2017 11:29 PM, Nagy �kos wrote:
> >> Hi,
> >>
> >> it is impossible, because the LO license is LGPL+MPL, that can't be
> >> merged
https://www.openoffice.org/licenses/lgpl_license.html
Based on this page, OpenOffice change the license from LGPLv3 to Apache
2.0 only when Oracle donate the code to Apache Foundation in june 2011,
but LibreOffice was forked from OOo in september 2010.
An article about this:
http://www.zdnet.com/a
Is the past on topic for the future?
Is a dogmatist a good pontifex?
Regards
Michael
signature.asc
Description: OpenPGP digital signature
Nagy,
I'm a simple user so the code base and license are completely irrelevant to
me. What IS relevant is the way the software works. So, please, can you
tell me half a dozen things that LO can do that OO cannot do?
I recently was given a 30,000 row excel sheet to read into a database so
that I
On 12.01.2017 16:54, RA Stehmann wrote:
> Is the past on topic for the future?
Assuming that you are responding to my post in this thread, the answer
to your question is no. My post was nothing more than a simple
correction of Patricia's seemingly mistaken idea that the original LO
code came from
Thanks for the correction.
On 1/12/2017 7:38 AM, Nagy Ákos wrote:
https://www.openoffice.org/licenses/lgpl_license.html
Based on this page, OpenOffice change the license from LGPLv3 to Apache
2.0 only when Oracle donate the code to Apache Foundation in june 2011,
but LibreOffice was forked from
Please correct the specific non Apache licenses if I get them wrong. As far as
I know the sequence of events is:
Oracle buys Sun including OpenOffice (closed license) and the open source
OpenOffice.org (GPL2).
TheDocumentFoundation forms and forks OpenOffice.org as LibreOffice under GPL2
Oracl
Hi Dave, all.
On 12 Jan 2017 22:50, "Dave Fisher" wrote:
Please correct the specific non Apache licenses if I get them wrong. As far
as I know the sequence of events is:
OpenOffice.org was originally dual licensed under LGPLv2 and SISSL (OSI
approved but now retired). With v3 we changed the li
On Wed, Jan 11, 2017 at 10:38 AM, Dr. Michael Stehmann
wrote:
> Hello,
>
> this discussion is really useless. We have to do more urgend tasks yet.
>
> If TDF people want to talk with us, they know where to find us. And vice
> versa.
>
> We have talked a lot in the past. But at the moment I can not
On 12 January 2017 at 18:29, Simon Phipps wrote:
> S.
> (speaking here only as an AOO community member)
Thanks, Simon. I have long desired for there to be a useful confluence
and even convergence of code, effort, vision--I mean between LO and
AOO. Would still be nice, if only for the sake of larg
Am 12.01.2017 um 19:21 schrieb Dave:
> On 12.01.2017 16:54, RA Stehmann wrote:
>> Is the past on topic for the future?
>
> Assuming that you are responding to my post in this thread,
I do not want to answer to your post, but the questions are caused by
the post of Nagy Ákos some minutes before.
Am 13.01.2017 um 01:26 schrieb Simos Xenitellis:
>
> There is the standing issue with the old www.openoffice.org
> that has been repurposed as the front page for Apache OpenOffice.
>
> I would expect that the historical hostname "www.openoffice.org" to simply
> show
> a list of OpenOffice.org-b
I will answer later today, I hope. Sorry for the delay.
Pedro schrieb am Do., 12. Jan. 2017, 11:01:
> Hi Peter
>
> > If your model works directly with the Product, the flexibility of the
> > Permissive license can be the stronger choice.
> > I do not believe that a lot of people understand this.
15 matches
Mail list logo