+1 (binding) As a minor comment - but definitely not the place to discuss it - I wonder if having a dedicated JIRA for that is really required. We could have the same approach as we do with nifi-fds (use the NIFI JIRA with the right use of tags, components, versions).
Le mer. 4 sept. 2019 à 08:22, Jeff <jtsw...@gmail.com> a écrit : > +1 Create NiFi Standard Libraries (binding) > > On Wed, Sep 4, 2019 at 12:19 AM Peter Wicks (pwicks) <pwi...@micron.com> > wrote: > > > +1, binding > > > > -----Original Message----- > > From: Kevin Doran <kdo...@apache.org> > > Sent: Tuesday, September 3, 2019 7:12 PM > > To: dev@nifi.apache.org; dev@nifi.apache.org > > Subject: [EXT] Re: [VOTE] Create NiFi Standard Libraries sub-project > > > > +1, binding > > > > > > ________________________________ > > From: Tony Kurc <trk...@gmail.com> > > Sent: Tuesday, September 3, 2019 8:33 PM > > To: dev@nifi.apache.org > > Subject: Re: [VOTE] Create NiFi Standard Libraries sub-project > > > > +1 (binding) > > > > On Wed, Sep 4, 2019 at 12:29 AM Aldrin Piri <aldrinp...@gmail.com> > wrote: > > > > > +1, binding > > > > > > On Tue, Sep 3, 2019 at 19:46 Yolanda Davis <yolanda.m.da...@gmail.com> > > > wrote: > > > > > > > +1 Create NiFi Standard Libraries (binding) > > > > > > > > On Tue, Sep 3, 2019 at 7:03 PM Koji Kawamura > > > > <ijokaruma...@gmail.com> > > > > wrote: > > > > > > > > > +1 Create NiFi Standard Libraries (binding) > > > > > > > > > > On Wed, Sep 4, 2019 at 7:25 AM Mike Thomsen > > > > > <mikerthom...@gmail.com> > > > > > wrote: > > > > > > > > > > > > +1 binding > > > > > > > > > > > > On Tue, Sep 3, 2019 at 5:33 PM Andy LoPresto > > > > > > <alopre...@apache.org> > > > > > wrote: > > > > > > > > > > > > > +1, create NiFi Standard Libraries (binding) > > > > > > > > > > > > > > Andy LoPresto > > > > > > > alopre...@apache.org > > > > > > > alopresto.apa...@gmail.com > > > > > > > PGP Fingerprint: 70EC B3E5 98A6 5A3F D3C4 BACE 3C6E F65B 2F7D > > > > > > > EF69 > > > > > > > > > > > > > > > On Sep 3, 2019, at 2:16 PM, Bryan Bende <bbe...@gmail.com> > > > wrote: > > > > > > > > > > > > > > > > All, > > > > > > > > > > > > > > > > In a previous thread there was a plan discussed to > > > > > > > > restructure > > > some > > > > > of > > > > > > > > the repositories in order to address several different > > > > > > > > issues, > > > such > > > > > as > > > > > > > > build time, reusability of code, and eventually separating > > > > > > > > how > > > the > > > > > > > > framework and extensions are released [1][2]. > > > > > > > > > > > > > > > > The overall plan requires many steps to get there, so I'd > > > > > > > > like to propose starting with a small actionable step - the > > > > > > > > creation of a > > > > new > > > > > > > > sub-project called NiFi Standard Libraries (formerly > > > > > > > > referred to > > > as > > > > > > > > nifi-commons). > > > > > > > > > > > > > > > > Project Name: Apache NiFi Standard Libraries Git Repository: > > > > > > > > nifi-standard-libraries > > > > > > > > JIRA: NIFILIBS > > > > > > > > > > > > > > > > Description: > > > > > > > > > > > > > > > > A collection of standard implementations used across the > > > > > > > > NiFi > > > > > ecosystem. > > > > > > > > > > > > > > > > Candidate Libraries: > > > > > > > > > > > > > > > > In general, each library may consist of multiple Maven > > > > > > > > modules, > > > and > > > > > > > > should be independent from the rest of the ecosystem, and > > > > > > > > from > > > > other > > > > > > > > libraries within NiFi Standard Libraries. > > > > > > > > > > > > > > > > In addition, each library may make it's own decision about > > > whether > > > > it > > > > > > > > is considered a public facing extension point/API, or an > > > > > > > > internal library that may be changed at any time. This > > > > > > > > should be > > > documented > > > > in > > > > > > > > a README at the root of each library, such as > > > > > > > > nifi-standard-libraries/nifi-xyz/README. > > > > > > > > > > > > > > > > An initial library that has been discussed was referred to > > > > > > > > as 'nifi-security' and would centralize much of the security > > > > > > > > related > > > > > code > > > > > > > > shared by NiFi and NiFi Registry, such as shared security > > > > > > > > APIs, > > > and > > > > > > > > implementations for various providers, such as > > LDAP/Kerberos/etc. > > > > > > > > > > > > > > > > A second candidate library would be an optimistic-locking > > > > > > > > library based on NiFi's revision concept. Currently this has > > > > > > > > been created inside nifi-registry for now [3], but could be > > > > > > > > moved as soon as nifi-standard-libraries exists. > > > > > > > > > > > > > > > > (This list does not have to be final in order to decide if > > > > > > > > we are creating NiFi Standard Libraries or not) > > > > > > > > > > > > > > > > Integration & Usage: > > > > > > > > > > > > > > > > Once NiFi Standard Libraries is created, the community can > > > > > > > > start creating and/or moving code there and perform releases > > > > > > > > as > > > > necessary. > > > > > A > > > > > > > > release will consist of the standard Apache source release, > > > > > > > > plus artifacts released to Maven central. The community can > > > > > > > > then > > > decide > > > > > > > > when it is appropriate to integrate these released libraries > > > > > > > > into > > > > one > > > > > > > > of our downstream projects. > > > > > > > > > > > > > > > > For example, if we create a nifi-security library in > > > > > > > > nifi-standard-libraries, we can release that whenever we > > > > > > > > decide, > > > > but > > > > > > > > we may not integrate it into NiFi or NiFi Registry until it > > > > > > > > makes sense for a given release of those projects. > > > > > > > > > > > > > > > > This vote will be open for 48 hours, please vote: > > > > > > > > > > > > > > > > [ ] +1 Create NiFi Standard Libraries [ ] +0 no opinion [ ] > > > > > > > > -1 Do not create NiFi Standard Libraries because... > > > > > > > > > > > > > > > > [1] > > > > > > > > > > > > > > > > > > > https://nam01.safelinks.protection.outlook.com/?url=http%3A%2F%2Fapach > > > e-nifi.1125220.n5.nabble.com%2Fdiscuss-Splitting-NiFi-framework-and-ex > > > tension-repos-and-releases-td27499.html&data=02%7C01%7Cpwicks%40mi > > > cron.com%7Cc81e3e4badd04535ffc508d730d4e61d%7Cf38a5ecd28134862b11bac1d > > > 563c806f%7C0%7C0%7C637031563258015148&sdata=m7YbxAEybvM0JzYmvB1KKu > > > 461I4w38jQtkeZ1Wfdt7o%3D&reserved=0 > > > > > > > > [2] > > > > > > > > > > > > > > > > > > > https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fcwik > > > i.apache.org%2Fconfluence%2Fdisplay%2FNIFIREG%2FNiFi%2BProject%2Band%2 > > > BRepository%2BRestructuring&data=02%7C01%7Cpwicks%40micron.com%7Cc > > > 81e3e4badd04535ffc508d730d4e61d%7Cf38a5ecd28134862b11bac1d563c806f%7C0 > > > %7C0%7C637031563258015148&sdata=XSSCVo0AJoh46tpddUMScEjxDy1RRX2c%2 > > > FBRAD%2FtDeQQ%3D&reserved=0 > > > > > > > > [3] > > > > > > > > > > > > > > > > > > > https://nam01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgith > > > ub.com%2Fapache%2Fnifi-registry%2Ftree%2Fmaster%2Fnifi-registry-core%2 > > > Fnifi-registry-revision&data=02%7C01%7Cpwicks%40micron.com%7Cc81e3 > > > e4badd04535ffc508d730d4e61d%7Cf38a5ecd28134862b11bac1d563c806f%7C0%7C0 > > > %7C637031563258015148&sdata=p%2FTCdfpvXdN0TysMHkIKeP3cnNs8bEERHro3 > > > NVfnfi4%3D&reserved=0 > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > -- > > > > yolanda.m.da...@gmail.com > > > > @YolandaMDavis > > > > > > > > > >
