From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: The parallel projects (was Re: Apache 2.4 and php 5.6 test branch)
Date: Wed, 20 Jan 2016 23:43:09 +0000 [thread overview]
Message-ID: <1453333389.585.4.camel@ipfire.org> (raw)
In-Reply-To: <1453291479.2200.0@smtp.1und1.de>
[-- Attachment #1: Type: text/plain, Size: 2279 bytes --]
Hello,
thank you for your comment.
I pretty much agree despite that I am not the only maintainer of IPFire
2 and IPFire 3. We should move on to IPFire 3 as soon as possible so
that we can use the benefits of the build system and the social
development process we have built there.
Best,
-Michael
On Wed, 2016-01-20 at 13:04 +0100, Jonatan Schlag wrote:
> Hi all,
>
> I am a user of IPFire, but i also develop ( in the moment for me
> alone), things which i need.
> It is no easy to follow this conversation, so if do not cover
> anything I just do this because the discussion is to big o comment it
> at once and I think this is not necessary.
> In the moment I see Michael Tremer, which is Maintainer of the
> “whole” project. And I see a lot of other people here and in the
> forum which contribute, and want to contribute.
> That the people want to contribute is simple great.
> The problem is from my point of view the way how they do that and how
> the whole project “work!” in the moment. Please do not misunderstand
> me, the last thing what I want is to say this is your or you fault. I
> know enough situation where people do that and make only noise, but
> do not solve any Problems.
> So I do not think that these parallel projects should be separated,
> this only split the energy, and this is not good. What I think is
> that I should be clear who is appropriate for this or for these.
> Michael is not appropriate for maintain every thing and write
> thousand of E – Mails. He is appropriate for the core.
> When people development a addon they should maintain it. I know that
> IPFire a firewall router is but some addons may be useful. Not for
> everyone but for some people they are useful. So they could be
> developed, but should not be maintained by the core developers. The
> core developers should maintain the core and nothing else.
> So maybe is is a solution to drop every addon which has no maintainer
> (this is a very hard way).
> But for this we need a information in the lfs files like in IPFire 3
> # maintainer = Jonatan Schlag (jonatan(at)familyschlag.de)
> So it is more clear which person is appropriate for which thing.
>
> So this are some thoughts form my side. I hope they are useful.
>
> Yours Sincerely Jonatan Schlag
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next parent reply other threads:[~2016-01-20 23:43 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1453291479.2200.0@smtp.1und1.de>
2016-01-20 23:43 ` Michael Tremer [this message]
[not found] <25A90500-70D9-4904-A434-6DE9AB6007FA@gmail.com>
2016-01-23 11:33 ` Michael Tremer
2016-01-23 2:19 Michael Tremer
2016-01-23 7:23 ` R. W. Rodolico
[not found] <24C74A6E-65D3-471E-8F83-9EFABBD57DC4@ipfire.org>
2016-01-19 11:41 ` Michael Tremer
2016-01-20 7:50 ` ummeegge
2016-01-20 23:25 ` Michael Tremer
[not found] <C88CCB4C-7B6E-458A-9BCF-7A1AD320F99D@gmail.com>
2016-01-19 11:28 ` Michael Tremer
[not found] <56966461.3090401@ipfire.org>
2016-01-19 1:16 ` Michael Tremer
2016-01-19 20:56 ` David J. Allen
2016-01-19 21:59 ` R. W. Rodolico
2016-01-19 22:11 ` Larsen
2016-01-19 23:25 ` Michael Tremer
2016-01-20 1:02 ` R. W. Rodolico
2016-01-20 14:58 ` Michael Tremer
2016-01-19 23:05 ` 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=1453333389.585.4.camel@ipfire.org \
--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