Hi,

a long time has passed since the last E-Mail in this thread but as some 
Questions are still open, I want to try to answer some of them.

1. It might be helpful to know a little more about the insides which 
kind
of work needs to be currently done and who is working on what. (by 
ummeegge)

    The following will be a short overview of who is doing what now (or 
tries to do):

    Michael Tremer: 	Is currently working on the new build system 
(https://pakfire.ipfire.org/) and the port to python3. You can see the
			changes here:
			https://git.ipfire.org/?p=network.git;a=summary
                        This is something where we can not really help.
                        He is also working on the network:
                        https://git.ipfire.org/?p=network.git;a=summary

    Arne Fitzenreiter: 	Builds a new kernel and doing some stuff for 
WIFI :
                        
https://git.ipfire.org/?p=ipfire-3.x.git;a=search;h=refs/heads/master;s=Arne+Fitzenreiter;st=author
                        This is also a task were can not really help

    Peter Müller: 	He is updating some packages. This is a task which 
everybody can do and should do. So If you update a package in IPFire-2.x
                    	please also update this package on IPFire-3.x. 
This task is currently a bit hard as the build system has some bugs, but
			Michael is working on that.

    Stefan Schantl: 	Also updating packages:
                    
	https://git.ipfire.org/?p=ipfire-3.x.git;a=search;s=Stefan+Schantl;st=author

    Jonatan Schlag: 	I am working in my currently very limited time on 
the VPN (IPSEC)
                    	https://git.ipfire.org/?p=network.git;a=summary 
and the network in general. Another big working Area is NITSI:
                    	https://git.ipfire.org/?p=nitsi.git;a=summary I 
will explain this word later. Another thing is building an image which 
is
			available under the known link.

Which work needs to be done currently:

    	- Updating packages (a Guide can be found here: 
https://wiki.ipfire.org/devel/start)
    	- Writing tests for NITSI, so what is NITSI?
    	NITSI is the Network Integration Test Suite for Ipfire. It is a 
program which can execute commands over a serial console in a virtual
	machine. We developed it to test the network code on a higher level, 
then it is possible without a running IPFire-3.x machine. So do run a
	test, NITSI starts several machines defined in a config file and 
networks also defined in a config file. Then it connects to each machine
	via serial console and executes network commands on it. These commands 
are defined in a recipe file.
    	Example: 
	https://git.ipfire.org/?p=network.git;a=blob;f=test/nitsi/test/zone-port-attach
			bridge/recipe;h=4efbd184de78f32ea42034e7cc7f19efb3e7b32a;hb=refs/heads/master)

    	These tests need to be written and everybody can do that. So only 
thing to run these tests is to install NITSI from git and run the
	following command in a network repository 
(https://git.ipfire.org/?p=network.git;a=summary):

	make nitsi test/nitsi/test/zone-port-attach-bridge

    	This is a good starting point to play around with this new tool. A 
guide what tests needs to be written and how exactly you can do that
	will be added to the wiki (hopefully soon).


This E-Mail is incomplete in several ways (NITSI guide) but I hope you 
have a short overview of what needs to be done and who is working on 
what.

Jonatan



Am Mo, 18. Feb, 2019 um 1:14 P. M. schrieb Michael Tremer 
<michael.tremer(a)ipfire.org>:
> Hi,
> 
> I do not really want to bring down the excitement, but IPFire 3 is no 
> where near ready for production.
> 
> This image is rather the status from last autumn when we had our last 
> developer summit. Since then, literally nothing has happened in 
> regard of IPFire 3. There is just no time to work on that.
> 
> As Jonatan has said, all of our time is very limited and we are 
> putting every minute into IPFire 2 to at least keep that running 
> well. Unfortunately that has become more time in the past since I 
> have the feeling that we are getting less and less feedback from 
> testers and so on.
> 
> The time that we do spend on IPFire 3 is rather on regrouping and 
> finding the spot where we stopped working because too much time 
> passes between those two points in time. So far we have failed to 
> continue working on it a little bit every single day…
> 
> But, there is also good news… I always tend to talk about the 
> downsides of all of this, but actually there is more positive things 
> to say about IPFire 3:
> 
> * We have an amazing build system - which is not bug-free but doing a 
> much better job than what we have in IPFire 2
> 
> * Networking is working really well. It is powerful, has loads of 
> features. We just need to round it off a little bit.
> 
> * The OS is modern, small and faster than IPFire 2.
> 
> If you want to toy around with the networking, here is the 
> documentation: https://man-pages.ipfire.org/network/
> 
> Please report any bugs, please talk about IPFire 3. I am happy to 
> help out and answer questions :)
> 
> -Michael
> 
>>  On 17 Feb 2019, at 20:05, Tom Rymes <trymes(a)rymes.com> wrote:
>> 
>> 
>>>  On Feb 17, 2019, at 12:28 PM, ummeegge <ummeegge(a)ipfire.org> wrote:
>>> 
>>>  On Sa, 2019-02-16 at 10:39 +0100, Jonatan Schlag wrote:
>>>> 
>>>>  As stated time is limited and 4 persons are not enough to build
>>>>  IPFire-
>>>>  3.x.  To push the development of IPFire-3.x it would be cool If
>>>>  everybody would thinking about working on this next major version
>>>>  too.
>>>  It might be helpful to know a little more about the insides which 
>>> kind
>>>  of work needs to be currently done and who is working on what.
>> 
>>  I’d also like to have a better feel for what are the items that 
>> need attention before 3.x can be released. It has long been that 
>> “IPFire 3 is coming soon", but it’s unclear what work is needed 
>> where to get to the next step.
>> 
>>  Tom
>