vlsi commented on PR #108: URL: https://github.com/apache/xalan-java/pull/108#issuecomment-1774900516
> we need to use few of the Eclipse WTP XPath 2.0 processor's code algorithm patterns, to make progress on XalanJ's XSLT 3.0 and XPath 3.1 implementation development See https://www.apache.org/legal/release-policy.html#licensing > Every ASF release MUST comply with ASF licensing policy. This requirement is of utmost importance and an audit SHOULD be performed before any full release is created Of course, no release with xslt3 has been made yet, however, once you spoil the codebase with bad-licensed code, it will be hard to reverse it. > we're not using exact copies of the code files, but we're using few algorithm outlines I would suggest asking for a lawyer, however, borrowing "only algorithms" does not sound much different from "borrowing exact code". For instance, if you analyze code written in C, and "reproduce it in Java in Xalan", you still borrow from a project, and it does not count that you "use a completely different language". Of course, it is up to PMC to decide what they think is shippable, however, this case sounds fishy to me. The branch does contain code with a doubtful license. It means the code will be hard to release, and delaying such an analysis till the release would make it even harder. --- > IHMO, I'm a XalanJ committer and I may commit code and merge that myself however quickly Mukul, I beg your pardon, but it does not clarify the reason **why** you keep creating the PRs. Of course, you can create branches, commits, and PRs. Why do you keep creating PRs for xslt3 though? > Any other XalanJ committer or a pmc member, can raise any concerns and objections to the PRs and the git merges that I'm doing on these PRs, and then I shall be bound to accept those points Correct me if I am wrong: does that mean you consider concerns from other committers and PMC only? -- 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: dev-unsubscr...@xalan.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@xalan.apache.org For additional commands, e-mail: dev-h...@xalan.apache.org
