From: "Erik K." <ummeegge@ipfire.org>
To: documentation@lists.ipfire.org
Subject: Re: [Documentation] Thinking about to make it easier for all of us ; )
Date: Mon, 09 Jan 2012 15:00:07 +0100 [thread overview]
Message-ID: <4F9E1F80-B2FE-46F8-9210-A3838969A2A7@ipfire.org> (raw)
In-Reply-To: <4F0AC445.40202@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1360 bytes --]
Hi Daniel,
i think this is a quiet good idea, so the inner team structure is more transparent, and if some questions for special themes coming up, there are a list where we can go to find a quicker help.
Where you want to open up this list ?
Greetings
Erik
Am 09.01.2012 um 11:41 schrieb Daniel Weismüller:
> Hi all,
>
> I think everyone knows this. You have a problem or feature request and you don't know which one of us may help you. So I am thinking about to create a short list of funktions and addons in which everyone of us may fill his own knowledge level about it.
>
> Maybe looks like this:
>
> 0: dont know anything about it
> 1: use it but not more
> 2: basic knowledge
> 3: know a lot of it
>
> Feature / WhyTea / Person2 /
> __________________________________
> squid / 2 / 3 /
> snort / 1 / 0 /
> addon1 / 0 / 1 /
>
> So a with a short look we see which one of us may help us in our question.
>
> Of course this list should not be public! It would be only for internal use!
>
> Supplements and opinions are highly appreciated...
>
> yours
>
> Daniel
>
>
>
> _______________________________________________
> Documentation mailing list
> Documentation(a)lists.ipfire.org
> http://lists.ipfire.org/mailman/listinfo/documentation
next prev parent reply other threads:[~2012-01-09 14:00 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-01-09 10:41 [Documentation] Thinking about to make it easier for all of us ;) Daniel Weismüller
2012-01-09 14:00 ` Erik K. [this message]
2012-01-09 22:46 ` [Documentation] Thinking about to make it easier for all of us ; ) Michael Tremer
2012-01-10 10:34 ` Daniel Weismüller
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=4F9E1F80-B2FE-46F8-9210-A3838969A2A7@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