Why this repository is not public?

[BulatSaif]

Why this repository is not public?

1. This repository was created mostly for internal usage https://github.com/paritytech/devops/issues/1299
2. The repository is private, but GitHub pages is public because sometimes we need to allow partners to connect. But we don't want random nodes to connect to our internal test chains and spoil the tests.
3. we should have a single source of truth, and for public chains we already have it : binary (e.g --chain kusama)

There are no problems to make this repo open-source (we can remove private chainspec). We can open-source this repo if it will be useful for the community. Parity has a lot of open-source.

[nuke-web3]

Redundant, possibility conflicting, sources of truth for various networks is not ideal. If the goal here is to have things for parity to use for convince, that's great. But IMHO if this goes public it should be the source of truth as opposed to the repositories that store the network code. But also that doesn't make much sense to me, the closer that is to the code the better (likely)

[PierreBesson]

I think we could envision having this repository as some kind of source of truth or pipeline to publish chainspec to cloud (S3) or decentralized storage (IPFS) but we would need additional trust mechanism for external people to independently verify the validity of the published chainspecs (eg. timestamping the IPFS CIDs on chain). However the devops team might not be qualified enough to provide such a system.
The rationale for creating this repo was simply to provide convenient URLs for accessing chainspecs and removing the existing chainspec files being commited to our internal repos (eg. ansible collections).

[PierreBesson]

The repo was just made public.