Has the topic deviated enough to warrant a different thread? For ease of discussion, and future searches on-list?
[ ex: licenses, future versions, importing code, etc ] On Sun, Aug 10, 2025, 05:04 Henrik Ingo <hen...@nyrkio.com> wrote: > On Sat, Aug 9, 2025 at 11:03 PM Dave Fisher <w...@apache.org> wrote: > > > Sorry for the delayed reply. > > > > > No rush, I think this is within the pace all of us work on Otava :-) > > > > > >> 2b. What is the IP provenance of this signal processing code? Who > holds > > >> the copyright? > > >> > > > > > > This was written 100% by MongoDB employees and published with the > > > appropriate approval processes. For the version we use most of the code > > was > > > written by William Brown and Jim O'Leary. Later code I was no longer > > there, > > > but I believe was written by David Bradford and Alexander Costas. > (David > > > Daly will now better, and we're still hoping the current author would > > > actually show up here...) > > > > Then as far as copyright is concerned this code is © MongoDB. To be added > > directly to Otava then an SGA from MongoDB is likely to be required. [1] > > > > [1] https://www.apache.org/licenses/contributor-agreements.html#grants > > > > > I had previously read this: https://www.apache.org/legal/resolved.html > > ...based on which I have assumed that since the code we are talking about > clearly falls within category A, we would be able to bring it into the > project, with at most a very routine and light weight clearance process. > Now when I follow the link you provide above, as well as > https://incubator.apache.org/ip-clearance/index.html ...I only observe a > process where the 3rd party formally transfers code to the ASF. (In which > case it doesn't really matter how the code was originally licensed.) > > For the purpose of this discussion, I was interested in exploring the path > where there's some code on the internet that is Apache licensed, and the IP > provenance is easy to confirm, so one would think we can easily copy parts > of such code into an ASF project that of course also is Apache 2.0 > licensed. The copyright of course would continue to belong to the original > author of the code. (MongoDB) > > I get the impression this isn't actually done a lot in ASF projects? > > To be clear, I'm not against having this discussion on the private list and > approaching MongoDB for a more serious discussion about this. I'm just > wondering since being able to copy code between projects is one of the > greatest benefits of working with OSS licensed code, it's kind of ironic if > that way of working isn't available to ASF itself. > > Also, I agree that the amount of code we're talking about isn't > non-trivial, so this discussion at least, if not the ensuing paper work, is > entirely justified. > > > > > The IP Clearance process while done in the Incubator is for PMCs and not > > podlings. > > > > > Sorry, can you clarify this sentence? > > > > >> 2c. How large is this codebase? > > >> > > >> > > > > > > The initial dump seems to be 2600 lines. The commit history after that > is > > > relatively short, and in any case we don't currently use the newer > > features. > > > > That’s substantial enough so that an SGA is preferred to a fork. Any > > details about negotiating this process should proceed on the private > list. > > > > > It's a relatively small project, doing a single thing. A lot of the code is > duplicated, where the same 100+ lines of code is implented 5 different ways > in order to explore performance differences. But as said, I agree it isn't > insignificant. > > Let’s review those comms on the private list. > > > Essentially we can start from a clean slate there. > > henrik > > -- > *nyrkio.com <http://nyrkio.com/>* ~ *git blame for performance* > > Henrik Ingo, CEO > hen...@nyrkio.com LinkedIn: > www.linkedin.com/in/heingo > +358 40 569 7354 Twitter: > twitter.com/h_ingo >
