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: Re: Unterstützung
Date: Wed, 26 Dec 2012 17:18:38 +0100	[thread overview]
Message-ID: <1356538718.8107.81.camel@rice-oxley.tremer.info> (raw)
In-Reply-To: <50DAE2A2.8080107@morlix.de>

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

Hey Timo,

I am replying in English, because that is the language of this list.

On Wed, 2012-12-26 at 12:42 +0100, morlix wrote:
> Hallo zusammen,
> 
> ich verwende jetzt schon ziemlich lange IPFire und bin eigentlich mit
> dem Produkt sehr zufrieden.
> 
> Was mich allerdings etwas stört, ist die meiner Meinung nach schlechte
> Reaktion auf Hilfe die ich anbiete, wobei ich mit dieser Email gerne
> auch erfahren will, was ich eventuell falsch gemacht habe.

First of all, you did not make anything wrong. In fact, it is very good
to create bugs in the bugtracker with really important tasks. Bugs have
the advantage, that we don't forget about them.

> Ich meine damit folgendes. Ich habe 2 Bugs im Bugtracker geöffnet und
> niemand bearbeitet diese, obwohl es meiner Meinung nach kein großer
> Aufwand wäre.

Currently, the IPFire developers are busy. And in addition, it's
Christmas, which means that in December there is not going anything on.

Despite celebrating the holidays, we are making the finishing touches on
IPFire 2.13 and we are also working a lot on IPFire 3. A lot of this
work is totally invisible to most people - which is a bit sad, but it
still needs to be done.

The first thing that we drop are the "little beans", i.e. bug reports
that do minor changes. If we would focus on them, we wouldn't have a
chance to push through big changes. The world evolves very fast and
keeping up with that is a thing were a lot of work is being put it.
Constantly. Hours. Every day.

Keep that in mind. Some people try to push us doing things we scheduled
in a different order and this often leads to not doing anything at all.
At last, we are all volunteers.

> Es geht dabei um folgende Bugs:
> 
> 10065 New Bacula 5.2.6 FileDaemon Addon
> (https://bugzilla.ipfire.org/show_bug.cgi?id=10065)
> 10233 Severall small improvements for the backiso script
> (https://bugzilla.ipfire.org/show_bug.cgi?id=10233)
> 
> Also die konkrete Frage ist, was muss ich tun oder ändern, damit das was
> ich als Unterstützung einreiche auch Beachtung findet.

What you did is exactly the right thing. Do as much work on your own as
possible. If you got stuck with a problem, ask for help. But don't
expect the developers to solve your problems. We have got our own.

In this particular problem: #10223 won't be merged into IPFire 2.13,
because that one is frozen. We only fix bugs.

The other one is more complicated. The patch is around since March and
has been assigned to Arne. He will eventually do what has to be done
with it, but that is a lot of work. Because no one uses Bacula and hence
it is hard to test what you have been done there.
The best thing you could do is to distribute a binary version of this
add-on and get more people to test it. If we have the evidence that more
people successfully tested this add-on, we don't have to do much testing
on our own.

> Ich frage dies deshalb, da ich in meinem ipfire 2.x clone an den
> conntrack-tools, einem update für Bacula und check_mk für IPFire arbeite
> und ich diese Arbeit gerne in euer Projekt einfließen lassen würde.

Of course we value the work that you are doing. Even if we are very
quiet about that.

> Mir ist klar das ihr lieber Supporter hättet die sehr aktiv in Forum und
> Maillingliste sind, aber ich habe selbst sehr viel zu tun mit meiner
> Arbeit und daher kann ich nur anbieten was ich eben nebenher noch
> leisten kann.

Everyone does as much as possible and if we keep that in mind and live
by that every day, we will get things solved very soon.

Thanks for your post. I will write some more comments on the bugs about
problems I have with them.

Have a Merry Christmas,
-Michael


  reply	other threads:[~2012-12-26 16:18 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-12-26 11:42 Unterstützung morlix
2012-12-26 16:18 ` Michael Tremer [this message]
2012-12-27  8:50   ` Unterstützung morlix
2013-01-05 12:31     ` Unterstützung Michael Tremer
2013-01-06 14:42       ` Unterstützung morlix

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