On Wed, 2005-03-30 at 21:18 -0800, Rahul Sundaram wrote: > Hi > > > * I hope the gpg key isn't a bad hurdle for writers > > and editors who are > > new to open source projects. > > It wouldnt be if the process of gpg key generation is > documented or an external link is provided on the > exact steps including the specific path where the key > is stored What?!? Don't make them google for it, like I have to every time? Well, kind fella that he is, Paul is writing something up on the Wiki, if my adding him to the EditGroup worked as predicted. My thinking, fwiw, is that it's OK to have small hurdles that people have to think in order to overcome, if they don't have the knowledge already. It's like having to register your nick on irc.freenode.net before gaining voice on #fedora. The steps are all right there in the welcome message, if you can't follow those instructions, you definitely won't be able to follow the help you receive on #fedora. I just wanted to be sure we weren't excluding potential writers because of too high barriers. This is why I appreciate the volunteering to DocBookalize submissions from non-DocBook using authors, with the understanding they will do the work to learn how to maintain it. - Karsten -- Karsten Wade, RHCE * Sr. Tech Writer * http://people.redhat.com/kwade/ gpg fingerprint: 2680 DBFD D968 3141 0115 5F1B D992 0E06 AD0E 0C41 Red Hat SELinux Guide http://www.redhat.com/docs/manuals/enterprise/RHEL-4-Manual/selinux-guide/
Attachment:
signature.asc
Description: This is a digitally signed message part
