search

nodejs / admin

Administrative space for policies of the TSC
153 stars 134 forks source link

bot for crowdin? #785

Closed richardlau closed 10 months ago

richardlau commented 1 year ago

I'd like to suggest a dedicated GitHub bot account for syncing with CrowdIn. We're currently using https://github.com/nodejs-github-bot, which is owned by the Build WG. This is problematic as there are only a handful of people with access to the appropriate area of Build's GPG encrypted secrets repository who are able to log into this account. Also https://github.com/nodejs-github-bot is a Node.js collaborator with write access to nodejs/node and I think it would be a better idea to have a dedicated bot with write permissions scoped to the website repository.

My suggestion would be a dedicated bot owned by the managers for Node.js CrowdIn, possibly with the details stored in 1password.

I believe we used to do the sync via https://github.com/nodejs-crowdin -- I have no idea who owns that account (it is not Build).

nschonni commented 1 year ago

docker-node also uses this bot. Would you also like to change that? Could be split to a separate issue to track though

richardlau commented 1 year ago

docker-node also uses this bot. Would you also like to change that? Could be split to a separate issue to track though

I wasn't aware of that. I think it's worth considering.

mhdawson commented 1 year ago

+1 to @richardlau's suggestions.

ovflowd commented 1 year ago

+1 to @richardlau's suggestions.

ovflowd commented 1 year ago

I still believe we need to recover access to the original Bot, as it is the project's owner. We might need to check with the people that created this integration back then.

image

ovflowd commented 1 year ago

I've tried to send a recovery request for password... Maybe the e-mail address in question is an alias for anything from the TSC?

image

ovflowd commented 1 year ago

Maybe @alexandrtovmach?

richardlau commented 1 year ago

According to @ovflowd the Crowd-in integration is currently broken. If we cannot recover the original https://github.com/nodejs-crowdin bot account, perhaps we should create a new one?

mhdawson commented 1 year ago

Maybe the e-mail address in question is an alias for anything from the TSC?

I don't remember seeing anything related when you did the reset but it was a while ago. Maybe worth trying again and I'll keep an eye out.

targos commented 1 year ago

I just found this issue: https://github.com/nodejs/nodejs.dev/issues/438 It seems @zeke might have some information.

ovflowd commented 1 year ago

Hey y'all is there anything we can do? At the moment the integration still seems to be broken. Having a new Bot would be great, or recovering the current one.

ovflowd commented 1 year ago

FYI I opened a PR https://github.com/nodejs/email/pull/219 to add myself to this email alias. Maybe this is useful for getting access to the Bot.

ovflowd commented 1 year ago

FYI, apparently, my e-mail got added there, but still, if I try to send anything to nodejs-crowdin@iojs.org I get nothing. I guess I'm stuck here and help would be appreciated 🙇

ovflowd commented 11 months ago

FYI I'm in talks with GitHub Support to disable 2FA on that account, and we're trying to get access back to the account.

mhdawson commented 11 months ago

Good to hear. It is strange that one alias is not working while the others do. Adding somebody else's email to see if they get the mail might be a next thing to try on that front.

ovflowd commented 11 months ago

Good to hear. It is strange that one alias is not working while the others do. Adding somebody else's email to see if they get the mail might be a next thing to try on that front.

I finally was able to get the email, after changing the recipient email, but it seems sorta flaky

mhdawson commented 11 months ago

k good to hear you are getting the emails.

ovflowd commented 10 months ago

Closing as this was completed!