[arch-dev-public] RFC: Adoption of a distribution-wide Code of Conduct

2021-09-15 Thread David Runge via arch-dev-public
A new RFC (request for comment) has been opened here:

https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/6

Please visit the above link for discussion.

Summary:
The adoption of a distribution-wide Code of Conduct (CoC) helps to
describe the social contract by which communication takes place on the
various communication channels offered by Arch Linux.
This document describes the current CoC, its purpose and location and
how to interact with it.

Best,
David


signature.asc
Description: PGP signature


Re: [arch-dev-public] Formal Objection to Adopting the Code of Conduct

2021-09-15 Thread Levente Polyak via arch-dev-public

On 9/5/21 04:38, Allan McRae via arch-dev-public wrote:

Either the CoC was already a formal document and changes were made by a
small number of staff with limited oversight from the governing body -
in this case we need to revert to the last formal version and all
changes need formally agreed on.  Or it was not an official document and
we need to discuss formally adopting it.

So I see this issue can be addressed by the current governing body (the
Developers, preferably with input from all staff) in at least two ways:

1) There is a discussion and agreement around the formal adoption of the
CoC.

or

2) There is an agreement that the CoC was already official, AND a
discussion and agreement around the changes that were made since import
into the service agreement repo.

Effectively these are the same discussion.



I think at this point it isn't really leading anywhere to try to argue 
who is exactly right about the status quo. What does matter more is how 
we want to proceed to get the changes official -- this is where i agree 
that it kind of is the very same discussion/procedure this should go 
through to either get the changes or the overall thing in place.


Using a clear procedure for the current and future changes does not only 
make sense because this is a distro wide formal document, but also as 
this is implicitly part of the service agreement and changes will hence 
need to be propagated to all users actively.


We've talked about this in a small working group for a while and came to 
two action points partially related but independent from each other:



1) Use the RFC process to adapt the CoC document in its current form:

https://gitlab.archlinux.org/archlinux/rfcs/-/merge_requests/6

This RFC formalizes the current CoC changes as well as defines how to 
proceed with changes in terms of transparency (visibility across the 
staff) as well as implications for the terms of service.



2) Adaption of the Arch Mediation Program

This program has been discussed for a while now. The time has come to 
take it forward and propose a concrete RFC that can be reviewed and 
adapted including a procedure to nominate and vote on mediators.


This is related to the CoC, but can live independently. In case former 
got adapted, this would lead to a small change in the CoC escalation 
paragraphs including the mediators as an official layer.




Thanks for bringing up this discussion and making those changes rock solid.

cheers,
Levente


OpenPGP_signature
Description: OpenPGP digital signature


Re: [arch-dev-public] Go 1.17 released - to rebuild or not to rebuild

2021-09-15 Thread Levente Polyak via arch-dev-public

On 8/22/21 12:03, Jelle van der Waa via arch-dev-public wrote:

On 17/08/2021 20:36, Morten Linderud via arch-dev-public wrote:

Yo,

I packaged up the new Go release yesterday and moved it over to stable 
earlier

today.

Usually new Go minor releases frequently include new compiler 
improvements and
some assorted runtime changes. Previous releases I have done complete 
rebuilds
of Go packages in our repositories but the reception for these 
rebuilds have

been a bit mixed.

People do not really see the need to rebuild $goWorld when packages a 
compiled
and nothing inherently breaks unless there is a rebuild. We don't do 
this for
GCC, Rust and so on. However I do think it's nice to group up these 
ecosystem
changes in one swoop as it spares me from having to repeat myself for 
the next

few months as people occasionally update their Go packages.

But on the other hand I'm not super eager to be alone rebuilding all 
of this

either. So what are peoples thoughts on the subject?


I'm in favor of rebuilding, just ask foutrelis to spin up his rebuilder 
and it should be done in no time :)


Greetings,

Jelle van der Waa




As far as i see this has not yet happened but people were for it and 
nobody objected -- can we make it happen?


cheers,
Levente


OpenPGP_signature
Description: OpenPGP digital signature