I think it's inevitable that more and more differences of opinion will
arise, so I also believe LO should start their own independent path.
Just my 2c, ;-)
Jaime
On Thu, Feb 24, 2011 at 16:51, Phil Hibbs wrote:
> Kohei:
> > That's the wrong assumption I was trying to point out. It's not alway
On Thu, 2011-02-24 at 15:51 +, Phil Hibbs wrote:
> Kohei:
> > That's the wrong assumption I was trying to point out. It's not always
> > applied as-is, and in fact it's rare that patches be accepted as is.
> > Even we don't do that too often.
>
> Nonetheless, saying "it's better for us if you
Kohei:
> That's the wrong assumption I was trying to point out. It's not always
> applied as-is, and in fact it's rare that patches be accepted as is.
> Even we don't do that too often.
Nonetheless, saying "it's better for us if you don't submit your
patches to OOo" is kind of like saying "Lets h
Plus,
On Fri, 2011-02-18 at 09:26 -0500, Kohei Yoshida wrote:
> > more work", given that this is going to happen anyway, and submitting
> > the bug fix to both projects will simplify things where OOo accept the
> > patch more or less as-is.
That's the wrong assumptio
On Fri, 2011-02-18 at 13:48 +, Phil Hibbs wrote:
> Kohei Yoshida:
> > So, as Michael says, I'm not a big fan of people submitting patches to
> > both projects. And yes, it will create extra work for us but not
> > necessarily for them since we pull their changes but they don't pull
> > ours.
>
Kohei Yoshida:
> So, as Michael says, I'm not a big fan of people submitting patches to
> both projects. And yes, it will create extra work for us but not
> necessarily for them since we pull their changes but they don't pull
> ours.
That's kind of like saying, "lets keep working on our project,
Hi Kohei,
Kohei Yoshida wrote (18-02-11 02:07)
On Thu, 2011-02-17 at 23:44 +0100, Cor Nouws wrote:
Reading Christophes question though, I see the route that people
contribute code both to LibreOffice and OpenOffice.org.
It is right that this (which indeed is perfect possible) will give extra
On Thu, 2011-02-17 at 23:44 +0100, Cor Nouws wrote:
> Hi Michael, *,
>
> Michael Meeks wrote (16-02-11 18:36)
> > This question prolly belongs best on the dev list.
> >
> > On Wed, 2011-02-16 at 15:28 +0100, Christophe Strobbe wrote:
> >> 1. Now imagine that I contribute code to LibreOffice an
Hi,
Christophe Strobbe wrote (16-02-11 15:28)
I have a question about licences and copyright.
[...]
These are important questions for developers who don't want to take
sides for or against OpenOffice.org or LibreOffice. If this has already
been clarified in a wiki somewhere, please let me know.
Hi Michael, *,
Michael Meeks wrote (16-02-11 18:36)
This question prolly belongs best on the dev list.
On Wed, 2011-02-16 at 15:28 +0100, Christophe Strobbe wrote:
1. Now imagine that I contribute code to LibreOffice and the
contribution is accepted. Is it then still acceptable (from a
Hi Christophe,
This question prolly belongs best on the dev list.
On Wed, 2011-02-16 at 15:28 +0100, Christophe Strobbe wrote:
> 1. Now imagine that I contribute code to LibreOffice and the
> contribution is accepted. Is it then still acceptable (from a
> copyright point of view) to sig
Hello Christophe,
Le Wed, 16 Feb 2011 15:28:43 +0100,
Christophe Strobbe a écrit :
> Hi,
>
> I have a question about licences and copyright. As many of you know,
> contributing code to the core of OpenOffice.org requires that one
> signs the Oracle Contributor Agreement [1] (which is identic
Hi Christophe,
On Wed, Feb 16, 2011 at 3:28 PM, Christophe Strobbe
wrote:
>
> 1. Now imagine that I contribute code to LibreOffice and the contribution is
> accepted. Is it then still acceptable (from a copyright point of view) to
> sign the Oracle Contributor Agreement and submit the same code t
Hi,
I have a question about licences and copyright. As many of you know,
contributing code to the core of OpenOffice.org requires that one
signs the Oracle Contributor Agreement [1] (which is identical to the
Sun Contributor Agreement). Extensions are exempt from this [2].
1. Now imagine tha
14 matches
Mail list logo
