Re: LICENSE info for ALv2, not ASF

[Alex Harui]

On 3/7/16, 2:38 PM, "Craig Russell"  wrote:

>>>Agreed.  Sebb's recommendation, AIUI, was to simply mention in LICENSE
>>> that there is a non-ASF AL bundle without copying the entire LICENSE.
>
>That’s what I was objecting to. LICENSE is for licenses. If notice is
>required, then use NOTICE.

Hmm.  It feels like maybe folks aren't actually reading the first link I
provided [1].  In it, sebb approves a patch to the how-to [2].  The how-to
currently recommends not placing 3rd party licenses in the LICENSE file
and instead using a template like:

This product bundles SuperWidget 1.2.3, which is available under a
"3-clause BSD" license.  For details, see deps/superwidget/.


In [1], the proposed patch is to use a similar template for non-ASF ALv2
bundles.  The text being added is, AIUI, not stuff we are supposed to put
in NOTICE.

Justin is technically correct that [2] does not clearly state to list
non-ASF ALv2 bundles using the template but it would if the patch had been
applied.  The patch would create a section that reads:

"Assuming once again that that the bundled dependency itself contains no
bundled subcomponents under other licenses and thus the ALv2 applies
uniformly to all files, there is no need to add another copy of the ALv2
license, but if the dependency is third-party, the LICENSE file should
include:

'Includes Foo V1.2 under the Apache License 2.0'"


I've been hoping someone braver than me would apply the patch, but now it
appears that Marvin is going to refresh the whole document, so maybe it
will finally get settled when his revision comes up for review.

Thanks,
-Alex

[1] http://s.apache.org/qDa
[2] http://www.apache.org/dev/licensing-howto.html


>
>Craig
>
>>> 
>>> -Alex
>> 
>> Got it. Thanks Alex & Craig for the clarifications.
>> 
>> -Steve
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>> 
>
>Craig L Russell
>Architect
>craig.russ...@oracle.com
>P.S. A good JDO? O, Gasp!
>
>
>
>
>
>
>-
>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: [DRAFT] - Incubator Board Report March 2016

[Justin Mclean]

Hi John,

