Hi Laurent, all,
Laurent Godard wrote:
Hi sophie


+1 From several discussions and threads that I remind, this was not the topic. But adding new articles was the concern.


adding to something non-free ? no
write new ones, yes

The last discussion I remember (it was between Rene and Juergen) Juergen said that Sun was evaluating open sourcing the guide. The concern they had was more about maintaining the 1200 pages than freeing it.

- provide translation of code source of the devGuide on the wiki into new languages (Basic, Python) in our own licence provided we're allowed to ...some info on this ?

you're always allowed to provide new material on another licence. The concern is how this will be integrated, and how this will be interacting with the already existing material. From what I remember of all the discussions about the dev guide, this came out about adding new articles or rewriting existing articles. The purpose was not about rewriting from scratch.


don't expect people widely contributing on something non-free

Frank and Juergen said that the licence will be open sourced (I only hope that it will take less time than for the OLH ;-)

- populate the extensions wiki ! a lot or redactionnal is here needed
 http://wiki.services.openoffice.org/wiki/Extensions_development

I've done my best ;-)


thanks i'll have a look
btw, i'll call on [EMAIL PROTECTED] for more help

The issue is that even in the NLC, people available have not the extensible time they would like and you would need. Imho, at this point, there is some marketing actions needed to populate your project. So cc John ;-)

NLC are not leads only
they must relay the massage to their doc community
i'll do for french but can't for other nlc

I was not speaking about leads only, but from my experience, there is very few people that are contributing on a regular basis in the NLC communities and you'll find most of the time always the same people :-)

Kind regards
Sophie

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

Reply via email to