> > > It can be better than one Wiki, but I think that we need a on-line version that > > > the people can read the newest modifications. Because If only a group, or one > > > person, works in this job the manual could turn boring and discourage people to > > > send fixes. I think that we need most people possible > > > > > > > thats what CVS usually is for. When its software, its all the > > experimental updates being worked on, some good, some currently > > broken, so the same applies to software for the human mind as well. > > Using a wiki when you already have CVS to do that is redundant, and > > pointless when as said before, a wiki is less secure to people > > meddling and putting false information in. You can track who made > > what changes with CVS with very fine detail. > > > > but nor all have CVS and to send something to a cvs server you need a acount, and > this will turn the simple fact to send a fix so complex that the people go to give > up to fix, if had not liked the ideia of Wiki, that such one list of e-mails? or any > another way where anyone can help, and that be simple.
make an anonymous buffer where someone can submit a revision to CVS pending a review from some admin. give that person a unique tag so that if they want to submit something else, or apply for an account several submissions down the road, all the anonymous submissions can be credited to the new account. (in theory this could be applied to any CVS, but with computer software, it takes alot of effort for the admin to verify each anonymous submission) _______________________________________________ Bug-hurd mailing list [EMAIL PROTECTED] http://lists.gnu.org/mailman/listinfo/bug-hurd
