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 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.

The below items in bold are Requested while the other items are optional but recommended.

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: Alexey

Body

• Alexey
• Minsk, BElarus
• IT TV Specialist
• TVR.by
• I'm just new one, but this project is really interesting gor me. Unfortunately i didn't find a lot of information abou this project and system on russian, so it would be very beautiful if i could change it.
• I could write small reviews, tips, etc on russian
• All kind of information what's helps to suite Fedora to just users.
• Translation, help?
• I'm a new one
• What other projects or writing have you worked on in the past?

no one, but i'm really want to try.

• What level and type of computer skills do you have?

At least Superuser.

• What other skills do you have that might be applicable? User interface design, other so-called soft skills (people skills), programming, etc.

I'm familliar with programming, but i'd like to focus on writing.

• What makes you an excellent match for the project?

A big wish to work as Doc writer.

• 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] 

---