Should this repo remain public or move to private?

[eap]

In the recent Terraform config migration pull request (https://github.com/JCSDA-internal/github-admin/pull/40) we uncovered the fact that this repository is listed as public and thus, readable by non-logged-in and non-JCSDA users on the internet.

@srherbener added this comment quoted below:

I'm not aware of the need for the ioda-data repo to be public. When we push releases to the public organization, the corresponding (tagged) contents of the ioda-data repo should be downloaded in a tarball from a server (UWisc or S3 - I don't remember where off-hand).

My preference would be to make ioda-data private, but I think we need to determine why it was made public in the first place. @mer-a-o do you have any insight on this? Thanks!

This issue tracks the resolution of this decision. The public status can be changed by editing the Terraform config (tf/configuration.tf) in our github-admin repo.

[climbfuji]

I don't think there was any intention behind it. When you look at our repos, it seems to be accidental. ioda-converters is public, ioda is private. soca is public, fv3-jedi is private.

So my suggestion is to leave things as they are for the purpose of the terraform work, and revisit all repositories in AOP24 - we need to do a major sweep, archive repos, delete old repos, etc.

[climbfuji]

I moved this to the icebox for now and unassigned Maryam - assigned myself instead.

[eap]

@eap @srherbener - discuss this with Phil and Tom