sbp commented on issue #311: URL: https://github.com/apache/tooling-trusted-releases/issues/311#issuecomment-3533562864
We should certainly document this more, but I don't think we can add a default because some projects use `-source` or `-src` and have the rest be binary by default, and some do the opposite, using `-binary` or `-bin` and then having the rest be source by default. You might think "ah, there are only two options, so maybe have a button to choose between the two", but there are also lots of other conventions, and these are quite common. We analysed all ASF projects to come to this conclusion. That's how we created this heuristic path matcher: https://github.com/apache/tooling-trusted-releases/blob/main/atr/analysis.py One thing we discussed for ATR was just having a set convention and then projects have to use it. For example, we could mandate the `-src` pattern, and be done with it. The problem here is that it raises the barrier for using ATR, and we very much want to avoid that. We _could_ perhaps set a default convention and then that gives a mild carrot (if there is such a thing) for migrating to that convention. We'd have to see what the majority convention actually is; I don't recall it from the analysis results. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
