Follow up on Robyn proposal

Eric Christensen sparks at fedoraproject.org
Mon Apr 29 14:40:08 UTC 2013


-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512

On Mon, Apr 29, 2013 at 08:42:57AM -0500, Bruno Wolff III wrote:
> On Mon, Apr 29, 2013 at 09:24:23 -0400,
>   Eric Christensen <sparks at fedoraproject.org> wrote:
> >
> >Quite frankly, all this talk has me thinking that we're trying to run Fedora like a company.  If we want our product to be X then we have to allocate people, money, and resources over there.  Well, this isn't a company and we don't have control over what the people are going to work on.  We need to let the people do their thing and support them through education initiatives, making sure that lines of communication are available, and to make sure we're one big group that is there to help each other out.
> 
> We do have some control over resources. We have money that gets used
> to fund things like Flock, FUDcons and media. The board can ask
> people to give higher priority to some tasks relative to others.
> That doesn't magically make things happen, but can influence where
> contributors decide to spend their time.

Flock, FUDcons, and other similar events are supposed to be open to EVERYONE.  I would argue that we do have control over monies that could be used for FADs but those are generally started at the SIG level and should be something that we, the Board, should encourage when a SIG has a formal task they feel is important enough to need to get people together.

Sure, the Board can ask that some tasks happen but we really shouldn't outside of getting a solid base out the door.  If there are enough developers that want to have a "server spin" (for lack of better vocabulary) then there will be one.  We can't dictate that there will be an amateur radio spin just because we want one.  If the people aren't there then neither will the output.

- --Eric
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.13 (GNU/Linux)

iQGcBAEBCgAGBQJRfoZFAAoJEB/kgVGp2CYvwVIL/12uOXWo9qjb/1T7Uk8ZPscE
+2hGxkQQH/2qbglySJC27zT4FNyypmL4bZLEQpLnB4qn3j+VLtyvqkRuOyn7KyRZ
3h+XZbAUmGPUAGvLZ1a+wB6W3O6gFHT3Oiq9K9BaRKDgEZt4m7SguNe4VPS57J6y
w4pRG7WF4n3Cz6/2DWD2tkXN6bjXs/i2K/NqkzLGAGY/1mQE/WIZKCgKY4lTCrMY
lqPRW1FHyz8VGmfuE7+2Hthqy+x2jMcHU8Jg9WBm1RRRLYFaSdAzp8mwYRDRZb6o
RniHo+4/JYgGiWJruI+9tgADCDJPdji1e3XAycZB7vxLC4Tw4h1eMrRXisKybX2R
O11nlo5kfhnvPF3QOx3VJ4+U5NBi7wXcFcmPNkG4o8y/pair1XZQt5SPylhP79/1
glQVaEQaC0TlJoei825LukxJy2CTp8mvg4Z1GnfRi0WXS9bCNeAKrwJZcMoHfpJK
CnzVUsAr5XtsahLKwDWghJjFUdi/2Zipta1jE9IfTQ==
=BWQs
-----END PGP SIGNATURE-----


More information about the advisory-board mailing list