From: josh@joshtriplett.org
To: "H. Peter Anvin" <hpa@zytor.com>
Cc: ksummit-discuss@lists.linuxfoundation.org
Subject: Re: [Ksummit-discuss] [TOPIC] Services needed from kernel.org
Date: Tue, 20 May 2014 15:53:01 -0700 [thread overview]
Message-ID: <20140520225301.GC21744@cloud> (raw)
In-Reply-To: <537BA385.6090208@zytor.com>
On Tue, May 20, 2014 at 11:48:37AM -0700, H. Peter Anvin wrote:
> I have been discussing with the Linux Foundation about if there are any
> new IT services needed or desired for kernel developers (maybe or maybe
> not under the kernel.org.) The kernel.org cleanup and inevitable
> changes meant we couldn't service some of the needs that we had in the
> past, some of which has moved to privately owned equipment and some of
> which has migrated to cloud services or discontinued.
>
> However, the big question is: what IT services do kernel developers
> need, and how can we best provide them? One idea bandied about would be
> to provide either managed or unmanaged VMs to kernel developers. Would
> that reduce the workload on the upper tier of kernel developers so that
> we can focus more on our time on what actually provides value to our
> users and employers, and which we hopefully find more interesting/fun?
How feasible is it to support git hooks that want to construct and send
(significant volumes of) email, while retaining the security and
sandboxing currently being applied to git repositories?
- Josh Triplett
next prev parent reply other threads:[~2014-05-20 22:53 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-20 18:48 H. Peter Anvin
2014-05-20 22:53 ` josh [this message]
2014-05-20 23:28 ` James Bottomley
2014-05-20 23:46 ` Jiri Kosina
2014-05-21 0:40 ` Konstantin Ryabitsev
2014-05-21 17:17 ` H. Peter Anvin
2014-05-21 17:37 ` Andy Lutomirski
2014-05-21 18:12 ` Josh Triplett
2014-05-21 15:18 ` David Howells
2014-05-21 16:15 ` Konstantin Ryabitsev
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=20140520225301.GC21744@cloud \
--to=josh@joshtriplett.org \
--cc=hpa@zytor.com \
--cc=ksummit-discuss@lists.linuxfoundation.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