astropy / astropy-project

Documents and policies regarding the Astropy Project as a whole.
Creative Commons Attribution 4.0 International
36 stars 43 forks source link

Request for a new repository (Community Management repository) #368

Closed BerylKanali closed 10 months ago

BerylKanali commented 10 months ago

Description

I am requesting for a new repository as suggested by Moritz. This repository will have all the work and code used in the community management work. This includes community data, engagement tracking scripts, GitHub actions, and output data(which can be later added to the website), survey data and reports that are currently ongoing and any other community work. We have been doing some work on engagement tracking and we have been keeping the work in private repo but we talked about moving it to the Astropy GitHub since we have made good progress.

As the current community manager, I will be responsible for keeping the repository up to date. Here is a link to how the repo will look like, Astropy community management repo it is currently on my personal account and we have been working on Organizational Mycology's GitHub account as well. @jduckles will be helping me set up this new repository and ensuring it has everything we had envisioned.

cc: @astropy/community-managers, @astropy/coordinators

pllim commented 10 months ago
  1. Is this requested repo public or private?
  2. Our policy recommends we provide access by team, so does that mean you will be added to @astropy/community-managers or something else? @kelle ?
BerylKanali commented 10 months ago

@pllim

  1. Ideally it should be public so that the reports we will be updating and plots can be visible to the Astropy community before we figure out how to create a dashboard or add them on the website.
  2. Our policy recommends we provide access by team, so does that mean you will be added to @astropy/community-managers or something else? @kelle ?

@kelle and @eteq can answer this second question.

kelle commented 10 months ago

I just updated the membership of the @astropy/community-managers team. So should be good for that team to be assigned the new repo.

pllim commented 10 months ago

@kelle , while we're at this, shouldn't the GitHub team membership be consistent with "Community engagement coordinator" names on https://www.astropy.org/team website?

GitHub: astrofrog, eteq, adrn, kelle, eblur, BerylKanali

Website: BerylKanali, mwcraig, kelle, Cadair, eteq

Can I go ahead and clean up the GitHub team?

kelle commented 10 months ago

Go for it! Thanks!

pllim commented 10 months ago

I see jduckles was invited to the GitHub team but he is not on the website. (I cancelled the invitation.)

kelle commented 10 months ago

Regarding Jonah: What's the best way to make it so github will autocomplete/autosuggest his name when we're trying to tag people?

pllim commented 10 months ago

You could do something similar to https://github.com/orgs/astropy/teams/astroquery-triage where you can add people but only give them Triage access to the repo.

pllim commented 10 months ago

I have created a new public repo https://github.com/astropy/community_management/ and added the following teams as admin:

Please do not post sensitive data there. This would include PIIs and so on.

Since the original request has been satisfied. I am closing this issue. Thanks for your work!