The Pulp development team has a difficult time with a lot of significant decisions due to a lack of basic data. This was discussed some at the Pulpcon 2021. Here is a sampling of the decisions we struggle with:
We launch a lot of our features as “tech preview” to get feedback from users on how it’s going before declaring it stable, thus preventing further changes to it from a semver perspective. Yet we have almost no data on if users are even using these features. Knowing when to declare an API stable is really hard.
Similar to ^, what about the single container or the installer? How broadly are they being? It would be valuable for everyone to know if it’s heavily used or not.
What about dropping EL7 support (eventually, no plans anytime soon)? When we did this for EL6 we basically guessed. If we knew 3% were using EL7 versus 30% we would be able to serve our users much better.
Or what about the database versions, when do we raise the support for the minimum database version? If hypothetically a minimum version raise would affect 23% of the install base, that is key information to know.
We prototype some basic telemetry gathering data in pulpcore. I’d like to form a working group to collaborate on this effort, and use this thread for asynchronous discussion around the effort.
Maintaining the trust of our users is of the utmost importance and should be the prevailing, guiding principle throughout this effort. I hope the working group discusses in detail how this can be done responsibly and with great respect of our users privacy and autonomy. I believe transparency and user choice are good strategies to keep in mind.
Would you like to join the working group?
Would you like to follow along with the group’s discussions and give feedback on the more detailed plan it produces?