From Fedora Project Wiki

m (1 revision(s))
m (Format edit)
Line 1: Line 1:
= Introduce Yourself to the Docs Project =
= Introduce Yourself to the Docs Project =


When a new writer/editor joins the Documentation Project, we ask that he/she introduces themselves on the [[MailTo(fedora DASH docs DASH list AT redhat DOT com)]  mailing list.  To sign up for the list, visit [http://www.redhat.com/mailman/listinfo/fedora-docs-list the fedora-docs-list signup page] .  The primary purpose of this is to begin the process of building trust by learning about the writer/editor, and downloading their GPG key.
When a new writer/editor joins the Documentation Project, we ask that he/she introduces themselves on the Fedora Docs mailing list.  To sign up for the list, visit [http://www.redhat.com/mailman/listinfo/fedora-docs-list the fedora-docs-list signup page] .  The primary purpose of this is to begin the process of building trust by learning about the writer/editor, and downloading their GPG key.


{| border="1"
{{admon/note|The below items in bold are '''Requested''' while the other items are optional but recommended.|}}
|-
| {{Template:Note}} The below items in bold are '''Requested''' while the other items are optional but recommended.
|}


{{ Template:message/notice | '''IMPORTANT:'''  Translators do not need to do self-introductions on the fedora-docs-list mailing list, and can instead refer to the rest of the information on the [[DocsProject/Translation]]  page.
{{admon/important|Translators do not need to do self-introductions on the fedora-docs-list mailing list, and can instead refer to the rest of the information on the [[DocsProject/Translation]]  page.|}}
}}


The purpose of all this is to break anonymity and foster real-world community within the project.  You are under no obligation to reveal personal secrets.  The objective is to establish a level of trust with yourself and the other members of the project.
The purpose of all this is to break anonymity and foster real-world community within the project.  You are under no obligation to reveal personal secrets.  The objective is to establish a level of trust with yourself and the other members of the project.

Revision as of 15:17, 28 May 2008

Introduce Yourself to the Docs Project

When a new writer/editor joins the Documentation Project, we ask that he/she introduces themselves on the Fedora Docs mailing list. To sign up for the list, visit the fedora-docs-list signup page . The primary purpose of this is to begin the process of building trust by learning about the writer/editor, and downloading their GPG key.

Note.png
The below items in bold are Requested while the other items are optional but recommended.
Important.png
Translators do not need to do self-introductions on the fedora-docs-list mailing list, and can instead refer to the rest of the information on the DocsProject/Translation page.

The purpose of all this is to break anonymity and foster real-world community within the project. You are under no obligation to reveal personal secrets. The objective is to establish a level of trust with yourself and the other members of the project.


A question to keep in mind is:

~+What do you want to know about people before working with and trusting them?+~


Then tell us what you would want to know about yourself.

Subject

  • Self-Introduction: Your Name Here

Body

  • Full legal name (as you use it is fine)
  • City, Country; you may use your timezone if you have a compelling reason not to specify your city or country
  • Profession or Student status
  • Company, School, or other affiliation
  • Your goals in the Fedora Project
  • What do you want to write about?
  • What other documentation do you want to see published?
  • Anything else you'd like to do?
  • Historical qualifications
  • What other projects or writing have you worked on in the past?
  • What level and type of computer skills do you have?
  • What other skills do you have that might be applicable? User interface design, other so-called soft skills (people skills), programming, etc.
  • What makes you an excellent match for the project?
  • GPG KEYID and fingerprint
  • See DocsProject/UsingGpg/CreatingKeys for help and instructions if you don't have a GPG key.
  • 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.
[warren@computer ~] # gpg --fingerprint 54A2ACF1
pub  1024D/54A2ACF1 2002-11-25 Warren Togami (Linux) <warren@togami.com>
Key fingerprint = 785A 304B 08C1 F291 F54F  9A68 6BDD FE8E 54A2 ACF1
sub  2048g/4AD75982 2002-11-25 [expires: 2007-11-24]