Adding meeting's notes 2023-06-15 and fixing date on older ones

docs/events/meeting-notes/2023-05-18.md

@@ -11,15 +11,15 @@
     * Sherif
 
 ## Discussions:
-     Chris: Are we willing to support all openHPC stack or just the modules and how we imagine achieving this?
+Chris: Are we willing to support all openHPC stack or just the modules and how we imagine achieving this?
-     Jeremy: Clear a bit of distro related stuff from openHPC would be great such as automake / autoconf
+Jeremy: Clear a bit of distro related stuff from openHPC would be great such as automake / autoconf
-     Stack: We need to have a base line so people can start use rocky on HPC and make Rocky accessible
+Stack: We need to have a base line so people can start use rocky on HPC and make Rocky accessible
-     Chris: A Demo / technical talk in 4 weeks
+Chris: A Demo / technical talk in 4 weeks
-     Chris: Are we going to focus on 8 and 9?
+Chris: Are we going to focus on 8 and 9?
-     Stack and Chris, would be great if we can focus on 9
+Stack and Chris, would be great if we can focus on 9
-     Sherif: I hope we can do both but with 9 in the spotlight "this needs to be a SIG decision"
+Sherif: I hope we can do both but with 9 in the spotlight "this needs to be a SIG decision"
-     Stack: Question, if we start moving openHPC within HPC sig are they going support more distros, we don't want to break packages for other EL distros
+Stack: Question, if we start moving openHPC within HPC sig are they going support more distros, we don't want to break packages for other EL distros
-     Chris: so far testing on Rocky as the only supported EL distro
+Chris: so far testing on Rocky as the only supported EL distro
 
 ## Action items:
     * Get a demo / technical talk after 4 weeks "Sherif can arrange that with Chris"

docs/events/meeting-notes/2023-06-01.md

@@ -8,17 +8,17 @@
     * Chris Simmons
 
 ## Discussions:
-    Getting toolchains outside of openHPC such as automake
+Getting toolchains outside of openHPC such as automake
-    Greg: We need to talk if we need to have a generic SIG for toolchains
+Greg: We need to talk if we need to have a generic SIG for toolchains
-    Greg: We need to look into adding more release packages such as intel compiler
+Greg: We need to look into adding more release packages such as intel compiler
-    Brain storm ideas about optimizing binaries
+Brain storm ideas about optimizing binaries
-    David: What would be the interest of having a light weight kernel for HPC
+David: What would be the interest of having a light weight kernel for HPC
-    Jeremy: mentioning intel light weight kernel https://github.com/intel/mos
+Jeremy: mentioning intel light weight kernel https://github.com/intel/mos
-    Chris: asking if there is any benchmark, hard numbers between shipped kernel and light weight kernel, so far, nothing solid
+Chris: asking if there is any benchmark, hard numbers between shipped kernel and light weight kernel, so far, nothing solid
-    Sherif: Slurm now is build but not in standard path and we agreed we are going to move standard path 
+Sherif: Slurm now is build but not in standard path and we agreed we are going to move standard path 
-    Greg: make sure you have the provide type
+Greg: make sure you have the provide type
-    Chris: also make sure that downgrade works
+Chris: also make sure that downgrade works
-    Greg and Chris, we can also contribute to openHPC documentation
+Greg and Chris, we can also contribute to openHPC documentation
 
 ## Action items:
     * Get a list of packages from Jeremy to pick up from openHPC

docs/events/meeting-notes/2023-06-15.md

@@ -0,0 +1,52 @@
+# SIG/HPC meeting 2023-06-01
+
+## Attendees:
+    * Chris Simmons
+    * Nick Eggleston
+    * Forrest Burt
+    * Stack
+    * David DeBonis
+    * Jeremy Siadal
+    * Greg Kurtzer
+    * Sherif
+
+## Discussions:
+
+Chris gave a quick demo about openHPC / presentation 
+Jeremy sent the packages
+Greg: asked how the SIG's slurm is compatible with openHPC
+Sherif needs to look at openHPC slurm packages
+Chris we need to look on how to build easybuild and look into how to improve it
+Chris and Greg talking about if there is any standard that explains how to build systems compatible with each others, openHPC does follow best practices from different entities
+Chris provided https://github.com/holgerBerger/hpc-workspace which now a part of openHPC
+Sherif mentioned, forums category is now in place https://forums.rockylinux.org/c/sig/hpc/61
+
+## Action items:
+    * Sherif to look int openHPC slurm spec file
+    * We need to get lists of centres and HPC that are moving to Rocky to make a blog post and PR
+
+## Old business:
+
+## 2023-06-01:
+
+    * Get a list of packages from Jeremy to pick up from openHPC - Done
+    * Greg / Sherif talk in Rocky / RESF about generic SIG for common packages such as chaintools
+    * Plan the openHPC demo Chris / Sherif - Done
+    * Finlise the slurm package with naming / configuration - Done
+
+## 2023-05-18:
+    * Get a demo / technical talk after 4 weeks "Sherif can arrange that with Chris" - Done
+    * Getting a list of packages that openHPC would like to move to distros "Jeremy will be point of contact if we need those in couple of weeks" - Done
+
+## 2023-05-04
+    * Start building slurm - On going, a bit slowing down with R9.2 and R8.8 releases, however packages are built, some minor configurations needs to be fixed -
+    * Start building apptainer - on hold -
+    * Start building singulartiry - on hold -
+    * Start building warewulf - on hold -
+    * Sherif: check about forums - done, we can have our own section if we want, can be discussed over the chat -
+
+## 2023-04-20
+    * Reach out to other communities “Greg” - on going -
+    * Reaching out for different sites that uses Rocky for HPC “Stack will ping few of them and others as well -Group effort-”
+    * Reaching out to hardware vendors - nothing done yet -
+    * Statistic / public registry for sites / HPC to add themselves if they want - nothing done yet -