On 2/23/2010 1:01 PM, Simon Wilkinson wrote: >> For Unix this would result in easy access to the information from all >> man pages. > > This isn't the kind of material that would traditionally appear in a manpage, > certainly not with the kind of verbosity you are suggesting (our contributors > list, alone, is over 200 names). There's a tradition on Linux and some other > systems of putting this kind of information, along with a copy of the > license, into /usr/share/doc/. I'm not against having a manpage, but I do > think that something along these lines would be more in keeping.
The rationale for this being part of the Reference Manual (aka manpages on Unix) is that this document is installed on all systems and published on the web site. If there is consensus that using a man page would be inappropriate, I am not opposed to generating a new document. Looking at the contents of some /usr/doc/<project>/ directories, I often see separate text only files for AUTHORS, CHANGELOG, COPYING or LICENSE, INSTALL, NEWS, README, etc. We could certainly do the same or install .html and .pdf versions of the documentation files which could include the same contents. > I also think that improving our crediting of contributors ... We have tried to maintain the contributors list on openafs.org/credits.html. This is however a very manual process. Note that the web site is now maintained in git. Any contributor that notices they are not on the credits.html is welcome to submit a patchset to correct the oversight. We might also want to add a link to https://www.ohloh.net/p/openafs/contributors which generates a list from the Git repository contents. > > We also badly need to come up with some kind of statement on adding copyright > messages to source code files. ... While I do not disagree that improvements can be made in this area I think it is off topic for this discussion thread. Jeffrey Altman
smime.p7s
Description: S/MIME Cryptographic Signature
