Re: schedule for translating documentation
by A S Alam
Karsten Wade wrote:
>This is mainly for the release notes, but we can follow it for other
>documentation for FC5.
>
>2 November - test1 documentation freeze
>7 November - test1 release
>7 December - test2 documentation freeze
>12 December - test2 release
>4 January - test3 documentation freeze
>9 January - test3 release
>1 February - FC5 documentation freeze (final)
>13 February - FC5 release
>
>This based on the schedule found at:
>
>http://fedora.redhat.com/participate/schedule/
>
>You'll notice that the docs freeze is two days after the devel freeze.
>
>This is really only one additional day for writing beyond devel freeze,
>accounting for the dateline. This additional day gives us a chance to
>take urgent changes to the release notes right up to devel freeze, and
>have one more day to make changes.
>
>Most of the translation will be in test1. We plan to have rolling
>content available throughout the writing cycle. Following that, we
>don't expect the document to churn very much, perhaps 10% to 20% change
>(change, additions) between tests. Expect the changes between test3 and
>release to be very minimal.
>
>This schedule is subject to changes in the master schedule.
>
>What do you think? With your agreement, I'll share this with the docs
>project as our schedule.
>
>BTW, documents that you may want to translate in addition to the release
>notes, which are planned for FC5:
>
>* Installation Guide
>* Desktop User Guide
>* Managing Software with Yum
>
>
>
Hello,
I m translating Fedora GUI (I have cvs account for GUI)
How can I start Translation docuement for my Language?
can u please provide some Ideas about this?
thanks
AP Brar
Punjabi Translator
>thx - Karsten
>
>
>------------------------------------------------------------------------
>
>--
>Fedora-trans-list mailing list
>Fedora-trans-list(a)redhat.com
>http://www.redhat.com/mailman/listinfo/fedora-trans-list
>
18 years, 7 months
this is for you
by Karsten Wade
Maybe you introduced yourself, or are still lurking.
Perhaps you have a document in progress, or an idea in process.
The Documentation Project needs you to help keep the momentum going.
* What is stopping you from submitting your document?
* From using CVS?
* Do you need more directions?
* Do you want fewer restrictions?
The steering committee for this project is here to help you be
successful working on Fedora documentation.
What can we do for you?
- 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
Self-Introduction: Ignacio Vazquez-Abrams
by Ignacio Vazquez-Abrams
Name: Ignacio Vazquez-Abrams
Location: Toronto, Ontario, Canada
Status: Freelance developer/sysadmin
Goals:
While a lot of very good basic end-user documentation has been written,
as well as some sysadmin stuff, I can't help but feel that there's still
a lack of documentation for users that are ready to take the leap from
just using their system to actually manipulating it in ways beyond what
the average user or sysadmin is expected to do. I hope that I can at
least start to fill that hole.
Historical Qualifications:
Well, I don't really write much in the way of documentation, but samples
of my writings are available all across Google ;) You can also check my
Fedora website (http://fedora.ivazquez.net/) for some small samples of
writing and editing.
--
Ignacio Vazquez-Abrams <ivazquez(a)ivazquez.net>
http://fedora.ivazquez.net/
gpg --keyserver hkp://subkeys.pgp.net --recv-key 38028b72
18 years, 7 months
Doc ideas - Python, Java, PostgreSQL
by Stuart Ellis
I've just added a few more ideas to:
http://www.fedoraproject.org/wiki/DocsProject/DocIdeas
These are a bit vague so anybody with an interest, please feel free to
comment or rewrite what's in the Wiki.
- PostgreSQL: Last meeting Gavin noted that we don't have anything on
Postgres. Fedora ships with PostgreSQL 8 and some specific admin tools,
so it would be great to promote this.
- Overview of the Free Java stack.
- Overview of Python Development with Fedora (or Fedora Development with
Python ?). Not so much a "Hello World" tutorial as "what is it, why
it's good, how to set it up, and where to find the tutorials".
More people working with Python = more patches :).
--
Stuart Ellis
stuart(a)elsn.org
Fedora Documentation Project: http://fedora.redhat.com/projects/docs/
GPG key ID: 7098ABEA
GPG key fingerprint: 68B0 E291 FB19 C845 E60E 9569 292E E365 7098 ABEA
18 years, 7 months
Using ulink
by Paul W. Frields
(Possibly) helpful tip for the day:
FDP standard usage for the DocBook XML tag <ulink> is to always use the
link URL as the text for the link itself. In other words, instead of
this:
<ulink url="http://some.link.to/somewhere/">A good link</ulink>
...use this:
<ulink
url="http://some.link.to/somewhere/">http://some.link.to/somewhere/</ulink>
But wait! It gets easier. DocBook XML specifies that when the XML tag
closes itself (i.e. you don't provide any link text), the link itself is
used as the text for any rendering process. So what you should probably
do instead, for better XML readability, is this:
<ulink url="http://some.link.to/somewhere/"/>
Isn't that a lot easier? I think so. Remember the tag-closing slash
after closing the quotes for the URL, or xmlto will give you a hard time
when you attempt to build your document. :-)
--
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
mentors
by Karsten Wade
A new project/idea has been started about pairing experienced Fedora
community members with new community members.
http://fedoraproject.org/wiki/Mentors
There are lots of ways to help as a mentor. Technical, cultural,
factual, simply how to find people and get stuff done.
We ask that all mentoring is done on-list, where feasible. An
alternative is to report back to the list with summaries of off-list
work. This way we all learn from each other.
Recognize that mentoring happens all the time on Fedora lists. This is
a way of elevating the process, and making sure that people who care
enough to seek out this level of help are paired with someone who can
take the time to answer.
If you are a mentor or a mentee, take a look and get involved.
We are one of the first projects piloting this idea. Whatever we learn
can be taken to the other projects, and hopefully create something the
community at large can use.
- 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
Kernel Compile Lurker
by Kevin H. Hobbs
Grumble grumble. I've been lurking since the purchase of compatible
hardware eliminated the need to compile kernels at work. However, I know
it's important to get the Doc in CVS the webserver gets hit constantly
for this.
I'll go read the "Get CVS Access" stuff.
18 years, 7 months
Minutes FDSCo 16 August 2005
by Karsten Wade
Nice little meeting today, tools and mentoring were the main topics.
FDSCo Meeting
16-AUG-2005
#fedora-docs on irc.freenode.net
Attendees:
==========
Tammy Fox
Paul Frields
Tommy Reynolds
Stuart Elliss
Gavin Henry
Karsten Wade
Contributors:
=============
Patrick Barnes
Bob Jensen
Updates:
========
Discussions about participation and recruiting are beginning on
f-docs-l. These tie into ongoing discussions on f-marketing-l.
Documentation Project has a few mentors. See
http://fedoraproject.org/wiki/Mentors for more information.
Actions:
========
Karsten - make sure FC devels know where to point potential writers
Paul - how-to engage tidy-bowl
Tommy - patch tidy-bown to add '-n' to not change doc but show changes
only - DONE
Paul, Stuart, Karsten - Post yum tutorial, deprecate old update
tutorial - DONE
All - if you want to be a mentor:
* pick someone to contact from
http://fedoraproject.org/wiki/DocsProject/Contributors
* anyone is worth asking, they might appreciate the help
* Cc: the initial contact to f-dsco-l, with a blurb such as, "I
Cc:'d the docs project committee so we can keep track of who
we each contact."
* Alternately, send a separate email, if you prefer.
* Ask to keep mentoring discussions on f-docs-l *or* have
summaries occassionaly sent. For example, the mentee could
send an email, "I discussed this idea with Karsten on IRC, and
he thinks it will work great, so this is what I'm doing ..."
## 30 ##
--
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