Sourceware Open Office Friday, June 13, 16:00 UTC

[Mark Wielaard]

Hi,

It was a busy open office, so a quick overview:

- During the meeting Frank and Karen finalized the procurement of the
  bigger server (3x memory [24x64GB], 10x storage [6x3.84TB], 2x cpu
  ish [2x28 cores] compared to the current servers). The new data
  center should also have a a faster/bigger network pipe. Thanks to
  the FUTO grant, individual Sourceware donations and Red Hat OSPO
  CommInfra & IT. It will be installed in the new RDU3 data center and
  joined by the two other servers from RDU2 in September. We like to
  have it setup and in production before the move of the other two
  servers so there is a minimum of downtime. Once it is installed and
  has a minimal setup we should probably have more frequent meetings
  so people can help with the planning of moving some services in
  their own isolated VMs. We did discuss various things that need
  to be untangled for that, but don't have a working plan yet.

- Various people reported issues with DNSSEC. This was caused by an
  old (sha1) algorithm which is deprecated. A new (sha256) algorithm
  was added and the old one should be deprecated. So once the old key
  gets out of the DNS caches things should work without
  warnings. Please let us know if you are still seeing issues.
  (This was the same issue that caused the email problems with
  forge.sourceware.org which was resolved by the new algo.)

- forge on the forge. There is now a forge project:
  https://forge.sourceware.org/forge
  So now people can fork and request merges on the forge.

- The forge now also uses Anubis. It is based on Claudio's work
  https://inbox.sourceware.org/a5931117-d633-4db7-8422-b56dcb1b48a9@arm.com
  But still doesn't use ansible (sorry).

- We want to rewire the mailman/public-inbox bridge.
  https://sourceware.org/bugzilla/show_bug.cgi?id=32977
  At least for the -announce and -patches lists that don't
  use From rewriting.

- We didn't get to secure development policy work because there was no
  project champion available. But if you want to follow the check list
  and document your project's verifiable cybersecurity policy:
  https://sourceware.org/cyber-security-faq.html#policy-checklist
  Please let us know. https://sourceware.org/mission.html#organization

Cheers,

Mark