Re: Resolution Arch Linux 32 as associated project

From: Ian Jackson <ijackson(at)chiark(dot)greenend(dot)org(dot)uk>
To: Martin Michlmayr <tbm(at)cyrius(dot)com>
Cc: Erich Eckner <arch(at)eckner(dot)net>, spi-general(at)lists(dot)spi-inc(dot)org, aaron(at)archlinux(dot)org
Subject: Re: Resolution Arch Linux 32 as associated project
Date: 2019-02-19 11:34:05
Views: Raw Message | Whole Thread | Download mbox
Lists: spi-general

Martin Michlmayr writes ("Re: Resolution Arch Linux 32 as associated project"):
> 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).

You indeed point out a deficiency in the standard wording.

Also, I would like to say that the purpose of standard wordings is not
to be immutable. It is fine to change them if we understand the
reasons why the standard wording is the way it is. In this case, we
don't want to nail things down which may turn out to be unworkable in
the distant and unknowable future.

How about the following alternative standard wording:

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.

The SPI Board will try to identify a similar successor project; SPI
will transfer the assets to the successor's US charity, or hold them
in trust for the successor. Failing that the assets will become
part of the SPI general fund.

Significant differences:

- Say that the successor:
- is up to the Board
- should be `similar'

- `Will' rather than `may', since I don't think really we expect the
board to leave assets attached to a defunct earmark.

- SPI general fund more clearly the last resort.

Technical differences:

- Wording reorganised.

- Mention the possibility that the assets would end up with SPI
but with the successor's earmark.

- Remove unclear `nominated'.

> 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...).


> (Adding xnox who I believe came up with the language or might
> remember who did.)

I think it's after my time. It's possible that the intent was to
allow the defunct project to nominate its successor but there are
obvious practical problems with that...


Ian Jackson <ijackson(at)chiark(dot)greenend(dot)org(dot)uk> These opinions are my own.

If I emailed you from an address or, that is
a private address which bypasses my fierce spamfilter.


Browse spi-general by date

  From Date Subject
Next Message Martin Michlmayr 2019-02-19 17:52:19 Resolution Removal of Torch as an associated project
Previous Message Martin Michlmayr 2019-02-14 16:43:23 Re: Resolution Arch Linux 32 as associated project