[Bug 534968] Consider permitting the creation of private/hidden repositories to address vulnerabilities

Bugzilla Link	534968
Status	NEW
Importance	P3 normal
Reported	May 22, 2018 15:05 EDT
Modified	Jun 11, 2020 16:52 EDT
Blocks	510142

Description

At present, we really don't very many things that are not accessible to the public (the only thing that comes to mind is the ability to mark a Bugzilla record as "committers-only"). This is by design: as an open and transparent community, we actively avoid any notion of private.

As we engage in more runtime projects, vulnerabilities are going to become more common and having a means for a project team to engage collaboratively is likely going to be important.

I'd like to use this record to capture requirements and related issues.

• We need a means for a project team to work in Git out of public view.\
• The public repositories must remain publicly accessible. That is, we can't just temporarily restrict access to existing repositories or development branches.\
• All project committers have access.\
• It must be short-lived (weeks, not months).

Input welcome.