from: http://fedoraproject.org/wiki/DocsProject_2fSelfIntroduction
The below items in bold are Required while the other items are
optional but highly recommended.
WTF!!?? People volunteer to help and get rather long list of *required* information!!?? I reserve further comment and decided it would be bad form for a new user to edit the wiki... I won't even start talking about right to privacy and the idea of a meritocracy!
Anyway...
Body
1. Duncan Lithgow
2. I'm in the city of Århus in Denmark (pronounced 'oar-huus'), but New Zealander by birth and taste in breakfast cereals.
3. I'm trained as an architect, self taught so-so php programmer but good with html/css. Currently doing boring labour temping. Done lot's of other irrelevant stuff. Oh, one relevant thing is I'm a trained 'english as a foreign language' (efl/esl) teacher - so i'm passionate on the need for docs written in easy to understand english - far too much is written for advanced english speakers - think how many non english speakers try to make use of these docs.
4. n/a
5. Your goals in the Fedora Project
* What do you want to write about? * - don't know yet. Maybe 'Why should your non-nerd girlfriend/boss/college use linux and how to convince them and them her'
* What other documentation do you want to see published? - see above
* Do you want to edit for grammar/writing and/or technical accuracy? * - yes/yes/no
* Anything else special? * - editing for friendliness to esl readers.
6. Historical qualifications
* What other projects or writing have you worked on in the past? * - while learning postnuke cms I wrote this about the theme system, I thought it was poorly documented and neede to keep track of what I was learning. I've since turned the xml file over to the postnuke docs team ( i don't use postnuke any more) http://www.lithgow- schmidt.dk/pnThemeManual_v01/ch01.html
* What level and type of computer skills do you have? * - modest, just starting to learn the command line. Long time semi-power-user of windows.
* What other skills do you have that might be applicable? User interface design, other so-called soft skills (people skills), programming, etc. * - good at cross-culture communication, constructive critic of design quality of gui's in terms of logical structure and intuitiveness.
* Why should we trust you? <--- too blunt? * You shouldn't until I've proved myself, but hey, get over it, we're talking about writing docs!
7. GPG KEYID and fingerprint
* Be sure that your GPG key is uploaded to pgp.mit.edu. Use "gpg --keyserver pgp.mit.edu --send-key KEYID".
* Your GPG fingerprint is 40 hexadecimal characters long, while your KEYID is the last 8 digits.
* Below is an example of a block of text suitable for cut & paste into your self-introduction e-mail. * sounds like a hastle, follow the link, it's easier: http://pgp.mit.edu:11371/pks/lookup?op=vindex&search=0x21A8C63A
So, that's me on a good day, in an impatient tone. ;-)
Duncan
On Thu, 2005-03-31 at 19:17 +0200, Duncan Lithgow wrote:
from: http://fedoraproject.org/wiki/DocsProject_2fSelfIntroduction
The below items in bold are Required while the other items are
optional but highly recommended.
WTF!!?? People volunteer to help and get rather long list of *required* information!!?? I reserve further comment and decided it would be bad form for a new user to edit the wiki... I won't even start talking about right to privacy and the idea of a meritocracy!
I changed the word to "Requested", since this matches the concept and spirit better. Hopefully less offensive, eh? ;-)
I'm a trained 'english as a foreign language' (efl/esl) teacher - so i'm passionate on the need for docs written in easy to understand english - far too much is written for advanced english speakers - think how many non english speakers try to make use of these docs.
I suffer from overly complex English in my writing. I am very interested in this subject, particularly for self-improvement and the usability of FLOSS in developing nations. We haven't connected much with the internationalization (i18n) project, but when we do have something to ask them to translate, I'd like it to be good from the start.
Please watch for the style guide announcement, perhaps as early as next week. We want to address writing for i18n at the earliest stages of document creation. I'll be curious to see your comments on what it says about these subjects.
- Karsten
On Saturday 02 April 2005 01:54, Karsten Wade wrote:
I suffer from overly complex English in my writing. I am very interested in this subject, particularly for self-improvement and the usability of FLOSS in developing nations. We haven't connected much with the internationalization (i18n) project, but when we do have something to ask them to translate, I'd like it to be good from the start.
Release Notes!
This is the most needed thing and there are people willing to do it.
On Sat, 2005-04-02 at 19:16 +0200, Ronny Buchmann wrote:
On Saturday 02 April 2005 01:54, Karsten Wade wrote:
I suffer from overly complex English in my writing. I am very interested in this subject, particularly for self-improvement and the usability of FLOSS in developing nations. We haven't connected much with the internationalization (i18n) project, but when we do have something to ask them to translate, I'd like it to be good from the start.
Release Notes!
This is the most needed thing and there are people willing to do it.
Have you visited http://fedoraproject.org/wiki/FedoraDocsProject yet? There's a link there to the release notes:
http://fedoraproject.org/wiki/FedoraDocs_2fRelNotes_2fCore4Test1RelNotes
If you find any problems or omissions, the second link on that page is a pre-formatted Bugzilla request you can use to enter a bug against the release notes. Thanks for your interest and we look forward to your continued input.
On Sat, 2005-04-02 at 19:16 +0200, Ronny Buchmann wrote:
On Saturday 02 April 2005 01:54, Karsten Wade wrote:
I suffer from overly complex English in my writing. I am very interested in this subject, particularly for self-improvement and the usability of FLOSS in developing nations. We haven't connected much with the internationalization (i18n) project, but when we do have something to ask them to translate, I'd like it to be good from the start.
Release Notes!
This is the most needed thing and there are people willing to do it.
I posted the first iteration of the release notes process here:
http://www.fedoraproject.org/wiki/FedoraDocs/RelNotes/RelNotesProcess
Scroll down to the heading, Release Notes Process - Iteration One, April 2005. The Wiki process described at the top of the page is short term only, hopefully we can supplant it with real changes to the relnotes for test3
For all -- if you want to help with the release notes as a writer, start by reading that process, make sure you understand the general FDP docs process, and come back here to tell us what you'd like to write about in the relnotes.
As Paul pointed out, if you see -anything- in the relnotes on the Wiki that needs changing, file a bug report. The master tracking bug for the release notes is here, showing the dependency tree:
https://bugzilla.redhat.com/bugzilla/showdependencytree.cgi?id=151189
And please do use the pre-filled bug from the Wiki, also as pointed out. :)
- Karsten
On Sunday 03 April 2005 03:37, Karsten Wade wrote:
On Sat, 2005-04-02 at 19:16 +0200, Ronny Buchmann wrote:
On Saturday 02 April 2005 01:54, Karsten Wade wrote:
I suffer from overly complex English in my writing. I am very interested in this subject, particularly for self-improvement and the usability of FLOSS in developing nations. We haven't connected much with the internationalization (i18n) project, but when we do have something to ask them to translate, I'd like it to be good from the start.
Release Notes!
This is the most needed thing and there are people willing to do it.
I posted the first iteration of the release notes process here:
Oh, I was refering to the i18n project, Release Notes need to be translated.
Could you add me to the EditGroup?
There are also a lot of Wiki Markup errors in almost all Pages :( I'm quite familiar with MoinMoin (the Wiki software) so I think I can help here. I think the Wiki is really the best way for the Release Notes. I could help with automatic conversion to Docbook if needed.