cvs commit: doc/en_US.ISO8859-1/articles/committers-guide article.sgml doc/en_US.ISO8859-1/articles/releng article.sgml doc/en_US.ISO8859-1/books/developers-handbook/policies chapter.sgml

Gabor PALI pgj at
Sun Aug 17 12:29:04 UTC 2008

Hiroki Sato wrote:
> moving only the team information into www does not agree with the 
> reason why we have article/contributors.

I see.  Well...  According to revision 1.1 [1] (by murray and nik):

"Combine parts of Chapter 21 and Appendix D from the FreeBSD Handbook
into a separate 'Contributors' article so that everything is in one
place.  This was done for various reasons :

  * This information is way out of scope for the Handbook.

  * When we talk about "Contributors" to FreeBSD or developed by "A
    large team of individuals" on the web site we can point the user
    to a complete document on our web page rather than two separate
    chapters in the Handbook.

  * We can create a plain-text 'CREDITS' file from this SGML and put
    it in /usr/share/misc or similar for all FreeBSD installs if that
    is desired."

It was full of outdated and out of synch information, but there is
always place for ideas for a better a documentation, I think.

> And in a long term, maybe we should merge www and doc into a single 
> repository (like www/en -> doc/en_US.ISO8859-1/htdocs or so) because 
> of making reuse of information easier.

I support it.  When do you think this process could be started?  Are
there any actual obstacles?

> what do you think about adding files including who it is on per
> developer basis? [..] Most of member descriptions of teams/hats can
> be generated from the files, and also the traditional first commit by
> a new committer can be simplified.

I am fond of this kind of approach ;)  For example, mentors could only
send a file like you attached to their mentees to fill up in advance.  I
would be happy to see something like this.

What do you think will be needed to implement this and get the ball rolling?



More information about the cvs-all mailing list