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
