Cons of the current spec: It combines three programming languages: YAML, Jinja and the custom selector syntax Jinja and selectors makes it hard to parse using standard YAML parsers from Python Parsing is a multi-stage process in Python that iterates until all values are filled Version numbers are interpreted as floating point values ("0.14") in YAML more ideas (convo w/ MB) test matrix for noarch for different platforms / versions keep all steps independent

Agenda: Link to the previous brainstorming notes: https://docs.google.com/document/d/1t5KA93w33-ic_gOaGsrDhvm1sPwOjQgeqlEP2CUkg70/edit?usp=sharing Name?! Emoji-domains open 📦con.io :) boxcon.dev is availble box-con.org as well Other names: packageCon, PkgCon...

11 May 2021 Agenda RoboStack paper (https://arxiv.org/abs/2104.12910) rosdep working cross-platform CI (example for MoveIt Core: https://github.com/ros-planning/moveit/pull/2604)

Here is a list of CFEP Proposals that I wanted to note down. I am happy about any kind of suggestion -- maybe some of these things aren't CFEP worthy? Formalize conda-forge build scripts The conda-build mechanism with build.sh and bld.bat is obviously very powerful, and flexible. But with flexibility comes also a price -- it's harder to be correct and follow good practices. This CFEP suggests to implement and maintain a collection of build scripts for common build tools. For example for CMake. Instead of creating or copy pasting a CMake build.sh file, it would be possible to depend on the cf-buildscripts package in the build environment and run script: cf-cmake -DMY_VAR=ON This would allow us to set common configuration settings from the cf-buildscripts package.