agenda-devOps 8/3 -- PLEASE COMMENT

[jessb0t]

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)

[jessb0t]

HPC setup

37

[jessb0t]

GitHub access levels:

• 50

• wiki issue 41

• 78: review lab-wide default settings

GitHub Template Repos

• Do we need/want templates for PRs on template-research and template-tool to help enforce our new etiquette rules? If so, what should those look like? [FS, #77]

GitHub<>G-Drive

• What issues do we need to create connections that will facilitate research projects and avoid manual duplications?

GitHub<>HPC

• What issues do we need to create connections that will facilitate research projects and avoid manual duplications?

[F-said]

• discuss a protocol for testing permissions on the cluster (https://docs.google.com/document/d/10EHzRBb-cDgUiG0nORX48JTeXH6esSpmeTTV00AGTVE/edit#)

  • access-list is not always obvious. It would be a good idea to test the locks before putting additional data
  • What would it take to be compliant?
  • Completed audit of HPC, all set!
  • Completed first draft of tech manual, will update wiht Soft. Dev. lifecycle process

• 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?)

[F-said]

generated issues for lab scripts & updated docs

• lab technology manual edit

• 79

• 80

• PR Template for template-tool (https://github.com/NDCLab/template-tool/pull/3)

• 72

• 74

[jessb0t]

Google Drive Cleanup

baseEEG Can't move these items:

• https://drive.google.com/drive/u/1/folders/1gsEFYHksRzznmDSi5WHV87uY0rNUlWO7
• https://drive.google.com/drive/u/1/folders/1zU3UchvrRLFnVVebLSy1Mhg8wYMAmGy-

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.

[jessb0t]

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.

[jessb0t]

OSF v Zenodo v OpenNeuro v GIN

• Limitations
• GitHub Integrations
• Datalad Integrations
• Popularity/Acceptance

[jessb0t]

Wiki Readme

• Image options: held within _assets or copy/paste (user content).
• Markdown follow-up.

[F-said]

• Updated lab scripts
  • bad input handling
  • internal documentation
  • true mirror for repo updates
• Started creating PEPPER wiki doc
• Working w/IRCC to resolve accidental deletion
• Create plan to migrate structure
• Publish docker images to docker-hub for convenience?
• stumped on tfpca size.
  • 5 GB of data as well, maybe we can remove from repo? Keep on local

[F-said]

• resolve tfpca by removing git history regarding data

[F-said]

Moved issues, closing