Lists: | spi-general |
---|
From: | Bdale Garbee <bdale(at)gag(dot)com> |
---|---|
To: | secretary(at)spi-inc(dot)org |
Cc: | spi-private(at)lists(dot)spi-inc(dot)org, spi-general(at)lists(dot)spi-inc(dot)org |
Subject: | SPI resolution 2016.05.01.bg.1: ArduPilot as associated project |
Date: | 2016-05-05 22:30:12 |
Message-ID: | 87d1p0t9xn.fsf@rover.gag.com |
Views: | Raw Message | Whole Thread | Download mbox |
Lists: | spi-general |
Please add this resolution to our May agenda.
ArduPilot is a well-known project delivering a suite of autopilot
software for autonomous planes, copters, and rovers. The primary web
site is at ardupilot.org.
ArduPilot participates as a member project of the Linux Foundation
Dronecode community, which has web content at dronecode.org.
Bdale
SPI resolution 2016.05.01.bg.1
WHEREAS
1. ArduPilot is a substantial and significant Free Software project.
2. The ArduPilot developers would like SPI's support and assistance,
including taking donations.
THE SPI BOARD RESOLVES THAT
3. ArduPilot 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 http://www.spi-inc.org/corporate/resolutions/2004/2004-08-10.iwj.1/
4. Andrew Tridgell is recognised by SPI as the authoritative decision
maker and SPI liaison for ArduPilot. Successors will be appointed by a
vote on the ArduPilot development team mailing list
ardupilot-dev-team(at)googlegroups(dot)com(dot) Communication by SPI to the
ArduPilot dev team leads (including the liason) can be made by email to
ardupilot(dot)devel(at)gmail(dot)com(dot)
5. This invitation will lapse, if not accepted, 60 days after it is
approved by the SPI Board.
From: | Martin Zobel-Helas <zobel(at)spi-inc(dot)org> |
---|---|
To: | Bdale Garbee <bdale(at)gag(dot)com> |
Cc: | spi-private(at)lists(dot)spi-inc(dot)org, spi-general(at)lists(dot)spi-inc(dot)org, secretary(at)spi-inc(dot)org |
Subject: | Re: SPI resolution 2016.05.01.bg.1: ArduPilot as associated project |
Date: | 2016-05-10 21:24:38 |
Message-ID: | 20160510212438.GG22062@ftbfs.de |
Views: | Raw Message | Whole Thread | Download mbox |
Lists: | spi-general |
Hi,
On Thu May 05, 2016 at 16:30:12 -0600, Bdale Garbee wrote:
> Please add this resolution to our May agenda.
>
> ArduPilot is a well-known project delivering a suite of autopilot
> software for autonomous planes, copters, and rovers. The primary web
> site is at ardupilot.org.
>
> ArduPilot participates as a member project of the Linux Foundation
> Dronecode community, which has web content at dronecode.org.
>
> Bdale
>
>
> SPI resolution 2016.05.01.bg.1
>
> WHEREAS
>
> 1. ArduPilot is a substantial and significant Free Software project.
>
> 2. The ArduPilot developers would like SPI's support and assistance,
> including taking donations.
>
> THE SPI BOARD RESOLVES THAT
>
> 3. ArduPilot 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 http://www.spi-inc.org/corporate/resolutions/2004/2004-08-10.iwj.1/
>
> 4. Andrew Tridgell is recognised by SPI as the authoritative decision
> maker and SPI liaison for ArduPilot. Successors will be appointed by a
> vote on the ArduPilot development team mailing list
> ardupilot-dev-team(at)googlegroups(dot)com(dot) Communication by SPI to the
> ArduPilot dev team leads (including the liason) can be made by email to
> ardupilot(dot)devel(at)gmail(dot)com(dot)
>
> 5. This invitation will lapse, if not accepted, 60 days after it is
> approved by the SPI Board.
I would like to see something like the following added to the resolution:
6. In the event that the ArduPilot dissolves without defining what
SPI shall do with the managed assets or the ArduPilot becomes
provable uncontactable for SPI, the board reserves the right to assign
those assets to it's general fund.
That maybe needs a bit of rewording as i am not a native english
speaker, but i hope everyone gets what i mean here.
For those who are wondering, why i want this added: During our face2face
meeting earlier this year we were advised by SFLC to add a paragraph
like this to every future resolution. Otherwise if a project goes MIA or
even dissolves without giving us any notice, we cannot take their money
or other assets and use them for something else.
Martin
--
Martin Zobel-Helas <zobel(at)spi-inc(dot)org>
Software in the Public Interest, Inc. | Member of the Board of Directors
GPG Fingerprint: 6B18 5642 8E41 EC89 3D5D BDBB 53B1 AC6D B11B 627B
From: | Peter Cock <p(dot)j(dot)a(dot)cock(at)googlemail(dot)com> |
---|---|
To: | Martin Zobel-Helas <zobel(at)spi-inc(dot)org> |
Cc: | spi-general(at)lists(dot)spi-inc(dot)org, secretary(at)spi-inc(dot)org, spi-private(at)lists(dot)spi-inc(dot)org |
Subject: | Re: SPI resolution 2016.05.01.bg.1: ArduPilot as associated project |
Date: | 2016-05-10 21:38:43 |
Message-ID: | CAKVJ-_5pBODz1WyhmjuAOOZtOB3V9tkYZ2JmBGhK2ASRwfkeHg@mail.gmail.com |
Views: | Raw Message | Whole Thread | Download mbox |
Lists: | spi-general |
That sounds like a sensible idea in principle for all future projects.
In addition to having a lawyer review the final wording, I would
suggest there be some minimum time period as well before
the SPI can move earmarked funds under this clause (e.g. six
months or a year)?
Peter
(Open Bioinformatics Foundation secretary)
On Tue, May 10, 2016 at 10:24 PM, Martin Zobel-Helas <zobel(at)spi-inc(dot)org> wrote:
> Hi,
>
> ...
>
> I would like to see something like the following added to the resolution:
>
> 6. In the event that the ArduPilot dissolves without defining what
> SPI shall do with the managed assets or the ArduPilot becomes
> provable uncontactable for SPI, the board reserves the right to assign
> those assets to it's general fund.
>
> That maybe needs a bit of rewording as i am not a native english
> speaker, but i hope everyone gets what i mean here.
>
> For those who are wondering, why i want this added: During our face2face
> meeting earlier this year we were advised by SFLC to add a paragraph
> like this to every future resolution. Otherwise if a project goes MIA or
> even dissolves without giving us any notice, we cannot take their money
> or other assets and use them for something else.
>
> Martin
From: | "Joshua D(dot) Drake" <jd(at)commandprompt(dot)com> |
---|---|
To: | Peter Cock <p(dot)j(dot)a(dot)cock(at)googlemail(dot)com>, Martin Zobel-Helas <zobel(at)spi-inc(dot)org> |
Cc: | spi-private(at)lists(dot)spi-inc(dot)org, spi-general(at)lists(dot)spi-inc(dot)org, secretary(at)spi-inc(dot)org |
Subject: | Re: SPI resolution 2016.05.01.bg.1: ArduPilot as associated project |
Date: | 2016-05-10 21:41:34 |
Message-ID: | 5732558E.8080308@commandprompt.com |
Views: | Raw Message | Whole Thread | Download mbox |
Lists: | spi-general |
On 05/10/2016 02:38 PM, Peter Cock wrote:
> That sounds like a sensible idea in principle for all future projects.
>
> In addition to having a lawyer review the final wording, I would
> suggest there be some minimum time period as well before
> the SPI can move earmarked funds under this clause (e.g. six
> months or a year)?
Agreed but I also think we need to forgo this option on the pending
resolutions and get a global resolution written for all past and future
projects.
JD
--
Command Prompt, Inc. http://the.postgres.company/
+1-503-667-4564
PostgreSQL Centered full stack support, consulting and development.
Everyone appreciates your honesty, until you are honest with them.