From: | Josh Berkus <josh(at)postgresql(dot)org> |
---|---|
To: | Jimmy Kaplowitz <jimmy(at)spi-inc(dot)org> |
Cc: | board(at)spi-inc(dot)org, spi-general(at)lists(dot)spi-inc(dot)org, secretary(at)spi-inc(dot)org |
Subject: | Re: Resolution 2009-03-16.jrk.1: OpenWRT as associated project |
Date: | 2009-03-16 23:51:17 |
Message-ID: | 49BEE5F5.4040806@postgresql.org |
Views: | Raw Message | Whole Thread | Download mbox |
Thread: | |
Lists: | spi-general |
Jimmy,
> Decisions are made according to their internal rules in the charter linked from
> the resolution preamble, and Andy or Gregers lets us know about them. They
> don't seem to be able to make independent decisions. However, I agree that
> their charter could use various clarifications and revisions. I've been meaning
> to suggest specific details to them, but none of the problems are serious
> enough to further delay approving them.
Well, for prior organizations we haven't allowed having more than one
liaison for *any* organization to avoid confusion. Why would OpenWRT be
different? One of the two needs to be the main liaison, and the other
an alternate.
For replacement of the liaisons, their procedure isn't any more muddy
than anyone else's. We can live with it.
> If we have doubts about what to do in a specific case, we can just delay any
> action while we investigate, just like we'd do if Debian's Secretary told us
> that a GR overruled a DPL decision but the DPL told us otherwise.
We don't want to repeat past mistakes with new affiliates.
--Josh
From | Date | Subject | |
---|---|---|---|
Next Message | Bdale Garbee | 2009-03-17 07:15:36 | Re: Resolution 2009-03-16.jrk.1: OpenWRT as associated project |
Previous Message | Jimmy Kaplowitz | 2009-03-16 23:32:07 | Re: Resolution 2009-03-16.jrk.1: OpenWRT as associated project |