On Mon, 2006-09-04 at 12:26 +0200, Charles Schulz wrote:
> Hello Kai,
> 
> thank you for your points: indeed, art and/or multimedia content is not
> the same thing as software, this we knew.

Content in general is not software and is more appropriately licensed
with CC or similar. Everything on the INGOT web site is CC share-a-like
if its content. We have some programs so they are GPL. I can't see why
the same separation can't be done with OOo. The code is LGPL, content
and support data is CC. We could even set up a range of OOo products by
combining OOo with other open content. eg OOo distributed with the text
of all the books in the Gutenberg project. Ok you can get it from the
internet but what about people in say developing countries without an
internet connection? Add value in niche markets and get a wide range of
volunteers to support these through their individual interests - that is
the bazaar model.

> > btw. I think Chad is on the right track with the FOSS thing. Treating
> > forks well, be they small or big, is the sign of a wise project.

> Except that OOo premium is not a fork. Except that Kami is part of our
> community. 

I think the broader point he is making is that the over-arching goal is
proliferation of OOo, not who "owns" or controls what. Assume that
people with ideas are supportive rather than malevolent and help them
achieve their goals. Only intervene if its something illegal and then
try and fix that specific problem rather than throwing the baby out with
the bath water.

> You do remember that I was complaining about an article, not
> about OOo Premium? Fortunately, this thread may offer us the opportunity
> to fix the "OOo premium" problem and get the bundle or part of the
> bundle inside OOo.

Let's hope so. An even more significant win would be to ensure that this
type of confusion doesn't arise again.  

Ian
-- 
www.theINGOTS.org
www.schoolforge.org.uk
www.opendocumentfellowship.org

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to