Coordinator: Fed (Rachel joined late)

Meeting began with roundtable introductions

Markus took notes of the meeting

Goals:

• [ ] Define a charter - the scope of the task force
• [ ] Timeline for these items - gantt chart -> volunteers? The timeline will be public on the TVS page
• Suggesting software for TVS and outlining a mechanism for members to propose, review currently available software
• Design benchmarks to be compliant with the in-kind call
• Review TVS Science Roadmap to identify needed software packages
• Specifying software projects
• Selecting software to be developed by intern'l contributors
• Distribute the call to volunteers and in-kind contributors, e.g. by asking for a short presentation
• Figure out a validation scheme fulfilling the objective and serving the community (also for meeting the criteria to be a valid in-kind contribution)
• Take notes on the notion task management software, continue to invite people
• Lower the barrier to entry for use of the software by TVS members
• What kind of software?: Define which software development tasks are necessary (and therefore high priority) and which are "nice-to-have" (which can be developed more gradually).
• What languages?: Software will be developed by multiple teams. We have to keep track in what languages (e.g. Python, C++ etc) and how the different parts will interface (if that is required) with one another. What about documentation requirements? We need to develop a process to select a few testers and reviewers. The guiding development principle, as discussed yesterday, should be ease of use “Everything should be made as simple as possible, but no simpler.”
• Where will it be hosted? For software services (i.e. not specific packages, e.g. fitting code or pipelines, that can be placed on github), we need to define where these will be hosted and develop appropriate APIs.
• What kind of software exists? Beneficial to get an overview - Teams have proposed contributions, present to the whole collaboration and ask to contribute