Meeting summary for 5 June 2024:

 * *New, closed: no community meeting on 12 June 2024*
   /Due to an event that a large amount of people will attend, this
   particular day will be inconvenient to do a meeting./
   /Meetings will resume the week after on 19 June 2024./

 * *Updated: Buildbot and t_server null*
   /Builds were failing because worker containers have not been rebuilt./
   /This issue was resolved between mattock and djpig./

 * *Updated: community.openvpn.net trac wiki*
   /It turned out that outline is not really open source, it has BSL
   1.1 license. Not suitable for us./
   /Wiki.js still seems at the moment the direction we want to go. To
   be sure leoossa will present some workflows to test./
   /Based on the results of those tests we can then see where the
   limitations of wiki.js are, and then we can see if those are
   dealbreakers or not./

 * *Updated: release openvpn 2.6.11*
   /Waiting to complete review/merge process of Windows tunnelcrack
   mitigations./
   /Waiting to complete review/merge process of item reported by reynir./
   /Once those items are in we'll prepare for a release, tentatively in
   2 weeks from now./

 * *Updated: DCO and Linux upstreaming, API change*/
   //Upstreaming DCO to Linux is proceeding, it is in review stage at
   the moment.
   ordex will send a *patchset v4* based on feedback received over the
   past days.
   There will be an API change that makes it incompatible with the
   current implementation.
   A graceful solution to that was already discussed and in motion.
   giaan will be working on this.
   (in a nutshell, make OpenVPN understand old and new API, DKMS and
   kernel versions both will then use new API, then we drop old API)/

As always you're welcome to join at #openvpn-meeting on Libera IRC network every Wednesday at 14:00 Central European Time.

Kind regards,
Johan Draaisma
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Reply via email to