6 Editorial Governance
This chapter explains management of the blog editors GitHub team and the process for staff-authored posts.
6.1 GitHub team
rOpenSci blog editors are the member of the @ropensci/blog-editors
team.
The team is maintained by @stefaniebutland
at the moment.
Blog editors can be tagged in any ropensci repo, in particular roweb3, by writing
@ropensci/blog-editors
(e.g.:wave: @ropensci/blog-editors, I have trouble adding citations in my post!
).Blog editors have write access to the roweb3 repo.
Blog editors are “code owners” of
roweb3/content/blog
,roweb3/content/commcalls
according to roweb3’s CODEOWNERS file so any PR touching a file under these paths will automatically request their review. When one of them posts a review, it will be marked as “on behalf of@ropensci/blog-editors
”.
For adding a new blog editor, the team maintainer or any ropensci admin
ensures the user has enabled 2FA,
adds them to the team as Member (the default role).
The blog editors can filter their notifications, e.g. using the reason:team-mention
filter.
The blog editors don’t necessarily have write access to the blog-guidance repo but are encouraged to make PRs.