Re: [QUESTION] Oracle JDBC Driver as a test dependency

[Joe Witt]

Hello

In general with all such things ASF and licensing a great place to start
for information is here [1].  It lays out the different categories and how
ASF Legal has designated a given license.

The way to really consider this largely comes down to whether you package
that binary in a release you make available.  Based on the POM this implies
to me the JAR is only pulled by someone taking the source release and then
building it.  So in terms of the official apache source release you'd do as
part of KIE you're fine since this is not in the source.  Then you consider
your convenience binary build if you have one.  If this is only with tests
then it is clearly optional provided it doesn't end up in the actual build
results of the project.

In your source release anything in Category A is fair game.  Things in
Category B are not.  Things in Category X never are.

In your convenience binary release (if you have one) anything in Category A
is fair game.  Anything in Category B can be fair game as well.  Anything
in Category X is generally a no unless is an optional package and you
generally want to ensure the user is grabbing that dependency and bringing
it to the resulting build as you cannot ship it.

Biggest advice here is to become really familiar with these categories and
which licenses are there.  I do not see the Oracle Free License listed so
I'd handle that as Category X until reviewed.

[1] https://www.apache.org/legal/resolved.html

Thanks

On Wed, Jan 10, 2024 at 8:39 AM Juan Pablo Santos Rodríguez <
juanpablo.san...@gmail.com> wrote:

> Hi!
>
> I'd say the situation has changed a bit, as those jars are available at
> central since version 19.3, IIRC ([#1]).
>
> They are published under Oracle Free Use Term and Conditions (FUCT) license
> ([#2]), so I'd check again with legal to see if this license is allowed or
> not.
>
>
> HTH,
> juan pablo
>
>
> [#1] https://search.maven.org/search?q=g:com.oracle.database.jdbc
> [#2 ]
> https://www.oracle.com/downloads/licenses/oracle-free-license.html
>
> El mié, 10 ene 2024, 16:23, Alex Porcelli  escribió:
>
> > In KIE podling we have reference for the Oracle JDBC driver being used
> > only for tests [1], however based on this ticket [2], it's not clear
> > if we can continue to use it or this dependency has to be removed.
> >
> > Guidance on this topic would be highly appreciated!
> >
> > Regards,
> > Alex
> >
> > [1]
> >
> https://github.com/apache/incubator-kie-kogito-runtimes/blob/3aa26113d7e88f0fd7d0331ec20fe392f343afb6/kogito-test-utils/pom.xml#L89-L99
> > [2] https://issues.apache.org/jira/browse/LEGAL-526
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Accept StreamPipes into the Apache Incubator

[Joe Witt]

+1(binding)

On Thu, Nov 7, 2019 at 4:45 PM Kevin Ratnasekera 
wrote:

> +1 ( binding )
>
> On Fri, Nov 8, 2019 at 2:04 AM Bertrand Delacretaz <
> bdelacre...@codeconsult.ch> wrote:
>
> > On Thu, Nov 7, 2019 at 8:00 PM Dominik Riemer  wrote:
> > >   [X ] +1, bring StreamPipes into the Incubator..
> >
> > With 5 mentors for 5 initial committers you should be well taken care of
> > ;-)
> >
> > -Bertrand
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [Vote] call a vote for IoTDB incubation proposal

[Joe Witt]

+1 binding.

would be interested to participate as a mentor

thanks

On Wed, Nov 7, 2018, 12:53 PM Matt Sicker  +1 (binding)
>
> On Wed, 7 Nov 2018 at 08:03, Kevin A. McGrail  wrote:
>
> > +1 (binding)
> >
> > On 11/7/2018 2:46 AM, hxd wrote:
> > > Hi,
> > > Sorry for the previous mail with bad format.
> > > I'd like to call a VOTE to accept IoTDB project, a database for
> managing
> > large amounts of time series data  from IoT sensors in industrial
> > applications, into the Apache Incubator.
> > > The full proposal is available on the wiki:
> > https://wiki.apache.org/incubator/IoTDBProposal
> > > and it is also attached below for your convenience.
> > >
> > > Please cast your vote:
> > >
> > >   [ ] +1, bring IoTDB into Incubator
> > >   [ ] +0, I don't care either way,
> > >   [ ] -1, do not bring IoTDB into Incubator, because...
> > >
> > > The vote will open at least for 72 hours.
> > >
> > > Thanks,
> > > Xiangdong Huang.
> > >
> > > = IoTDB Proposal  =
> > > v0.1.1
> > >
> > >
> > > == Abstract ==
> > > IoTDB is a data store for managing large amounts of time series data
> > such as timestamped data from IoT sensors in industrial applications.
> > >
> > > == Proposal ==
> > > IoTDB is a database for managing large amount of time series data with
> > columnar storage, data encoding, pre-computation, and index techniques.
> It
> > has SQL-like interface to write millions of data points per second per
> node
> > and is optimized to get query results in few seconds over trillions of
> data
> > points. It can also be easily integrated with Apache Hadoop MapReduce and
> > Apache Spark for analytics.
> > >
> > > == Background ==
> > >
> > > A new class of data management system requirements is becoming
> > increasingly important with the rise of the Internet of Things. There are
> > some database systems and technologies aimed at time series data
> > management.  For example, Gorilla and InfluxDB which are mainly built for
> > data centers and monitoring application metrics. Other systems, for
> > example, OpenTSDB and KairosDB, are built on Apache HBase and Apache
> > Cassandra, respectively.
> > >
> > > However, many applications for time series data management have more
> > requirements especially in industrial applications as follows:
> > >
> > >  * Supporting time series data which has high data frequency. For
> > example, a turbine engine may generate 1000 points per second (i.e.,
> > 1000Hz), while each CPU only reports 1 data points per 5 seconds in a
> data
> > center monitoring application.
> > >
> > >  * Supporting scanning data multi-resolutionally. For example,
> > aggregation operation is important for time series data.
> > >
> > >  * Supporting special queries for time series, such as pattern
> matching,
> > time series segmentation, time-frequency transformation and frequency
> query.
> > >
> > >  * Supporting a large number of monitoring targets (i.e. time series).
> > An excavator may report more than 1000 time series, for example,
> revolving
> > speed of the motor-engine, the speed of the excavator, the accelerated
> > speed, the temperature of the water tank and so on, while a CPU or an
> > application monitor has much fewer time series.
> > >
> > >  * Optimization for out-of-order data points. In the industrial sector,
> > it is common that equipment sends data using the UDP protocol rather than
> > the TCP protocol. Sometimes, the network connect is unstable and parts of
> > the data will be buffered for later sending.
> > >
> > >  * Supporting long-term storage. Historical data is precious for
> > equipment manufacturers. Therefore, removing or unloading historical data
> > is highly desired for most industrial applications. The database system
> > must not only support fast retrieval of historical data, but also should
> > guarantee that the historical data does not impact the processing speed
> for
> > “hot” or current data.
> > >
> > >  * Supporting online transaction processing (OLTP) as well as complex
> > analytics. It is obvious that supporting analyzing from the data files
> > using Apache Spark/Apache Hadoop MapReduce directly is better than
> > transforming data files to another file format for Big Data analytics.
> > >
> > >  * Flexible deployment either on premise or in the cloud.  IoTDB is as
> > simple and can be deployed on a Raspberry Pi handling hundreds of time
> > series. Meanwhile, the system can be also deployed in the cloud so that
> it
> > supports tens of millions ingestions per second, OLTP queries in
> > milliseconds, and analytics using Apache Spark/Apache Hadoop MapReduce.
> > >
> > >  * * (1) If users deploy IoTDB on a device, such as a Raspberry Pi, a
> > wind turbine, or a meteorological station, the deployment of the chosen
> > database is designed to be simple. A device may have hundreds of time
> > series (but less than a thousand time series) and the database needs to
> > handle them.
> > >  * * (2) When deploying IoTDB in a data center, the 

Re: Graduation Resolutions Should Not Include Project Bylaws Clause

[Joe Witt]

John,

The clause as written right now doesn't speak to the ASF level bylaws.
It gives the PMC the specific tasking to create bylaws.  If not
removed the language should probably change to not encourage creation
of new bylaws but rather understand the implicit adoption of the ASF
level bylaws.

Thanks
On Sun, Sep 2, 2018 at 5:25 PM John D. Ament  wrote:
>
> -private list for now.
>
>
> I disagree with removing the bylaws clause.  It's assumed your going to use
> the ASF level bylaws if you don't have another one.
>
> On Sun, Sep 2, 2018, 14:29 Dave Fisher  wrote:
>
> > Note the cross-posting between public and private mailing lists.
> >
> > Sent from my iPhone
> >
> > > On Sep 2, 2018, at 11:22 AM, Kevin A. McGrail 
> > wrote:
> > >
> > > Good point, Dave.  +board as this was an issue with emeritus pmc and
> > > project bylaws
> > >
> > >> On Sun, Sep 2, 2018, 12:37 Dave Fisher  wrote:
> > >>
> > >> Hi -
> > >>
> > >> Pulsar is currently discussing a graduation proposal and Taylor noticed
> > >> the following that came out of the whimsy boilerplate.
> > >>
> > >> Quick question:
> > >>
> > >> RESOLVED, that the initial Apache Pulsar PMC be and hereby is tasked
> > >> with the creation of a set of bylaws intended to encourage open
> > >> development and increased participation in the Apache Pulsar Project;
> > >> and be it further
> > >>
> > >>
> > >> Does the Pulsar PPMC feel the need to adopt bylaws (it’s not required),
> > or
> > >> are the Apache defaults acceptable?
> > >>
> > >> One option is to simply not have bylaws, which means you would simply
> > >> adhere to [1] and [2], and put any clarifications in a contributors’
> > guide
> > >> (which you’ve done).
> > >>
> > >> -Taylor
> > >>
> > >> [1] http://www.apache.org/foundation/voting.html
> > >> [2] http://www.apache.org/dev/pmc.html
> > >>
> > >>
> > >> I think that this clause needs to be removed from the template.
> > >>
> > >> Regards,
> > >> Dave
> > >>
> > >>
> >
> >
> > -
> > 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

Re: [VOTE] Release of Apache Tephra-0.14.0-incubating [rc1]

[Joe Witt]

+1 (binding)

Verified source bundle signature and hashes and disclaimer.
Verified build and distribution artifact (no live testing).

Tephra release vote findings/improvements for consideration:
1) Use of md5 hashes worth removing in future releases
2) Copyright year in source and binary notice
3) I dont believe category B (for example the EPL dependencies in
binary license) dependencies belong in the license (binary or
otherwise).  https://www.apache.org/legal/resolved.html#category-b
  It is my understanding those would be reflected in the notice.
4) There are a number of binary dependencies in the lib folder of the
tephra distribution artifact that are not called out in the
license/notice. These include ASF projects.  Should review these for
inclusion. The ASF projects might not need a mention but they often
have NOTICE files and those usually need to be carried forward as well
- ASF projects also have copyrights that might need to be carried over
as well. Commons lang has an interesting line worth considering for
inclusion https://github.com/apache/commons-lang/blob/master/NOTICE.txt

On Tue, May 22, 2018 at 2:01 AM, Jitendra Pandey
 wrote:
> +1 (binding)
> Verified md5 of the source tarball.
> Downloaded source, built successfully, ran a few unit tests.
>
> On 5/21/18, 9:02 PM, "Josh Elser"  wrote:
>
> +1 (binding)
>
> Things look good for the most part, a few things I noticed which can be
> fixed next release:
>
> * NOTICE needs an updated copyright year
> * `mvn apache-rat:check` fails on the below files
>
> 
> apache-tephra-0.14.0-incubating/tephra-distribution/licenses/Aopa.PL
> apache-tephra-0.14.0-incubating/tephra-distribution/licenses/Asm.BSD
> apache-tephra-0.14.0-incubating/tephra-distribution/licenses/JLine.BSD
> apache-tephra-0.14.0-incubating/tephra-distribution/licenses/Logback.EPL
> apache-tephra-0.14.0-incubating/tephra-distribution/NOTICE_BINARY
> 
>
> On 5/21/18 6:51 PM, James Taylor wrote:
> > Hi all,
> >
> > This is a call for a vote on releasing Apache Tephra 0.14.0-incubating,
> > release candidate 1. This is the seventh release of Tephra. The Tephra 
> dev
> > community has voted on and approved a proposal to release Tephra
> > 0.14.0-incubating, release candidate 1.
> >
> > PPMC Vote Call: https://s.apache.org/jWVD
> >
> > PPMC Vote Result: https://s.apache.org/zwog
> >
> > The source tarball, including signatures, digests, etc. can be found at:
> > 
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.14.0-incubating-rc1/src
> >
> > The tag to be voted upon is v0.14.0-incubating:
> > 
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=shortlog;h=refs/tags/v0.14.0-incubating
> >
> > The release hash is e93942adae0ece286157a8f6a2e5c63b53669e03:
> > 
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=e93942adae0ece286157a8f6a2e5c63b53669e03
> >
> > The Nexus Staging URL:
> > https://repository.apache.org/content/repositories/orgapachetephra-1011
> >
> > Release artifacts are signed with the following key:
> > http://people.apache.org/keys/committer/jamestaylor
> >
> > KEYS file available:
> > https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
> >
> > For information about the contents of this release, see:
> > 
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.14.0-incubating-rc1/CHANGES.txt
> >
> > Please vote on releasing this package as Apache Tephra 0.14.0-incubating
> >
> > The vote will be open for 72 hours.
> >
> > [ ] +1 Release this package as Apache Tephra 0.14.0-incubating
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because ...
> >
> > Thanks,
> > James
> >
>
> -
> 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

Re: [VOTE] Superset Proposal for Apache Incubator

[Joe Witt]

+1 (binding)

On Tue, Apr 25, 2017 at 4:52 PM, Jitendra Pandey
 wrote:
> +1 (binding)
>
> On 4/25/17, 1:27 PM, "Julian Hyde"  wrote:
>
> +1 binding
>
> > On Apr 25, 2017, at 12:48 PM, moon soo Lee  wrote:
> >
> > +1 (non-binding)
> >
> > On Tue, Apr 25, 2017 at 11:49 AM Ashutosh Chauhan 
> > wrote:
> >
> >> +1 (binding)
> >>
> >> Thanks,
> >> Ashutosh
> >>
> >> On Mon, Apr 24, 2017 at 5:45 AM, Luke Han  wrote:
> >>
> >>> +1 binding
> >>>
> >>> Love to see Superset to be new incubator project.
> >>>
> >>>
> >>> Best Regards!
> >>> -
> >>>
> >>> Luke Han
> >>>
> >>> On Sun, Apr 23, 2017 at 10:53 PM, Jeff Feng  
> wrote:
> >>>
>  Dear Apache Incubator Community,
> 
>  We have updated the Superset proposal
>   (copied below) 
> for
> 
>  Apache Incubation with an additional mentor (Luke Han -
>  luke@apache.org),
>  and would like to start a vote thread for acceptance into the 
> incubator.
> 
>  Our team is excited to share Superset with the Apache community and 
> we
>  hope
>  for the your continued support!
> 
>  Cheers,
>  Jeff & the Superset Team
> 
> 
> 
> 
>  = Superset =
> 
>  == Abstract ==
>  Superset is an enterprise-ready web application for data exploration,
> >> data
>  visualization and dashboarding.
> 
>  == Proposal ==
>  Superset is business intelligence (BI) software that helps modern
>  organizations visualize and interact with their data. Superset 
> enables
>  users explore data from a variety of databases, assemble beautiful
>  dashboards and share their findings.  Superset works neatly with all
>  modern
>  SQL-speaking databases, and integrates with Druid.io to provide
> >> real-time,
>  interactive, blazing fast data access to large datasets.
> 
>  == Background ==
>  Data is mission critical. To succeed in this era, organizations need 
> to
>  provide low-friction, intuitive and interactive access to data. It is
>  paramount for knowledge workers to be capable of answering their own
>  questions by querying, exploring and visualizing data.
> 
>  The entire business intelligence industry has pivoted from a model of
>  centralized top-down platforms driven by IT organizations to
> >> self-service
>  analytics and agile workflows by any user.  This shift unblocks
>  centralized
>  service bottlenecks for creating data visualizations while also 
> creating
>  an
>  environment that is iterative and fast-moving.  This means that 
> business
>  intelligence software must also be easy and delightful to use.
>  Self-service analytics doesn’t mean that admin and governance 
> features
> >> are
>  not needed.
>  Modern BI tools provide fine-grain access controls and auditing
>  capabilities to understand how data is being used.  Superset is a
> >> solution
>  that delivers on all of these vectors.
> 
>  The technology stack is also constantly morphing - vendors are
> >> struggling
>  to provide cheap, quick and easy solutions to access data.  Business
>  intelligence users are finding existing solutions lacking as these
>  software
>  products either disregard or react slowly to recent game-changing
>  technologies like Druid.io, PrestoDB, Apache Drill, Apache Kylin, 
> d3.js,
>  React.js and iPython’s Jupyter for instance.
> 
>  == Rationale ==
>  Business intelligence is more relevant today than at any other point 
> in
>  history.  Organizations are currently very limited in options for 
> open
>  source data visualization solutions, especially solutions that are 
> both
>  self-service and enterprise-ready.  Every company informing their
>  decisions
>  with data needs a BI tool.
> 
>  We believe that Superset will be a strong compliment to existing 
> Apache
>  Software Foundation technologies by offering scalable user 
> interactions
> >> to
>  distributed storage and computation solutions.  Users will often find
> >> that
>  Superset can act as a catalyst for tooling that can visualize the
>  byproduct
>  of data and computation infrastructure.
> 
>  Superset has many key design elements that help fill a gap in current
>  solutions 

Re: [VOTE] Retire the Pirk podling

[Joe Witt]

+1 (binding)

On Apr 13, 2017 11:25 PM, "Josh Elser"  wrote:

> Folks,
>
> The Pirk PPMC have recently voted unanimously to retire the podling.
> This decision, while heavy-hearted, comes on the tails of months of no
> development with no change on the horizon.
>
> Context for those interesting in reading: DISCUSS [1], VOTE [2], RESULT
> [3].
>
> [ ] +1: Retire Pirk
> [ ] -1: Do not retire Pirk because
>
> Here's my +1 (binding)
>
> - Josh
>
> [1] https://lists.apache.org/thread.html/c0a2bcc6271d71efb60c688ad83c4c
> 3e1aeffb8851e01f675135b0c5@%3Cdev.pirk.apache.org%3E
> [2] https://lists.apache.org/thread.html/447f04840531c439250ca6b05e3592
> ea3159d2e982b5bb75320ec427@%3Cdev.pirk.apache.org%3E
> [3] https://lists.apache.org/thread.html/ef4699debd5fe0441e94c8f68e40e6
> 3d8a20d249a241bb50cf5341a6@%3Cdev.pirk.apache.org%3E
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Apache Metron - licensing question

[Joe Witt]

Jon,

It is always best to get definitive legal guidance from legal discuss.

This case is only complicated in that it sounds like the author
originally created the code in the metron codebase under ASLv2.  Then
copied it to another location under BSD 3-Clause.  Then each copy
evolved a little.  Now you want to merge them.  Ultimately it sounds
workable since we're talking about two Cat-A licenses compatible as
source or binary dependencies.

Thanks
Joe

On Thu, Apr 13, 2017 at 8:27 AM, zeo...@gmail.com <zeo...@gmail.com> wrote:
> Hi Josh,
>
> Can you specify which message you're referring to?  I did get some feedback
> on the Metron dev mailing list from a mentor and from a PMC member, I get
> the feeling that nobody else in the community is comfortable answering this
> sort of question.  Should I perhaps ask this to the legal-discuss mailing
> list?  Happy to do whatever is necessary to bring this to resolution.
> Thanks,
>
> Jon
>
> On Tue, Apr 11, 2017 at 11:58 AM Josh Elser <els...@apache.org> wrote:
>
>> Also, it may be worth mentioning: Metron is on its way out of the Apache
>> Incubator. A vote has recently passed at the Incubator level for their
>> graduation. It is likely that after the next ASF board meeting, Metron
>> will no longer be a podling.
>>
>> I am worried that you did not receive a response from the community on a
>> previous message. They should be more than capable to answer your
>> questions in the future. I'd suggest you re-ping them if your questions
>> go unanswered in the future.
>>
>> zeo...@gmail.com wrote:
>> > Ok great, thank you for your feedback.  I did a bit more searching
>> because
>> > that timeline didn't seem right and found that the original
>> > bro-kafka-plugin code[1] first appeared in the Metron repo on February 8,
>> > 2016.  My apologies for not properly linking this in my first email, I
>> > hadn't realized it was moved.
>> >
>> > 1:
>> >
>> https://github.com/apache/incubator-metron/commit/bc140a571a78c428e9ae5a3315c427724183782f
>> >
>> > Much appreciated,
>> >
>> > Jon
>> >
>> > On Mon, Apr 10, 2017, 11:33 PM Joe Witt<joe.w...@gmail.com>  wrote:
>> >
>> >> Jon,
>> >>
>> >> It appears that the code at [1] was initially committed on Mar 8,
>> >> 2016.  The code in Apache Metron [2] was committed on April 13, 2016.
>> >>
>> >> The code in Metron [2] appears heavily derived from the code in the
>> >> initial repository [1].
>> >>
>> >> In the Metron repository that code has an ASL v2 license and the
>> >> Apache license headers.  That, to me, is where the error occurred.
>> >>
>> >> When the code was copied over, even if it was the original author
>> >> doing it, the original license from [1] should be retained/honored and
>> >> this is very easy to do.  You would simply ensure your source release
>> >> LICENSE indicates the use of the BSD source.  You would still be free
>> >> to alter that source code you've pulled into the Metron codebase and
>> >> build around it as you need. Obviously there are maintenance
>> >> challenges and tradeoffs to consider but the licensing part can be
>> >> pretty clear straightforward other than the question of "how much do I
>> >> have to change the original before it would be appropriate to slap the
>> >> apache license header on a given source file"?
>> >>
>> >> Anyway, I'm not an expert and my advice/interpretation could be wildly
>> >> inaccurate but this looks like it might have an easy solution so
>> >> hopefully that helps.
>> >>
>> >> [1] https://github.com/bro/bro-plugins/tree/master/kafka
>> >> [2]
>> >>
>> https://github.com/apache/incubator-metron/tree/master/metron-sensors/bro-plugin-kafka
>> >>
>> >> Thanks
>> >> Joe
>> >>
>> >> On Mon, Apr 10, 2017 at 8:46 PM, zeo...@gmail.com<zeo...@gmail.com>
>> >> wrote:
>> >>> Hi all,
>> >>>
>> >>>
>> >>> I recently asked a licensing question to our dev mailing list.  I did
>> get
>> >>> feedback
>> >>> <
>> >>
>> https://lists.apache.org/thread.html/a4e2e7bb7fb7497033696645b011c5604790f23f3802aaab32f1bd01@%3Cdev.metron.apache.org%3E
>> >>> from one of our mentors, but he also requested that we get a double
>> >> check.
>> >

Re: Apache Metron - licensing question

[Joe Witt]

Jon,

It appears that the code at [1] was initially committed on Mar 8,
2016.  The code in Apache Metron [2] was committed on April 13, 2016.

The code in Metron [2] appears heavily derived from the code in the
initial repository [1].

In the Metron repository that code has an ASL v2 license and the
Apache license headers.  That, to me, is where the error occurred.

When the code was copied over, even if it was the original author
doing it, the original license from [1] should be retained/honored and
this is very easy to do.  You would simply ensure your source release
LICENSE indicates the use of the BSD source.  You would still be free
to alter that source code you've pulled into the Metron codebase and
build around it as you need. Obviously there are maintenance
challenges and tradeoffs to consider but the licensing part can be
pretty clear straightforward other than the question of "how much do I
have to change the original before it would be appropriate to slap the
apache license header on a given source file"?

Anyway, I'm not an expert and my advice/interpretation could be wildly
inaccurate but this looks like it might have an easy solution so
hopefully that helps.

[1] https://github.com/bro/bro-plugins/tree/master/kafka
[2] 
https://github.com/apache/incubator-metron/tree/master/metron-sensors/bro-plugin-kafka

Thanks
Joe

On Mon, Apr 10, 2017 at 8:46 PM, zeo...@gmail.com  wrote:
> Hi all,
>
>
> I recently asked a licensing question to our dev mailing list.  I did get
> feedback
> 
> from one of our mentors, but he also requested that we get a double check.
> Please see below for a bit of background and my questions.  Thanks!
>
>
> *Background*
>
> We have a situation where a portion of code
> 
> was created for Apache Metron (incubating), which is a plugin for a
> separate open source project, bro .  The code was
> later pushed out by the initial author to the bro community under the
> 3-Clause BSD license
> , and
> some important
> enhancements
> 
> have been made to the plugin in that separate community, which we would
> like to include in our code, while merging with some recent changes
> 
> that have been made in the Metron code base as well (i.e. we are not simply
> pulling the code down from the external project).  This was discussed
> recently
> 
> on the Metron dev mailing list, and we wanted to get some clarification
> before moving forward.
>
>
> *Questions*
>
> 1. Is it valid to assume that, as Casey mentioned
> ,
> these are two separate plugins and we can simply make modifications to our
> code base to resolve the current multithreading issue?
>
> 2. If we do 1, will this require a line in our LICENSE file as a derivative
> work, or anything else?
>
>
> Thanks,
>
> Jon
> --
>
> Jon

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Apache Metron podling Graduation

[Joe Witt]

+1 (binding)

On Wed, Mar 29, 2017 at 3:40 PM, Dave Fisher  wrote:
> +1 (binding)
>
>> On Mar 29, 2017, at 10:22 AM, Josh Elser  wrote:
>>
>> +1 (binding)
>>
>> Casey Stella wrote:
>>> Hi Everyone,
>>>
>>> I propose that we graduate Apache Metron (incubating) from the incubator.
>>> The full text of the proposal is below, with requisite modifications
>>> applied from the discussion thread.
>>>
>>> The discuss thread can be found at
>>> https://lists.apache.org/thread.html/e5d106456b28562bdc947624c6f33e3281297dfd3803aab3d171bbad@%3Cgeneral.incubator.apache.org%3E
>>>
>>>
>>> Best,
>>>
>>> Casey
>>>
>>> Resolution:
>>>
>>> Establish the Apache Metron Project
>>>
>>> WHEREAS, the Board of Directors deems it to be in the best
>>> interests of the Foundation and consistent with the
>>> Foundation's purpose to establish a Project Management
>>> Committee charged with the creation and maintenance of
>>> open-source software, for distribution at no charge to the
>>> public, related to a security analytics platform for big data use cases.
>>>
>>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>>> Committee (PMC), to be known as the "Apache Metron Project",
>>> be and hereby is established pursuant to Bylaws of the
>>> Foundation; and be it further
>>>
>>> RESOLVED, that the Apache Metron Project be and hereby is
>>> responsible for the creation and maintenance of software
>>> related to:
>>> (a) A mechanism to capture, store, and normalize any type of security
>>> telemetry at extremely high rates.
>>> (b) Real time processing and application of enrichments
>>> (c) Efficient information storage
>>> (d) An interface that gives a security investigator a centralized view
>>> of data and alerts passed through the system.
>>>
>>> RESOLVED, that the office of "Vice President, Apache Metron" be
>>> and hereby is created, the person holding such office to
>>> serve at the direction of the Board of Directors as the chair
>>> of the Apache Metron Project, and to have primary responsibility
>>> for management of the projects within the scope of
>>> responsibility of the Apache Metron Project; and be it further
>>>
>>> RESOLVED, that the persons listed immediately below be and
>>> hereby are appointed to serve as the initial members of the
>>> Apache Metron Project:
>>>
>>>
>>> PPMC by Affiliation:
>>>
>>> Hortonworks:
>>>   Sheetal Dolas (sheetal_dolas)
>>>   Ryan Merriman (rmerriman)
>>>   Larry McCay (lmccay)
>>>   P. Taylor Goetz (ptgoetz)
>>>   Nick Allen (nickallen)
>>>   David Lyle (lyle)
>>>   George Vetticaden (gvetticaden)
>>>   James Sirota (jsirota)
>>>   Casey Stella (cstella)
>>>   Michael Perez (mperez)
>>>   Kiran Komaravolu (kirankom)
>>>   Vinod Kumar Vavilapalli (vinodkv)
>>>
>>> Cisco:
>>>   Debo Dutta (ddutta)
>>>   Discovery Gerdes (discovery)
>>>
>>> Rackspace:
>>>   Oskar Zabik (smogg)
>>>   Andrew Hartnett (dev_warlord)
>>>   Paul Kehrer (reaperhulk)
>>>   Sean Schulte (sirsean)
>>>
>>> B23:
>>>   Mark Bittmann (mbittmann)
>>>   Dave Hirko (dbhirko)
>>>   Brad Kolarov (bjkolly)
>>>
>>> Mantech:
>>>   Charles Porter (cporter)
>>>   Ray Urciuoli (rurcioli)
>>>
>>> Fogbeam Labs:
>>>   Phillip Rhodes (prhodes)
>>>
>>>
>>>
>>>
>>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Casey Stella
>>> be appointed to the office of Vice President, Apache Metron, to
>>> serve in accordance with and subject to the direction of the
>>> Board of Directors and the Bylaws of the Foundation until
>>> death, resignation, retirement, removal or disqualification,
>>> or until a successor is appointed; and be it further
>>>
>>> RESOLVED, that the initial Apache Metron PMC be and hereby is
>>> tasked with the creation of a set of bylaws intended to
>>> encourage open development and increased participation in the
>>> Apache Metron Project; and be it further
>>>
>>> RESOLVED, that the Apache Metron Project be and hereby
>>> is tasked with the migration and rationalization of the Apache
>>> Incubator Metron podling; and be it further
>>>
>>> RESOLVED, that all responsibilities pertaining to the Apache
>>> Incubator Metron podling encumbered upon the Apache Incubator
>>> Project are hereafter discharged.
>>>
>>
>> -
>> 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
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Graduate Apache Ranger Project from the Incubator - Resending with additional mail distro

[Joe Witt]

+1 binding

On Jan 7, 2017 2:20 PM, "Edward Zhang"  wrote:

> +1
> Glad to see Range will graduate!
>
> Thanks
> Edward
>
> On Sat, Jan 7, 2017 at 9:26 AM, Drew Farris  wrote:
>
> > +1 (binding)
> >
> > On Sat, Jan 7, 2017 at 12:56 AM Niclas Hedhman 
> wrote:
> >
> > > +1 (binding)
> > >
> > > On Sat, Jan 7, 2017 at 6:29 AM, Owen O'Malley 
> > wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > On Wed, Jan 4, 2017 at 5:15 PM, Balaji Ganesan <
> > > balaji.ganesa...@gmail.com
> > > > >
> > > > wrote:
> > > >
> > > > > +1 Great to see the progress from the Ranger community.
> > > > >
> > > > > On Wed, Jan 4, 2017 at 4:54 PM, Suneel Marthi 
> > > > wrote:
> > > > >
> > > > > > +1 binding
> > > > > >
> > > > > > On Wed, Jan 4, 2017 at 5:48 PM, Ramesh Mani <
> rm...@hortonworks.com
> > >
> > > > > wrote:
> > > > > >
> > > > > > > Dear Incubator members,
> > > > > > >
> > > > > > > Apache Ranger Project community has successfully released 0.6.2
> > > > version
> > > > > > > and with it there had been a lot of discussion within Apache
> > Ranger
> > > > > > > community to consider graduation to TLP. Apache Ranger entered
> > into
> > > > > > > incubation on 24th July 2014 and from this welcoming community
> > had
> > > > > done a
> > > > > > > tremendous job in resolving various technical hurdles like
> > > > refactoring
> > > > > > the
> > > > > > > project core model to  be service based, adding more Apache
> > Hadoop
> > > > > > > components like Apache YARN, Apache Storm, Apache Kafka, Apache
> > > Nifi,
> > > > > > > Apache Ranger KMS into Ranger Authorizing  model for security
> and
> > > > > making
> > > > > > it
> > > > > > > into a core product in the Apache Hadoop security space. PPMC
> has
> > > > > > exhibited
> > > > > > > a clear understanding of this growing apache community by
> > > electing  4
> > > > > > > individuals as committers  and  inculding 22 individuals as
> > > > > contributors
> > > > > > to
> > > > > > > the Apache Ranger project. PPMC also has done 8 successful
> > releases
> > > > > under
> > > > > > > the guidance of mentors demonstrating their mastery over AFS’s
> IP
> > > > > > policies.
> > > > > > >
> > > > > > > An voting was conducted within Apache Ranger Community to
> > graduate
> > > > > Apache
> > > > > > > Ranger Project to Top Level Project. Vote passed with 16 +1
> > votes ,
> > > > no
> > > > > 0
> > > > > > or
> > > > > > > –1 votes.
> > > > > > > http://mail-archives.apache.org/mod_mbox/incubator-ranger-
> > > > > > > dev/201612.mbox/%3CD479D4C8.11E4E%25rmani%40hortonworks.com%3E
> > > > > > >
> > > > > > > Apache Ranger Project has shown a great perspective to become a
> > > true
> > > > > TLP.
> > > > > > > Following summary on the project reflects its accomplishment.
> > > > > > >
> > > > > > > Please vote on the Project resolution that is found in bottom
> to
> > > > > graduate
> > > > > > > Apache Ranger Project from Incubator to Top Level Project.
> > > > > > >
> > > > > > > [ ] +1 Graduate Apache Ranger from the Incubator.
> > > > > > > [ ] +0 No opinion
> > > > > > > [ ] -1 Don't graduate Apache Ranger from the Incubator ( please
> > > > provide
> > > > > > > the reason)
> > > > > > >
> > > > > > > This VOTE will be opened for next 72 hours.
> > > > > > >
> > > > > > > Thanks all Mentors and Apache Ranger Project members for their
> > > > support
> > > > > > and
> > > > > > > contributions.
> > > > > > >
> > > > > > > Here is my vote +1 (binding)
> > > > > > >
> > > > > > > Project Summary:
> > > > > > > =
> > > > > > >
> > > > > > > http://incubator.apache.org/projects/ranger.html
> > > > > > >
> > > > > > > Project website:
> > > > > > > =
> > > > > > >
> > > > > > > http://ranger.incubator.apache.org > > > incubator.apache.org/
> > > > > >
> > > > > > >
> > > > > > > Project Documentation:
> > > > > > > ===
> > > > > > >
> > > > > > > http://ranger.incubator.apache.org/index.html
> > > > > > > http://ranger.incubator.apache.org/quick_start_guide.html
> > > > > > > https://cwiki.apache.org/confluence/display/RANGER/
> > Release+Folders
> > > > > > >
> > > > > > > Project maturity Assessment:
> > > > > > > ===
> > > > > > >
> > > > > > > https://cwiki.apache.org/confluence/display/RANGER/
> > > > > > > Apache+Ranger+Project+Ma
> > > > > > > turity+Model
> > > > > > >
> > > > > > > Proposed PMC size: 17
> > > > > > >
> > > > > > > Total number of committers   : 14 members
> > > > > > > Total number of contributors : 22 members
> > > > > > >
> > > > > > > PMC affiliation (* indicated chair)
> > > > > > >
> > > > > > > * Hortonworks (9)
> > > > > > >Privacera (2)
> > > > > > >BlueTalon (1)
> > > > > > >Others(1)
> > > > > > >
> > > > > > > 1802 commits on develop
> > > > > > > 22 contributors across all branches
> > > > > > > Dev list averaged ~50 msgs/month in 2016
> > > 