> I've moved the podlings that had no report submitted to non-reporting and
> marked them as monthly.  I'm especially concerned about iota and Johnzon,
> one a brand new podling (maybe they shouldn't have reported this month?)

JFYI Iota has been slow to start up I’m not sure they would have anything to 
report.

Thanks,
Justin


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

Re: Short form IP clearance

[John D. Ament]

Just to follow up on this thread, were the changes ever completed?

On Sun, Nov 1, 2015 at 2:20 PM William A Rowe Jr 
wrote:

> On Sun, Nov 1, 2015 at 6:38 AM, Sam Ruby  wrote:
>
> > On Sun, Nov 1, 2015 at 7:20 AM, Marvin Humphrey 
> > wrote:
> > > On Sun, Nov 1, 2015 at 3:41 AM, John D. Ament 
> > wrote:
> > >> I don't think anyone in the incubator is begging to be responsible.
> We
> > >> just need a new process defined.
> > >
> > > Actually, since the Incubator continues to receive criticism for its
> > > role in IP Clearance, I specifically request that the Incubator be
> > > relieved of that role. If having the Incubator hold the power to
> > > "meddle" causes such alarm, the Board should find somebody else to do
> > > this work.
> >
> > I don't think we should be looking to the Board directly for this, we
> > should be looking to Legal Affairs to reaffirm, adjust, or revoke this
> > arrangement.
> >
>
> And Legal Affairs has tangential control over Incubator, but the board is
> responsible
> for the IPMC charter, so if you want to change the scope of this project,
> the board
> is the final arbiter.
>
> Some of this might be confusion over Incubator's role.  From memory,
> incubator
> generally didn't 'vote' on incoming other PMC code bases, but maintained
> the
> canonical list of imports (the format is this committee's creation and
> choice),
> and the general@i.a.o list was used to 'announce' the importation of
> external
> code bases.  If someone at g@i.a.o noticed something amiss, they are
> always
> welcome to point out whatever IP provenance issue they perceive to a
> receiving
> committee (often the IPMC itself for incubating code bases).
>
> If we trust the importing PMC to understand IP provenance, which we do
> because
> each of them maintain code bases, than this whole issue of IPMC non-voting
> vs. record keeping becomes much simpler.  Since the IPMC is good at
> specific
> things, such as recording entry to the ASF, it still seems like a smart
> place for
> the records.  The alternative seems like adding a converse to the attic
> project,
> perhaps we could title it Apache Doormat?
>
> > We have enough to worry about with our primary responsibility of
> > > incubating podlings. We don't need more reasons for powers-that-be to
> > > give us grief.
> >
> > The powers that be (a.k.a., the board) either need to reinstate Jim as
> > VP of Affairs or find a replacement, and then hold that individual
> > (and associated committee) accountable for revisiting this issue.
> >
>
> That's extra confusing, I don't see where in the prior meeting minutes or
> any
> other ASF resources where there is not an active VP Legal Affairs?  I think
> you are confusing process (act of resigning, recognition of a resignation,
> appointing a replacement) with the actual motivation for someone to hold
> a role.
>
> You did a nice job of reinforcing Marvin's concern about micromanagement.
> Reading this statement above and the tone you used, I personally wouldn't
> be keen to serve as an officer under your directatorship.  /boggle
>

Re: [DRAFT] - Incubator Board Report March 2016

[John D. Ament]

I've moved the podlings that had no report submitted to non-reporting and
marked them as monthly.  I'm especially concerned about iota and Johnzon,
one a brand new podling (maybe they shouldn't have reported this month?)
and the other a podling that was trying to graduate.  I'll reach out to
those communities separately.

I left the following reports in for now, without sign off.  They should be
removed before we submit the report to the board unless one of their
mentors can sign off on the reports:

- Kudu
- Myriad

Both are fine reports, so shouldn't be an issue to sign off on them.

Note that I signed off on the CommonsRDF report, but to be clear to
everyone, it is an acknowledgement that the podling is in danger of
retiring.

This month seems to have been a pretty big swing in mentors on projects.  I
think everyones realizing how busy they are.  For those mentors who have
resigned, if you could please update podlings.xml to indicate your
resignation that would be appreciated.

For any podling that may be suffering from a lack of mentorship, I would
suggest to please reach out to the IPMC for support, we have many trained
members who may be willing to give you a hand.

John

On Mon, Mar 7, 2016 at 2:15 PM John D. Ament  wrote:

> Hi all,
>
> I have some things I'm going to wrap up tonight.  But below is the current
> draft report.  I notice that there are still many missing podlings.
>
> - Atlas
> - Htrace
> - iota (new podling)
> - Johnzon (just raised a graduation vote)
> - OpenAz
> - Ranger
> - Sirona
> - Wave
>
> I'd like to hear from these podlings/mentors to understand where their
> reports are.
>
> John
>
>
> = Incubator PMC report for March 2016 =
> === Timeline ===
> ||Wed March 02 ||Podling reports due by end of day ||
> ||Sun March 06 ||Shepherd reviews due by end of day ||
> ||Sun March 06 ||Summary due by end of day ||
> ||Tue March 08 ||Mentor signoff due by end of day ||
> ||Wed March 09 ||Report submitted to Board ||
> ||Wed March 16 ||Board meeting ||
>
>
> === Shepherd Assignments ===
> ||Drew Farris ||Sirona ||
> ||John Ament ||Streams ||
> ||John Ament ||Wave ||
> ||Justin Mclean ||Metron ||
> ||P. Taylor Goetz ||Joshua ||
> ||P. Taylor Goetz ||Zeppelin ||
> ||P. Taylor Goetz ||log4cxx2 ||
> ||Timothy Chen ||Impala ||
> ||Timothy Chen ||Johnzon ||
> ||Timothy Chen ||MRQL ||
> ||[none] ||Atlas ||
> ||[none] ||Climate Model Diagnostic Analyzer ||
> ||[none] ||CommonsRDF ||
> ||[none] ||Fineract ||
> ||[none] ||HTrace ||
> ||[none] ||Kudu ||
> ||[none] ||Milagro ||
> ||[none] ||Myriad ||
> ||[none] ||OpenAz ||
> ||[none] ||Ranger ||
> ||[none] ||SAMOA ||
> ||[none] ||Sentry ||
> ||[none] ||Singa ||
> ||[none] ||Taverna ||
> ||[none] ||Toree ||
> ||[none] ||Trafodion ||
> ||[none] ||iota ||
>
>
> === Report content ===
> {{{
> Incubator PMC report for March 2016
>
> The Apache Incubator is the entry path into the ASF for projects and
> codebases wishing to become part of the Foundation's efforts.
>
> There are 52 podlings currently undergoing incubation.
>
> * Community
>
>   New IPMC members:
>
>   - Kathey Marsden
>   - Daniel John Debrunner
>
> * New Podlings
>
>   - Guacamole
>   - Joshua
>   - Quarks
>
> * Graduations
>
>   The board has motions for the following:
>
>   - Sentry
>
> * Releases
>
>   The following releases entered distribution during the month of
>   February:
>
>   2016-02-06 Apache Geode 1.0.0-incubating.M1
>   2016-02-07 Apache Apex v3.3.0-incubating
>   2016-02-11 Apache Wave 0.4.0-incubating
>   2016-02-11 Apache SystemML 0.9.0-incubating
>   2016-02-11 Apache TinkerPop 3.1.1-incubating
>   2016-02-20 Apache Johnzon 0.9.3-incubating
>   2016-02-25 Apache Kudu (incubating) 0.7.0
>   2016-02-26 Apache AsterixDB 0.8.8-incubating
>
> * IP Clearance
>
>
>
> * Legal / Trademarks
>
>   - There was substantial discussion on general@incubator about how
> challenging it is to produce compliant LICENSE and NOTICE files.
>
>   - A couple of podlings with runtime LGPL dependencies pledged to remove
> those dependencies before graduation but were permitted to make
> incubating releases in the meantime.  There was uncertainty as to
> whether VP Legal's approval was required; ultimately VP Legal appeared
> on general@incubator and approved the plans.
>
> * Infrastructure
>
>
>
> * Miscellaneous
>
>   - The Incubator's Retirement Guide has been substantially refreshed, and
> it should now be easier for a Mentor or other volunteer to perform the
> administrative steps to retire a podling.
>
> * Credits
>
>   - Report Manager: Marvin Humphrey
>
>  Summary of podling reports 
>
> * Still getting started at the Incubator
>
>   - Impala
>   - Joshua
>   - Milagro
>
> * Not yet ready to graduate
>
>   No release:
>
>   - CMDA
>   - Fineract
>   - log4cxx2
>   - Metron
>   - Toree
>
>   Community growth:
>
>   - Commons RDF
>   - Kudu
>   - Myriad
>   - SAMOA
>   - Singa
>   - Taverna
>   - 

Re: [VOTE] Release Apache Ranger 0.5.2 (incubating)

[John D. Ament]

Release contents look good, +1 from me.

Now about your missing board report...  Any comments?

John

On Sun, Mar 6, 2016 at 7:18 PM Madhan Neethiraj  wrote:

> Incubator PMC,
>
> Apologies for yet another location-change of the release artifacts. The
> artifacts are moved from https://dist.apache.org/repos/dist/release to
> https://dist.apache.org/repos/dist/dev; please use the new location given
> below. John - thanks for your guidance.
>
> Artifacts for this release are given below:
>   - Git tag for the release:
> https://git-wip-us.apache.org/repos/asf?p=incubator-ranger.git;a=shortlog;h=refs/tags/ranger-0.5.2-rc1
>   - Sources for the release:
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.2-incubating/apache-ranger-incubating-0.5.2.tar.gz
>   - Source release verification:
>   - PGP Signature:
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.2-incubating/apache-ranger-incubating-0.5.2.tar.gz.asc
>   - MD5/SHA  Hash:
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.2-incubating/apache-ranger-incubating-0.5.2.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
>
>
> Please review and vote.
>
> The vote will be open for at least 72 hours or until necessary number of
> votes is reached.
>   [  ] +1  approve
>   [  ] +0  no opinion
>   [  ] -1  disapprove (and reason why)
>
> Here is my +1 (non binding).
>
> There is already one binding +1 vote from Alan Gates.
>
>
>
> Thanks,
> Madhan
>
>
> 
> From: John D. Ament 
> Sent: Sunday, March 6, 2016 5:50 AM
> To: general@incubator.apache.org
> Subject: Re: [VOTE] Release Apache Ranger 0.5.2 (incubating)
>
> To clarify ( to avoid any possibility of confusion ), your release under
> vote goes to
>
> https://dist.apache.org/repos/dist/dev/incubator/ranger/
>
> Once its approved, it goes to
>
> https://dist.apache.org/repos/dist/release/incubator/ranger/
>
> In addition, you should keep both of these directories clean, dev only
> contains the release under vote, dist only contains the last successful
> release.
>
> John
>
>
>
>
>
>
> On 3/6/16, 5:45 AM, "Madhan Neethiraj"  wrote:
>
> >Incubator PMC,
> >
> >The release artifacts are now available under https://dist.apache.org.
> Please use the new locations given below.
> >
> >Artifacts for this release are given below:
> >  - Git tag for the release:
> https://git-wip-us.apache.org/repos/asf?p=incubator-ranger.git;a=shortlog;h=refs/tags/ranger-0.5.2-rc1
> >  - Sources for the release:
> https://dist.apache.org/repos/dist/release/incubator/ranger/0.5.2-incubating/apache-ranger-incubating-0.5.2.tar.gz
> >  - Source release verification:
> >- PGP Signature:
> https://dist.apache.org/repos/dist/release/incubator/ranger/0.5.2-incubating/apache-ranger-incubating-0.5.2.tar.gz.asc
> >- MD5/SHA  Hash:
> https://dist.apache.org/repos/dist/release/incubator/ranger/0.5.2-incubating/apache-ranger-incubating-0.5.2.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
> >
> >
> >
> >Thanks,
> >Madhan
> >
> >
> >
> >On 2/29/16, 3:44 PM, "Madhan Neethiraj"  wrote:
> >
> >>Incubator PMC,
> >>
> >>The Apache Ranger community has voted on and approved the proposal to
> release Apache Ranger 0.5.2 (incubating). The voting result is available at
> http://mail-archives.apache.org/mod_mbox/incubator-ranger-dev/201602.mbox/%3c62fd4d6f-2a7e-4b7a-b9ce-347f868c2...@apache.org%3e
> .
> >>
> >>Prior releases of Apache Ranger (incubating) are:
> >>  - Apache Ranger 0.5.1 Jan 2016
> >>  - Apache Ranger 0.5.0 Jul 2015
> >>  - Apache Ranger 0.4.0 Nov 2014
> >>
> >>
> >>Artifacts for this release are given below:
> >>  - Git tag for the release:
> https://git-wip-us.apache.org/repos/asf?p=incubator-ranger.git;a=shortlog;h=refs/tags/ranger-0.5.2-rc1
> >>  - Sources for the release:
> http://people.apache.org/~madhan/ranger/ranger-0.5.2-rc1/apache-ranger-incubating-0.5.2.tar.gz
> >>  - Source release verification:
> >>- PGP Signature:
> http://people.apache.org/~madhan/ranger/ranger-0.5.2-rc1/apache-ranger-incubating-0.5.2.tar.gz.asc
> >>- MD5/SHA  Hash:
> http://people.apache.org/~madhan/ranger/ranger-0.5.2-rc1/apache-ranger-incubating-0.5.2.tar.gz.mds
> >>- Keys to verify the signature of the release artifact are available
> at:  https://people.apache.org/keys/group/incubator.asc
> >>
> >>
> >>
> >>Please review and vote.
> >>
> >>
> >>The vote will be open for at least 72 hours or until necessary number of
> votes is reached.
> >>  [  ] +1  approve
> >>  [  ] +0  no opinion
> >>  [  ] -1  disapprove (and reason why)
> >>
> >>Here is my +1 (non binding).
> >>
> >>There is already one binding +1 vote from Alan Gates.
> >>
> >>Thanks
> >>Madhan
> >>
>
>
> 

Re: [VOTE] Release Apache Ranger 0.5.2 (incubating)

[Justin Mclean]

Hi,

+1 binding

I checked:
- name include incubating
- signature and hashes good
- disclaimer exits
- LICENSE is OK but missing a couple of licenses
- NOTICE has too much info
- A couple of files are missing Apache headers, for example [1][5][6]. There 
may be others.
- No unexpected binary files
- Can compile from source 

NOTICE should only include the first 4 lines of test there’s no need to repeat 
the copyrights here.

License is missing:
- Fontawesome (MIT and SIL) [3]
- Qunit (MIT) [7]
- Jquery migrate (MIT) [8]
- bootstrap [9] Probably MIT but depend on version used.
- jsDump (inside Qunit) BSD licensed
- Block UI (MIT) inside [10]

Please fix this for the next release.

I’m not sure how HijriCalendar.js [4] is licensed, assuming it permissive it 
will most likely need to be added to LICENSE.

Thanks,
Justin

1. migration-util/ambari2.0-hdp2.2-ranger0.40/bin/import_ranger_to_ambari.py
2. migration-util/ambari2.1-hdp2.3-ranger0.50/bin/import_ranger_to_ambari.py
3. security-admin/src/main/webapp/fonts/fontawesome/fontawesome-webfont.svg
4. 
security-admin/src/main/webapp/libs/bower/globalize/generator/HijriCalendar.js
5. 
apache-ranger-incubating-0.5.1/security-admin/src/main/webapp/libs/bower/globalize/generator/StringExt.cs
6. 
security-admin/src/main/webapp/libs/bower/globalize/generator/UmAlQuraCalendar.js
7. security-admin/src/main/webapp/libs/bower/globalize/test/qunit/qunit.js
8. security-admin/src/main/webapp/libs/bower/jquery/js/jquery-migrate.js
9. security-admin/src/main/webapp/themejs/1.3.0/bootstrap.min.js
10. security-admin/src/main/webapp/scripts/modules/XAOverrides.js


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

Re: [VOTE] Apache Kudu (incubating) 0.7.1 RC2

[Justin Mclean]

Hi,

+1 binding

I checked:
- signatures and hashes fine
- name contains incubating
- DISCLAIMER exists
- LICENSE and NOTICE good
- No unexpected binaries
- Source file have apache headers (some have extra ones)
- Can compile on OS X (but it takes a while)

I still think there’s a couple of minor issues with license.
- For instance the added text "The following dependencies or pieces of 
incorporated source code have licenses such that either:...” is IMO incorrect. 
For instance BSD requires license to be both in source and binary distributions.
- It’s unclear why the 1/2 dozen non Apache license software listed under this 
text are treated in a different way to the other bundled software.Wouldn’t it  
be better to be consistent and handle all licenses the same way?
- This file [1] isn’t BSD as noted in the license but a modified zlib, notice 
the clauses about modifications

There also looks to be some minor issues with Apache headers in several files

Several files have double Apache headers. For instance in src/kudu/util:
bit-stream-utils.h, bit-stream-utils.inline.h, bit-util-test.cc, bit-util.h, 
logging.cclogging.h, rle-encoding.h, rle-test.cc, url-coding-test.cc, 
url-coding.h

It also may be that Apache headers have been added to files that shouldn’t have 
them? For  Instance [2] is stated as BSD in the license file but has an Apache 
header. Was the original header removed? Also [3] has an Apache header but 
notes it's BSD licensed. These are not the only examples.

Thanks,
Justin

1. src/kudu/gutil/valgrind.h
2. src/kudu/util/random-util.cc
3. src/kudu/util/sync_point.cc
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: Copyright sign offs

[Stian Soiland-Reyes]

Basically http://incubator.apache.org/projects/datafu.html does not
include any timestamps for the sections Copyright and Verify
Distribution Right. So we don't know if this has happened or not.

In fact no dates appear in this particular incubator, so I guess it's
just not updated. Some email archive digging might be required to find
the right dates..

https://svn.apache.org/repos/asf/incubator/public/trunk/content/projects/datafu.xml
is the file to update.

On 7 March 2016 at 04:49, Roman Shaposhnik  wrote:
> Henri, it seems I'm a bit lost with your terminology. See the question bellow:
>
> On Fri, Feb 26, 2016 at 5:28 PM, Henri Yandell  wrote:
>> Haven't done this in a while :)
>>
>> Thought I'd share that the following podlings have not yet signed off on
>> their Copyright sections in their status reports.
>
> What does it mean exactly? For example...
>
>>   datafu
>
> ...what is the actionable item I need to bring up with this community?
>
>> I'd be interested to hear about any reasons why the above aren't able to
>> sign that element of their status file off.
>>
>> (same, but for those who are < 6 months in the incubator, ie) still working
>> on it)
>>
>>   fineract
>
> Ditto here.
>
> Thanks,
> Roman.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>



-- 
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/-0001-9842-9718

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

Re: [VOTE] Accept Tephra into the Apache Incubator

[Gangumalla, Uma]

+1 (non binding)

Regards,
Uma

On 3/3/16, 5:29 PM, "Poorna Chandra"  wrote:

>Hi All,
>
>Tephra proposal was sent out for discussion last week. The proposal is
>available at https://wiki.apache.org/incubator/TephraProposal
>
>Please vote to accept Tephra into the Apache Incubator. The vote will be
>open for the next 72 hours.
>
>[ ] +1 Accept Tephra as an Apache Incubator podling.
>[ ] +0 Abstain.
>[ ] -1 Don¹t accept Tephra as an Apache Incubator podling because ...
>
>Thanks,
>Poorna.
>
>--
>
>= Abstract =
>
>Tephra is a system for providing globally consistent transactions on
>top of Apache HBase and other storage engines.
>
>= Proposal =
>
>Tephra is a transaction engine for distributed data stores like Apache
>HBase.
>It provides ACID semantics for concurrent data operations that span over
>region
>boundaries in HBase using Optimistic Concurrency Control.
>
>= Background =
>
>HBase provides strong consistency with row- or region-level ACID
>operations. However, it sacrifices cross-region and cross-table
>consistency in favor of scalability. This trade-off requires application
>developers to handle  the complexity of ensuring consistency when their
>modifications span region boundaries. By providing support for global
>transactions that span regions, tables, or multiple RPCs,
>Tephra simplifies application development on top of HBase, without a
>significant impact on performance or scalability for many workloads.
>
>Tephra leverages HBase¹s native data versioning to provide multi-versioned
>concurrency control (MVCC) for transactional reads and writes.
>With MVCC capability, each transaction sees its own consistent ³snapshot²
>of
>data, providing snapshot isolation of concurrent transactions.
>MVCC along with conflict detection and handling enables Optimistic
>Concurrency
>Control.
>
>Tephra consists of three main components:
> * Transaction Server ­ maintains global view of transaction state,
>assigns
>   new transaction IDs and performs conflict detection;
> * Transaction Client ­ coordinates start, commit, and rollback of
>transactions; and
> * Transaction Processor Coprocessor ­ applies filtering to the data read
>(based
>   on a given transaction¹s state) and cleans up any data from old
>   (no longer visible) transactions.
>
>Although Tephra only supports HBase now, it can be extended to support
>transactions on any store that has multi-versioning and rollback
>support. The transactions
>can span over multiple stores and storage paradigms.
>
>= Rationale =
>
>Tephra has simple abstractions which can be used by an application to
>add transaction support over HBase. By abstracting away transaction
>handling using Tephra, the application is freed of
>transaction logic, and the application developer can focus on the use
>case.
>Also, Tephra can be extended to support transactions on data sources other
>than HBase.
>
>By making Tephra an Apache open source project, we believe that there will
>be wider adoption and more opportunities for Tephra to be integrated
>into other Apache projects.
>
>= Current Status =
>
>Tephra was built at Cask Data Inc. initially as part of
>open-source framework Cask Data Application Platform (CDAP)
>[[http://cdap.io/]].
>It was later converted into an independent open source project with
>Apache 2.0 License [[https://github.com/caskdata/tephra]].
>
>Tephra is used in CDAP as the transaction engine. As part of CDAP, Tephra
>has been deployed at multiple companies.
>
>Apache Phoenix is using Tephra as transaction engine in the next release.
>
>== Meritocracy ==
>
>Our intent with this incubator proposal is to start building a diverse
>developer community around Tephra following the Apache meritocracy model.
>Since Tephra was initially developed in early 2013, we have had fast
>adoption and contributions within Cask Data. We are looking forward to
>new contributors. We wish to build a community based on Apache's
>meritocracy principles, working with those who contribute significantly to
>the project and welcoming them to be committers both during the incubation
>process and beyond.
>
>== Community ==
>
>Core developers of Tephra are at Cask Data. Recently the developer
>community
>has expanded to include folks from Apache Phoenix. We hope to extend our
>contributor base significantly and we will invite all who are interested
>in working on distributed transaction engine.
>
>== Core Developers ==
>
>A few engineers from Cask Data and outside have developed Tephra:
>Andreas Neumann, Terence Yim, Gary Helmling, Andrew Purtell and
>Poorna Chandra.
>
>
>== Alignment ==
>
>The ASF is the natural choice to host the Tephra project as its goal of
>encouraging community-driven open source projects fits with our vision for
>Tephra.
>
>Additionally, many other projects with which we are familiar and expect
>Tephra to integrate with, such as Phoenix, Zookeeper, HDFS, log4j, and
>others
>mentioned in the External Dependencies section are Apache projects, and

Re: LICENSE info for ALv2, not ASF

[Craig Russell]

> On Mar 7, 2016, at 1:43 PM, Steve Varnau  wrote:
> 
>> From: Alex Harui [mailto:aha...@adobe.com]
>> Sent: Monday, March 7, 2016 1:09 PM
>> To: general@incubator.apache.org
>> Subject: Re: LICENSE info for ALv2, not ASF
>> 
>> On 3/7/16, 12:26 PM, "Craig Russell"  wrote:
>> 
>>> As I understand it, LICENSE is for licenses. Period. If advertising is
>>> required, the NOTICE file is used.
>> 
>> Sorry, I should have been more clear.  When I said "consider NOTICE" I
>> meant that any NOTICE for the non-ASF AL dependency may have content that
>> needs to into the NOTICE and not LICENSE.
>> 
>>> 
>>> If there are third party works included in a distribution that use the
>>> same Apache 2.0 license as any Apache components, the license file
>>> already contains the appropriate license.
>> 
>> Agreed.  Sebb's recommendation, AIUI, was to simply mention in LICENSE
>> that there is a non-ASF AL bundle without copying the entire LICENSE.

That’s what I was objecting to. LICENSE is for licenses. If notice is required, 
then use NOTICE.

Craig

>> 
>> -Alex
> 
> Got it. Thanks Alex & Craig for the clarifications.
> 
> -Steve
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 

Craig L Russell
Architect
craig.russ...@oracle.com
P.S. A good JDO? O, Gasp!






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

Re: [VOTE] Release taverna-language-0.15.1-incubating-RC5 and taverna-osgi-0.2.1-incubating-RC5

[Justin Mclean]

Hi,

As the PPMC seem on top of the issue and know what needs to be done changing my 
vote to:
 +1 binding

Re mentoring sorry but I'm a little too much stretched as it is and can't take 
on another project to mentor.

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

RE: LICENSE info for ALv2, not ASF

[Steve Varnau]

> -Original Message-
> From: Justin Mclean [mailto:jus...@classsoftware.com]
> Sent: Monday, March 7, 2016 2:10 PM
> To: general@incubator.apache.org
> Subject: Re: LICENSE info for ALv2, not ASF
>
> HI,
>
> Current recommendation is not to include it [1] but it’s not an error to
> do so.
>
> Justin
>
> 1.http://www.apache.org/dev/licensing-howto.html#alv2-dep
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org

Good point. That section does make clear the distinction between the Apache
licensed SW and ASF SW.

Thanks,
-Steve

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

[RESULT][IP CLEARANCE] Apache Brooklyn - CLI

[Richard Downer]

This is the result thread for the IP Clearance vote started in this thread:
https://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3CCABQFKi1-VxhduAnn0BKewsDihWJP0kcBZ5KerWi%3DVXVjs-%2B5bQ%40mail.gmail.com%3E

No explicit binding votes were cast. As this is a lazy consensus vote,
this means that the Apache Brooklyn CLI has passed IP Clearance.

Some comments were raised on the vote thread. These comments have been
noted and clarifying notes added to the record. The comments made did
not affect the outcome of the vote.

Thank you to those who participated in this IP clearance vote.

Richard.


-- Forwarded message --
From: Richard Downer 
Date: 29 February 2016 at 21:19
Subject: [IP CLEARANCE] Apache Brooklyn - CLI
To: general@incubator.apache.org


Apache Brooklyn is receiving a code for a new CLI tool.

See http://incubator.apache.org/ip-clearance/brooklyn-cli.html

Please vote to approve this contribution.

This is a lazy consensus majority vote, open for at least 72 hours.

Thanks
Richard

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

Re: LICENSE info for ALv2, not ASF

[Justin Mclean]

HI, 

Current recommendation is not to include it [1] but it’s not an error to do so.

Justin

1.http://www.apache.org/dev/licensing-howto.html#alv2-dep
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

RE: LICENSE info for ALv2, not ASF

[Steve Varnau]

> From: Alex Harui [mailto:aha...@adobe.com]
> Sent: Monday, March 7, 2016 1:09 PM
> To: general@incubator.apache.org
> Subject: Re: LICENSE info for ALv2, not ASF
>
> On 3/7/16, 12:26 PM, "Craig Russell"  wrote:
>
> >As I understand it, LICENSE is for licenses. Period. If advertising is
> >required, the NOTICE file is used.
>
> Sorry, I should have been more clear.  When I said "consider NOTICE" I
> meant that any NOTICE for the non-ASF AL dependency may have content that
> needs to into the NOTICE and not LICENSE.
>
> >
> >If there are third party works included in a distribution that use the
> >same Apache 2.0 license as any Apache components, the license file
> >already contains the appropriate license.
>
> Agreed.  Sebb's recommendation, AIUI, was to simply mention in LICENSE
> that there is a non-ASF AL bundle without copying the entire LICENSE.
>
> -Alex

Got it. Thanks Alex & Craig for the clarifications.

-Steve

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

Re: LICENSE info for ALv2, not ASF

[Alex Harui]

On 3/7/16, 12:26 PM, "Craig Russell"  wrote:

>As I understand it, LICENSE is for licenses. Period. If advertising is
>required, the NOTICE file is used.

Sorry, I should have been more clear.  When I said "consider NOTICE" I
meant that any NOTICE for the non-ASF AL dependency may have content that
needs to into the NOTICE and not LICENSE.

>
>If there are third party works included in a distribution that use the
>same Apache 2.0 license as any Apache components, the license file
>already contains the appropriate license.

Agreed.  Sebb's recommendation, AIUI, was to simply mention in LICENSE
that there is a non-ASF AL bundle without copying the entire LICENSE.

-Alex

Re: LICENSE info for ALv2, not ASF

[Craig Russell]

As I understand it, LICENSE is for licenses. Period. If advertising is 
required, the NOTICE file is used.

If there are third party works included in a distribution that use the same 
Apache 2.0 license as any Apache components, the license file already contains 
the appropriate license.

Section 4 of the Apache 2.0 license discusses whether notice is required. All 
Apache distributions contain NOTICEs that call out Apache components. Does the 
third party distribution contain NOTICE requirements? Then the Apache 
distribution that includes the third party needs to contain the notice about 
the third party in its NOTICE.

Craig

> On Mar 7, 2016, at 12:06 PM, Alex Harui  wrote:
> 
> 
> On 3/7/16, 11:21 AM, "Steve Varnau"  wrote:
> 
>> Hi,
>> 
>> 
>> 
>> I’m compiling information for LICENSE file for a binary distribution.  We
>> (Trafodion) have a bundled dependency that is Apache-2.0 license, but not
>> part of ASF.  Do we need to call these out in the license file, or only
>> call out the things that are non-Apache-2.0?
> 
>> 
> Sebb says yes in [1], but IMO, it isn't wrong either way.  Make sure you
> consider the NOTICE file though.  Hopefully Marvin will nail this down one
> way or the other in the next revision of the how-to.
> 
> HTH,
> -Alex
> 
> [1] http://s.apache.org/qDa
> 
> 
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org

Craig L Russell
Secretary, Apache Software Foundation
c...@apache.org http://db.apache.org/jdo


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

Re: [VOTE] Graduation for Apache Johnzon

[Romain Manni-Bucau]

@John: thks, will do


Romain Manni-Bucau
@rmannibucau  |  Blog
 | Github  |
LinkedIn  | Tomitriber


2016-03-07 21:16 GMT+01:00 John D. Ament :

> Yes, you're missing a proposed charter, the name of the proposed VP, who
> the initial committers, initial PMC, etc.  Please review it carefully and
> work with your mentors to define all this stuff.
>
> John
>
> On Mon, Mar 7, 2016 at 2:52 PM Romain Manni-Bucau 
> wrote:
>
> > I did, the idea was to reuse asf charter (replacing ${PROJECT} by
> Johnzon),
> > ppmc vote was considered useless since everyone agreed and nobody
> objected
> > so we were at voting on IPMC step, did I miss something?
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Github <
> > https://github.com/rmannibucau> |
> > LinkedIn  | Tomitriber
> > 
> >
> > 2016-03-07 20:47 GMT+01:00 John D. Ament :
> >
> > > Romain,
> > >
> > > Please review the graduation guide:
> > > http://incubator.apache.org/guides/graduation.html
> > >
> > > John
> > >
> > > On Mon, Mar 7, 2016 at 2:42 PM Romain Manni-Bucau <
> rmannibu...@gmail.com
> > >
> > > wrote:
> > >
> > > > 2016-03-07 20:08 GMT+01:00 John D. Ament :
> > > >
> > > > > Usually graduation votes include things like the proposal.
> > > > >
> > > > > It seems like this wasn't particularly discussed on the dev list,
> and
> > > not
> > > > > voted on at the dev list...
> > > > >
> > > > >
> > > > Was not voted cause everyone agreed, it has been discussed twice and
> > > > acknowledged twice so a vote was not mandatory since there was a
> > > concensus
> > > > (
> > > >
> > > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-johnzon-dev/201603.mbox/browser
> > > > ).
> > > > Also Justin said we can just use the default ASF policy to graduate
> so
> > we
> > > > don't need our own. Should we still write it?
> > > >
> > > >
> > > > > John
> > > > >
> > > > > On Mon, Mar 7, 2016 at 1:55 PM Romain Manni-Bucau <
> > > > rmannibu...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Hi,
> > > > > >
> > > > > > We discussed on johnzon@ and the graduation is out next goal
> > (there
> > > > was
> > > > > > several threads but the one triggering this vote is
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-johnzon-dev/201603.mbox/browser
> > > > > > ).
> > > > > >
> > > > > > I'd ilke the IPMC to recommend the resolution to the Board and
> > > > therefore
> > > > > > I'm asking for a vote for it.
> > > > > >
> > > > > > [ ] +1 great!
> > > > > > [ ] +0 don't care
> > > > > > [ ] -1 cause...
> > > > > >
> > > > > > Thanks,
> > > > > > Romain
> > > > > >
> > > > >
> > > >
> > >
> >
>

Re: [VOTE] Graduation for Apache Johnzon

[John D. Ament]

Yes, you're missing a proposed charter, the name of the proposed VP, who
the initial committers, initial PMC, etc.  Please review it carefully and
work with your mentors to define all this stuff.

John

On Mon, Mar 7, 2016 at 2:52 PM Romain Manni-Bucau 
wrote:

> I did, the idea was to reuse asf charter (replacing ${PROJECT} by Johnzon),
> ppmc vote was considered useless since everyone agreed and nobody objected
> so we were at voting on IPMC step, did I miss something?
>
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Github <
> https://github.com/rmannibucau> |
> LinkedIn  | Tomitriber
> 
>
> 2016-03-07 20:47 GMT+01:00 John D. Ament :
>
> > Romain,
> >
> > Please review the graduation guide:
> > http://incubator.apache.org/guides/graduation.html
> >
> > John
> >
> > On Mon, Mar 7, 2016 at 2:42 PM Romain Manni-Bucau  >
> > wrote:
> >
> > > 2016-03-07 20:08 GMT+01:00 John D. Ament :
> > >
> > > > Usually graduation votes include things like the proposal.
> > > >
> > > > It seems like this wasn't particularly discussed on the dev list, and
> > not
> > > > voted on at the dev list...
> > > >
> > > >
> > > Was not voted cause everyone agreed, it has been discussed twice and
> > > acknowledged twice so a vote was not mandatory since there was a
> > concensus
> > > (
> > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-johnzon-dev/201603.mbox/browser
> > > ).
> > > Also Justin said we can just use the default ASF policy to graduate so
> we
> > > don't need our own. Should we still write it?
> > >
> > >
> > > > John
> > > >
> > > > On Mon, Mar 7, 2016 at 1:55 PM Romain Manni-Bucau <
> > > rmannibu...@apache.org>
> > > > wrote:
> > > >
> > > > > Hi,
> > > > >
> > > > > We discussed on johnzon@ and the graduation is out next goal
> (there
> > > was
> > > > > several threads but the one triggering this vote is
> > > > >
> > > > >
> > > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-johnzon-dev/201603.mbox/browser
> > > > > ).
> > > > >
> > > > > I'd ilke the IPMC to recommend the resolution to the Board and
> > > therefore
> > > > > I'm asking for a vote for it.
> > > > >
> > > > > [ ] +1 great!
> > > > > [ ] +0 don't care
> > > > > [ ] -1 cause...
> > > > >
> > > > > Thanks,
> > > > > Romain
> > > > >
> > > >
> > >
> >
>

Re: LICENSE info for ALv2, not ASF

[Alex Harui]

On 3/7/16, 11:21 AM, "Steve Varnau"  wrote:

>Hi,
>
>
>
>I’m compiling information for LICENSE file for a binary distribution.  We
>(Trafodion) have a bundled dependency that is Apache-2.0 license, but not
>part of ASF.  Do we need to call these out in the license file, or only
>call out the things that are non-Apache-2.0?

>
Sebb says yes in [1], but IMO, it isn't wrong either way.  Make sure you
consider the NOTICE file though.  Hopefully Marvin will nail this down one
way or the other in the next revision of the how-to.

HTH,
-Alex

[1] http://s.apache.org/qDa




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

[RESULT] [VOTE] Accept Tephra into the Apache Incubator

[Poorna Chandra]

Hi All,

Thanks to all who voted! The vote has passed with the following tallies:

+1 Binding (7 total)
Henry Saputra
James Taylor
Andrew Purtell
Jean-Baptiste Onofré
Alan Gates
Julian Hyde
Lars Hofhansl

+1 Non-binding (4 total)
Ramakrishna Vasudevan
Terence Yim
Andreas Neumann
Naresh Agarwal

We'll work with the mentors to get the project bootstrapped.

Thanks,
Poorna.

Re: [VOTE] Graduation for Apache Johnzon

[Romain Manni-Bucau]

I did, the idea was to reuse asf charter (replacing ${PROJECT} by Johnzon),
ppmc vote was considered useless since everyone agreed and nobody objected
so we were at voting on IPMC step, did I miss something?


Romain Manni-Bucau
@rmannibucau  |  Blog
 | Github  |
LinkedIn  | Tomitriber


2016-03-07 20:47 GMT+01:00 John D. Ament :

> Romain,
>
> Please review the graduation guide:
> http://incubator.apache.org/guides/graduation.html
>
> John
>
> On Mon, Mar 7, 2016 at 2:42 PM Romain Manni-Bucau 
> wrote:
>
> > 2016-03-07 20:08 GMT+01:00 John D. Ament :
> >
> > > Usually graduation votes include things like the proposal.
> > >
> > > It seems like this wasn't particularly discussed on the dev list, and
> not
> > > voted on at the dev list...
> > >
> > >
> > Was not voted cause everyone agreed, it has been discussed twice and
> > acknowledged twice so a vote was not mandatory since there was a
> concensus
> > (
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-johnzon-dev/201603.mbox/browser
> > ).
> > Also Justin said we can just use the default ASF policy to graduate so we
> > don't need our own. Should we still write it?
> >
> >
> > > John
> > >
> > > On Mon, Mar 7, 2016 at 1:55 PM Romain Manni-Bucau <
> > rmannibu...@apache.org>
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > We discussed on johnzon@ and the graduation is out next goal (there
> > was
> > > > several threads but the one triggering this vote is
> > > >
> > > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-johnzon-dev/201603.mbox/browser
> > > > ).
> > > >
> > > > I'd ilke the IPMC to recommend the resolution to the Board and
> > therefore
> > > > I'm asking for a vote for it.
> > > >
> > > > [ ] +1 great!
> > > > [ ] +0 don't care
> > > > [ ] -1 cause...
> > > >
> > > > Thanks,
> > > > Romain
> > > >
> > >
> >
>

Re: [VOTE] Graduation for Apache Johnzon

[John D. Ament]

Romain,

Please review the graduation guide:
http://incubator.apache.org/guides/graduation.html

John

On Mon, Mar 7, 2016 at 2:42 PM Romain Manni-Bucau 
wrote:

> 2016-03-07 20:08 GMT+01:00 John D. Ament :
>
> > Usually graduation votes include things like the proposal.
> >
> > It seems like this wasn't particularly discussed on the dev list, and not
> > voted on at the dev list...
> >
> >
> Was not voted cause everyone agreed, it has been discussed twice and
> acknowledged twice so a vote was not mandatory since there was a concensus
> (
>
> http://mail-archives.apache.org/mod_mbox/incubator-johnzon-dev/201603.mbox/browser
> ).
> Also Justin said we can just use the default ASF policy to graduate so we
> don't need our own. Should we still write it?
>
>
> > John
> >
> > On Mon, Mar 7, 2016 at 1:55 PM Romain Manni-Bucau <
> rmannibu...@apache.org>
> > wrote:
> >
> > > Hi,
> > >
> > > We discussed on johnzon@ and the graduation is out next goal (there
> was
> > > several threads but the one triggering this vote is
> > >
> > >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-johnzon-dev/201603.mbox/browser
> > > ).
> > >
> > > I'd ilke the IPMC to recommend the resolution to the Board and
> therefore
> > > I'm asking for a vote for it.
> > >
> > > [ ] +1 great!
> > > [ ] +0 don't care
> > > [ ] -1 cause...
> > >
> > > Thanks,
> > > Romain
> > >
> >
>

Re: [VOTE] Graduation for Apache Johnzon

[Romain Manni-Bucau]

2016-03-07 20:08 GMT+01:00 John D. Ament :

> Usually graduation votes include things like the proposal.
>
> It seems like this wasn't particularly discussed on the dev list, and not
> voted on at the dev list...
>
>
Was not voted cause everyone agreed, it has been discussed twice and
acknowledged twice so a vote was not mandatory since there was a concensus (
http://mail-archives.apache.org/mod_mbox/incubator-johnzon-dev/201603.mbox/browser).
Also Justin said we can just use the default ASF policy to graduate so we
don't need our own. Should we still write it?


> John
>
> On Mon, Mar 7, 2016 at 1:55 PM Romain Manni-Bucau 
> wrote:
>
> > Hi,
> >
> > We discussed on johnzon@ and the graduation is out next goal (there was
> > several threads but the one triggering this vote is
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-johnzon-dev/201603.mbox/browser
> > ).
> >
> > I'd ilke the IPMC to recommend the resolution to the Board and therefore
> > I'm asking for a vote for it.
> >
> > [ ] +1 great!
> > [ ] +0 don't care
> > [ ] -1 cause...
> >
> > Thanks,
> > Romain
> >
>

LICENSE info for ALv2, not ASF

[Steve Varnau]

Hi,



I’m compiling information for LICENSE file for a binary distribution.  We
(Trafodion) have a bundled dependency that is Apache-2.0 license, but not
part of ASF.  Do we need to call these out in the license file, or only
call out the things that are non-Apache-2.0?



Thanks,

--Steve

[DRAFT] - Incubator Board Report March 2016

[John D. Ament]

Hi all,

I have some things I'm going to wrap up tonight.  But below is the current
draft report.  I notice that there are still many missing podlings.

- Atlas
- Htrace
- iota (new podling)
- Johnzon (just raised a graduation vote)
- OpenAz
- Ranger
- Sirona
- Wave

I'd like to hear from these podlings/mentors to understand where their
reports are.

John


= Incubator PMC report for March 2016 =
=== Timeline ===
||Wed March 02 ||Podling reports due by end of day ||
||Sun March 06 ||Shepherd reviews due by end of day ||
||Sun March 06 ||Summary due by end of day ||
||Tue March 08 ||Mentor signoff due by end of day ||
||Wed March 09 ||Report submitted to Board ||
||Wed March 16 ||Board meeting ||


=== Shepherd Assignments ===
||Drew Farris ||Sirona ||
||John Ament ||Streams ||
||John Ament ||Wave ||
||Justin Mclean ||Metron ||
||P. Taylor Goetz ||Joshua ||
||P. Taylor Goetz ||Zeppelin ||
||P. Taylor Goetz ||log4cxx2 ||
||Timothy Chen ||Impala ||
||Timothy Chen ||Johnzon ||
||Timothy Chen ||MRQL ||
||[none] ||Atlas ||
||[none] ||Climate Model Diagnostic Analyzer ||
||[none] ||CommonsRDF ||
||[none] ||Fineract ||
||[none] ||HTrace ||
||[none] ||Kudu ||
||[none] ||Milagro ||
||[none] ||Myriad ||
||[none] ||OpenAz ||
||[none] ||Ranger ||
||[none] ||SAMOA ||
||[none] ||Sentry ||
||[none] ||Singa ||
||[none] ||Taverna ||
||[none] ||Toree ||
||[none] ||Trafodion ||
||[none] ||iota ||


=== Report content ===
{{{
Incubator PMC report for March 2016

The Apache Incubator is the entry path into the ASF for projects and
codebases wishing to become part of the Foundation's efforts.

There are 52 podlings currently undergoing incubation.

* Community

  New IPMC members:

  - Kathey Marsden
  - Daniel John Debrunner

* New Podlings

  - Guacamole
  - Joshua
  - Quarks

* Graduations

  The board has motions for the following:

  - Sentry

* Releases

  The following releases entered distribution during the month of
  February:

  2016-02-06 Apache Geode 1.0.0-incubating.M1
  2016-02-07 Apache Apex v3.3.0-incubating
  2016-02-11 Apache Wave 0.4.0-incubating
  2016-02-11 Apache SystemML 0.9.0-incubating
  2016-02-11 Apache TinkerPop 3.1.1-incubating
  2016-02-20 Apache Johnzon 0.9.3-incubating
  2016-02-25 Apache Kudu (incubating) 0.7.0
  2016-02-26 Apache AsterixDB 0.8.8-incubating

* IP Clearance



* Legal / Trademarks

  - There was substantial discussion on general@incubator about how
challenging it is to produce compliant LICENSE and NOTICE files.

  - A couple of podlings with runtime LGPL dependencies pledged to remove
those dependencies before graduation but were permitted to make
incubating releases in the meantime.  There was uncertainty as to
whether VP Legal's approval was required; ultimately VP Legal appeared
on general@incubator and approved the plans.

* Infrastructure



* Miscellaneous

  - The Incubator's Retirement Guide has been substantially refreshed, and
it should now be easier for a Mentor or other volunteer to perform the
administrative steps to retire a podling.

* Credits

  - Report Manager: Marvin Humphrey

 Summary of podling reports 

* Still getting started at the Incubator

  - Impala
  - Joshua
  - Milagro

* Not yet ready to graduate

  No release:

  - CMDA
  - Fineract
  - log4cxx2
  - Metron
  - Toree

  Community growth:

  - Commons RDF
  - Kudu
  - Myriad
  - SAMOA
  - Singa
  - Taverna
  - Trafodion
  - Zeppelin

* Ready to graduate

  The Board has motions for the following:

  - Sentry

* Did not report, expected next month



--
   Table of Contents
Atlas
Climate Model Diagnostic Analyzer
CommonsRDF
Fineract
HTrace
Impala
iota
Johnzon
Joshua
Kudu
log4cxx2
Metron
Milagro
MRQL
Myriad
OpenAz
Ranger
SAMOA
Sentry
Singa
Sirona
Streams
Taverna
Toree
Trafodion
Wave
Zeppelin

--


Atlas

Apache Atlas is a scalable and extensible set of core foundational
governance services that enables enterprises to effectively and efficiently
meet their compliance requirements within Hadoop and allows integration with
the complete enterprise data ecosystem

Atlas has been incubating since 2015-05-05.

Three most important issues to address in the move towards graduation:

  1.
  2.
  3.

Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
aware of?



How has the community developed since the last report?



How has the project developed since the last report?



Date of last release:

  -XX-XX

When were the last committers or PMC members elected?



Signed-off-by:

  [ ](atlas) Arun Murthy
  [ ](atlas) Chris Douglas
  [ ](atlas) Jakob Homan
  [ ](atlas) Vinod Kumar Vavilapalli

Shepherd/Mentor notes:




Climate Model Diagnostic Analyzer

CMDA provides web services for multi-aspect physics-based and phenomenon-

Re: [VOTE] Graduation for Apache Johnzon

[John D. Ament]

Usually graduation votes include things like the proposal.

It seems like this wasn't particularly discussed on the dev list, and not
voted on at the dev list...

John

On Mon, Mar 7, 2016 at 1:55 PM Romain Manni-Bucau 
wrote:

> Hi,
>
> We discussed on johnzon@ and the graduation is out next goal (there was
> several threads but the one triggering this vote is
>
> http://mail-archives.apache.org/mod_mbox/incubator-johnzon-dev/201603.mbox/browser
> ).
>
> I'd ilke the IPMC to recommend the resolution to the Board and therefore
> I'm asking for a vote for it.
>
> [ ] +1 great!
> [ ] +0 don't care
> [ ] -1 cause...
>
> Thanks,
> Romain
>

Re: [VOTE] Release Apache Ranger 0.5.2 (incubating)

[Alan Gates]

Forwarding my +1 from the vote on the dev list.

Alan.

> On Mar 6, 2016, at 16:18, Madhan Neethiraj  wrote:
> 
> Incubator PMC,
> 
> Apologies for yet another location-change of the release artifacts. The 
> artifacts are moved from https://dist.apache.org/repos/dist/release to 
> https://dist.apache.org/repos/dist/dev; please use the new location given 
> below. John - thanks for your guidance.
> 
> Artifacts for this release are given below:
>  - Git tag for the release: 
> https://git-wip-us.apache.org/repos/asf?p=incubator-ranger.git;a=shortlog;h=refs/tags/ranger-0.5.2-rc1
>  - Sources for the release: 
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.2-incubating/apache-ranger-incubating-0.5.2.tar.gz
>  - Source release verification:
>  - PGP Signature:   
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.2-incubating/apache-ranger-incubating-0.5.2.tar.gz.asc
>  - MD5/SHA  Hash:  
> https://dist.apache.org/repos/dist/dev/incubator/ranger/0.5.2-incubating/apache-ranger-incubating-0.5.2.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
> 
> 
> Please review and vote.
> 
> The vote will be open for at least 72 hours or until necessary number of 
> votes is reached.
>  [  ] +1  approve
>  [  ] +0  no opinion
>  [  ] -1  disapprove (and reason why)
> 
> Here is my +1 (non binding).
> 
> There is already one binding +1 vote from Alan Gates.
> 
> 
> 
> Thanks,
> Madhan
> 
> 
> 
> From: John D. Ament 
> Sent: Sunday, March 6, 2016 5:50 AM
> To: general@incubator.apache.org
> Subject: Re: [VOTE] Release Apache Ranger 0.5.2 (incubating)
> 
> To clarify ( to avoid any possibility of confusion ), your release under
> vote goes to
> 
> https://dist.apache.org/repos/dist/dev/incubator/ranger/
> 
> Once its approved, it goes to
> 
> https://dist.apache.org/repos/dist/release/incubator/ranger/
> 
> In addition, you should keep both of these directories clean, dev only
> contains the release under vote, dist only contains the last successful
> release.
> 
> John
> 
> 
> 
> 
> 
> 
> On 3/6/16, 5:45 AM, "Madhan Neethiraj"  wrote:
> 
>> Incubator PMC,
>> 
>> The release artifacts are now available under https://dist.apache.org. 
>> Please use the new locations given below. 
>> 
>> Artifacts for this release are given below:
>> - Git tag for the release: 
>> https://git-wip-us.apache.org/repos/asf?p=incubator-ranger.git;a=shortlog;h=refs/tags/ranger-0.5.2-rc1
>> - Sources for the release: 
>> https://dist.apache.org/repos/dist/release/incubator/ranger/0.5.2-incubating/apache-ranger-incubating-0.5.2.tar.gz
>> - Source release verification:
>>   - PGP Signature:   
>> https://dist.apache.org/repos/dist/release/incubator/ranger/0.5.2-incubating/apache-ranger-incubating-0.5.2.tar.gz.asc
>>   - MD5/SHA  Hash:  
>> https://dist.apache.org/repos/dist/release/incubator/ranger/0.5.2-incubating/apache-ranger-incubating-0.5.2.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
>> 
>> 
>> 
>> Thanks,
>> Madhan
>> 
>> 
>> 
>> On 2/29/16, 3:44 PM, "Madhan Neethiraj"  wrote:
>> 
>>> Incubator PMC,
>>> 
>>> The Apache Ranger community has voted on and approved the proposal to 
>>> release Apache Ranger 0.5.2 (incubating). The voting result is available at 
>>> http://mail-archives.apache.org/mod_mbox/incubator-ranger-dev/201602.mbox/%3c62fd4d6f-2a7e-4b7a-b9ce-347f868c2...@apache.org%3e.
>>>  
>>> 
>>> Prior releases of Apache Ranger (incubating) are:
>>> - Apache Ranger 0.5.1 Jan 2016
>>> - Apache Ranger 0.5.0 Jul 2015
>>> - Apache Ranger 0.4.0 Nov 2014
>>> 
>>> 
>>> Artifacts for this release are given below:
>>> - Git tag for the release: 
>>> https://git-wip-us.apache.org/repos/asf?p=incubator-ranger.git;a=shortlog;h=refs/tags/ranger-0.5.2-rc1
>>> - Sources for the release: 
>>> http://people.apache.org/~madhan/ranger/ranger-0.5.2-rc1/apache-ranger-incubating-0.5.2.tar.gz
>>> - Source release verification:
>>>   - PGP Signature:   
>>> http://people.apache.org/~madhan/ranger/ranger-0.5.2-rc1/apache-ranger-incubating-0.5.2.tar.gz.asc
>>>   - MD5/SHA  Hash:  
>>> http://people.apache.org/~madhan/ranger/ranger-0.5.2-rc1/apache-ranger-incubating-0.5.2.tar.gz.mds
>>>   - Keys to verify the signature of the release artifact are available at:  
>>> https://people.apache.org/keys/group/incubator.asc
>>> 
>>> 
>>> 
>>> Please review and vote.
>>> 
>>> 
>>> The vote will be open for at least 72 hours or until necessary number of 
>>> votes is reached.
>>> [  ] +1  approve
>>> [  ] +0  no opinion
>>> [  ] -1  disapprove (and reason why)
>>> 
>>> Here is my +1 (non binding).
>>> 
>>> There is already one binding +1 vote from Alan Gates.
>>> 
>>> Thanks
>>> Madhan
>>> 
> 
> 
> 

[VOTE] Graduation for Apache Johnzon

[Romain Manni-Bucau]

Hi,

We discussed on johnzon@ and the graduation is out next goal (there was
several threads but the one triggering this vote is
http://mail-archives.apache.org/mod_mbox/incubator-johnzon-dev/201603.mbox/browser
).

I'd ilke the IPMC to recommend the resolution to the Board and therefore
I'm asking for a vote for it.

[ ] +1 great!
[ ] +0 don't care
[ ] -1 cause...

Thanks,
Romain

Re: [IP CLEARANCE] Apache Brooklyn - CLI

[Alex Harui]

Thanks Craig.  Richard, I would take Craig's answer as authorization to
proceed.

-Alex

On 3/7/16, 9:43 AM, "Craig Russell"  wrote:

>A software grant can only grant rights that are owned by the grantor.
>
>If there was a(n innocent) mistake in the file referenced by the grant,
>no big deal IMHO.
>
>Clearly, bundled dependencies cannot be included in a grant since the
>grantor has no rights to them. The fact that they were included in a file
>referenced by the grant has no relevance. Including them was just a
>mistake.
>
>No action needed IMHO since the intent is clear.
>
>Craig
>
>> On Mar 7, 2016, at 9:34 AM, Alex Harui  wrote:
>> 
>> 
>> 
>> On 3/7/16, 6:05 AM, "Richard Downer"  wrote:
>> 
>>> Alex, Justin, all,
>>> 
>>> Thank you for your comments. With your comments in mind, I will make
>>> this statement for the record:
>>> 
>>> Regarding the subject of the Software Grant Agreement, download link:
>>> 
>>>https://github.com/brooklyncentral/brooklyn-cli/archive/b8b39e54ecbb7c12
>>>f4
>>> 828783f07bec978a76b7be.zip
>>> SHA1: 5b5ef46c56adfff8ca86cca04694d5abc10ec447
>>> SHA256: 
>>>0cfaac11df7075c723bfb982ed5852d790fa195dcfe67c9bbbd545f34df71770
>>> 
>>> The folder 
>>>brooklyn-cli-b8b39e54ecbb7c12f4828783f07bec978a76b7be/br/Godeps
>>> is *excluded* from the code grant; this folder contains bundled
>>> dependencies licensed by 3rd parties using the MIT and BSD licenses.
>>> 
>>> With this folder removed from the ZIP file using the command zip -d
>>> FILENAME.zip 
>>> brooklyn-cli-b8b39e54ecbb7c12f4828783f07bec978a76b7be/br/Godeps\*,
>>> the hashes become:
>>> SHA1: 91fda2ca20c4b171985e1f5bb545ed8a236123dd
>>> SHA256: 
>>>4de28b308ad09f0e5642b4cefdd54b1c91b255fecd00184763a7d260bf8ec12d
>>> 
>>> I am updating the IP Clearance record with this same statement.
>>> 
>>> Is this sufficient notice for the record to address your comments?
>> 
>> I would hope it is sufficient, but I am not the person who can make the
>> call.  Other more senior folks may be able to make the call, but if you
>> want to be more sure, I would ask on legal-discuss if this is a
>>sufficient
>> way to update an SGA.
>> 
>> -Alex
>> 
>> 
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>
>Craig L Russell
>Secretary, Apache Software Foundation
>c...@apache.org http://db.apache.org/jdo
>
>
>-
>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: [IP CLEARANCE] Apache Brooklyn - CLI

[Craig Russell]

A software grant can only grant rights that are owned by the grantor.

If there was a(n innocent) mistake in the file referenced by the grant, no big 
deal IMHO.

Clearly, bundled dependencies cannot be included in a grant since the grantor 
has no rights to them. The fact that they were included in a file referenced by 
the grant has no relevance. Including them was just a mistake.

No action needed IMHO since the intent is clear. 

Craig

> On Mar 7, 2016, at 9:34 AM, Alex Harui  wrote:
> 
> 
> 
> On 3/7/16, 6:05 AM, "Richard Downer"  wrote:
> 
>> Alex, Justin, all,
>> 
>> Thank you for your comments. With your comments in mind, I will make
>> this statement for the record:
>> 
>> Regarding the subject of the Software Grant Agreement, download link:
>> https://github.com/brooklyncentral/brooklyn-cli/archive/b8b39e54ecbb7c12f4
>> 828783f07bec978a76b7be.zip
>> SHA1: 5b5ef46c56adfff8ca86cca04694d5abc10ec447
>> SHA256: 0cfaac11df7075c723bfb982ed5852d790fa195dcfe67c9bbbd545f34df71770
>> 
>> The folder brooklyn-cli-b8b39e54ecbb7c12f4828783f07bec978a76b7be/br/Godeps
>> is *excluded* from the code grant; this folder contains bundled
>> dependencies licensed by 3rd parties using the MIT and BSD licenses.
>> 
>> With this folder removed from the ZIP file using the command zip -d
>> FILENAME.zip 
>> brooklyn-cli-b8b39e54ecbb7c12f4828783f07bec978a76b7be/br/Godeps\*,
>> the hashes become:
>> SHA1: 91fda2ca20c4b171985e1f5bb545ed8a236123dd
>> SHA256: 4de28b308ad09f0e5642b4cefdd54b1c91b255fecd00184763a7d260bf8ec12d
>> 
>> I am updating the IP Clearance record with this same statement.
>> 
>> Is this sufficient notice for the record to address your comments?
> 
> I would hope it is sufficient, but I am not the person who can make the
> call.  Other more senior folks may be able to make the call, but if you
> want to be more sure, I would ask on legal-discuss if this is a sufficient
> way to update an SGA.
> 
> -Alex
> 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org

Craig L Russell
Secretary, Apache Software Foundation
c...@apache.org http://db.apache.org/jdo


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

Re: [IP CLEARANCE] Apache Brooklyn - CLI

[Alex Harui]

On 3/7/16, 6:05 AM, "Richard Downer"  wrote:

>Alex, Justin, all,
>
>Thank you for your comments. With your comments in mind, I will make
>this statement for the record:
>
>Regarding the subject of the Software Grant Agreement, download link:
>https://github.com/brooklyncentral/brooklyn-cli/archive/b8b39e54ecbb7c12f4
>828783f07bec978a76b7be.zip
>SHA1: 5b5ef46c56adfff8ca86cca04694d5abc10ec447
>SHA256: 0cfaac11df7075c723bfb982ed5852d790fa195dcfe67c9bbbd545f34df71770
>
>The folder brooklyn-cli-b8b39e54ecbb7c12f4828783f07bec978a76b7be/br/Godeps
>is *excluded* from the code grant; this folder contains bundled
>dependencies licensed by 3rd parties using the MIT and BSD licenses.
>
>With this folder removed from the ZIP file using the command zip -d
>FILENAME.zip 
>brooklyn-cli-b8b39e54ecbb7c12f4828783f07bec978a76b7be/br/Godeps\*,
>the hashes become:
>SHA1: 91fda2ca20c4b171985e1f5bb545ed8a236123dd
>SHA256: 4de28b308ad09f0e5642b4cefdd54b1c91b255fecd00184763a7d260bf8ec12d
>
>I am updating the IP Clearance record with this same statement.
>
>Is this sufficient notice for the record to address your comments?

I would hope it is sufficient, but I am not the person who can make the
call.  Other more senior folks may be able to make the call, but if you
want to be more sure, I would ask on legal-discuss if this is a sufficient
way to update an SGA.

-Alex

Re: [VOTE] MADlib v1.9alpha-rc1

[Roman Shaposhnik]

With the blocking (vestiges of MPL code) jiras fixed and the blessing
from legal-discuss on how to proceed re: missing BSD licensing headers:
 
http://mail-archives.apache.org/mod_mbox/www-legal-discuss/201603.mbox/%3C9D1AF43C-370B-4E58-B0EF-2E29D242F50B%40jaguNET.com%3E
I propose we move ahead with RC2.

Thanks,
Roman.

On Wed, Mar 2, 2016 at 2:45 PM, Frank McQuillan  wrote:
> Thank you all for your comments and suggestions.
>
> At this point I would like to cancel the vote on MADlib v1.9alpha-rc1.  The
> following JIRAs have been identified based on comments received; they have
> either been fixed or are in the process of being fixed:
>
> https://issues.apache.org/jira/browse/MADLIB-971
> https://issues.apache.org/jira/browse/MADLIB-972
>
> We are waiting to hear from Roman regarding the need to add a header to BSD
> files, and if so, what the header content should be.  This is the only
> outstanding item.  Once it has been resolved we will be putting up a RC2
> and calling for another vote by the Incubator PMC.
>
> Regards,
> Frank
>
>
> On Sun, Feb 28, 2016 at 1:45 PM, Roman Shaposhnik 
> wrote:
>
>> On Sun, Feb 28, 2016 at 1:38 PM, Justin Mclean 
>> wrote:
>> > Hi,
>> >
>> >> Good point, Roman -- I don't think there's one right answer there.
>> >> Copyright credits in open source works with lots of collaborators are
>> >> a can of worms.
>> > 
>> >> Maybe add a short header to each file (vet wording with
>> >> legal-discuss), something to the effect of…
>> >
>> > Could the files in question be considered copyright MADLib project? (the
>> pre/non Apache one that is)
>>
>> They could, but that would be us inventing things retrospectively
>> which, when it comes to legal matters, I'm terrified of.
>>
>> I'll ask this question on legal-discuss to be sure. Stay tuned!
>>
>> Thanks,
>> Roman.
>>
>> P.S. Justin, your -1 is still very much justified (and appreciated!) given
>> that
>> we  did, indeed, left one MPL source file (we got rid of other MPL source
>> files, but missed this one).
>>
>> -
>> 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 Gearpump into the Apache Incubator

[Flavio Junqueira]

+1 (binding)

Really nice project, happy to see it incubating.

-Flavio

> On 04 Mar 2016, at 09:14, Jean-Baptiste Onofré  wrote:
> 
> +1 (binding)
> 
> Regards
> JB
> 
> On 03/02/2016 04:06 PM, Gangumalla, Uma wrote:
>> +1 (non-binding)
>> 
>> Regards,
>> Uma
>> 
>> On 3/1/16, 4:53 PM, "Andrew Purtell"  wrote:
>> 
>>> Greetings,
>>> 
>>> The discussion of the Gearpump proposal has concluded. Please vote to
>>> accept Gearpump into the Apache Incubator. I will leave this vote open for
>>> at least the next 72 hours and will aim to close it Monday the 7th of
>>> March, 2016 at midnight PT. Gearpump is a flexible, efficient, and
>>> scalable
>>> micro-service based real-time big data streaming engine. The text of the
>>> proposal is included below and is also available at
>>> https://wiki.apache.org/incubator/GearpumpProposal
>>> 
>>> [ ] +1 Accept Gearpump as an Apache Incubator podling.
>>> [ ] +0 Abstain.
>>> [ ] -1 Don’t accept Gearpump as an Apache Incubator podling because ...
>>> 
>>> Note that while votes from Incubator PMC members are binding, all are most
>>> definitely welcome to vote!
>>> 
>>> I am +1 (binding).
>>> 
>>> Best regards,
>>> 
>>>   - Andy
>>> 
>>> ​-
>>> 
>>> = Gearpump Proposal =
>>> 
>>> === Abstract ===
>>> Gearpump is a flexible, efficient and scalable micro-service based
>>> real-time big data streaming engine developed by Intel Corporation which
>>> has been licensed by Intel under the Apache License 2.0.
>>> 
>>> === Proposal ===
>>> Gearpump is a reactive real-time streaming engine; completely based on the
>>> micro-service Actor model. Gearpump provides extremely high performance
>>> stream processing while maintaining millisecond latency message delivery.
>>> It enables reusable, composable flows or partial graphs that can be
>>> remotely deployed and executed in a diverse set of environments, including
>>> IoT edge devices. These flows may be deployed and modified at runtime -- a
>>> capability few real time streaming frameworks provide today.
>>> 
>>> The goal of this proposal is to incubate Gearpump as an Apache project in
>>> order to build a diverse, healthy, and self-governed open source community
>>> around this project.
>>> 
>>> === Background ===
>>> In past decade, there have been many advances within real-time streaming
>>> frameworks. Despite many advances, users of streaming frameworks often
>>> complain about flexibility, efficiency, and scalability. Gearpump
>>> endeavors
>>> to solve these challenges by adopting the micro-service Actor model. The
>>> Actor model was proposed by Carl Hewitt in 1973. In the Actor model, each
>>> actor is a message driven micro-service; actors are the basic building
>>> blocks of concurrent computation. By leveraging Actor Model’s location
>>> transparency feature,Gearpump allows a graph to be composed of several
>>> partial graphs, where, for example, some parts may be deployed to remote
>>> IoT edge devices, and other parts to a data center. This division and
>>> deployment model can be changed at runtime to adapt to a changing physical
>>> environment, providing extreme flexibility and elasticity in solving
>>> various ingestion and analytics problems. We’ve found Actors to be a much
>>> smaller computation unit compared with threads, where smaller usually
>>> means
>>> better concurrency, and potentially better CPU utilization.
>>> 
>>> === Rationale ===
>>> Gearpump tightly integrates and enhances the big data community of Apache
>>> projects. Intel believes Gearpump can bring benefits to the Apache
>>> community in a number of ways:
>>> 
>>> 1. Gearpump complements many existing Apache projects, in particular,
>>> those
>>> commonly found within the big data space. Users of this project are also
>>> users of other Apache projects, such as Hadoop ecosystem projects. It is
>>> beneficial to align these projects under the ASF umbrella. In real-time
>>> streaming, Gearpump offers some special features that are useful for
>>> Apache
>>> users, such as exactly-once processing with millisecond message level
>>> latency and dynamic DAGs that allow online topology modifications.
>>> 
>>> 2. Gearpump tightly integrates with Apache big data projects. It supports
>>> for Apache HDFS, YARN, Kafka, and HBase. It uses Apache YARN for resource
>>> scheduling and Apache HDFS as the essential distributed storage system.
>>> 
>>> 3. The micro-service model of reusable flows that Gearpump has adopted is
>>> very unique, and it may become common in the future.Gearpump sets a good
>>> example about how distributed software can be implemented within a
>>> micro-service model.  An open project is of best interest to our users. By
>>> joining Apache, it will be a neutral infrastructure platform that will
>>> benefit everyone.
>>> 
>>> 4. The process and development philosophy of Apache will help Gearpump
>>> grow,
>>> and build a diverse, healthy, and self-governed open source community.
>>> 
>>> === 

Re: Update on Apache Toree and LGPL dependency

[Jim Jagielski]

+1

> On Mar 6, 2016, at 6:58 PM, Gino Bustelo  wrote:
> 
> @john The 0mq ecosystem is made up of many projects of different sizes and 
> maturity. In the case of JeroMQ, the committers are showing an overwhelming 
> momentum to transition to MPL. I don't see any reason for us to consider any 
> other alternative at this juncture. 
> 
> Gino B.
> 
>> On Mar 5, 2016, at 11:42 PM, Henri Yandell  wrote:
>> 
>> Having chatted around the 0mq community in the past; I've confidence in
>> their desire to move to MPL; and 26/32 committers is a great step forward.
>> You raise a good reservation though John - if you remove the blocker on the
>> usage side, it's easy for the licensing to remain as is.
>> 
>> 
>> I'm +1 for releasing, with a prominent note of the LGPL dependency (along
>> with a note of the resolution plan). It might be that the Toree committers
>> may be motivated to rewrite code over at 0mq if there ends up being any
>> committers who are unavailable or unwilling to relicense.
>> 
>> Hen
>> 
>>> On Sat, Mar 5, 2016 at 3:45 PM, John D. Ament  wrote:
>>> 
>>> Sorry, misread the revision I was looking at.  The intent to move to MPL
>>> was done on March 22 2014, 2 years ago this month, not December 2013.
>>> 
>>> John
>>> 
>>> On Sat, Mar 5, 2016 at 6:41 PM John D. Ament 
>>> wrote:
>>> 
 I have some reservations with what you're proposing, and would like you
>>> to
 consult w/ legal-discuss on this first.
 
 There's a difference between what Mynewt did and what you're proposing.
 Specifically, this was a transitive dependency that they relied upon
 indirectly, so its more of a call out for the library that was leveraging
 it.  They also intended to replace the library.
 
 In your case, you're directly tied to a presently LGPL'd library.  You
 have no intentions (from what I can see) of moving off of the library.
 
 I'm also doubting their long term goals of moving to MPL.  If you look at
 [1], you'll see that the page hasn't been updated since October 2014.  In
 addition, looking at the pages revision history (the beauty of wikis),
>>> the
 intent to move to MPL was published in December 2013, making the
>>> statement
 over 2 years old.
 
 I think while this might be OK for an initial incubator release, the
 project needs to weigh very heavily if it wants to continue to leverage
 ZeroMQ or not going forward.
 
 [1]: http://zeromq.org/area:licensing
 
 
> On Sat, Mar 5, 2016 at 5:06 PM Gino Bustelo  wrote:
> 
> Wanted to give folks an update on our progress with dealing with JeroMQ,
> an
> LGPL package that enables us to communicate via 0MQ. The 0MQ community
>>> is
> very aware of the issues with LGPL (LGPLv3 + static link exception) and
>>> it
> is their intention to try to move projects to MPL v2. This is not an
>>> easy
> task depending on the age and size of the projects.
> 
> Apache Toree's API access point is through the 0MQ transport layer
>>> (using
> JeroMQ) and that is how Apache Toree connects out-of-the-box with
>>> Jupyter,
> a very common way of consuming Apache Toree that is already in
>>> production.
> 
> At this point, the JeroMQ project is still released under LGPL, but our
> team initiated communications in mid-February with members of the JeroMQ
> community to begin their transition to MPL v2 (
> https://github.com/zeromq/jeromq/issues/326). The JeroMQ community
> reacted
> very positively and quickly began the process of collecting votes from
> their committers (https://github.com/zeromq/jeromq/issues/327). After
>>> 15
> days, the current tally stands at 26 out of 32 committers have agreed to
> switch license.
> 
> Apache Toree has a JIRA (
>>> https://issues.apache.org/jira/browse/TOREE-262)
> where we keep all the relevant links and update with the latest
> information. As that process is underway, we will move forward with
>>> plans
> to release a 0.1.0 version of Apache Toree based on the precedence set
>>> by
> Apache Mynewt (
>>> http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3C5F118AA0-4ADA-403B-A6EB-4A85F0B30651%40me.com%3E
> ).
> 
> Thanks,
> Gino
>>> 
> 
> -
> 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: [IP CLEARANCE] Apache Brooklyn - CLI

[Richard Downer]

Alex, Justin, all,

Thank you for your comments. With your comments in mind, I will make
this statement for the record:

Regarding the subject of the Software Grant Agreement, download link:
https://github.com/brooklyncentral/brooklyn-cli/archive/b8b39e54ecbb7c12f4828783f07bec978a76b7be.zip
SHA1: 5b5ef46c56adfff8ca86cca04694d5abc10ec447
SHA256: 0cfaac11df7075c723bfb982ed5852d790fa195dcfe67c9bbbd545f34df71770

The folder brooklyn-cli-b8b39e54ecbb7c12f4828783f07bec978a76b7be/br/Godeps
is *excluded* from the code grant; this folder contains bundled
dependencies licensed by 3rd parties using the MIT and BSD licenses.

With this folder removed from the ZIP file using the command zip -d
FILENAME.zip brooklyn-cli-b8b39e54ecbb7c12f4828783f07bec978a76b7be/br/Godeps\*,
the hashes become:
SHA1: 91fda2ca20c4b171985e1f5bb545ed8a236123dd
SHA256: 4de28b308ad09f0e5642b4cefdd54b1c91b255fecd00184763a7d260bf8ec12d

I am updating the IP Clearance record with this same statement.

Is this sufficient notice for the record to address your comments?

Thanks!
Richard.

[Sorry for the delay in replying, due to illness]


On 1 March 2016 at 21:42, Alex Harui  wrote:
>
>
> On 3/1/16, 12:18 PM, "Justin Mclean"  wrote:
>
>>Hi,
>>
>>> Sorry if I'm missing something, but it sounds like Justin found these
>>> files in the zip referenced by the Grant.
>>
>>The files are clearly marked as BSD/MIT licensed and who the copyright
>>owner is IMO (but I could be wrong) I don’t think the grant needs to be
>>redone as it’s clear what would be under the ASF license. It would also
>>be relatively easy to remove the files from the zip and resubmit.
>
> I don't know if there is an official protocol for a scenario like this.
> All I think is needed is an email trail that indicates that the Grant
> needed some modifications and what the modifications were.  The grant
> document contains a SHA hash for the zip so if you change the zip the
> grant may need the SHA hash updated.  But hopefully it will be ok for
> folks to find an updated SHA hash in an email in the archives or maybe in
> the IP Clearance record itself.
>
> Thanks,
> -Alex
>
>
> -
> 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: Copyright sign offs

[John D. Ament]

On Mar 6, 2016 23:49, "Roman Shaposhnik"  wrote:
>
> Henri, it seems I'm a bit lost with your terminology. See the question
bellow:
>
> On Fri, Feb 26, 2016 at 5:28 PM, Henri Yandell  wrote:
> > Haven't done this in a while :)
> >
> > Thought I'd share that the following podlings have not yet signed off on
> > their Copyright sections in their status reports.
>
> What does it mean exactly? For example...
>
> >   datafu
>
> ...what is the actionable item I need to bring up with this community?
>
> > I'd be interested to hear about any reasons why the above aren't able to
> > sign that element of their status file off.
> >
> > (same, but for those who are < 6 months in the incubator, ie) still
working
> > on it)
> >
> >   fineract
>
> Ditto here.
>
> Thanks,
> Roman.

I believe he's referring to your IP Clearance pages.

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

Re: Making license adjustment tools publicly available

[sebb]

On 7 March 2016 at 01:46, Roman Shaposhnik  wrote:
> To close a loop on this: based on the consensus I created a public
> version of the tools under:
> http://svn.apache.org/viewvc/comdev/tools/licensing/
>
> My attempts of preserving the history weren't successfully since
> private and public are two different SVN repos (you can't just svn cp/mv).
> I don't think this is that big of a deal, but please let me know if it is.

In such cases it would be helpful to document the original source in
the commit log message.

> Finally, I'd like to remove content of:
> https://svn.apache.org/repos/private/committers/relicense/
> and replace it with a README.txt saying that the content has moved
> to a new public location. Please let me know if that sounds ok.
>
> My final step would be to update a few bits of publicly visible documentation
> to point to a new public location.
>
> Thanks,
> Roman.
>
> On Sat, Feb 6, 2016 at 8:33 AM, Shane Curcuru  wrote:
>> Christopher wrote on 2/4/16 7:25 PM:
>>> It might be relevant that that both of those tools appear to be licensed
>>> under ASL 2.0, which explicitly permits redistribution (presumably outside
>>> the private area?). I would think it confusing to have an open source
>>> license on software which is expected to remain private, or otherwise
>>> restricted from redistribution. As such, it seems prudent to move them to a
>>> more appropriate area. That's my opinion, anyway.
>>
>> Yes, the Apache license explicitly gives broad permissions.  But the ASF
>> organizationally is very conservative about actually redistributing
>> software.  That is, we *could* legally redistribute some random software
>> we found under AL or MIT or the like, but if someone makes it clear they
>> *didn't* intend to submit it to an Apache project, then we'll generally
>> respect their wishes.
>>
>> In this case, it's all work done by ASF Committers for the purpose of
>> doing work on Apache projects, so I can't see why it would be a problem.
>>  It's most likely that once Apache projects finished updating to 2.0
>> license, no-one bothered to think of these tools again.
>>
>> In any case, I would definitely recommend either testing them, or
>> putting in behavior so that it doesn't actually change files in the
>> default command line (to prevent surprises, if it doesn't work as
>> someone anticipated).
>>
>> - Shane
>>
>>>
>>> On Thu, Feb 4, 2016 at 7:14 PM Roman Shaposhnik  wrote:
>>>
 Hi!

 a podling recently asked me why:
 https://svn.apache.org/repos/private/committers/relicense/
 https://svn.apache.org/repos/private/committers/tools/copy2license.pl
 are only available to commiters. I see
 no reason why, but of course I'm appreciative
 of the warning here:
 https://svn.apache.org/repos/private/committers/README

 Two questions:
1. Is there any disagreement that making this tool publically
 available would be a 'good thing' ?
 2. Who should bless the svn mv if we all agree?

 Thanks,
 Roman.

>>>
>>

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