5 ms·

...They wanted me to sign up to a jira instance that wasn't publicly available to create an issue so that I could create a github pull request or some such. Rea

...They wanted me to sign up to a jira instance that wasn't publicly available to create an issue so that I could create a github pull request or some such. Real byzantine. Couldn't even find any contact information to the developers To me, all this seems like a reasonable filter. Not much of a barrier when if contributing to this particular code base was of high personal importance. I mean, if that's the way the team works. That's the way it works and if it isn't the way a particular person wants to work then perhaps they are not a good fit with the team. [This is not intended as snark] If the project is important to you and the team doesn't work in a way that works for you, set up your own fork. Yes it's a lot of work that will beget more work. But that's what important things usually entail. Once you have your fork, you can set your own bar for contributions and other project policies.

marginalia_nu 4y ago
Well I mean I started out essentially with my own fork, that has modifications that make sense to me. In doing so, I found a trivial optimization that it would be neat if it was backported. Although this would benefit everyone using the mainline project, this is of very low personal importance to me and my patience for navigating an obstacle course is fairly low, even if this is to the detriment of the wider developer community.
- brudgers 4y ago
  The goal of the filter is probably to pass people for whom benefiting everyone who uses the project is important because in the long run that's more valuable to the team and more sustainable for the project.
  - funcDropShadow 4y ago
    I agree with you in general. But in this specific case, a walk by merge request should be acceptable. To anyone who is familiar with Java enought to be able to work on performance sensitive code, the described change is a no brainer. It doesn't need to be documented, it doesn't need to be discussed, I am pretty sure Intellij IDEA would highlight it as proposed change for performance reasons.

marginalia_nu 4y ago

Well I mean I started out essentially with my own fork, that has modifications that make sense to me. In doing so, I found a trivial optimization that it would be neat if it was backported. Although this would benefit everyone using the mainline project, this is of very low personal importance to me and my patience for navigating an obstacle course is fairly low, even if this is to the detriment of the wider developer community.

brudgers 4y ago
The goal of the filter is probably to pass people for whom benefiting everyone who uses the project is important because in the long run that's more valuable to the team and more sustainable for the project.
- funcDropShadow 4y ago
  I agree with you in general. But in this specific case, a walk by merge request should be acceptable. To anyone who is familiar with Java enought to be able to work on performance sensitive code, the described change is a no brainer. It doesn't need to be documented, it doesn't need to be discussed, I am pretty sure Intellij IDEA would highlight it as proposed change for performance reasons.