Re: [RESULT] Accept ICLA and Software Grant from UMD Into the Apache Flagon Podling
That's great. Thanks Joshua! On Tue, Sep 27, 2022 at 6:02 AM Austin Bennett wrote: > Great, thanks josh! > > On Mon, Sep 26, 2022, 7:23 PM Joshua Poore wrote: > > > Good news! > > > > I think we’re clear on all our actions following the CCLA and SW Grant. > > > > I’ve pushed the SW grant to the Apache Flagon Distill repo ( > > https://github.com/apache/incubator-flagon-distill < > > https://github.com/apache/incubator-flagon-distill>). > > > > I’ve also started on some of our overhead actions (updating copyright, > > headers, etc.) on a dev branch: > > https://github.com/apache/incubator-flagon-distill/tree/license_headers > < > > https://github.com/apache/incubator-flagon-distill/tree/license_headers> > > > > I’ve preserved our legacy code on another branch: > > > https://github.com/apache/incubator-flagon-distill/tree/distill_server_legacy > > < > > > https://github.com/apache/incubator-flagon-distill/tree/distill_server_legacy > > > > > > > best, > > > > Josh > > > > > Begin forwarded message: > > > > > > From: Joshua Poore > > > Subject: [RESULT] Accept ICLA and Software Grant from UMD Into the > > Apache Flagon Podling > > > Date: September 26, 2022 at 10:18:23 PM EDT > > > To: gene...@incubator.apache.org > > > Reply-To: gene...@incubator.apache.org > > > > > > The VOTE is closed. Thanks to all those who VOTE’d! > > > > > > The RESULTS are as follows: > > > > > > [4] +1 (3 IPMC Binding) > > > [0] 0 > > > [0] -1 > > > > > > The consensus VOTE to accept the SW Grant from UMD for the Distill > > refactor has passed. > > > > > > Some additional clarification following from John’s comments: > > > > > > 1. UMD has granted the copyright to ASF (this is explicitly stated in > > our IP disclosure case through UMD Ventures)--those of us that can commit > > on behalf of UMD are changing the copyright statement to appropriately > > reflect ASF. > > > 2. This is a substantial SW gift, but there remains much overhead > before > > an official ASF release—including ensuring appropriate headers are on > every > > source file. > > > 3. .ipynb are json, however, it’s easy enough to include an ASF header > > in a cell at the top of notebook. Notwithstanding, we’ll ask around and > see > > if there is a (better) best practice. > > > > > > Thanks! > > > > > > Josh (on behalf of Flagon PPMC) > > > > > >> On Sep 17, 2022, at 10:11 AM, John D. Ament > > wrote: > > >> > > >> Here's my +1 on the code > > >> > > >> There's a few notes: > > >> - I would recommend the podling add some kind of reference to this > > clause > > >> in their NOTICE file: Copyright 2022 The Applied Research Laboratory > for > > >> Intelligence and Security (ARLIS) (see [1]) > > >> - There's many files missing any headers. I think it's safe to assume > > they > > >> follow the same license since there is a LICENSE file at the root. I > > >> couldn't find any evidence that the files missing headers were > > copy/pasted > > >> from other repositories. > > >> - For files like the .ipynb files, I don't think there's a way to > > >> explicitly add a license header (since they're JSON files). You may > > want > > >> to consult with legal on how to add license file references for them. > > >> > > >> > > >> [1]: > > >> > > > https://github.com/UMD-ARLIS/incubator-flagon-distill/blob/distill_toolkit_refactor/NOTICE > > >> > > >> > > >> On Fri, Sep 16, 2022 at 11:12 AM John D. Ament > > > >> wrote: > > >> > > >>> Hey Josh, > > >>> > > >>> Thanks for the clarification, I found the thread from Craig. For > > future > > >>> reference, you shouldn't be voting on accepting a CCLA and/or SGA. > > >>> Procedure wise, this doesn't make sense. You're voting on accepting > a > > code > > >>> donation, and it's just that code donations from the foundation's > > >>> standpoint require a SGA. The vote to accept the donation happens on > > the > > >>> podling's private list. I think we're in alignment up to that point > > (other > > >>> than the fact that the vote on the private lis
Re: [RESULT] Accept ICLA and Software Grant from UMD Into the Apache Flagon Podling
Great, thanks josh! On Mon, Sep 26, 2022, 7:23 PM Joshua Poore wrote: > Good news! > > I think we’re clear on all our actions following the CCLA and SW Grant. > > I’ve pushed the SW grant to the Apache Flagon Distill repo ( > https://github.com/apache/incubator-flagon-distill < > https://github.com/apache/incubator-flagon-distill>). > > I’ve also started on some of our overhead actions (updating copyright, > headers, etc.) on a dev branch: > https://github.com/apache/incubator-flagon-distill/tree/license_headers < > https://github.com/apache/incubator-flagon-distill/tree/license_headers> > > I’ve preserved our legacy code on another branch: > https://github.com/apache/incubator-flagon-distill/tree/distill_server_legacy > < > https://github.com/apache/incubator-flagon-distill/tree/distill_server_legacy > > > > best, > > Josh > > > Begin forwarded message: > > > > From: Joshua Poore > > Subject: [RESULT] Accept ICLA and Software Grant from UMD Into the > Apache Flagon Podling > > Date: September 26, 2022 at 10:18:23 PM EDT > > To: gene...@incubator.apache.org > > Reply-To: gene...@incubator.apache.org > > > > The VOTE is closed. Thanks to all those who VOTE’d! > > > > The RESULTS are as follows: > > > > [4] +1 (3 IPMC Binding) > > [0] 0 > > [0] -1 > > > > The consensus VOTE to accept the SW Grant from UMD for the Distill > refactor has passed. > > > > Some additional clarification following from John’s comments: > > > > 1. UMD has granted the copyright to ASF (this is explicitly stated in > our IP disclosure case through UMD Ventures)--those of us that can commit > on behalf of UMD are changing the copyright statement to appropriately > reflect ASF. > > 2. This is a substantial SW gift, but there remains much overhead before > an official ASF release—including ensuring appropriate headers are on every > source file. > > 3. .ipynb are json, however, it’s easy enough to include an ASF header > in a cell at the top of notebook. Notwithstanding, we’ll ask around and see > if there is a (better) best practice. > > > > Thanks! > > > > Josh (on behalf of Flagon PPMC) > > > >> On Sep 17, 2022, at 10:11 AM, John D. Ament > wrote: > >> > >> Here's my +1 on the code > >> > >> There's a few notes: > >> - I would recommend the podling add some kind of reference to this > clause > >> in their NOTICE file: Copyright 2022 The Applied Research Laboratory for > >> Intelligence and Security (ARLIS) (see [1]) > >> - There's many files missing any headers. I think it's safe to assume > they > >> follow the same license since there is a LICENSE file at the root. I > >> couldn't find any evidence that the files missing headers were > copy/pasted > >> from other repositories. > >> - For files like the .ipynb files, I don't think there's a way to > >> explicitly add a license header (since they're JSON files). You may > want > >> to consult with legal on how to add license file references for them. > >> > >> > >> [1]: > >> > https://github.com/UMD-ARLIS/incubator-flagon-distill/blob/distill_toolkit_refactor/NOTICE > >> > >> > >> On Fri, Sep 16, 2022 at 11:12 AM John D. Ament > >> wrote: > >> > >>> Hey Josh, > >>> > >>> Thanks for the clarification, I found the thread from Craig. For > future > >>> reference, you shouldn't be voting on accepting a CCLA and/or SGA. > >>> Procedure wise, this doesn't make sense. You're voting on accepting a > code > >>> donation, and it's just that code donations from the foundation's > >>> standpoint require a SGA. The vote to accept the donation happens on > the > >>> podling's private list. I think we're in alignment up to that point > (other > >>> than the fact that the vote on the private list looks a bit off). > >>> > >>> To be 100% clear on the scope, you're looking for a third vote to view > the > >>> repo at [1] and confirm whether or not the content within is compliant > to > >>> be imported into a repository hosted by the ASF? Where I'm concerned > with > >>> the original vote, you're including in scope adding 5 new committers > (which > >>> aren't named in the vote thread) to the project. It's not apparent > that > >>> both are in scope, the vote to add committers should be separate from > the > >>> vote to add code to the repos
Fwd: [RESULT] Accept ICLA and Software Grant from UMD Into the Apache Flagon Podling
Good news! I think we’re clear on all our actions following the CCLA and SW Grant. I’ve pushed the SW grant to the Apache Flagon Distill repo (https://github.com/apache/incubator-flagon-distill <https://github.com/apache/incubator-flagon-distill>). I’ve also started on some of our overhead actions (updating copyright, headers, etc.) on a dev branch: https://github.com/apache/incubator-flagon-distill/tree/license_headers <https://github.com/apache/incubator-flagon-distill/tree/license_headers> I’ve preserved our legacy code on another branch: https://github.com/apache/incubator-flagon-distill/tree/distill_server_legacy <https://github.com/apache/incubator-flagon-distill/tree/distill_server_legacy> best, Josh > Begin forwarded message: > > From: Joshua Poore > Subject: [RESULT] Accept ICLA and Software Grant from UMD Into the Apache > Flagon Podling > Date: September 26, 2022 at 10:18:23 PM EDT > To: gene...@incubator.apache.org > Reply-To: gene...@incubator.apache.org > > The VOTE is closed. Thanks to all those who VOTE’d! > > The RESULTS are as follows: > > [4] +1 (3 IPMC Binding) > [0] 0 > [0] -1 > > The consensus VOTE to accept the SW Grant from UMD for the Distill refactor > has passed. > > Some additional clarification following from John’s comments: > > 1. UMD has granted the copyright to ASF (this is explicitly stated in our IP > disclosure case through UMD Ventures)--those of us that can commit on behalf > of UMD are changing the copyright statement to appropriately reflect ASF. > 2. This is a substantial SW gift, but there remains much overhead before an > official ASF release—including ensuring appropriate headers are on every > source file. > 3. .ipynb are json, however, it’s easy enough to include an ASF header in a > cell at the top of notebook. Notwithstanding, we’ll ask around and see if > there is a (better) best practice. > > Thanks! > > Josh (on behalf of Flagon PPMC) > >> On Sep 17, 2022, at 10:11 AM, John D. Ament wrote: >> >> Here's my +1 on the code >> >> There's a few notes: >> - I would recommend the podling add some kind of reference to this clause >> in their NOTICE file: Copyright 2022 The Applied Research Laboratory for >> Intelligence and Security (ARLIS) (see [1]) >> - There's many files missing any headers. I think it's safe to assume they >> follow the same license since there is a LICENSE file at the root. I >> couldn't find any evidence that the files missing headers were copy/pasted >> from other repositories. >> - For files like the .ipynb files, I don't think there's a way to >> explicitly add a license header (since they're JSON files). You may want >> to consult with legal on how to add license file references for them. >> >> >> [1]: >> https://github.com/UMD-ARLIS/incubator-flagon-distill/blob/distill_toolkit_refactor/NOTICE >> >> >> On Fri, Sep 16, 2022 at 11:12 AM John D. Ament >> wrote: >> >>> Hey Josh, >>> >>> Thanks for the clarification, I found the thread from Craig. For future >>> reference, you shouldn't be voting on accepting a CCLA and/or SGA. >>> Procedure wise, this doesn't make sense. You're voting on accepting a code >>> donation, and it's just that code donations from the foundation's >>> standpoint require a SGA. The vote to accept the donation happens on the >>> podling's private list. I think we're in alignment up to that point (other >>> than the fact that the vote on the private list looks a bit off). >>> >>> To be 100% clear on the scope, you're looking for a third vote to view the >>> repo at [1] and confirm whether or not the content within is compliant to >>> be imported into a repository hosted by the ASF? Where I'm concerned with >>> the original vote, you're including in scope adding 5 new committers (which >>> aren't named in the vote thread) to the project. It's not apparent that >>> both are in scope, the vote to add committers should be separate from the >>> vote to add code to the repository (usually you would import the code >>> first, then vote to add the committers to the project). Do keep in mind >>> since these are your coworkers you're not building a diverse community of >>> committers. >>> >>> I'm including a few links to show a bit better how TLPs have handled this >>> before to give a little better picture. I'll take a deeper look in the >>> repo I linked in a bit, but I'm not seeing any major issues with the code. >>> >>> - John >>> >>> [1]: >>
