Summary of the Gentoo council meeting 2024-06-09


Agenda [1]
==========

1. Roll call

2. Enable GitHub sponsorship using SPI Fiscal Host [2]

3. Arch status

4. Open bugs with council participation

5. Open floor


1. Roll call
============

Present: ajak, dilfridge, mattst88, mgorny, sam, soap, ulm


2. Enable Github sponsorship using SPI Fiscal Host [2]
======================================================

While there was no clear understanding how this would actually be implemented
within the Github framework, the general sentiment was that allowing sponsorship
via Github and SPI was a useful and unproblematic thing to do.

Motion:  Enable Github sponsorship using SPI Fiscal Host
Passed with 7 yes, unanimous


3. Arch status
==============

A discussion ensued, touching the topics of 
 * the value of stabilization on slow hardware, e.g., a slow-moving solid
   foundation that keeps builders functional
 * reducing stable set vs. removing some profiles vs. removing stable keywords
   entirely
 * the status of ia64 (close to death, guppy is down, kernel and glibc dropped
   the architecture)
 * the status of hppa (sad, issues with devbox, but there is interest)
 * what to do with the 32-bit sparc profiles (boot media should certainly
   be dropped, can run in chroot otherwise)
 * what to do with the 31-bit s390 (not x) profiles (dito)
 * ppc32 and x86 (~arch only? no changes for now?)
 * the general topic of mips (let's drop what is not needed)
 * the alignment transition of m68k
 * and the general topic of 64bit time_t on 32bit arches

The consensus was to start more discussion and revisit the topic at a future meeting.


4. Open bugs with council participation
=======================================

* bug 925014, "PR services lacking developer redundancy"

No news

* bug 801499, "Approach Nitrokey for Nitrokey 3 upgrade"

ulm, soap, and dilfridge received Nitrokeys 3 to test them out. The impression was
mixed, with a very flimsy design and the USB-C connector just padded out for 
the size of an USB-A connector. Other council members reported that their 
Nitrokey 2 died on them.

A discussion ensued whether Nitrokey should be preferred to, e.g., Yubikey
because of the social contract.

Motion: Approach Nitrokey for a renewal of keys for developers with Nitrokey 3
3 no, 3 abstain, 1 missing, motion not passed

Motion: Approach Yubikey and try to establish a similar deal
5 yes, 1 no, 1 abstain, motion carried


5. Open floor
=============

ulm expressed disappointment regarding the progress of the migration to SPI. 
This should be a priority item for the upcoming council.



[1] https://public-inbox.gentoo.org/gentoo-project/3812942.PYKUYFuaPT@pinacolada/T/#u
[2] https://marc.info/?l=gentoo-project&m=171676255409548&w=2