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
{{ message }}
This repository has been archived by the owner on Feb 8, 2023. It is now read-only.
I propose creating a separate ipfs-labs Github org to house repositories that are not formally supported by the IPFS project. This creates a space for us to incubate new ideas, experiments, and specialized repositories that don't belong in the ipfs org.
It also allows us to have distinct security models for the two orgs, where access to the formally supported stuff in the ipfs org is more tightly controlled (for example, as a security precaution @flyingzumwalt is not an admin on the ipfs org but could be an admin on ipfs-labs for convenience of community management)
I propose creating a separate ipfs-labs Github org to house repositories that are not formally supported by the IPFS project. This creates a space for us to incubate new ideas, experiments, and specialized repositories that don't belong in the ipfs org.
It also allows us to have distinct security models for the two orgs, where access to the formally supported stuff in the ipfs org is more tightly controlled (for example, as a security precaution @flyingzumwalt is not an admin on the ipfs org but could be an admin on ipfs-labs for convenience of community management)
Examples of things that could go in ipfs-labs:
The text was updated successfully, but these errors were encountered: