| 1 |
Am Freitag, 8. Juni 2018, 19:44:00 CEST schrieb Andreas K. Huettel: |
| 2 |
> Dear all, |
| 3 |
> |
| 4 |
> the Gentoo Council will meet again this sunday, 10 June 2018, 18:00 UTC on |
| 5 |
> the #gentoo-council IRC channel. |
| 6 |
> |
| 7 |
> Please reply to this e-mail with agenda item proposals. |
| 8 |
> |
| 9 |
|
| 10 |
I would like to put the following proposal on the agenda once more (clarified |
| 11 |
and expanded): |
| 12 |
|
| 13 |
The Gentoo council shall directly contact "Software in the Public Interest |
| 14 |
Inc." (SPI), with the intention of Gentoo becoming a SPI Associated Project. |
| 15 |
The intention is for SPI to become an *additional* service provider of the |
| 16 |
Gentoo developer community for Accepting Donations, Holding Funds, and Holding |
| 17 |
Assets. The SPI project liaison shall be appointed by the Gentoo council. |
| 18 |
|
| 19 |
No transfer of funds or assets of any kind between SPI and the Gentoo |
| 20 |
Foundation is stipulated (it would be the trustees' responsibility anyway), so |
| 21 |
any (dys)function of the Gentoo Foundation has no impact on this new business |
| 22 |
relationship. Equally, the business relationship with SPI shall have no impact |
| 23 |
on the current function of the Gentoo Foundation. Essentially, the proposal is |
| 24 |
that we start with an empty account at SPI. (I'll be happy to make the first |
| 25 |
donation.) |
| 26 |
|
| 27 |
|
| 28 |
SPI does not require exclusivity; the company explicitly allows that a project |
| 29 |
is also sponsored by further parties. As long as SPI does not publicly |
| 30 |
represent Gentoo, there is no conflict regarding trademarks. Most SPI |
| 31 |
associated projects are unincorporated associations of individuals, as is the |
| 32 |
Gentoo developer community electing the Gentoo Council. |
| 33 |
|
| 34 |
As additional bonus, we will be gaining that donations to SPI are tax- |
| 35 |
deductible both in the US and in the EU. |
| 36 |
|
| 37 |
The precise procedure for appointing the project liaison is up to debate; a |
| 38 |
draft proposal can be found below. |
| 39 |
== |
| 40 |
a) The project liaison is a Gentoo developer appointed by the Gentoo council, |
| 41 |
and bound to follow its instructions. |
| 42 |
b) Appointment of the project liaison is by vote of the majority of council |
| 43 |
members (i.e. >=4 votes). The only way to unseat the project liaison is to |
| 44 |
appoint a different project liaison by vote. |
| 45 |
c) Officers and trustees of the Gentoo Foundation are not eligible for |
| 46 |
project liaison. |
| 47 |
d) The restriction of c) can be lifted permanently by Gentoo council majority |
| 48 |
decision only after the council, the Gentoo Foundation trustees, and the board |
| 49 |
of the financial sponsor organization have come into agreement that |
| 50 |
* the financial situation of the Gentoo Foundation has been sufficiently |
| 51 |
clarified, |
| 52 |
* any outstanding taxes have been determined and paid, and |
| 53 |
* any further outstanding relevant business of the Gentoo Foundation, i.e., |
| 54 |
with the IRS, has been concluded. |
| 55 |
== |
| 56 |
|
| 57 |
-- |
| 58 |
Andreas K. Hüttel |
| 59 |
dilfridge@g.o |
| 60 |
Gentoo Linux developer |
| 61 |
(council, toolchain, perl, libreoffice, comrel) |
Archives