[gentoo-project] Council meeting 2024-07-21 - call for agenda items

[gentoo-project] Council meeting 2024-07-21 - call for agenda items

[Ulrich Mueller]

[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]

The first council meeting of this election term will be on
Sunday 2024-07-21 at 19:00 UTC in the #gentoo-council channel
on Libera Chat.

*** Note change of date, exceptionally _3rd_ Sunday of the month ***

Preliminary agenda:

1. Roll call
2. Constitute the new council
   - Decide on time of meetings. The previous council had its meetings
     on the 2nd Sunday of every month at 19:00 UTC
   - Vote for continuing last council's workflow considering sending
     a call for agenda items (two weeks in advance), sending the
     agenda (one week in advance) and have the meeting focussed, i.e.
     have major discussions on the gentoo-project mailing list prior
     to the meeting
   - Appoint chairmen for this term's meetings
3. Change GLEP 84 status to Final [1]
4. Foundation dissolution status update
5. Missing meeting logs and summaries
6. Open bugs with council involvement [2]
7. Open floor

The agenda is still open for additional items that the council should
discuss or vote on. For agenda items, please respond to this message
on the gentoo-project mailing list.

The final agenda for the meeting will be sent on Sunday 2024-07-14.

Ulrich

[1] https://bugs.gentoo.org/914982
[2] https://wiki.gentoo.org/wiki/Project:Council#Open_bugs_with_Council_participation

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]

Re: [gentoo-project] Council meeting 2024-07-21 - call for agenda items

[Arthur Zamarin]

[-- Attachment #1.1: Type: text/plain, Size: 2992 bytes --]

On 02/07/2024 22.30, Ulrich Mueller wrote:
> ...
> 
> The agenda is still open for additional items that the council should
> discuss or vote on. For agenda items, please respond to this message
> on the gentoo-project mailing list.

I want to pass the first plan from previous thread about the Various
Gentoo Arches statuses [1], mainly the changes which aren't
controversial. I have plan for next meetings, but the next steps warrant
more talks in ML.

I think those should be separate motions, but I leave this decision to
the chairman.

a. `alpha - make profile stable`

Thanks to matoro's work, alpha dep-tree is nearly done (the latest
breakage occurred since last check, so we can say we can get a stable
tree). He is responsive for issues and pings, so I believe we can trust
this arch.

I propose we pass make the alpha profile stable (I mean profile stable,
not arch stable). We will apply the motion the moment he finishes fixing
the tree (otherwise if we wait, we risk breaking it again without noticing).


b. `ia64 - deprecate arch`

We don't believe in the possibility of continuing supporting this arch
(drop from kernel & glibc, issues with devbox). I think the normal
deprecation period of 1 year is fine here.


c. `ppc64/32ul - shorten deprecation period`

By this "arch" I mean the 32-bit userland on 64 bit kernel. None need
it, mostly broken, and all hardware that might need it has better state
(normal 64 bit userland). Currently all profiles are 17.0 and
deprecated, but I want to ask we shorter the period, since removing it
helps a lot in cleanup of ppc64 profiles mess and future keyword split.
I think 2 month from motion pass should be good enough?


d. `sparc32 - deprecate profiles`

Various reasons stated in email thread [1], no opposition. I would like
to request shorter window from 1 year, to around 3 month? For an unused
profile, I don't think we need to wait the full time?


This means all the user facing profiles of:
```
default/linux/sparc
default/linux/sparc/17.0
default/linux/sparc/17.0/desktop
default/linux/sparc/17.0/developer
default/linux/sparc/17.0/systemd/merged-usr
default/linux/sparc/23.0
default/linux/sparc/23.0/desktop
default/linux/sparc/23.0/systemd
default/linux/sparc/23.0/split-usr
default/linux/sparc/23.0/split-usr/desktop
```

e. `s390 not s390x - deprecate profiles`

I mean here the s390 not s390x variant (confusing), which is the 31 bit
variant. Various reasons stated in email thread [1], no opposition.


This means all the user facing profiles of:
```
default/linux/s390/17.0
default/linux/s390/17.0/systemd/merged-usr
default/linux/s390/23.0
default/linux/s390/23.0/systemd
default/linux/s390/23.0/split-usr
```


[1]
https://public-inbox.gentoo.org/gentoo-dev/75654daa-c5fc-45c8-a104-fae43b9ca490@gentoo.org/T/

-- 
Arthur Zamarin
arthurzam@gentoo.org
Gentoo Linux developer (Council, Python, pkgcore stack, QA, Arch Teams)


[-- Attachment #2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 488 bytes --]

[gentoo-project] Council meeting 2024-07-21 - agenda

[Ulrich Mueller]

[-- Attachment #1: Type: text/plain, Size: 1151 bytes --]

The first council meeting of this election term will be on
Sunday 2024-07-21 at 19:00 UTC in the #gentoo-council channel
on Libera Chat.

*** Note change of date, exceptionally _3rd_ Sunday of the month ***

Agenda:

1. Roll call
2. Constitute the new council
   - Decide on time of meetings. The previous council had its meetings
     on the 2nd Sunday of every month at 19:00 UTC
   - Vote for continuing last council's workflow considering sending
     a call for agenda items (two weeks in advance), sending the
     agenda (one week in advance) and have the meeting focussed, i.e.
     have major discussions on the gentoo-project mailing list prior
     to the meeting
   - Appoint chairmen for this term's meetings
3. Change GLEP 84 status to Final [1]
4. Status of architectures [2]
5. Foundation dissolution status update
6. Missing meeting logs and summaries
7. Open bugs with council involvement [3]
8. Open floor

Ulrich

[1] https://bugs.gentoo.org/914982
[2] https://public-inbox.gentoo.org/gentoo-dev/bb74c3a3-06c9-4c76-b9ff-b5a111b33605@gentoo.org/
[3] https://wiki.gentoo.org/wiki/Project:Council#Open_bugs_with_Council_participation

[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 507 bytes --]