From: Rich Freeman <rich0@gentoo.org>
To: gentoo-project@lists.gentoo.org
Subject: Re: [gentoo-project] Re: [gentoo-dev-announce] Call For Agenda Items - 10 Jun 2014
Date: Sat, 7 Jun 2014 16:05:37 -0400 [thread overview]
Message-ID: <CAGfcS_mhtuyVi2i-5cK5VVPvAUu=1NBpuHNK5=-pjgstX_o6Mg@mail.gmail.com> (raw)
In-Reply-To: <1402162558.1662.0@NeddySeagoon_Static>
On Sat, Jun 7, 2014 at 1:35 PM, Roy Bamford <neddyseagoon@gentoo.org> wrote:
> The foundation do not need to be involved any more that they are now.
> Anyone can apply for foundation funding for a project.
> As an individual trustee, I don't see this project as any different to
> any other project that way apply for funding.
I think the idea is that the policy would be that the Foundation would
agree to not fund services that didn't follow the guidelines.
The rationale would be that if somebody hosts a service funded by the
Foundation and it gets used to serve malware then the Foundation might
be legally responsible. That is why most organizations don't let
random people run its webservers/etc without any kind of adherence to
central administration/security/etc. Or perhaps Foundation funds get
used to build some service, but because there is no coordination with
infra there is no way to ever move it into production and it just
fizzles out.
This wouldn't be about keeping people from running services, but
rather encouraging it in a way that makes it safer for the community,
gives recognition to those who built it, and gives it some kind of
roadmap to being a full-fleged Gentoo service. Maybe it creates a way
to on-board new devs into Infra as well.
I'm talking about services - if somebody wants a sparc under their
desk not generally exposed to the world advertising its services under
the Gentoo name then there really isn't any need for this.
I imagine most organizations do it this way. If some Google employee
wants to build a development tool or a 10% project hosted on a PC in
their cube most likely the policy requirements are minimal, but on the
other hand if somebody is touching some server that actually generates
content that goes out under the google.com domain then I'm sure the
red tape gets fairly thick.
If we're not going to give any kind of Foundation preference to
following the new guidelines, then I don't really see the point in
going forward with it.
Rich
next prev parent reply other threads:[~2014-06-07 20:05 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAGfcS_nydQyxTBw1h0J37o2k7hTRDCdEyy=z=f02geLtauy++Q@mail.gmail.com>
2014-05-29 13:56 ` [gentoo-project] Re: [gentoo-dev-announce] Call For Agenda Items - 10 Jun 2014 Ulrich Mueller
2014-05-29 19:03 ` Andreas K. Huettel
2014-05-29 21:45 ` [gentoo-project] Maximum number of EAPIs in tree (was: Call For Agenda Items - 10 Jun 2014) Ulrich Mueller
2014-05-29 23:27 ` Rich Freeman
2014-05-30 0:11 ` Jeroen Roovers
2014-05-30 1:31 ` Rich Freeman
2014-05-30 1:33 ` Ulrich Mueller
2014-06-05 16:06 ` [gentoo-project] Re: [gentoo-dev-announce] Call For Agenda Items - 10 Jun 2014 Richard Yao
2014-06-05 16:42 ` Brian Dolbec
2014-06-05 16:55 ` Rich Freeman
2014-06-05 16:56 ` Tom Wijsman
2014-06-03 22:02 ` Andreas K. Huettel
2014-06-07 17:35 ` Roy Bamford
2014-06-07 20:05 ` Rich Freeman [this message]
[not found] ` <CAGfcS_nkawNaJ58cFh1bezQOWe_kNczDfkBC=J0+zEu2chMg4Q@mail.gmail.com>
2014-06-05 6:10 ` [gentoo-project] [gentoo-dev-announce] " Ulrich Mueller
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='CAGfcS_mhtuyVi2i-5cK5VVPvAUu=1NBpuHNK5=-pjgstX_o6Mg@mail.gmail.com' \
--to=rich0@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