Repository private
Closed this issue · 4 comments
@MPAS-Dev/all-developers, is there any reason why we have this repository marked as private when MPAS-Model and MPAS-Tools are public?
It might have been the case that we wanted to do some clean-up before making the repository public, but others may remember more correctly than I can whether this was the case.
I could see arguments both ways. I think this repo is a bit of a mess and I'm not sure I'd welcome pull requests from non-core developers. At the same time, as changes get made, they need to get documented. Over all, I'm not a big fan of having several repos that have to be synchronized. I think we should ideally keep the (always up-to-date) documentation side-by-side with the code version it is meant to document. But I guess that ship has sailed...
We had planned to make this repo public when we discussed in last spring. That is still the plan, we just didn't pay attention to it.
Q: When you live in a glass house, does it need to be clean?
A: Now that everyone lives in a glass house, nobody cares.
Here is the initial discussion for repo organization:
https://docs.google.com/document/d/1MGYIydK9ufuqfUySkbxcusPSPL9eGUphbot9-GP8DjE/edit?usp=sharing
I just revised with the most current information:
https://docs.google.com/document/d/1h5QFXcDtoX-pUSlYfJkhpb1WAF6otGbP5SZXsWInITs/edit?usp=sharing
I'm closing this. The repo is now public.