On Mon, Oct 9, 2017 at 5:24 PM, Neil Bartlett (Paremus) <neil.bartl...@paremus.com> wrote: > >> On 9 Oct 2017, at 16:20, Karl Pauls <karlpa...@gmail.com> wrote: >> >> On Mon, Oct 9, 2017 at 5:12 PM, Jan Willem Janssen >> <janwillem.jans...@luminis.eu <mailto:janwillem.jans...@luminis.eu>> wrote: >>> Hi, >>> >>>> On 9 Oct 2017, at 14:00, Neil Bartlett (Paremus) >>>> <neil.bartl...@paremus.com> wrote: >>>> >>>> Hello Jan, >>>> >>>>> On 9 Oct 2017, at 09:56, Jan Willem Janssen >>>>> <janwillem.jans...@luminis.eu> wrote: >>>>> >>>>>> >>>>>> On 7 Oct 2017, at 18:30, Neil Bartlett (Paremus) >>>>>> <neil.bartl...@paremus.com> wrote: >>>>>> >>>>>> Hello Felix developers, >>>>>> >>>>>> I would like to initiate a contribution of external code into Apache >>>>>> Felix. This code is being contributed on behalf of Intel Corporation, >>>>>> who funded development. The contribution is a plugin for File Install — >>>>>> an implementation of the ArtifactInstaller service — which handles >>>>>> Bundle ARchive (BAR) files. This is a proposed format for an aggregate >>>>>> of functionality represented as one or more OSGi bundles along with an >>>>>> OSGi index. It includes use of the OSGi resolver API to check >>>>>> consistency and permits overlapping resources from multiple installable >>>>>> units. >>>>>> […snip…] >>>>>> All sources are already Apache licensed, and were originally developed >>>>>> for the Open Security Controller project >>>>>> (https://www.opensecuritycontroller.org/ >>>>>> <https://www.opensecuritycontroller.org/>). >>>>> >>>>> Nice work! I’ve glanced through the code and was wondering whether it is >>>>> an idea to separate the file-install specifics from the more generic >>>>> resolver/management parts. It would allow BARs to be installed by using >>>>> different means (for example, a custom management agent) than >>>>> file install. >>>> >>>> Yes that would be a relatively simple refactoring. I suggest looking at >>>> this kind of change after the initial contribution is in the Apache >>>> incubator. >>> >>> Sure, no problem. Happy to accept this contribution... >> >> +1 >> >>> I do see a copyright notice from Intel in the source files. Do we need an >>> CCLA for this contribution? >> >> We will need to get this through the incubator as this is a code >> contribution. It needs to follow the process outlined at >> http://incubator.apache.org/ip-clearance/ >> <http://incubator.apache.org/ip-clearance/> . >> >> I think we should give this thread a little more time but if nobody >> raises any objections I'll call a vote on the acceptance of the >> contribution in a day or so. Assuming the vote passes I volunteer to >> drive the ip-clearance and follow-up with the incubator. > > Many thanks Karl!
As a precursor to that, could you provide a link to the complete contribution (zip, github repo, pull-request) containing the complete contribution (you did a pull-request initially - is that the complete contribution)? Furthermore, please identify the copyright situation (i.e., what contributors exist and what is there status wrt. (c)cla etc.). regards, Karl > Regards, > Neil > >> >> regards, >> >> Karl >> >>> -- >>> Met vriendelijke groeten | Kind regards >>> >>> Jan Willem Janssen | Software Architect >>> +31 631 765 814 >>> >>> >>> My world is something with Amdatu and Apache >>> >>> Luminis Technologies >>> John F. Kennedylaan 32 >>> 7314 PS Apeldoorn >>> +31 88 586 46 25 >>> >>> https://www.luminis.eu >>> >>> KvK (CoC) 09 16 28 93 >>> BTW (VAT) NL8170.94.441.B.01 >>> >> >> >> >> -- >> Karl Pauls >> karlpa...@gmail.com <mailto:karlpa...@gmail.com> -- Karl Pauls karlpa...@gmail.com
