Formed in 2009, the Archive Team (not to be confused with the archive.org Archive-It Team) is a rogue archivist collective dedicated to saving copies of rapidly dying or deleted websites for the sake of history and digital heritage. The group is 100% composed of volunteers and interested parties, and has expanded into a large amount of related projects for saving online and digital history.
Join GitHub today
GitHub is home to over 50 million developers working together to host and review code, manage projects, and build software together.
Sign upModeration Team features #200
Comments
|
github-bot is basically just a giant "if webhook do this" application -- would it make sense to use outgoing webhooks in the moderation team slack (I believe there is a slack for the moderation team?) as the way to interact? Or, if actions should be seen by people other than the moderation team, use comments in GitHub issues? I can't commit to implementing this stuff myself, but I am happy to mentor/pair/review if there are moderation team members willing to work on the bot :) |
|
It was pointed out by @gibfahn that the org-wide search is probably not needed. Members have read-access to nearly everything in the |
Here are some features that might make it possible to have the Moderation Team use the GitHub bot and not have to have the Owner role in the org. All these features would be available to Moderation Team members only:
Org-wide search: Just passes queries directly to GitHub search and returns the results, but it logs the fact that so-and-so searched for something on such-and-such a day. The difference between using the bot search and doing search yourself would be that the bot has access to all repositories in the org while the individual user may not. Because they would be searching sensitive information, the use of the search should be logged so that someone can audit that searching is only done for moderation purposes.
A "give me access to this repo" feature. You can instruct the bot to add you as a Collaborator or Owner on a specific repo. Again, it's logged, and maybe time-bound.
The other thing the bot will need to do is be able to block and unblock folks for us.
That might be all that's needed.
/cc @nodejs/moderation