From: | Theodore Ts'o <tytso(at)mit(dot)edu> |
---|---|
To: | MJ Ray <mjr(at)phonecoop(dot)coop> |
Cc: | spi-general(at)lists(dot)spi-inc(dot)org |
Subject: | Re: Draft resolution formalising Debian's Associated Project status |
Date: | 2007-03-08 12:28:21 |
Message-ID: | 20070308122821.GA20348@thunk.org |
Views: | Raw Message | Whole Thread | Download mbox |
Thread: | |
Lists: | spi-general |
On Thu, Mar 08, 2007 at 11:30:29AM +0000, MJ Ray wrote:
> Josh Berkus <josh(at)postgresql(dot)org> wrote:
> > I feel like I keep saying, "I want a simple API definition" and Ian & MJ keep
> > saying "read the whole codebase".
>
> I meant to say "summarise the API if you want, but acknowledge that
> the codebase decides the API" - IOW, project constitutions are
> authoritative and SPI doesn't seek to change them.
When you get a checking account for any non-profit organization, the
bank wants one or two people to be authorized signatories on the
account, and each year when there is an election the secretary or some
other officer sends a official letter to the bank (with a
countersignature from one of the people who are currently authorized
to sign on the account) saying who the new people with signature
authority should be.
This is a simple API, but it does not involve "rewriting the project
constitution". Claiming that the project constitution requires SPI or
a bank to be intimately involved with the project internal politics is
completely bogus and makes no sense.
- Ted
From | Date | Subject | |
---|---|---|---|
Next Message | Michael Schultheiss | 2007-03-08 16:09:09 | Re: Treasurer's report for Feburary |
Previous Message | MJ Ray | 2007-03-08 11:30:29 | Re: Draft resolution formalising Debian's Associated Project status |