content developer, writer, oh my!

[Karsten Wade]

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?

- Karsten
-- 
   Karsten Wade, 108 Editor       ^     Fedora Documentation Project 
 Sr. Developer Relations Mgr.     |  fedoraproject.org/wiki/DocsProject
   quaid.108.redhat.com           |          gpg key: AD0E0C41
////////////////////////////////// \\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\\
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 189 bytes
Desc: This is a digitally signed message part
URL: <http://listman.redhat.com/archives/fedora-docs-list/attachments/20070521/d2a338be/attachment.sig>