Training Planning Meeting

Monday 4 May 2020, 15:30 → 17:00 Europe/Zurich

200504_hsf.pdf

Live notes

Meeting 2020-05-04

Present: Adam Parker, Dan Katz, Graeme Stewart, Kevin Nelson, Kilian Lieret, Samuel Meehan, Sudhir Malik

Virtual training

• All roles have volunteers

• Accessibility: In particular will have closed captions for videos. Might hire a captioning service (~1$/minute, will probably total at around 500$)

• Date: june 2, 4, ...

Future virtual trainings

• Situation won’t change so quickly and there are other reasons for having virtual trainings in the long term

• How do the Carpentries deal with this? Will need them to help with training. → Talk to them

Jupyter notebooks for training sessions

• Jupyter notebooks can be included nicely in an existing sphinx setup to build webpages and integrate with other parts of documentation

• Discussion about suitability of Jupyter notebooks for training sessions

• Good resource pedagogical POV: http://teachtogether.tech/ 

Sustainability

Can be summarized as

    developing and maintaining software that continues to meet its purpose over time

which can be done by:

1. reducing the amount of work needed to sustain the software

2. increasing the available resources to sustain the software

3. items that do both 1 and 2

 

Under 1 is:

• 1a - developing training

• 1b - disseminating training (aka training people)

• 1c - developing best practices

• 1d - disseminating best practices

 

Under 2 is:

• 2a - Creating incentives so that people want to work on the software, e.g.

• 2a1 - getting citations that help in existing career paths,

• 2a2 - adjusting existing career paths to ensure that they reward software work,

• 2a3 - creating new career paths

• 2b - Increasing funding by

• 2b1 - making the role of software in research clear to those who make decisions about funding allocations

• 2b2 - making clear the case for them to increase funding for new software, and to provide funding for software maintenance

 

Under 3 is:

• 3a - using or adapting software that is developed and maintained by others, by being aware of software outside the HEP community, then determining what can be of use, and using it.

• 3b - creating software that is of use outside HEP and that others will want to help develop for their own use, by being aware of needs out the HEP community, explaining software in a non-HEP-specific way, and starting collaborations

 

We are already doing a good job with 1a and 1b. IRIS-HEP is also doing some work in 3a, and maybe a little in 3b.

What do you think we should focus on at this point?

15:30 → 16:00 Discussion