Hi, > This isn't true for many licensing issues. The answer > isn't always clear
But there’s usually an option to make it just a documentation issue rather than a possible licensed error. When in doubt that should be the path we take that was it doesn’t hold up the release. > and often the message feels more like Justin is telling someone else to do > the work instead proposing "hey, I think we > should apply this patch to this file”. How much work is it (for instance) to add a header or add something to LICENSE? > For all of these recent issues agh we did not resolve, > pushing their resolution off to the next release will not harm the ASF's > reputation but has a good chance of helping build the community. At least one issue here has been unresolved for 2 releases, marking it as “fix later” sometime means it doesn’t get fixed. Thanks, Justin
