Am Mon, 12 Oct 2009 12:31:10 +0900
schrieb JiHui Choi <[email protected]>:

> I have some questions about the license. If you help me or introduce
> me someone who can help me, I'll really appreciate to you. :)
Please be advised we cant give you legal advise.

> 1. and 2.
Please ask only questions related to OOo on this list. Crossposting to
KDE, Gnome, Mozilla and OOo is no good idea, as all lists are likely
high volume and answers might be project specific.

> 3. Can I publish and share my glossary under GPL? If I can, which
> version should I use, v3.0 or v2.0? There are several licenses, for
> GNOME, KDE and GIMP are GPL, LGPL for OpenOffice, Firefox has MPL and
> BSD for Launchpad. I wonder whether I can mix all these licenses and
> publish under a specific license such as GPL.
>
> I'd like to share my works under GPL or similar it and works with
> many people. However, before that I think I should make to be clear
> about the license. Here is my demo. http://gloss.mr-dust.pe.kr/

Here is a starting point:
http://www.openoffice.org/FAQs/faq-licensing.html
   3.  Which license should I use?

      That depends on what you want to do. If you wish for your code
      submissions to be included in the product, you must sign the Sun
      Microsystems Inc. Contributor Agreement (SCA) (see below); the
      license in effect is the LGPL for code. If you wish for your work
      to be used outside of any product (say, as website FAQ), then you
      may use the PDL. The usage of the source license differs from
      that of the PDL. To apply a source license, you must fill out and
      sign a Sun Microsystems Inc. Contributor Agreement (SCA). You
      only need to do this once. To apply the PDL, on the other hand,
      you must attach a copy of the license to each modifiable document
      covered by that license. Please see the section below on the use
      of the PDL.


Best Regards,

Bjoern Michaelsen


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to