Self-Introduction: Thomas R. Jones
by Thomas Jones
Full Legal Name::
Thomas Riley Jones Jr.
City, State::
Bowling Green, Kentucky
Profession::
Security Analyst
Company::
Weyerhaeuser
Goals::
What do I want to write about?:
Information security, kernel, and/or networking related topics.
What other documentation do I want to see published?:
I am not very particular as long as it is contains correct content and meets
the needs of end-users.
Do I want to edit for grammar/writing and/or technical accuracy?:
I have edited and reviewed various Linux documentation. Currently, I am a
technical reviewer for a new book entitled "GnuPG for the desperate" due
from the No Starch Press publishing entity. I am open to editing and/or
technical editor of topics within my skillset.
Anything else special?:
Member of the IEEE Information Assurance Task Force
Member of the IEEE Security and Privacy Technical Committee
I formerly was the administrator of the Linux-Howtos.com domain.
Historical qualifications::
What other projects or writing have I worked on in the past?:
Security Document Initiative - (extracted from my website
http://www.buddhalinux.com)
"The Security Document Initiative is an implementation of the domain of
applied cryptography as it relates to an XML defined and regulated security
mechanism and the creation of a security infrastructure to protect
information systems and resources."
Osiris Host Integrity System.
SuSE FAQ.
Numerous Linux Howtos now maintained by the LDP.
What level and type of computer skills do I have?:
Experienced Administrator. Career direction into a variety of XML applications
and their use in a security application.
What other skills do I have that might be applicable?:
5 years experience in bash programming.
Developed numerous init scripts for the SuSE Linux distribution.
C++ development experience.
What makes me an excellent match for the project?:
I have almost 3 years XML/Docbook experience; and have a great desire to help
the Linux, Fedora, and Open Source community. I believe whole-heartedly in
the Open Source Initiative and advocate its utilization in all aspects of
computing.
GPG KEYID and fingerprint::
pub 1024D/57BF9042 2004-12-26 Thomas Jones (The Buddha Linux Group)
<adminATbuddhalinux.com>
Key fingerprint = 5264 BCA1 6059 57A8 58E5 7F04 A11E 5C13 57BF 9042
uid Thomas R. Jones (IEEE Computer Society Account)
<thomasjonesATcomputer.org>
uid Thomas Jones (The Buddha Linux Group)
<adminATbuddhalinux.org>
sub 1024g/5EDEFE5D 2004-12-26
As you can see I am heavily oriented towards the security aspect of Fedora.
But, I would be more than happy to author and/or review any topic if
requested.
Thank for your time and look forward working with all of you.
Thomas Jones
18 years, 12 months
Self-Introduction: Eric Jon Rostetter
by Eric Rostetter
1. Full legal name
Eric Jon Rostetter
2. City, Country
Austin, Texas, USA
3. Profession or Student status
Computer Programmer, Full Time
4. Company or School
Department of Physics, The University of Texas at Austin
5. Your goals in the Fedora Project
* What do you want to write about?
What ever strikes my fancy, if anything.
* What other documentation do you want to see published?
As much as possible.
* Do you want to edit for grammar/writing and/or technical accuracy?
Sure, why not. I'm great at picking nits.
* Anything else special?
I really want to help co-ordinate Fedora Docs Project with the
Fedora Legacy Project. I'm manage the web site and docs for the
Fedora Legacy Project. I'd like to make the two groups work together
to the benefit of both.
6. Historical qualifications
* What other projects or writing have you worked on in the past?
I work with the Horde Project (www.horde.org)
(docs, faq, programming, etc)
I work with the Fedora Legacy Project (wwww.fedoralegacy.org)
(web, docs, QA, etc)
We run a "Homework Service" here at UT Austin.
I help maintain the departmental web server and my groups web pages
here in the Physics Department (www.ph.utexas.edu).
Used to work on many other projects in a previous life many moons ago
(Minitab, NBS Pascal Compiler, VMS Ted/Sed editor, etc).
* What level and type of computer skills do you have?
Can write decent docs. Can do web pages, including html, php, xml/xslt,
javascript. Do the usual programming and system admin stuff.
* What other skills do you have that might be applicable? User interface
design, other so-called soft skills (people skills), programming, etc.
See above.
* What makes you an excellent match for the project?
My participation in the Fedora Legacy Project, and my desire to help
the two projects co-ordinate docs between them, transition docs from
one to another, etc.
7. GPG KEYID and fingerprint
pub 1024D/49C7A0F2 2004-02-06 Eric Jon Rostetter <rostetter@xxxxxxxxxxxxxxx>
Key fingerprint = E4E7 E674 2BCA 14CC 54CF 13C9 E236 516E 49C7 A0F2
sub 1024g/BBFD8C0C 2004-02-06
--
Eric Rostetter
18 years, 12 months
Self Introduction: Gareth Russell
by Gareth Russell
Hey folks,
I decided that it was about time I got involved with the documentation
project so here's my introduction:
1. Full Legal Name:
Gareth Thomas Russell
2. Country, City:
England, Nottingham (University) OR England, Rural Suffolk (Home)
3. Profession or Student status:
1st Year Politics BA at the University of Nottingham
(http://www.nottingham.ac.uk/)
4. Company or School
University of Nottingham
5. Your Goals in the Fedora Project
- Comprehensive range of detailed easy to follow documentation.
- Attract more users to Fedora
- Help those less fortunate than myself, i.e. newbies
Do you want to edit for grammar/writing and/or technical accuracy? Yes
6. Historical Qualifications
- What other projects have you worked on in the past?
I'm an Administrator of FedoraForum.org.
I've written several articles for OSDir.com and MadPenguin.org
I've contributed to the FedoraFAQ (http://www.fedorafaq.org/)
- What computer languages and skills do you know?
Not really a programmer. But am quite skilled with general linux
administration.
- Why should we trust you?
I'm already involved in the fedora community via the running of
FedoraForum.org and have been for the last 15 months.
7. GPG KEYID and Fingerprint.
My KeyID is: A126ED91
My fingerprint is: 93CA 9DB3 4A08 3CDA 113B 3076 4178 3862 A126 ED91
It expires 2007-04-24
Well, thats it for now.
--
Gareth Russell http://www.fedoraforum.org/
gpg fingerprint: 93CA 9DB3 4A08 3CDA 113B 3076 4178 3862 A126 ED91
19 years
Random "Topics" Question
by tuxxer
I was checking out the list of "ideas without owners" to see if there
was anything that I could pick up. I didn't see anything without an
owner in the attachment Tammy put in there many moons ago. Are the
subjects listed there actively being worked on by the people to whom
they've been assigned? Or have they been abandoned?
-Charlie
--
-tuxxer
gpg: 57EB F948 76AE 25BC E340 EFA9 FAF6 E1AC F1E1 1EA1
19 years
Self Introduction: Rahul Sundaram
by Rahul Sundaram
Hi
Sorry for the delay in getting this done....
Rahul Sundaram
Pune, India
Red Hat
Your goals in the Fedora Project
* Task oriented documentation in doing typical
stuff on Fedora
* Desperate to see the Installation guide and other
basic documentation completed before the release of FC4
* Do you want to edit for grammar/writing and/or
technical accuracy? yes
* Some videos in ogg theora format might be a
interesting thing to try inorder to target non technical users
Historical qualifications
* Linux documentation project (tldp.org) and small
help in various other projects
* Not into programming currently but I consider
myself to fairly knowledgeable in Linux
* An active volunteer in LDP, wrote the LDP FAQ and
few other docs and been reviewing a good number of documents in the list
and taking part in all kinds of discusions there
pub 1024D/1A24E6F3 2005-04-24 Rahul Sundaram (IRC nick: mether)
<sundaram(a)redhat.com>
Key fingerprint = 829A 1929 4F62 97DD D393 2ED4 E5DF BD66 1A24 E6F3
sub 1024g/9BD8985F 2005-04-24 [expires: 2006-04-24]
regards
Rahul
19 years
why o why
by gaurav
Hi List,
I was wondering why this documentation submition process is
overly complex...why don t we we use some wiki like tikiwiki or media
wiki (of webopedia fame) to manage documents ...why I am required to
submit docs in docbook xml format ....and check into cvs ....then built
it .....,most wiki system have have built in work flow, revision
mechanism, doc conversion to pdf and tons of other stuff etc
...........what is the requirement or need for such complexity ...
Regards,
Gaurav
19 years
getting started (false start 1 of ?)
by Duncan Lithgow
Hi all
I've just started reading the 'Fedora Project Documentation Guide' and
have some comments on it. Are the people who edit that document on this
list and tuned in?
As a newbie I'm trying to document some of my problems as I go, and I
want to use docbook for other projects. I'm familiar with XMLMind but
can't get anything working on fc3 to write/edit DocBook.
The first page of 'Fedora Project Documentation Guide' doesn't help me
at all. It first refers to 3 files I can get through yum (xmlto —
docbook-style-xsl — docbook-dtds) and then jumps into checking things
out of cvs.
So, on the very first page fedora docs has lost me.
I need two types of help
1. getting going with DocBook
2. who to talk to to make the docs newbie friendly
Duncan
19 years
All formats
by Karsten Wade
Yes, we are working on fixing the Doc Guide and Quick Start Guide to be
better. Let's keep that discussion separate. Same for the processes.
First, our process for taking submissions and turning them into docs is
entirely separate from the tool used to generate the docs.
As a project, we are centered around DocBook and XML. I think this is
the right thing to do, to have a single source for documentation that
can generate _all_ formats.
So, it should be our goal to move all _appropriate_ documentation into
that format and work from there. Eventually.
Because of the existence of tools such as DocBook Wiki, we may be able
to author bi-directionally with a Wiki. Until that is in place, Wiki
authoring is a one-time conversion to DocBook.
We will take a new doc in any format.
We will help to convert it to DocBook XML.
All new documents _must_ have a maintainer who commits to keeping the
doc up to date. That person doesn't have to be the original author.
If you have a doc that is _already_ in a Wiki and an argument why it
should stay there, let's consider it.
If you can only write in {Wiki, HTML, plain text, RTF, troff, LaTeX},
then go ahead. After we convert it for you for maintenance, you can
learn the DocBook. It's just not that hard. Really. And you can use
vi, jedit, Conglomerate, or whatever you choose. You can even use
Notepad under Windows, just don't come here complaining about getting
the toolchain to work under Cygwin. :)
- 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/
19 years
