From mboxrd@z Thu Jan 1 00:00:00 1970 From: Jonatan Schlag To: development@lists.ipfire.org Subject: Re: IPFire-3.x Images Date: Sun, 17 Mar 2019 18:17:22 +0100 Message-ID: <1552843042.3.0@ipfire.org> In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============4529838993106521347==" List-Id: --===============4529838993106521347== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi, a long time has passed since the last E-Mail in this thread but as some=20 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=20 kind of work needs to be currently done and who is working on what. (by=20 ummeegge) The following will be a short overview of who is doing what now (or=20 tries to do): Michael Tremer: Is currently working on the new build system=20 (https://pakfire.ipfire.org/) and the port to python3. You can see the changes here: https://git.ipfire.org/?p=3Dnetwork.git;a=3Dsummary This is something where we can not really help. He is also working on the network: https://git.ipfire.org/?p=3Dnetwork.git;a=3Dsummary Arne Fitzenreiter: Builds a new kernel and doing some stuff for=20 WIFI : =20 https://git.ipfire.org/?p=3Dipfire-3.x.git;a=3Dsearch;h=3Drefs/heads/master;s= =3DArne+Fitzenreiter;st=3Dauthor This is also a task were can not really help Peter M=C3=BCller: He is updating some packages. This is a task which=20 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.=20 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: =20 https://git.ipfire.org/?p=3Dipfire-3.x.git;a=3Dsearch;s=3DStefan+Schantl;st= =3Dauthor Jonatan Schlag: I am working in my currently very limited time on=20 the VPN (IPSEC) https://git.ipfire.org/?p=3Dnetwork.git;a=3Dsummary=20 and the network in general. Another big working Area is NITSI: https://git.ipfire.org/?p=3Dnitsi.git;a=3Dsummary I=20 will explain this word later. Another thing is building an image which=20 is available under the known link. Which work needs to be done currently: - Updating packages (a Guide can be found here:=20 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=20 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,=20 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=20 networks also defined in a config file. Then it connects to each machine via serial console and executes network commands on it. These commands=20 are defined in a recipe file. Example:=20 https://git.ipfire.org/?p=3Dnetwork.git;a=3Dblob;f=3Dtest/nitsi/test/zone-po= rt-attach bridge/recipe;h=3D4efbd184de78f32ea42034e7cc7f19efb3e7b32a;hb=3Drefs/heads= /master) These tests need to be written and everybody can do that. So only=20 thing to run these tests is to install NITSI from git and run the following command in a network repository=20 (https://git.ipfire.org/?p=3Dnetwork.git;a=3Dsummary): make nitsi test/nitsi/test/zone-port-attach-bridge This is a good starting point to play around with this new tool. A=20 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=20 have a short overview of what needs to be done and who is working on=20 what. Jonatan Am Mo, 18. Feb, 2019 um 1:14 P. M. schrieb Michael Tremer=20 : > Hi, >=20 > I do not really want to bring down the excitement, but IPFire 3 is no=20 > where near ready for production. >=20 > This image is rather the status from last autumn when we had our last=20 > developer summit. Since then, literally nothing has happened in=20 > regard of IPFire 3. There is just no time to work on that. >=20 > As Jonatan has said, all of our time is very limited and we are=20 > putting every minute into IPFire 2 to at least keep that running=20 > well. Unfortunately that has become more time in the past since I=20 > have the feeling that we are getting less and less feedback from=20 > testers and so on. >=20 > The time that we do spend on IPFire 3 is rather on regrouping and=20 > finding the spot where we stopped working because too much time=20 > passes between those two points in time. So far we have failed to=20 > continue working on it a little bit every single day=E2=80=A6 >=20 > But, there is also good news=E2=80=A6 I always tend to talk about the=20 > downsides of all of this, but actually there is more positive things=20 > to say about IPFire 3: >=20 > * We have an amazing build system - which is not bug-free but doing a=20 > much better job than what we have in IPFire 2 >=20 > * Networking is working really well. It is powerful, has loads of=20 > features. We just need to round it off a little bit. >=20 > * The OS is modern, small and faster than IPFire 2. >=20 > If you want to toy around with the networking, here is the=20 > documentation: https://man-pages.ipfire.org/network/ >=20 > Please report any bugs, please talk about IPFire 3. I am happy to=20 > help out and answer questions :) >=20 > -Michael >=20 >> On 17 Feb 2019, at 20:05, Tom Rymes wrote: >>=20 >>=20 >>> On Feb 17, 2019, at 12:28 PM, ummeegge wrote: >>>=20 >>> On Sa, 2019-02-16 at 10:39 +0100, Jonatan Schlag wrote: >>>>=20 >>>> 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=20 >>> kind >>> of work needs to be currently done and who is working on what. >>=20 >> I=E2=80=99d also like to have a better feel for what are the items that=20 >> need attention before 3.x can be released. It has long been that=20 >> =E2=80=9CIPFire 3 is coming soon", but it=E2=80=99s unclear what work is n= eeded=20 >> where to get to the next step. >>=20 >> Tom >=20 --===============4529838993106521347==--