On Thu, 2006-04-20 at 20:04 -0400, Paul W. Frields wrote:
On Thu, 2006-04-20 at 08:12 -0700, Karsten Wade wrote:
> On Thu, 2006-04-20 at 07:38 -0400, Paul W. Frields wrote:
> > Hi all Docsters,
> > 1. Who wants to take on the Account Setup Guide? Keep in mind you
> > won't have to do an awful lot of writing; it's mostly just collecting
> > written bits from the wiki, expanding them where needed, and making sure
> > everything flows nicely for an absolute newcomer.
> Edward Haddock started this already, from the angle of just trying to
> understand the sign-up process:
Excellent! Edward, if you're out there, my canvassing was not meant as
a slight, I simply forgot this was on the cooker already. Thanks for
stepping up to do this and -- if you have a chance -- let us know how
you're doing, and whether you could use any help.
No worries! Aloha all the same. :) I have been working on it a little.
I will paste here and you can look at it. As I said though, life has got
real busy lately. Also I am still on FC4 and haven't quite got the plan
finished to move to FC5. I only have the first section fleshed out a
1.) The first step in joining the Fedora Documentation Project is to
join the community and engage in the discussion. Subscribe to the
fedora-docs-list, fedora-dsco-list and fedora-announce-list to keep up
to date and informed about the project and Fedora in general. The links
can be found at
. After visiting
the pages and filling in the needed information an automated email
message will be sent. Choose to follow the link or respond to the email
as outlined in the instructions contained in the emails. Please note
that to be part of the Fedora Documentation Project you have to at a
minimum join the fedora-docs-list.
Next, ensure that the proper tool chain installed. The first tools that
should be installed are Yum and/or up2date. These Software Management
Utilities will ensure that all software packages are current and aid in
installing those not already installed. Both are installed by default on
Fedora Core 4 but this can be checked using rpm.
[xyz@xyz ~]$ rpm -qa up2date
[xyz@xyz ~]$ rpm -qa yum
Either package will work for managing software packages.
After that, setup Privacy Guard Software and utilities to manage the
Gpg keys. Use GPG to identify yourself and authenticate your
communications, even with people you don't know. GPG allows anyone
reading a GPG-signed email to verify its authorship. In other words, GPG
allows someone to be reasonably certain that communications signed by
you actually come from you. GPG is useful because it helps prevent
mischievous third parties from polluting code or conversations by
masquerading as other entities. To participate in any part of the Fedora
- you should have a GPG key pair, and
- your public key must be available on pgp.mit.edu
, a well-known public
1.) Subscribe to the fedora-docs-list, fedora-dsco-list and
a.) Visit the pages and filling in the needed information
b.) An automated email message will be sent
c.) Follow the link or respond to the email as outlined in the
instructions contained in the email
2.) Ensure that the proper tool chain installed
a.) Package Management
b.) Privacy Guard Software and Management Utilities.
III.) Docbook files
3.) Generate a GPG key and setup your email client
a.) Create a key Pair
b.) Post public key at pgp.mit.edu
c.) GPG key management utilities
III.) At the command line
d.) Setup email client to work with GPG
4.) Create a Bugzilla account(Red Hat)
a.) Fill out subscription page
b.) Receive email
c.) Respond to or follow link in email
d.) Account done
5.) Create a Fedora Project Account (Not the same as a Bugzilla
a.) Apply for an account
I.) Fill out Subscription page
II.) Receive an email
III.) Respond to or follow link in email
IV.) Account setup.
b.) Request and Complete a Contributor License Agreement(CLA)
I.) Form the accounts page click to have it emailed to the
account on file.
II.) Receive it and following the instructions in the email,
fill it out, sign it with your GPG key and return it.
III.) Get confirmation email. Done.
c.) Download and save the client-side certificate.
6.) Post a self-introduction to the fedora-docs-list
c.) Include Public GPG Key
> Edward -- if you want to write that up in plain text, OO.org
> whatever you are most comfortable with, another of us can convert it to
> XML and make it build with our toolchain. Then you'd have a good, XML
> reference source to continue work from. We can also generate a
> barebones outline in XML, with chapters sparsely populated with content
> ready to fill out, based on your outline.
Yeah, what he said!
> Just two moving-forward ideas. :)
> > 2. How can we make our toolchain do the majority of the work for the
> > CMS, like publishing and such? This is a more subtle question that
> > probably needs some batting around, and will require coordination with
> > Websites. Seth Vidal and I will help connect these dots, but folks here
> > are intimate with our toolchain and we should be prepared to come to the
> > table with some answers.
> Perhaps Elliot and Tommy's look at DIY on webtest.fedora might make the
> argument for Autobuild stronger or ...?
I don't have any experience with (or, frankly -- other than looking
through some of the intro/FAQ/doc pages -- knowledge of) this tool. But
certainly anything that would allow us to get our doc-building fingers
into all sort of presentation-layer pies is a Great Idea.
> > 3. It might be a good idea for us to start thinking about what docs
> > content is "faster-evolving" than we can or should keep up with in
> I'd like to see the Wiki graduate content into the CMS, just as it
> graduates contributors from the lower-level tools to the upper-level
> tools. This models the growing pattern we all have as writers, from
> basic content to more advanced content.
I couldn't agree more. The interesting thing about the CMS is that it
combines the easy idea-to-posting capability of a Wiki with some of the
security and workflow aspects that would help us ensure quality
documentation for all. I am just getting started using it so I'm sure
other people have a far better idea about how it all works.
fedora-docs-list mailing list