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: TODO list for IPFire 3 ?
Date: Fri, 10 Apr 2020 15:28:27 +0100	[thread overview]
Message-ID: <4CE1222C-C9DF-463A-8CEF-CC545D3E6065@ipfire.org> (raw)
In-Reply-To: <20200408122854.GA88526@hellisempty.reich.home.arpa>

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

Hey Stephan,

Thank you for writing and apologies for my late reply.

> On 8 Apr 2020, at 13:28, Stephan Mending <list(a)md5collisions.eu> wrote:
> 
> Hi everybody, 
> I was wondering if there was any kind of todo list for IPFirev3 ? 
> For people like me who would like to get started ? 

Yes, there kind of is, but only on a very high level.

The distribution cannot be built right now because our build system is down and I lack time to have a look at it and bring it all back to work.

> I've found such a list neither in the wiki nor in bugzilla. (Though I found a few unrelated bugs). 

There are plenty of bugs in BZ for IPFire 3.

> Do those tasks come naturally to you as soon as you've configured your 3 ? 

No, there is no setup process yet, no images. So won’t be very obvious what to do.

There is a short quick start guide on the networking: https://man-pages.ipfire.org/network/network-quick-start.html

> Do you have any kind of definition when version 3 is good for release ? Which features have to be available? 

It lacks a build system, a firewall and a web UI. So we are very far away from release.

Nobody of the core developers has substantially touched the distribution in years.

> Which functionalities are required ? Anything in that direction ? I'd guess there is.. I'm just overlooking something again. 
> 
> Best regards, 
> Stephan

Sorry for all this bad news, but right now what would help the project is keeping development of IPFire 2 going and fix all those nasty bugs so that they won’t hold us back any longer.

Best,
-Michael


      reply	other threads:[~2020-04-10 14:28 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-08 12:28 Stephan Mending
2020-04-10 14:28 ` Michael Tremer [this message]

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=4CE1222C-C9DF-463A-8CEF-CC545D3E6065@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