From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-dev@lists.gentoo.org
Subject: [gentoo-dev] Re: Automated Package Removal and Addition Tracker, for the week ending 2015-09-06 23:59 UTC
Date: Tue, 8 Sep 2015 03:30:51 +0000 (UTC) [thread overview]
Message-ID: <pan$5e172$3ccca2a8$b7f2873d$303ff43b@cox.net> (raw)
In-Reply-To: 20150907235436.GF4589@orbis-terrarum.net
Robin H. Johnson posted on Mon, 07 Sep 2015 23:54:36 +0000 as excerpted:
> I've been travelling a lot the past month (Helsinki, LA, Seattle), and
> it's on my list of stuff to do (along with finalize and announce the
> migrated git history).
[grumble grumble, top posting, tho you just followed what you were
replying to, but it still makes it all but impossible to quote proper
context, so I only did one level deep]
This is definitely not a personal complaint as I know you're doing what
you can and will get to it in due time, and I'm immensely grateful that
we have you working on it at all and that the git switch did actually
happen even if it seemed to be an instance of DukeNukem:Forever, but...
The above has me somewhat concerned. Any time an individual has to make
excuses for something as ultimately critical to an organization as
finishing up the loose ends on the git switchover is to gentoo, the words
"bus factor" loom large in my head.
Is it simply that while others can do it, you were the one who
volunteered, as you could make at least enough time to get the basics
squared away in a relatively immediate timeframe, and will do the rest
later, but there's others who would have eventually (perhaps months, or
even a year or two later) gotten to it were you to meet some misfortune,
or is it really down to (singular) YOU, and there's reason to worry, not
just because of that, but because of the inevitable overwork and burnout
such a situation unfortunately tends to lead to?
IOW, is there something the council or foundation needs to do proactively
here to ease a pressure point before something blows and it's reactive,
or are there human backups in place and tested/ready-if-needed just as
surely as are the server backups?
--
Duncan - List replies preferred. No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master." Richard Stallman
next prev parent reply other threads:[~2015-09-08 3:31 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-07 0:05 [gentoo-dev] Automated Package Removal and Addition Tracker, for the week ending 2015-09-06 23:59 UTC Robin H. Johnson
2015-09-07 0:10 ` Dale
2015-09-07 15:59 ` Daniel Campbell
2015-09-07 16:27 ` Dale
2015-09-07 17:46 ` malc
2015-09-07 23:54 ` Robin H. Johnson
2015-09-08 3:30 ` Duncan [this message]
2015-09-08 11:48 ` [gentoo-dev] " Philip Webb
2015-09-08 14:35 ` malc
2015-09-08 17:48 ` Duncan
2015-09-08 16:29 ` [gentoo-dev] " Dale
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='pan$5e172$3ccca2a8$b7f2873d$303ff43b@cox.net' \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-dev@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