Proposed resolution: Clarify SPI 5% administrative fee for conference sponsorships

[Michael Schultheiss]

Luca Filipozzi wrote:
> @all: Having slept on things, I'm changing my position from (2a) to (2c)
> since it is more appropriate to correct the lack of charging Debian 5%
> on sponsorships than it is to correct the actual/perceived
> miscommunication between Debian and SPI.
> 
> So, for clarity:
> - do not refund Debian for 2016-2019; do not charge fees on Debian
>   sponsorships prior to 2016; do not refund other projects (2c)
> - charge all projects' donations and sponsorships the same 5% fee, which
>   is the current practice (3b)
> 
> @president: kindly consider revising the draft resolution per above
> since there are now several of us in holding this view.

The latest draft of the resolution for tomorrow's meeting is attached.

-- 
----------------------------
Michael Schultheiss
E-mail: schultmc at spi-inc.org
-------------- next part --------------
Resolution 2020-06-22.mcs.1: 
Conferences and SPI 5% fee

WHEREAS

1. Software in the Public Interest, Inc. (SPI) is a Debian Trusted
   Organization.

2. The annual Debian Conference (Debian) utilizes SPI to collect
   some of the conference sponsorship funds.

3. SPI has inconsistently charged its 5% administrative fee for
   conference sponsorships.

4. SPI has not yet determined the effect of waiving the 5%
   administrative fee for conference sponsorships in perpetuity.

THE SPI BOARD RESOLVES THAT

1. Going forward, SPI will consistently charge all projects donations
   and conference sponsorships a 5% administrative fee, as is SPI's
   current practice.

2. SPI will not retroactively charge Debian its 5% adminsitrative fee for
   Debian conferences held prior to 2016.

3. SPI will not refund associated projects the 5% adminsitrative fee for
   conferences held 2016-2019.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 833 bytes
Desc: not available
URL: <http://lists.spi-inc.org/pipermail/spi-general/attachments/20200621/b04f9c2f/attachment.pgp>