The code base, including the history of commits, needs to be checked for the following prior to this repo becoming public:
[x] PID - Personally IDentifying information. I doubt this will be a huge issue, but make sure you don't have anything you don't want to be public. One particular issue is the UCF Network ID. I think UCF now has instituted a <first_name>.<last_name>@ucf.edu email scheme so you don't have to give out half of your credentials every time you send an email. If so, and it's not too difficult to do, we might want to change some of the commit signatures. It's not the particularly important half of the credentials to keep secret, but still. That leads to point 2...
[x] Passwords. Yeah, not something you want to make public. Kinda not the point at all there.
[x] Etc. To be defined on a person to person basis.
@chfleming, @georgeomics, @Bvpboy and myself will all need to sign off on each (especially the last). We can just do this by responding to this issue as we feel we have checked it over sufficiently.
The code base, including the history of commits, needs to be checked for the following prior to this repo becoming public:
<first_name>.<last_name>@ucf.eduemail scheme so you don't have to give out half of your credentials every time you send an email. If so, and it's not too difficult to do, we might want to change some of the commit signatures. It's not the particularly important half of the credentials to keep secret, but still. That leads to point 2...@chfleming, @georgeomics, @Bvpboy and myself will all need to sign off on each (especially the last). We can just do this by responding to this issue as we feel we have checked it over sufficiently.