From tbm at cyrius.com Sun Feb 10 12:05:15 2019 From: tbm at cyrius.com (Martin Michlmayr) Date: Sun, 10 Feb 2019 12:05:15 +0000 Subject: Task for someone with some time Message-ID: <20190210120515.ta5pqoffahvrkxe3@jirafa.cyrius.com> I have a task in case someone wants to help SPI. Go through all meeting minutes at http://spi-inc.org/meetings/minutes/ and look for resolutions that were voted on. Check if they are listed on our resolutions page at http://spi-inc.org/corporate/resolutions/ Create a list of missing resolutions. I'll start: * 2003-11-11.bmh.1 Passed in https://spi-inc.org/meetings/minutes/2003/2003-11-11/ * 2003-11-11.bmh.2 Passed in https://spi-inc.org/meetings/minutes/2003/2003-11-11/ -- Martin Michlmayr https://www.cyrius.com/ From tbm at cyrius.com Tue Feb 12 10:45:27 2019 From: tbm at cyrius.com (Martin Michlmayr) Date: Tue, 12 Feb 2019 11:45:27 +0100 Subject: Resolution 2018-07-11.mm.1: Arch Linux 32 as associated project In-Reply-To: <20190126173030.xxeo4f2nkxfuh3uj@jirafa.cyrius.com> References: <20190126173030.xxeo4f2nkxfuh3uj@jirafa.cyrius.com> Message-ID: <20190212104527.7qyilccuqzlbyzis@jirafa.cyrius.com> Dimitri John Ledkov pointed out during the SPI meeting yesterday that the resolution doesn't contain a clause saying what will happen if the project becomes defunct (something we add in new resolutons). I added clause 3. Erich, please check if this is okay. (If Arch Linux 32 becomes defunct and nobody replies to SPI, we'd probably transfer the remaining funds to the Arch Linux earmark.) New proposed resolution: WHEREAS 1. Arch Linux 32 is a substantial and significant Free Software project. 2. The Arch Linux 32 developers would like SPI's support and assistance, including taking donations. THE SPI BOARD RESOLVES THAT 1. Arch Linux 32 is formally invited to become an SPI Associated Project, according to the SPI Framework for Associated Projects, SPI Resolution 1998-11-16.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 the outgoing SPI liaison, or if the current SPI liaison is unavailable or refuses to appoint a successor, by a simple majority vote by the current master key holders of Arch Linux 32. 3. If the last known SPI liaison for Arch Linux 32 is missing in action, and no new SPI liaison is appointed for two consecutive years the associated project is deemed defunct. Defunct project's assets may be transferred to a nominated US 501(c)(3) charity or to the SPI general fund. 4. This invitation will lapse, if not accepted, 60 days after it is approved by the SPI Board. * Martin Michlmayr [2019-01-26 14:30]: > I'd like to propose this resolution for the February meeting. > I initially posted this to the list last year and some people asked > whether Arch Linux agrees and whether there's an agreement in place. > We have a light-weight trademark agreement from Arch Linux (Aaron) now, > so I think we're good to vote on this resolution. > > Resolution 2018-07-11.mm.1: Arch Linux 32 as associated project ... -- Martin Michlmayr https://www.cyrius.com/ From tbm at cyrius.com Thu Feb 14 15:35:40 2019 From: tbm at cyrius.com (Martin Michlmayr) Date: Thu, 14 Feb 2019 16:35:40 +0100 Subject: Resolution 2018-07-11.mm.1: Arch Linux 32 as associated project In-Reply-To: <46e48c23-002a-67a3-1b85-0ad378319859@eckner.net> References: <20190126173030.xxeo4f2nkxfuh3uj@jirafa.cyrius.com> <20190212104527.7qyilccuqzlbyzis@jirafa.cyrius.com> <46e48c23-002a-67a3-1b85-0ad378319859@eckner.net> Message-ID: <20190214153540.GC5023@jirafa.cyrius.com> * 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 ", preferably to the assets of > Arch Linux." (or something similar) to the end of the last sentence? I was considering that but in the end didn't do it because it's a standard sentence we use in all new project resolutions and I didn't want to modify it if there wasn't a strong reason. If you have strong feelings about it, I can add it. Otherwise let's hope a) the situation won't happen and b) if it does the board will do the right thing. -- Martin Michlmayr https://www.cyrius.com/ From tbm at cyrius.com Thu Feb 14 16:43:23 2019 From: tbm at cyrius.com (Martin Michlmayr) Date: Thu, 14 Feb 2019 17:43:23 +0100 Subject: Resolution 2018-07-11.mm.1: Arch Linux 32 as associated project In-Reply-To: <4ff95d09-194d-43a0-95d3-adb9083cab84@eckner.net> References: <20190126173030.xxeo4f2nkxfuh3uj@jirafa.cyrius.com> <20190212104527.7qyilccuqzlbyzis@jirafa.cyrius.com> <46e48c23-002a-67a3-1b85-0ad378319859@eckner.net> <20190214153540.GC5023@jirafa.cyrius.com> <4ff95d09-194d-43a0-95d3-adb9083cab84@eckner.net> Message-ID: <20190214164323.GG5023@jirafa.cyrius.com> * Erich Eckner [2019-02-14 17:32]: > Well, when it's default, then I have no objections. Well, it's a new clause. I just meant to say I copy & pasted. :) But it makes tracking easier if it's the same everywhere... Anyway, it's not clear to me what "nominated charity" means in the clause. Is that something the project nominates when they join (as you sort of did when you indicated a preference to give it to Arch) or something the board "nominates"? (but then "nominates" is a weird word). If it's something the project nominates, we need to implement a way to track it (i.e. write it down somewhere) so we'll remember in X years/decades (and how do we know the org originally nominated doesn't change over time...). I already sent an email to the board asking about this "nominated charity" question, but there's no need for this to be board-only and we can discuss here. (Adding xnox who I believe came up with the language or might remember who did.) -- Martin Michlmayr https://www.cyrius.com/ From arch at eckner.net Thu Feb 14 10:23:19 2019 From: arch at eckner.net (Erich Eckner) Date: Thu, 14 Feb 2019 11:23:19 +0100 Subject: Resolution 2018-07-11.mm.1: Arch Linux 32 as associated project In-Reply-To: <20190212104527.7qyilccuqzlbyzis@jirafa.cyrius.com> References: <20190126173030.xxeo4f2nkxfuh3uj@jirafa.cyrius.com> <20190212104527.7qyilccuqzlbyzis@jirafa.cyrius.com> Message-ID: <46e48c23-002a-67a3-1b85-0ad378319859@eckner.net> Yes, this is fine for me. However, maybe we can put your comment about Arch Linux into (3), too? Like adding ", preferably to the assets of Arch Linux." (or something similar) to the end of the last sentence? regards, Erich On 12.02.19 11:45, Martin Michlmayr wrote: > Dimitri John Ledkov pointed out during the SPI meeting yesterday that > the resolution doesn't contain a clause saying what will happen if the > project becomes defunct (something we add in new resolutons). > > I added clause 3. Erich, please check if this is okay. (If Arch > Linux 32 becomes defunct and nobody replies to SPI, we'd probably > transfer the remaining funds to the Arch Linux earmark.) > > New proposed resolution: > > WHEREAS > > 1. Arch Linux 32 is a substantial and significant Free Software project. > > 2. The Arch Linux 32 developers would like SPI's support and assistance, > including taking donations. > > THE SPI BOARD RESOLVES THAT > > 1. Arch Linux 32 is formally invited to become an SPI Associated > Project, according to the SPI Framework for Associated Projects, SPI > Resolution 1998-11-16.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 the > outgoing SPI liaison, or if the current SPI liaison is unavailable or > refuses to appoint a successor, by a simple majority vote by the current > master key holders of Arch Linux 32. > > 3. If the last known SPI liaison for Arch Linux 32 is missing in action, > and no new SPI liaison is appointed for two consecutive years the > associated project is deemed defunct. Defunct project's assets may be > transferred to a nominated US 501(c)(3) charity or to the SPI general > fund. > > 4. This invitation will lapse, if not accepted, 60 days after it is > approved by the SPI Board. -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: From arch at eckner.net Thu Feb 14 16:32:47 2019 From: arch at eckner.net (Erich Eckner) Date: Thu, 14 Feb 2019 17:32:47 +0100 Subject: Resolution 2018-07-11.mm.1: Arch Linux 32 as associated project In-Reply-To: <20190214153540.GC5023@jirafa.cyrius.com> References: <20190126173030.xxeo4f2nkxfuh3uj@jirafa.cyrius.com> <20190212104527.7qyilccuqzlbyzis@jirafa.cyrius.com> <46e48c23-002a-67a3-1b85-0ad378319859@eckner.net> <20190214153540.GC5023@jirafa.cyrius.com> Message-ID: <4ff95d09-194d-43a0-95d3-adb9083cab84@eckner.net> 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 ", preferably to the assets of >> Arch Linux." (or something similar) to the end of the last sentence? > > I was considering that but in the end didn't do it because it's a > standard sentence we use in all new project resolutions and I didn't > want to modify it if there wasn't a strong reason. > > If you have strong feelings about it, I can add it. Otherwise let's > hope a) the situation won't happen and b) if it does the board will do > the right thing. > -------------- next part -------------- A non-text attachment was scrubbed... Name: signature.asc Type: application/pgp-signature Size: 833 bytes Desc: OpenPGP digital signature URL: