- **Time**: Wed June 22nd 2022 10:30 CEST (8:30 UTC)

- **Place**: #openvpn-meeting channel on LiberaChat IRC network

- 2.5

- 2.6

- New Patchwork is ready to be used; it has already collected the most recent patches.

- Ordex is able to resend relevant patches so the new Patchwork gets them.

- Our mailing list archive contains the discussion history for patches that have been merged/are not relevant anymore -> no real need to have those in new Patchwork.

- DNS can be switched at any time.

- Users need to be added for those who need Patchwork, but doing this will be easier once patches are in.

- In Patchwork, Git authors and users are kind of the same thing afaik, so this is mostly about permissions.

- When to do this?

- Trac project has struggled quite a bit to get Python 3 support in ([see Trac ticket #12130](https://trac.edgewall.org/ticket/12130)).

- This was somewhat expected, given that a large number of its dependencies needed to become Python 3 compatible first.

- There are no stable Trac releases with Python 3 support.

- The only Trac version that supports Python 3 is the development release (1.5).

- While Trac is still being developed, it is not moving forward very fast.

- e.g., Python 3 support was supposed to land in Trac 1.3.

- Our Trac setup is fairly complex (LDAP auth, lots of plugins, spam filtering, etc.).

- When Trac was set up originally it was deemed important by OpenVPN Inc. management to self-host everything: this may have changed since then.

- Update to Trac 1.5

- Can be done, but users may experience issues.

- Some of the Trac plugins may no longer work (warrants research).

- Migrate to Github

- We are using Github for most of our development already (excluding a subset of OpenVPN 2.x development).

- Benefit: contents of "community.openvpn.net" would be reachable via IPv6 - assuming Github supports IPv6 :)

- Wiki import seems possible and can even be done manually (we don't have hundreds or thousands of pages).

- Issue import (without comments) can apparently be done from CSV with [github-csv-tools](https://github.com/gavinr/github-csv-tools).

- Issue comments can be imported with a custom script that drives the [GitHub issues API](https://docs.github.com/en/rest/issues/comments).

- We'd want HTTP redirects for the most important pages at least.

- A simple nginx/apache server doing these redirects would be sufficient.

- Overall: it will be a hassle, but can be done.

- Use separate software for Wiki and Bug tracking

- Wikis

- [Self-hosted wiki software](https://geekflare.com/self-hosted-wiki-software/)

- [Best self-hosted wiki software](https://rooferne.mooo.com/best-self-hosted-wiki-software/)

- Bug tracking

- [OS bug and issues tracking and management solutions](https://medevel.com/19-os-bug-and-issues-tracking-and-management-solutions/)

- Other options?

- Self-hosted gitlab or gitlab.com

- Mattock is not very keen on doing this even though he does have a self-hosted Gitlab instance and uses gitlab.com to an extent: Gitlab has turned into a pig/beast with a gazillion of features most of which we would not even use. If we wanted to use Gitlab then we should probably go all the way in or not at all.