Details
-
Type:
RFC
-
Status: Implemented
-
Resolution: Done
-
Component/s: DM
-
Labels:None
Description
[Sorry this is more of an announcement than a discussion, but this seems like the right crowd for it]
For historical reasons [^1] there are 80+ current and former project members in the lsst-sqre Github org. The reason for it is moot, and the org is used for production-critical gitops activities, so anyone who is not an active code contributor or service maintainer will be removed.
- There is no intent to prevent anybody who actually needs org membership from having it. If you find yourself in this position after the purge, leave a note here.
- If you are not a SQuaRE developer or a maintainer of services on SQuaRE-managed clusters, there are no extant services that you should be getting access to through this route. If you find that after your removal you have lost access to a service you are using, leave a note here
[^1] a little experiment called nublado.lsst.codes on a small google cluster grew up and flew the coop, and sqre-friends was the team that allowed access to it.
Attachments
Activity
| Field | Original Value | New Value |
|---|---|---|
| Description |
[Sorry this is more of an announcement than a discussion, but this seems like the right crowd for it]
For historical reasons [^1] there are 80+ current and former project members in the lsst-sqre Github org. The reason for it is moot, and the org is used for production-critical gitops activities, so anyone who is not an active code contributor or service maintainer will be removed. * There is no intent to prevent anybody who actually needs org membership from having it. If you find yourself in this position, leave a note here. * If you are not a SQuaRE developer or a maintainer of services on SQuaRE-managed clusters, here are no extant services that you should be getting access to through this route. If you find that after your removal you have lost access to a service you are using, leave a note here [^1] a little experiment called nublado.lsst.codes on a small google cluster grew up and flew the coop, and sqre-friends was the team that allowed access to it. |
[Sorry this is more of an announcement than a discussion, but this seems like the right crowd for it]
For historical reasons [^1] there are 80+ current and former project members in the lsst-sqre Github org. The reason for it is moot, and the org is used for production-critical gitops activities, so anyone who is not an active code contributor or service maintainer will be removed. * There is no intent to prevent anybody who actually needs org membership from having it. If you find yourself in this position after the purge, leave a note here. * If you are not a SQuaRE developer or a maintainer of services on SQuaRE-managed clusters, here are no extant services that you should be getting access to through this route. If you find that after your removal you have lost access to a service you are using, leave a note here [^1] a little experiment called nublado.lsst.codes on a small google cluster grew up and flew the coop, and sqre-friends was the team that allowed access to it. |
| Description |
[Sorry this is more of an announcement than a discussion, but this seems like the right crowd for it]
For historical reasons [^1] there are 80+ current and former project members in the lsst-sqre Github org. The reason for it is moot, and the org is used for production-critical gitops activities, so anyone who is not an active code contributor or service maintainer will be removed. * There is no intent to prevent anybody who actually needs org membership from having it. If you find yourself in this position after the purge, leave a note here. * If you are not a SQuaRE developer or a maintainer of services on SQuaRE-managed clusters, here are no extant services that you should be getting access to through this route. If you find that after your removal you have lost access to a service you are using, leave a note here [^1] a little experiment called nublado.lsst.codes on a small google cluster grew up and flew the coop, and sqre-friends was the team that allowed access to it. |
[Sorry this is more of an announcement than a discussion, but this seems like the right crowd for it]
For historical reasons [^1] there are 80+ current and former project members in the lsst-sqre Github org. The reason for it is moot, and the org is used for production-critical gitops activities, so anyone who is not an active code contributor or service maintainer will be removed. * There is no intent to prevent anybody who actually needs org membership from having it. If you find yourself in this position after the purge, leave a note here. * If you are not a SQuaRE developer or a maintainer of services on SQuaRE-managed clusters, there are no extant services that you should be getting access to through this route. If you find that after your removal you have lost access to a service you are using, leave a note here [^1] a little experiment called nublado.lsst.codes on a small google cluster grew up and flew the coop, and sqre-friends was the team that allowed access to it. |
| Remote Link | This issue links to "Page (Confluence)" [ 31071 ] |
| Status | Proposed [ 10805 ] | Adopted [ 10806 ] |
| Resolution | Done [ 10000 ] | |
| Status | Adopted [ 10806 ] | Implemented [ 11105 ] |
| Remote Link | This issue links to "Page (Confluence)" [ 31138 ] |