Closed jessb0t closed 2 years ago
HPC setup
GitHub access levels:
GitHub Template Repos
GitHub<>G-Drive
GitHub<>HPC
discuss a protocol for testing permissions on the cluster (https://docs.google.com/document/d/10EHzRBb-cDgUiG0nORX48JTeXH6esSpmeTTV00AGTVE/edit#)
moved ahead with cron jobs for repos and lab scripts. Will update with any correction from IRCC
BLOCKED template-tool automatically sets protected branches on dev using github actions. included additional documentation
virtual desktop x11
who should be able to run lab scripts? (given the permissions they have?)
generated issues for lab scripts & updated docs
Google Drive Cleanup
baseEEG Can't move these items:
Per George:
for baseEEG, we can't actually move all that. that is mainly used to house data, and that cant be moved to gh and also cant go on the hpc because people without hpc access need it.
devOps Review these items together. Delete or integrate.
GitHub Cleanup
For projects like Criticality that are on pause, we want a place to park "on pause" gh repos so they are not just sitting in our public profile as if they are active/real projects.
i think we want to either "hide" the gh repo (can we do that? maybe we make it private or something? or we clone it to hpc and delte the gh repo? or, we update the readme as you said.
OSF v Zenodo v OpenNeuro v GIN
Wiki Readme
Moved issues, closing
Retrospective (<15 mins; reflect on processes that did/did not work) Sprint review (15 mins: review what was completed/ not completed) Planning (60 mins: discuss/plan work for next sprint and finalize milestone)