Hello, @quick-holiday-44874 @alert-architect-36218 @polite-winter-30234 @curved-computer-88379 @bumpy-spring-43024 @eager-waitress-57583 @cuddly-rain-33371 @clean-alligator-41449 @billowy-artist-40838 @cold-engineer-60067 @jolly-noon-50330! A warm welcome to Pantsbuild. We hope you feel right at home here. Would you mind telling us a little about yourself, your organization, how you came across Pantsbuild, and which features you're most interested in exploring? Feel free to ask any questions too—we're a friendly bunch!

Hey, cool! I’m a data scientist at decentral games and came across pants because I was exploring monorepos. I compared some monorepos at a high level, and since most data scientists work in python I decided to go with pants because it seemed python friendly. I have never used a monorepo tool before, but I was exploring them in the first place because I find it inefficient and error prone to manage multiple versions of the same (or similar) code across repos 🙃. I’ve been occasionally reading through the docs. Pretty interesting stuff!

Hi! Thanks @bitter-ability-32190 for the warm welcome. I'm a Principal Engineer at Onna. We are a Python shop, and in the connectors area, we are considering the possibility of moving to a monorepo. Currently, each connector resides in its own repository, and managing that and all the shared dependencies is a bit time-consuming. We have explored other options like writing our own makefiles or solutions like Bazel, but the former is complex to maintain, and the latter is too enterprise for our taste. We are assessing Pants now, with the main key points being a seamless experience on both local machines and the CI pipeline, automatic dependency graph resolution (so targets can be applied only to what has changed and its dependents), caching to speed up execution, and simplicity (we cannot afford to learn a large enterprise solution). The availability of targets for Docker and Helm is a plus, as those are the artifacts that we produce. At the moment, we are working on a small PoC to validate all these points and evaluate the integration with our CI and deployment system.

To both of y'all, let us know how we can help 🙂. We love feedback of all shapes and sizes