Home | Docs | Forums | Lists | Bugs | Planet | Store | GMN | Get Gentoo!
View Bug Activity | Format For Printing | XML | Clone This Bug
Wulf is going to help with kde herd development. He is already working on ebuilds for the upcoming kde4.
I'm going to take a look at his quizzes once he sent them.
I've just emailed the quizzes. Thanks for your time, guys. I'd like to add to genstef's introduction that I'd like to join the amd64 team as well as that's my primary (albeit not only) platform.
(In reply to comment #2) > I've just emailed the quizzes. Thanks for your time, guys. > > I'd like to add to genstef's introduction that I'd like to join the amd64 team > as well as that's my primary (albeit not only) platform. > That's for the amd64 team to decide but I don't see why not.
phreak: What's the status here? Philantrop sent his quizes a month ago.
I'm sorry, but I won't have time for you guys next week (that's April 2nd till 6th), I'm pretty busy with work; I'll try to read my mails and look at my backlog from time to time.
(In reply to comment #5) > I'm sorry, but I won't have time for you guys next week (that's April 2nd till > 6th), I'm pretty busy with work; I'll try to read my mails and look at my > backlog from time to time. > I reviewed his quizes and was satisfied enough with his answers. I will set him up later when I have the time. Feel free to do it if you beat me to it :)
These things setup: LDAP userinfo.xml bugzilla cvs/svn groups on cvs.gentoo.org IRC-cloak announcement #gentoo-dev channel access Still to do: gentoo-core access (The mailing list manager does not let me in) What you need to do: - subscribe to mailing lists with @gentoo.org address - request forum status bump from from amne or tomk (if you have a forums account) - add yourself to mail aliases ( like java@gentoo.org ) see /var/mail/alias on dev.gentoo.org - ask team leads to add yourself to herds.xml for the herds you want to join or do it yourself if you have the permission to do so
- I've received mail on -core so I'm obviously subscribed. - I'm subscribed to -dev as philantrop@gentoo.org. - Forums account has been updated. - Got lots of spam on the kde-aliases so that works, too. ;-) - Was asked to add myself to the kde herd in herds.xml and did that. Everything seems to work just fine so far. Thank you!
(In reply to comment #8) > - I've received mail on -core so I'm obviously subscribed. > - I'm subscribed to -dev as philantrop@gentoo.org. > - Forums account has been updated. > - Got lots of spam on the kde-aliases so that works, too. ;-) > - Was asked to add myself to the kde herd in herds.xml and did that. > > Everything seems to work just fine so far. Thank you! > Marking as FIXED.
Please proceed with retirement procedures, reference bug 216219, however use this bug for processing.
Forums fixed.
- Removed gentoo/developer cloak on freenode - Removed #gentoo-dev access - Reassigned all remaining bugs
dev/cvs/lists/ldap done
- Removed from proj/ pages.
Created an attachment (id=151215) [edit] Excerpts
Why is bug 216219 restricted even to developers!? I'd really like to know what it is about.
Please open bug #216219, or do we have to get our own? Taking away our KDE project lead over night is clearly not the way to go.
Wait, exactly what is going on here? I'd say _don't_ retire Philantrop unless he wants to leave, of course. One of the biggest contributors ATM, and well appericiated among the community.
- removed from metadata.xml files - removed from all herds
- Planet done and retirement procedure completed.
(In reply to comment #15) > Created an attachment (id=151215) [edit] > Excerpts > Uh, that's the reason for retiring him without even giving notice? That's a joke, right?
Ferris, it's not a joke, it's a measure for preventing Philantrop introducing malicous code in the tree or break it: ( 16:50 musikc ) i do agree that some information should have been shared but also feel that there were concerns for potential retaliation over the possibility of the action... if that makes sense [...] ( 16:55 zlin ) musikc: what kind of retaliation? ( 16:58 musikc ) tree access i suppose ( 16:58 astinus ) pft. ( 16:59 zlin ) I don't follow ( 17:00 astinus ) zlin: People doing daft stuff in the tree like commit "wars" + EAPI-50 without prior discussion ( 17:02 zlin ) huh? ( 17:04 antarus ) while I don't think they would make malicious commits to the tree I can at least see where that fear comes from ( 17:04 antarus ) zlin: can you not? ( 17:05 zlin ) not at all ( 17:05 zlin ) they have never done any such thing ( 17:05 antarus ) ahh ( 17:05 antarus ) I know ( 17:05 antarus ) hence 'I don't think they would' ( 17:05 antarus ) but I have been wrong before ( 17:06 zlin ) and even on the odd chance that they did it wouldn't really be hard to respond swiftly and correct it.. no huge deal. ( 17:06 astinus ) zlin: With even the slightest risk/hint anyone would do something malicious to the tree, access would be immediately yanked by Infra ( 17:06 musikc ) i dont believe that people want to be malicious, but when i have seen malicious behavior has been in situations such as this ( 17:06 zlin ) exactly. but there has been no such slightest risk/hint... ( 17:06 musikc ) i view it as preventative measures [...]
You've completely lost me there. You think Wulf would destroy the tree if we just processed the complaint (from wherever it comes) normally? I guess I'm not quite so suspicious of our fellow developers.
This is a resolved bug for recruitment and retirement procedures. Please continue your conversation elsewhere.
Łukasz, I can understand your comment, but since there's no open bug about a complaint against Wulf, I don't know where else I can post any comment about his forced retirement. I just want to add a note that I had personally talked to Wulf about the issues that are listed in the excerpt and had told him imho he deserved a good "clubbing on the head". I never thought it would get to this extreme.
(In reply to comment #22) > ( 16:50 musikc ) i do agree that some information should have been shared > but also feel that there were concerns for potential retaliation over the > possibility of the action... if that makes sense If that really is the reason, and not just some lame excuse, then why not just suspend commit access? There's absolutely no need for goiNG through with the full retirement procedure so quickly.
(In reply to comment #24) > This is a resolved bug for recruitment and retirement procedures. Please > continue your conversation elsewhere. > People --- even me --- comment on closed bugs all the time in order to keep a record of events and updates, and sometimes closed bugs (perhaps even this one) get reopened and then you need the complete history. It's a real pain digging through emails and cross-referencing bugs and such. Why make this comment on this bug now? Where do you suggest for "elsewhere" --- gentoo-dev@ because the bug is public?
(In reply to comment #22) > Ferris, it's not a joke, it's a measure for preventing Philantrop introducing > malicous code in the tree or break it: > > ( 16:50 musikc ) i do agree that some information should have been shared > but also feel that there were concerns for potential retaliation over the > possibility of the action... if that makes sense > Everything else deleted. Where and when is that from? It's not identified and there's no date.
(In reply to comment #28) > > Where and when is that from? It's not identified and there's no date. > Yesterday on #-infra iirc. If that really matters, ask to any of the people who appears in the log ;-)
