an open source user looking to migrate to pants is instead using bazel, and was extremely specific when describing what wasn't quite working for them, and how the pants documentation was lacking. this inspired me to think of: - making a github issue to develop a strategy to improve the first-time experience with pants - sending a link to the github issue to

pants-devel

- iterating on that to produce tickets for a github project. are there any communication channels i'm missing? i'd drop a link in this channel too.

thanks, good ideas. the Toolchain folks would probably like a direct ping too, because i believe they have thoughts in this area

Yep, especially wrt documentation

got it!