Hi,

>> What do you think?
>> 
>> Regards,
>> Vailton Renato
> 
> Nice !
> Two questions comes to mind...
> 
> 2) What would be the methodology to update harbour/doc files in a 
> collaborative way ?

They should be committed to SVN just like code changes. 
Either directly by authors (if they have R/W access) or 
by someone who aggregates the work of certain authors. 
If there is any volunteer for this aggregation task we 
can grant R/W access, if other admins also agree.

If this is to cumbersome for a start, we may simply gather 
.txt files somewhere, and commit them from time to time 
to SVN.

> I've done a searh for hb_ functions only on harbour tree and I got 888 
> ocurrences. And we are talking about harbour extensions alone.
> So there must be a way to divide tasks among many volunteers and a DocMaster 
> reviewing and aproving submitted documents.
> This DocMaster need not only excelent English languaje skills but also deep 
> knowledge of Harbour internals and some ability to read C code.

Since we don't appear to have a Doc Master at the moment, 
and I wouldn't really block any documentation effort by 
looking for one, I think the process just has to be 
started. "Who starts with which section?" is enough to 
decide at this point.

As for a (non-visual!) "style" guideline for the docs,
I think it's just perfect if we follow the path of 
Hannes Ziegler with xhb and Xbase++ docs.

my 2 cents, that is.

Brgds,
Viktor

_______________________________________________
Harbour mailing list (attachment size limit: 40KB)
Harbour@harbour-project.org
http://lists.harbour-project.org/mailman/listinfo/harbour

Reply via email to