Rearrangement of ENCCS Github Repositories

All ENCCS Lessons (105 Repositories) ## 1. Lessons should be published on [ENCCS lesson webpage](https://enccs.se/lessons/) - [Quantum Autumn School 2024](https://enccs.github.io/qas2024/) - there is a separate repo [QAS24_Finance](https://github.com/ENCCS/QAS24_Finance) - if this repo is a part of QAS24, please create a link at QAS24 pointing to [QAS24_Finance](https://github.com/ENCCS/QAS24_Finance) - Thor: AA needs to say how this should be included - [intro-cmake](https://enccs.github.io/intro-cmake/) - Thor: how does this relate to https://github.com/ENCCS/cmake-workshop? - it is a shortened version from **cmake-workshop** - [plasma-pepsc-workshop](https://github.com/ENCCS/plasma-pepsc-workshop) - Thor: need to add to lessons page and track on Plausible! - add to the `awosome HPC resources` - [veloxchem-hpc](https://enccs.github.io/veloxchem-hpc/) - update the link to this repo at ENCCS lesson page - Juan will join us and work on this repo - [HIP101](https://enccs.github.io/HIP101/) - Thor: it's incomplete. Publish only if it's first completed - delete this (yl) - provide more hip part at the `gpu programming` - [intro-gpu-programming](https://enccs.github.io/intro-gpu-programming/) - Thor: I suggest renaming. "Introduction to GPU programming" implies there's more technical material, but this lesson only covers concepts. So maybe "Key Concepts in GPU Computing" - YL will take this repo - [ju-systems-applications-procedures](https://enccs.github.io/ju-systems-applications-procedures/) - maybe we can update this repo before publish it - this can be used as a template for us to guide new clients when they are interested to apply for EU hpc sources but don't know what to prepare - @erik - Thor: we can ==archive== it i think, it's not complete and the contents fit better in a slide deck - [colonyos-tutorial](https://github.com/ENCCS/colonyos-tutorial/tree/main) - Thor: publish! - [Upscaling AI with Containers](https://enccs.github.io/upscalingAIcontainer/) - Thor: see below - [Upscaling AI Workflows](https://enccs.github.io/upscalingAIworkflows/) - Thor: see below - [Upscaling AI Training](https://enccs.github.io/upscaling-ai-training/) - Thor: the three "upscaling AI" lessons have overlaps - probably only two should be kept. Some consolidation may be necessary - keep the `workflow` repo and archive the other two repos - ashwin - [NVIDIA Bootcamp](https://github.com/ENCCS/Nvidia-Bootcamp) - Thor: what to do with this? Maybe just link somewhere as external training material - add a link to `hpc resources` - [deep-learning-intro](https://github.com/ENCCS/deep-learning-intro) - Thor: add Plausible integration and publish https://enccs.github.io/deep-learning-intro/ - ==a small group on web-design to improve lesson page== ## 2. Categorize github repositories - most repos are for lesson materials, we do need some specific repos as listed below - repo to store configuration files - [devops](https://github.com/ENCCS/devops) - [docker](https://github.com/ENCCS/docker) - [.github](https://github.com/ENCCS/.github) - francesco - repo to share external lesson materials - [awesome-high-performance-computing](https://github.com/ENCCS/awesome-high-performance-computing) - repo to store files for training event organization (registration, survey, *etc.*) - [**see the 4th category**](https://hackmd.io/T5Ls3k_SRTm-JWMuU_do5A#4-Merging-some-repositories) --- --- ## 3. Repositories should be rearranged some repos are relevant to ENCCS, but not active now, and therefore we should archive these repositories - [contemporary-nlp](https://github.com/ENCCS/contemporary-nlp) - keep it What to do with following repositories? - [port-to-lumi](https://enccs.github.io/port-to-lumi/#/) - add to `gpu programming` - mini page of the lesson - qiang --- --- ## 4. Merging some repositories ### 4.1 **Hackmd documents**: how to handle hackmd documents for our training events? - 1. leave everything on the web - 2. only leave the `schedule` one on the web and remove others - where to store these hackmd notes? using github repos - store all notes in one github repo - store notes to be workshop-dependent notes - we have to repos for all hackmd notes - [course-notes-archive](https://github.com/ENCCS/course-notes-archive) - [md_docs_for_workshops](https://github.com/ENCCS/md_docs_for_workshops) - a step further to distribute/merge notes in these two repos - ==yl will merge all hackmd documents== ### 4.2 **documents for event organization (registration, survey, *etc.*)** - [event-organisation](https://github.com/ENCCS/event-organisation) - [services-survey-2023](https://github.com/ENCCS/services-survey-2023) - [training-hackathon](https://github.com/ENCCS/training-hackathon) - [training-needs-survey](https://github.com/ENCCS/training-needs-survey) - [event-registrations](https://github.com/ENCCS/event-registrations) - [event-surveys](https://github.com/ENCCS/event-surveys) - [training-landscape](https://github.com/ENCCS/training-landscape) - [reporting](https://github.com/ENCCS/reporting/tree/main) - ==yl will take care of this== --- --- ## 5. Reorganize repositories for a workshop We can deliver a regular workshop on the `OpenACC-CUDA` topic - [OpenACC-CUDA-beginners](https://github.com/ENCCS/OpenACC-CUDA-beginners) - [cuda](https://enccs.github.io/cuda/) - [openacc](https://enccs.github.io/openacc/) ## 6. Future lesson developments - anyone interested in developing something new? - what's the status with OpenFOAM lesson? - Mathworks wants to collaborate with us. Business lunch in Krakow next week. Any opinions? ## 7. Explore Hartree centre training platform - https://hartreetraining.stfc.ac.uk/ - they use https://www.totara.com/us/ - slides from CASTIEL2 event on certification will probably be added here eventually: https://bscw.hlrs.de/sec/bscw.cgi/1815144 :::danger :::