I think you can freely repackage and republish under your own artifact/groupid. Nobody will object -- ASL gives you the right to do so. And if you include an information about the rationale of the fork (the kind you've just provided) the situation seems very clear to me.
Dawid On Thu, Jul 11, 2013 at 5:51 PM, Alan Woodward <[email protected]> wrote: > Hi all, > > We're looking to release as open source some code that we've written that > makes extensive use of LUCENE-2878, a branch which allows Scorers access to > positional information for highlighting. At some point it would be nice to > land this branch on trunk, eventually to get it into a release, but that's > not going to happen any time soon. So I'd like to get some idea of the > legal issues/etiquette around releasing our own fork. > > Ideally we'd release our project using maven, with a dependency on our fork > hosted either in a Flax repository, or in something like sonatype. > Releasing it under the group "org.apache.lucene" seems wrong, though, as > that implies (to me at least) that this is something supported and/or > endorsed by Apache, which isn't true (yet!). But releasing it under our own > group also doesn't seem right, as the vast, vast majority of code wasn't > written by us. Does anyone on the list have an opinion as to what the Done > Thing is here, or know if there are legal concerns? > > Thanks! > > Alan Woodward > www.flax.co.uk > > --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
