On Thu Oct 28 2010 04:31:41 GMT-0700 (PDT) webmas...@krackedpress.com wrote:
On 10/27/2010 08:39 PM, RA Brown wrote:
On Wed Oct 27 2010 17:05:23 GMT-0700 (PDT)  webmas...@krackedpress.com
wrote:
Who is now in charge of the code our volunteers contribute?
Who "owns" the rights to the code that is summited?  With only
Oracle employees in control of the "open source" code, is it truly
open or just open with what they want to share, even the code that
was provided by non-Oracle sources.
Due to agreements with the "community" developers Sun/Oracle has owned
the code from the start.  The "owner" of the trademark owns the code.

But with this new attitude with the council being made up of all employees,
are they going to share the code?  If a volunteer sends in a great piece of
code that makes it work better, does Oracle share the code or can they just
keep it for their "paid" version, if they continue that line of products
as well?

Because of the agreements Oracle can do as they wish. They are not required share the code with any of the forks.

If a volunteer developer of code sends in the code to Oracle under the
opinion
that it will be open source and shared, does Oracle still own the code
and can
keep it as their own, or does the developer have rights to share that
same code
to the other forks of OOo?  If a developer shares the code with Oracle,
then, because
it is shared, does the developer still have the rights to the code?  He
shared it
with Oracle under the GPL or other open source sharing options, so
Oracle should
not say they own the code.  They also would not have the rights to keep
the code
from the open source version of their office package.

My understanding is that the developer is free to share the code any way they want. They are not required to contribute only to Oracle.

Hope that explains thing a little.

Andy

---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@openoffice.org
For additional commands, e-mail: users-h...@openoffice.org

Reply via email to