[Discussion] Future of Important Repos in the cloudfoundry-community Organisation

[vipinvkmenon]

What

The most important repositiories that are consumed and maintained in the cloudfoundry-community org must be protected.

Why:
With the recent unavailability of the cloudfoundry-community due to its deletion/attack many of the repositories such as go-cfclient & cf-terraform-provider that were important to developers/users were unavailable.

From discussions, it is understood that this org is not in the purview/control of the CloudFoundry Foundation. (Admins are people from Stark & Wayne?)

How
Therefore, I request the KeyMembers/Drivers/Administrators of the CloudFoundry Foundation to either take control of the org OR fork the most important and popular repositories (or all) to the foundation so that it will be protected, standardized and well maintained.

[bgandon]

Right after the incident, we've stripped down to few people that are trustworthy.

The current reduced set of admins are from the CF Foundation, the Gstack (myself) and the FiveTwenty consultancies, which are companies actively involved in maintaining the community's projects.

We are working on re-organizing the way we give access in the future, so that we eliminate risks of similar incidents.

Long story short, this is being worked on. A blog post will also do a full recap of facts and outcomes.

[beyhan]

There is a summary of the incident and taken actions to restore trust in the cloudfoundry-community org here. Additionally, we discussed this topic during the TOC meeting on 13th of February (recording).

Therefore, I request the KeyMembers/Drivers/Administrators of the CloudFoundry Foundation to either take control of the org OR fork the most important and popular repositories (or all) to the foundation so that it will be protected, standardized and well maintained.

The driving party here should be the maintainers of those repositories. They should initiate discussions with the CFF and the TOC. From the TOC side we can help to execute the move when we have an agreement.

[vipinvkmenon]

The driving party here should be the maintainers of those repositories. They should initiate discussions with the CFF and the TOC. From the TOC side we can help to execute the move when we have an agreement.

Makes sense. I believe we should try to get in touch with the maintainers (at least for the active projects that are maintained and heavily used) and work with them to move their repos to the CF Foundation.

For eg: cloudfoundry/go-cfclient#379

[beyhan]

We discussed this during the TOC meeting today. Our advice for the maintainers willing to move their repositories into the cloudfoundry org is to start the discussion by opening an issue in this repository.