Hi John, Thanks for your response.
I had a long thread with Calvin, Justin, and Craig Russell to clarify the process of onboarding new SW grants into existing podlings RE CCLA. The thread is on private@incubator, which I'm unable to grab a permalink for through lists... Bottom line up front: Suggestion was that formal votes through the incubator were not necessary in this case, but discussion and a vote on general level was encouraged to document consensus. Trying to adhere to good practice, but at this point a "consensus vote" on general is perfunctory. Respectfully, Josh (Flagon PPMC) On 2022/08/30 11:05:03 "John D. Ament" wrote: > Note that you're using public and private lists which is a big no-no. > > I'll be honest I don't understand what you're trying to get the IPMC to > vote on. You may need some help from mentors. I saw IP clearance and will > point out that [1] isn't for podlings. Likewise if this CCLA is new after > your proposal then likely [2] needs to be updated instead. After which your > mentors should be verifying the distribution rights. > > > [1]: https://incubator.apache.org/ip-clearance/index.html > [2]: https://incubator.apache.org/projects/flagon.html > > On Mon, Aug 29, 2022, 21:06 Joshua Poore <poor...@apache.org> wrote: > > > Hello General! > > > > Refreshing this 72 VOTE: > > > > I am looking for additional review and binding VOTEs from the Incubator > > regarding a recent SW grant (via CCLA) from UMD to the Flagon Podling. The > > Flagon community has VOTED to accept for reasons outlined below and > > Secretary has accepted the CCLA. We are seeking concurrence from the > > incubator. > > > > Details follow: > > > > > On Aug 19, 2022, at 9:32 PM, Joshua Poore <poor...@apache.org> wrote: > > > > > > Hello Incubator! > > > > > > I am continuing a 72 VOTE from the Flagon Community on Incubator General > > regarding the acceptance of an ICLA and Software Grant into the Apache > > Flagon (Incubating) Podling. > > > > > > The purpose of this VOTE is to establish consensus and transparency wrt > > to IP Clearance. > > > > > > We conducted a Community Discussion @ Flagon and a VOTE. > > > > > > VOTE Thread on Flagon Private: > > https://lists.apache.org/thread/t5gof3sj40xrv2ylrgntx6oz2vdcc37t > > > > > > VOTE Result on Flagon Private: > > https://lists.apache.org/thread/dvz7rtxl77pfqb3c3tgn36g1wbfgr54h > > > > > > [3] +1 (+2 Binding) > > > [0] 0 > > > [0] -1 > > > > > > Accepted Submission of ICLA to Secretary: > > https://lists.apache.org/thread/fz6v7x9gjcllr5dvsf5ho9hbt7ogrwvw > > > > > > > > > > > > Respectfully, > > > > > > Josh (Flagon PPMC) > > > > > > > > > Details on the Software Grant Follow (copied from original Flagon VOTE) > > below: > > > > > > > > > The Software Grant encompasses a refactor of the Apache Flagon Distill > > product, which has been deprecated for a few years now [1] > > > > > This Grant includes ~150 new commits and thousands of new insertions > > (and a lot of deletions) At UMD my team and I re-thought Distill as a > > Python Package (for distro through PyPI) [2] that allows users to: > > > > > - efficiently segment UserALE.js (or User Behavior Logs) data > > > > > - curate segments - transform segments with logical operations > > (intersection, union, etc.) > > > > > - filter log data extracted from segments > > > > > - apply analytics (e.g., statistical, graphs) to data extracted from > > segments > > > > > - support graph-based visualization (funnel, sankey) > > > > > Additionally: > > > > > - code is well documented [3] > > > > > - excellent working examples [4] > > > > > Distill also provides examples for dashboards to visualize segments > > using both Apache Superset and Plotly/Dash > > > > > The original Distill product was tethered to a front-end (Tap), relied > > on rudimentary (and error-prone) processing of segments within the client. > > This made Distill difficult to maintain and required users to adopt tap, > > limiting their analytical use-cases with UserALE.js and Distill. Overall, > > I think that Distill provides a far more scaleable product to engage (and > > expand) our development community. I think this will add real value to > > Apache Flagon. > > > > > > > Overhead/Actions prior to release: > > > > > - Documentation builds will need be adjusted for a new repo/branch > > > > > - Additional documentation for a few analytical functions (i.e., > > click-rate) > > > > > - Minor tweaks to simply code in a few functions (i.e., click-rate) > > > > > - Some restructuring of Repo to consolidate and organize examples > > > > > - a few additional README’s should be added (i.e., examples /dir) > > > > > IP Clearance The Software Grant is signed by Felicia Metz, esq. who is > > an Associate Director at the University of Maryland’s, UMD Ventures office, > > which has authority to release UMD IP. That makes accepting this grant > > significantly easier from an IP Clearance perspective. New Committers The > > UMD executed CCLA includes 5 new committers and potentially new PPMC > > members [see 5 for executed Software Grant from UMD] > > > > > > [1] https://github.com/apache/incubator-flagon-distill > > > [2] > > https://github.com/UMD-ARLIS/incubator-flagon-distill/tree/distill_toolkit_refactor > > > [3] > > https://incubator-flagon-distill.readthedocs.io/en/distill_toolkit_refactor > > > [4] > > https://github.com/UMD-ARLIS/incubator-flagon-distill/blob/distill_toolkit_refactor/examples/Segments_Demo.ipynb > > > [5] https://lists.apache.org/thread/fz6v7x9gjcllr5dvsf5ho9hbt7ogrwvw > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org > > For additional commands, e-mail: general-h...@incubator.apache.org > > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org For additional commands, e-mail: general-h...@incubator.apache.org
