From mboxrd@z Thu Jan 1 00:00:00 1970 From: ludo@gnu.org (Ludovic =?utf-8?Q?Court=C3=A8s?=) Subject: Buck collection Date: Wed, 30 Sep 2015 11:55:19 +0200 Message-ID: <87d1x0tens.fsf@gnu.org> Mime-Version: 1.0 Content-Type: multipart/signed; boundary="=-=-="; micalg=pgp-sha256; protocol="application/pgp-signature" Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:56192) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZhE6j-0002B5-Ts for guix-devel@gnu.org; Wed, 30 Sep 2015 05:55:31 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1ZhE6i-00062K-CQ for guix-devel@gnu.org; Wed, 30 Sep 2015 05:55:29 -0400 Received: from fencepost.gnu.org ([208.118.235.10]:49396) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1ZhE6i-000623-8a for guix-devel@gnu.org; Wed, 30 Sep 2015 05:55:28 -0400 Received: from reverse-83.fdn.fr ([80.67.176.83]:52494 helo=pluto) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_128_CBC_SHA1:128) (Exim 4.82) (envelope-from ) id 1ZhE6h-0003Q3-Fg for guix-devel@gnu.org; Wed, 30 Sep 2015 05:55:28 -0400 List-Id: "Development of GNU Guix and the GNU System distribution." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org Sender: guix-devel-bounces+gcggd-guix-devel=m.gmane.org@gnu.org To: guix-devel --=-=-= Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hello! substitute: while fetching http://hydra.gnu.org/nix-cache-info: server is= somewhat slow substitute: try `--no-substitutes' if the problem persists You=E2=80=99ve already seen that one, haven=E2=80=99t you? :-) Hardware donations have worked fine and have allowed us to get powerful build machines=C2=B9. To the point the hydra.gnu.org front-end has become the real bottleneck. To remedy this, we=E2=80=99ll start a Buck Collection Program=E2=84=A2. Na= mely, we=E2=80=99ll add Guix to the FSF=E2=80=99s Free Software Fund=C2=B2, which will allow th= e FSF to collect financial donations on behalf of the Guix project. The main goal once this is set up will be to get money for hardware and possibly hosting of hydra.gnu.org. The reason is that we cannot really rely on hardware donations from third parties for the front-end because we need to make sure it=E2=80=99s perennial and under tight control by the = Guix folks. Also, as the project grows, I think it=E2=80=99s good a way to impr= ove our infrastructure and make it hopefully more future-proof. Below is a summary of how the Free Software Fund works in practice. There=E2=80=99ll be a =E2=80=9Ccommittee=E2=80=9D to decide when and how to= spend money. I=E2=80=99m thinking of having 3 people to fill that role initially: Mark H Weaver, Ricardo Wurmus, and myself, which makes for a good geographical distribution; new members can be designated based on a consensus among current members. Comments welcome! Ludo=E2=80=99. =C2=B9 http://www.gnu.org/software/guix/donate/ =C2=B2 http://www.fsf.org/working-together/fund Overview of how the Free Software Fund program works: 0. Funds will be held by the FSF. They will be disbursed to their designated projects either as reimbursements for specific expenses incurred by contributors (following usual best practices like providing receipts), or as outright individual contractor payments for development (following usual best practices such as asking for a description of what development was achieved as a result of the funds, or if funding precedes the development, having a contract in place specifying commitments). Expense reimbursement will be available for travel, meaning that funds can be used to help get you and your contributors to conferences to promote the project, organize hack sessions, etc. Another example of expenses that could be reimbursed would be hosting, or equipment for development. 1. The project will designate who is authorized to receive such funds, and will take responsibility for letting us know about changes to that. One person or legal entity will be designated as the ultimate authority for this (likely the same person as the primary maintainer). The project will ideally have a simple governance system for deciding this -- we suggest a committee of three or more people and a basic process for adding and removing people on the committee (such as either consensus or majority vote). 2. Donations will be made to the project via a specific form on the FSF web site, which can be linked to from wherever. We will also be developing a widget for convenient use on project web sites. Donations can be received natively in Euro via wire transfer, in Bitcoin, Litecoin, and in USD via PayPal, credit cards, wire transfers, checks, employer matching, etc -- all the same mechanisms that the FSF uses to receive donations. 3. In the event the project dissolves or leaves the program, we will do our best to channel remaining donations to another project in the same general topic area. Failing that, they will revert to the FSF general fund (this will all be made clear in our public description of the program so that donors understand). Should a project decide to stop working with the FSF, the donations have to remain with the FSF, unless the project associates with a different 501(c)(3) -- or starts its own. In that case, the balance of donations can be transferred from the FSF to the other organization. 4. 10% of each donation will go to the FSF to support operation of the program and shared GNU infrastructure. This includes covering transaction costs charged by our payment providers (currently TrustCommerce, for handling all credit cards, and PayPal). So 90% of the donation will be available for the project's use. We will also include your donors in our usual donor acknowledgment process, which means you don't have to worry about things like thank-you letters or annual tax receipts. --=-=-= Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJWC7GLAAoJEAkLEZk9muu1NfgP/iOiiGBX0DkhARCqKuGvE9cx DkQeS6+di/QFyDafl+IEV6vuBa95oXdAFuQvQHYKTN0B0l1yfUvoU9RLwwrmZJW1 0Ns94plM/TNpNkfjDxOzL5ejiZD/Wps2vcwx6UvispGePBH8BdEkvvvej+guktnE ZXfTC6Ptzxl62a7fqMtewDdh2RDavEVghouARdsF2ewHuYMhjMUMm6+kgFICbsi+ AYjlhnR3TA1uH/pB+1hil6LprY/kpugASwfIjOaPjm1X0HHOIWmz/1nRHuzh4hqX VLZMakaWmjIglYQyjBASivQvXJ7rdTr7hDASIKy5cUBsEjuyePxqpoIHoU081YWc bvlm46IZXmKJQmnDi6yNDGxeHmzMgrFXRObIYptxGabOtADLGc/LknRui3+PmiJ/ SqrQuHoIcS13B5BoyFwjh98rEuuVM2WqM1L05skZnvRFfmddSAoz1lyOAB5cl1zK ue3XQfsT35R1wLQwzGn8CLRbTlyBSXIVPpdmA/sRwUZ/PepfhLvIbdB5GPlQnRwJ +OCKGxMQsMf4j2384V1jNlQO6nQ4tZBXxBznItsn1Fyq2UJKVnoA1jHk7FK6o2yu ZXFwTNBlHrD7hzVItmV/v1006FmJDfcfgo/tdT1rBmMWhdcujTu0Cd8DZ+/H6Jt7 iTT878tMzCYV6SHMBywr =kW8C -----END PGP SIGNATURE----- --=-=-=--