We can publish binary packages that include LGPL components, as long as we communicate this very precisely.
We can't include LGPL in a source release, but we might be able to host a Git repository on ASF infra that includes LGPL source. As long as we do not make any source releases from it. But I am not sure on this point. A quick note to legal-discuss@ would clear this up. If it's not a good idea, then yes, a Github repository would work. On 22 November 2013 11:52, Kasper Sørensen <[email protected]> wrote: > Hi all, > > At Human Inference (and in the old eobjects.org community of MetaModel) we > have a number of small projects/modules that provide the capability of > Apache MetaModel to connect to these additional datastore types: > > * SAS datasets (.sas7bdat files) > * dBase databases (.dbf files) > * MS Access databases > > For various reasons, these modules could not be Apache licensed, so they > have to live on somewhere else with the LGPL license. Right now they're > individually available at different SVN locations etc. etc... I would like > to see if we can clean that up a bit and make a package available with a > name like "MetaModel extras". > > Obviously without any commitment from the Apache community, I wanted to ask > if anyone had any preference as to where and how we publish these modules. > I am thinking we might do something like putting them on GitHub, and for > now still use package name and Maven group id like "org.eobjects....". > > Kind regards, > Kasper -- Noah Slater https://twitter.com/nslater