Re: [VOTE] Release Apache Ranger 0.6.0 (incubating) - rc1

[Joe Witt]

+1 (binding)

Review focused on the source release mechanics specifically around
build/licensing.

Signature checks out w/SHA512
Hashes all check out
Verified last meaningful commit in specific tag found in source.
Full clean build as per instructions found in readme worked perfectly.

Commentary:
[Minor - for next release - might not be true]
In source LICENSE.  "This product includes json2.js
(https://github.com/douglascrockford/JSON-js - Public Domain license)
by Douglas Crockford".  Should be in notice.  This doesn't alter the
LICENSE but is worth referencing in the NOTICE as per attribution
guidance in 
http://www.apache.org/legal/resolved.html#can-works-placed-in-the-public-domain-be-included-in-apache-products
which refers to http://www.apache.org/legal/resolved.html#category-a

[Minor - for next release - might not be true]
In source LICENSE.  "This product includes Font Awesome 3.2.1
(http://fontawesome.io/ - SIL Open Font License (OFL) licensee) by
Dave Gandy"
This should be in the NOTICE and not LICENSE.  Such a dependency
(Category B) should only be a binary dependency unless in source
release it meets this exception "small amounts of source that is
directly consumed by the ASF product at runtime in source form, and
for which that source is unmodified and unlikely to be changed anyway
(say, by virtue of being specified by a standard), inclusion of
appropriately labeled source is also permitted" as stated in
http://www.apache.org/legal/resolved.html#category-b

[Minor - for next release]
In source license several references are made to ASL V2 items.  These
references belong in NOTICE and only if there is information worth
carrying forward.  The Copyright is good to include so those belong in
NOTICE.

[Minor - for next release]
In source LICENSE.  The 'visualsearch license' is referenced.  This
should say something like
  "This product bundles 'VisualSearch.js 0.4.0' which is available
under an MIT style license." then include license text w/copyright.
Or just put it up in the already present MIT license listing you have.

[Minor - for next release]
In source license.  The requires-handlebar-plugin.  As per text at
bottom of readme
(https://github.com/SlexAxton/require-handlebars-plugin)
  Nice job catching the 'handlebars.js' listing and putting under MIT
licenses (with proper copyright) and the 'require.js'.
  But, it appears the require.js listing under MIT licenses has
incorrect copyright.  It should be "Copyright (c) 2010-2012, The Dojo
Foundation All Rights Reserved." as found in
(./security-admin/target/security-admin-web-0.6.0/libs/bower/requirejs/js/require.js)
for example.


On Fri, Jul 15, 2016 at 1:05 AM, Velmurugan Periasamy  wrote:
> Incubator PMC:
>
> Apache Ranger community has voted on and approved a proposal to release 
> Apache Ranger 0.6.0 (incubating).
>
> [VOTE RESULT] thread:
> 
> https://lists.apache.org/thread.html/c21a99659362bcd2fef0119d9937b9ab245c99400902cf75a7e77910@%3Cdev.ranger.apache.org%3E
>
> Apache ranger-0.6.0-rc1 release candidate is now available with the following 
> artifacts up for IPMC vote. I kindly request that the Incubator PMC members 
> review and vote on this incubator release.
>
> Git tag for the release:
> https://github.com/apache/incubator-ranger/tree/ranger-0.6.0-rc1
> Sources for the release:
> 
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.6.0-incubating-rc1/apache-ranger-incubating-0.6.0.tar.gz
> Source release verification:
> PGP Signature:
> 
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.6.0-incubating-rc1/apache-ranger-incubating-0.6.0.tar.gz.asc
> MD5/SHA  Hash:
> 
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.6.0-incubating-rc1/apache-ranger-incubating-0.6.0.tar.gz.mds
> Keys to verify the signature of the release artifact are available at:
> https://dist.apache.org/repos/dist/release/incubator/ranger/KEYS
>
> Release Notes:
> https://cwiki.apache.org/confluence/display/RANGER/0.6.0+Release+Notes
> Build verification steps can be found at:
> http://ranger.incubator.apache.org/quick_start_guide.html
>
> The vote will be open for at least 72 hours or until necessary number of 
> votes are reached.
> [ ] +1  approve
> [ ] +0  no opinion
> [ ] -1  disapprove (and reason why)
>
> Here is my +1 (non binding).
>
> Thank you,
> Vel

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Atlas version 0.7-incubating RC2

[Joe Witt]

+1 (bindng).

Conducted a review focused largely on mechanics of the source release
and licensing.  Findings as follows:

good
- hashes check out
- signature checks out
- source release license/notice/3party license references look great!
nicely done
- full clean build w/out tests + apache-rat:check passes.  As a
caution might want to reconsider how broad rat exclusions are for
things like txt/json files.  Can be easy to miss things which should
have headers.

things to address in upcoming release
- full clean build w/tests results in tests failures (already
identified).  Recommend getting all tests passing on supported
platforms.  I was on Java8/OSX which seems to be supported.
- checkstyle results reveal that style checks are quite optional.
Recommend getting to a good stable state with checkstyle so others can
help keep good hygiene going forward.
- following the build instructions on the wiki i was unable to create
the convenience binary tar.gz.  Perhaps the instructions need
updating.  Ideally the readme of the source release would describe the
current build process as well.  My interest there was to look through
any resulting convenience binaries to help with licensing/notice
considerations there too.

things which lead toward a negative release vote
- N/A

On Fri, Jul 8, 2016 at 2:52 PM, Arun C Murthy  wrote:
> +1 (binding)
>
> Arun
>
> On Fri, Jul 8, 2016 at 2:00 PM, Alan Gates  wrote:
>
>> +1.
>>
>> I checked the LICENSE, DISCLAIMER, and NOTICE files.  Checked that there
>> were no binary files in the distribution (there are images, but that seems
>> ok).  Checked the signatures.  Did a build with a fresh local maven repo
>> with -DskipTests set.
>>
>> When I built with tests it failed with:
>> Running org.apache.atlas.TestUtils
>> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.171 sec
>> - in org.apache.atlas.TestUtils
>>
>> Results :
>>
>> Failed tests:
>>   StoreBackedTypeCacheTest.testGetTraitType:146 expected: but
>> was:
>>   StoreBackedTypeCacheTest.testHasTraitType:164 expected: but
>> was:
>>
>> Tests run: 452, Failures: 2, Errors: 0, Skipped: 0
>>
>> This isn’t enough to scuttle the release, though it’s nice when tests
>> pass.  I’m building on a Mac with JDK 1.8.
>>
>> Alan.
>>
>> > On Jul 6, 2016, at 00:09, Hemanth Yamijala  wrote:
>> >
>> > Hi all,
>> >
>> > This is a call for a vote on the Apache Atlas 0.7-incubating release
>> > (release candidate RC2).
>> >
>> > A vote was held on developer mailing list and it passed with 7 +1s.
>> >
>> > Vote thread: https://s.apache.org/Czm4
>> > Results thread: https://s.apache.org/PAeO
>> >
>> > The source tarball (*.tar.gz), signature (*.asc), checksum (*.md5,
>> *.sha512):
>> >
>> https://dist.apache.org/repos/dist/dev/incubator/atlas/0.7.0-incubating-rc2/
>> >
>> > The SHA512 checksum of the archive is
>> > 8B923CEA 2CDD32C8 7CE9A066 38002BFA 14F666DC C56F95AF 2805D5C1 08B58F9E
>> 436E3E3C
>> > 61B40908 474C67E7 782E720E 1BFA3678 B8099EBC 282F64C2 C16A48C4
>> >
>> > The commit id (15748e7bc5ed019a63326f201258e3a55d512d96) to be voted
>> upon:
>> >
>> https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=commit;h=15748e7bc5ed019a63326f201258e3a55d512d96
>> >
>> > The tag to be voted upon:
>> >
>> https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=log;h=refs/tags/release-0.7-rc2
>> >
>> > The list of fixed issues:
>> >
>> https://git-wip-us.apache.org/repos/asf?p=incubator-atlas.git;a=blob;f=release-log.txt;hb=refs/heads/0.7-incubating
>> >
>> > Keys to verify the signature of the release artifact are available at:
>> > http://www.apache.org/dist/incubator/atlas/KEYS
>> > PGP release keys:
>> > http://pgp.mit.edu/pks/lookup?op=vindex=0xA0E6F9F5D96BF0FD
>> >
>> > Note that this is a source only release and we are voting on the
>> > source release-0.7-incubating-rc2.
>> >
>> > Please download, test, and try it out.
>> >
>> > Vote will be open for at least 72 hours till 9th July, 2016 1 AM Pacific
>> time.
>> >
>> > [ ] +1 approve
>> > [ ] +0 no opinion
>> > [ ] -1 disapprove (and reason why)
>> >
>> > Thank you!
>> >
>> > Regards,
>> > Hemanth
>> >
>> > -
>> > 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
>>
>>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: IPMC release vote checklist

[Joe Witt]

Is this what you're looking for

   http://incubator.apache.org/guides/releasemanagement.html#check-list

On Fri, Jul 1, 2016 at 3:05 PM, Roman Shaposhnik  wrote:
> Hi!
>
> I remember we used to have a checklist of things published
> somewhere, but I can't find it anymore? What I'm talking about
> is something along the lines of:
>
> 
> signature and hashes good?
> DISCLAIMER is good?
> NOTICE is good?
> LICENSE is good?
> incubating in name?
> all source files have Apache headers?
> no unexpected binary files?
> can compile from source?
> can compile from source on a machine disconnected from the internet
>(provided all the dependencies are pre-installed from a published 
> manifest)?
> 
>
> Thanks,
> Roman.
>
> -
> 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

Re: [VOTE] Accept Pirk into the Apache Incubator

[Joe Witt]

can help us quickly come up to speed.
>
> Homogenous Developers
>
> The initial committers of Pirk come from a limited set of entities though
> we are committed to recruiting and developing additional committers from a
> broad spectrum of industries and backgrounds.
>
> Reliance on Salaried Developers
>
> We expect Pirk development to continue on salaried time and through
> volunteer time. The majority of 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.
>
> Relationship with other Apache Projects
>
> As described in the alignment section, Pirk is already heavily dependent on
> other ASF projects and we anticipate further dependence and integration
> with new and emerging projects in the Apache family.
>
> An Excessive Fascination with the Apache Brand
>
> We respect the Apache brand and desire to adopt its community building
> principles. Our desire is to build and foster an open source community
> around scalable, robust PIR which aligns with the Apache tenets. Further,
> Apache is a natural home for Pirk given our existing dependencies and
> alignment with ASF projects.
>
> Documentation
>
> At this time there is no Pirk documentation on the web. However, we have
> documentation included within the application that details usage. Using
> incubator infrastructure we will be rapidly expanding the available
> documentation to cover things like installation, developer guide,
> frequently asked questions, best practices, and more.
>
> Initial Source
>
> The core codebase is written in Java and includes detailed Javadocs and
> feature documentation.
>
> Source and Intellectual Property Submission
>
> The Pirk code and documentation materials will be submitted by the National
> Security Agency. Pirk has been developed by government employees. Material
> developed by the government employees is in the public domain and no U.S.
> copyright exists in works of the federal government. NSA has submitted
> Corporate Contributor License Agreement to the Apache Software Foundation;
> the Software Grant Agreement is forth coming.
>
> External Dependencies
>
> We believe all current dependencies are compatible with the ASF guidelines.
> Our dependency licenses come from the Apache v 2.0 and Eclipse Public v1.
>
> Cryptography
>
> Consistent with http://www.apache.org/licenses/exports/ we believe Pirk is
> classified as ECCN 5D002. 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.
>
> Required Resources
>
> Mailing Lists
>
> d...@pirk.incubator.apache.org
>
>     priv...@pirk.incubator.apache.org
>
> comm...@pirk.incubator.apache.org
>
> Source Control
>
> Pirk requests use of Git for source control (git://git.apache.org/pirk.git).
> We request a writeable Git repo for Pirk with mirroring to be setup to
> Github through INFRA.
>
> Issue Tracking
>
> JIRA Pirk (PIRK)
>
> Initial Committers
>
> Tracy Brown , CLA submitted
>
> Christopher Harris , CLA submitted
>
> Walter Ray-Dulaney , CLA submitted
>
> Jacob Wilder , CLA submitted
>
> Ellison Anne Williams , CLA confirmed
>
> Joe Witt , CLA confirmed
>
> Sponsors
>
> Champion
>
> Billie Rinaldi , IPMC Member
>
> Nominated Mentors
>
> Billie Rinaldi , IPMC Member
>
> Joe Witt , IPMC Member
>
> Josh Elser , IPMC Member
>
> Suneel Marthi , IPMC Member
>
> Tim Ellison , Apache Member
>
> Sponsoring Entity
>
> We request the Apache Incubator to sponsor this project.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Pirk Incubation Proposal

[Joe Witt]

evelopers are employed by the US Government. We will work
>> to grow the community among a more diverse set of developers and
>> industries.
>>
>> === Alignment ===
>>
>> Pirk was developed with an open source philosophy in mind and the Apache
>> way is consistent with the approach we have taken to date. Further, Pirk
>> depends on numerous ASF libraries and projects including Hadoop, Spark,
>> Commons, and Maven. We also anticipate extensions and dependencies with
>> several more ASF projects, including Accumulo, Avro, HBase, Storm, Kafka,
>> and others. This existing alignment with Apache and the desired community
>> makes the Apache Incubator a good fit for Pirk.
>>
>>
>> == Known Risks ==
>>
>> === Orphaned Products ===
>>
>> Risk of orphaning is limited though it is important to grow the community.
>> The project user and developer base is growing and there is already
>> operational use of Pirk.
>>
>> === Inexperience with Open Source ===
>>
>> The initial committers to Pirk have limited experience with true open
>> source software development. However, despite the project origins being
>> from closed source development we have modeled our behavior and community
>> development on The Apache Way to the greatest extent possible. We are
>> committed to the ideals of open source software and will eagerly seek out
>> mentors and sponsors who can help us quickly come up to speed.
>>
>> === Homogenous Developers ===
>>
>> The initial committers of Pirk come from a limited set of entities though
>> we are committed to recruiting and developing additional committers from a
>> broad spectrum of industries and backgrounds.
>>
>> === Reliance on Salaried Developers ===
>>
>> We expect Pirk development to continue on salaried time and through
>> volunteer time. The majority of 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.
>>
>> === Relationship with other Apache Projects ===
>>
>> As described in the alignment section, Pirk is already heavily dependent on
>> other ASF projects and we anticipate further dependence and integration
>> with new and emerging projects in the Apache family.
>>
>> === An Excessive Fascination with the Apache Brand ===
>>
>> We respect the Apache brand and desire to adopt its community building
>> principles. Our desire is to build and foster an open source community
>> around scalable, robust PIR  which aligns with the Apache tenets. Further,
>> Apache is a natural home for Pirk given our existing dependencies and
>> alignment with ASF projects.
>>
>> === Documentation ===
>>
>> At this time there is no Pirk documentation on the web. However, we have
>> documentation included within the application that details usage. Using
>> incubator infrastructure we will be rapidly expanding the available
>> documentation to cover things like installation, developer guide,
>> frequently asked questions, best practices, and more.
>>
>> == Initial Source ==
>>
>> The core codebase is written in Java and includes detailed Javadocs and
>> feature documentation.
>>
>> == Source and Intellectual Property Submission ==
>>
>> The Pirk code and documentation materials will be submitted by the National
>> Security Agency. Pirk has been developed by government employees. Material
>> developed by the government employees is in the public domain and no U.S.
>> copyright exists in works of the federal government. NSA has submitted
>> Corporate Contributor License Agreement to the Apache Software Foundation;
>> the Software Grant Agreement is forth coming.
>>
>> == External Dependencies ==
>>
>> We believe all current dependencies are compatible with the ASF guidelines.
>> Our dependency licenses come from the Apache v 2.0 and Eclipse Public v1.
>>
>> == Cryptography ==
>>
>> Consistent with http://www.apache.org/licenses/exports/ we believe Pirk is
>> classified as ECCN 5D002. 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.
>>
>> == Required Resources ==
>>
>> === Mailing Lists ===
>>
>>  * d...@pirk.incubator.apache.org <javascript:;>
>>  * priv...@pirk.incubator.apache.org <javascript:;>
>>  * comm...@pirk.incubator.apache.org <javascript:;>
>>
>> === Source Control ===
>>
>> Pirk requests use of Git for source control (git://git.apache.org/pirk.git
>> ).
>> We request a writeable Git repo for Pirk with mirroring to be setup to
>> Github through INFRA.
>>
>> === Issue Tracking ===
>>
>> JIRA Pirk (PIRK)
>>
>> === Initial Committers ===
>>
>>  * Tracy Brown , CLA submitted
>>  * Christopher Harris , CLA submitted
>>  * Walter Ray-Dulaney , CLA submitted
>>  * Jacob Wilder , CLA submitted
>>  * Ellison Anne Williams  , CLA confirmed
>>  * Joe Witt (Hortonworks) , CLA confirmed
>>
>> == Sponsors ==
>>
>> === Champion ===
>>
>>  * Billie Rinaldi (Hortonworks) , IPMC Member
>>
>> === Nominated Mentors ===
>>
>>  * Billie Rinaldi (Hortonworks) , IPMC Member
>>  * Joe Witt (Hortonworks) , IPMC Member
>>  * Josh Elser (Hortonworks) , IPMC Member
>>
>> === Sponsoring Entity ===
>>
>> We request the Apache Incubator to sponsor this project.
>>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Pirk Incubation Proposal

[Joe Witt]

 
> Maven. We also anticipate extensions and dependencies with several more ASF 
> projects, including Accumulo, Avro, HBase, Storm, Kafka, and others. This 
> existing alignment with Apache and the desired community makes the Apache 
> Incubator a good fit for Pirk.
>
>
> == Known Risks ==
>
> === Orphaned Products ===
>
> Risk of orphaning is limited though it is important to grow the community.
> The project user and developer base is growing and there is already 
> operational use of Pirk.
>
> === Inexperience with Open Source ===
>
> The initial committers to Pirk have limited experience with true open source 
> software development. However, despite the project origins being from closed 
> source development we have modeled our behavior and community development on 
> The Apache Way to the greatest extent possible. We are committed to the 
> ideals of open source software and will eagerly seek out mentors and sponsors 
> who can help us quickly come up to speed.
>
> === Homogenous Developers ===
>
> The initial committers of Pirk come from a limited set of entities though we 
> are committed to recruiting and developing additional committers from a broad 
> spectrum of industries and backgrounds.
>
> === Reliance on Salaried Developers ===
>
> We expect Pirk development to continue on salaried time and through volunteer 
> time. The majority of 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.
>
> === Relationship with other Apache Projects ===
>
> As described in the alignment section, Pirk is already heavily dependent on 
> other ASF projects and we anticipate further dependence and integration with 
> new and emerging projects in the Apache family.
>
> === An Excessive Fascination with the Apache Brand ===
>
> We respect the Apache brand and desire to adopt its community building 
> principles. Our desire is to build and foster an open source community around 
> scalable, robust PIR  which aligns with the Apache tenets. Further, Apache is 
> a natural home for Pirk given our existing dependencies and alignment with 
> ASF projects.
>
> === Documentation ===
>
> At this time there is no Pirk documentation on the web. However, we have 
> documentation included within the application that details usage. Using 
> incubator infrastructure we will be rapidly expanding the available 
> documentation to cover things like installation, developer guide, frequently 
> asked questions, best practices, and more.
>
> == Initial Source ==
>
> The core codebase is written in Java and includes detailed Javadocs and 
> feature documentation.
>
> == Source and Intellectual Property Submission ==
>
> The Pirk code and documentation materials will be submitted by the National 
> Security Agency. Pirk has been developed by government employees. Material 
> developed by the government employees is in the public domain and no U.S.
> copyright exists in works of the federal government. NSA has submitted 
> Corporate Contributor License Agreement to the Apache Software Foundation; 
> the Software Grant Agreement is forth coming.
>
> == External Dependencies ==
>
> We believe all current dependencies are compatible with the ASF guidelines.
> Our dependency licenses come from the Apache v 2.0 and Eclipse Public v1.
>
> == Cryptography ==
>
> Consistent with http://www.apache.org/licenses/exports/ we believe Pirk is 
> classified as ECCN 5D002. 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.
>
> == Required Resources ==
>
> === Mailing Lists ===
>
>  * d...@pirk.incubator.apache.org
>  * priv...@pirk.incubator.apache.org
>  * comm...@pirk.incubator.apache.org
>
> === Source Control ===
>
> Pirk requests use of Git for source control (git://git.apache.org/pirk.git).
> We request a writeable Git repo for Pirk with mirroring to be setup to Github 
> through INFRA.
>
> === Issue Tracking ===
>
> JIRA Pirk (PIRK)
>
> === Initial Committers ===
>
>  * Tracy Brown , CLA submitted
>  * Christopher Harris , CLA submitted
>  * Walter Ray-Dulaney , CLA submitted
>  * Jacob Wilder , CLA submitted
>  * Ellison Anne Williams  , CLA confirmed
>  * Joe Witt (Hortonworks) , CLA confirmed
>
> == Sponsors ==
>
> === Champion ===
>
>  * Billie Rinaldi (Hortonworks) , IPMC Member
>
> === Nominated Mentors ===
>
>  * Billie Rinaldi (Hortonworks) , IPMC Member
>  * Joe Witt (Hortonworks) , IPMC Member
>  * Josh Elser (Hortonworks) , IPMC Member
>
> === Sponsoring Entity ===
>
> We request the Apache Incubator to sponsor this project.
>
> -
> 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

Re: Joe Witt joins the Incubator PMC

[Joe Witt]

Thank you all.  Very happy to be able to help and give back to new
communities forming in the incubator.  I know I benefited greatly from
the mentors we had during incubation and definitely feel like I need
to return the favor.

I can definitely not be as awesome as Justin is with licensing/release
review diligence but I can sure try to help take the edge off!

On Mon, Jun 6, 2016 at 9:53 PM, Martin Gainty <mgai...@hotmail.com> wrote:
> Welcome Joseph!
>
> Martin
>
>
>
>> From: mar...@rectangular.com
>> Date: Mon, 6 Jun 2016 12:48:35 -0700
>> Subject: Joe Witt joins the Incubator PMC
>> To: general@incubator.apache.org
>>
>> Greets,
>>
>> I'm pleased to announce that Apache Member Joe Witt has joined the
>> Incubator PMC!
>>
>> Joe is a core contributor to Apache NiFi, and is currently the
>> project's PMC Chair.  Joe knows the Incubator from NiFi's trip through
>> it -- we look forward to him returning to contribute as a member of
>> the IPMC!
>>
>> Marvin Humphrey, on behalf of the IPMC
>>
>> -
>> 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

Re: [VOTE] Accept Gossip into the Apache Incubator

[Joe Witt]

+1 (non-binding)

Very interesting and hope to participate.

On Mon, Apr 25, 2016 at 2:14 PM, P. Taylor Goetz  wrote:
> Following the discussion thread [1], I would like to call a VOTE to accept
> Gossip into the Apache Incubator.
>
> The Gossip proposal can be found here [2] and is also listed below.
>
> [ ] +1 Accept Gossip into the Apache Incubator
> [ ] +0 Abstain.
> [ ] -1 Do not accept Gossip into the Apache Incubator because…
>
> This vote will be open for at least 72 hours.
>
> Obviously I am +1 (binding).
>
> -Taylor
>
> [1] https://s.apache.org/gossip-discuss
> [2] https://wiki.apache.org/incubator/GossipProposal
>
> 
> = Abstract =
>
> Apache Gossip will be an implementation of the Gossip Protocol based on code
> available here: https://github.com/edwardcapriolo/gossip/ which is already
> licenced using the glorious Apache V2 License.
>
> = Proposal =
>
> Apache Gossip aims to provide a gossip based consensus protocol written in
> Java for peer-to-peer communication to the Apache Incubator
> (http://incubator.apache.org/). This implementation will effectively scale
> from one to one-thousand node clusters. In addition to the code
> implementation, the project should produce specifications of the wire
> protocol, features, and expected behavior of the system such that compatible
> implementations can communicate.
>
> = Background =
>
> The gossip protocol has been implemented to varying levels of rigor by a
> number of entities. In particular, Apache Cassandra uses an implementation
> of gossip to locate peers and transmit up/down state. Apache Spark leverages
> tooling in Akka which provides peer-to-peer node discovery capabilities.
>
>  *
> http://highscalability.com/blog/2011/11/14/using-gossip-protocols-for-failure-detection-monitoring-mess.html
>
>  * https://en.wikipedia.org/wiki/Gossip_protocol
>
> = Rationale =
>
> With distributed computing becoming extremely widespread, and the growth of
> the buzz-factor of ‘the-internet-of-things’ it is increasingly important
> that networks of IP addressable devices can form a peer-to-peer network.
> Applications of peer-to-peer networks include generating crypto currency,
> managing hardware such as solar power micro-grids, and more traditional
> roles like grid/High Performance Computing and distributed storage systems.
> Different implementations of gossip based consensus protocols have been
> implemented in numerous languages or as part of more complex software
> stacks. The Apache Software Foundation should lead the effort of producing a
> purpose built tool that can be used by downstream projects to form
> peer-to-peer networks.
>
> = Initial Goals =
>
>  * Migration of current code https://github.com/edwardcapriolo/gossip and
> existing community to the Apache Software Foundation infrastructure
>  * Secure communications
>   * Transport security using a pre-shared key
>   * Public Key Infrastructure
>  * Introduce a cluster name to wire protocol to avoid misconfigurations
>  * Effectively operate when systems have multiple network interfaces by
> controlling IP binding settings
>  * Effectively operate when systems have Network Address Translations
> devices between them using a broadcast IP settings
>  * Develop advanced integration testing from cluster sizes of 1-1000 nodes
>   * Test convergence times
>   * Demonstrate the tradeoffs of different settings in regard to
> bandwidth/cpu/convergence time/accuracy
>  * Gossip data other than cluster state such as application/user data
>  * Provide detailed specifications such that others can implement the
> protocol in other programming languages
>  * Explore HTTP transport as an alternative to UDP
>
> = Current Status =
>
> The current code has been around for some time. Previously it was a Google
> code project. Since the fork in January 2015 there have been 55 commits and
> 4 releases.
>
> == Meritocracy ==
>
> We believe in meritocracy. All suggestions are taken seriously. We enjoy
> helping new people become part of process. For other projects available on
> our Github, once a user shows enough activity we grant them collaborator
> status.
>
> == Community ==
>
> In a relatively short amount of time, with a small amount of promotion on
> twitter and through blogging, we have 50+ followers on Github and several
> forks of the project. With the Apache brand we should be able to attract
> more. Once we have entered the incubator we believe it will be easier to
> attempt to unify with other similar implementations.
>
> == Core Developers ==
>
> The code was forked on Jan 9th 2015, since then there have been 4 releases
> and 55 commits. Since that period, the majority of the work was undertaken
> by Edward Capriolo. Several people are interested in the features of this
> proposal and have indicated they will volunteer their time.
>
> == Alignment ==
>
> Apache is the perfect organization to take on the Gossip project. Besides
> benefiting a number of 

Re: Confusion over NOTICE vs LICENSE files

[Joe Witt]

Justin,

Speaking from the NiFi side I can assure you an enormous amount of
time, energy, and communication go into LICENSE and NOTICE handling
for this project.  We've had discussions with PMC and committers of
other projects to learn their approach as well as to encourage them to
follow these policies as well.

We attempt to adhere to both spirit and letter of policy regarding
licensing and notice information.  The NOTICE [1] you reference for us
is only the source release NOTICE and I believe it to be correct for
the source release.  Can you share what you see is missing?

We also maintain a notice that specifically applies to any convenance
binaries we produce [2].  In fact, we also do that level of artifact
specific NOTICE resolution for any bundling of dependencies we do (for
example [3]).

We produced and frequently reference this guide to help our community
stay consistent with the policy as we understood/understand it [4].

And here you can see that we are pretty strict in following the
understanding of the policy even when it deviates from otherwise
accepted practice [5].

I very much welcome efforts to improve this guidance.  I think some of
the work Todd Lipcon has initiated recently is a great start.

Now I write this realizing you are an excellent contributor to the
licensing/notice discussions and you provided some of the best RC
reviews in this area as well for us in incubation.  So I write this
fully respecting you just want things to be done right.  if we're
actually doing something wrong let us know and we'll sort it out.

[1] https://github.com/apache/nifi/blob/master/NOTICE
[2] https://github.com/apache/nifi/blob/master/nifi-assembly/NOTICE
[3] 
https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-hadoop-libraries-bundle/nifi-hadoop-libraries-nar/src/main/resources/META-INF/NOTICE
[4] https://nifi.apache.org/licensing-guide.html
[5] https://issues.apache.org/jira/browse/LEGAL-230

On Wed, Feb 3, 2016 at 7:01 PM, Justin Mclean  wrote:
> Hi
>
> It seems that some of the confusion comes from what top level projects have 
> done and not keep up with policy? From a 5 minute search (and not to pick on 
> / point out any particular project) here’s some examples were I think 
> improvement could be made to NOTICE files. [1][2][3][4][5][6][7]
>
> Perhaps it's time to ask TLP to review their LICENCE / NOTICE to be a little 
> more consistent with current policy? Any suggestion on how we would go about 
> this? Does the policy need to be made clearer first?
>
> Thanks,
> Justin
>
> 1. https://github.com/apache/spark/blob/master/NOTICE 
> 
> 2. https://github.com/apache/flink/blob/master/NOTICE 
> 
> 3. https://github.com/apache/nifi/blob/master/NOTICE 
> 
> 4. https://github.com/apache/accumulo/blob/master/NOTICE 
> 
> 5. https://github.com/apache/camel/blob/master/NOTICE.txt 
> 
> 6. https://github.com/apache/phoenix/blob/master/NOTICE 
> 
> 7. https://github.com/apache/lucene-solr/blob/master/lucene/NOTICE.txt 
> 
>
>
>
>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Beam into the Apache Incubator

[Joe Witt]

t;> == External Dependencies ==
>>
>> All external dependencies are licensed under an Apache 2.0 or
>> Apache-compatible license. As we grow the Beam community we will configure
>> our build process to require and validate all contributions and
>> dependencies are licensed under the Apache 2.0 license or are under an
>> Apache-compatible license.
>>
>> == Required Resources ==
>>
>> === Mailing Lists ===
>>
>> We currently use a mix of mailing lists. We will migrate our existing
>> mailing lists to the following:
>>
>>  * d...@beam.incubator.apache.org
>>  * u...@beam.incubator.apache.org
>>  * priv...@beam.incubator.apache.org
>>  * comm...@beam.incubator.apache.org
>>
>> === Source Control ===
>>
>> The Dataflow team currently uses Git and would like to continue to do so.
>> We request a Git repository for Beam with mirroring to GitHub enabled.
>>
>>  * https://git-wip-us.apache.org/repos/asf/incubator-beam.git
>>
>> === Issue Tracking ===
>>
>> We request the creation of an Apache-hosted JIRA. The Dataflow project is
>> currently using both a public GitHub issue tracker and internal Google
>> issue tracking. We will migrate and combine from these two sources to the
>> Apache JIRA.
>>
>>  * Jira ID: BEAM
>>
>> == Initial Committers ==
>>
>>  * Aljoscha Krettek[aljos...@apache.org]
>>  * Amit Sela   [amitsel...@gmail.com]
>>  * Ben Chambers[bchamb...@google.com]
>>  * Craig Chambers  [chamb...@google.com]
>>  * Dan Halperin[dhalp...@google.com]
>>  * Davor Bonaci[da...@google.com]
>>  * Frances Perry   [f...@google.com]
>>  * James Malone[jamesmal...@google.com]
>>  * Jean-Baptiste Onofré[jbono...@apache.org]
>>  * Josh Wills  [jwi...@apache.org]
>>  * Kostas Tzoumas  [kos...@data-artisans.com]
>>  * Kenneth Knowles [k...@google.com]
>>  * Luke Cwik   [lc...@google.com]
>>  * Maximilian Michels  [m...@apache.org]
>>  * Stephan Ewen[step...@data-artisans.com]
>>  * Tom White   [t...@cloudera.com]
>>  * Tyler Akidau[taki...@google.com]
>>  * Robert Bradshaw [rober...@google.com]
>>
>> == Additional Interested Contributors ==
>>
>>  * Debo Dutta  [dedu...@cisco.com]
>>  * Henry Saputra   [hsapu...@apache.org]
>>  * Taylor Goetz[ptgo...@gmail.com]
>>  * James Carman[ja...@carmanconsulting.com]
>>  * Joe Witt[joew...@apache.org]
>>  * Vaibhav Gumashta[vgumas...@hortonworks.com]
>>  * Prasanth Jayachandran   [pjayachand...@hortonworks.com]
>>  * Johan Edstrom   [seij...@gmail.com]
>>  * Hugo Louro  [hmclo...@gmail.com]
>>  * Krzysztof Sobkowiak [krzys.sobkow...@gmail.com]
>>  * Jeff Genender   [jgenen...@apache.org]
>>  * Edward J. Yoon  [edward.y...@samsung.com]
>>  * Hao Chen[h...@apache.org]
>>  * Byung-Gon Chun  [bgc...@gmail.com]
>>  * Charitha Elvitigala [charit...@apache.org]
>>  * Alexander Bezzubov  [b...@apache.org]
>>  * Tsuyoshi Ozawa  [oz...@apache.org]
>>  * Mayank Bansal   [maban...@gmail.com]
>>  * Supun Kamburugamuve [su...@apache.org]
>>  * Matthias Wessendorf [mat...@apache.org]
>>  * Felix Cheung[felixche...@apache.org]
>>  * Ajay Yadava [ajay.ya...@inmobi.com]
>>  * Liang Chen  [chenliang...@huawei.com]
>>  * Renaud Richardet[renaud (at) apache (dot) org]
>>  * Bakey Pan   [bakey1...@gmail.com]
>>  * Andreas Neumann [a...@apache.org]
>>  * Suresh Marru[sma...@apache.org]
>>  * Hadrian Zbarcea [hzbar...@gmail.com]
>>
>> == Affiliations ==
>>
>> The initial committers are from six organizations. Google developed
>> Dataflow and the Dataflow SDK, data Artisans developed the Flink runner,
>> and Cloudera (Labs) developed the Spark runner.
>>
>>  * Cloudera
>>   * Tom White
>>  * Data Artisans
>>   * Aljoscha Krettek
>>   * Kostas Tzoumas
>>   * Maximilian Michels
>>   * Stephan Ewen
>>  * Google
>>   * Ben Chambers
>>   * Dan Halperin
>>   * Davor Bonaci
>>   * Frances Perry
>>   * James Malone
>>   * Kenneth Knowles
>>   * Luke Cwik
>>   * Tyler Akidau
>>   * Robert Bradshaw
>>  * PayPal
>>   * Amit Sela
>>  * Slack
>>   * Josh Wills
>>  * Talend
>>   * Jean-Baptiste Onofré
>>
>> == Sponsors ==
>>
>> === Champion ===
>>
>>  * Jean-Baptiste Onofre [jbono...@apache.org]
>>
>> === Nominated Mentors ===
>>
>>  * Jean-Baptiste Onofre   [jbono...@apache.org]
>>  * Jim Jagielski  [j...@apache.org]
>>  * Venkatesh Seetharam[venkat...@apache.org]
>>  * Bertrand Delacretaz[bdelacre...@apache.org]
>>  * Ted Dunning[tdunn...@apache.org]
>>
>> === Sponsoring Entity ===
>>
>> The Apache Incubator
>> 
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Apache Dataflow Incubator Proposal

[Joe Witt]

Hello

This is a very interesting proposal and concept.  I'd like to contribute.

Thanks
Joe

On Wed, Jan 20, 2016 at 2:50 PM, James Carman
 wrote:
> Of course! I'd be happy to help
>
> On Wed, Jan 20, 2016 at 2:02 PM Jean-Baptiste Onofré 
> wrote:
>
>> Hi James,
>>
>> Can I add your to the proposal ?
>>
>> Regards
>> JB
>>
>> On 01/20/2016 07:20 PM, James Carman wrote:
>> > Well, I for one would be very interested in this project and would be
>> happy
>> > to contribute.
>> >
>> >
>> > On Wed, Jan 20, 2016 at 12:09 PM Jean-Baptiste Onofré 
>> > wrote:
>> >
>> >> Hi Sean,
>> >>
>> >> It's a fair point, but not present in most of the proposals. It's
>> >> something that we can address in the "Community" section.
>> >>
>> >> Regards
>> >> JB
>> >>
>> >> On 01/20/2016 05:55 PM, Sean Busbey wrote:
>> >>> Great proposal. I like that your proposal includes a well presented
>> >>> roadmap, but I don't see any goals that directly address building a
>> >> larger
>> >>> community. Y'all have any ideas around outreach that will help with
>> >>> adoption?
>> >>>
>> >>> As a start, I recommend y'all add a section to the proposal on the wiki
>> >>> page for "Additional Interested Contributors" so that folks who want to
>> >>> sign up to participate in the project can do so without requesting
>> >>> additions to the initial committer list.
>> >>>
>> >>> On Wed, Jan 20, 2016 at 10:32 AM, James Malone <
>> >>> jamesmal...@google.com.invalid> wrote:
>> >>>
>>  Hello everyone,
>> 
>>  Attached to this message is a proposed new project - Apache Dataflow,
>> a
>>  unified programming model for data processing and integration.
>> 
>>  The text of the proposal is included below. Additionally, the proposal
>> >> is
>>  in draft form on the wiki where we will make any required changes:
>> 
>>  https://wiki.apache.org/incubator/DataflowProposal
>> 
>>  We look forward to your feedback and input.
>> 
>>  Best,
>> 
>>  James
>> 
>>  
>> 
>>  = Apache Dataflow =
>> 
>>  == Abstract ==
>> 
>>  Dataflow is an open source, unified model and set of language-specific
>> >> SDKs
>>  for defining and executing data processing workflows, and also data
>>  ingestion and integration flows, supporting Enterprise Integration
>> >> Patterns
>>  (EIPs) and Domain Specific Languages (DSLs). Dataflow pipelines
>> simplify
>>  the mechanics of large-scale batch and streaming data processing and
>> can
>>  run on a number of runtimes like Apache Flink, Apache Spark, and
>> Google
>>  Cloud Dataflow (a cloud service). Dataflow also brings DSL in
>> different
>>  languages, allowing users to easily implement their data integration
>>  processes.
>> 
>>  == Proposal ==
>> 
>>  Dataflow is a simple, flexible, and powerful system for distributed
>> data
>>  processing at any scale. Dataflow provides a unified programming
>> model,
>> >> a
>>  software development kit to define and construct data processing
>> >> pipelines,
>>  and runners to execute Dataflow pipelines in several runtime engines,
>> >> like
>>  Apache Spark, Apache Flink, or Google Cloud Dataflow. Dataflow can be
>> >> used
>>  for a variety of streaming or batch data processing goals including
>> ETL,
>>  stream analysis, and aggregate computation. The underlying programming
>>  model for Dataflow provides MapReduce-like parallelism, combined with
>>  support for powerful data windowing, and fine-grained correctness
>> >> control.
>> 
>>  == Background ==
>> 
>>  Dataflow started as a set of Google projects focused on making data
>>  processing easier, faster, and less costly. The Dataflow model is a
>>  successor to MapReduce, FlumeJava, and Millwheel inside Google and is
>>  focused on providing a unified solution for batch and stream
>> processing.
>>  These projects on which Dataflow is based have been published in
>> several
>>  papers made available to the public:
>> 
>>  * MapReduce - http://research.google.com/archive/mapreduce.html
>> 
>>  * Dataflow model  - http://www.vldb.org/pvldb/vol8/p1792-Akidau.pdf
>> 
>>  * FlumeJava - http://notes.stephenholiday.com/FlumeJava.pdf
>> 
>>  * MillWheel - http://research.google.com/pubs/pub41378.html
>> 
>>  Dataflow was designed from the start to provide a portable programming
>>  layer. When you define a data processing pipeline with the Dataflow
>> >> model,
>>  you are creating a job which is capable of being processed by any
>> >> number of
>>  Dataflow processing engines. Several engines have been developed to
>> run
>>  Dataflow pipelines in other open source runtimes, including a Dataflow
>>  runner for Apache Flink and Apache Spark. There is also a “direct
>> >> runner”,
>>  for execution on the 

Re: [VOTE] Release apache-singa-incubating-0.2.0

[Joe Witt]

John,

The language within the header of those files includes things like the
following as found in ltmain.sh

# As a special exception to the GNU General Public License,
# if you distribute this file as part of a program or library that
# is built using GNU Libtool, you may include this file under the
# same distribution terms that you use for the rest of that program.

I suspect that is the exception being referred to here since they
mentioned their use is consistent with being for build.

Thanks
Joe

On Sun, Jan 10, 2016 at 12:18 PM, John D. Ament  wrote:
> Daniel,
>
> Could you explain those exceptions? I don't think I've ever heard of GPL
> being OK'd to use in an AL release.
>
> John
>
> On Sun, Jan 10, 2016 at 7:41 AM Daniel Gruno  wrote:
>
>> +0.999 - seem okay but some files are missing license headers.
>>
>> The seemingly GPL (some aren't GPL at all) files Justin linked to have
>> exceptions for use which allows it.
>>
>> I ran it through my usual stuff,
>> http://compliance.rocks/result.html?358649c0
>> - and every single GPL-licensed file has an exception which allows it to
>> be bundled with ALv2 projects.
>>
>> With regards,
>> Daniel.
>>
>> On 01/10/2016 01:14 PM, Justin Mclean wrote:
>> > Hi,
>> >
>> > Sorry it’s -1 binding due to the inclusion of GPL licenced files [1] and
>> other license issues [2] and unable to compile from source. Happy to
>> reconsider if explained.
>> >
>> > I checked:
>> > - release contains incubating
>> > - signatures and hashes good
>> > - DISCLAIMER exists
>> > - LICENSE has some minor issues
>> > - NOTICE contains too much information
>> > - No binaries in source
>> > - All source files have apache header
>> > - Unable to compile from source
>> >
>> > GPL licensed files includes:
>> > ./config/ltmain.sh
>> > ./config/ltversion.m4
>> > ./config/lt~obsolete.m4
>> > ./config/config.guess
>> > ./config/config.sub
>> > ./config/install-sh (?)
>> > ./Makefile.in (?) this also has a ASF header which seems odd
>> >
>> > While this seems to be a build tool [7] I’m not 100% sure if all files
>> here are OK.
>> >
>> > For LICENSE:
>> > - path to tinydir.h is incorrect
>> > - missing licence for ./include/singa/utils/cuda_utils.h
>> > - include/utils/common.h path is incorrect and the file most likely has
>> an incorrect ASF header
>> > - missing license for (BSD licensed) ./tool/cpplint.py. Possibly
>> tool/cppling.py should be tool/cpplint.py?
>> > - missing licence for (BSD license?) ./examples/rnnlm/create_data.cc
>> > - copyright for tinydir is incorrect should be "Cong Xu, Baudouin
>> Feildel”
>> > - files in include/mshadow/* are missing Apache header so it’s unclear
>> if they are Apache licensed or where they are from. I think this is sort of
>> OK [3]
>> > - copyright "Copyright (c) 2014, 2015, The Regents of the University of
>> California (Regents)” may be incorrect, you may want to double check years
>> >
>> > May be other issues as at this point i gave up.
>> >
>> > Also LICENSE file is also missing some whitespace on the first line
>> which you may want to fix.
>> >
>> > For NOTICE:
>> > - No need to include BSD licence information [4]
>> > - Too much info in NOTICE [5]
>> > - No need to list non bundled software [6]
>> >
>> > Would also be nice to have compile instructions. On OS X configure fails
>> for me with:
>> > configure: error: unable to find cblas_sgemm() function
>> >
>> > Assuming you run configure &&  make to compile and OS X is supported but
>> it’s not 100% clear.
>> >
>> > Thanks,
>> > Justin
>> >
>> > 1. http://www.apache.org/legal/resolved.html#category-x
>> > 2. http://www.apache.org/dev/licensing-howto.html#permissive-deps
>> > 3. https://github.com/dmlc/mshadow
>> > 4. http://www.apache.org/dev/licensing-howto.html#permissive-deps
>> > 5. http://www.apache.org/dev/licensing-howto.html#mod-notice
>> > 6. http://www.apache.org/dev/licensing-howto.html#guiding-principle
>> > 7. http://www.apache.org/legal/resolved.html#build-tools
>> > -
>> > 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
>>
>>

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Accept Metron into Apache Incubator

[Joe Witt]

+1 (non-binding).

Solid apache mentors and team.  Good luck!

On Thu, Dec 3, 2015 at 12:33 PM, Owen O'Malley  wrote:
> The [DISCUSS] thread has would down, so I'd like to start a VOTE on whether
> Apache Incubator should accept Metron as a podling. The proposal is pasted
> below and is available on the wiki as well.
>
> https://wiki.apache.org/incubator/MetronProposal
>
> We've added a paragraph in the background section discussing how Apache
> avoids hostile forks of projects, because we don't want to fork
> communities. We've also added Larry McCay, P. Taylor Goetz, and Phillip
> Rhodes to the proposal.
>
> The vote will run until 12pm PST on Sunday.
>
> Thanks,
>Owen
>
> = Apache Metron Proposal =
>
> 
> /!\ '''FINAL''' /!\
>
> This proposal is now complete and has been submitted for a VOTE.
> 
>
> == Abstract ==
>
> The Metron project is an open source project dedicated to providing an
> extensible and scalable advanced security analytics tool. It has strong
> foundations in the Apache Hadoop ecosystem.
>
> == Proposal ==
>
> Metron integrates a variety of open source big data technologies in order
> to offer a centralized tool for security monitoring and analysis. Metron
> provides capabilities for log aggregation, full packet capture indexing,
> storage, advanced behavioral analytics and data enrichment, while applying
> the most current threat-intelligence information to security telemetry
> within a single platform.
>
> Metron can be divided into 4 areas:
>
>   1. '''A mechanism to capture, store, and normalize any type of security
> telemetry at extremely high rates.''' Because security telemetry is
> constantly being generated, it requires a method for ingesting the data at
> high speeds and pushing it to various processing units for advanced
> computation and analytics.
>   1. '''Real time processing and application of enrichments''' such as
> threat intelligence, geolocation, and DNS information to telemetry being
> collected. The immediate application of this information to incoming
> telemetry provides the context and situational awareness, as well as the
> “who” and “where” information that is critical for investigation.
>   1. '''Efficient information storage''' based on how the information will
> be used:
> a. Logs and telemetry are stored such that they can be efficiently
> mined and analyzed for concise security visibility
> a. The ability to extract and reconstruct full packets helps an analyst
> answer questions such as who the true attacker was, what data was leaked,
> and where that data was sent
> a. Long-term storage not only increases visibility over time, but also
> enables advanced analytics such as machine learning techniques to be used
> to create models on the information. Incoming data can then be scored
> against these stored models for advanced anomaly detection.
>   1. '''An interface that gives a security investigator a centralized view
> of data and alerts passed through the system.''' Metron’s interface
> presents alert summaries with threat intelligence and enrichment data
> specific to that alert on one single page. Furthermore, advanced search
> capabilities and full packet extraction tools are presented to the analyst
> for investigation without the need to pivot into additional tools.
>
> Big data is a natural fit for powerful security analytics. The Metron
> framework integrates a number of elements from the Hadoop ecosystem to
> provide a scalable platform for security analytics, incorporating such
> functionality as full-packet capture, stream processing, batch processing,
> real-time search, and telemetry aggregation. With Metron, our goal is to
> tie big data into security analytics and drive towards an extensible
> centralized platform to effectively enable rapid detection and rapid
> response for advanced security threats.
>
> == Background ==
>
> OpenSOC was developed by Cisco over the last two years and pushed out to
> Github (https://github.com/OpenSOC/opensoc) under the ALv2. However, the
> development was mostly closed and has largely stopped. As evidence of the
> inactivity, users have complained that pull requests are not answered for a
> while
> https://groups.google.com/d/msg/opensoc-support/R2W-ZFux8Vk/Y-5tL-EmAAAJ.
> Finally, no public releases of OpenSOC have been made. From an Apache point
> of view, the current community is not viable.
>
> However, some of the developers of the project have left Cisco and have
> found interest from several others that would like to work together to form
> an active and open community at Apache starting from the current OpenSOC
> code base. A message to the current support group proposing moving to
> Apache got a single positive response.
> https://groups.google.com/d/msg/opensoc-support/rFlW2uSSvmU/09PIsWL4AAAJ
>
> In general Apache accepts only voluntary contributions and avoids
> hostile forks. In this case, given that the community is demonstrably
> dead, it 

Re: [VOTE] Accept Kudu into the Apache Incubator

[Joe Witt]

+1 (non-binding)

On Wed, Nov 25, 2015 at 5:26 PM, Hitesh Shah  wrote:
> +1 (binding)
>
> — Hitesh
>
> On Nov 24, 2015, at 11:32 AM, Todd Lipcon  wrote:
>
>> Hi all,
>>
>> Discussion on the [DISCUSS] thread seems to have wound down, so I'd like to
>> call a VOTE on acceptance of Kudu into the ASF Incubator. The proposal is
>> pasted below and also available on the wiki at:
>> https://wiki.apache.org/incubator/KuduProposal
>>
>> The proposal is unchanged since the original version, except for the
>> addition of Carl Steinbach as a Mentor.
>>
>> Please cast your votes:
>>
>> [] +1, accept Kudu into the Incubator
>> [] +/-0, positive/negative non-counted expression of feelings
>> [] -1, do not accept Kudu into the incubator (please state reasoning)
>>
>> Given the US holiday this week, I imagine many folks are traveling or
>> otherwise offline. So, let's run the vote for a full week rather than the
>> traditional 72 hours. Unless the IPMC objects to the extended voting
>> period, the vote will close on Tues, Dec 1st at noon PST.
>>
>> Thanks
>> -Todd
>> -
>>
>> = Kudu Proposal =
>>
>> == Abstract ==
>>
>> Kudu is a distributed columnar storage engine built for the Apache Hadoop
>> ecosystem.
>>
>> == Proposal ==
>>
>> Kudu is an open source storage engine for structured data which supports
>> low-latency random access together with efficient analytical access
>> patterns. Kudu distributes data using horizontal partitioning and
>> replicates each partition using Raft consensus, providing low
>> mean-time-to-recovery and low tail latencies. Kudu is designed within the
>> context of the Apache Hadoop ecosystem and supports many integrations with
>> other data analytics projects both inside and outside of the Apache
>> Software Foundation.
>>
>>
>>
>> We propose to incubate Kudu as a project of the Apache Software Foundation.
>>
>> == Background ==
>>
>> In recent years, explosive growth in the amount of data being generated and
>> captured by enterprises has resulted in the rapid adoption of open source
>> technology which is able to store massive data sets at scale and at low
>> cost. In particular, the Apache Hadoop ecosystem has become a focal point
>> for such “big data” workloads, because many traditional open source
>> database systems have lagged in offering a scalable alternative.
>>
>>
>>
>> Structured storage in the Hadoop ecosystem has typically been achieved in
>> two ways: for static data sets, data is typically stored on Apache HDFS
>> using binary data formats such as Apache Avro or Apache Parquet. However,
>> neither HDFS nor these formats has any provision for updating individual
>> records, or for efficient random access. Mutable data sets are typically
>> stored in semi-structured stores such as Apache HBase or Apache Cassandra.
>> These systems allow for low-latency record-level reads and writes, but lag
>> far behind the static file formats in terms of sequential read throughput
>> for applications such as SQL-based analytics or machine learning.
>>
>>
>>
>> Kudu is a new storage system designed and implemented from the ground up to
>> fill this gap between high-throughput sequential-access storage systems
>> such as HDFS and low-latency random-access systems such as HBase or
>> Cassandra. While these existing systems continue to hold advantages in some
>> situations, Kudu offers a “happy medium” alternative that can dramatically
>> simplify the architecture of many common workloads. In particular, Kudu
>> offers a simple API for row-level inserts, updates, and deletes, while
>> providing table scans at throughputs similar to Parquet, a commonly-used
>> columnar format for static data.
>>
>>
>>
>> More information on Kudu can be found at the existing open source project
>> website: http://getkudu.io and in particular in the Kudu white-paper PDF:
>> http://getkudu.io/kudu.pdf from which the above was excerpted.
>>
>> == Rationale ==
>>
>> As described above, Kudu fills an important gap in the open source storage
>> ecosystem. After our initial open source project release in September 2015,
>> we have seen a great amount of interest across a diverse set of users and
>> companies. We believe that, as a storage system, it is critical to build an
>> equally diverse set of contributors in the development community. Our
>> experiences as committers and PMC members on other Apache projects have
>> taught us the value of diverse communities in ensuring both longevity and
>> high quality for such foundational systems.
>>
>> == Initial Goals ==
>>
>> * Move the existing codebase, website, documentation, and mailing lists to
>> Apache-hosted infrastructure
>> * Work with the infrastructure team to implement and approve our code
>> review, build, and testing workflows in the context of the ASF
>> * Incremental development and releases per Apache guidelines
>>
>> == Current Status ==
>>
>>  Releases 
>>
>> Kudu has undergone one public release, tagged here

Re: [VOTE] Accept Impala into the Apache Incubator

[Joe Witt]

+1 (non-binding)

On Thu, Nov 26, 2015 at 2:50 PM, Konstantin Boudnik  wrote:
> Come to think of it a bit more, yes I am not satisfied with the outcome of
> the CTR/RTC exchange in the project.
>
> Hence changing my vote to
>  -1 [binding]
>
> On Thu, Nov 26, 2015 at 11:47AM, Konstantin Boudnik wrote:
>> -0 [binding]
>>
>> On Tue, Nov 24, 2015 at 01:03PM, Henry Robinson wrote:
>> > Hi -
>> >
>> > The [DISCUSS] thread has been quiet for a few days, so I think there's been
>> > sufficient opportunity for discussion around our proposal to bring Impala
>> > to the ASF Incubator.
>> >
>> > I'd like to call a VOTE on that proposal, which is on the wiki at
>> > https://wiki.apache.org/incubator/ImpalaProposal, and which I've pasted
>> > below.
>> >
>> > During the discussion period, the proposal has been amended to add Brock
>> > Noland as a new mentor, to add one missed committer from the list and to
>> > correct some issues with the dependency list.
>> >
>> > Please cast your votes as follows:
>> >
>> > [] +1, accept Impala into the Incubator
>> > [] +/-0, non-counted vote to express a disposition
>> > [] -1, do not accept Impala into the Incubator (please give your reason(s))
>> >
>> > As with the concurrent Kudu vote, I propose leaving the vote open for a
>> > full seven days (to close at Tuesday, December 1st at noon PST), due to the
>> > upcoming US holiday.
>> >
>> > Thanks,
>> > Henry
>> >
>> > 
>> >
>> > = Abstract =
>> > Impala is a high-performance C++ and Java SQL query engine for data stored
>> > in Apache Hadoop-based clusters.
>> >
>> > = Proposal =
>> >
>> > We propose to contribute the Impala codebase and associated artifacts (e.g.
>> > documentation, web-site content etc.) to the Apache Software Foundation
>> > with the intent of forming a productive, meritocratic and open community
>> > around Impala’s continued development, according to the ‘Apache Way’.
>> >
>> > Cloudera owns several trademarks regarding Impala, and proposes to transfer
>> > ownership of those trademarks in full to the ASF.
>> >
>> > = Background =
>> > Engineers at Cloudera developed Impala and released it as an
>> > Apache-licensed open-source project in Fall 2012. Impala was written as a
>> > brand-new, modern C++ SQL engine targeted from the start for data stored in
>> > Apache Hadoop clusters.
>> >
>> > Impala’s most important benefit to users is high-performance, making it
>> > extremely appropriate for common enterprise analytic and business
>> > intelligence workloads. This is achieved by a number of software
>> > techniques, including: native support for data stored in HDFS and related
>> > filesystems, just-in-time compilation and optimization of individual query
>> > plans, high-performance C++ codebase and massively-parallel distributed
>> > architecture. In benchmarks, Impala is routinely amongst the very highest
>> > performing SQL query engines.
>> >
>> > = Rationale =
>> >
>> > Despite the exciting innovation in the so-called ‘big-data’ space, SQL
>> > remains by far the most common interface for interacting with data in both
>> > traditional warehouses and modern ‘big-data’ clusters. There is clearly a
>> > need, as evidenced by the eager adoption of Impala and other SQL engines in
>> > enterprise contexts, for a query engine that offers the familiar SQL
>> > interface, but that has been specifically designed to operate in massive,
>> > distributed clusters rather than in traditional, fixed-hardware,
>> > warehouse-specific deployments. Impala is one such query engine.
>> >
>> > We believe that the ASF is the right venue to foster an open-source
>> > community around Impala’s development. We expect that Impala will benefit
>> > from more productive collaboration with related Apache projects, and under
>> > the auspices of the ASF will attract talented contributors who will push
>> > Impala’s development forward at pace.
>> >
>> > We believe that the timing is right for Impala’s development to move
>> > wholesale to the ASF: Impala is well-established, has been Apache-licensed
>> > open-source for more than three years, and the core project is relatively
>> > stable. We are excited to see where an ASF-based community can take Impala
>> > from this strong starting point.
>> >
>> > = Initial Goals =
>> > Our initial goals are as follows:
>> >
>> >  * Establish ASF-compatible engineering practices and workflows
>> >  * Refactor and publish existing internal build scripts and test
>> > infrastructure, in order to make them usable by any community member.
>> >  * Transfer source code, documentation and associated artifacts to the ASF.
>> >  * Grow the user and developer communities
>> >
>> > = Current Status =
>> >
>> > Impala is developed as an Apache-licensed open-source project. The source
>> > code is available at http://github.com/cloudera/Impala, and developer
>> > documentation is at https://github.com/cloudera/Impala/wiki. The majority
>> > of commits to the project have come from 

Re: Concerning Sentry: A disagreement over the Apache Way and graduation

[Joe Witt]

"Trust is the basis of a healthy community"

-- For sure.

"and RTC (via Jira or otherwise) just screams "we don't trust you. we
must review all commits first.""

-- I disagree.  RTC has merit independent of concerns of trust.  If
trust issues are present in a community then any number of challenges
will exist and all processes will suffer.  Keep in mind RTC applies to
everyone (PMC, committer, contributor).  So it isn't about trust at
all.  It is about community.

Not wanting to sidetrack this thread but also didn't want that comment
to go without a counter.

Thanks
Joe

On Wed, Nov 11, 2015 at 12:59 PM, Greg Stein  wrote:
> On Wed, Nov 11, 2015 at 6:27 AM, Steve Loughran 
> wrote:
>
>>
>> > On 11 Nov 2015, at 09:38, Bertrand Delacretaz 
>> wrote:
>> >
>> > Hi Steve,
>> >
>> > On Tue, Nov 10, 2015 at 9:31 PM, Steve Loughran 
>> wrote:
>> >> ...is JIRA-first development conducive to developing a community?...
>> >
>> > I don't think so, as you say this breaks the project into very small
>> > buckets and it's very hard for someone new to get the overview of
>> > what's going on and what the big ideas and visions are.
>>
>
> Agreed.
>
> I also find it sad that work is *gated* by using Jira first. We should be
> trusting our peers, let them commit changes necessary, and review their
> work afterwards. Trust is the basis of a healthy community, and RTC (via
> Jira or otherwise) just screams "we don't trust you. we must review all
> commits first."
>
>>...
>
>> One of the troublespots is those "minor" patches which have traumatic
>> consequences; you don't notice when the issue is created, don't watch it,
>> and then, when its merged in, you discover that things now behave
>> differently. Anything related to specific dependency updates are things to
>> watch there (guava, jackson, jersey), but it could be something more subtle
>> like a change in the concurrency model of some bit of code. It's only later
>> that you find your code has stopped working and you are left trying to work
>> out what happened and why.
>>
>
> I'm not sure what the above has to do with issues/Jira. Any commit can have
> this effect, whether it was done directly or via an issue. It's just a
> typical problem with development.
>
> (and yeah, it leads into a whole separate conversation about testing and CI)
>
>>...
>
>> Noted, but we're going to try it in the slider dev group anyway, so we can
>> do some more detailed code review of various complex things more
>> interactively. I know it excludes people who can't be there, but its still
>> more inclusive of
>>
>
> I see no problem doing code reviews this way, as other devs can still
> comment/review whatever output gets committed. They're only "shut out" of
> the first review, not ALL review.
>
> Using them for initial code development or decisions? Not so much.
>
> Using them to reach a consensus among a subset of the community? Sure, and
> bring that result to the dev@ list to reach full community consensus. We
> see this done all the time with hackathons: the group at the 'thon come up
> with some idea they all like, and bring that to the dev@ list. 10 people
> think it is the right approach and share it, then rope in the other 10.
>
>>...
>
> Cheers,
> -g

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT][VOTE] Graduate Apache NiFi from the Incubator

[Joe Witt]

Hello

The vote has passed with 12 +1 binding votes and no neutral or negative votes.

Will send the submission to the board cc'ing the IPMC and NiFi PPMC as
mentioned in [1] for next months board meeting.

Binding +1 votes include Chris Mattmann, Henry Saputra, Jan Iversen,
Bertrand Delacretaz, Justin Mclean, Roman Shaposhnik, John D Ament,
Andrew Purtell, Billie Rinaldi, Arvind Prabhakar, P Taylor Goetz, Jake
Farrell.

Thanks to all who voted and for the nice comments!

[1] 
http://incubator.apache.org/guides/graduation.html#ipmc-top-level-recommendation

Joe

 On Wed, Jun 17, 2015 at 12:05 AM, Joe Witt joe.w...@gmail.com wrote:

 Hello Apache Incubator

 This thread is to call a vote within the Incubator for the graduation
 of Apache NiFi.

 Status page:  http://incubator.apache.org/projects/nifi.html
 Incubator graduation discussion: http://s.apache.org/wmy
 NiFi community graduation vote: http://s.apache.org/GT9

 The discussion prompted Benson to join the PMC list to provide apache
 member experience and we clarified the scope language with discussion
 in the NiFi community.

 From the discussion thread Chris Mattmann offered his binding +1 vote.

 Since joining the Incubator in November, 2014 the NiFi community has:
  * Produced three IPMC approved releases.
  * Expanded the PPMC with 4 new members.
  * Grown the community.  Developed increased interoperability with
 other Apache projects.
  * Conducted a successful community vote to graduate with 22 +1 votes
 (5 IPMC binding).

 Please vote

 [  ] +1 Graduate Apache NiFi as a TLP
 [  ] +0
 [  ] -1 Do not graduate Apache NiFi as a TLP because…

 Voting will last 72 hours ending at 05:00 June 20, 2015 UTC.

 Thanks
 Joe

 === Board Resolution ===

 Establish the Apache NiFi Project

 WHEREAS, the Board of Directors deems it to be in the best
 interests of the Foundation and consistent with the
 Foundation's purpose to establish a Project Management
 Committee charged with the creation and maintenance of
 open-source software, for distribution at no charge to
 the public, related to an automated and durable data broker
 between systems providing interactive command and control
 and detailed chain of custody for data.

 NOW, THEREFORE, BE IT RESOLVED, that a Project Management
 Committee (PMC), to be known as the Apache NiFi Project,
 be and hereby is established pursuant to Bylaws of the
 Foundation; and be it further

 RESOLVED, that the Apache NiFi Project be and hereby is
 responsible for the creation and maintenance of software
 related to an automated and durable data broker
 between systems providing interactive command and control
 and detailed chain of custody for data; and be it further

 RESOLVED, that the office of Vice President, Apache NiFi be
 and hereby is created, the person holding such office to
 serve at the direction of the Board of Directors as the chair
 of the Apache NiFi Project, and to have primary responsibility
 for management of the projects within the scope of
 responsibility of the Apache NiFi Project; and be it further

 RESOLVED, that the persons listed immediately below be and
 hereby are appointed to serve as the initial members of the
 Apache NiFi Project:
 * Brandon DeVries (devri...@apache.org)
 * Matt Gilman (mcgil...@apache.org)
 * Tony Kurc (tk...@apache.org)
 * Mark Payne (marka...@apache.org)
 * Aldrin Piri (ald...@apache.org)
 * Dan Bress (danbr...@apache.org)
 * Jennifer Barnabee (jbarna...@apache.org)
 * Joseph L. Witt (joew...@apache.org)
 * Jason Carey (jca...@apache.org)
 * Adam Taft (tafts...@apache.org)
 * Benson Margulies (bimargul...@apache.org)
 * Bryan Bende (bbe...@apache.org)

 NOW, THEREFORE, BE IT FURTHER RESOLVED, that
 Joseph L. Witt be appointed to the office of Vice President,
 Apache NiFi, to serve in accordance with and subject to the
 direction of the Board of Directors and the Bylaws of the
 Foundation until death, resignation, retirement, removal or
 disqualification, or until a successor is appointed;
 and be it further

 RESOLVED, that the initial Apache NiFi PMC be and hereby is
 tasked with the creation of a set of bylaws intended to
 encourage open development and increased participation in the
 Apache NiFi Project; and be it further

 RESOLVED, that the Apache NiFi Project be and hereby
 is tasked with the migration and rationalization of the Apache
 Incubator NiFi podling; and be it further

 RESOLVED, that all responsibilities pertaining to the Apache
 Incubator NiFi podling encumbered upon the Apache Incubator
 Project are hereafter discharged.

 -

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org

[VOTE] Graduate Apache NiFi from the Incubator

[Joe Witt]

Hello Apache Incubator

This thread is to call a vote within the Incubator for the graduation
of Apache NiFi.

Status page:  http://incubator.apache.org/projects/nifi.html
Incubator graduation discussion: http://s.apache.org/wmy
NiFi community graduation vote: http://s.apache.org/GT9

The discussion prompted Benson to join the PMC list to provide apache
member experience and we clarified the scope language with discussion
in the NiFi community.

From the discussion thread Chris Mattmann offered his binding +1 vote.

Since joining the Incubator in November, 2014 the NiFi community has:
 * Produced three IPMC approved releases.
 * Expanded the PPMC with 4 new members.
 * Grown the community.  Developed increased interoperability with
other Apache projects.
 * Conducted a successful community vote to graduate with 22 +1 votes
(5 IPMC binding).

Please vote

[  ] +1 Graduate Apache NiFi as a TLP
[  ] +0
[  ] -1 Do not graduate Apache NiFi as a TLP because…

Voting will last 72 hours ending at 05:00 June 20, 2015 UTC.

Thanks
Joe

=== Board Resolution ===

Establish the Apache NiFi Project

WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to
the public, related to an automated and durable data broker
between systems providing interactive command and control
and detailed chain of custody for data.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache NiFi Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

RESOLVED, that the Apache NiFi Project be and hereby is
responsible for the creation and maintenance of software
related to an automated and durable data broker
between systems providing interactive command and control
and detailed chain of custody for data; and be it further

RESOLVED, that the office of Vice President, Apache NiFi be
and hereby is created, the person holding such office to
serve at the direction of the Board of Directors as the chair
of the Apache NiFi Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache NiFi Project; and be it further

RESOLVED, that the persons listed immediately below be and
hereby are appointed to serve as the initial members of the
Apache NiFi Project:
* Brandon DeVries (devri...@apache.org)
* Matt Gilman (mcgil...@apache.org)
* Tony Kurc (tk...@apache.org)
* Mark Payne (marka...@apache.org)
* Aldrin Piri (ald...@apache.org)
* Dan Bress (danbr...@apache.org)
* Jennifer Barnabee (jbarna...@apache.org)
* Joseph L. Witt (joew...@apache.org)
* Jason Carey (jca...@apache.org)
* Adam Taft (tafts...@apache.org)
* Benson Margulies (bimargul...@apache.org)
* Bryan Bende (bbe...@apache.org)

NOW, THEREFORE, BE IT FURTHER RESOLVED, that
Joseph L. Witt be appointed to the office of Vice President,
Apache NiFi, to serve in accordance with and subject to the
direction of the Board of Directors and the Bylaws of the
Foundation until death, resignation, retirement, removal or
disqualification, or until a successor is appointed;
and be it further

RESOLVED, that the initial Apache NiFi PMC be and hereby is
tasked with the creation of a set of bylaws intended to
encourage open development and increased participation in the
Apache NiFi Project; and be it further

RESOLVED, that the Apache NiFi Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator NiFi podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache
Incubator NiFi podling encumbered upon the Apache Incubator
Project are hereafter discharged.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSSION] Graduate NiFi from the Apache Incubator

[Joe Witt]

I was hoping to see how things settle out through the rest of the day
and then kick off a vote tomorrow or Wednesday.  We had hoped that if
all goes well we'd be an option for the July meeting.  So, no rush I
think.

Thanks
Joe

On Mon, Jun 15, 2015 at 11:47 AM, Andrew Purtell apurt...@apache.org wrote:
 72 hours is customary as minimum. That would miss the Board meeting this
 week.


 On Mon, Jun 15, 2015 at 8:44 AM, Sean Busbey bus...@cloudera.com wrote:

 It sounds like we have consensus. Is there a minimum voting period? Any
 chance we could get this through in time for the NiFi proposal to make the
 Board meeting this week?

 On Sun, Jun 14, 2015 at 12:26 PM, jan i j...@apache.org wrote:

  On 14 June 2015 at 17:52, Joe Witt joe.w...@gmail.com wrote:
 
   The community agreed on what we posted originally.  Just trying to be
   responsive to niclas concerns in the spirit of the discussion thread.
  
  I was not suggesting otherwise.
 
  
   I have forwarded the thread to our dev list which is where the
 adjustment
   to 'interactive' came from.  Should these minor rephrasings give pause
 in
   the nifi community we will pass that forward.
  
  +1
  rgds
  jan i.
 
 
 
   On Jun 14, 2015 11:33 AM, jan i j...@apache.org wrote:
  
Hi
   
Sorry for top posting, I do understand why the resolution is being
   changed,
however it this
really the correct place to do it. The community must be behind and
agreeing to the resolution,
so changes should in my opinion by discussed on your dev@ list.
   
The IPMC should be presented with a resolution that the community
  agrees
on.
   
rgds
jan i.
   
   
On 14 June 2015 at 17:18, Joe Witt joe.w...@gmail.com wrote:
   
 Adjusted to clarify the 'realtime' reference which can be
 misleading:


 WHEREAS, the Board of Directors deems it to be in the best
 interests of the Foundation and consistent with the
 Foundation's purpose to establish a Project Management
 Committee charged with the creation and maintenance of
 open-source software, for distribution at no charge to
 the public, related to an automated and durable data broker
 between systems providing interactive command and control
 and detailed chain of custody for data.

 NOW, THEREFORE, BE IT RESOLVED, that a Project Management
 Committee (PMC), to be known as the Apache NiFi Project,
 be and hereby is established pursuant to Bylaws of the
 Foundation; and be it further

 RESOLVED, that the Apache NiFi Project be and hereby is
 responsible for the creation and maintenance of software
 related to an automated and durable data broker
 between systems providing interactive command and control
 and detailed chain of custody for data; and be it further

 ...

 On Sun, Jun 14, 2015 at 7:42 AM, Niclas Hedhman 
 nic...@hedhman.org
 wrote:
  It is less generic, but I think I am not in a position to
 determine
what
 is
  suitable. The community + mentors should be a better group to
  discuss
it.
 
  On Sun, Jun 14, 2015 at 9:55 PM, Joe Witt joe.w...@gmail.com
   wrote:
 
  Niclas,
 
  I agree that the scope could be improved.  It is a tough
 balancing
   act
  of course.  How would about this modification:
 
  WHEREAS, the Board of Directors deems it to be in the best
  interests of the Foundation and consistent with the
  Foundation's purpose to establish a Project Management
  Committee charged with the creation and maintenance of
  open-source software, for distribution at no charge to
  the public, related to an automated and durable data broker
  between systems providing realtime command and control
  and detailed chain of custody for data.
 
  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
  Committee (PMC), to be known as the Apache NiFi Project,
  be and hereby is established pursuant to Bylaws of the
  Foundation; and be it further
 
  RESOLVED, that the Apache NiFi Project be and hereby is
  responsible for the creation and maintenance of software
  related to an automated and durable data broker
  between systems providing realtime command and control
  and detailed chain of custody for data; and be it further
 
  ...
 
 
  Thanks
  Joe
 
  On Sat, Jun 13, 2015 at 10:25 PM, Niclas Hedhman 
   nic...@hedhman.org
  wrote:
   From the peanut gallery;
   Doesn't
   related to the automated and managed flow of information
between
   systems
   apply to at least half of all software out there?
  
   In other words, the scope is very wide, and could include
  anything
 from
   SNMP to Apache Mesos and much much

Re: [RESULT][VOTE] Graduate NiFi from the Apache Incubator

[Joe Witt]

Thanks Sean!  Benson put himself on the draft resolution today so I
think we're set on that front.

On Mon, Jun 15, 2015 at 1:39 PM, Sean Busbey bus...@cloudera.com wrote:
 I'd rather wait to get a position on the NiFi PMC because the community has
 decided that my involvement and contributions warrant the additional
 responsibility.

 Presuming the IPMC wants an ASF Member on the the NiFi PMC to ensure
 there's a guide with a binding vote, I'd personally prefer that it be one
 of the existing mentors of the project. I believe we already have
 volunteers to do so, so hopefully this won't cause a delay.

 -Sean

 On Fri, Jun 12, 2015 at 11:57 AM, Benson Margulies bimargul...@gmail.com
 wrote:

 Sean sure makes more sense than me.

 On Fri, Jun 12, 2015 at 12:35 PM, Joe Witt joe.w...@gmail.com wrote:
  Sean is one of those folks i referred to.  Id be an easy +1
  On Jun 12, 2015 9:24 AM, Andrew Purtell apurt...@apache.org wrote:
 
  As Sean says he's been engaged with the project while acting as mentor,
  IMHO beyond mentor-ly duties. If the NiFi folks will have him on the
  initial PMC and he's willing to join it, this should resolve the stated
  concerns.
 
 
  On Friday, June 12, 2015, Sean Busbey bus...@cloudera.com wrote:
 
   On Fri, Jun 12, 2015 at 9:40 AM, Bertrand Delacretaz 
   bdelacre...@apache.org javascript:;
wrote:
  
On Fri, Jun 12, 2015 at 3:53 PM, Sean Busbey bus...@cloudera.com
   javascript:; wrote:
 ...I have no reason to believe either my engagement or the PPMC's
willingness
 to reach out to or listen to what I have to say will change upon
 graduation, so I don't think they need a checkbox ASF member on
 the
initial
 PMC and I'd prefer they not add one...
   
It's not about ticking a checkbox - it's about an ASF member
 agreeing
to stay with the project to help here and there with things where
members can help.
   
   
  
   Understood. I can't speak for any other ASF member, but I'm already
  there,
   engaged, and planning to stay. I don't need a binding PMC vote to do
  that.
  
   --
   Sean
  
 
 
  --
  Best regards,
 
 - Andy
 
  Problems worthy of attack prove their worth by hitting back. - Piet Hein
  (via Tom White)
 

 -
 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

Re: [DISCUSSION] Graduate NiFi from the Apache Incubator

[Joe Witt]

Niclas,

I agree that the scope could be improved.  It is a tough balancing act
of course.  How would about this modification:

WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to
the public, related to an automated and durable data broker
between systems providing realtime command and control
and detailed chain of custody for data.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache NiFi Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

RESOLVED, that the Apache NiFi Project be and hereby is
responsible for the creation and maintenance of software
related to an automated and durable data broker
between systems providing realtime command and control
and detailed chain of custody for data; and be it further

...


Thanks
Joe

On Sat, Jun 13, 2015 at 10:25 PM, Niclas Hedhman nic...@hedhman.org wrote:
 From the peanut gallery;
 Doesn't
 related to the automated and managed flow of information between
 systems
 apply to at least half of all software out there?

 In other words, the scope is very wide, and could include anything from
 SNMP to Apache Mesos and much much more. I think the Board will be happier
 with a somewhat more narrow definition.

 Cheers
 Niclas


 On Sat, Jun 13, 2015 at 1:04 AM, jan i j...@apache.org wrote:

 thanks for the responses I will cast a +1 at vote time.

 sorry for asking the questions, but I was insecure.

 rgds
 jan i

 On Friday, June 12, 2015, Benson Margulies bimargul...@gmail.com wrote:

  Sean sure makes more sense than me.
 
  On Fri, Jun 12, 2015 at 12:35 PM, Joe Witt joe.w...@gmail.com
  javascript:; wrote:
   Sean is one of those folks i referred to.  Id be an easy +1
   On Jun 12, 2015 9:24 AM, Andrew Purtell apurt...@apache.org
  javascript:; wrote:
  
   As Sean says he's been engaged with the project while acting as
 mentor,
   IMHO beyond mentor-ly duties. If the NiFi folks will have him on the
   initial PMC and he's willing to join it, this should resolve the
 stated
   concerns.
  
  
   On Friday, June 12, 2015, Sean Busbey bus...@cloudera.com
  javascript:; wrote:
  
On Fri, Jun 12, 2015 at 9:40 AM, Bertrand Delacretaz 
bdelacre...@apache.org javascript:; javascript:;
 wrote:
   
 On Fri, Jun 12, 2015 at 3:53 PM, Sean Busbey bus...@cloudera.com
  javascript:;
javascript:; wrote:
  ...I have no reason to believe either my engagement or the
 PPMC's
 willingness
  to reach out to or listen to what I have to say will change upon
  graduation, so I don't think they need a checkbox ASF member on
  the
 initial
  PMC and I'd prefer they not add one...

 It's not about ticking a checkbox - it's about an ASF member
  agreeing
 to stay with the project to help here and there with things where
 members can help.


   
Understood. I can't speak for any other ASF member, but I'm already
   there,
engaged, and planning to stay. I don't need a binding PMC vote to do
   that.
   
--
Sean
   
  
  
   --
   Best regards,
  
  - Andy
  
   Problems worthy of attack prove their worth by hitting back. - Piet
 Hein
   (via Tom White)
  
 
  -
  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
  javascript:;
  For additional commands, e-mail: general-h...@incubator.apache.org
  javascript:;
 
 

 --
 Sent from My iPad, sorry for any misspellings.




 --
 Niclas Hedhman, Software Developer
 http://zest.apache.org - New Energy for Java

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSSION] Graduate NiFi from the Apache Incubator

[Joe Witt]

Adjusted to clarify the 'realtime' reference which can be misleading:


WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to
the public, related to an automated and durable data broker
between systems providing interactive command and control
and detailed chain of custody for data.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management
Committee (PMC), to be known as the Apache NiFi Project,
be and hereby is established pursuant to Bylaws of the
Foundation; and be it further

RESOLVED, that the Apache NiFi Project be and hereby is
responsible for the creation and maintenance of software
related to an automated and durable data broker
between systems providing interactive command and control
and detailed chain of custody for data; and be it further

...

On Sun, Jun 14, 2015 at 7:42 AM, Niclas Hedhman nic...@hedhman.org wrote:
 It is less generic, but I think I am not in a position to determine what is
 suitable. The community + mentors should be a better group to discuss it.

 On Sun, Jun 14, 2015 at 9:55 PM, Joe Witt joe.w...@gmail.com wrote:

 Niclas,

 I agree that the scope could be improved.  It is a tough balancing act
 of course.  How would about this modification:

 WHEREAS, the Board of Directors deems it to be in the best
 interests of the Foundation and consistent with the
 Foundation's purpose to establish a Project Management
 Committee charged with the creation and maintenance of
 open-source software, for distribution at no charge to
 the public, related to an automated and durable data broker
 between systems providing realtime command and control
 and detailed chain of custody for data.

 NOW, THEREFORE, BE IT RESOLVED, that a Project Management
 Committee (PMC), to be known as the Apache NiFi Project,
 be and hereby is established pursuant to Bylaws of the
 Foundation; and be it further

 RESOLVED, that the Apache NiFi Project be and hereby is
 responsible for the creation and maintenance of software
 related to an automated and durable data broker
 between systems providing realtime command and control
 and detailed chain of custody for data; and be it further

 ...


 Thanks
 Joe

 On Sat, Jun 13, 2015 at 10:25 PM, Niclas Hedhman nic...@hedhman.org
 wrote:
  From the peanut gallery;
  Doesn't
  related to the automated and managed flow of information between
  systems
  apply to at least half of all software out there?
 
  In other words, the scope is very wide, and could include anything from
  SNMP to Apache Mesos and much much more. I think the Board will be
 happier
  with a somewhat more narrow definition.
 
  Cheers
  Niclas
 
 
  On Sat, Jun 13, 2015 at 1:04 AM, jan i j...@apache.org wrote:
 
  thanks for the responses I will cast a +1 at vote time.
 
  sorry for asking the questions, but I was insecure.
 
  rgds
  jan i
 
  On Friday, June 12, 2015, Benson Margulies bimargul...@gmail.com
 wrote:
 
   Sean sure makes more sense than me.
  
   On Fri, Jun 12, 2015 at 12:35 PM, Joe Witt joe.w...@gmail.com
   javascript:; wrote:
Sean is one of those folks i referred to.  Id be an easy +1
On Jun 12, 2015 9:24 AM, Andrew Purtell apurt...@apache.org
   javascript:; wrote:
   
As Sean says he's been engaged with the project while acting as
  mentor,
IMHO beyond mentor-ly duties. If the NiFi folks will have him on
 the
initial PMC and he's willing to join it, this should resolve the
  stated
concerns.
   
   
On Friday, June 12, 2015, Sean Busbey bus...@cloudera.com
   javascript:; wrote:
   
 On Fri, Jun 12, 2015 at 9:40 AM, Bertrand Delacretaz 
 bdelacre...@apache.org javascript:; javascript:;
  wrote:

  On Fri, Jun 12, 2015 at 3:53 PM, Sean Busbey 
 bus...@cloudera.com
   javascript:;
 javascript:; wrote:
   ...I have no reason to believe either my engagement or the
  PPMC's
  willingness
   to reach out to or listen to what I have to say will change
 upon
   graduation, so I don't think they need a checkbox ASF member
 on
   the
  initial
   PMC and I'd prefer they not add one...
 
  It's not about ticking a checkbox - it's about an ASF member
   agreeing
  to stay with the project to help here and there with things
 where
  members can help.
 
 

 Understood. I can't speak for any other ASF member, but I'm
 already
there,
 engaged, and planning to stay. I don't need a binding PMC vote
 to do
that.

 --
 Sean

   
   
--
Best regards,
   
   - Andy
   
Problems worthy of attack prove their worth by hitting back. - Piet
  Hein
(via Tom White

Re: [DISCUSSION] Graduate NiFi from the Apache Incubator

[Joe Witt]

The community agreed on what we posted originally.  Just trying to be
responsive to niclas concerns in the spirit of the discussion thread.

I have forwarded the thread to our dev list which is where the adjustment
to 'interactive' came from.  Should these minor rephrasings give pause in
the nifi community we will pass that forward.
On Jun 14, 2015 11:33 AM, jan i j...@apache.org wrote:

 Hi

 Sorry for top posting, I do understand why the resolution is being changed,
 however it this
 really the correct place to do it. The community must be behind and
 agreeing to the resolution,
 so changes should in my opinion by discussed on your dev@ list.

 The IPMC should be presented with a resolution that the community agrees
 on.

 rgds
 jan i.


 On 14 June 2015 at 17:18, Joe Witt joe.w...@gmail.com wrote:

  Adjusted to clarify the 'realtime' reference which can be misleading:
 
 
  WHEREAS, the Board of Directors deems it to be in the best
  interests of the Foundation and consistent with the
  Foundation's purpose to establish a Project Management
  Committee charged with the creation and maintenance of
  open-source software, for distribution at no charge to
  the public, related to an automated and durable data broker
  between systems providing interactive command and control
  and detailed chain of custody for data.
 
  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
  Committee (PMC), to be known as the Apache NiFi Project,
  be and hereby is established pursuant to Bylaws of the
  Foundation; and be it further
 
  RESOLVED, that the Apache NiFi Project be and hereby is
  responsible for the creation and maintenance of software
  related to an automated and durable data broker
  between systems providing interactive command and control
  and detailed chain of custody for data; and be it further
 
  ...
 
  On Sun, Jun 14, 2015 at 7:42 AM, Niclas Hedhman nic...@hedhman.org
  wrote:
   It is less generic, but I think I am not in a position to determine
 what
  is
   suitable. The community + mentors should be a better group to discuss
 it.
  
   On Sun, Jun 14, 2015 at 9:55 PM, Joe Witt joe.w...@gmail.com wrote:
  
   Niclas,
  
   I agree that the scope could be improved.  It is a tough balancing act
   of course.  How would about this modification:
  
   WHEREAS, the Board of Directors deems it to be in the best
   interests of the Foundation and consistent with the
   Foundation's purpose to establish a Project Management
   Committee charged with the creation and maintenance of
   open-source software, for distribution at no charge to
   the public, related to an automated and durable data broker
   between systems providing realtime command and control
   and detailed chain of custody for data.
  
   NOW, THEREFORE, BE IT RESOLVED, that a Project Management
   Committee (PMC), to be known as the Apache NiFi Project,
   be and hereby is established pursuant to Bylaws of the
   Foundation; and be it further
  
   RESOLVED, that the Apache NiFi Project be and hereby is
   responsible for the creation and maintenance of software
   related to an automated and durable data broker
   between systems providing realtime command and control
   and detailed chain of custody for data; and be it further
  
   ...
  
  
   Thanks
   Joe
  
   On Sat, Jun 13, 2015 at 10:25 PM, Niclas Hedhman nic...@hedhman.org
   wrote:
From the peanut gallery;
Doesn't
related to the automated and managed flow of information
 between
systems
apply to at least half of all software out there?
   
In other words, the scope is very wide, and could include anything
  from
SNMP to Apache Mesos and much much more. I think the Board will be
   happier
with a somewhat more narrow definition.
   
Cheers
Niclas
   
   
On Sat, Jun 13, 2015 at 1:04 AM, jan i j...@apache.org wrote:
   
thanks for the responses I will cast a +1 at vote time.
   
sorry for asking the questions, but I was insecure.
   
rgds
jan i
   
On Friday, June 12, 2015, Benson Margulies bimargul...@gmail.com
   wrote:
   
 Sean sure makes more sense than me.

 On Fri, Jun 12, 2015 at 12:35 PM, Joe Witt joe.w...@gmail.com
 javascript:; wrote:
  Sean is one of those folks i referred to.  Id be an easy +1
  On Jun 12, 2015 9:24 AM, Andrew Purtell apurt...@apache.org
 javascript:; wrote:
 
  As Sean says he's been engaged with the project while acting
 as
mentor,
  IMHO beyond mentor-ly duties. If the NiFi folks will have him
 on
   the
  initial PMC and he's willing to join it, this should resolve
 the
stated
  concerns.
 
 
  On Friday, June 12, 2015, Sean Busbey bus...@cloudera.com
 javascript:; wrote:
 
   On Fri, Jun 12, 2015 at 9:40 AM, Bertrand Delacretaz 
   bdelacre

Re: [RESULT][VOTE] Graduate NiFi from the Apache Incubator

[Joe Witt]

Sean is one of those folks i referred to.  Id be an easy +1
On Jun 12, 2015 9:24 AM, Andrew Purtell apurt...@apache.org wrote:

 As Sean says he's been engaged with the project while acting as mentor,
 IMHO beyond mentor-ly duties. If the NiFi folks will have him on the
 initial PMC and he's willing to join it, this should resolve the stated
 concerns.


 On Friday, June 12, 2015, Sean Busbey bus...@cloudera.com wrote:

  On Fri, Jun 12, 2015 at 9:40 AM, Bertrand Delacretaz 
  bdelacre...@apache.org javascript:;
   wrote:
 
   On Fri, Jun 12, 2015 at 3:53 PM, Sean Busbey bus...@cloudera.com
  javascript:; wrote:
...I have no reason to believe either my engagement or the PPMC's
   willingness
to reach out to or listen to what I have to say will change upon
graduation, so I don't think they need a checkbox ASF member on the
   initial
PMC and I'd prefer they not add one...
  
   It's not about ticking a checkbox - it's about an ASF member agreeing
   to stay with the project to help here and there with things where
   members can help.
  
  
 
  Understood. I can't speak for any other ASF member, but I'm already
 there,
  engaged, and planning to stay. I don't need a binding PMC vote to do
 that.
 
  --
  Sean
 


 --
 Best regards,

- Andy

 Problems worthy of attack prove their worth by hitting back. - Piet Hein
 (via Tom White)

Re: [DISCUSSION] Graduate NiFi from the Apache Incubator

[Joe Witt]

Hello

 it would be nice to see a bit of statistics like number of releases in 
 incubator, growth in incubator…

Mailing lists:
The dev mailing list has 123 legit addresses on it and is quite active
for discussion, votes, feature ideas, etc..  We’ve just recently
created a user list as requested by non-developer users which is now
at 38.  We have 30 people who really like to get a ton of emails on
our commits list.

Releases:
We have produced three releases in the past 6 months with two
different release managers (RM).  Our project adheres rather strictly
to the letter and spirit of the licensing and legal guidance ensuring
that all source and runtime dependencies are properly accounted for in
the source release license and notice and ensuring that every binary
artifact produced also includes detailed and precise accounting in its
local license and notice.  We are now closing in on our fourth release
and I suspect we’ll level off around a monthly release cadence.  We've
put together detailed guidance for how to properly handle the
licensing that augments existing guidance and policy and we've also
created release guides to help ensure we can effectively RM and have
community members participate in the vote:

http://nifi.incubator.apache.org/release-guide.html
http://nifi.incubator.apache.org/licensing-guide.html

Commit Activity:
29 different people have committed to the codebase over the last 6
months with 14 different people committing in the past two months.
We’ve received over 67 PRs through Github including new features,
improvements to existing features, or bug fixes.

PPMC Growth:
We have added three new PPMC members as of the time of writing this
and we hope to announce our fourth new PPMC member within days.  We
see contribution in various forms from a significant number of folks.
And there are consistent contributions coming from a couple specific
people in the form of email activity, vote contributions, code
commits, and code review feedback that suggest our pipeline is strong.

Committer independence:
The graduation resolution proposal we put forward includes folks from
several different independent organizations including Requitest,
Twitter, iJet, US Gov, Onyx Consulting, and Onyara.

Should it be necessary we’re honored that some of our mentors are
happy to stay onboard.  While I think we’ve effectively demonstrated
awareness of and commitment to the Apache Way we recognize the value
of their experience.  And thank you to Benson and Sergio for already
offering.

Thanks
Joe

On Fri, Jun 12, 2015 at 6:53 AM, Sean Busbey bus...@cloudera.com wrote:
 On Fri, Jun 12, 2015 at 5:13 AM, Bertrand Delacretaz bdelacre...@apache.org
 wrote:

 On Fri, Jun 12, 2015 at 12:00 PM, jan i j...@apache.org wrote:
  ...one reason to be in incubator is to learn the apache way and that
   seems hard to learn without other apache people on the project...

 Not sure what you mean - the Nifi mentors have voted to graduate it,
 which indicates that they are confident that the project has learned
 how to operate as an Apache project.

 Still, in addition to acting as a liaison, having ASF members on the
 PMC is also a good way to have some form of post-graduation mentoring,
 when needed. Projects can always ask the board for advice, but when
 that advice is available in their PMC that's much better.



 I have been active on the project and thus far the PPMC has had no problem
 asking for feedback or getting (often unsolicited ;) ) advice, all without
 needing me to be on the PPMC.

 I have no reason to believe either my engagement or the PPMC's willingness
 to reach out to or listen to what I have to say will change upon
 graduation, so I don't think they need a checkbox ASF member on the initial
 PMC and I'd prefer they not add one.

 -Sean

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache NiFi 0.1.0-incubating

[Joe Witt]

Justin,

First, thanks for attempting to validate the release.  You will need
to build all three components mentioned above in order.  The error you
note suggests that the nifi-parent was not built before attempting the
build of nifi-0.1.0.

We expect most releases to be much easier to validate than this one
but we needed to factor out a common parent here to share across the
other two modules.  Our preference would be to have a single build
that does it all but that isn't possible when one of the artifacts you
want to build would also be an extension/plugin you'd use in maven in
that same build.

Regarding the email address used we will be sure to better reflect
that in our release guide.  The .zip is generated by the
'apache-release' profile that comes from the standard
org.apache/apache/16 artifact.  It uses a
'apache-source-release-assembly-descriptor' which only generates a
zip.  We could extend that but I'd be reluctant to.

Thanks
Joe

On Sat, May 16, 2015 at 11:19 PM, Justin Mclean justinmcl...@me.com wrote:
 Hi,

 +0 (binding) as I’m unable to get the release to compile.

 This may be my setup or perhaps an issue with the pom.xml file. When trying 
 to compile I get:
 The project org.apache.nifi:nifi:0.1.0-incubating 
 (/Users/justinmclean/Downloads/ApacheNiFi/nifi-0.1.0-incubating/pom.xml) has 
 1 error
 [ERROR] Non-resolvable parent POM: Could not find artifact 
 org.apache.nifi:nifi-parent:pom:1.0.0-incubating in central 
 (http://repo.maven.apache.org/maven2) and 'parent.relativePath' points at no 
 local POM @ line 18, column 13 - [Help 2]

 Any ideas?

 Everything else looks good:
 - Signatures and hashes correct
 - DISCLAIMER exists
 - LICENSE and NOTICE correct (I doubled check all licenses - nice work!)
 - No unexpected binary files (although there are some binary test files)
 - All source files have headers

 A couple of very minor things:
 - Consider signing release with an apache.org email. The signatures is fine 
 (and perhaps it's just me) but I‘m less likely to trust something signed with 
 “nam...@hotmail.com” style email address. :-)
 - Consider releasing a .tar.gz package as well as a .zip package
 -Consider (but not required) adding “apache to the artefact name.
 -The value of the scm tag (nifi-0.1.0-incubating-rc13”) in the pom file may 
 be incorrect.

 Thanks,
 Justin

 -
 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

Request to create a new mailing list for apache nifi

[Joe Witt]

Hello

The apache nifi dev list has had a few requests and discussions about
starting a user mailing list.  I submitted the JIRA request for it
today under here:

https://issues.apache.org/jira/browse/INFRA-9462

But was advised to have the PMC chair submit the request and by doing
so through this link:

https://infra.apache.org/officers/mlreq

Benson thought this appeared surprising but suggested i forward this
to the IPMC.

Can you help steer us in the proper direction so we can get

u...@nifi.incubator.apache.org established?

Thanks
Joe

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Request to create a new mailing list for apache nifi

[Joe Witt]

Can it be the same moderators as dev@nifi?

Believe that is myself (joewitt) and Tony Kurc (tkurc)

Thanks
Joe

On Fri, Apr 17, 2015 at 10:57 AM, Jake Farrell jfarr...@apache.org wrote:
 Who would you like as the moderators for the new list?

 -Jake

 On Fri, Apr 17, 2015 at 10:42 AM, Joe Witt joe.w...@gmail.com wrote:

 Hello

 The apache nifi dev list has had a few requests and discussions about
 starting a user mailing list.  I submitted the JIRA request for it
 today under here:

 https://issues.apache.org/jira/browse/INFRA-9462

 But was advised to have the PMC chair submit the request and by doing
 so through this link:

 https://infra.apache.org/officers/mlreq

 Benson thought this appeared surprising but suggested i forward this
 to the IPMC.

 Can you help steer us in the proper direction so we can get

 u...@nifi.incubator.apache.org established?

 Thanks
 Joe

 -
 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

Re: Request to create a new mailing list for apache nifi

[Joe Witt]

Gavin,

Appreciate your help.  I am doing exactly what you asked and following
the trail of guidance.

Thanks
Joe

On Fri, Apr 17, 2015 at 11:06 AM, Gavin McDonald ga...@16degrees.com.au wrote:

 On 17 Apr 2015, at 3:42 pm, Joe Witt joe.w...@gmail.com wrote:

 Hello

 The apache nifi dev list has had a few requests and discussions about
 starting a user mailing list.  I submitted the JIRA request for it
 today under here:

 https://issues.apache.org/jira/browse/INFRA-9462

 But was advised to have the PMC chair submit the request and by doing
 so through this link:

 https://infra.apache.org/officers/mlreq

 Benson thought this appeared surprising but suggested i forward this
 to the IPMC.

 Can you help steer us in the proper direction so we can get

 u...@nifi.incubator.apache.org established?

 Please follow what I said and get someone to use the mailing list request
 form. It allows infra to use a script.

 No idea why Benson is surprised, its been this way for months.

 Gav…


 Thanks
 Joe

 -
 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


-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[ANNOUNCE] Apache NiFi 0.0.2-incubating release

[Joe Witt]

Hello

The Apache NiFi team is excited to announce the release of Apache NiFi
0.0.2-incubating.

Apache NiFi is an easy to use, powerful, and reliable system to
process and distribute data.  Apache NiFi was made for dataflow.  It
supports highly configurable directed graphs of data routing,
transformation, and system mediation logic.

More details on Apache NiFi can be found here:
http://nifi.incubator.apache.org/

The release artifacts can be downloaded from here:
http://nifi.incubator.apache.org/downloads/

Maven artifacts have been made available here:
https://repository.apache.org/content/repositories/releases/org/apache/nifi/

Release notes available here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020version=12329373

Thank you
The Apache NiFi team


DISCLAIMER

Apache NiFi is an effort undergoing incubation at The Apache Software
Foundation (ASF), sponsored by  Apache Incubator. Incubation is
required of all newly accepted projects until a further review
indicates that the infrastructure, communications, and decision making
process have stabilized in a manner consistent with other successful
ASF projects. While incubation status is not necessarily a reflection
of the completeness or stability of the code, it does indicate that
the project has yet to be fully endorsed by the ASF.

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[RESULT][VOTE] Release Apache NiFi 0.0.2-incubating

[Joe Witt]

Hello,

The IPMC vote to release Apache NiFi 0.0.2-incubating passes.

The IPMC vote thread is here:
http://s.apache.org/nifi-0.0.2-ipmc-voteresult

Summary:
4 (binding) [+1]
0 [= 0]

The following binding +1 votes were received:
- Sergio Fernandez
- Justin Mclean
- Benson Margulies
- Billie Rinaldi

Feedback received during PPMC and IPMC votes on improving the release
package captured here:
https://issues.apache.org/jira/browse/NIFI-410

Thank you all very much!

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

[VOTE] Release Apache NiFi 0.0.2-incubating

[Joe Witt]

Hello

The Apache NiFi PPMC has voted to release Apache NiFi 0.0.2-incubating.
The vote was based on the release candidate described below.
We now request the IPMC to vote on the release.

Here is the PPMC voting result:

6 +1 (binding)
0 = 0 (binding)

Two of the +1 votes were from IPMC members.

Here is the PPMC vote thread: http://s.apache.org/0.0.2-vote

I am pleased to be calling this vote for the source release of Apache NiFi
nifi-0.0.2-incubating (RC1).

The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1023

The specific URL of the source zip is here:
https://repository.apache.org/service/local/repositories/orgapachenifi-1023/content/org/apache/nifi/nifi/0.0.2-incubating/nifi-0.0.2-incubating-source-release.zip

The Git tag is nifi-0.0.2-incubating-RC1
The Git commit ID is 22c6735126ed42dce33386e3ae31e0715d742c89
https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;a=commit;h=22c6735126ed42dce33386e3ae31e0715d742c89

Checksums of nifi-0.0.2-incubating-source-release.zip:
MD5: 1d542bb7259732bdbb1837ffb9553180
SHA1: b8877d9d190745a30d094c0b03be77f485c289fb

Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/joewitt.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/incubator/nifi/KEYS

66 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020version=12329373
* We need to review our adherence to semantic versioning principles
going forward.

The vote will be open for 72 hours.
Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test.
The please vote:

[ ] +1 Release this package as nifi-0.0.2-incubating
[ ] +0 no opinion
[ ] -1 Do not release this package because because...

Thanks!

-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [ANNOUNCE] Apache Streams 0.1-incubating release

[Joe Witt]

Julian

Take a look here:
http://incubator.apache.org/guides/releasemanagement.html#notes-disclaimer

Also in the checklist for things to validate
http://incubator.apache.org/guides/releasemanagement.html#check-list  It
calls out the disclaimer.

As a rep from a project that just finally cracked through on our first
release - very much understand what you're thinking right now.  Just stick
with it.

Thanks
Joe

On Tue, Feb 3, 2015 at 5:07 PM, Julian Hyde jh...@apache.org wrote:

 The Disclaimers section at
 http://incubator.apache.org/guides/branding.html says that the web site,
 documentation and releases should include a disclaimer. It does not say
 that the release announcement should include a disclaimer.

 Can someone please clarify?

 Julian


 On Feb 3, 2015, at 1:57 PM, Greg Stein gst...@gmail.com wrote:

 This release announcement does not contain the required DISCLAIMER
 necessary for all incubating projects.

 Please see:
  http://incubator.apache.org/guides/branding.html

 On Tue, Feb 3, 2015 at 12:27 PM, Steve Blackmon sblack...@apache.org
 wrote:

 I'm pleased to announce immediate availability of streams 0.1-incubating.

 Download links to the source code zip, md5, and asc are available from
 http://streams.incubator.apache.org.

 Steve Blackmon
 sblack...@apache.org

Re: [ANNOUNCE] Apache Streams 0.1-incubating release

[Joe Witt]

Steve,

I was under the impression that the comment was about the release itself
(not the announcement).   Only guidance I have found regarding the
announcement itself is:
http://incubator.apache.org/guides/releasemanagement.html#announcements  It
does contain a few TODOs though so there is likely some important
information not provided there yet.

Thanks
Joe



On Tue, Feb 3, 2015 at 6:09 PM, Steve Blackmon sblack...@apache.org wrote:

 Greg, Joe,

 I scanned both of those links and could not locate specific instructions
 regarding the text of a release announcement.

 My streams announcement from earlier today would have been in compliance
 if:
 a) a short description of the project was included in the body
 b) the project-specific incubator disclaimer (below) was included in the
 body

 True or False?

 Thanks,
 Steve Blackmon
 sblack...@apache.org

 -

 Disclaimer

 Apache Streams is an effort undergoing incubation at The Apache Software
 Foundation (ASF) sponsored by the Apache Incubator PMC. Incubation is
 required of all newly accepted projects until a further review indicates
 that the infrastructure, communications, and decision making process have
 stabilized in a manner consistent with other successful ASF projects. While
 incubation status is not necessarily a reflection of the completeness or
 stability of the code, it does indicate that the project has yet to be
 fully endorsed by the ASF.




 On Tue, Feb 3, 2015 at 4:45 PM, Joe Witt joe.w...@gmail.com wrote:

  Julian
 
  Take a look here:
 
 http://incubator.apache.org/guides/releasemanagement.html#notes-disclaimer
 
  Also in the checklist for things to validate
  http://incubator.apache.org/guides/releasemanagement.html#check-list  It
  calls out the disclaimer.
 
  As a rep from a project that just finally cracked through on our first
  release - very much understand what you're thinking right now.  Just
 stick
  with it.
 
  Thanks
  Joe
 
  On Tue, Feb 3, 2015 at 5:07 PM, Julian Hyde jh...@apache.org wrote:
 
   The Disclaimers section at
   http://incubator.apache.org/guides/branding.html says that the web
 site,
   documentation and releases should include a disclaimer. It does not say
   that the release announcement should include a disclaimer.
  
   Can someone please clarify?
  
   Julian
  
  
   On Feb 3, 2015, at 1:57 PM, Greg Stein gst...@gmail.com wrote:
  
   This release announcement does not contain the required DISCLAIMER
   necessary for all incubating projects.
  
   Please see:
http://incubator.apache.org/guides/branding.html
  
   On Tue, Feb 3, 2015 at 12:27 PM, Steve Blackmon sblack...@apache.org
   wrote:
  
   I'm pleased to announce immediate availability of streams
 0.1-incubating.
  
   Download links to the source code zip, md5, and asc are available from
   http://streams.incubator.apache.org.
  
   Steve Blackmon
   sblack...@apache.org
  
 

Re: [VOTE] Release Apache NiFI 0.0.1-incubating

[Joe Witt]

Billie

My concern with the dependencies file is the false sense of security it can
sometimes give.  These are dependencies for which Maven can find the
license information.  If it can't it isn't something that could be clearly
called out/articulated.  This is particularly true with a case like bundled
javascript dependencies.  I realize moving towards all externalized
dependencies is ideal but it is also not fail-proof.  Point taken thought
that they offer some utility in validating.

Will take a look at the Kafka licensing case.  Adding that to [
https://issues.apache.org/jira/browse/NIFI-291] now.

I went through every artifact personally including
nars/wars/javascript/etc... from raw source and the binary builds.  Kafka
though was indeed added after that.  Ideal case is the dev that adds it
takes care of rolling up as needed into overall LICENSE/NOTICE.  Then it is
on the R in RTC.  Then it is on the RM.  Then voters.  So that went right
past all phases.  Independent of the outstanding questions about binary
convenience packages does whatever specific license is missing from the
kafka bundle preclude us from providing a binary convenience package for
0.0.1?

Thanks
Joe

On Thu, Jan 29, 2015 at 10:10 AM, Billie Rinaldi bil...@apache.org wrote:

 On Thu, Jan 29, 2015 at 7:45 PM, Joe Witt joe.w...@gmail.com wrote:
  Will investigate how to have the build process for the convenience
 binaries
  not add the auto-generated dependencies file and for it to use our
 license
  rather than the stock one.

 I actually like the dependencies file.  It makes it easier to check over
 the license.
 Beware that the license does not currently cover all of the dependencies
 bundled in the nars/wars.  (As the license for the source package, it
 doesn't have to.)  The one I noticed was nifi-kafka-nar, but there could be
 others.

Re: [VOTE] Release Apache NiFI 0.0.1-incubating

[Joe Witt]

Billie,

Can you tell me specifically what you noticed in the Kafka bundle.  It
seems like we should be totally safe when depending on another Apache
Software Foundation project.  However, perhaps that is a dangerous
assumption.

I looked up Kafka's NOTICE and LICENSE file and appears to be the stock
one.  However, I then looked up the scala dependency which comes in from
using their client and it looks like a typical 3-clause BSD license which
should be called out in the overall license.  Will look further but would
like to know what you found as well.

Thanks
Joe

On Thu, Jan 29, 2015 at 10:23 AM, Joe Witt joe.w...@gmail.com wrote:

 Billie

 My concern with the dependencies file is the false sense of security it
 can sometimes give.  These are dependencies for which Maven can find the
 license information.  If it can't it isn't something that could be clearly
 called out/articulated.  This is particularly true with a case like bundled
 javascript dependencies.  I realize moving towards all externalized
 dependencies is ideal but it is also not fail-proof.  Point taken thought
 that they offer some utility in validating.

 Will take a look at the Kafka licensing case.  Adding that to [
 https://issues.apache.org/jira/browse/NIFI-291] now.

 I went through every artifact personally including
 nars/wars/javascript/etc... from raw source and the binary builds.  Kafka
 though was indeed added after that.  Ideal case is the dev that adds it
 takes care of rolling up as needed into overall LICENSE/NOTICE.  Then it is
 on the R in RTC.  Then it is on the RM.  Then voters.  So that went right
 past all phases.  Independent of the outstanding questions about binary
 convenience packages does whatever specific license is missing from the
 kafka bundle preclude us from providing a binary convenience package for
 0.0.1?

 Thanks
 Joe

 On Thu, Jan 29, 2015 at 10:10 AM, Billie Rinaldi bil...@apache.org
 wrote:

 On Thu, Jan 29, 2015 at 7:45 PM, Joe Witt joe.w...@gmail.com wrote:
  Will investigate how to have the build process for the convenience
 binaries
  not add the auto-generated dependencies file and for it to use our
 license
  rather than the stock one.

 I actually like the dependencies file.  It makes it easier to check over
 the license.
 Beware that the license does not currently cover all of the dependencies
 bundled in the nars/wars.  (As the license for the source package, it
 doesn't have to.)  The one I noticed was nifi-kafka-nar, but there could
 be
 others.

[RESULT][VOTE] Release Apache NiFI 0.0.1-incubating

[Joe Witt]

Hello,

The IPMC vote passes.

The IPMC vote thread is here:
http://s.apache.org/nifi-0.0.1-ipmc-voteresult

Summary:
6 (binding) [+1]
0 [= 0]

The following binding +1 votes were received:
- Sergio Fernandez
- Drew Farris
- Andrew Purtell
- Justin Mclean
- Benson Margulies
- Jan Iversen

All of the feedback on how to improve the release package as received
throughout both the PPMC and IPMC vote has been captured here:
https://issues.apache.org/jira/browse/NIFI-291

Thank you all very much!

Joe

Re: [VOTE] Release Apache NiFI 0.0.1-incubating

[Joe Witt]

Appreciate the feedback - understand the vote is still ongoing but wanted
to acknowledge the comments.

Will investigate how to have the build process for the convenience binaries
not add the auto-generated dependencies file and for it to use our license
rather than the stock one.  Will also look into options for making the
NOTICE file appear more customary with other projects.  Regarding the
license/notice being different for binary vs. source releases if anyone has
pointers to examples of this that would be helpful.  As it is right now
while I do agree it is complex it does also appear to consistent with the
ASF guidance found regarding license/notice handling.  If there is an
easier and less complex way we'd love to do that.

Thanks!
Joe

On Wed, Jan 28, 2015 at 6:40 PM, Benson Margulies bimargul...@gmail.com
wrote:

 On Wed, Jan 28, 2015 at 6:05 PM, jan i j...@apache.org wrote:
  +1 (binding)
 
  I am a bit confused about the mangling of license/notice files in respect
  of the source/binary releases.
 
  Can I please ask you to make a clear distinction between source and
 binary
  (which is not official ASF release) in the next release.
 
  On  side note, I am still not quite comfortable having binary releases,
 we
  (the incubator in general) need a discussion on how we look at jar files,
  they are not really object files (as from C/C++) but they are still
 binary.
  I acknowledge and DO NOT dispute the fact that java projects needs this.

 Jan, I'm not sure  precisely what you are uncomfortable about, but I
 note that
 http://www.apache.org/dev/publishing-maven-artifacts.html#staging-maven
 is official. The Apache Maven Project, just to cite an example, puts
 up several releases a month like this. We run the release plugin, it
 produces the 'official source release' bundle which is cited in the
 vote, and it also stages the binaries. All of this is staged in
 repository.apache.org. Maybe the correct response is, 'You don't look
 at binary files. The only thing up for a vote is the official source
 release bundle referenced specifically in the vote email. Pay No
 Attention To The Convenience Items Behind the Curtain.'

 If you are discomfortable with this, I think it would be helpful if
 you would raise this on comdev or some other venue that applies to the
 Foundation as a whole, so as not to end up accidently seeming to hold
 podlings to standards different than the project communities.

 regards,
 benson





 
  rgds
  jan I.
 
 
 
  On 28 January 2015 at 23:42, Billie Rinaldi bil...@apache.org wrote:
 
  The source artifacts look good.  The nar and war files deployed in the
  orgapachenifi-1022 repository seem to have default LICENSE files that
 don't
  have license info for their bundled dependencies, but they do all have
  DEPENDENCIES files listing this information.  I haven't worked with
 these
  dependencies files before.  Are they sufficient for communicating
 license
  information?
 
  On Mon, Jan 26, 2015 at 7:33 PM, Joe Witt joe.w...@gmail.com wrote:
   Hello
  
   The Apache NiFi (incubating) team is pleased to be calling this vote
 for
   the source release of Apache
   NiFi 0.0.1-incubating.
  
   With six binding (in the ppmc sense) +1 votes and no dissenting votes
 the
   PPMC has approved the vote for the release in this thread:
  
   http://s.apache.org/nifi-rc3
  
   We now ask the IPMC to vote for this release.
  
   Since this is our first release as part of the Apache Incubator it
 will
  be
   slightly unique because we need to release two components.
  
   The first component is the 'nifi-nar-maven-plugin' which allows us to
  build
   'NiFi Archives' which is part of our classloader isolation model.  The
   second is simply 'nifi' which is the full build and application that
 is
   'Apache NiFi (incubating)'.
  
   After this first release we expect to be releasing the
   'nifi-nar-maven-plugin' very rarely.
  
   So we'll break the information sections of this vote into two parts
 where
   one is for 'nifi-nar-maven-plugin' and the other 'nifi'.
  
   For the 'nifi-nar-maven-plugin'
   --
   The source zip, including signatures, digests, etc. can be found at:
   https://repository.apache.org/content/repositories/orgapachenifi-1021
  
   The specific repository path in that staging repo is:
  
  
 
 
 orgapachenifi-1021/content/org/apache/nifi/nifi-nar-maven-plugin/1.0.0-incubating/
  
   The sources.zip is called
   'nifi-nar-maven-plugin-1.0.0-incubating-source-release.zip'
  
   The Git tag is nifi-nar-maven-plugin-1.0.0-incubating-RC3
  
   The Git commit ID is 6e69d99444e22772df300cd777096dc21a7c8e35
  
  
  
 
 
 https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;a=commit;h=6e69d99444e22772df300cd777096dc21a7c8e35
  
   Checksums of nar-maven-plugin-1.0.0-incubating-source-release.zip:
   MD5: 2681be25c32a45df07fbac59f768c5d2
   SHA1: 1e6057e07c32a7a0208afdc36e7ce725bd9935e4
  
   7 issues were closed/resolved for this release

[VOTE] Release Apache NiFI 0.0.1-incubating

[Joe Witt]

Hello

The Apache NiFi (incubating) team is pleased to be calling this vote for
the source release of Apache
NiFi 0.0.1-incubating.

With six binding (in the ppmc sense) +1 votes and no dissenting votes the
PPMC has approved the vote for the release in this thread:

http://s.apache.org/nifi-rc3

We now ask the IPMC to vote for this release.

Since this is our first release as part of the Apache Incubator it will be
slightly unique because we need to release two components.

The first component is the 'nifi-nar-maven-plugin' which allows us to build
'NiFi Archives' which is part of our classloader isolation model.  The
second is simply 'nifi' which is the full build and application that is
'Apache NiFi (incubating)'.

After this first release we expect to be releasing the
'nifi-nar-maven-plugin' very rarely.

So we'll break the information sections of this vote into two parts where
one is for 'nifi-nar-maven-plugin' and the other 'nifi'.

For the 'nifi-nar-maven-plugin'
--
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1021

The specific repository path in that staging repo is:
orgapachenifi-1021/content/org/apache/nifi/nifi-nar-maven-plugin/1.0.0-incubating/

The sources.zip is called
'nifi-nar-maven-plugin-1.0.0-incubating-source-release.zip'

The Git tag is nifi-nar-maven-plugin-1.0.0-incubating-RC3

The Git commit ID is 6e69d99444e22772df300cd777096dc21a7c8e35

https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;a=commit;h=6e69d99444e22772df300cd777096dc21a7c8e35

Checksums of nar-maven-plugin-1.0.0-incubating-source-release.zip:
MD5: 2681be25c32a45df07fbac59f768c5d2
SHA1: 1e6057e07c32a7a0208afdc36e7ce725bd9935e4

7 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020version=12329307


Note once you have completed the verification of the
'nifi-nar-maven-plugin' you will have
'nifi-nar-maven-plugin:1.0.0-incubating' in your local repo and thus you
can move on to the 'nifi' build below which depends on it.


For 'nifi'
-
The source zip, including signatures, digests, etc. can be found at:
https://repository.apache.org/content/repositories/orgapachenifi-1022

The specific repository path in that staging repo is:
orgapachenifi-1022/org/apache/nifi/nifi/0.0.1-incubating/

The sources.zip is called 'nifi-0.0.1-incubating-source-release.zip'

The Git tag is 'nifi-0.0.1-incubating-RC3'

The Git commit ID is 3a7625920866deaab1f3973fc4db0847d054a9b5

https://git-wip-us.apache.org/repos/asf?p=incubator-nifi.git;a=commit;h=3a7625920866deaab1f3973fc4db0847d054a9b5

Checksums of nifi-0.0.1-incubating-source-release.zip:
MD5: f421bb67a775b9ef7e29a34c08c538c1
SHA1: a04a3914d9e5a4455c1b503785a7772ab772816c

114 issues were closed/resolved for this release:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316020version=12329078

The following information applies to both the 'nifi-nar-maven-plugin' and
'nifi':


Release artifacts are signed with the following key:
https://people.apache.org/keys/committer/joewitt.asc

KEYS file available here:
https://dist.apache.org/repos/dist/release/incubator/nifi/KEYS

This vote will follow 'http://www.apache.org/foundation/voting.html' 'Votes
on Package Releases' guidelines.

The vote will be open for 72 hours.
Please download the release candidate and evaluate the necessary items
including checking hashes, signatures, build from source, and test.  Then
please vote:

[ ] +1 Release this package as Apache NiFi 0.0.1-incubating
[ ] +0 no opinion
[ ] -1 Do not release this package because because...

Re: [Incubator Wiki] Update of January2015 by JosephWitt

[Joe Witt]

John,

I am not quite sure how to do that.  Where can I find that?

The mentor list we have is from here:
http://incubator.apache.org/projects/nifi.html

Thanks
Joe

On Fri, Jan 2, 2015 at 3:09 PM, John D. Ament johndam...@apache.org wrote:

 Hi Joe,

 I see you updated your mentor sign off list.  This list now does not match
 what is in podlings.xml.  Please update podlings.xml to match this list, if
 these three were in fact added as mentors to your project.

 John

 On Fri Jan 02 2015 at 3:03:09 PM Apache Wiki wikidi...@apache.org wrote:

  Dear Wiki user,
 
  You have subscribed to a wiki page or wiki category on Incubator Wiki
  for change notification.
 
  The January2015 page has been changed by JosephWitt:
  https://wiki.apache.org/incubator/January2015?action=diffrev1=6rev2=7
 
 
Three most important issues to address in the move towards graduation:
 
  -   1.
  -   2.
  -   3.
  +   1. Produce an initial release.
  +   2. Grow our community beyond the initial set of committers.
  +   3. Establish rhythm for releases, review processes, and document how
  to most effectively bring on new committers.
 
Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?
 
  + Nothing we wish to raise at this time.
 
  -
  - How has the community developed since the last report?
  -
  -
  -
  - How has the project developed since the last report?
  + How has the community developed since the last report?
 
  + The dev mailing list has picked up 20 new e-mails since the last report
  and is now at 62 (commits has grown to 25).
  + At the suggestion of the community we've adopted a review-then-commit
  strategy which is designed to among other things help with community
  development.
  + We've received several patches from members outside the initial
  committer list including changes which dramatically improved our build
  process and provide new extensions.
 
  + How has the project developed since the last report?
 
  - Date of last release:
  + All of our current infrastructure needs are setup and things are
 working
  really well.  Our focus now is on working towards our first release which
  is 0.0.1 and presently
  + comprised of 85 JIRA issues the vast majority of which are resolved.
  We've conducted a thorough review of all source files to ensure proper
  license headers/notices/disclaimers
  + are present.  We've completed a thorough review and modification of the
  overall LICENSE and NOTICE files in preparation for release.  We've
  conducted the initial podling name search
  + and submitted the ticket for that analysis to be verified and
  confirmed.  Our main focus now is getting past the first release so we
 can
  do a better job of building the community.
 
  -   -XX-XX
 
  - When were the last committers or PMC members elected?
  + Date of last release:
 
  +   N/A
 
  + When were the last committers or PMC members elected?
  +
  + We have not grown the official committer list beyond the initial
  committer list.  Though there are a couple of folks who are committing
  fairly consistently now and a new member to join the dev mailing list
 that
  is very promising.
 
Signed-off-by:
 
  @@ -731, +737 @@
 
  [ ](nifi) Arvind Prabhakar
  [ ](nifi) Sergio Fernandez
  [ ](nifi) Benson Margulies
  +   [ ](nifi) Brock Noland
  +   [ ](nifi) Drew Farris
  +   [ ](nifi) Andrew Purtell
 
Shepherd/Mentor notes:
 
 
  -
  To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
  For additional commands, e-mail: cvs-h...@incubator.apache.org
 
 

Re: [Incubator Wiki] Update of January2015 by JosephWitt

[Joe Witt]

John,

Cool no problem.  I couldn't do it through raw svn for some reason i'll
look into.  But just did it via CMS.  So I think it is all good.

If not please advise.

Thanks
Joe

On Fri, Jan 2, 2015 at 3:21 PM, John D. Ament johndam...@apache.org wrote:

 Funny, because I had just started working on those instructions.

 http://incubator.apache.org/guides/ppmc.html

 The files mentioned under adding mentors, it looks like someone already
 updated projects/{podling}.xml (nifi.xml, to generate nifi.html).  The
 other file is this:
 http://svn.apache.org/repos/asf/incubator/public/trunk/content/podlings.xml


 On Fri Jan 02 2015 at 3:12:00 PM Joe Witt joe.w...@gmail.com wrote:

  John,
 
  I am not quite sure how to do that.  Where can I find that?
 
  The mentor list we have is from here:
  http://incubator.apache.org/projects/nifi.html
 
  Thanks
  Joe
 
  On Fri, Jan 2, 2015 at 3:09 PM, John D. Ament johndam...@apache.org
  wrote:
 
   Hi Joe,
  
   I see you updated your mentor sign off list.  This list now does not
  match
   what is in podlings.xml.  Please update podlings.xml to match this
 list,
  if
   these three were in fact added as mentors to your project.
  
   John
  
   On Fri Jan 02 2015 at 3:03:09 PM Apache Wiki wikidi...@apache.org
  wrote:
  
Dear Wiki user,
   
You have subscribed to a wiki page or wiki category on Incubator
 Wiki
for change notification.
   
The January2015 page has been changed by JosephWitt:
https://wiki.apache.org/incubator/January2015?action=
  diffrev1=6rev2=7
   
   
  Three most important issues to address in the move towards
  graduation:
   
-   1.
-   2.
-   3.
+   1. Produce an initial release.
+   2. Grow our community beyond the initial set of committers.
+   3. Establish rhythm for releases, review processes, and document
  how
to most effectively bring on new committers.
   
  Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to
 be
  aware of?
   
+ Nothing we wish to raise at this time.
   
-
- How has the community developed since the last report?
-
-
-
- How has the project developed since the last report?
+ How has the community developed since the last report?
   
+ The dev mailing list has picked up 20 new e-mails since the last
  report
and is now at 62 (commits has grown to 25).
+ At the suggestion of the community we've adopted a
 review-then-commit
strategy which is designed to among other things help with community
development.
+ We've received several patches from members outside the initial
committer list including changes which dramatically improved our
 build
process and provide new extensions.
   
+ How has the project developed since the last report?
   
- Date of last release:
+ All of our current infrastructure needs are setup and things are
   working
really well.  Our focus now is on working towards our first release
  which
is 0.0.1 and presently
+ comprised of 85 JIRA issues the vast majority of which are
 resolved.
We've conducted a thorough review of all source files to ensure
 proper
license headers/notices/disclaimers
+ are present.  We've completed a thorough review and modification of
  the
overall LICENSE and NOTICE files in preparation for release.  We've
conducted the initial podling name search
+ and submitted the ticket for that analysis to be verified and
confirmed.  Our main focus now is getting past the first release so
 we
   can
do a better job of building the community.
   
-   -XX-XX
   
- When were the last committers or PMC members elected?
+ Date of last release:
   
+   N/A
   
+ When were the last committers or PMC members elected?
+
+ We have not grown the official committer list beyond the initial
committer list.  Though there are a couple of folks who are
 committing
fairly consistently now and a new member to join the dev mailing list
   that
is very promising.
   
  Signed-off-by:
   
@@ -731, +737 @@
   
[ ](nifi) Arvind Prabhakar
[ ](nifi) Sergio Fernandez
[ ](nifi) Benson Margulies
+   [ ](nifi) Brock Noland
+   [ ](nifi) Drew Farris
+   [ ](nifi) Andrew Purtell
   
  Shepherd/Mentor notes:
   
   
-
To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
For additional commands, e-mail: cvs-h...@incubator.apache.org
   
   
  
 

Re: Running an experiment with pTLP

[Joe Witt]

Benson,

Speaking from within the nifi ppmc I'd be happy to try this.  Most of us in
the nifi ppmc (excluding the mentors) are quite new to Apache so we're
either perfect because we lack any of the biases or terrible because we're
too ignorant to the good and bad.  But I for one would be happy to help
however we can.

Thanks
Joe

On Mon, Dec 29, 2014 at 9:49 PM, Benson Margulies bimargul...@gmail.com
wrote:

 On Mon, Dec 29, 2014 at 6:14 PM, Roman Shaposhnik r...@apache.org wrote:
  Please note the change of subject.
 
  On Mon, Dec 29, 2014 at 6:28 AM, Rich Bowen rbo...@rcbowen.com wrote:
  On 12/19/2014 02:20 PM, Mattmann, Chris A (3980) wrote:
 
  What it would do however if we simply did away with the notion of the
  IPMC/Incubator/etc., is to return to the notion of pTLPs which were
  proposed earlier which I would most wholeheartedly support.
 
 
  Having read more, and understood more, and consumed more coffee ...
 
  I wonder if we might implement this proposal with one incoming project,
 as a
  test, under close observation by the board and the IPMC? Might be seen
 as
  grossly unfair by the project that remain in the old regime (or, who
 knows,
  maybe also by the test project), but it might give us some deeper
 insight
  into whether this fixes anything?
 
  This is very much what others were suggesting on the thread as well.
  Given that I'll be mentoring Zeppelin, I'd love to use that as a guinea
 pig.
  Provided, that I'd have some level of collaboration from the board.
  Perhaps between three of us (Chris, Rich and I) this is all we need.
 
  Thoughts?

 Any interest in a retroactive retrofit of NiFi?

 
  Thanks,
  Roman.
 
  -
  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

Re: P. An Excessive Fascination with the Apache Brand

[Joe Witt]

Hello

I am a very new participant in Apache and a member of the ppmc for apache
nifi (incubating).

So I thought it would be good to share that perspective for this
discussion...

In writing the NiFi proposal this section was honestly a bit awkward.  The
other sections are largely about providing information so the community
could better understand the project and they were intuitive in purpose.
But this 'fascination with the brand section' seemed more like a comment to
the new project.  It was clear there was past history that prompted the
need for such a section but there was little to draw on to truly appreciate
the intent and thus to write anything that felt truly genuine.

Perhaps this section would be better off written as a question: Does the
proposed podling intend to learn and follow the Apache Way and to
participate through appropriate discourse?  It is also reasonable to
include with the question examples or patterns of behavior which are
problematic as well as examples or patterns which best reflect the ideals.

Thanks
Joe

On Mon, Dec 22, 2014 at 8:37 AM, Sean Owen sro...@apache.org wrote:

 I was going to ask the same. I've seen ~5 proposals now, and was
 surprised to see how they all copied and pasted the same boilerplate
 to answer several points, including this stanza about risk of
 excessive fascination with the brand.

 I also suspect that there is excessive fascination, and that paying
 lip service to it as a risk is not really sufficient. That may be
 another discussion.

 But concretely: what about just asking proposers to not copy and paste
 past proposals? Surely it's not so much to ask the proposed project to
 address, individually and from scratch, the issues raised by the
 proposal process. Or, explicitly ask the proposal to address why the
 project should be part of the ASF, now -- that is, what *else* besides
 becoming Apache Foo is the motivation?

 On Mon, Dec 22, 2014 at 1:21 PM, Jim Jagielski j...@jagunet.com wrote:
  I was wondering... What we *REALLY* want are projects
  that are interested more in The Apache Way than in the
  Apache Brand. We need to make it more clear, somehow,
  that new projects want to enter the ASF because they
  approve of, and want to follow, the *how* of creating
  projects and communities. Lately, it appears, that we
  have graduated projects which are more interested in
  simply being able to add 'Apache' to their name, and
  then deride/minimize/ignore/dispute most/all of the
  aspects of The Apache Way which is what made the Apache
  brand so valuable and noteworthy.
 
  Maybe we need to change the proposal guide.
 
  -
  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

Re: [Incubator Wiki] Update of December2014 by JosephWitt

[Joe Witt]

It was requested by Benson.
On Dec 6, 2014 6:40 AM, John D. Ament johndam...@apache.org wrote:

 All,

 Please see below change by Joseph Witt.

 He signed off on the NiFi report on behalf of Benson.

 Is that generally considered to be OK?

 John

 On Fri Dec 05 2014 at 10:21:13 PM Apache Wiki wikidi...@apache.org
 wrote:

  Dear Wiki user,
 
  You have subscribed to a wiki page or wiki category on Incubator Wiki
  for change notification.
 
  The December2014 page has been changed by JosephWitt:
 
 https://wiki.apache.org/incubator/December2014?action=diffrev1=36rev2=37
 
  [X](nifi) Billie Rinaldi
  [X](nifi) Arvind Prabhakar
  [X](nifi) Sergio Fernández
  -   [x](nifi) Benson Margulies
  +   [X](nifi) Benson Margulies
  [ ](nifi) Drew Farris
  [ ](nifi) Brock Noland
  [X](nifi) Andrew Purtell
 
  -
  To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
  For additional commands, e-mail: cvs-h...@incubator.apache.org
 
 

Re: [Incubator Wiki] Update of December2014 by JosephWitt

[Joe Witt]

On the dev@nifi.I.a.o mailing list.
On Dec 6, 2014 7:14 AM, Joe Witt joe.w...@gmail.com wrote:

 It was requested by Benson.
 On Dec 6, 2014 6:40 AM, John D. Ament johndam...@apache.org wrote:

 All,

 Please see below change by Joseph Witt.

 He signed off on the NiFi report on behalf of Benson.

 Is that generally considered to be OK?

 John

 On Fri Dec 05 2014 at 10:21:13 PM Apache Wiki wikidi...@apache.org
 wrote:

  Dear Wiki user,
 
  You have subscribed to a wiki page or wiki category on Incubator Wiki
  for change notification.
 
  The December2014 page has been changed by JosephWitt:
 
 https://wiki.apache.org/incubator/December2014?action=diffrev1=36rev2=37
 
  [X](nifi) Billie Rinaldi
  [X](nifi) Arvind Prabhakar
  [X](nifi) Sergio Fernández
  -   [x](nifi) Benson Margulies
  +   [X](nifi) Benson Margulies
  [ ](nifi) Drew Farris
  [ ](nifi) Brock Noland
  [X](nifi) Andrew Purtell
 
  -
  To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
  For additional commands, e-mail: cvs-h...@incubator.apache.org
 
 

Re: [Incubator Wiki] Update of December2014 by JosephWitt

[Joe Witt]

The exact thread is here:
http://mail-archives.apache.org/mod_mbox/incubator-nifi-dev/201412.mbox/%3CCALJK9a7OzgKTNh0R9qpqD8_pCmOXpqN4yagQCSkTY6zQQayp3g%40mail.gmail.com%3E

Thanks
Joe

On Sat, Dec 6, 2014 at 7:15 AM, Joe Witt joe.w...@gmail.com wrote:

 On the dev@nifi.I.a.o mailing list.
 On Dec 6, 2014 7:14 AM, Joe Witt joe.w...@gmail.com wrote:

 It was requested by Benson.
 On Dec 6, 2014 6:40 AM, John D. Ament johndam...@apache.org wrote:

 All,

 Please see below change by Joseph Witt.

 He signed off on the NiFi report on behalf of Benson.

 Is that generally considered to be OK?

 John

 On Fri Dec 05 2014 at 10:21:13 PM Apache Wiki wikidi...@apache.org
 wrote:

  Dear Wiki user,
 
  You have subscribed to a wiki page or wiki category on Incubator Wiki
  for change notification.
 
  The December2014 page has been changed by JosephWitt:
 
 https://wiki.apache.org/incubator/December2014?action=diffrev1=36rev2=37
 
  [X](nifi) Billie Rinaldi
  [X](nifi) Arvind Prabhakar
  [X](nifi) Sergio Fernández
  -   [x](nifi) Benson Margulies
  +   [X](nifi) Benson Margulies
  [ ](nifi) Drew Farris
  [ ](nifi) Brock Noland
  [X](nifi) Andrew Purtell
 
  -
  To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
  For additional commands, e-mail: cvs-h...@incubator.apache.org
 
 

Re: [VOTE] accept NiFi into the incubator

[Joe Witt]

John,

I've added the volunteering mentors. Updated the IPMC membership status of
the mentors.  Updated the CLA status of the contributors.  I'll stop doing
so now though to avoid any confusion.

Thanks
Joe

On Sat, Nov 22, 2014 at 4:42 PM, John D. Ament john.d.am...@gmail.com
wrote:

 Is it me or has the proposal changed since the vote went out? Ideally we
 want the proposal to be final before sending the vote.

 John

 On Sat Nov 22 2014 at 11:09:52 AM Ted Dunning ted.dunn...@gmail.com
 wrote:

  +1 (binding)
 
 
 
  On Sat, Nov 22, 2014 at 1:49 AM, Joey Echeverria joe...@gmail.com
 wrote:
 
   +1 (non-binding)
  
   Great proposal!
   On Fri, Nov 21, 2014 at 16:22 Alan D. Cabrera l...@toolazydogs.com
   wrote:
  
+1 - binding
   
On Nov 21, 2014, at 10:55 AM, Benson Margulies 
 bimargul...@gmail.com
wrote:
   
 http://wiki.apache.org/incubator/NiFiProposal has elicited a
  cheerful
and
 positive conversation, so I offer this vote.

 Vote will be open for the usual 72 hours ...

 Here is my [+1]
   
   
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org
   
   
  
 

Re: [PROPOSAL] NiFi for Incubation

[Joe Witt]

Arvind

Thank you for offering to be a mentor.  The proposal has been updated.

Arvind Prabhakar (StreamSets) arvind at apache dot org

One of the comments we have received thus far is a potential concern of
whether multiple communities/projects can exist in similar problem areas.
Your background in Flume which solves similar problems to NiFi is a good
sign that multiple projects and communities can co-exist within the space
and even provide complimentary capability.

Thanks
Joe

On Thu, Nov 20, 2014 at 9:20 PM, Joe Witt joe.w...@gmail.com wrote:

 Josh,

 Really appreciate it and have updated the proposal.

 Thanks
 Joe

 On Thu, Nov 20, 2014 at 9:35 AM, Josh Elser els...@apache.org wrote:

 Very exciting stuff!

 Not presently on IPMC, but if you'd have me, I'd be happy to volunteer as
 a mentor. If so, I'll submit an application to join the IPMC and we can go
 from there.

 - Josh


 Joe Witt wrote:

 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


 = NiFi Proposal =

 == Abstract ==
 NiFi is a dataflow system based on the concepts of flow-based
 programming.

 == Proposal ==
 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 versus
 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

 == Background ==
 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 the
 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.

 == Rationale ==
 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-departmental, and
 inter-departmental flows.  NiFi fits well within the Apache Software
 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.

 == Initial Goals ==
* 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.

 == Current Status ==
 === Meritocracy ===
 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 perspectives as
 integration systems by their nature are always evolving.  We will
 actively seek help and encourage promotion of influence in the project
 through meritocracy.

 === Community ===
 Over the past several years, NiFi has developed a strong community of
 both developers and operators within the U.S. government.  We look
 forward to helping grow this to a broader base of industries

Re: [PROPOSAL] NiFi for Incubation

[Joe Witt]

Bertrand,

Understood.  I had noticed other proposals listing these folks as mentors
but also providing their IPMC status along side.  I'll do the same for now
and if they join the ipmc i'll update it and if they end up not doing so
will remove them.  If that is not reasonable then just let me know.

Thanks
Joe

On Fri, Nov 21, 2014 at 7:59 AM, Bertrand Delacretaz bdelacre...@apache.org
 wrote:

 Hi,

 On Fri, Nov 21, 2014 at 1:52 PM, Joe Witt joe.w...@gmail.com wrote:
 ...
  http://wiki.apache.org/incubator/NiFiProposal

 Note that AFAICS some of the nominated mentors are not members of the
 Incubator PMC [1] - they cannot be formal incubation mentors then.

 ASF members can join that PMC just by asking.

 ASF committers can be elected to that PMC with the support of ASF or
 Incubator PMC members, subject to an Incubator PMC vote, that can be
 discussed on the incubator private list.

 Others can help with mentoring activities of course - and that's a
 great way of eventually joining this PMC if you're not an ASF member.
 But they won't be listed as mentors on the proposal or podling status
 page.

 -Bertrand

 [1] http://people.apache.org/committers-by-project.html#incubator-pmc

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org

Re: [PROPOSAL] NiFi for Incubation

[Joe Witt]

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 els...@apache.org 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)​​,
 merely to suggest that Sean's concerns should not be dismissed as they
 were.


 On Fri, Nov 21, 2014 at 2:11 PM, Josh Elserels...@apache.org  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 Marguliesbimargul...@gmail.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 Busbeybus...@cloudera.com
 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:

   == Initial Goals ==

 One of these should be to grow the community outside of the current

 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.


   === Community ===

 Over the past several years, NiFi has developed a strong community of
 both developers and operators within the U.S. government.  We look
 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?


   === Orphaned Products ===

 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 this
 out
 as an
 independent issue is worthwhile.


   possible.  This environment includes widely accessible source code

 repositories, published artifacts, ticket tracking, and extensive
 documentation. We also encourage contributions and frequent debate
 and
 hold regular, collaborative discussions through e-mail, chat rooms,
 and in-person meet-ups.

  Do you anticipate any difficulties moving these established

 communication
 mechanisms to ASF public lists?

   === Documentation ===

 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 expanding
 the
 available documentation to cover things like installation, developer
 guide, frequently asked questions, best practices, and more.  This
 documentation will be posted to the NiFi wiki at apache.org.

  I 

Re: [PROPOSAL] NiFi for Incubation

[Joe Witt]

Andrew - I've updated the proposal to reflect you as a mentor.

  * Andrew Purtell (Salesforce) apurtell at apache dot org, IPMC Member

Thanks again

Joe

On Fri, Nov 21, 2014 at 5:29 PM, Joe Witt joe.w...@gmail.com 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 els...@apache.org 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)​​,
 merely to suggest that Sean's concerns should not be dismissed as they
 were.


 On Fri, Nov 21, 2014 at 2:11 PM, Josh Elserels...@apache.org  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 Marguliesbimargulies@gmail.
 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 Busbeybus...@cloudera.com
 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:

   == Initial Goals ==

 One of these should be to grow the community outside of the current

 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.


   === Community ===

 Over the past several years, NiFi has developed a strong community
 of
 both developers and operators within the U.S. government.  We look
 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?


   === Orphaned Products ===

 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 this
 out
 as an
 independent issue is worthwhile.


   possible.  This environment includes widely accessible source code

 repositories, published artifacts, ticket tracking, and extensive
 documentation. We also encourage contributions and frequent debate
 and
 hold regular, collaborative discussions through e-mail, chat rooms,
 and in-person meet-ups.

  Do you anticipate any difficulties moving these established

 communication
 mechanisms to ASF public lists?

   === Documentation ===

 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

Re: [PROPOSAL] NiFi for Incubation

[Joe Witt]

Hello

Thank you for all the feedback thus far.

Sean, Jan I,

I've adjusted the proposal for the goals, community, and documentation.

Thanks
Joe

On Thu, Nov 20, 2014 at 1:50 AM, Sean Busbey bus...@cloudera.com 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:

  == Initial Goals ==

 One of these should be to grow the community outside of the current 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.


  === Community ===
  Over the past several years, NiFi has developed a strong community of
  both developers and operators within the U.S. government.  We look
  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?


  === Orphaned Products ===
  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 this out
 as an
 independent issue is worthwhile.


  possible.  This environment includes widely accessible source code
  repositories, published artifacts, ticket tracking, and extensive
  documentation. We also encourage contributions and frequent debate and
  hold regular, collaborative discussions through e-mail, chat rooms,
  and in-person meet-ups.

 Do you anticipate any difficulties moving these established communication
 mechanisms to ASF public lists?

  === Documentation ===
  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 expanding the
  available documentation to cover things like installation, developer
  guide, frequently asked questions, best practices, and more.  This
  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 br...@cloudera.com 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.mattm...@jpl.nasa.gov wrote:
 
   This is *fan freakin¹ tastic* Sounds like an awesome  project and
   glad to hear a relationship to Tika! Awesome to see more government
   projects coming into the ASF!
  
   you already have a great set of mentors and I don¹t really have 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.mattm...@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 joe.w...@gmail.com
   Reply-To: general@incubator.apache.org general@incubator.apache.org
 
   Date: Thursday, November 20, 2014 at 3:02 AM
   To: general@incubator.apache.org general@incubator.apache.org
   Subject: [PROPOSAL] NiFi

Re: [PROPOSAL] NiFi for Incubation

[Joe Witt]

Hadrian

Yes there is a Software Grant Agreement.  NSA's tech transfer folks have
already sent that to Apache.

Given that we are coming from a closed source environment you won't find
much.  That is what this proposal is about though as we're working hard to
change that.

The github link you reference has no relationship to this project.

The relationship to Apache Camel will need to be explored further as NiFi
is often used in similar problem spaces (integration).  Camel is really
powerful in its core purpose and has an excellent community and a great
deal of maturity.  NiFi provides a complete dataflow application with a
major focus on the user experience, graphical creation and real-time
command and control of those flows.  It will be interesting as we progress
to see how we can best integrate with projects like Camel and I am looking
forward to hearing some of the thoughts and ideas the community comes up.

Thanks
Joe

On Thu, Nov 20, 2014 at 7:45 AM, Hadrian Zbarcea hzbar...@gmail.com wrote:

 Sounds exciting. I have a couple of questions:

 1. Is there a code grant? I assume so, the proposal states that the
 project is active since 2006. What I could find [1] doesn't seem to be it.
 2. What is the overlap with Apache Camel (if any)?

 Cheers,
 Hadrian


 [1] https://github.com/Nifi



 On 11/19/2014 09:02 PM, Joe Witt wrote:

 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


 = NiFi Proposal =

 == Abstract ==
 NiFi is a dataflow system based on the concepts of flow-based programming.

 == Proposal ==
 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 versus
 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

 == Background ==
 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 the
 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.

 == Rationale ==
 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-departmental, and
 inter-departmental flows.  NiFi fits well within the Apache Software
 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.

 == Initial Goals ==
* 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.

 == Current Status ==
 === Meritocracy ===
 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

Re: [PROPOSAL] NiFi for Incubation

[Joe Witt]

Josh,

Really appreciate it and have updated the proposal.

Thanks
Joe

On Thu, Nov 20, 2014 at 9:35 AM, Josh Elser els...@apache.org wrote:

 Very exciting stuff!

 Not presently on IPMC, but if you'd have me, I'd be happy to volunteer as
 a mentor. If so, I'll submit an application to join the IPMC and we can go
 from there.

 - Josh


 Joe Witt wrote:

 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


 = NiFi Proposal =

 == Abstract ==
 NiFi is a dataflow system based on the concepts of flow-based programming.

 == Proposal ==
 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 versus
 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

 == Background ==
 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 the
 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.

 == Rationale ==
 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-departmental, and
 inter-departmental flows.  NiFi fits well within the Apache Software
 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.

 == Initial Goals ==
* 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.

 == Current Status ==
 === Meritocracy ===
 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 perspectives as
 integration systems by their nature are always evolving.  We will
 actively seek help and encourage promotion of influence in the project
 through meritocracy.

 === Community ===
 Over the past several years, NiFi has developed a strong community of
 both developers and operators within the U.S. government.  We look
 forward to helping grow this to a broader base of industries.

 === Core Developers ===
 The initial core developers are employed by the National Security
 Agency and defense contractors.  We will work to grow the community
 among a more diverse set of developers and industries.

 === Alignment ===
  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

[PROPOSAL] NiFi for Incubation

[Joe Witt]

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


= NiFi Proposal =

== Abstract ==
NiFi is a dataflow system based on the concepts of flow-based programming.

== Proposal ==
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 versus
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

== Background ==
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 the
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.

== Rationale ==
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-departmental, and
inter-departmental flows.  NiFi fits well within the Apache Software
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.

== Initial Goals ==
  * 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.

== Current Status ==
=== Meritocracy ===
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 perspectives as
integration systems by their nature are always evolving.  We will
actively seek help and encourage promotion of influence in the project
through meritocracy.

=== Community ===
Over the past several years, NiFi has developed a strong community of
both developers and operators within the U.S. government.  We look
forward to helping grow this to a broader base of industries.

=== Core Developers ===
The initial core developers are employed by the National Security
Agency and defense contractors.  We will work to grow the community
among a more diverse set of developers and industries.

=== Alignment ===
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 and
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 makes
the Apache Incubator a good fit for 

[Request] Wiki Access

[Joe Witt]

Hello

Can I please have access to edit the wiki?  I'd like to submit a project
proposal.

I've already created a wiki user.

User: JosephWitt
Email:  joe dot witt at gmail dot com

Thanks
Joe

Re: [Request] Wiki Access

[Joe Witt]

Thanks Nick

On Tue, Nov 11, 2014 at 12:12 AM, Nick Burch apa...@gagravarr.org wrote:

 On Mon, 10 Nov 2014, Joe Witt wrote:

 Can I please have access to edit the wiki?  I'd like to submit a project
 proposal.


 Karma granted, good luck!

 Nick

 -
 To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 For additional commands, e-mail: general-h...@incubator.apache.org