From: "Erik K." <ummeegge@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: IPFire Wiki Workflow - list of why it can be interesting to be in a documentation group
Date: Sat, 27 Jul 2013 17:25:41 +0200 [thread overview]
Message-ID: <7E5098A8-86EB-4DCC-8050-4D766338DD2A@ipfire.org> (raw)
In-Reply-To: <1373640925.16036.16.camel@rice-oxley.tremer.info>
[-- Attachment #1: Type: text/plain, Size: 983 bytes --]
Hi all,
i want to begin with a list of why it can be interesting to become a member in the documentation group ;-). May this can sometimes be used for a round mail or something...
- Be an important part of the development of IPFire by doing tests (quality management) of the new developed software while writing a documentation for end users.
- Lern more about IPFire by documenting IPFire.
- Support a good project ;-)
- Know more about software which are used in this project.
- Give better support to people who needs help in the forum --> become a supporter.
- Learn to make a good teamwork with other people.
- Extend your know-how.
- Make your language skills better.
- Meet new people, which are also involved by developing IPFire.
- Let´s lern more about the wiki code :-\
- In that way, the project benefits also from you... ---> thats how OpenSource works.
This only as a first idea. Please change or extend this list.
Greetings
Erik
next prev parent reply other threads:[~2013-07-27 15:25 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <D8D682F2-7C9C-4962-AA0E-9AD00D3D5003@ipfire.org>
2013-07-12 14:55 ` IPFire Wiki Workflow Michael Tremer
2013-07-27 15:25 ` Erik K. [this message]
2013-07-27 16:00 ` Erik K.
2013-07-27 16:50 ` Erik K.
2013-07-28 16:27 ` Michael Tremer
2013-07-12 17:50 ` R. W. Rodolico
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=7E5098A8-86EB-4DCC-8050-4D766338DD2A@ipfire.org \
--to=ummeegge@ipfire.org \
--cc=documentation@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox