I'd like to bring Richard on board to help out with the nascent QA project Brutalis, as well as general QA project work. He'd also like to help maintain a few packages, as well as joining the Ruby herd (pending approval from them). Eroyf will help with mentoring to help him get a feel for the process. Email: mynamewasgone@gmail.com IRC nick: rbrown`
Bug taken.
Ok, quiz had been sent. I reviewed it, had 3 slight issues. New answers have been resent, i reviewed and accepted it. LDAP done, core done, bugs.g.o account done, forums done, gentooAccess done, #gentoo-dev done. From my side everything is done.
Should be all setup. Feel free to reopen this bug if something is missing.
Please proceed with retirement procedures, reference bug 216219, however use this bug for processing.
Fixed in the forums.
- Removed gentoo/developer cloak on freenode - Removed #gentoo-dev access - Reassigned all remaining bugs
dev/cvs/lists/ldap done
- Removed from proj/ pages.
(In reply to comment #4) > Please proceed with retirement procedures, reference bug 216219, however use > this bug for processing. > Please open bug 216219 --- it's useless to reference it otherwise.
Created attachment 151218 [details] Excerpts
(In reply to comment #9) > (In reply to comment #4) > > Please proceed with retirement procedures, reference bug 216219, however use > > this bug for processing. > > > > Please open bug 216219 --- it's useless to reference it otherwise. > Again, no excerpts please. As (I believe) Mark noted, we are supposed to be open, and if we are retiring people based on a hidden bug, that is not open. There's nothing in the excerpts that would seem to me to justify firing someone without any normal process. The log excerpts do not have dates on them so I don't know when they happened, but for them to fall under "critical so that devrel lead can fire them bypassing any normal process" I'd hope they were very recent. Things that happened long ago are not critical pretty much by definition. So Council, please open your locked bug.
> He added an -r0 of an ebuild, making it the only -r0 in the entire tree. > This seems coincidentally shortly after ferringb said rbrown discovered > a pkgcore bug that broke in this case. That would imply rbrown purposely > broke another non-paludis package manager. Just want to comment on this specifically: 1) I'm pretty sure rbrown has already explained more than once that this was an accident 2) As far as I know, the pkgcore bug was discovered /because/ of this ebuild; no-one knew about it before it was added 3) Paludis, and I think Portage, also had bugs that were uncovered by this So, accusing him of deliberately breaking pkgcore and using it as a reason to retire him seems rather... disingenuous, to say the least.
- removed from metadata.xml files - removed from all herds
- Planet done and retirement procedure completed.
