public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: [Development] What is this all about?
Date: Wed, 01 Feb 2012 12:56:16 +0100	[thread overview]
Message-ID: <1328097376.3694.18.camel@rice-oxley.tremer.info> (raw)

[-- Attachment #1: Type: text/plain, Size: 1709 bytes --]

Hi,

some of you may wonder what this mailing list is all about. Let me
explain this in a few lines:

I have been asked by a lot of people recently why there is no
development mailing list. We had wonderful experience with the
documentation mailing list and the SIG-ARM mailing list too so we
thought we will give it a try and discuss our development stuff on such
a thing, too.

It should replace the development section in the forums, because the
forum is getting busier and busier every day and personally I am not
able to keep track of all the things that are going on there. As the
team has grown, it is no longer necessary, that the core developers
answer every single thread and tell users how to do basic things. So I
do not even want to handle the overhead of all those support threads and
make discussions more linear and searchable. Please prepare that the
development section on the forums will be closed soon.

We are also getting more and more people who have interest in developing
stuff for the IPFire system. This is a good place for them to start and
get involved into the project.

If there are very *hot* topics like ARM or VPN, there will be SIG-*
lists where those things are discussed to take traffic away from the
primary list which is this. You don't need to be concerned that you are
getting too many mails.

I am going to stop here, although I have lots advantages more to tell
you. The feedback from the doc mailing list has been all positive and
let's see if we this is working out for the development stuff, too. So I
need everyone to get familiar with the mailing list and how to post
messages and reply to them. Maybe somebody is coming forward with a
short guide?

 -Michael


                 reply	other threads:[~2012-02-01 11:56 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=1328097376.3694.18.camel@rice-oxley.tremer.info \
    --to=michael.tremer@ipfire.org \
    --cc=development@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