Changes between Version 40 and Version 41 of HelsinkiHackathon2016
- Timestamp:
- 09/20/16 07:43:45 (8 years ago)
Legend:
- Unmodified
- Added
- Removed
- Modified
-
HelsinkiHackathon2016
v40 v41 69 69 70 70 == results == 71 * OpenVPN 3 released to !GitHub (https://github.com/OpenVPN/openvpn3) 71 72 * OpenVPN 3 73 * Released to !GitHub (https://github.com/OpenVPN/openvpn3) 74 * Contributor Agreement. Discussed a draft for a contributor agreement to the OpenVPN 3 code base. It is based on the [http://www.developercertificate.org/ DCO] which is used by the Linux kernel as well as several other projects, but it has an extension to allow OpenVPN Technologies to re-license contributions, but also includes a promise that OpenVPN Technologies, Inc will share any changes to said contributions. Dazo will reach out to some contacts with legal expertise so OpenVPN Technologies can get a proper legal review on this agreement. 75 * OpenVPN 3 walk through - James did a couple of sessions walking through parts of the OpenVPN 3 code base. 76 * OpenVPN 2.4 77 * A semi-automated Windows test script was created. This will give us more confidence in the Windows code before making the alpha1 release. 72 78 * Discussed adding server-side support to OpenVPN 3. Even though OpenVPN 3 codebase would be much easier to work with that OpenVPN 2's codebase, adding server support would be a significant effort. 73 79 * FIPS mode ... Steffan will look into this and further look at how we also can remove MD5 dependencies all together. Challenge is how to avoid breaking clients not supporting PRF processes not using MD5 74 * D-Bus ... cron2: "Resistance is futile". This adds interesting possibilities and it makes sense for OpenVPN 3 code base. However, there are concerns about the complexity of adding it to the current OpenVPN 2 code base. There are also some concerns that this will primarily be used on Linux only, as many *BSD installs do not install D-Bus packages.75 * Contributor Agreement. Discussed a draft for a contributor agreement to the OpenVPN 3 code base. It is based on the [http://www.developercertificate.org/ DCO] which is used by the Linux kernel as well as several other projects, but it has an extension to allow OpenVPN Technologies to re-license contributions, but also includes a promise that OpenVPN Technologies, Inc will share any changes to said contributions. Dazo will reach out to some contacts with legal expertise so OpenVPN Technologies can get a proper legal review on this agreement.76 * OpenVPN 3 walk through - James did a couple of sessions walking through parts of the OpenVPN 3 code base.77 80 * Many Trac tickets were resolved or closed 78 81 * Buildbot setup was improved significantly, with the addition of a MacOS X buildslave and general fixes and cleanups. That said, many buildslaves require exceptions in various parts, so further refactoring and cleanup might be in order. 79 * Next year hackathon's location was discussed. One option would be [https://en.wikipedia.org/wiki/Karlsruhe Karlruhe] in Germany, as Sophos has an office there and Heiko works there. Another option would be to meet in the United States; cost-vise areas near the major airports with direct flights from Europe (Chicago or New York) would be best. 80 82 * D-Bus integration in OpenVPN 2.x and 3.x 83 * cron2: "Resistance is futile". 84 * This adds interesting possibilities and it makes sense for OpenVPN 3 code base. However, there are concerns about the complexity of adding it to the current OpenVPN 2 code base. There are also some concerns that this will primarily be used on Linux only, as many *BSD installs do not install D-Bus packages. 85 * Next year hackathon's 86 * We discussed the location. One option would be [https://en.wikipedia.org/wiki/Karlsruhe Karlruhe] in Germany, as Sophos has an office there and Heiko works there. Another option would be to meet in the United States; cost-vise areas near the major airports with direct flights from Europe (Chicago or New York) would be best.
