You seemed to have missed the point.
Ok, but I beg your pardon. As I'm not a native english speaker could you make clear, what the point is? (Ok, I guess I know)


What goes on the wiki is fine by
me. However, as I pointed out, the only editable stuff permitted on the
documentation project must follow the licensing set down by the CC. We
have managed to extend things to include non-editable files under other
licenses but only after much hassle. Thus, in the end, anything on the
wiki tends to be useless. So I ask again, please change the rules.
Please tell exactly, what rules you like to have changed - and if you like to have the CC vote on a change, please send a mail to [EMAIL PROTECTED] Please add some words *why* you like to change the rules. And why you consider the stuff att the wiki as useless. And - how a change of rules would change that?

Interesting discussion, and necessary, too. We need to look
at how we can make the wiki usable for documentation purposes
either by changing the licensing of the wiki or the docs.

Using wiki makes it so much easier to collaborate, particularly for
non-techie authors that it would be a wasted opportunity if we
would not make use of it.

The Sun docs group is currently evaluating how we can get dev
docs onto the ooo wiki, but we're focussing on the technical
side, not the legal side. I'll send a separate posting next week
with some updates and details.

I would like to learn about compatibilities and incompatibilities
of the two channels (doc.oo.o and ooowiki). If the legal status
of the wiki is undefined this should be changed. If docs licensing
is incompatible to wiki licensing this should be changed, too.
I'm gonna take a closer look at the licenses and ask around
to get a better idea what is possible and what is not.

We're shooting ourselves in the foot if we're unable to
set up a consistent licensing story.

Frank

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

Reply via email to