On Mon, 2007-05-21 at 03:52 -0700, Karsten Wade wrote: > On this page: > > http://fedoraproject.org/wiki/Join > > It previously said "Content Developer" for this link: > > http://fedoraproject.org/wiki/Join#ContentDeveloper > > Where it says, "Description of this role: Communicate through words." > > So why don't we say "Technical Writer"? Well, I did update the role > today to say "Content Developer (Writer)" instead, so at least it's not > deceiving. > > One reason is to maintain the developer/contributor paradigm -- everyone > is a developer. > > Another is to align with new industry standards. > > Yet, I have personally had problems with this label, so I am mixed about > the usage. The main reason is that most job roles look for "technical > writing" skills, which are specific to technical roles/needs. A > "content developer" could be developing content about toothpaste and cat > food; there is nothing in the title that specifies that it is focused on > the technical aspects. > > Your thoughts? Do you care? Meh. No strong feelings either way -- I doubt anyone comes to our site to learn about cat food, but certainly if we are interesting in capturing into our contributor base folks specifically looking for "Technical Writer" via google or elsewhere, this seems like a good idea. -- Paul W. Frields, RHCE http://paul.frields.org/ gpg fingerprint: 3DA6 A0AC 6D58 FEC4 0233 5906 ACDB C937 BD11 3717 Fedora Project: http://fedoraproject.org/wiki/PaulWFrields irc.freenode.net: stickster @ #fedora-docs, #fedora-devel, #fredlug
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-docs-list mailing list fedora-docs-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-docs-list
