Return-Path: X-Original-To: apmail-incubator-general-archive@www.apache.org Delivered-To: apmail-incubator-general-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 9A68117E14 for ; Sat, 22 Nov 2014 01:31:15 +0000 (UTC) Received: (qmail 77441 invoked by uid 500); 22 Nov 2014 01:31:15 -0000 Delivered-To: apmail-incubator-general-archive@incubator.apache.org Received: (qmail 77270 invoked by uid 500); 22 Nov 2014 01:31:14 -0000 Mailing-List: contact general-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: general@incubator.apache.org Delivered-To: mailing list general@incubator.apache.org Received: (qmail 77258 invoked by uid 99); 22 Nov 2014 01:31:14 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Nov 2014 01:31:14 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of joe.witt@gmail.com designates 209.85.218.50 as permitted sender) Received: from [209.85.218.50] (HELO mail-oi0-f50.google.com) (209.85.218.50) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Nov 2014 01:30:46 +0000 Received: by mail-oi0-f50.google.com with SMTP id a141so4470371oig.37 for ; Fri, 21 Nov 2014 17:28:29 -0800 (PST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=BjqGd0+RY6mCLc8OGWPQdujofrLEcuXG0D3MWC90HM8=; b=mvDiXWIUVt85W6dc3CzkTgIwnNmP8xkW3CYYhFK3+uXqvespsitIMP023ZfQ0E7eP3 BpVyNK3s7/l1a7hq7v2wkFHqsqfWFJrI07YDcbHX5GUTW7ZJdfZirudowdjwPMNmyTA8 1r4q12N8V5/5Td/gtcHY0bd+JelCHclSvr/s9wRAetl1ppGd6Nt/z9CMHDLsD4FNV6iq NVSfvSL/41PV0hiPq6O86ImaEPE/HuMCkN9T+tKEqTYabbfB4hrDkTsgfhO/COQtshhr 7a9AOxUgqV3I3ZBFN4VGMDRWK1m15WhDEHXfJed5d2cFco8kAcxSQ9laebn7pEQP3AuY HPPA== MIME-Version: 1.0 X-Received: by 10.60.50.137 with SMTP id c9mr3654905oeo.83.1416619709597; Fri, 21 Nov 2014 17:28:29 -0800 (PST) Received: by 10.202.230.66 with HTTP; Fri, 21 Nov 2014 17:28:29 -0800 (PST) In-Reply-To: References:

<546FB878.8030306@apache.org> <546FBA60.1040809@apache.org> Date: Fri, 21 Nov 2014 20:28:29 -0500 Message-ID: Subject: Re: [PROPOSAL] NiFi for Incubation From: Joe Witt To: general@incubator.apache.org Content-Type: multipart/alternative; boundary=001a11c2deb8928d150508687a43 X-Virus-Checked: Checked by ClamAV on apache.org --001a11c2deb8928d150508687a43 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Andrew - I've updated the proposal to reflect you as a mentor. * Andrew Purtell (Salesforce) , IPMC Member Thanks again Joe On Fri, Nov 21, 2014 at 5:29 PM, Joe Witt wrote: > Andrew - appreciate your comments and offer to assist as a mentor. Now > that the vote for incubation has kicked off i'm not sure what i'm allowed > to do or not. Will check will Benson. > > For what it is worth I agree Sean raised a great point. I think it will > be an important part of our community building effort. And to echo Josh'= s > point this proposal represents not just our intent to grow the community > outside our current home but rather move homes - to the ASF. We're very > excited to have this opportunity. > > Thanks > Joe > > On Fri, Nov 21, 2014 at 5:19 PM, Josh Elser wrote: > >> Thanks for the clarification -- that wasn't how it came across to me. >> >> >> Andrew Purtell wrote: >> >>> I didn't make an assertion *about* Accumulo, what I said exactly was: >>> >>> "that Accumulo may or may not suffer from "bifurcation" is >>> debatable" >>> >>> I assert there are two sides to that argument (I've heard them both)=E2= =80=8B=E2=80=8B, >>> merely to suggest that Sean's concerns should not be dismissed as they >>> were. >>> >>> >>> On Fri, Nov 21, 2014 at 2:11 PM, Josh Elser wrote: >>> >>> I would tend to disagree with your assertion about Accumulo, but this = is >>>> neither the time nor the place to discuss Accumulo's strengths and >>>> weaknesses. >>>> >>>> I'll make the assumption that request to enter incubation is a strong >>>> intent to grow outside of the project's current home. >>>> >>>> +1 (non-binding) for entry >>>> >>>> >>>> Andrew Purtell wrote: >>>> >>>> From what I understand, that Accumulo may or may not suffer from >>>>> "bifurcation" is debatable despite this blanket claim otherwise. >>>>> >>>>> Regardless, Sean's point is valid, even if only a theoretical concern >>>>> for >>>>> NiFi at this point. If the podling is interested in growing outside >>>>> community I'd be happy to sign on as a mentor to help that happen. >>>>> >>>>> On Thu, Nov 20, 2014 at 3:32 AM, Benson Margulies>>>> com> >>>>> wrote: >>>>> >>>>> Sean, >>>>> >>>>>> The precedent of Accumulo is that the govt people and agencies >>>>>> involved >>>>>> are >>>>>> ready and able to have their staff collaborate openly in an Apache >>>>>> community. There's no need to contemplate bifurcation; we have this >>>>>> proposal because the management recognizes that this collaboration >>>>>> produces >>>>>> better stuff that solves more problems than the 'inside the tent' >>>>>> alternative. >>>>>> >>>>>> --benson >>>>>> >>>>>> >>>>>> On Thu, Nov 20, 2014 at 1:50 AM, Sean Busbey >>>>>> wrote: >>>>>> >>>>>> I'm really excited to see NiFi come to the incubator; it'd be a >>>>>> great >>>>>> >>>>>>> addition to the ASF. >>>>>>> >>>>>>> A few points in the proposal: >>>>>>> >>>>>>> =3D=3D Initial Goals =3D=3D >>>>>>> >>>>>>>> One of these should be to grow the community outside of the curren= t >>>>>>>> >>>>>>> niche, >>>>>> >>>>>> IMHO. >>>>>>> >>>>>>> More on this below under "orphaned projects" >>>>>>> >>>>>>> * Determine and establish a mechanism, possibly including a >>>>>>> >>>>>>>> sub-project construct, that allows for extensions to the core >>>>>>>>> application to occur at a pace that differs from the core >>>>>>>>> application >>>>>>>>> itself. >>>>>>>>> >>>>>>>>> I don't think the proposal needs to include the "e.g. with >>>>>>>> >>>>>>> sub-projects" >>>>>>> part. Just noting >>>>>>> that your goals in the incubator are to address the need to have >>>>>>> >>>>>>> different >>>>>> >>>>>> release cycles >>>>>>> for core and extensions is sufficient. >>>>>>> >>>>>>> >>>>>>> =3D=3D=3D Community =3D=3D=3D >>>>>>> >>>>>>>> Over the past several years, NiFi has developed a strong community >>>>>>>>> of >>>>>>>>> both developers and operators within the U.S. government. We loo= k >>>>>>>>> forward to helping grow this to a broader base of industries. >>>>>>>>> >>>>>>>>> How much, if any, of this community do you expect to engage via >>>>>>>>> the >>>>>>>>> >>>>>>>> customary project >>>>>>> lists once NiFi is established within the ASF? Will the project be >>>>>>> able >>>>>>> >>>>>>> to >>>>>> >>>>>> leverage this >>>>>>> established group? >>>>>>> >>>>>>> >>>>>>> =3D=3D=3D Orphaned Products =3D=3D=3D >>>>>>> >>>>>>>> Risk of orphaning is minimal. The project user and developer base >>>>>>>>> is >>>>>>>>> substantial, growing, and there is already extensive operational >>>>>>>>> use >>>>>>>>> of NiFi. >>>>>>>>> >>>>>>>>> Given that the established base is internal to the U.S. >>>>>>>> government, I'd >>>>>>>> >>>>>>> encourage the >>>>>>> podling to consider the risk of a bifurcated project should a >>>>>>> substantial >>>>>>> outside >>>>>>> community fail to emerge or if those internal users should fail to >>>>>>> engage >>>>>>> with the >>>>>>> outside community. >>>>>>> >>>>>>> You cover a related issue in your "Homogenous Developers" section. >>>>>>> But I >>>>>>> think >>>>>>> building on the "Community" section of the current state to call th= is >>>>>>> out >>>>>>> as an >>>>>>> independent issue is worthwhile. >>>>>>> >>>>>>> >>>>>>> possible. This environment includes widely accessible source cod= e >>>>>>> >>>>>>>> repositories, published artifacts, ticket tracking, and extensive >>>>>>>>> documentation. We also encourage contributions and frequent debat= e >>>>>>>>> and >>>>>>>>> hold regular, collaborative discussions through e-mail, chat room= s, >>>>>>>>> and in-person meet-ups. >>>>>>>>> >>>>>>>>> Do you anticipate any difficulties moving these established >>>>>>>> >>>>>>> communication >>>>>>> mechanisms to ASF public lists? >>>>>>> >>>>>>> =3D=3D=3D Documentation =3D=3D=3D >>>>>>> >>>>>>>> At this time there is no NiFi documentation on the web. However, = we >>>>>>>>> have extensive documentation included within the application that >>>>>>>>> details usage of the many functions. We will be rapidly expandin= g >>>>>>>>> the >>>>>>>>> available documentation to cover things like installation, >>>>>>>>> developer >>>>>>>>> guide, frequently asked questions, best practices, and more. Thi= s >>>>>>>>> documentation will be posted to the NiFi wiki at apache.org. >>>>>>>>> >>>>>>>>> I love projects that start with documentation. :) >>>>>>>> >>>>>>> I don't think the proposal needs to include that the documentation >>>>>>> will >>>>>>> >>>>>>> be >>>>>> >>>>>> posted >>>>>>> to the NiFi wiki, since that's an implementation detail. Just say >>>>>>> "this >>>>>>> documentation >>>>>>> will be made available via the NiFi project's use of incubator >>>>>>> infra." >>>>>>> >>>>>>> (I'll save detail for the eventual dev@ list, but you should >>>>>>> strongly >>>>>>> consider not >>>>>>> using the wiki to host this documentation.) >>>>>>> >>>>>>> -Sean >>>>>>> >>>>>>> On Wed, Nov 19, 2014 at 11:27 PM, Brock Noland >>>>>>> >>>>>>> wrote: >>>>>> >>>>>> Hi Joe, >>>>>>> >>>>>>>> I know you've done a tremendous amount of work to make this happen >>>>>>>> so I >>>>>>>> >>>>>>>> am >>>>>>> >>>>>>> extremely happy this is *finally* making it's way to the incubator= ! >>>>>>>> >>>>>>>> I look forward to helping in anyway I can. >>>>>>>> >>>>>>>> Cheers! >>>>>>>> Brock >>>>>>>> >>>>>>>> On Wed, Nov 19, 2014 at 8:11 PM, Mattmann, Chris A (3980)< >>>>>>>> chris.a.mattmann@jpl.nasa.gov> wrote: >>>>>>>> >>>>>>>> This is *fan freakin=C2=B9 tastic* Sounds like an awesome proje= ct and >>>>>>>> >>>>>>>>> glad to hear a relationship to Tika! Awesome to see more governme= nt >>>>>>>>> projects coming into the ASF! >>>>>>>>> >>>>>>>>> you already have a great set of mentors and I don=C2=B9t really h= ave >>>>>>>>> more >>>>>>>>> time on my plate, but really happy and will try and monitor and >>>>>>>>> help >>>>>>>>> on the lists. >>>>>>>>> >>>>>>>>> Cheers! >>>>>>>>> >>>>>>>>> Chris >>>>>>>>> >>>>>>>>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= + >>>>>>>>> Chris Mattmann, Ph.D. >>>>>>>>> Chief Architect >>>>>>>>> Instrument Software and Science Data Systems Section (398) >>>>>>>>> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA >>>>>>>>> Office: 168-519, Mailstop: 168-527 >>>>>>>>> Email: chris.a.mattmann@nasa.gov >>>>>>>>> WWW: http://sunset.usc.edu/~mattmann/ >>>>>>>>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= + >>>>>>>>> Adjunct Associate Professor, Computer Science Department >>>>>>>>> University of Southern California, Los Angeles, CA 90089 USA >>>>>>>>> +++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++= + >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -----Original Message----- >>>>>>>>> From: Joe Witt >>>>>>>>> Reply-To: "general@incubator.apache.org"< >>>>>>>>> >>>>>>>>> general@incubator.apache.org >>>>>>>> >>>>>>> Date: Thursday, November 20, 2014 at 3:02 AM >>>>>>> >>>>>>>> To: "general@incubator.apache.org" >>>>>>>>> Subject: [PROPOSAL] NiFi for Incubation >>>>>>>>> >>>>>>>>> Hello, >>>>>>>>> >>>>>>>>>> >>>>>>>>>> I would like to propose NiFi as an Apache Incubator Project. >>>>>>>>>> >>>>>>>>>> In addition to the copy provided below the Wiki version of the >>>>>>>>>> proposal can be found here: >>>>>>>>>> http://wiki.apache.org/incubator/NiFiProposal >>>>>>>>>> >>>>>>>>>> Thanks >>>>>>>>>> >>>>>>>>>> Joe >>>>>>>>>> >>>>>>>>>> >>>>>>>>>> =3D NiFi Proposal =3D >>>>>>>>>> >>>>>>>>>> =3D=3D Abstract =3D=3D >>>>>>>>>> NiFi is a dataflow system based on the concepts of flow-based >>>>>>>>>> >>>>>>>>>> programming. >>>>>>>>> =3D=3D Proposal =3D=3D >>>>>>>>> >>>>>>>>>> NiFi supports powerful and scalable directed graphs of data >>>>>>>>>> routing, >>>>>>>>>> transformation, and system mediation logic. Some of the >>>>>>>>>> high-level >>>>>>>>>> capabilities and objectives of NiFi include: >>>>>>>>>> * Web-based user interface for seamless experience between >>>>>>>>>> design, >>>>>>>>>> control, feedback, and monitoring of data flows >>>>>>>>>> * Highly configurable along several dimensions of quality of >>>>>>>>>> >>>>>>>>>> service >>>>>>>>> >>>>>>>> such as loss tolerant versus guaranteed delivery, low latency vers= us >>>>>>> >>>>>>>> high throughput, and priority based queuing >>>>>>>>>> * Fine-grained data provenance for all data received, forked, >>>>>>>>>> joined, cloned, modified, sent, and ultimately dropped as data >>>>>>>>>> >>>>>>>>>> reaches >>>>>>>>> >>>>>>>> its configured end-state >>>>>>> >>>>>>>> * Component-based extension model along well defined interfaces >>>>>>>>>> enabling rapid development and effective testing >>>>>>>>>> >>>>>>>>>> =3D=3D Background =3D=3D >>>>>>>>>> Reliable and effective dataflow between systems can be difficult >>>>>>>>>> whether you're running scripts on a laptop or have a massive >>>>>>>>>> distributed computing system operated by numerous teams and >>>>>>>>>> organizations. As the volume and rate of data grows and as the >>>>>>>>>> >>>>>>>>>> number >>>>>>>>> >>>>>>>> of systems, protocols, and formats increase and evolve so too does >>>>>>> >>>>>>>> the >>>>>>>>> >>>>>>>> complexity and need for greater insight and agility. These are th= e >>>>>>> >>>>>>>> dataflow challenges that NiFi was built to tackle. >>>>>>>>>> >>>>>>>>>> NiFi is designed in a manner consistent with the core concepts >>>>>>>>>> described in flow-based programming as originally documented by = J. >>>>>>>>>> Paul Morrison in the 1970s. This model lends itself well to >>>>>>>>>> visual >>>>>>>>>> diagramming, concurrency, componentization, testing, and reuse. >>>>>>>>>> In >>>>>>>>>> addition to staying close to the fundamentals of flow-based >>>>>>>>>> programming, NiFi provides integration system specific features >>>>>>>>>> such >>>>>>>>>> as: guaranteed delivery; back pressure; ability to gracefully >>>>>>>>>> handle >>>>>>>>>> backlogs and data surges; and an operator interface that enables >>>>>>>>>> on-the-fly data flow generation, modification, and observation. >>>>>>>>>> >>>>>>>>>> =3D=3D Rationale =3D=3D >>>>>>>>>> NiFi provides a reliable, scalable, manageable and accountable >>>>>>>>>> platform for developers and technical staff to create and evolve >>>>>>>>>> powerful data flows. Such a system is useful in many contexts >>>>>>>>>> including large-scale enterprise integration, interaction with >>>>>>>>>> cloud >>>>>>>>>> services and frameworks, business to business, intra-departmenta= l, >>>>>>>>>> >>>>>>>>>> and >>>>>>>>> >>>>>>>> inter-departmental flows. NiFi fits well within the Apache Softwa= re >>>>>>> >>>>>>>> Foundation (ASF) family as it depends on numerous ASF projects and >>>>>>>>>> integrates with several others. We also anticipate developing >>>>>>>>>> extensions for several other ASF projects such as Cassandra, >>>>>>>>>> Kafka, >>>>>>>>>> and Storm in the near future. >>>>>>>>>> >>>>>>>>>> =3D=3D Initial Goals =3D=3D >>>>>>>>>> * Ensure all dependencies are compliant with Apache License >>>>>>>>>> >>>>>>>>>> version >>>>>>>>> >>>>>>>> 2.0 and all that all code and documentation artifacts have the >>>>>>> >>>>>>>> correct >>>>>>>>> >>>>>>>> Apache licensing markings and notice. >>>>>>> >>>>>>>> * Establish a formal release process and schedule, allowing for >>>>>>>>>> dependable release cycles in a manner consistent with the Apache >>>>>>>>>> development process. >>>>>>>>>> * Determine and establish a mechanism, possibly including a >>>>>>>>>> sub-project construct, that allows for extensions to the core >>>>>>>>>> application to occur at a pace that differs from the core >>>>>>>>>> >>>>>>>>>> application >>>>>>>>> >>>>>>>> itself. >>>>>>> >>>>>>>> =3D=3D Current Status =3D=3D >>>>>>>>>> =3D=3D=3D Meritocracy =3D=3D=3D >>>>>>>>>> An integration platform is only as good as its ability to >>>>>>>>>> integrate >>>>>>>>>> systems in a reliable, timely, and repeatable manner. The same >>>>>>>>>> can >>>>>>>>>> >>>>>>>>>> be >>>>>>>>> >>>>>>>> said of its ability to attract talent and a variety of perspective= s >>>>>>> >>>>>>>> as >>>>>>>>> >>>>>>>> integration systems by their nature are always evolving. We will >>>>>>> >>>>>>>> actively seek help and encourage promotion of influence in the >>>>>>>>>> >>>>>>>>>> project >>>>>>>>> >>>>>>>> through meritocracy. >>>>>>> >>>>>>>> =3D=3D=3D Community =3D=3D=3D >>>>>>>>>> Over the past several years, NiFi has developed a strong communi= ty >>>>>>>>>> >>>>>>>>>> of >>>>>>>>> >>>>>>>> both developers and operators within the U.S. government. We look >>>>>>> >>>>>>>> forward to helping grow this to a broader base of industries. >>>>>>>>>> >>>>>>>>>> =3D=3D=3D Core Developers =3D=3D=3D >>>>>>>>>> The initial core developers are employed by the National Securit= y >>>>>>>>>> Agency and defense contractors. We will work to grow the >>>>>>>>>> community >>>>>>>>>> among a more diverse set of developers and industries. >>>>>>>>>> >>>>>>>>>> =3D=3D=3D Alignment =3D=3D=3D >>>>>>>>>> >>>>>>>>>> From its inception, NiFi was developed with an open source >>>>>>>>>> >>>>>>>>> philosophy >>>>>>>> >>>>>>> in mind and with the hopes of eventually being truly open sourced. >>>>>>> >>>>>>>> The Apache way is consistent with the approach we have taken to >>>>>>>>>> >>>>>>>>>> date. >>>>>>>>> >>>>>>>> The ASF clearly provides a mature and effective environment for >>>>>>> >>>>>>>> successful development as is evident across the spectrum of >>>>>>>>>> >>>>>>>>>> well-known >>>>>>>>> >>>>>>>> projects. Further, NiFi depends on numerous ASF libraries and >>>>>>> >>>>>>>> projects including; ActiveMQ, Ant, Commons, Lucene, Hadoop, >>>>>>>>>> HttpClient, Jakarta and Maven. We also anticipate extensions an= d >>>>>>>>>> dependencies with several more ASF projects, including Accumulo, >>>>>>>>>> >>>>>>>>>> Avro, >>>>>>>>> >>>>>>>> Casandra, HBase, JClouds, Storm, Kafka, Thrift, Tika, and others. >>>>>>> >>>>>>>> This existing alignment with Apache and the desired community make= s >>>>>>>>>> the Apache Incubator a good fit for NiFi. >>>>>>>>>> >>>>>>>>>> =3D=3D Known Risks =3D=3D >>>>>>>>>> =3D=3D=3D Orphaned Products =3D=3D=3D >>>>>>>>>> Risk of orphaning is minimal. The project user and developer ba= se >>>>>>>>>> >>>>>>>>>> is >>>>>>>>> >>>>>>>> substantial, growing, and there is already extensive operational u= se >>>>>>> >>>>>>>> of NiFi. >>>>>>>>>> >>>>>>>>>> =3D=3D=3D Inexperience with Open Source =3D=3D=3D >>>>>>>>>> The initial committers to NiFi have limited experience with true >>>>>>>>>> >>>>>>>>>> open >>>>>>>>> >>>>>>>> source software development. However, despite the project origins >>>>>>> >>>>>>>> being from closed source development we have modelled our behavior >>>>>>>>>> >>>>>>>>>> and >>>>>>>>> >>>>>>>> community development on The Apache Way to the greatest extent >>>>>>> >>>>>>>> possible. This environment includes widely accessible source code >>>>>>>>>> repositories, published artifacts, ticket tracking, and extensiv= e >>>>>>>>>> documentation. We also encourage contributions and frequent deba= te >>>>>>>>>> >>>>>>>>>> and >>>>>>>>> >>>>>>>> hold regular, collaborative discussions through e-mail, chat rooms= , >>>>>>> >>>>>>>> and in-person meet-ups. We are committed to the ideals of open >>>>>>>>>> >>>>>>>>>> source >>>>>>>>> >>>>>>>> software and will eagerly seek out mentors and sponsors who can he= lp >>>>>>> >>>>>>>> us quickly come up to speed. >>>>>>>>>> >>>>>>>>>> =3D=3D=3D Homogenous Developers =3D=3D=3D >>>>>>>>>> The initial committers of NiFi come from a limited set of entiti= es >>>>>>>>>> though we are committed to recruiting and developing additional >>>>>>>>>> committers from a broad spectrum of industries and backgrounds. >>>>>>>>>> >>>>>>>>>> =3D=3D=3D Reliance on Salaried Developers =3D=3D=3D >>>>>>>>>> We expect NiFi development to continue on salaried time and >>>>>>>>>> through >>>>>>>>>> volunteer time. The initial committers are paid by their >>>>>>>>>> employers >>>>>>>>>> >>>>>>>>>> to >>>>>>>>> >>>>>>>> contribute to this project. We are committed to developing and >>>>>>> >>>>>>>> recruiting participation from developers both salaried and >>>>>>>>>> non-salaried. >>>>>>>>>> >>>>>>>>>> =3D=3D=3D Relationship with other Apache Projects =3D=3D=3D >>>>>>>>>> As described in the alignment section, NiFi is already heavily >>>>>>>>>> dependent on other ASF projects and we anticipate further >>>>>>>>>> dependence >>>>>>>>>> and integration with new and emerging projects in the Apache >>>>>>>>>> family. >>>>>>>>>> >>>>>>>>>> =3D=3D=3D An Excessive Fascination with the Apache Brand =3D=3D= =3D >>>>>>>>>> We respect the laudable Apache brand and that is certainly a >>>>>>>>>> factor >>>>>>>>>> >>>>>>>>>> in >>>>>>>>> >>>>>>>> the decision to propose NiFi for the Apache Incubator. We intend = to >>>>>>> >>>>>>>> provide a great deal of energy and capability to the ASF through >>>>>>>>>> >>>>>>>>>> this >>>>>>>>> >>>>>>>> project. We will be sensitive to and respectful of any overuse of >>>>>>> >>>>>>>> the >>>>>>>>> >>>>>>>> Apache brand and ensure our focus remains on how we benefit the >>>>>>> >>>>>>>> Apache >>>>>>>>> >>>>>>>> community. >>>>>>> >>>>>>>> =3D=3D=3D Documentation =3D=3D=3D >>>>>>>>>> At this time there is no NiFi documentation on the web. However= , >>>>>>>>>> we >>>>>>>>>> have extensive documentation included within the application tha= t >>>>>>>>>> details usage of the many functions. We will be rapidly expandi= ng >>>>>>>>>> >>>>>>>>>> the >>>>>>>>> >>>>>>>> available documentation to cover things like installation, develop= er >>>>>>> >>>>>>>> guide, frequently asked questions, best practices, and more. This >>>>>>>>>> documentation will be posted to the NiFi wiki at apache.org. >>>>>>>>>> >>>>>>>>>> =3D=3D Initial Source =3D=3D >>>>>>>>>> NiFi has been in active development since late 2006 with >>>>>>>>>> >>>>>>>>>> contributions >>>>>>>>> >>>>>>>> >from dozens of developers and feedback from hundreds of users and >>>>>>> >>>>>>>> developers. The core codebase is written in Java and includes >>>>>>>>>> detailed Javadocs and feature documentation. >>>>>>>>>> >>>>>>>>>> =3D=3D Source and Intellectual Property Submission =3D=3D >>>>>>>>>> Previously referred to as Niagarafiles, the NiFi code and >>>>>>>>>> documentation materials will be submitted by the National Securi= ty >>>>>>>>>> Agency. NiFi has been developed by a mix of government employee= s >>>>>>>>>> >>>>>>>>>> and >>>>>>>>> >>>>>>>> private companies under government contract. Material developed b= y >>>>>>> >>>>>>>> the government employees is in the public domain and no U.S. >>>>>>>>>> >>>>>>>>>> copyright >>>>>>>>> >>>>>>>> exists in works of the federal government. For the contractor >>>>>>> >>>>>>>> developed material in the initial submission, the U.S. Government >>>>>>>>>> >>>>>>>>>> has >>>>>>>>> >>>>>>>> sufficient authority to open source per DFARS 252.227-7014. NSA >>>>>>> >>>>>>>> has >>>>>>>>> >>>>>>>> submitted the Software Grant Agreement and Corporate Contributor >>>>>>> >>>>>>>> License Agreement to the Apache Software Foundation. >>>>>>>>>> >>>>>>>>>> =3D=3D External Dependencies =3D=3D >>>>>>>>>> We have at least one dependency on an LGPL library which we will >>>>>>>>>> promptly address. Otherwise, we believe all current dependencie= s >>>>>>>>>> >>>>>>>>>> are >>>>>>>>> >>>>>>>> compatible with the ASF guidelines. Our dependency licenses come >>>>>>> >>>>>>>> from >>>>>>>>> >>>>>>>> the following license styles: Apache v 2.0, BSD, Public Domain, >>>>>>> >>>>>>>> Eclipse Public v1, MIT, CDDL v1. >>>>>>>>>> >>>>>>>>>> =3D=3D Cryptography =3D=3D >>>>>>>>>> Consistent with http://www.apache.org/licenses/exports/ we >>>>>>>>>> believe >>>>>>>>>> NiFi is classified as ECCN 5D002. NiFi doesn't implement any >>>>>>>>>> cryptographic algorithms but is designed to use algorithms >>>>>>>>>> provided >>>>>>>>>> >>>>>>>>>> by >>>>>>>>> >>>>>>>> Oracle Java Cryptographic Extensions, BouncyCastle, and JCraft, In= c. >>>>>>> >>>>>>>> These cryptographic algorithm providers are used to support SSL, >>>>>>>>>> SSH/SFTP, and the encryption and decryption of sensitive >>>>>>>>>> properties. >>>>>>>>>> In the event that it becomes necessary we will engage with >>>>>>>>>> >>>>>>>>>> appropriate >>>>>>>>> >>>>>>>> Apache members to ensure we file any necessary paperwork or >>>>>>> >>>>>>>> clarified >>>>>>>>> >>>>>>>> any cryptographic export license concerns. >>>>>>> >>>>>>>> =3D=3D Required Resources =3D=3D >>>>>>>>>> =3D=3D=3D Mailing Lists =3D=3D=3D >>>>>>>>>> * user@nifi.incubator.apache.org >>>>>>>>>> * dev@nifi.incubator.apache.org >>>>>>>>>> * private@nifi.incubator.apache.org >>>>>>>>>> * commits@nifi.incubator.apache.org >>>>>>>>>> >>>>>>>>>> =3D=3D=3D Source Control =3D=3D=3D >>>>>>>>>> NiFi requests use of Git for source control >>>>>>>>>> (git://git.apache.org/nifi.git). We request a writeable Git rep= o >>>>>>>>>> >>>>>>>>>> for >>>>>>>>> >>>>>>>> NiFi with mirroring to be setup to Github through INFRA. We reque= st >>>>>>> >>>>>>>> sponsor Benson Margulies (bimargulies) to assist with creating the >>>>>>>>>> INFRA ticket for this. >>>>>>>>>> >>>>>>>>>> =3D=3D=3D Issue Tracking =3D=3D=3D >>>>>>>>>> JIRA NiFi (NIFI) >>>>>>>>>> >>>>>>>>>> =3D=3D=3D Initial Committers =3D=3D=3D >>>>>>>>>> * Brandon Devries >>>>>>>>>> * Matt Gilman >>>>>>>>>> * Tony Kurc >>>>>>>>>> * Mark Payne >>>>>>>>>> * Adam Taft >>>>>>>>>> * Joseph Witt >>>>>>>>>> >>>>>>>>>> =3D=3D=3D Affiliations =3D=3D=3D >>>>>>>>>> * Brandon Devries (Requitest, Inc.) >>>>>>>>>> * Matt Gilman (Raytheon) >>>>>>>>>> * Tony Kurc (National Security Agency) >>>>>>>>>> * Mark Payne (Sotera Defense Solutions, Inc.) >>>>>>>>>> * Adam Taft (Requitest, Inc.) >>>>>>>>>> * Joseph Witt (National Security Agency) >>>>>>>>>> >>>>>>>>>> =3D=3D Sponsors =3D=3D >>>>>>>>>> =3D=3D=3D Champion =3D=3D=3D >>>>>>>>>> * Benson Margulies (Basis Technology)>>>>>>>>> >>>>>>>>>> org> >>>>>>>>> >>>>>>>> =3D=3D=3D Nominated Mentors =3D=3D=3D >>>>>>>> >>>>>>>>> * Drew Farris (Booz Allen Hamilton) >>>>>>>>>> * Brock Noland (Cloudera) >>>>>>>>>> * Billie Rinaldi (Hortonworks) >>>>>>>>>> >>>>>>>>>> =3D=3D=3D Sponsoring Entity =3D=3D=3D >>>>>>>>>> We request the Apache Incubator to sponsor this project. >>>>>>>>>> >>>>>>>>>> ------------------------------------------------------------ >>>>>>>>> --------- >>>>>>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org >>>>>>>>> For additional commands, e-mail: general-help@incubator.apache.or= g >>>>>>>>> >>>>>>>>> >>>>>>>>> >>>>>>>>> -- >>>>>>> Sean >>>>>>> >>>>>>> >>>>>>> >>>>> >>>>> --------------------------------------------------------------------= - >>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org >>>> For additional commands, e-mail: general-help@incubator.apache.org >>>> >>>> >>>> >>> >>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org >> For additional commands, e-mail: general-help@incubator.apache.org >> >> > --001a11c2deb8928d150508687a43--