Self-Introduction: Debra Deutsch
by Debbie Deutsch
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Full legal name - Debra Deutsch. (My friends call me Debbie.)
City, Country - Boston, USA
Profession or Student status - Product Manager (telecommunications
products).
Company, School, or other affiliation - EG&H, Inc. My interest in the
Fedora Project is strictly personal.
My goals in the Fedora Project
What do I want to write about? My primary interest is to write about
topics that will help people who are comfortable with computer software
and hardware but are not expert in Linux. That is how I see myself.
These readers understand operating system principals, the functions of
the hardware components in a computer system, and how the hardware and
software work together. They may be willing to take on complex tasks
that are not appropriate to a non-technical user. On the other hand,
they may not have all the Linux-specific knowledge that some discussions
of advanced topics assume.
What other documentation do you want to see published? I have no
suggestions now, but may have some after I gain experience with the project.
Do you want to edit for grammar/writing and/or technical accuracy? I
can edit for grammar if that would be useful. I would want some
experience writing for the project before I offered to edit for style.
As I am not an Linux expert, my ability to edit for technical accuracy
is limited, but probably not zero.
Anything else special? I would be happy to start by helping someone who
has a large task, or by taking on very small tasks of my own. I would
rather do a good, timely job on something small than a mediocre or late
job on something too large or complex. I am new here.
Historical qualifications
What other projects or writing have you worked on in the past? I have
never participated in an open source or similar large volunteer effort.
However I have a great deal of paid experience working in large,
geographically distributed groups to accomplish complex projects. For
example, I have participated in technical standards committees and on
product teams in large, multinational corporations. Even though I have
never held a position as a technical writer, writing has always been an
important part of my work. I have authored technical reports, standards
documents, and all kinds of product collaterol. I have also been paid
to write articles and a book chapter for publication.
What level and type of computer skills do you have? I have been using
computers for more than 30 years and have a good understanding of
operating system and system architecture principles. I have worked as a
software engineer. That was a long time ago; I am not qualified to
write about development using modern Linux tools. (On the other hand, I
probably would be a good choice to try out a HOWTO aimed at readers who
were new to a tool.) In recent years I have used Windows as my primary
computing environment in my workplace. At the same time, I have also
been using Linux in more a limited way at home. Three years ago, I
converted an old Windows system to Redhat 9.0, so I could run my own
mail server for my domain. I am writing this email using a new system
that I assembled from parts and a downloaded FC4 distribution. Other
than using it as a file server, my plan is to make this system the
administrative hub of my home computing environment.
What other skills do you have that might be applicable? I am
experienced at project management, inbound marketing, and outbound
marketing. My inbound marketing experience has been primarily with
requirements definition. My outbound marketing experience includes
writing product collaterol, such as brochures, white papers, and
specification sheets. I know a fair amount about data networking and
the Internet.
What makes you an excellent match for the project? I have had a great
deal of fun with my Redhat and Fedora projects. I take on something
complex and learn along the way. There is a fine sense of
accomplishment when everything works. The project is an opportunity to
share my enthusiasm with other people who are considering jumping into
the Fedora pool. Perhaps I can help make it easier for them to swim
when they do.
GPG KEYID and fingerprint
pub 1024D/73CD2969 2006-01-21 [expires: 2007-01-21]
Key fingerprint = F668 0373 4BE5 737E 13F6 557F 16CC 9D70 73CD 2969
uid Debra Deutsch <fedoradocs(a)ddeutsch.org>
sub 2048g/E421BAD1 2006-01-21 [expires: 2007-01-21]
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFD0uqRFsydcHPNKWkRAob9AKDGj7DtNIe5m7GZPTi7NgRaXoiMFwCgkFtL
edPqfHfLwY+dvBKTSUa+M7g=
=36Yu
-----END PGP SIGNATURE-----
18 years, 3 months
Re: docs-common/bin insert-changelog,1.5,1.6
by Tommy Reynolds
Uttered "Paul W. Frields" (pfrields) <fedora-docs-commits(a)redhat.com>, spake thus:
> - REVDATE=`date +"%Y-%M-%d"`
> + REVDATE=`date +"%Y-%m-%d"`
While I realize that the RPM-mandated date string "%s %b %d %Y" will
not sort very well, at least it won't mess up the RPM changelog.
Shouldn't we be using that for this insert command?
Cheers
18 years, 3 months
self-introduction: sam folk-williams
by Sam Folk-Williams
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
name: sam folk-williams
City, Country; Raleigh, NC, USA
Profession: Technical Support Engineer
Company or School: Red Hat
Your goals in the Fedora Project
What do you want to write about? Specifically, I would like to
contribute to documentation on the Xen project.
What other documentation do you want to see published? I'd like to see
more how-to's or "knowledge base" type articles that walk new users
through specific problems or common pitfalls.
- -Do you want to edit for grammar/writing and/or technical accuracy? I
certainly can do this.
- -Historical qualifications
- -What other projects or writing have you worked on in the past? I have
worked as a professional writer for several years. I have articles
published in various places on the web. Currently, I'm contributed to
Red Hat's knowledge base (kbase.redhat.com).
- -What level and type of computer skills do you have? I have an RHCE and
I am working towards my RHCA -- I provide support of all kinds to linux
users.
- -What other skills do you have that might be applicable? I have a lot of
"soft skills" and work a lot with a variety of folks.
- -What makes you an excellent match for the project? I love fedora, I use
it all the time for work and personal computing, and I actively
encourage other people to use it. I have a strong background in writing,
training, and providing technical support.
- - GPG KEYID and fingerprint
pub 1024D/1B0D46BA 2005-11-01
Key fingerprint = 4832 3A28 C266 0CB5 7931 5AF1 CCEC 3EBC 1B0D 46BA
uid Sam Folk-Williams <sfolkwil at redhat dot com>
sub 1024g/5EEFE462 2005-11-01
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.1 (GNU/Linux)
Comment: Using GnuPG with Fedora - http://enigmail.mozdev.org
iD8DBQFD0NdtzOw+vBsNRroRAhONAKCsQz0hiwMaYJrVfI/nc680fMohPgCdH1Pd
bLInTsUYlo9uxV7pHbBuRq4=
=/VCw
-----END PGP SIGNATURE-----
18 years, 3 months
Life settled enough to work on RPMs?
by Tommy Reynolds
Hello, All!
I am ready to start checking in some of my hacks against
the preliminary work that stickster has done on the RPM
packaging front. It's not yet ready for prime time,
but it is close.
These changes may or not break any packaging currently
in place for the FC5 tests, so I thought I'd check the
list before doing the commit.
So, are you ready to rumble?
18 years, 3 months
Re: docs-common/packaging fedora-doc-common.spec, 1.5, 1.6 fedora-doc.spec.in.common, 1.2, 1.3
by Paul W. Frields
Question about this follows, keep reading...
On Thu, 2006-01-19 at 14:50 -0500, Tommy Reynolds wrote:
> Author: jtr
>
> Update of /cvs/docs/docs-common/packaging
> In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv3874/docs-common/packaging
>
> Modified Files:
> fedora-doc-common.spec fedora-doc.spec.in.common
> Log Message:
> First cut a integrating the RPM packaging stuff with the
> "docs-common/Makefile.common" infrastructure. While this appears to
> work *somewhat* with the "example-tutorial", it is certainly not
> ready for prime time yet.
>
> TODO:
> 1) Verify that all generated RPM's have the necessary files inside.
> 2) Mangle the "../docs-common" strings in Makefiles, *.xml, to
> reference the "/usr/share/fedora/doc" ${FDPDIR} so that we don't
> need to bugger the RPM checksums of the files by altering them at
> RPM install time.
> 3) Buy a beer all round.
>
>
>
[...snip...]
> Index: fedora-doc.spec.in.common
> ===================================================================
> RCS file: /cvs/docs/docs-common/packaging/fedora-doc.spec.in.common,v
> retrieving revision 1.2
> retrieving revision 1.3
> diff -u -r1.2 -r1.3
> --- fedora-doc.spec.in.common 21 Nov 2005 00:37:58 -0000 1.2
> +++ fedora-doc.spec.in.common 19 Jan 2006 19:50:05 -0000 1.3
> @@ -25,9 +25,12 @@
>
> %prep
> %setup -q -n %{docbase}-%{version}
> +# FIXME: Need to do this remapping in the RPM build section, since it
> +# causes "rpm -V foo" to fail, even if it's done immediately after an
> +# install...
> for i in $RPM_BUILD_DIR/%{docbase}-%{version}/%{docbase}*.xml
> do
> - %{__sed} -i 's!../docs-common/!../../docs-common/!' "$i"
> + %{__sed} -i 's!../docs-common/!/usr/share/fedora/doc/docs-common/!' "$i"
> done
I haven't seen that failure... I don't have any wacky RPM macros AFAIK,
and if I build the example-tutorial RPM and install, "rpm -V
example-tutorial" returns an okey-doke. Doesn't the package
checksumming, etc., come after %install?
--
Paul W. Frields, RHCE http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Documentation Project: http://fedora.redhat.com/projects/docs/
18 years, 3 months
RPM Packaging: here we go!
by Tommy Reynolds
Hi, All!
I've just checked in the RPM packaging changes needed to get
RPM building into the "docs-common/Makefile.common" infrastructure.
There are still some serious problems with the packaging; it is NOT
yet ready for general usage, so if you are not interested in RPM
debugging, best steer clear for the time being.
But, when all this works, you will be able to create your document
RPM's by installing the docs-common RPM and then:
$ make rpm
so just be a patient a couple of more days.
Cheers!
18 years, 3 months
Re: translation-quick-start-guide rpm-info.xml,1.1,1.2
by Paul W. Frields
On Wed, 2006-01-18 at 22:04 -0500, Manuel Ospina wrote:
> Author: mospina
>
> Update of /cvs/docs/translation-quick-start-guide
> In directory cvs-int.fedora.redhat.com:/tmp/cvs-serv2291
>
> Modified Files:
> rpm-info.xml
> Log Message:
> updated
Manuel (&co.),
I am working on editing your document. Hopefully I will have a new
draft finished shortly.
--
Paul W. Frields, RHCE http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Documentation Project: http://fedora.redhat.com/projects/docs/
18 years, 3 months
Re: install-guide rpm-info.xml,1.2,1.3
by Paul W. Frields
re: Commit below --
On Tue, 2006-01-17 at 18:04 -0500, Tommy Reynolds wrote:
> Log Message:
> Dates must be in ctime(3) format, not ISO format.
>
> TODO: We need an XSL magic to translate the dates if they have dashes.
> Index: rpm-info.xml
> ===================================================================
> RCS file: /cvs/docs/install-guide/rpm-info.xml,v
> retrieving revision 1.2
> retrieving revision 1.3
> diff -u -r1.2 -r1.3
> --- rpm-info.xml 17 Jan 2006 22:49:29 -0000 1.2
> +++ rpm-info.xml 17 Jan 2006 23:04:15 -0000 1.3
> @@ -28,7 +28,7 @@
> <!--PLEASE ADD A TRANSLATION FOR EACH ADDITIONAL LANGUAGE.-->
> </titles>
> <changelog order="newest-first">
> - <revision date="2006-01-17" number="0" role="rpm">
> + <revision date="Tue Jan 17 2006" number="0" role="rpm">
> <author worker="megacoder"/>
> <details>Added initial empty RPM revision to test packaging.</details>
> </revision>
The "make clog" target takes care of this automatically. I would
recommend folks using that target whenever possible since it minimizes
hassle. If you edit manually, well, just respect the normal rules for
such things. If you break the revision's @date attribute, the rpmbuild
process will tell you what you did wrong (i.e. %changelog date is not in
proper format).
Since no one will be creating rpm-info.xml files that have any RPM
revisions yet, there shouldn't be any cruft to worry about.
--
Paul W. Frields, RHCE http://paul.frields.org/
gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717
Fedora Documentation Project: http://fedora.redhat.com/projects/docs/
18 years, 3 months