Hi, I'd like to request full dev status for: Ole Markus With (nickname olemarkus on IRC), email: olemarkus@olemarkus.org As the php herd lay dormant for some time, users have taken over and helped enormously to get php related stuff going again. Ole has been one of them and he's been most helpful updating stuff for the imminent php-5.3 release. He's already been given access to the team's git overlay and has proven very good ebuild skills, converting a dozen packages to EAPI2 with some of them ending up in the tree already (proxied by me). Because of this, I'd like to shorten the recommended training period of 30 days to whatever he needs to get the first and second quiz accepted. The earlier we have some active devs maintaining the state of affairs of php in gentoo, the better. I'm the official mentor in this case and will continue to review his commits. Ole is usually idling in #gentoo-php, with me joining in whenever I get the time. We're both in the UTC+2 TZ, if that matters. Recruitment policy calls for the team's lead to give their approval. The php team currently does not have a lead, so I'm attesting that we very much want new developers to join the team. Thanks for your time.
I have emailed my answers to the quiz to the recruites alias. Cheers
I will be your recruiter. Please send your quizzes to recruiters@gentoo.org when approved by your mentor. Always add a comment to this bug when you send something to that address. When the quizzes are sent please contact me by IRC or email to schedule the first review session. If you think that recruiters aren't paying attention to this bug at any later point in time, it's your job to ping us on IRC if you don't want any delays. I see, that you have already sent a first version of the ebuild quiz. Please leave the questions there and put your answers after them, makes it easier for recruiters during review sessions. ;-)
Answers to both quizzes sent Cheers!
New version of the quizzes sent to recruiters. Cheers!
New version of the quizzes sent to recruiters. Thanks for your patience.
Just sent a mail about personal stuff such as keys and information about myself. Cheers!
Mail with updated answers to quizzes sent.
What we did: - LDAP - bugzilla - cvs/svn/git groups on cvs.gentoo.org - IRC cloak - sent you your LDAP/mail password via encrypted mail - announcement What you need to do: - subscribe to mailing lists with your @gentoo.org address - request forum status bump in #gentoo-forums or by mail to forum-mods@gentoo.org (if you have a forums account) - send yourself mail to check if it works - 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 - set lat and lon attributes in LDAP if you want others to know where exactly you are located - set gentooIM if you want people to be able to contact you via other means than email - If you want your blog to be syndicated to planet.gentoo.org, check http://www.gentoo.org/proj/en/userrel/planet/index.xml - contact trustees@gentoo.org for Foundation membership (optional) For the mentor: - You are also responsible for the commits of your recruit during the first month so you should watch the commits of your recruit via gentoo-commits mailing list.
I am responding to points raised in: https://bugs.gentoo.org/show_bug.cgi?id=332451#c11 > Even for QA related stuff (btw. i thought only QA people are allowed to commit > QA related stuff?) ... test it or don't commit it. Oh, and *if* you screwed up > - then at least revert the changes or fix your commits. Neither has happened. > And not reacting for now 14 days ... that's also quite bad. I didn't see this explained yet. olemarkus: Could you please explain. Mistakes are inevitable but we should be around to clean up after ourselves. > Being a mentor and having no time for Gentoo - well that's a combination that's > not going to work. Also it isn't that "optimal" to have a new dev being > responsible for such important stuff (and especially if his mentor has time > constraints). Officially mentors are only required to closely monitor new developers for one month which is now full but if no close review has been done and there's been problems due to it then we can think about extending it a little. olemarkus/mabi: Do you think there's use for searching for someone else who can offer advice/experience for a while? As for important stuff when a new developer has to take charge it means the other option is for the package not being maintained at all. I think it's a worse option. It's not optimal but usually any problems fix themselves in the long run when people get more experience.
(In reply to comment #10) > As for important stuff when a new developer has to take charge it means the > other option is for the package not being maintained at all. I think it's a > worse option. It's not optimal but usually any problems fix themselves in the > long run when people get more experience. Agreed - but usually there's a mentor around.
I obviously take the blame for not monitoring gentoo-commits as closely as I should have. Coupled with RL work load for both Ole and me came the stable hassle for php-5.3. There were issues in our planning and we missed some packages that needed changing to work with php-5.3. Fixing those seemed urgent and I guess the size of the problem combined with our time constraints was responsible for the lack of care. Points taken: I need to communicate time constraints and even halt action on bugs I can't fix with due care. I'm grateful to Ole picking up pieces, though. Well, we should not leave broken patches for 2 weeks in tree, that's obvious. I don't know why this happened, but as I said, it's bad and I apologize for not catching this. I'm now watching closely and time constraints have eased a little, allowing more testing. Dunno, I'd be glad if someone has the time to improve my/Ole's ebuild skills. Peer review is great and I wouldn't mind it if you think it'd be appropriate. I don't foresee any *big* impact commits next couple weeks, though. From what I've seen Ole has done the profiles stuff (thanks for the help on those :), and slotted php is in the tree, almost ready to be unmasked. There's still the dev-php/dev-php5 category merge, but I think nothing will move on this until php-5.3 is sorted out.
(In reply to comment #10) > I am responding to points raised in: > > https://bugs.gentoo.org/show_bug.cgi?id=332451#c11 > > > Even for QA related stuff (btw. i thought only QA people are allowed to commit > > QA related stuff?) ... test it or don't commit it. Oh, and *if* you screwed up > > - then at least revert the changes or fix your commits. Neither has happened. > > And not reacting for now 14 days ... that's also quite bad. > > I didn't see this explained yet. olemarkus: Could you please explain. Mistakes > are inevitable but we should be around to clean up after ourselves. > I have no problem with cleaning up after myself. But between the 14th and 20th I did not have time to react. Then I saw comment 8 stating it was fixed in CVS. Later, mabi even asked for next-action, but no reply came on anything needing to be done. > > Being a mentor and having no time for Gentoo - well that's a combination that's > > not going to work. Also it isn't that "optimal" to have a new dev being > > responsible for such important stuff (and especially if his mentor has time > > constraints). > > Officially mentors are only required to closely monitor new developers for one > month which is now full but if no close review has been done and there's been > problems due to it then we can think about extending it a little. > olemarkus/mabi: Do you think there's use for searching for someone else who can > offer advice/experience for a while? > I'll let mabi be the judge of this one. Anyway, I doubt the mistake I did is something I will repeat in the future. Since I am new at all of this, I also believe that things could have worked out more smoothly if the feedback I got after the mistake had been more constructive. > As for important stuff when a new developer has to take charge it means the > other option is for the package not being maintained at all. I think it's a > worse option. It's not optimal but usually any problems fix themselves in the > long run when people get more experience. > I honestly believe that a package like PHP need a dedicated maintainer, and do believe I have done a decent job there.
I should mix in to as I encouraged him to go and fix it and did not make it clear in http://bugs.gentoo.org/show_bug.cgi?id=336869#c17 that tests are absolutely necessary....so go easy on Ole, just remember the mess Chris White once caused, that was epic.
I think everything is sorted out so I am closing this bug again
I have been sort of in hiatus the last couple of months and I doubt that will change anytime soon. Please go ahead and retire me.
@infra please proceed - metadatas, projects and bugs cleaned
Nothing on planet/universe and no blog.
Forums done.
Seems that infra didn't proceed (per comments here and also I still get him listed in "slackers" periodical report to undertakers)
gitolite done
LOG: Running on oystercatcher.gentoo.org for CVS/SVN removal LOG: Removing olemarkus from groups
LOG: Running on pigeon.gentoo.org for lists LOG: Removing olemarkus from all lists.
LOG: Started on woodpecker.gentoo.org LOG: Found olemarkus. LOG: Finished at Tue Jun 20 19:37:23 UTC 2017 with rc=0
LOG: Running on grouse.gentoo.org for bugzilla retire LOG: Found 321263 for olemarkus.
infra done.
LOG: Started on woodpecker.gentoo.org LOG: Found olemarkus. LOG: Finished at Tue Jun 20 20:37:16 UTC 2017 with rc=0
LOG: Running on grouse.gentoo.org for bugzilla retire
Done: - wiki - no cloak found
