Mass removal from committers for afedorov3un
Summary
I have got notifications about removal from committers
Steps to reproduce
https://projects.eclipse.org/user/11593
What is the current bug behavior?
I have no committer rights anymore
What is the expected correct behavior?
I don't know
Relevant logs and/or screenshots
Priority
- Urgent
- High
- Medium
- Low
Severity
- Blocker
- Major
- Normal
- Low
Impact
Perhaps, several Eclipse projects will not be active
Activity
mentioned in issue eclipsefdn/emo-team/emo#380 (closed)
mentioned in issue #4398 (closed)
added IT-priorityhigh IT-severitymajor statetodo team:webdev labels
The EMO records team requested this on 03/06/24, and my presumption is that your paperwork is no longer valid, but I don't know. Your best bet is to engage with @emo-team or emo-records@eclipse-foundation.org to resolve the issue.
/cc @skilpatrick
removed team:webdev label
added team:projects label
removed IT-severitymajor label
removed IT-priorityhigh label
assigned to @mdelgado624
I hope that this is an easy to resolve issue for @afedorov3un.
I accidentally noticed that Alexander had been removed as a committer. Is it possible for Project leads and/or PMCs to be proactively notified about such changes, ideally ahead of time to allow us to help the committer resolve paperwork issues if that ends up being the case here?
Speaking as a project lead or committer on many of the projects that Alexander has been removed from I also hope that once issues are resolved he can simply be reinstated and won't require new elections.
A couple of internal people have also questioned our communications around these kinds of events, so I expect there will more discussions about how it's handled in future.
My concern with roping in PLs and PMCs is that it's just one more thing to deal with, and there may be nothing more they can do than we have.
Fortunately these situations are usually temporary and once the issue is fixed, we reinstate the committer on all of the relevant projects automagically.
My concern with roping in PLs and PMCs is that it's just one more thing to deal with, and there may be nothing more they can do than we have.
Fair enough - I was quite surprised by the removal as I hadn't seen that happen for someone active before. I leave it for you all to figure out what is best, but if you are looking for an external sounding board I can provide my 2cents (along with the Architecture Council no doubt)
Fortunately these situations are usually temporary and once the issue is fixed, we reinstate the committer on all of the relevant projects automagically.
That is great to hear. Relieved that we don't have to redo loads of elections.
Hello,
Alexander's committer account was temporarily suspended as we received a bounce-back from his email account on file (alexander.fedorov@arsysop.ru). This is standard practice in cases where a committer is no longer able to be reached by email. If you could please confirm Alexander's current email address, we can update his contact details and restore his account to full functionality.
-
The bounceback was reported after we attempted to send you a committer document for your signature. If you are confident that there are no issues with your email account, we can restore your access and try again.
Edited by Shawn Kilpatrick
-
@afedorov3un We have now reinstated access to your committer account so you should once again have full access to your projects. We have also re-sent the document to your email address. Please confirm that you have received it.
@skilpatrick I have the following related emails in my alexander.fedorov@arsysop.ru mailbox
There was nothing with attachments today and also nothing in Spam folder. I have no idea why some emails from your side are being delivered well and others maybe not.
The last email with attachment from EF side in my alexander.fedorov@arsysop.ru mailbox is
If I can help somehow to trace the problem I'm open to assist.
-
That's very strange. I can only assume that this is an issue with Dropbox Sign, as your email account seems to be functioning normally. I will cancel the existing document and create a new one to send to you shortly. Please let me know if it is received, if not I will contact Dropbox Sign to see if there is an issue at their end. Thanks for your patience with this.
Hello @skilpatrick It seems that documents was not delivered to my alexander.fedorov@arsysop.ru mailbox
I"m going to close this for now, as I presume @afedorov3un and @skilpatrick are working on the signing issue on a different channel.
