From: Frank Mainz <frank@cybermainzel.de>
To: development@lists.ipfire.org
Subject: Re: [PATCH] New package: IPTraffic 0.8.2
Date: Mon, 25 Jan 2021 21:58:30 +0100 [thread overview]
Message-ID: <c184e2ccbc8d2513fff3a7138456127e8ca5588e.camel@cybermainzel.de> (raw)
In-Reply-To: <8FF22F1B-04FF-421D-92D7-70E408059B3C@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 3690 bytes --]
Michael,
I had not answered without reason only privately.
Throw away the AddOn. Forget it.
unfortunately you can't unsubscribe with a simple "unsubscibe".
What is a spam filter for.
Am Montag, den 25.01.2021, 20:48 +0000 schrieb Michael Tremer:
> Hello Frank,
>
> > On 25 Jan 2021, at 20:22, Frank Mainz <frank(a)cybermainzel.de>
> > wrote:
> >
> > Am Montag, den 25.01.2021, 20:05 +0000 schrieb Michael Tremer:
> > > Hi Frank,
> > >
> > > Thank you for your email, but it didn’t answer any of my
> > > questions.
> > >
> > > I wasn’t aware of the wiki pages, but I had a look at it.
> > >
> > > The questions from my previous email remain though. I do not
> > > think a
> > > single one was answered.
> >
> > That is not my problem.
>
> Okay, I am sorry, but I would have to vote to reject this patch then.
>
> It is very important that we review all code that is going into the
> distribution and that we have a reason that it is there. Code that is
> redundant, not needed and unmaintained is a potential security
> problem. I am sure this is very easy to understand.
>
> Also, you can read here what it takes to get your patches into the
> distribution:
>
> https://wiki.ipfire.org/devel/submit-patches
>
> This is not there for our own entertainment. It is a tested and tuned
> process which guarantees that IPFire is a product of very high
> quality.
>
> > > > On 25 Jan 2021, at 19:51, Frank Mainz <frank(a)cybermainzel.de>
> > > > wrote:
> > > >
> > > > Hello Michael,
> > > >
> > > > look in the WIKI and you know what is displayed. Otherwise, the
> > > > traffic
> > > > of individual IP addresses is logged with the help of entries
> > > > in
> > > > the
> > > > CUSTOM chains and graphically prepared.
> > >
> > > The CUSTOM* chains can’t be touched by any programs that come
> > > with
> > > the distributions. They exist for users to add any custom rules
> > > and
> > > they are under full control by the user only.
> >
> > Then it does fit.
>
> No, it doesn’t, because you are not the user of all those firewalls.
>
> Every chain has a defined purpose, and you are using it for something
> it isn’t designed for and it will break setups.
>
> > > > https://wiki.ipfire.org/addons/iptraffic-playground
> > > >
> > > >
> > > > Greetings Frank
> > > >
> > > > PS: Fullquote removed
> > >
> > > Why? I don’t recommend doing this because it removes context from
> > > the
> > > conversation.
> > >
> > > Best,
> > > -Michael
> >
> > Then be careful next time not to quote >100 lines of source code.
> > How
> > this is supposed to preserve context is beyond me.
>
> Because we write comments into the code. And we normally try to
> answer other people’s questions.
>
> Do not forget that many people are reading this list and they do not
> devote a lot of time to get themselves involved in everything.
> Therefore things have to be understood at a quick glance.
>
> > But do what you want. Exactly because of such reactions I didn't
> > want
> > to port the AddOn for IPFire.
>
> I have absolutely no idea why you are reacting like this. The process
> is clear and I am here to make IPFire as good as I can possibly do.
>
> I have simply asked what your code is and what it does. You seem to
> not want to answer those questions and why is unfortunately beyond
> me.
>
> > Have a nice life. I am out.
>
> Under those circumstances I must say that I find it very
> disappointing that you have wasted my time and Matthias’ time, too. I
> have re-read my email and I do not see why this might have caused any
> offence.
>
> I assume that nobody else wants to push this forward any more and
> maintain this code?
>
> -Michael
next prev parent reply other threads:[~2021-01-25 20:58 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <2cc215c55a63d98924de4db8780ebf7ca89aefd7.camel@cybermainzel.de>
2021-01-25 20:48 ` Michael Tremer
2021-01-25 20:58 ` Frank Mainz [this message]
2021-01-25 21:01 ` Michael Tremer
2021-01-25 21:50 ` Aw: " Bernhard Bitsch
2021-01-26 11:38 ` Michael Tremer
2021-01-17 17:15 Matthias Fischer
2021-01-25 19:27 ` Michael Tremer
2021-01-25 19:51 ` Frank Mainz
2021-01-25 20:05 ` Michael Tremer
2021-01-26 16:45 ` Matthias Fischer
2021-01-27 11:32 ` Michael Tremer
2021-01-27 18:36 ` Matthias Fischer
2021-01-28 10:08 ` Matthias Fischer
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=c184e2ccbc8d2513fff3a7138456127e8ca5588e.camel@cybermainzel.de \
--to=frank@cybermainzel.de \
--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