Resolution 2019-05-02.jrk.2: Arch Linux 32 as associated project

I'd like to propose this resolution for the May 13 meeting.

We were most recently discussing this on spi-general from January
through March, but a resolution with the revised wording didn't get
prepared in time to vote on this before now. Hopefully we can get Arch
Linux 32 approved this month.

Thanks to Martin Michlmayr for his previous work on this resolution
during his time on the board, and to Ian Jackson for his wording
improvements.

Resolution 2019-05-02.jrk.2: Arch Linux 32 as associated project

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.

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 or 501(c)(3) charities which can accept
the project's assets and use them for a similar purpose, and transfer
the assets to the identified destination or destinations as feasible.
Assets for which no such transfer can be arranged within a reasonable
time will become part of the SPI general fund.

4. This invitation will lapse, if not accepted, 60 days after it is
approved by the SPI Board.

- Jimmy Kaplowitz
jimmy(at)spi-inc(dot)org

On 2 May 2019, at 10:58 pm, Jimmy Kaplowitz <jimmy(at)spi-inc(dot)org> wrote:
>
> I'd like to propose this resolution for the May 13 meeting.
>
> We were most recently discussing this on spi-general from January
> through March, but a resolution with the revised wording didn't get
> prepared in time to vote on this before now. Hopefully we can get Arch
> Linux 32 approved this month.
>
> Thanks to Martin Michlmayr for his previous work on this resolution
> during his time on the board, and to Ian Jackson for his wording
> improvements.
>
> Resolution 2019-05-02.jrk.2: Arch Linux 32 as associated project

Added to the agenda but unfortunately after I sent out the initial notice.

Tim.

Hi Tim,

On Sat, May 04, 2019 at 07:52:10PM +1000, Tim Potter wrote:
> On 2 May 2019, at 10:58 pm, Jimmy Kaplowitz <jimmy(at)spi-inc(dot)org> wrote:
> >
> > I'd like to propose this resolution for the May 13 meeting.
> >
> > We were most recently discussing this on spi-general from January
> > through March, but a resolution with the revised wording didn't get
> > prepared in time to vote on this before now. Hopefully we can get Arch
> > Linux 32 approved this month.
> >
> > Thanks to Martin Michlmayr for his previous work on this resolution
> > during his time on the board, and to Ian Jackson for his wording
> > improvements.
> >
> > Resolution 2019-05-02.jrk.2: Arch Linux 32 as associated project
>
> Added to the agenda but unfortunately after I sent out the initial notice.

Thanks for adding this and the other agenda items submitted so far. The
Arch Linux 32 agenda item has formatting glitches but that should be a
straightforward enough Markdown fix.

- Jimmy Kaplowitz
jimmy(at)spi-inc(dot)org