Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

New Website / Tweeters Volunteer: andrewgdick #94

Open
IstoraMandiri opened this issue Dec 23, 2022 · 3 comments
Open

New Website / Tweeters Volunteer: andrewgdick #94

IstoraMandiri opened this issue Dec 23, 2022 · 3 comments

Comments

@IstoraMandiri
Copy link
Contributor

Following up on ethereumclassic/ethereumclassic.github.io#1039, this issue is to document the on-boarding process of a new user to the @ethereumclassic/tweeters and @ethereumclassic/website teams.

The new on-boarding process requires some checks to help keep the org secure.

This issue is open to everyone including the new volunteer to provide additional details or objections before existing volunteers make a recommendation to @ethereumclassic org admins to add as a volunteer to help manage tweets.

Volunteer @andrewgdick
2FA ?
Contributions ETC Coop (is this alone enough)
Anti-Sybil Public Profile, Vouched for by Donald / Bob
@IstoraMandiri
Copy link
Contributor Author

IstoraMandiri commented Dec 23, 2022

My only concern here is that 'being a member of ETC coop' may not be considered by some to be a reasonable standard for past contributions.

Open to comments about how to handle this one. Bureaucracy shouldn't get in the way of pragmatism and we can update the on-boarding process if we need to, perhaps by adding an option for vouching or 'under supervision of', etc.

In addition we might want to add a rule that PRs must be approved by at least one person that is not part of the same team (ETC coop), allowing these teams to delegate without sacrificing broader community input.

@IstoraMandiri IstoraMandiri changed the title New Website / Tweetres Volunteer: andrewgdick New Website / Tweeters Volunteer: andrewgdick Dec 23, 2022
@ghost
Copy link

ghost commented Dec 23, 2022

In addition we might want to add a rule that PRs must be approved by at least one person that is not part of the same team (ETC coop), allowing these teams to delegate without sacrificing broader community input.

As long as the people who manage reviewers are independent I don't see any hazard. From the moment there is a malicious intent we can revert the action and remove the bad actor.
My initial thought that it didn't make much sense that the Coop goes through the internal reviewing process and then replicates it on GitHub but then I thought that when they review it publicly it's really transparent and best practise for ETC.

It is true that we have a better track history of Bob and Donald, not sure how newer community members selected by the Coop, or other organisations, can demonstrate more contributions than the task they signed up for. Probably in an ideal world but here I lean to give the benefit of the doubt and start creating some momentum => Green light from me.

@TheCrowbill
Copy link
Member

As I said in the original discussion, I have no objection to adding @andrewgdick to the review team. I would encourage others to volunteer as well.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants