Re: Resolution 2018-07-11.mm.1: Arch Linux 32 as associated project

2018-07-17 Thread Erich Eckner
Hi Martin, your list looks good, but I'd like to include the following items: 1st: Configurational changes we deem necessary to make Arch Linux 32 running and maintainable (e.g. we obviously have a separate mirror list and an extra keyring). - Or did you mean to cover this in your 2nd point? 2nd

Re: Resolution 2018-07-11.mm.1: Arch Linux 32 as associated project

2019-02-14 Thread Erich Eckner
Well, when it's default, then I have no objections. regards, Erich On 14.02.19 16:35, Martin Michlmayr wrote: > * Erich Eckner [2019-02-14 11:23]: >> Yes, this is fine for me. However, maybe we can put your comment about >> Arch Linux into (3), too? Like adding ", pr

Re: Resolution 2018-07-11.mm.1: Arch Linux 32 as associated project

2019-02-14 Thread Erich Eckner
iwj.1-amended-2004-08-10.iwj.1, a copy of which > can be found at > https://www.spi-inc.org/corporate/resolutions/2004/2004-08-10.iwj.1/ > > 2. Erich Eckner is recognized by SPI as the authoritative decision maker > and SPI liaison for Arch Linux 32. Successors will be appointed by th

Re: Resolution 2018-07-11.mm.1: Arch Linux 32 as associated project

2019-03-26 Thread Erich Eckner
On Tue, 5 Mar 2019, Ian Jackson wrote: Jimmy Kaplowitz writes ("Re: Resolution 2018-07-11.mm.1: Arch Linux 32 as associated project"): In such a circumstance, the SPI Board will, in its good-faith discretion, proceed as follows: the Board will identify one or more other SPI associated projects