All of lore.kernel.org
 help / color / mirror / Atom feed
From: John David Anglin <dave.anglin@bell.net>
To: Thibaut VARENE <T-Bone@parisc-linux.org>
Cc: dann frazier <dannf@dannf.org>,
	linux-parisc List <linux-parisc@vger.kernel.org>,
	taggart@lackof.org, bame@riverrock.org,
	"Carlos O'Donell" <carlos@systemhalted.org>
Subject: Re: decommissioning parisc-linux.org
Date: Sat, 11 Feb 2012 17:41:43 -0500	[thread overview]
Message-ID: <BLU0-SMTP7852C9372515DE54919E3697790@phx.gbl> (raw)
In-Reply-To: <CA+DQjFicockZMkgKNwF=5Dk--gWraTfZg5mo1Ph8BnQjYkfK8A@mail.gmail.com>

On 11-Feb-12, at 5:12 PM, Thibaut VARENE wrote:

> Erm, it appears I didn't make myself clear: I'm willing to provide the
> /hardware/ for buildd setup, but I certainly do not have time to tend
> to routine buildd maintenance, as I've mentioned already. I understood
> that at some point Carlos wanted to handle that part, but from what I
> gather, he's also busy so it's probably not happening. I agree we need
> someone to take care of the buildds, but I'm afraid it cannot be me.


I understand.  I'm willing to take care of the buildds, and do whatever
porting and patches that need doing as I can.  What I meant is that
you have to be in charge of system security as impacts the cluster
as a whole.  In particular, I think you will have to be involved in the
firewall setup.

I wasn't asking you to support the general system updates or buildd  
maintenance.

I will try to setup the autobuilders and hopefully Dann can answer any
questions that might arise.  The big question is the is the upload  
process
which I'm totally unfamiliar with.  There is also the security updates.

I don't know how busy Carlos is at the moment and whether he is still  
interested
in helping.  I know he gets impossible projects from time to time.

Dave
--
John David Anglin	dave.anglin@bell.net




  reply	other threads:[~2012-02-11 22:41 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-02-08 14:33 decommissioning parisc-linux.org dann frazier
2012-02-08 22:16 ` Thibaut VARENE
2012-02-08 23:47   ` John David Anglin
2012-02-09  1:53     ` John David Anglin
2012-02-09 14:54       ` John David Anglin
2012-02-09 15:41         ` Paul Bame
2012-02-09 17:55     ` dann frazier
2012-02-11 19:11       ` John David Anglin
2012-02-11 22:12         ` Thibaut VARENE
2012-02-11 22:41           ` John David Anglin [this message]
2012-02-11 23:26             ` Thibaut VARENE
2012-02-11 23:29             ` Carlos O'Donell
2012-02-12  0:25               ` John David Anglin
2012-02-14 18:05         ` dann frazier
2012-02-14 18:31           ` Thibaut VARENE
2012-02-14 18:33             ` Carlos O'Donell
2013-01-23 21:17               ` dann frazier
2013-01-23 23:14                 ` John David Anglin
2013-01-23 23:32                   ` dann frazier
2012-02-09 17:56   ` dann frazier
2012-02-09 19:18     ` Martin K. Petersen
2012-02-09 20:49       ` dann frazier
2012-02-12 14:38 ` James Bottomley
2012-02-12 14:49   ` James Bottomley
2012-02-12 20:01     ` James Bottomley
2012-02-12 22:47       ` Carlos O'Donell
2012-02-12 22:56         ` John David Anglin
2012-02-13  2:22           ` Carlos O'Donell
2012-02-13  5:20             ` James Bottomley
2012-02-13 22:26           ` Carlos O'Donell
2012-02-13  4:05       ` Grant Grundler
2012-02-13  5:19         ` James Bottomley
2012-02-14 18:06         ` dann frazier
2012-02-13 11:23       ` Thibaut VARENE
2012-02-14 13:41         ` Thibaut VARENE
2012-02-14 18:06       ` dann frazier

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=BLU0-SMTP7852C9372515DE54919E3697790@phx.gbl \
    --to=dave.anglin@bell.net \
    --cc=T-Bone@parisc-linux.org \
    --cc=bame@riverrock.org \
    --cc=carlos@systemhalted.org \
    --cc=dannf@dannf.org \
    --cc=linux-parisc@vger.kernel.org \
    --cc=taggart@lackof.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.