GRIFFINCollaboration / detectorSimulations_v10

Geant4 version 10 of the simulation code for the GRIFFIN array and it's suite of ancillary detection systems.
MIT License
9 stars 14 forks source link

Suppressed files #78

Open VinzenzBildstein opened 1 year ago

VinzenzBildstein commented 1 year ago

I just noticed when signing in on gitlab, that there is a warning message that our collaboration there is exceeding the limit of 5 free members. This means it could get changed into read-only (which I assume means we won't be able to add more people to it) unless we upgrade the account to a paid one (which we won't do).

I don't know if this limit is a recent change or just something they never enforced, but it means we will have to think of another way to provide access to the suppressed files. I checked GitHub (which nowadays also allows private repo's), but their limit is even lower at maximum 3 users. So I think having a private repository might not be the solution. I thought about setting up a repo-server on one of our computers here in Guelph, but since they are now behind a firewall that isn't a solution either.

One option would be to create a group user on gitlab to replace all other users and simply provide the ssh-key for that user via email. This would allow people to get the newest version of the suppressed files (assuming anything changes in them) after getting the key once via email, instead of emailing the files themselves.

Another option might be to encrypt the suppressed files and then add them to this repository. In that case we would have only a single repository to deal with, and users would only be required to email me for the password (or someone else who knows it).

Does anyone have any other options or a strong opinion for one option or the other?