Self-Introduction: Noriko Mizumoto
by Noriko Mizumoto
Noriko Mizumoto
Brisbane, Australia
Translator_ja/Engineering
Red Hat Asia-Pacific
Goals;
- Establish consolidated procedure linking docs and trans
Historical Qualification;
* What other projects or writing have you worked on in the past?
Consultant, UK 2001
Trainer, HKG 2000
Call Centre Team Leader, AUS 1994-2000
* What level and type of computer skills do you have?
Red Hat Certified Technician
* What other skills do you have that might be applicable?
Royal Life Saving Club Bronze Medallion (showing a bit of toughness :))
Writting/customization training manuals and some papers
* What makes you an excellent match for the project?
More documents to come up and finish, then those should spread arround
the world, making people impressed. What is needed? => translation :)
I'd like to be a part of PIPE between writers and translators.
GPG KEYID and fingerprint;
pub 1024D/46F6383D 2005-06-30 Noriko Mizumoto (Fedora Project)
<noriko(a)redhat.com>
Key fingerprint = 8325 2A54 5528 B573 9E2C 2D70 A7B3 CA57 46F6 383D
sub 1024g/5E902D70 2005-06-30 [expires: 2006-06-30]
18 years, 7 months
Who's the Fedora user?
by Greg DeKoenigsberg
This is one potential user of Fedora: Judy, from Arizona. She sent in a
letter to the editor of Red Hat Magazine that makes me weep inside.
What do we have to say to her?
--g
-------- Original Message --------
Subject: [CM] RE: Red Hat | Training News | Americas | August 2005
Date: 24 Aug 2005 14:58:40 -0000
From: azgjudy(a)azgalaxyonline.com
To: <bblell(a)redhat.com>
CC: Support <support-byzukdeavsdrjebc9mkazb7v1zzhgs-r(a)redhat.com>
Dear Red Hat, I hope you will get this e-mail. I am a single user
computer person. I put yes down - so I could receive your e-mails.
To tell you the truth I do not know why. Your main emphasis seems to
be on business. I switched from Windows because I thought it would
be safer and healthier all the way round. To tell you the truth I
feel totally lost in your system. I cannot use my CDs that have
games. I downloaded a game I had paid for. No way could I get it to
work. I wrote to Linux Game. Their directions were like Greek, and
I only speak English. I tried to download the anti-virus I use.
They have a version for Linux. No way did I get that. I looked
into your training, but that is extremely costly. I have bought
books. It all come s down to the fact There is little I am able to
do with Linux. Mostly I would like to have a plug-in that works, as
to the fact there are many things I am unable to open, including some
mail, because I can find no way to do it. Dear Red Hat - what are
you doing for us little people out here? I am no further today than
I was the day this was installed. Thank you, Judy D.
---- Original Message ----
From: redhat(a)info.redhat.com
To: azgjudy(a)azgalaxyonline.com
Subject: RE: Red Hat | Training News | Americas | August 2005
Date: Tue, 23 Aug 2005 14:36:21 -0000
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>Red Hat | Training News | August 2005
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>* August trivia question
>* Summer gear promotion almost over
>* Training press: What certification means to you (Certification
> Magazine)
>* Red Hat news: Red Hat Network adds monitoring tool, Solaris support
>
>* South American training news: "Capacitar para progresar" (Latin
> Source Tech)
>* Ask the expert: Red Hat Training Q & A
>* Tips from RHCEs: Remote controlled desktops without VNC
>
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>AUGUST TRIVIA QUESTION:
>
>Late last year CertCities.com picked Red Hat Certified Engineer
>(RHCE)
>as the _____ hottest IT certification for 2005.
>
>A) 1st
>B) 3rd
>C) 5th
>D) 10th
>E) None of the above
>
>[Stumped? Answer appears at the bottom of this newsletter.]
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>~
>
>SUMMER GEAR PROMOTION ALMOST OVER: SURF'S UP WITH RED HAT TRAINING
>
>Improve your skills, increase your career performance, and get Red
>Hat
>summer gear. Sign up for select summer North American training
>courses
>and receive:
>
>* Shadowman boogie board
>* Flip-flops
>* Visor
>* Oversize beach towel
>* Kite
>* Frisbee
>
>--> View the gear and learn more about this limited time offer.
>http://info.redhat.com/a/tBDCzLwAUfRoFAYV5P3AT-kh4gt/trai17
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>~~~~
>
>TRAINING PRESS: WHAT CERTIFICATION MEANS TO YOU (CERTIFICATION
>MAGAZINE)
>
>"[M]ost qualified candidates feel that their experience speaks for
>itself, but as Linux becomes more prevalent in the corporate
>environment, more potential employers are looking for certifications
>as
>a benchmark of the candidate's knowledge and experience in skill sets
>relevant to the job at hand. This month, I'll help you to understand
>which certifications corporations are looking for - and why."
>
>--> Read the full article.
>http://info.redhat.com/a/tBDCzLwAUfRoFAYV5P3AT-kh4gt/trai10
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
>RED HAT NEWS: RED HAT NETWORK ADDS MONITORING TOOL, SOLARIS SUPPORT
>(ENTERPRISE NETWORKING PLANET)
>
>"Red Hat has announced a new monitoring tool it says will support
>Sun's
>Solaris as well as its own Linux offerings. The Red Hat Network
>Monitoring Module is built on the company's Red Hat Network (RHN), a
>web-based systems management tool used to monitor and schedule
>updates
>for subscribed Red Hat Enterprise Linux systems. RHN allows
>administrators to track errata for their systems, create common
>software
>profiles for groups of systems, and allow for rollback of problematic
>updates. The RHN Monitoring Module adds four key pieces of
>functionality..."
>
>--> Read the full article.
>http://info.redhat.com/a/tBDCzLwAUfRoFAYV5P3AT-kh4gt/trai14
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>~~~
>
>SOUTH AMERICA TRAINING NEWS
>
>--> Article: "Capacitar para progresar":
>http://info.redhat.com/a/tBDCzLwAUfRoFAYV5P3AT-kh4gt/trai15
>
>--> South American course schedule and special offers.
>http://info.redhat.com/a/tBDCzLwAUfRoFAYV5P3AT-kh4gt/trai4
>
>Email capacitacion(a)latinsourcetech.com for further information.
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>
>ASK THE EXPERT: Red Hat Training Q & A
>
>Q: I am a computer software engineer and I have Linux+, OCA (Oracle
>Certified Association), and OCP (Oracle Certified Professional)
>certifications. I am familiar with Red Hat and I want to improve my
>job
>position. Can a Red Hat certification help enhance my career and get
>me
>a job with a large international company?
>
>Best Regards,
>Alireza Rahmani
>
>A: Thanks for your question Alireza. While it's impossible to ensure
>that any professional certification will universally lead to
>promotions,
>increased responsibility, or high-paying positions with large
>companies,
>industry analysts agree that RHCT and RHCE are both likely to boost
>your
>employment options and overall career standing. Recently,
>Certification
>Magazine and Fairfield Research ranked the RHCE the most valuable
>certificaiton in all of IT. In addition, according to numerous
>industry
>surveys, Red Hat certifications are one of a handful of IT
>credentials
>that command double digit annual salary increases.
>
>http://info.redhat.com/a/tBDCzLwAUfRoFAYV5P3AT-kh4gt/trai12
>
>So while nobody can guarantee that a certification will lead to
>automatic career success, most would agree that RHCT and RHCE are
>guarantees of competency that resonate with colleagues and employers
>alike.
>
>-->Submit a question.
> ask-the-expert(a)redhat.com
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>TIPS FROM RHCEs: REMOTE CONTROLLED DESKTOPS WITHOUT VNC
>
>In Red Hat Enterprise Linux 4 the GNOME desktop is provided with a
>vnc
>like service called vino. It will allow a vnc client to remotely
>control the logged in users native GNOME desktop and enable desktop
>sharing.
>
>--> Read more.
>http://info.redhat.com/a/tBDCzLwAUfRoFAYV5P3AT-kh4gt/trai9
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
>TRIVIA QUESTION ANSWER:
>
>B) 3rd
>
>In December, CertCities.com ranked Red Hat Certified Engineer (RHCE)
>as
>the third hottest IT certification for 2005.
>
>-> Read the full article here.
>http://info.redhat.com/a/tBDCzLwAUfRoFAYV5P3AT-kh4gt/trai11
>~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>~
>
>Want
18 years, 7 months
Docs-Common
by Andy Hudson
Hey...
Just spent ten minutes grappling with this - don't you think it would be
a good idea to update the documentation guide with the new CVS location
(docs-common) for the DTDs and Stylesheets etc?
It's still pointing to fedora-docs...
Thanks,
Andy
18 years, 7 months
Self-Introduction: AP Singh Brar
by A S Alam
* Amanpreet Singh Brar Alamwalia
*Full legal name : Amanpreet Singh Brar
*City, Country: Moga (Punjab), India
*Profession or Student status: Translator
*Company or School: member of Punjabi Translation Team
(http://punlinux.sf.net)
(o) Your goals in the Fedora Project
Translation of Open Source Software and Document in Punjabi
(Gurmukhi)
*What do you want to write about?
User guide
* Do you want to edit for grammar/writing and/or technical accuracy?
NO
(0) Historical qualifications
* What other projects or writing have you worked on in the past?
I m working for Translation of Open Source Project gnome,
kde, xfce, openoffice and
working for gnome docs translation.
* What level and type of computer skills do you have?
I m working for Translation from last 1 and 1/2 year
* What other skills do you have that might be applicable?
User interface design, other so-called soft skills (people skills),
programming, etc.
Translation of GUI
* GPG KEYID and fingerprint
pub 1024D/A35AFB3B 2005-08-24 Amanpreet Singh Brar Alamwalia
(Punjabi) <apbrar(a)gmail.com>
Key fingerprint = C6B9 15F9 203A 3597 1892 F416 9128 AAFB A35A FB3B
uid [jpeg image of size 14199]
sub 1024g/0B66D407 2005-08-24
18 years, 7 months
RFC - Moving to Fedora from Windows
by Andy Hudson
Hi everyone,
Having read with a heavy heart the post from Greg concerning a newbie
experience with Fedora, I kinda figured that what we need is an
orientation document for new users (ie new to Linux) to pick up when
they come to Fedora.
Brief outline below:
Welcome to Fedora Core Linux
Linux concepts (ie root etc)
First impressions
Gnome - where do I find? Screensaver, desktop background etc
Email - What's this Evolution thing? (potential to include
Thunderbird here because of availabilty on Windows)
Internet - Finding the web
Productivity - Finding OpenOffice.org, brief intro to each component
IM - Where's AIM or Windows Messenger?
Moving Further
Games - getting your Windows games working under Fedora
Getting support for your graphics card/Installing appropriate drivers
This is just a starting point - feel free to shout down or include any
other areas that you feel would be genuinely advantageous for a newbie
to read about when they first boot into Fedora.
Thanks,
Andy
18 years, 7 months
Docs packaging
by Paul W. Frields
I want to take a stab at packaging at least a few of the biggie Fedora
docs for FC5. Some of these thoughts below:
* Since docs are not absolutely necessary to run a system, Extras seems
like the right place to me. Putting Fedora on a diet was discussed
endlessly before and after FC4, so I'm not sure we can make a great case
for getting docs into Core. Nor should we really bother -- Extras is
not a second-class citizen or a myth, it's a living, breathing, vital
repository where we can be proud to have our documentation. Plus,
putting it in Extras means it can stay fresh, which is absolutely
important to this project. (I have Extras membership, as do some of our
other contributors, and can easily find someone to review the package
for inclusion. In fact, any of you could do it, and probably should, to
speed the process up.)
* Packages will consist of HTML. The XML will be in the .src.rpm as
expected. Building to be done via the buildsys/plague per normal
routine, unless someone has a better idea that doesn't require a lot of
manual intervention. We don't really need our own buildsys, since the
docs packages would live in Extras anyway.
* As far as the process goes, I see it as snapshotting the CVS for
SOURCES stuff, updating Extras CVS with the results, and do a build
request on normal channels. Package versioning is done from the CVS
date, per Fedora Extras guidelines. The resulting packages can be
linked from the f.r.c/docs/* pages alongside any tarballs.
* I am not keen on a single docs package, because updates should be
available on a rolling schedule in very small pieces. Some documents
require large files bundled in the package; an example is the
Installation Guide, which has a few MB worth of screen shots. Users
should not be required to download that amount of material just to get a
new release of foo-tutorial. A better organization would be:
* fedora-docs-common: Anything used by all the docs, such as CSS;
probably to be installed in %{_docdir}/fedora-docs/
* fedora-install-guide: self-explanatory, sits in
%{_docdir}/fedora-docs/install-guide/
* fedora-documentation-guide: ...and so forth...
Note that these are not subpackages, so that their version information
can move independently and track the revision history in each doc if
need be. This is especially important with the canonical guides,
although I could see using CVS dating (i.e. M.m-R.YYYYMMDDcvs) as well.
My preference would be to keep it simple if possible.
* I would like the /usr/share/doc/HTML/index.html file (which is part of
fedora-release, and comes up when people launch Firefox) to show a SHORT
and informative menu on how to:
* Read the release notes
* Install and update software, in particular Fedora docs
(i.e. "yum install fedora-docs\*" plus link to Stuart's yum doc)
* Access fedoraproject.org, especially the Wiki
* Get involved in Fedora (probably also through fp.org)
This menu should simply be incorporated at the top of the release notes
to minimize clicking around for new users as well as the work required
to get it in under deadline.
I'm sure everyone can come up with additional thoughts -- I am trying to
jot all this down quickly, so I've likely forgotten important things.
Have at it, please!
--
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, 7 months
Wiki musings
by Karsten Wade
We had a lively discussion about Wiki at the FDSCo meeting this week.
Here is my summary of the current argument and ideas:
Fact: The community has bypassed FDP technologies in favor of the Wiki
Fact: To still be the project that handles Fedora documentation, we
need to address this activity. These docs need to be brought into the
fold, and a process created to formalize them.
Why the last fact?
Our goal is to create high quality documentation for Fedora. Tools are
not specified in that goal. Just the quality. Printable, packageable,
viewable with XML viewers, useful offline as well as on.
To ensure quality, we need:
* Actual technical and grammatical editing
* Some control over some kinds of content, to protect from accidental or
malicious tampering
* Multiple output formats for our finished documentation
To get those, we need to move our process to include the Wiki.
Otherwise, there is a growing amount of documentation that is within the
project because it is hosted on fedoraproject.org, but is not QA'd or
available for printing, etc.
Here are some ideas for how to accomplish this:
* Create a structure in the Wiki that will let us host a Docs/Drafts/Foo
and a Docs/Foo, to help differentiate draft content
* Draft documents must have the word Draft in their title, perhaps even
their Wiki title? The name could be changed (using a rename or a
#redirect) to the final doc, when finalized.
* Editors need to subscribe to /Docs/Drafts/* and help writers by
watching content changes. Via RSS feed, if they prefer.
* wiki/Docs/Drafts/ needs to be closed to all but those in the
DocWriters groups. This membership should be easy to obtain.
* Wiki/Docs/ needs to be for DocEditors only
* We can add people to those groups quickly and easily, and we encourage
cross-work. If you see something that needs fixing within those trees,
fix it, knowing others are watching you to help fix your mistakes.
* To be promoted from wiki/Docs/Drafts to wiki/Docs/ requires an editor
approve the document as ready to publish. Once it's moved, the writer
can continue to work on it. Anyone else who wants to work on it need
only be in the DocWriter group, which is the same as described in
NewWriters. Developers need to have self-intro'd on some mailing
list. :)
* New documents can be written and abandoned in Docs/Drafts/. We'll
have quarterly clean-ups and purge cruft. This is a safe scratch space,
well marked with "Tygers Be Here, Users Run Away!!"
* Formal documents should be available in PDF, tarball, and RPM format.
To accomplish this, part of promoting every document to Docs/ is to
create a CVS module for it and get the Wiki to pull from CVS instead of
its own flat-files.
This last part is the one that requires some new infrastructure. I am
working on this with Seth and Elliot. The idea is to edit the XML
directly through the Wiki, with the XML stored in CVS and thus part of
the whole build system.
Bottom line is, your choice of what tool to edit your content should not
stop us from fully utilizing your content.
Opening up our documentation this way will attract developers who won't
fool with XML in CVS. We just give them DocWriter access, and away they
go.
Thoughts?
- 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/
18 years, 7 months
Fedora DTD?
by Thomas Jones
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hello all,
I have been playing with this idea and wanted to present it to the community
with a request for comment:
With the increase in independence of Fedora from it's parent entity Redhat, I
think there should be some formal declarations. These simple declarations are
all in the realm of XML. This submission should/may provide a central
document modeling scheme with respect to all documentation written prior to
and thereafter.
Projected doctype declaration:
<!DOCTYPE article PUBLIC "-//Fedora Core//DTD DocBook XML V4.2-Based Subset
0.1//EN"
"http://fedora.redhat.com/projects/docs/dtd/fedorax.dtd"
[...]>
I have quickly built up a DTD Driver for the Docbook 4.2 release. This driver
contains declarations for Fedora Core specific documentation.
Development location:
http://www.buddhalinux.com/xml/docbook/custom/fedoradtd/0.1.0/schema/dtd/...
There are higher-level advantages to such approach:
- Central repository for all elements to be utilized and/or deprecated. No
more requesting help about an element.
- Element consistency. If an element is available, when you build your
documentation instance against this DTD; it will proceed without error. If
you attempt to build a document instance with an invalid element that is not
available in the Document Model, you will be unable to build successfully.
- - Entity validation. Any entity can be added, altered, and removed from the
Document Model with minimal intrusion to the author(s).
- - Formal Definition of the FDP and its namespace. The FDP can be formally
declared on all documentation. FDP document elements can then be included
with other namespace elements without error.
- - Architecture content. Declaration can be made for architecture specific
content which can then be portrayed to the end-user via stylesheets.
- - Language declarations. Language translations can be included inline in
sources by translators.
- - Fedora specific entities inclusion.
Most of all this document negates any of the inconsistencies found in the FDP
documentation site. The site doesn't really provide guidance or
recommendations for the markup of the documentation. With this DTD. there is
no question as to what can and can't be utilized --- and in which way.
I know that as a new author there were(still is) alot of ambiguities and
problems with constructing documentation according to the editors and/or
process. [Paul can vouch for this one!] ;)
Hopefully this may help the other newbie authors out there who want to help as
well; but are hitting the same walls as I once did/am doing.
Thanks,
Thomas Jones
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)
iD8DBQFDC1W5oR5cE1e/kEIRApk2AJ0dbexvSIBJxTfjvCz0+Wd7tt1ikwCeMQcK
dgL8ew9T6VEApuUqYSBImeo=
=/Vn3
-----END PGP SIGNATURE-----
18 years, 7 months