We would like for Andrew to become a dev. He has been helping with maintenance of voip related packages (linphone and mediastreamer). After reviewing his contributions, hasufell and I think this is the logical step. I will be his mentor, hasufell will assist in mentoring.
Hello, I just sent my ebuild quiz to recruiters@g.o
Ping. Any news on ebuild quiz review and irc recruitment interview schedule? Also I'm CCing sci team since I already proxy-maintain some sci packages and plan to join them after and if all recruitment sucseedes.
(In reply to Andrew Savchenko from comment #2) > Ping. > > Any news on ebuild quiz review and irc recruitment interview schedule? > Also I'm CCing sci team since I already proxy-maintain some sci packages and > plan to join them after and if all recruitment sucseedes. Hi, There are other recruits before you so it may take sometime (not a lot) for a recruiter to become free and handle this bug. In the meantime, this should not stop you on working on the end-quiz. We will need both to complete the review sessions. Once approved by your mentor, please send it to us.
Hello, OK, I'll work on the end-quiz then. However, looks like quiz docs should be updated, ATM they state that end-quiz must be completed at the end of mentoring period (or earlier at developers opinion): http://www.gentoo.org/proj/en/devrel/quiz/ "Once the mentoring period is completed (or during the mentoring period, at the developer's option) the developer must also submit the end of mentoring quiz." So this statement let me to assume that I don't need to complete end-quiz before the first interview.
(In reply to Andrew Savchenko from comment #4) > However, looks like quiz docs should be updated, ATM they state that > end-quiz must be completed at the end of mentoring period (or earlier at > developers opinion): This is a common misunderstanding. When the docs claim at the end of the monitoring process, they mean after you had some time to work with your mentors. The review process with a recruiter should happen when the mentoring process is over, or reaching it's end. Thus, the end quiz should be completed "before" the recruitment starts.
(In reply to Jorge Manuel B. S. Vicetto from comment #5) > (In reply to Andrew Savchenko from comment #4) > > However, looks like quiz docs should be updated, ATM they state that > > end-quiz must be completed at the end of mentoring period (or earlier at > > developers opinion): > > This is a common misunderstanding. When the docs claim at the end of the > monitoring process, they mean after you had some time to work with your > mentors. The review process with a recruiter should happen when the > mentoring process is over, or reaching it's end. Thus, the end quiz should > be completed "before" the recruitment starts. I updated the docs like this http://sources.gentoo.org/cgi-bin/viewvc.cgi/gentoo/xml/htdocs/proj/en/devrel/quiz/index.xml?r1=1.11&r2=1.12
(In reply to Andrew Savchenko from comment #4) > OK, I'll work on the end-quiz then. Is this finished by now?
Hello, No, but I'm planning to send it for review by my mentor in a few days.
ping again?
Hello, I'm still here, sorry for delay. Will send end quiz to my mentor in a day.
(In reply to Andrew Savchenko from comment #10) > Hello, > > I'm still here, sorry for delay. Will send end quiz to my mentor in a day. Any progress?
Hi, half of quiz is completed now. Will do the other part till weekend (I'll have few extra free days this week.)
Hello, there is some progress here. I completed the end of mentoring quiz and sent it to my mentor for review.
I just sent end-of-mentoring quiz to recruiters@g.o.
Dear all, I'd like to inform you that I'll be unavailable from July 11th till July 28th. It is most likely I'll be offline during this period. (Just in case you have plans to arrange some quiz discussion or other appointment during mentioned time interval.)
Status here?
(In reply to Justin Lecher from comment #16) > Status here? Both quizzes are at the recruiters.
Ok.
I will be your recruiter. Always add a comment to this bug when you send something to that address. 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.
Hello, (In reply to Justin Lecher from comment #19) > I will be your recruiter. > Always add a comment to this bug when you send something to that address. > Please contact me by IRC or email to schedule the first review session. I just sent you an e-mail. > 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. OK. Should I use #gentoo-comrel for pings?
(In reply to Andrew Savchenko from comment #20) > OK. Should I use #gentoo-comrel for pings? I will keep #bircoph-review open until everthing is finished.
What we did: - LDAP - bugzilla - cvs/git groups on cvs.gentoo.org - IRC cloak - sent you your LDAP/mail password via encrypted mail Pending: - announcement Automatic: - gentoo-core - gentoo-dev-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 - Register to wiki.gentoo.org with your @gentoo.org e-mail address using the following instructions: https://wiki.gentoo.org/getting-started - 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.
(In reply to Justin Lecher from comment #22) > Pending: > - announcement Send
He looks inactive for a long time
I know you are involved in the summer of code project, but you still didn't commit anything and your packages need some attention... should we proceed with the reassignment then? :/
Hi! I right now I'm travelling, so my options are limited and I've set up devaway appropriately. I'll return at 12th July. Since I already told many times I'll commit something let's set up the deadline by 16th July 0:00 UTC. If I'll make no commits by than, start reassignment.
OK!
First to go: fixed bug 195461 by commit 24d104cdffb3fd63356d3b9aadadc34ba10c3779.
As for linphone update: can't push to the tree right now due to dep on net-libs/ortp update which is maintained by another dev. I'
[sorry, some brother glitch resulted in the message being sent prematurely] As for linphone update: can't push to the tree right now due to dep on net-libs/ortp update which is maintained by another dev. I'm preparing this update with dependencies now, thanks to rion's overlay this is much easier than from scratch, but still requires some work.
There's new commit activity (2018-07-03), so closing.
First mail sent.
gentoo.git access disabled.
(In reply to Michał Górny from comment #33) > gentoo.git access disabled. Re-enabled on 15th per email.
Let, me reply here, since I have technical diffuculties with sending e-mail. From: Andrew Savchenko <bircoph@gentoo.org> To: retirement@gentoo.org Cc: Michal Gorny <mgorny@gentoo.org> Subject: Re: Requesting status update for developer bircoph Date: Sat, 4 Mar 2023 23:20:57 +0300 Hi! On Sat, 4 Mar 2023 14:51:06 +0000 (UTC) Michal Gorny wrote: > Dear Andrew, > > We are in the process of requesting status updates for developers that > haven't committed anything in the gentoo.git tree for more than two > months. > > > It appears your last commit was on 2022-10-28 Sorry for inactivity: a combination of health problems and other issues. I'm working on imlib2 update. Will try to commit within a week. > Please consider dropping some of your packages to maintainer- > needed@gentoo.org so other people can step up and maintain them in case > you have no time anymore. If this is a viable option for you, please > send an e-mail to the gentoo-dev mailing list telling others which > packages are up for grabs. I will consider dropping some packages, e.g. pygame_sdl2. The only motivation for me to support this package was renpy, which is not in the tree now due to python2 removal. Though renpy 8 now supports python3, to be realistic I don't have resources to readd and support it. Maybe I should write a call on gentoo-dev for those interested in renpy games. Best regards, Andrew Savchenko [application/pgp-signature (Good signature)] Signature made at Sat 04 Mar 2023 11:20:58 PM MSK
As for e-mail problems: I can receive messages via pop3, but can't send them via smtp: [23:23:40] ESMTP> AUTH PLAIN ******** [23:23:42] ESMTP< 535 5.7.8 Error: authentication failed: authentication failure I use sylpheed-3.7.0. My guess that there is something wrong with SPF validation of this e-mail as described in the wiki:https://wiki.gentoo.org/wiki/Project:Infrastructure/Developer_E-Mail#Sender_Policy_Framework Though I was unable to find what exactly is wrong with outgoing e-mail (error message from the server is not suitable for debugging), how to explicitly set up sylpheed to work with Gentoo SPF validation or how to set sylpheed to work with another MTA. Help is welcome, thank you.
Please file a bug in the Infra component or join #gentoo-infra to seek help.
We had a glibc-related upgrade hiccup, mail is fixed again.
Second mail sent.
Hi! I'm still here. Will resume activities within 15 days.
(In reply to Andrew Savchenko from comment #41) > I'm still here. Will resume activities within 15 days. Very well. However, it's already time for third mail, so sending it now.
Third mail sent.
