public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: DJ Lucas <dj@lucasit.com>
To: development@lists.ipfire.org
Subject: Re: IPFire-3.x Images
Date: Thu, 21 Mar 2019 04:12:49 +0000	[thread overview]
Message-ID: <7b2b568c-2890-839d-6328-ae25e3485718@lucasit.com> (raw)
In-Reply-To: <1552843042.3.0@ipfire.org>

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



On 3/17/2019 12:17 PM, Jonatan Schlag wrote:
> 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

Should be: https://git.ipfire.org/?p=pakfire.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.
>
While I do not have the time right this second, I'd like to jump in and 
assist when other work lulls. Thank you for the update and please 
continue to keep them coming. It'll help those who are not part of the 
core team to be able to jump in and assist where/when they can. I 
suspect many more than have replied are watching, and eagerly awaiting 3.x.

--DJ


      reply	other threads:[~2019-03-21  4:12 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-16  9:39 Jonatan Schlag
2019-02-17 17:28 ` ummeegge
2019-02-17 20:05   ` Tom Rymes
2019-02-18 12:14     ` Michael Tremer
2019-03-17 17:17       ` Jonatan Schlag
2019-03-21  4:12         ` DJ Lucas [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=7b2b568c-2890-839d-6328-ae25e3485718@lucasit.com \
    --to=dj@lucasit.com \
    --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