From: Michael Tremer <michael.tremer@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Hey guys...
Date: Sat, 10 Aug 2013 14:43:10 +0200 [thread overview]
Message-ID: <1376138590.28398.13.camel@rice-oxley.tremer.info> (raw)
[-- Attachment #1: Type: text/plain, Size: 1954 bytes --]
Hey guys,
on Thursday, Erik sent an email to the Core Developers which said that
he won't have the time to work on the project, because of personal
reasons and that his job requires him to travel a lot in the near
future.
He was the Wiki Coordinator [1] and we have currently been working on
organizing the people who work on the documentation in a better way. The
goal was to raise everybody's awareness about what there is to do, so
that we work together as best as possible.
As more and more volunteers have shown up in the last weeks and month,
(which I am very happy about, by the way) I think that it is becoming
more and more important that the documentation team will finally become
a real "team", which more than just one person.
As long as we don't have a coordinator, I wouldn't like seeing things
going down, so that I am going to take the role for a little while,
until we found solutions for the problems we need to sort out.
This is not intended to go on for more than one or two weeks.
What are those problems?
* We started working on a so called "workflow" [2], which should help to
keep us all on the "same page" - almost literally.
* We are planning to build translation teams, so that the documentation
team and the group of translations are completely independent. This only
makes sense, because they always work independently and status of the
translations also varies a lot.
I am still undecided on how we should handle this, so please feel free
to send me ideas or opinions on this list.
* We have got a whole bunch of things to do at the moment. A lot of new
functionality has been added to the distribution and for parts of that
there is no documentation at all.
So, there is a lot of chaos going on here right now. Now you know the
reasons and I would be happy if we could solve this all together very
soon.
-Michael
[1] http://wiki.ipfire.org/projects/docs/start
[2] http://wiki.ipfire.org/projects/docs/workflow
next reply other threads:[~2013-08-10 12:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-08-10 12:43 Michael Tremer [this message]
[not found] <CAKTTqHNKsmDUa77ijJoTm1jpE6J4DwBSjQ7_7Wc1412wjWP7ZA@mail.gmail.com>
2013-08-10 14:08 ` Michael Tremer
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=1376138590.28398.13.camel@rice-oxley.tremer.info \
--to=michael.tremer@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