From: Aaron Bauman <bman@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Questions for Council candidates: Future of the Foundation
Date: Mon, 29 Jun 2020 13:41:45 -0400 [thread overview]
Message-ID: <20200629174145.GB109251@bubba> (raw)
In-Reply-To: <15474247.tgchFWduMW@noumea>
[-- Attachment #1: Type: text/plain, Size: 2080 bytes --]
On Mon, Jun 29, 2020 at 05:38:16PM +0300, Andreas K. Huettel wrote:
> > Q1: What are your feels on the recent history of the Foundation? (last
> > 2-3 years)
> > Q2: What should the Foundation do more of?
> > Q3: What should the Foundation do less of?
>
> One of my pet projects was already to get Gentoo to sponsor (up to a cap)
> expenses for *one* conference attendance for each new developer. I.e. up to
> XXXX EUR cost reimbursement (travel, accommodation, daily living expenses at
> capped/set rate, similar to what is done for public servants like me) for
> FOSDEM attendance. This might be quite helpful in getting new devs integrated
> into the community.
>
+1 Of note, there is some financial considerations here dependent on the
501cX chosen.
> > Q4: What should become of the Foundation?
> > * something not the following list at all?
> > * long-term continue to exist as-is non-501c6 state
> > * finish 501c6 state
> > * convert to 501c3 in some way
>
> If it continues to exist, convert to a tax-exempt state. Preferably 501c3. See
> below.
>
+1
> > * join an umbrella?
> > ** what should the selection criterion be?
> > * disband entirely
> > ** where should the financial holdings go?
> > ** where should the copyright & trademark holdings go?
> > ** what actions will be impacted by this?
>
> I was recruited in 2010, and there was never any doubt for many years that the
> foundation was a mostly passive observer of the distribution, without
> interfering in the daily business.
> In the wake of the idella4 story and the subsequent "takeover attempt", I
> would like to make sure 100% that this never happens again and that developers
> know which elected group steers the distribution (the council).
>
I am not aware of what that individual did, but I am familair with him
so I can only imagine. Please see my response to Robin as well with
other ways of addressing such shenanigans from occuring. I believe it
paramount that we retain our autonomy as a distribution.
--
Cheers,
Aaron
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
next prev parent reply other threads:[~2020-06-29 17:41 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-29 6:30 [gentoo-project] Questions for Council candidates: Future of the Foundation Robin H. Johnson
2020-06-29 8:27 ` Ulrich Mueller
2020-06-29 15:58 ` Rich Freeman
2020-07-04 16:33 ` Andrew Savchenko
2020-07-04 21:43 ` Rich Freeman
2020-07-05 0:57 ` Alec Warner
2020-07-05 3:20 ` Aaron Bauman
2020-07-06 19:30 ` Alec Warner
2020-07-06 21:11 ` Aaron Bauman
2020-07-06 22:49 ` Alec Warner
2020-07-07 2:35 ` Aaron Bauman
2020-07-05 11:02 ` Andreas K. Hüttel
2020-06-29 14:38 ` Andreas K. Huettel
2020-06-29 17:41 ` Aaron Bauman [this message]
2020-06-29 17:19 ` Aaron Bauman
2020-07-01 19:36 ` Brian Dolbec
2020-07-02 21:26 ` William Hubbs
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200629174145.GB109251@bubba \
--to=bman@gentoo.org \
--cc=gentoo-project@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox