Re: [VOTE] Accept Tephra into the Apache Incubator

[larsh]

+1 (binding)
Exciting!

  From: Poorna Chandra 
 To: general@incubator.apache.org 
 Sent: Thursday, March 3, 2016 5:29 PM
 Subject: [VOTE] Accept Tephra into the Apache Incubator
   
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
Tephra will benefit by close 

Re: Possible ASF Incubator Project transfer..

[Henri Yandell]

So you include it in conversations - there would also need to be
discussions on the Glassfish trademark/any domains.  Nothing as
standardized as the software license grant others have referred to, but I
would expect it to be 'if a registered trademark/domain, transferring to
ASF; if not a registered trademark, possibly some form of understanding of
future use'.

Hen

On Thu, Mar 3, 2016 at 3:39 PM, Reza Rahman  wrote:

> Yep, understood. We will give it an honest effort.
>
> Sent from my iPhone
>
> > On Mar 3, 2016, at 6:30 PM, John D. Ament  wrote:
> >
> > You need to start with convincing oracle to provide an SGA for the
> entire glassfish codebase.  Your best bet is to start that before you leave
> oracle.
> >
> > John
> >
> >> On Thu, Mar 3, 2016 at 4:08 PM Reza Rahman 
> wrote:
> >> Obviously I need to take this up in earnest after Friday. In the
> meanwhile let me know what I need to do in order to get myself setup for
> this.
> >>
> >> Anything that is worth it is never easy. This matters enough to try and
> there are many that will be with us, even inside Oracle.
> >>
> >>> On Mar 3, 2016, at 3:57 PM, John D. Ament 
> wrote:
> >>>
> >>> Hi Martin, Reza,
> >>>
> >>> The biggest hurdle would likely be Oracle signing an SGA for the
> glassfish codebase.  Not to mention that all dependencies are currently
> GPL/CDDL dual licensed.
> >>>
> >>> John
> >>>
>  On Thu, Mar 3, 2016 at 3:17 PM Martin Gainty 
> wrote:
>  Looking for procedures for transferring control of currently
> un-maintained glassfish J2EE Server from Oracle to ASF incubator project
> 
>  Thanks and Regards
>  Martin Gainty
> 
> 
>  Subject: Re: [gf-users] Re: Farewell to Oracle
>  To: mgai...@hotmail.com
>  From: reza_rah...@lycos.com
>  Date: Thu, 3 Mar 2016 13:56:02 -0500
> 
> 
> 
> 
> 
> 
>  That sounds just about right. How can I
>    get involved?
> 
> 
> 
>    On 3/3/2016 1:53 PM, Martin Gainty wrote:
> 
> 
> 
> 
>    Feel free to join Marcus and myself to transfer
>  Glassfish to ASF  ..
> 
> 
> 
> 
> 
> 
>    > To: us...@glassfish.java.net
> 
>  > From: reza_rah...@lycos.com
> 
>  > Date: Thu, 3 Mar 2016 12:51:49 -0500
> 
>  > Subject: [gf-users] Farewell to Oracle
> 
>  >
> 
>  > Folks,
> 
>  >
> 
>  > I am leaving Oracle behind on Friday. I have no doubt
>  whatsoever that
> 
>  > this was one of the top five hardest decisions of my
>  life. I am also at
> 
>  > this stage equally certain that this is the way I
>  personally can best
> 
>  > help continue to advance the Java and Java EE
>  communities. I will be
> 
>  > resuming the community work I have been part of for the
>  better part of a
> 
>  > decade in earnest as soon as possible post-Oracle.
> 
>  >
> 
>  > At Oracle folks like my colleagues David Delabassee and
>  Bruno Borges
> 
>  > will continue their roles in the Java EE ecosystem. I
>  certainly wish the
> 
>  > many good folks at Oracle nothing but the best of luck.
>  They have a very
> 
>  > hard job to do and they will continue to need our
>  support, perhaps now
> 
>  > more than ever.
> 
>  >
> 
>  > As always anyone is absolutely welcome to reach out to
>  me on just about
> 
>  > anything. Below are all my contact points.
> 
>  >
> 
>  > Cheers,
> 
>  > Reza
> 
>  >
> 
>  > Email: reza_rah...@lycos.com
> 
>  > Cell: 717-329-8149
> 
>  > Home Office: 215-736-1208
> 
>  > Google/Skype: m.reza.rahman
> 
>  > Twitter: @reza_rahman
> 
>  > https://www.linkedin.com/in/javareza
> 
>  > http://blog.rahmannet.net/
> 
>  > http://cargotracker.java.net
> 
> 
> 
> 
> 
> 
> 
>

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

[Madhan Neethiraj]

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


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

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

[Daniel Gruno]

On 03/06/2016 02:45 PM, 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
> 

Wrong directory, please fix ASAP.
Please put release candidates in the dev directory, only move them to
release once they have been approved - otherwise they go out to all the
mirrors.

With regards,
Daniel.

> 
> 
> 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
>>
>>
> 
> 
> -
> 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: Update on Apache Toree and LGPL dependency

[Gino Bustelo]

@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

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

[Stian Soiland-Reyes]

Thank you for a thorough review!

We've started tracking the Category B issues at
https://issues.apache.org/jira/browse/TAVERNA-927
We would appreciate your insight and help as we are a bit short on
active mentors! :-)



The ZIP files under the test directory needs to be zipped because the
Taverna Language deals (in part) with reading and writing a
zip-derived file format.

I've fixed in git master the workflowrun.bundle.zip internal LICENSE
file which was missing the appendix so it should be fine for next
release.


As for code signature, the release candidate and Maven artifacts are
signed by st...@apache.org A0FFD119 which is listed in KEYS. I
switched my primary UID so that st...@apache.org is on the top and
updated
https://dist.apache.org/repos/dist/release/incubator/taverna/KEYS
(See http://unix.stackexchange.com/a/153310 )


(BTW - we used to update KEYS from
https://people.apache.org/keys/group/taverna.asc to make sure that
id.apache.org had the openpgp fingerprint - but this has gone 404 in
the recent update of home.apache.org together with most incubator
groups)

On 5 March 2016 at 23:02, Justin Mclean  wrote:
> Hi,
>
> Sorry it -1 binding due to Category B software in a source release. [10]
>
> I checked:
> - artefacts contain incubating
> - signature and hashes good
> - DISCLAIMER exists
> - LICENSE is good however it lists Category B software
> - NOTICE is good
> - There are a couple of binary files (under the test directory) do these need 
> to be zipped?
> - All source files have headers
>
>
> There are some licensing issues:
> - Several items [3][4][5][6] are licensed under W3C document license, this is 
> not a category A license and looks like they can only be included in binary 
> release [2]. (i.e. Category B but it's not listed) You may need to clarify 
> this on legal discuss.
> - Files [8][9][16][17][18][19][20] licensed under CC-BY-3 can only be 
> included in a binary release. [10]
> - I assume CC-A [11][12] would also need to be handled the same way.
> - It is unclear how [13] is licensed.
> - Looks like [14][15] are not licensed under a Category A license. Again 
> probably needs to be discussed on legal discuss.
>
> The LICENSE and NOTICE in ./taverna-tavlang-tool/src/main/resources/META-INF/ 
> may need updating, looks like the contents don’t match the top level license 
> and year is incorrect.
>
> Also:
> - Please consider signed the artefacts with an apache email address.
> - The workflowrun.bundle.zip [1] file contains a LICENSE which is missing the 
> appendix
>
> Thanks,
> Justin
>
> 1. 
> apache-taverna-language-0.15.1-incubating/taverna-robundle/src/test/resources/workflowrun.bundle.zip
> 2. https://issues.apache.org/jira/browse/LEGAL-111
> 3. 
> ./taverna-scufl2-schemas/src/main/resources/org/apache/taverna/scufl2/rdfxml/xsd/xml.xsd
> 4. ./taverna-robundle/src/main/resources/ontologies/prov-aq.rdf
> 5. ./taverna-robundle/src/main/resources/ontologies/prov-o.rdf
> 6. ./taverna-robundle/src/main/resources/ontologies/prov-o.rdf
> 7. ./taverna-robundle/src/main/resources/ontologies/dcam.owl
> 8. ./taverna-robundle/src/main/resources/ontologies/dcam.owl
> 9. ./taverna-robundle/src/main/resources/ontologies/dcterms_od.owl
> 10. http://www.apache.org/legal/resolved.html#category-b
> 11. ./taverna-robundle/src/main/resources/ontologies/foaf.rdf
> 12. ./taverna-scufl2-wfdesc/src/main/resources/com/xmlns/foaf/foaf.rdf
> 13. ./taverna-robundle/src/main/xsd/xenc-schema.xsd
> 14. ./taverna-robundle/src/main/resources/ontologies/oa.rdf
> 15. ./taverna-robundle/src/main/resources/ontologies/ro.owl
> 16. 
> ./taverna-scufl2-wfdesc/src/main/resources/org/purl/wf4ever/wfdesc/wfdesc.ttl
> 17. 
> ./taverna-scufl2-wfdesc/src/main/resources/org/purl/wf4ever/wfdesc/wfprov.ttl
> 18. 
> ./taverna-scufl2-wfdesc/src/main/resources/org/purl/wf4ever/wfdesc/roterms.ttl
> 19. 
> ./taverna-scufl2-wfdesc/src/main/resources/org/purl/wf4ever/wfdesc/wf4ever.ttl
> 20 
> ./taverna-scufl2-schemas/src/main/resources/org/apache/taverna/scufl2/rdfxml/xsd/roevo.xsd
>
> -
> 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: Making license adjustment tools publicly available

[Roman Shaposhnik]

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.

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

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

[Stack]

+1 (binding)

Checked signature, hash, and compared tarball to git tag. Built it
successfully. Ran unit tests. Poked around. Licenses look good.

St.Ack

On Sun, Mar 6, 2016 at 10:20 AM, Jean-Daniel Cryans 
wrote:

> Hi,
>
> The PPMC vote to release Apache Kudu (incubating) 0.7.1 RC2 passed and I'm
> now submitting this to the IPMC.
>
> Vote thread:
>
> http://mail-archives.apache.org/mod_mbox/incubator-kudu-dev/201603.mbox/%3CCAGpTDNfBpLCqYEeArpDUFM0EUvW-aOUHDpCtCQARetHTY%2BUACw%40mail.gmail.com%3E
>
> Result:
>
> http://mail-archives.apache.org/mod_mbox/incubator-kudu-dev/201603.mbox/%3CCAGpTDNdH-pK_cmoxXzTag5T0G9Bm6jqN-7Bf%3DcQjX1vrrpnUxw%40mail.gmail.com%3E
>
> The is a source-only release. The artifacts were staged here:
> https://dist.apache.org/repos/dist/dev/incubator/kudu/0.7.1-RC2/
>
> Please try the release and vote; vote will be open for at least 72 hours.
>
> There's already one binding +1 from Todd Lipcon.
>
> Thanks,
>
> J-D
>

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

[Madhan Neethiraj]

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


-
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

[Naresh Agarwal]

+1 (non-binding)

Looking forward to this project.

Thanks
Naresh Agarwal
On 7 Mar 2016 02:09,  wrote:

> +1 (binding)
> Exciting!
>
>   From: Poorna Chandra 
>  To: general@incubator.apache.org
>  Sent: Thursday, March 3, 2016 5:29 PM
>  Subject: [VOTE] Accept Tephra into the Apache Incubator
>
> 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 

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

[John D. Ament]

On Sun, Mar 6, 2016 at 1:21 PM Jean-Daniel Cryans 
wrote:

> Hi,
>
> The PPMC vote to release Apache Kudu (incubating) 0.7.1 RC2 passed and I'm
> now submitting this to the IPMC.
>
> Vote thread:
>
> http://mail-archives.apache.org/mod_mbox/incubator-kudu-dev/201603.mbox/%3CCAGpTDNfBpLCqYEeArpDUFM0EUvW-aOUHDpCtCQARetHTY%2BUACw%40mail.gmail.com%3E
>
> Result:
>
> http://mail-archives.apache.org/mod_mbox/incubator-kudu-dev/201603.mbox/%3CCAGpTDNdH-pK_cmoxXzTag5T0G9Bm6jqN-7Bf%3DcQjX1vrrpnUxw%40mail.gmail.com%3E
>
> The is a source-only release. The artifacts were staged here:
> https://dist.apache.org/repos/dist/dev/incubator/kudu/0.7.1-RC2/
>
> Please try the release and vote; vote will be open for at least 72 hours.
>
> There's already one binding +1 from Todd Lipcon.
>
>
Would you mind following the incubator release best practice from
http://incubator.apache.org/guides/releasemanagement.html#best-practice-incubator-release-vote
and
include the link to the git commit for tag?


> Thanks,
>
> J-D
>

Re: Copyright sign offs

[Roman Shaposhnik]

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

Re: [VOTE] Accept Mnemonic into the Apache Incubator

[Olivier Lamy]

+1 (binding)

On 4 March 2016 at 11:40, Cheng, Hao  wrote:

> +1 (binding)
>
> Hao
>
> -Original Message-
> From: Ted Dunning [mailto:ted.dunn...@gmail.com]
> Sent: Friday, March 4, 2016 5:32 AM
> To: general@incubator.apache.org
> Subject: Re: [VOTE] Accept Mnemonic into the Apache Incubator
>
> I thought I sent a vote in earlier today but I may have hit the wrong
> thread.
>
> Please accept this vote.
>
> +1 (binding)
>
>
>
> On Thu, Mar 3, 2016 at 11:19 AM, P. Taylor Goetz 
> wrote:
>
> > +1 (binding)
> >
> > -Taylor
> >
> > > On Feb 29, 2016, at 12:37 PM, Patrick Hunt  wrote:
> > >
> > > Hi folks,
> > >
> > > OK the discussion is now completed. Please VOTE to accept Mnemonic
> > > into the Apache Incubator. I’ll leave the VOTE open for at least the
> > > next 72 hours, with hopes to close it Thursday the 3rd of March,
> > > 2016 at 10am PT.
> > > https://wiki.apache.org/incubator/MnemonicProposal
> > >
> > > [ ] +1 Accept Mnemonic as an Apache Incubator podling.
> > > [ ] +0 Abstain.
> > > [ ] -1 Don’t accept Mnemonic as an Apache Incubator podling because..
> > >
> > > Of course, I am +1 on this. Please note VOTEs from Incubator PMC
> > > members are binding but all are welcome to VOTE!
> > >
> > > Regards,
> > >
> > > Patrick
> > >
> > > 
> > > = Mnemonic Proposal =
> > > === Abstract ===
> > > Mnemonic is a Java based non-volatile memory library for in-place
> > > structured data processing and computing. It is a solution for
> > > generic object and block persistence on heterogeneous block and
> > > byte-addressable devices, such as DRAM, persistent memory, NVMe,
> > > SSD, and cloud network storage.
> > >
> > > === Proposal ===
> > > Mnemonic is a structured data persistence in-memory in-place library
> > > for Java-based applications and frameworks. It provides unified
> > > interfaces for data manipulation on heterogeneous
> > > block/byte-addressable devices, such as DRAM, persistent memory,
> > > NVMe, SSD, and cloud network devices.
> > >
> > > The design motivation for this project is to create a non-volatile
> > > programming paradigm for in-memory data object persistence,
> > > in-memory data objects caching, and JNI-less IPC.
> > > Mnemonic simplifies the usage of data object caching, persistence,
> > > and JNI-less IPC for massive object oriented structural datasets.
> > >
> > > Mnemonic defines Non-Volatile Java objects that store data fields in
> > > persistent memory and storage. During the program runtime, only
> > > methods and volatile fields are instantiated in Java heap,
> > > Non-Volatile data fields are directly accessed via GET/SET operation
> > > to and from persistent memory and storage. Mnemonic avoids SerDes
> > > and significantly reduces amount of garbage in Java heap.
> > >
> > > Major features of Mnemonic:
> > > * Provides an abstract level of viewpoint to utilize heterogeneous
> > > block/byte-addressable device as a whole (e.g., DRAM, persistent
> > > memory, NVMe, SSD, HD, cloud network Storage).
> > >
> > > * Provides seamless support object oriented design and programming
> > > without adding burden to transfer object data to different form.
> > >
> > > * Avoids the object data serialization/de-serialization for data
> > > retrieval, caching and storage.
> > >
> > > * Reduces the consumption of on-heap memory and in turn to reduce
> > > and stabilize Java Garbage Collection (GC) pauses for latency
> > > sensitive applications.
> > >
> > > * Overcomes current limitations of Java GC to manage much larger
> > > memory resources for massive dataset processing and computing.
> > >
> > > * Supports the migration data usage model from traditional
> > > NVMe/SSD/HD to non-volatile memory with ease.
> > >
> > > * Uses lazy loading mechanism to avoid unnecessary memory
> > > consumption if some data does not need to use for computing
> immediately.
> > >
> > > * Bypasses JNI call for the interaction between Java runtime
> > > application and its native code.
> > >
> > > * Provides an allocation aware auto-reclaim mechanism to prevent
> > > external memory resource leaking.
> > >
> > >
> > > === Background ===
> > > Big Data and Cloud applications increasingly require both high
> > > throughput and low latency processing. Java-based applications
> > > targeting the Big Data and Cloud space should be tuned for better
> > > throughput, lower latency, and more predictable response time.
> > > Typically, there are some issues that impact BigData applications'
> > > performance and scalability:
> > >
> > > 1) The Complexity of Data Transformation/Organization: In most
> > > cases, during data processing, applications use their own
> > > complicated data caching mechanism for SerDes data objects, spilling
> > > to different storage and eviction large amount of data. Some data
> > > objects contains complex values and structure that will make it much
> > > more difficulty for data organization.