<style> .reveal section p { font-size: 0.6em; line-height: 1.2em; vertical-align: top; } li { font-size: 0.6em; line-height: 1.2em; vertical-align: top; } .reveal section img { background:none; border:none; box-shadow:none; } </style> # OpenFOAM RSE group proposal _Gerasimos Chourdakis (TUM)_, Tomislav Maric (TUDa), and more --- ## Main goal Bring together the developers community of OpenFOAM --- ## Additional goals 1. Disseminate good development practices in the community. 2. Learn, try, and demonstrate new workflows for developing code. 3. Long-term: Add the tooling that downstream developers need. 4. Long-term: Scale up OpenFOAM development (and testing) workflows. 5. Long-term: Increase trust in the community and open up. --- ## Example topics - Continuous Integration / automated testing - Data repositories for reusable (and continuous) benchmarking - Managing community contributions - Effective documentation - Build systems - Development and debugging techniques/tools --- ## Why call it "RSE"? _"Research software engineering is the use of software engineering practices in research applications."_ International community (see society-rse.org), also industry efforts. --- ## Why is this different from HPC? _"HPC Technical Committee' commitment is to work together with the community to overcome the actual HPC bottlenecks of OpenFOAM"_ Code recommendations is an outcome, but with different focus/goals. --- ## Why now? - Two improvised sessions in OFW17 (Cambridge) - Consistent follow-up interest - Enough time to try it till the OFW18 --- ## Context Working for precice.org (coupling library) Bridging and learning from other related community projects: deal.II, FEniCS, SU2, Nutils, CalculiX, ... --- ## Format Monthly (invited) talks + panels Community space Documentation --- ## Needs 1. Some Governance umbrella (wiki page) 2. Open channels with core developers 3. Space for documentation 4. Communication platform