Well, we discussed this in length last week, and as a matter of fact the OSGi API which is under development is not available publically. So how can we define a policy that is practically impossible?
This goes back to what I said several times last week, we can only change our side (Apache) but we can't change the OSGi Alliance side. I think having a separate commit for the API and mentioning some reference like the commit id or similar is a good idea. However, only developers working for a member company of the OSGi Alliance can verify this. But in practice, we have a lot of committers here being able to do so, including Guillaume. Carsten Guillaume Nodet wrote > As discussed on legal@ (see [1]), and in order to be able to track code IP > correctly, I propose that all commits that includes API code from the OSGi > Alliance are done in separate commit and include a reference to the public > source where the code comes from. > > Thoughts ? > Guillaume > > [1] > http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201701.mbox/%3ccaa66tppc9lp71ak4uoxsnz8qzg+bnutyntzspbt+z48dynu...@mail.gmail.com%3e > -- Carsten Ziegeler Adobe Research Switzerland cziege...@apache.org
