HPSF Conference Sketch

[crtrott]

HPSF All-Hands Meeting Template

• 2+3 Days
  • HPSF All-Hands for 2 Days
    • Target audience: project developer teams, participants in working groups,
    • Secondary: may be attractive to the larger HPC (user) community to get a wider overview of HPSF
  • Project Meetings 3 days
    • Target audience: project user community
  • Benefit of co-locating: audience bleed-over and less aggregate org effort
    • For example: more of the projects devs would attend HPSF meeting if the project user-group meeting also happens
    • Users of projects may decide to attend HPSF days to get a better impression of the overall effort
    • Folks from HPSF WGs etc may attend project meetings to get more in-depth information about specific projects
    • Only one overall event is getting organized instead of many
• HPSF All-Hands Day-1
  • HPSF Status Overview (1.5 hours)
    • What: GB and TAC activity update, general status of HPSF, highlight achievements?
    • Goal: give everyone a summary of what the different HPSF bodies have been up to
  • Project Updates (3 hours)
    • What: What’s new, what’s going on
    • Goal: inform devs across projects what other HPSF projects are up to
    • Depending on number of projects may need parallel tracks
  • New and upcoming HPC Systems/Hardware (1.5 hours)
    • What: Reps associated with facilities and vendor reps provide updates on new or upcoming systems and hardware
    • Goal: inform developers about the evolving hardware landscape, what are platforms we may as a community need to invest into in the near future, what hardware opportunities are out there
• HPSF All-Hands Day-2
  • Performance, Usability and Issues on current systems (1.5 hours)
    • What: presentations by projects specific to Performance comparisons of systems Issues with toolchains, porting efforts etc. insights into how hurdles were overcome
    • Goal: Provide a feeling for all developers how things are going, in order to identify common problems, establish a better know-how of expected performance etc., Lessons learned sharing
  • Working Group Breakouts (1.5 hours)
    • What: Face-to-face meeting of WGs - finalize plans for next year, discuss feedback on how the WG has been working out for the last year
    • Goal: bring the WG participants together, help gather feedback, interest new participants from dev community
  • Working Group Breakout reports in plenary (1.5 hours)
    • What: update for everyone what the WGs have been up to and plan to tackle next
    • Goal: raise awareness of WG activities in entire dev community
  • BOF/Panel/Discussion (1.5 hours)
    • What: discuss Health of community, activity plans, enable general Q&A
    • Who: GB/TAC members as panelists
    • Goal: foster discussion and idea exchange by including also a robust Q&A part
• Project Days 3-5
  • Content (and whether they happen) up to individual projects
  • Could include:
    • Update by devs on new features, planned development
    • User community presentation on how the project is leveraged, what is working, what are pain points
    • Tutorials
  • Kokkos Example:
    • We organized a 3.5 day user group meeting with about 1-day worth of developer updates, 2-days of user presentation and 0.5 days of discussion/feedback round
    • Organization was relatively short notice (~2-months from fix date announcement) but still attracted about 60 in-person participants including numerous international travelers
    • User presentations were 20mins but we did not break into multiple tracks: we had about 25-30 teams report on their work not counting the Kokkos team presentations
    • Was extremely useful to get a better feeling for what the community is doing and what their concerns are, helped connect user community, jump started new community efforts

[crtrott]

Possible cities:

• Chicago, Miami, maybe Denver

Time:

• preferred mid May, late June, maybe late September/early October.

[foertter]

Need to come up with a list of expected benefits for developers to attend in person. What will attendees get out of it that couldn't be done say, if they were dialing in? Otherwise we face major competition for travel funding.