This issue is to kick off a conversation leading to a formal governance document for all Bluesky Projects. Initial goals:
Survey existing governance models for multi-institution software collaborations.
Draw on both internal and external experience that has been offered. (Several folks have written these kinds of these before I have lessons learned.)
I hope that we can work toward something that welcomes new collaborators and institutions to the project and makes them feel secure in its direction and long-term prospects. I anticipate that this will not change too much the way that normal operations proceed in the projects, but an agreed-upon process is a good thing to have before you need it.
I believe that Bluesky should also adopt a Code of Conduct. I am not sure yet whether that belongs is a separate conversation or as part of this one. They are usually separate documents, but perhaps they could be developed as part of the same process.
This issue is to kick off a conversation leading to a formal governance document for all Bluesky Projects. Initial goals:
I hope that we can work toward something that welcomes new collaborators and institutions to the project and makes them feel secure in its direction and long-term prospects. I anticipate that this will not change too much the way that normal operations proceed in the projects, but an agreed-upon process is a good thing to have before you need it.
I believe that Bluesky should also adopt a Code of Conduct. I am not sure yet whether that belongs is a separate conversation or as part of this one. They are usually separate documents, but perhaps they could be developed as part of the same process.