Meeting summary for 17 April 2024:

 * *New: updated 2.6.10 with new MSI installers*
   /There is a new Windows DCO driver that should handle coming back
   from hibernation better/faster, as it doesn't wait for keepalive
   timeout after hibernation./

 * *New: --topology directive*
   /We changed the default for this to be 'subnet' as this is the most
   commonly used setup and has been for ages (used to be net30)./
   /This is however breaking things by default for peer to peer setups.
   We could limit the change to just --server mode./
   /djpig will propose a patch and it can be discussed further there./

 * *Closed: live route update feature*
   /In short, the ability to update routes, DNS, ifconfig options,
   live, without having to do a full reconnect./
   /After discussing last week seems like a path forward is clear./

 * *Updated: Security mailing list procedure can stand improvement*
   /company will improve process on picking up tasks from security
   mailing list in the next week or so./
   /The idea being that community guys will continue doing their thing
   as usual, and company guys monitor the list for company related
   items and follow up on those./
   /The idea of an NDA is also revived. But it was made clear
   internally that we need like a one-page simple NDA for community
   members, not the unnecessarily restrictive one originally suggested
   by legal guys./

 * *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 v3 based on feedback received today./
   /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)//

 * *Updated: donation collection*
   /From earlier exploration it is clear that setting up a legal entity
   is not worth the expense at this point. We're just starting out with
   donations./
   /What we can do is start out with an existing company that can
   collect the money and puts it to good community use. ordex
   volunteers to take this on./
   /There are some options to consider. There may be existing solutions
   that we want to consider./
   /PayPal? <https://community.openvpn.net/openvpn/wiki/PayPal>seems
   overly expensive with all their fees./
   /Stripe could be worth considering for credit card processing./
   /GitHub? <https://community.openvpn.net/openvpn/wiki/GitHub>Sponsors
   was mentioned as a possible solution, this is worth investigating./
   /Open Collective was also mentioned, that needs some investigating
   how that exactly would work for us./

 * *Updated: forums topics*
   /ecrist still working on forums. waiting on ecrist to move things
   around./
   /Plan is to soon switch URLs so new forum is on forums.openvpn.net
   and old forums is on archive address./
   /- email confirmation on registration was suggested./
   /- mod guide, hard or soft delete (chuck board?), what to do with
   GDPR, etc. (write it down and actually make it available to mods,
   maybe a hidden topic)/
   /- access for mods to logs so one can see what others did/

 * *Updated: mattock topics*
   /Managed to make tests run reliably now, the occassional failures
   seem resolved now./
   /Documentation
   
here:​https://github.com/mattock/openvpn/blob/dev_null/doc/dev-null-test-suite.rst
   
<https://github.com/mattock/openvpn/blob/dev_null/doc/dev-null-test-suite.rst>/
   /Will submit a patch soon./

As always you're welcome to join at #openvpn-meeting on Libera IRC network every Wednesday at 13: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