My name is Shajia Khan . I am a student of Technical Communication, Seneca
College, Toronto. From the January 2009 till April 2009 I will have my co-op
semester and I am planning to work with Fedora project in the area of
documentation writing and editing to gain my co-op experience.
My educational background is basically in English. I have done my bachelors
in English language and literature. Then I worked as a news paper reporter
for a while and then worked as language teacher in middle school. After
that, I did my M.A. in Applied Linguistics from Carleton University, Ottawa.
I worked for a linguistic consultant for a company in Calgary for a year. I
worked as a teacher in various educational settings. Then I enrolled in
Seneca College to make a career change. I am planning to become a technical
writer because I believe as a teacher my main object was to convey complex
ideas to my students in simple terms. Here as a technical writer I will be
doing the same.
I have summed up my experiences and knowledge which will bring result to
My working experience as a writer: I wrote in news paper articles. As a
teacher I wrote handouts, course outlines and even teaching units which are
very similar to the technical documents.
My experience in editing: As a teacher I had to review my students writing
and help them to write in correct English. Moreover the course in Editing
and Style in Seneca had brushed up those editing skills and taught me some
tools especially on how to edit in an electronic document.
The technical know -how: The technical communication course in Seneca
taught me some key concept in documentation. For example, task analysis,
user analysis, writing a procedure, technical description, technical
specification, software lifecycle etc. It will enable me to be familiarized
in the term.
Communication Skills: As I mentioned earlier, as a teacher my key
responsibility was to explain complex ideas into simple terms. I believe
that is very crucial when someone works as a technical writer.
I will be able to work full time for Fedora, so I am looking for lots and
lots of works!
I think there are some great documents on /wiki/Docs/Drafts/, but
these are hard to find:
2. Click "Docs"
3. I might be impatient, but I can't actually find the link to the
drafts (I know it is there somewhere though)
4. phail :-)
2. support -> documentation
3. Admire pretty list of documentation that desktop users and
non-Linux people probably want to know.
2. Click Discover it
3. Click Documentation (lots of clutter, but I found it easy to find).
4. Nice list of links. Looks pretty
It seems the Fedora process is too formal and too hung up on having
'professional documentation', that all the useful information gets
left behind on wiki drafts where people aren't going to look. Maybe
instead of the fedora admin guide , the drafts sections could be
turned into mini howtos?
Sorry if I sound grumpy :-)
I would be happy to convert
to DocBook if it could be placed somewhere other than in the drafts
David Nalley (ke4qqq)
Paul W. Frields (stickster)
John McDonaugh (jjmcd)
Susan Lauber (laubersm)
Karsten Wade (quaid)
Doran L. Barton (fozzmoo)
Brian Pepple (bpepple)
David Woodhouse (dwmw2_yoyo)
Thorsten Leemhuis (knurd)
Francesco Ugolini (fugolini)
* Continued confusion over timing -- do we switch with DST or not?
Discussion carried to fedora-advisory-board to set a project wide
* Discussed knurd's post on the release notes. Some ideas we can do
fairly easily (single HTML page), others require effort where
resources are few:
* Formed a page to track which standard operating procedures (SOP) we
need for the future, which include items culled from knurd's blog post:
* Lessons learned:
- Too much process in the heads of too few -- fix how-to-help docs.
- More rigorous schedule for release notes updates via web and RPM
- Need to improve docs on how to manage a beat
ACTION: quaid and stickster working on Docs team content
improvements by mid-December; page renaming is a dependency.
* Virtual classroom and hackfest on tools, docs, wiki gardening over
the Holidaze break -- use
http://fedoraproject.org/wiki/Communicate/IRC/Classroom, Gobby, and VoIP.
ACTION: Sparks to organize via list
* Training on Docs tools and processes at FUDCon.
* Page renaming, include page owner via category: [[:Category:Username
is responsible for this page]]
Karsten 'quaid' Wade, Community Gardener