You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'd like to create a bus-factors resource page for Pangeo so that people can find the necessary owners when organizing events and to minimize risks of the community losing important resources.
Here's what I think would be the most helpful information to maintain bus-factor information on:
Making this a public resource would minimize effort for organizers, but increases the risk of people being targeted in phishing attempts. If this can be public, it could just be hosted as a markdown file in https://github.com/pangeo-data/governance. For slightly more restricted access, it could be a private repo in https://github.com/pangeo-data. The most restricted option would be hosting the information in a google drive or private Discourse Channel owned by the Steering Council, but that wouldn't help solve the first motivation for these docs.
The text was updated successfully, but these errors were encountered:
I'd like to create a bus-factors resource page for Pangeo so that people can find the necessary owners when organizing events and to minimize risks of the community losing important resources.
Here's what I think would be the most helpful information to maintain bus-factor information on:
Making this a public resource would minimize effort for organizers, but increases the risk of people being targeted in phishing attempts. If this can be public, it could just be hosted as a markdown file in https://github.com/pangeo-data/governance. For slightly more restricted access, it could be a private repo in https://github.com/pangeo-data. The most restricted option would be hosting the information in a google drive or private Discourse Channel owned by the Steering Council, but that wouldn't help solve the first motivation for these docs.
The text was updated successfully, but these errors were encountered: