meeting 2022 11 21 planning

Jump to bottom

Kenneth Hoste edited this page Nov 22, 2022 · 2 revisions

MultiXscale planning meeting 2022-11-21

Joining: Caspar, Satish, Kenneth, Ewald, Alan, Elisabeth, Susana, Xavier, Bob
Excused: Thomas, Henk-Jan

Notes

people per WP1/WP5/WP6 partner
- contact points per partner, how much time will you spend on this?
  - SURF: Caspar (~0.5FTE), Satish (~0.25FTE), Maksim (~0.25FTE), XXX (open vacancy)
  - RUG: Bob (initial ~0.5FTE, full time eventually? not yet clear), Henk-Jan (mgmt, hardware purchase)
  - UGent: Kenneth (~0.5FTE initially), Ewald, XXX (open vacancy)
  - UBarcelona: Alan (1 FTE) + extra 24PMs in scientific WPs for post-doc
  - HPCNow!: Elisabeth (technical) [~0.5FTE], Susana (dissemination), + extra hire [1FTE]
  - BSC: Xavier/Roger/Julian (technical) [only meetings in 1st year, 2x0.5FTE from 2nd year]
  - UBergen: Thomas [0.4 FTE], ??? [~ 0.15 FTE]
sync meetings (WP1+WP5)
- probably separate meetings for WP6, less frequent (and fueled by upcoming training events)
- bi-weekly (every other week)?
  - all hands, ~1h
  - maybe later extra meeting when helpdesk rotation switches from one partner to another
- fixed day+time:
  - not Wed/Thu/Fri
  - Tuesdays at 10:00
    - starting on Tue 10 Jan 2023
- fixed person for taking notes (Kenneth?)
  - live during meeting via HackMD, then copy-paste to multixscale GitHub wiki
communication & data sharing
- website
  - multixscale.io ? .eu?
    - Alan has bought multixscale.eu
- email
  - mailing list per MXS WP + a general one?
    - by NIC?
    - by us as stop gap solution?
- Slack
  - #multixscale in EESSI Slack?
  - dedicated MultiXscale Slack, channel per WP?
- MultiXscale GitHub organisation => https://github.com/multixscale
  - public/private repos where needed
  - also serves as bug tracker (via issues), wiki, planning via GitHub project, work-in-progress sandbox, ...
  - who needs access?
  - repo per WP? per WP task?
  - labels for priority, MXS target month ('M6', ...), deliverables
  - GitHub handles: @boegel (Kenneth) @casparvl (Caspar), @epauwels (Ewald), @bedroge (Bob), @xteruel (Xavier), @draentropia (Elisabeth), @satishskamath (Satish), @zilverberg (Henk-Jan), @maxim-masterov (Maxim), @trz42 (Thomas)
- shared drive
  - Google? oneDrive? something provided by NIC?
  - for presentations, spreadsheets, project reports, ...
fixed "MultiXscale" day(s) per week?
- focused time for (only) MXS (no others meetings/tasks that day)
- easy to plan call/PR review with others
list of year one deliverables, milestones (+who leads +who contributes)
- as GitHub issues?
  - labels: lead:UGent, MXS:T5.1, priority:{high,medium,low}, type:{docs,code,...}, contributor labels: SURF, RUG,
  - milestones for deadlines (cfr. https://github.com/easybuilders/easybuild-framework/milestones)
work until kickoff
- (mostly for Thomas)
- bot
- set up repos, populate issues, create project boards + milestones
tasks to start with in Jan'23
- production EESSI repo (incl. test repo?)
- get software in place for scientific side of MXS
feature roadmap
- eessi.io
  - website
  - Stratum-0
- support portal + helpdesk rotation
- contribution policy
  - restrict toolchains
  - different policies for test & prod
- bot
  - build-test-deploy support
- test suite
  - reconsider deployment (currently part of software-layer)
  - test suite as separate python package?

Action points

Kenneth: Send out agenda invite for bi-weekly meeting
Kenneth: set up MultiXscale Slack
Alan: push NIC on picking a date for the kickoff meeting (in February, Caspar can join if it is 6th Feb or later). Push NIC also on setting up a mailing list, ask for mailing list per WP, and one general one. Also ask about shared storage for work on deliverables, etc. (will we have a oneDrive issue? Word template? Latex template? Etc)
Alan: give the key technical people access to github.com/multixscale (see above)
Bob: check if we can get the Stratum 0 hardware a.s.a.p. Both for the project (it's a bit of a blocker) and for the depreciation (if you don't have the bill by 1st of January, you're missing out)