Re: [native-lang] IRC Talk starts now!!

Andre Schnabel wrote:

> Hi,
> 
> ....
> 
>>
>> The reason is simple for me. If I write documentation that can't be 
>> put on the community site, I'm working for OOo the product, but not 
>> for OOo the community. It's a choice and that doesn't minus the work 
>> done.
> 
> 
> That's my "reason" to see OOoAuthors as a fork. I couldn't argue with 
> Daniel on that issue, as I've not been involved in the discussion about 
> the license change.

This is not to argue, this is a simple choice he has made.
If we need a tool for the documentation project, so we make it 
compatible with our work flow and our licences.

> 
>> The fork is when you settled first your project using the PDL (see 
>> april 2004 mails in doc projects) then change it to CC and when you 
>> try to keep the 'in place' community or the new members wishing to 
>> participate out and drive them systematically to your project 
>> (whatever the topic of the participation and this almost every day).
> 
> 
> As said: rading the Chatlog, OOoAuthors does not enforce any particular 
> license. Nail them on that.
> (And yes, I know, there is confusion about that .. but I this has to be 
> discussed and may be resolved in some cases)

Yes, and believe me, I know how licence is important, when your 
contributors are in difficulty because of the licence, you pay more 
attention to it and how they are protected.

[...]

> 
> See that one for my opinion:
> http://qa.openoffice.org/issues/show_bug.cgi?id=8331

oh, I didn't know !
> 
> (I spent days for the translation only to find out, nobody at the 
> documentation proejct was interested in publishing it)

I can understand it :(
> 
>> I won't tell you that because I'm aware also for a long time of the 
>> issues meeting by the documentation project. Scott and Ger should be 
>> in that discussion BTW.
> 
> 
> Absolutely ... *sigh* I'll join the dev@doc lists again ;-)

The best to work on an issue is to jump in it ;)
> 
>> The same will happen with scripting if we don't take care to keep it 
>> inside the project. Why is it important to have it in OOo community ? 
>> because it brings value to the community, it brings people to 
>> participate and it's much more easier for the NLC to have all in one 
>> place, and at the end, it brings credibility to our project.
> 
> 
> If you define "OOo community" as "all who strictly work with OOo 
> website", we will make many people upset.

Working in the OOo community force you to respect a lot of things, this 
is not easy, sometimes very tiring and iritating, but I can say that lot 
of things are getting better this is why may be I'm still here :)

And if you prefer I'll use community contributors ;)Why, because when 
working in a project you don't do only what you like to do, but you work 
for the sake of the project. Says for example Marketing people should 
work on RFEs consolidation and 3.0 features set, and marketing guides, 
templates for presentation, flyers, and so on. As far as I can see, it's 
only very very few people working here and most of the time not 
belonging to marketing :(.
For doc project the emergency now is the install guide, we even don't 
know if it will ship with OOo and if yes what is the deadline for it. 
Ger get no help for consolidation of the master, that won't allow other 
projects to work on a translation in reasonable time frame. Their is a 
lot of items to add to the OLH, a list of them is on the doc project, 
this is also documentation work that have to be done.
More anonymous are QA contributors but the work they do is fabulous, 
they are great contributors because with their work the project is going 
really further. So it's not about working with OOo website, it's about 
pushing things to make the project and the product better who ever you 
are and the responsabilities you endorse.

> Anyway .. there is still the problem of the license, that makes it 
> impossible to contribute editable content from OOoAuthors (2.0 users 
> guide) to OOo Website.

Yes, but it's not a problem if OOoAuthors admit that it's not the OOo 
documentation development project, it's not a question of content or 
value. You make your choice to be part of the OOo project or not. When 
contributors come to the project and don't accept the PDL, they put 
their documentation elsewhere and you put the link to it on our site, 
that's all. See Dmaths for example they use GPL, they cant'be part of 
OOo project, anyway I promote their tool at each conf or events we do, I 
even print flyers for them.

Kind regards
Sophie



-- 
No virus found in this outgoing message.
Checked by AVG Anti-Virus.
Version: 7.0.323 / Virus Database: 267.8.16/50 - Release Date: 15/07/2005