Since it seems I wasn't clear, let me try again: Jira is where we manage needs and ideas to be worked on. There may be discussion there of that particular idea, but try to keep it focused, and if a discussion becomes extended bring it back here to the dev list.
Git is where we manage the codebase. Focused discussion of a pull request may occur there as part of review, but keep it focused on the questions I pointed out: is there an actual problem with this proposal that can not deferred to a subsequent PR, and is the proposal an improvement over what we have. If an exchange goes on for more than a few comments, it is probably drifting away from that focus and should be taken offline or brought here, or perhaps or be addressed with another PR proposing a specific change, or a Jira item asking that someone investigate that change. If it isn't about a specific idea or change set, and only about that, it belongs here. Other Apache projects may be less strict about this. But at least three of the five people most active here, including myself, tend to talk things into the ground. We don't have enough resources to let "it could also be done this way" tie us up. Moving discussion that isn't directly about clarifying and prioritizing a jira item, or a _blocking_ issue in a PR, here will keep digressions from distracting us from actually completing tasks. -- /_ Joe Kesselman (he/him/his) -/ _) My Alexa skill for New Music/New Sounds fans: / https://www.amazon.com/dp/B09WJ3H657/ Caveat: Opinionated old geezer with overcompensated writer's block. May be redundant, verbose, prolix, sesquipedalian, didactic, officious, or redundant. ________________________________
