Re: [VOTE] Recommend Apache Iceberg graduation to top-level project resolution to the board

[James Taylor]

+1 (binding)

On Fri, May 15, 2020 at 5:40 PM Ryan Blue  wrote:

> Hi everyone,
>
> With the support of our mentors (as well as helpful ASF members), the
> Apache Iceberg community has voted to graduate to a top-level project.
>
> I propose a vote to recommend graduation for the Iceberg community to the
> board. Here is the proposed resolution:
>
> ```
> Establish the Apache Iceberg Project
>
> WHEREAS, the Board of Directors deems it to be in the best interests of
> the Foundation and consistent with the Foundation's purpose to establish
> a Project Management Committee charged with the creation and maintenance
> of open-source software, for distribution at no charge to the public,
> related to managing huge analytic datasets using a standard at-rest
> table format that is designed for high performance and ease of use..
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Iceberg Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Iceberg Project be and hereby is responsible
> for the creation and maintenance of software related to managing huge
> analytic datasets using a standard at-rest table format that is designed
> for high performance and ease of use; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Iceberg" be and
> hereby is created, the person holding such office to serve at the
> direction of the Board of Directors as the chair of the Apache Iceberg
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Iceberg
> Project; and be it further
>
> RESOLVED, that the persons listed immediately below be and hereby are
> appointed to serve as the initial members of the Apache Iceberg Project:
>
>  * Anton Okolnychyi 
>  * Carl Steinbach   
>  * Daniel C. Weeks  
>  * James R. Taylor  
>  * Julien Le Dem
>  * Owen O'Malley
>  * Parth Brahmbhatt 
>  * Ratandeep Ratti  
>  * Ryan Blue
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Ryan Blue be appointed to
> the office of Vice President, Apache Iceberg, to serve in accordance
> with and subject to the direction of the Board of Directors and the
> Bylaws of the Foundation until death, resignation, retirement, removal
> or disqualification, or until a successor is appointed; and be it
> further
>
> RESOLVED, that the Apache Iceberg Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Iceberg
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Iceberg podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
> ```
>
> The community vote passed with 19 +1 votes:
>
> https://lists.apache.org/thread.html/r9081df0181768f26490f5a85aed7b5a111a82a741764eb3a0e99621d%40%3Cdev.iceberg.apache.org%3E
>
> We also addressed concerns on the IPMC thread, which you can read here:
>
> https://lists.apache.org/thread.html/r3e5795d959feb0a19b233aeaf1121a1d97fd473f5e9b14227de41c54%40%3Cgeneral.incubator.apache.org%3E
>
> Please vote on whether to recommend graduation for the Apache Iceberg
> community to the board.
>
> [ ] +1 Apache Iceberg should graduate
> [ ] +0
> [ ] -1 Apache Iceberg should not graduate because . . .
>
> The vote will be open for at least 72 hours.
>
> --
> Ryan Blue
>

Re: Omid and Tephra

[James Taylor]

+1. That seems like the best course of action IMHO.

On Wed, Oct 23, 2019 at 12:54 PM Flavio Junqueira  wrote:

> +1
>
> -Flavio
>
> > On 23 Oct 2019, at 21:08, Terence Yim  wrote:
> >
> > +1 on this
> >
> > On Wed, Oct 23, 2019 at 11:36 Dave Fisher  wrote:
> >
> >> +1. That’s a good idea.
> >>
> >> Sent from my iPhone
> >>
> >>> On Oct 23, 2019, at 11:26 AM, Alan Gates  wrote:
> >>>
> >>> Justin and mentors of Omid and Tephra,
> >>>
> >>> As Justin noted in his emails to these podlings this month both are
> very
> >>> low activity, struggling to even file their reports, and appear to be
> >>> candidates for retirement.
> >>>
> >>> The situation here is somewhat special because Phoenix uses one or both
> >> of
> >>> these technologies (they are both transaction managers on top of
> HBase),
> >> so
> >>> they may have an interest in their continued survival.  Tephra briefly
> >>> discussed this last June[1], though nothing came of it.  My conclusion
> is
> >>> there is not enough momentum left for these podlings to vote themselves
> >>> into Phoenix without an external push.
> >>>
> >>> So before we push them into retirement I believe we should involve the
> >>> Phoenix PMC and see if they want to adopt either or both of these, with
> >> the
> >>> knowledge that they will likely be getting minimal contributions from
> >>> current members of those projects going forward.  If others are ok with
> >>> this I can contact the Phoenix PMC and see if they wish to take any
> >> action
> >>> on this.
> >>>
> >>> Alan.
> >>>
> >>> 1.
> >>>
> >>
> https://lists.apache.org/thread.html/87ace080ef8a967b238781979a8d9a0cb9607ac4a195d5937756ec66@%3Cdev.tephra.apache.org%3E
> >>
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Iceberg 0.7.0-incubating RC4

[James Taylor]

+1 (binding).

Successfully downloaded, verified license, verified checksum, verified
signature, built from source, and ran unit tests.
Minor nit (ok to fix in next release IMHO): Copyright in NOTICE for Iceberg
should read 2017-2019



On Tue, Oct 22, 2019 at 3:21 PM Ryan Blue  wrote:

> Hi everyone,
>
> I propose the following RC to be released as official Apache Iceberg
> 0.7.0-incubating release.
>
> This candidate has passed a PPMC vote. The result thread is here:
> *
>
> https://lists.apache.org/thread.html/fe76494f9feab454837bc2dc540cd9e59d55dac3f7e0b5b335de7725@
> 
>
> The commit id is 9c81babac65351f7aa21dd878f01c5c81ae304af
> * This corresponds to the tag: apache-iceberg-0.7.0-incubating-rc4
> *
>
> https://github.com/apache/incubator-iceberg/tree/apache-iceberg-0.7.0-incubating-rc4
> *
>
> https://github.com/apache/incubator-iceberg/tree/9c81babac65351f7aa21dd878f01c5c81ae304af
>
> The release tarball, signature, and checksums are here:
> *
>
> https://dist.apache.org/repos/dist/dev/incubator/iceberg/apache-iceberg-0.7.0-incubating-rc4/
>
> You can find the KEYS file here:
> * https://dist.apache.org/repos/dist/dev/incubator/iceberg/KEYS
>
> This release includes convenience binary artifacts that are staged in
> Nexus. The Maven repository URL is:
> *
> https://repository.apache.org/content/repositories/orgapacheiceberg-1004/
>
> The convenience binaries include a Spark runtime Jar with shaded
> dependencies. The LICENSE and NOTICE content for that Jar are viewable in
> github as well as in the Jar:
>
> https://github.com/apache/incubator-iceberg/tree/apache-iceberg-0.7.0-incubating-rc4/runtime
>
> To build and test, run `./gradlew build`. You can also test by adding the
> iceberg-spark-runtime Jar to the jars folder of Spark 2.4.
>
> This is the first Apache Iceberg release.
>
> Please download, verify, and test; then vote in the next 72 hours.
>
> [ ] +1 Release this as Apache Iceberg 0.7.0-incubating
> [ ] +0
> [ ] -1 Do not release this because...
>
> --
> Ryan Blue
>

Re: [VOTE] Release Apache Omid 1.0.1 (incubating)

[James Taylor]

Transferring my +1 from the dev list vote.

FYI, the correct pointer the the PPMC vote is here:
https://s.apache.org/8q5z

Thanks,
James



On Mon, May 6, 2019 at 7:43 AM James Taylor  wrote:

> Thanks, Justin. I've fixed the roster for Omid.
>
> On Sun, May 5, 2019 at 3:47 PM Justin Mclean 
> wrote:
>
>> Hi,
>>
>>
>> > 4 binding (IPMC member) +1 votes
>>
>> I only count 2 IPMC votes (from your mentors) have I miscounted?
>>
>> Can you also please fix up your roster [1] as it currently shows no PPMC
>> members.
>>
>> Thanks,
>> Justin
>>
>> 1. https://whimsy.apache.org/roster/ppmc/omid
>>
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

Re: [VOTE] Release Apache Omid 1.0.1 (incubating)

[James Taylor]

Thanks, Justin. I've fixed the roster for Omid.

On Sun, May 5, 2019 at 3:47 PM Justin Mclean 
wrote:

> Hi,
>
>
> > 4 binding (IPMC member) +1 votes
>
> I only count 2 IPMC votes (from your mentors) have I miscounted?
>
> Can you also please fix up your roster [1] as it currently shows no PPMC
> members.
>
> Thanks,
> Justin
>
> 1. https://whimsy.apache.org/roster/ppmc/omid
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache Omid 1.0.0 (incubating)

[James Taylor]

Transferring my +1 from the dev vote.

On Sat, Nov 17, 2018 at 11:45 PM Ohad Shacham 
wrote:

> Hi,
>
>
> The Apache Omid community has voted on and approved a proposal
> to release Apache Omid 1.0.0-incubating.
>
> PPMC Vote Call:
> http://mail-archives.apache.org/mod_mbox/omid-dev/201811.mbox/%3ccahuxfymp-_qvcn2qde3bqcqdta3hwbwfa52ygtuqr64qkjk...@mail.gmail.com%3e
>
>
> PPMC Vote Result:
>
>
> http://mail-archives.apache.org/mod_mbox/omid-dev/201811.mbox/%3cCAAF1JdinF60+hsxHbvxcx3oDruGqoE7BJ=gh_EbadFbDRHm8=w...@mail.gmail.com%3e
>
>
> PPMC Vote Summary:
> 4 binding (IPMC member) +1 votes
> 0 non-binding PPMC member +1 votes
> No -1 votes
>
> Release notes for the 1.0.0 release:
>
>
> https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.0-rc0/RELEASE_NOTES.html
>
>
> Git tag for the release:
>
>
> https://git-wip-us.apache.org/repos/asf/incubator-omid.git/?p=incubator-omid.git;a=tag;h=14d5cb2d899ef381be40edc6d95aede50bb396ea
>
>
> Sources for the release:
>
>
> https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.0-rc0/apache-omid-incubating-1.0.0-src.tar.gz
>
>
>
> Source release verification:
>
>
> PGP Signature:
>
>
> https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.0-rc0/apache-omid-incubating-1.0.0-src.tar.gz.asc
>
> SHA512 Hash:
> https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.0-rc0/apache-omid-incubating-1.0.0-src.tar.gz.sha512
>
> Keys to verify the signature of the release artifact are available
> at:https://dist.apache.org/repos/dist/dev/incubator/omid/1.0.0-rc0/KEYS
>
>
> We request the permission of IPMC to publish the above release candidate as
> Apache Omid 1.0.0-incubating. Please try out the package and vote. The vote
> is open for a minimum of 72 hours or until the necessary number of votes (3
> binding +1s) is reached. [ ] +1 Release this package as Apache Omid
> 1.0.0-incubating [ ] 0 I don't feel strongly about it, but I'm okay with
> the release [ ] -1 Do not release this package because... Please add
> (binding) if your vote is binding.
>
>
> Thanks,
> Ohad and Yoni
>

Re: [VOTE] Accept the Iceberg project for incubation

[James Taylor]

+1 (binding)

On Tue, Nov 13, 2018 at 4:15 PM Willem Jiang  wrote:

> +1 (binding)
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Wed, Nov 14, 2018 at 1:07 AM Ryan Blue  wrote:
> >
> > The discuss thread seems to have reached consensus, so I propose
> accepting
> > the Iceberg project for incubation.
> >
> > The proposal is copied below and in the wiki:
> > https://wiki.apache.org/incubator/IcebergProposal
> >
> > Please vote on whether to accept Iceberg in the next 72 hours:
> >
> > [ ] +1, accept Iceberg for incubation
> > [ ] -1, reject the Iceberg proposal because . . .
> >
> > Thank you for reviewing the proposal and voting,
> >
> > rb
> > --
> > Iceberg Proposal Abstract
> >
> > Iceberg is a table format for large, slow-moving tabular data.
> >
> > It is designed to improve on the de-facto standard table layout built
> into
> > Apache Hive, Presto, and Apache Spark.
> > Proposal
> >
> > The purpose of Iceberg is to provide SQL-like tables that are backed by
> > large sets of data files. Iceberg is similar to the Hive table layout,
> the
> > de-facto standard structure used to track files in a table, but provides
> > additional guarantees and performance optimizations:
> >
> >- Atomicity - Each change to the table is will be complete or will
> fail.
> >“Do or do not. There is no try.”
> >- Snapshot isolation - Reads use one and only one snapshot of a table
> at
> >some time without holding a lock.
> >- Safe schema evolution - A table’s schema can change in well-defined
> >ways, without breaking older data files.
> >- Column projection - An engine may request a subset of the available
> >columns, including nested fields.
> >- Predicate pushdown - An engine can push filters into read planning
> to
> >improve performance using partition data and file-level statistics.
> >
> > Iceberg does NOT define a new file format. All data is stored in Apache
> > Avro, Apache ORC, or Apache Parquet files.
> >
> > Additionally, Iceberg is designed to work well when data files are stored
> > in cloud blob stores, even when those systems provide weaker guarantees
> > than a file system, including:
> >
> >- Eventual consistency in the namespace
> >- High latency for directory listings
> >- No renames of objects
> >- No folder hierarchy
> >
> > Rationale
> >
> > Initial benchmarks show dramatic improvements in query planning. For
> > example, in Netflix’s Atlas use case, which stores time-series metrics
> from
> > Netflix runtime systems and 1 month is stored across 2.7 million files in
> > 2,688 partitions:
> >
> >- Hive table using Parquet:
> >   - 400k+ splits, not combined
> >   - Explain query: 9.6 minutes wall time (planning only)
> >- Iceberg table with partition filtering:
> >   - 15,218 splits, combined
> >   - Planning: 10 seconds
> >   - Query wall time: 13 minutes
> >- Iceberg table with partition and min/max filtering:
> >   - 412 splits
> >   - Planning: 25 seconds
> >   - Query wall time: 42 seconds
> >
> > These performance gains combined with the cross-engine compatibility are
> a
> > very compelling story.
> > Initial Goals
> >
> > The initial goal will be to move the existing codebase to Apache and
> > integrate with the Apache development process and infrastructure. A
> primary
> > goal of incubation will be to grow and diversify the Iceberg community.
> We
> > are well aware that the project community is largely comprised of
> > individuals from a single company. We aim to change that during
> incubation.
> > Current Status
> >
> > As previously mentioned, Iceberg is under active development at Netflix,
> > and is being used in processing large volumes of data in Amazon EC2.
> >
> > Iceberg license documentation is already based on Apache guidelines for
> > LICENSE and NOTICE content.
> > Meritocracy
> >
> > We value meritocracy and we understand that it is the basis for an open
> > community that encourages multiple companies and individuals to
> contribute
> > and be invested in the project’s future. We will encourage and monitor
> > participation and make sure to extend privileges and responsibilities to
> > all contributors.
> > Community
> >
> > Iceberg is currently being used by developers at Netflix and a growing
> > number of users are actively using it in production environments. Iceberg
> > has received contributions from developers working at Hortonworks,
> WeWork,
> > and Palantir. By bringing Iceberg to Apache we aim to assure current and
> > future contributors that the Iceberg community is meritocratic and open,
> in
> > order to broaden and diversity the user and developer community.
> > Core Developers
> >
> > Iceberg was initially developed at Netflix and is under active
> development.
> > We believe Netflix will be of interest to a broad range of users and
> > developers and that incubating the project at the ASF will help us build
> a

[ANNOUNCE] Apache Tephra-0.15.0-incubating released

[James Taylor]

Hi All,

The Apache Tephra team is excited to announce the latest release of Apache
Tephra-0.15.0-incubating. This is the eighth release of Apache Tephra.

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

The release artifacts are available at
http://www.apache.org/dyn/closer.cgi/incubator/tephra/0.15.0-incubating/src

Maven artifacts have also been made available on repository.apache.org.

We would like to thank all the contributors that made this release possible.

Thanks,
The Apache Tephra (incubating) Team

=

*Disclaimer*

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

[RESULT][VOTE] Release of Apache Tephra-0.15.0-incubating [rc1]

[James Taylor]

The vote is now closed and passes with 3 +1s and no +0 or -1s.
Thanks to those who voted.

James

On Tue, Sep 4, 2018 at 7:36 AM James Taylor  wrote:

> +1 (binding)
>
> Built from scratch
> Successfully ran all unit tests
>
> On Tue, Sep 4, 2018 at 12:55 AM Justin Mclean 
> wrote:
>
>> Hi,
>>
>> +1 (binding)
>>
>> I checked:
>> - incubating in name
>> - signatures and hashes good
>> - LICENSE and NOTICE good (binary NOTICE year needs updating)
>> - No unexpected binary files
>> - all source files have ASF headers
>> - can compile from source
>>
>> Thanks,
>> Justin
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>
>>

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

[James Taylor]

+1 (binding)

Built from scratch
Successfully ran all unit tests

On Tue, Sep 4, 2018 at 12:55 AM Justin Mclean 
wrote:

> Hi,
>
> +1 (binding)
>
> I checked:
> - incubating in name
> - signatures and hashes good
> - LICENSE and NOTICE good (binary NOTICE year needs updating)
> - No unexpected binary files
> - all source files have ASF headers
> - can compile from source
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Zipkin into the Apache Incubator

[James Taylor]

+1 (binding)

On Sun, Aug 26, 2018 at 8:41 PM Greg Trasuk  wrote:

> +1 Accept Zipkin (binding).
>
> Greg Trasuk.
>
> > On Aug 26, 2018, at 11:14 PM, Mick Semb Wever  wrote:
> >
> > After a brief discussion¹ I would like to call a VOTE to accept Zipkin
> into the Apache Incubator.
> > The full proposal is available on the wiki² and is pasted below in text
> form as well.
> >
> > This vote will run at least 72 hours. Please VOTE as follows:
> >
> > [ ] +1 Accept Zipkin into the Apache Incubator
> > [ ] +0 No opinion
> > [ ] -1 Do not accept Zipkin into the Apache Incubator because…
> >
> > regards,
> > Mick
> >
> > [1]
> https://lists.apache.org/thread.html/54798a5059db1d5716ed9910a15c92945509a25ec3b7ccb6b1215c53@%3Cgeneral.incubator.apache.org%3E
> > [2] https://wiki.apache.org/incubator/ZipkinProposal
> >
> >
> >
> > = Abstract =
> > Zipkin is a distributed tracing system. It helps gather timing data
> needed to troubleshoot latency problems in microservice architectures. It
> manages both the collection and lookup of this data. Zipkin’s design is
> based on the Google Dapper paper.
> >
> > = Proposal =
> > Zipkin provides a defined data model and payload type for distributed
> trace data collection. It also provides an UI and http api for querying the
> data. Its server implements this api and includes abstractions for storage
> and transport of trace payloads. The combination of these parts avoid
> lock-in to a specific tracing backend. For example, Zipkin includes
> integration with different open source storage mechanisms like Apache
> Cassandra and Elasticsearch. It also includes bridges to convert collected
> data and forward it to service offerings such as Amazon X-Ray and Google
> Stackdriver. Ecosystem offering extend this portability further.
> >
> > While primarily focused on the system, Zipkin also includes tracing
> libraries which applications use to report timing information. Zipkin's
> core organization includes tracer libraries written in Java, Javascript,
> Go, PHP and Ruby. These libraries use the formats mentioned above to report
> data, as well "B3" which is a header format needed to send trace
> identifiers along with production requests. Many Zipkin libraries can also
> send data directly to other services such as Amazon X-Ray and Google
> Stackdriver, skipping any Zipkin infrastructure. There are also more Zipkin
> tracing libraries outside the core organization than inside it. This is due
> to the "OpenZipkin" culture of promoting ecosystem work.
> >
> > = Background =
> > Zipkin began in 2012 at Twitter during a time they were investigating
> performance problems underlying the "fail whale" seen by users. The name
> Zipkin is from the Turkish word for harpoon: the harpoon that will kill the
> failures! Incidentally, Zipkin was not the first tracing system, it had
> roots in a former system at Twitter named BigBrotherBird. It is due to
> BigBrotherBird that the de-facto tracing headers we still use today include
> the prefix "X-B3".
> >
> > In 2015, a community of users noticed the project was not healthy in so
> far as it hadn't progressed and often didn't accept pull requests, and the
> Cassandra backend was stuck on an unmaintained library. For example, the
> Apache Incubator H-Trace project started in some ways as a reaction to the
> inability to customize the code. The root cause of this was Twitter moving
> to internal storage (Manhattan) and also the project not being managed as a
> product. By mid 2015, the community regrouped as OpenZipkin and the
> codebase moved from Twitter to an org also named OpenZipkin. This led to
> fast progress on concerns including initially a server rewrite and Docker
> based deployment.
> >
> > In 2018, the second version of the data model completed, and along the
> way, many new libraries became standard, including javascript, golang and
> PHP. The community is dramatically larger than 2015, and Zipkin remains the
> most popular tracing system despite heavy competition.
> >
> > = Rationale =
> > Zipkin is a de-facto distributed tracing system, which is more important
> as architectures become more fine grained due to popularity of microservice
> or even serverless architectures. Applications transition to use more
> complex communication including asynchronous code and service mesh,
> increasing the need for tools that visualize the behavior of requests as
> they map across an architecture.
> >
> > Zipkin's server is focused only on distributed tracing. It is meant to
> be used alongside existing logging and metrics systems. Generally, the
> community optimizes brown field concerns such as interop over breaking
> changes such as experimental features. The combination of code and
> community make Zipkin a safe and easier choice for various sites to
> introduce or grow their observability practice.
> >
> > = Initial Goals =
> > The initial goals are to mature OpenZipkin's community process. For
> example, while OpenZipkin has a good 

Re: [PROPOSAL] Zipkin for Apache Incubator

[James Taylor]

+1

On Thu, Aug 23, 2018 at 3:11 AM  wrote:

> Very excited about the proposal and looking forward to the Apache journey.
>
> Bas van Beek
>
> On 2018/08/17 09:29:47, Adrian Cole  wrote:
> > I would like to propose Zipkin as an Apache Incubator project.>
> >
> > The text of the proposal can be found below as well as on the Incubator
> wiki:>
> >
> > https://wiki.apache.org/incubator/ZipkinProposal>
> >
> > I believe we should have 3 mentors.. currently we have 2 (plus Wu>
> > Sheng and I who are familiar but not mentor-grade :P). If another>
> > person can volunteer to mentor us, would be sweet.>
> >
> > -Adrian>
> >
> > = Abstract =>
> > Zipkin is a distributed tracing system. It helps gather timing data>
> > needed to troubleshoot latency problems in microservice architectures.>
> > It manages both the collection and lookup of this data. Zipkin’s>
> > design is based on the Google Dapper paper.>
> >
> > = Proposal =>
> > Zipkin provides a defined data model and payload type for distributed>
> > trace data collection. It also provides an UI and http api for>
> > querying the data. Its server implements this api and includes>
> > abstractions for storage and transport of trace payloads. The>
> > combination of these parts avoid lock-in to a specific tracing>
> > backend. For example, Zipkin includes integration with different open>
> > source storage mechanisms like Apache Cassandra and Elasticsearch. It>
> > also includes bridges to convert collected data and forward it to>
> > service offerings such as Amazon X-Ray and Google Stackdriver.>
> > Ecosystem offering extend this portability further.>
> >
> > While primarily focused on the system, Zipkin also includes tracing>
> > libraries which applications use to report timing information.>
> > Zipkin's core organization includes tracer libraries written in Java,>
> > Javascript, Go, PHP and Ruby. These libraries use the formats>
> > mentioned above to report data, as well "B3" which is a header format>
> > needed to send trace identifiers along with production requests. Many>
> > Zipkin libraries can also send data directly to other services such as>
> > Amazon X-Ray and Google Stackdriver, skipping any Zipkin>
> > infrastructure. There are also more Zipkin tracing libraries outside>
> > the core organization than inside it. This is due to the "OpenZipkin">
> > culture of promoting ecosystem work.>
> >
> > = Background =>
> > Zipkin began in 2012 at Twitter during a time they were investigating>
> > performance problems underlying the "fail whale" seen by users. The>
> > name Zipkin is from the Turkish word for harpoon: the harpoon that>
> > will kill the failures! Incidentally, Zipkin was not the first tracing>
> > system, it had roots in a former system at Twitter named>
> > BigBrotherBird. It is due to BigBrotherBird that the de-facto tracing>
> > headers we still use today include the prefix "X-B3".>
> >
> > In 2015, a community of users noticed the project was not healthy in>
> > so far as it hadn't progressed and often didn't accept pull requests,>
> > and the Cassandra backend was stuck on an unmaintained library. For>
> > example, the Apache Incubator H-Trace project started in some ways as>
> > a reaction to the inability to customize the code. The root cause of>
> > this was Twitter moving to internal storage (Manhattan) and also the>
> > project not being managed as a product. By mid 2015, the community>
> > regrouped as OpenZipkin and the codebase moved from Twitter to an org>
> > also named OpenZipkin. This led to fast progress on concerns including>
> > initially a server rewrite and Docker based deployment.>
> >
> > In 2018, the second version of the data model completed, and along the>
> > way, many new libraries became standard, including javascript, golang>
> > and PHP. The community is dramatically larger than 2015, and Zipkin>
> > remains the most popular tracing system despite heavy competition.>
> >
> > = Rationale =>
> > Zipkin is a de-facto distributed tracing system, which is more>
> > important as architectures become more fine grained due to popularity>
> > of microservice or even serverless architectures. Applications>
> > transition to use more complex communication including asynchronous>
> > code and service mesh, increasing the need for tools that visualize>
> > the behavior of requests as they map across an architecture.>
> >
> > Zipkin's server is focused only on distributed tracing. It is meant to>
> > be used alongside existing logging and metrics systems. Generally, the>
> > community optimizes brown field concerns such as interop over breaking>
> > changes such as experimental features. The combination of code and>
> > community make Zipkin a safe and easier choice for various sites to>
> > introduce or grow their observability practice.>
> >
> > = Initial Goals =>
> > The initial goals are to mature OpenZipkin's community process. For>
> > example, while OpenZipkin has a good collaborative process, it lacks>
> > 

[VOTE] Release of Apache Tephra-0.15.0-incubating [rc1]

[James Taylor]

Hi all,

This is a call for a vote on releasing Apache Tephra 0.15.0-incubating,
release candidate 1. This is the eighth release of Tephra. The Tephra dev
community has voted on and approved a proposal to release Tephra
0.15.0-incubating, release candidate 1.

PPMC Vote Call: https://s.apache.org/69XD

PPMC Vote Result: https://s.apache.org/Pvkd

The source tarball, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/incubator/tephra/0.15.0-incubating-rc1/src

The tag to be voted upon is v0.15.0-incubating:
https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=shortlog;h=refs/tags/v0.15.0-incubating

The release hash is fe4885003dfbc8fcfc2d0ae4192a109b03eaebe5:
https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=fe4885003dfbc8fcfc2d0ae4192a109b03eaebe5

The Nexus Staging URL:
https://repository.apache.org/content/repositories/orgapachetephra-1012

Release artifacts are signed with the following key:
http://people.apache.org/keys/committer/jamestaylor

KEYS file available:
https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS

For information about the contents of this release, see:
https://dist.apache.org/repos/dist/dev/incubator/tephra/0.15.0-incubating-rc1/CHANGES.txt

Please vote on releasing this package as Apache Tephra 0.15.0-incubating

The vote will be open for at least 72 hours.

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

Thanks,
James

[RESULT][VOTE] Release of Apache Tephra-0.14.0-incubating [rc1]

[James Taylor]

The vote is now closed and passes with 7 +1 votes and no +0 or -1 votes.
Thanks to everyone who voted.

James

On Thu, May 24, 2018 at 4:03 PM, James Taylor <jamestay...@apache.org>
wrote:

> +1 (transferred from my dev vote)
>
> On Thu, May 24, 2018 at 6:49 AM, larry mccay <lmc...@apache.org> wrote:
>
>> * built from source and ran all unit tests - over 1hr!
>> * checked LICENSE and NOTICE files
>> * Noticed things that others have already noted
>> * Noted that there is no CHANGES file in the release artifact - there is a
>> CHANGES.txt in
>> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.14
>> .0-incubating-rc1/
>> but this is not
>> cumulative across releases which is what I would expect
>>
>> Nothing that should block the release.
>>
>> +1
>>
>>
>> On Wed, May 23, 2018 at 8:13 PM, Billie Rinaldi <bil...@apache.org>
>> wrote:
>>
>> > +1 binding.
>> >
>> > One odd thing I noticed was the existence of these directories in the
>> > source tarball, but since they don't contain any files they can be
>> > addressed in the next release:
>> > apache-tephra-0.14.0-incubating/${project.basedir}/
>> > apache-tephra-0.14.0-incubating/${project.basedir}/src
>> > apache-tephra-0.14.0-incubating/${project.basedir}/src/main
>> > apache-tephra-0.14.0-incubating/${project.basedir}/src/main/site
>> > apache-tephra-0.14.0-incubating/${project.basedir}/src/main/
>> site/resources
>> > apache-tephra-0.14.0-incubating/${project.basedir}/
>> > src/main/site/resources/repo
>> >
>> > Another thing I would suggest addressing is that the jars published to
>> the
>> > maven repo don't contain LICENSE and NOTICE files. I'm not sure how this
>> > happened, since these files are typically added by default when projects
>> > use the ASF parent pom.
>> >
>> > Billie
>> >
>> > On 5/21/18 6:51 PM, James Taylor wrote:
>> >
>> > > Hi all,
>> > >
>> > > This is a call for a vote on releasing Apache Tephra
>> 0.14.0-incubating,
>> > > release candidate 1. This is the seventh release of Tephra. The Tephra
>> > dev
>> > > community has voted on and approved a proposal to release Tephra
>> > > 0.14.0-incubating, release candidate 1.
>> > >
>> > > PPMC Vote Call: https://s.apache.org/jWVD
>> > >
>> > > PPMC Vote Result: https://s.apache.org/zwog
>> > >
>> > > The source tarball, including signatures, digests, etc. can be found
>> at:
>> > > https://dist.apache.org/repos/dist/dev/incubator/tephra/0.14
>> > > .0-incubating-rc1/src
>> > >
>> > > The tag to be voted upon is v0.14.0-incubating:
>> > > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
>> > > it;a=shortlog;h=refs/tags/v0.14.0-incubating
>> > >
>> > > The release hash is e93942adae0ece286157a8f6a2e5c63b53669e03:
>> > > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
>> > > it;a=commit;h=e93942adae0ece286157a8f6a2e5c63b53669e03
>> > >
>> > > The Nexus Staging URL:
>> > > https://repository.apache.org/content/repositories/orgapache
>> tephra-1011
>> > >
>> > > Release artifacts are signed with the following key:
>> > > http://people.apache.org/keys/committer/jamestaylor
>> > >
>> > > KEYS file available:
>> > > https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
>> > >
>> > > For information about the contents of this release, see:
>> > > https://dist.apache.org/repos/dist/dev/incubator/tephra/0.14
>> > > .0-incubating-rc1/CHANGES.txt
>> > >
>> > > Please vote on releasing this package as Apache Tephra
>> 0.14.0-incubating
>> > >
>> > > The vote will be open for 72 hours.
>> > >
>> > > [ ] +1 Release this package as Apache Tephra 0.14.0-incubating
>> > > [ ] +0 no opinion
>> > > [ ] -1 Do not release this package because ...
>> > >
>> > > Thanks,
>> > > James
>> >
>>
>
>

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

[James Taylor]

+1 (transferred from my dev vote)

On Thu, May 24, 2018 at 6:49 AM, larry mccay <lmc...@apache.org> wrote:

> * built from source and ran all unit tests - over 1hr!
> * checked LICENSE and NOTICE files
> * Noticed things that others have already noted
> * Noted that there is no CHANGES file in the release artifact - there is a
> CHANGES.txt in
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.
> 14.0-incubating-rc1/
> but this is not
> cumulative across releases which is what I would expect
>
> Nothing that should block the release.
>
> +1
>
>
> On Wed, May 23, 2018 at 8:13 PM, Billie Rinaldi <bil...@apache.org> wrote:
>
> > +1 binding.
> >
> > One odd thing I noticed was the existence of these directories in the
> > source tarball, but since they don't contain any files they can be
> > addressed in the next release:
> > apache-tephra-0.14.0-incubating/${project.basedir}/
> > apache-tephra-0.14.0-incubating/${project.basedir}/src
> > apache-tephra-0.14.0-incubating/${project.basedir}/src/main
> > apache-tephra-0.14.0-incubating/${project.basedir}/src/main/site
> > apache-tephra-0.14.0-incubating/${project.basedir}/
> src/main/site/resources
> > apache-tephra-0.14.0-incubating/${project.basedir}/
> > src/main/site/resources/repo
> >
> > Another thing I would suggest addressing is that the jars published to
> the
> > maven repo don't contain LICENSE and NOTICE files. I'm not sure how this
> > happened, since these files are typically added by default when projects
> > use the ASF parent pom.
> >
> > Billie
> >
> > On 5/21/18 6:51 PM, James Taylor wrote:
> >
> > > Hi all,
> > >
> > > This is a call for a vote on releasing Apache Tephra 0.14.0-incubating,
> > > release candidate 1. This is the seventh release of Tephra. The Tephra
> > dev
> > > community has voted on and approved a proposal to release Tephra
> > > 0.14.0-incubating, release candidate 1.
> > >
> > > PPMC Vote Call: https://s.apache.org/jWVD
> > >
> > > PPMC Vote Result: https://s.apache.org/zwog
> > >
> > > The source tarball, including signatures, digests, etc. can be found
> at:
> > > https://dist.apache.org/repos/dist/dev/incubator/tephra/0.14
> > > .0-incubating-rc1/src
> > >
> > > The tag to be voted upon is v0.14.0-incubating:
> > > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
> > > it;a=shortlog;h=refs/tags/v0.14.0-incubating
> > >
> > > The release hash is e93942adae0ece286157a8f6a2e5c63b53669e03:
> > > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
> > > it;a=commit;h=e93942adae0ece286157a8f6a2e5c63b53669e03
> > >
> > > The Nexus Staging URL:
> > > https://repository.apache.org/content/repositories/
> orgapachetephra-1011
> > >
> > > Release artifacts are signed with the following key:
> > > http://people.apache.org/keys/committer/jamestaylor
> > >
> > > KEYS file available:
> > > https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
> > >
> > > For information about the contents of this release, see:
> > > https://dist.apache.org/repos/dist/dev/incubator/tephra/0.14
> > > .0-incubating-rc1/CHANGES.txt
> > >
> > > Please vote on releasing this package as Apache Tephra
> 0.14.0-incubating
> > >
> > > The vote will be open for 72 hours.
> > >
> > > [ ] +1 Release this package as Apache Tephra 0.14.0-incubating
> > > [ ] +0 no opinion
> > > [ ] -1 Do not release this package because ...
> > >
> > > Thanks,
> > > James
> >
>

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

[James Taylor]

Hi all,

This is a call for a vote on releasing Apache Tephra 0.14.0-incubating,
release candidate 1. This is the seventh release of Tephra. The Tephra dev
community has voted on and approved a proposal to release Tephra
0.14.0-incubating, release candidate 1.

PPMC Vote Call: https://s.apache.org/jWVD

PPMC Vote Result: https://s.apache.org/zwog

The source tarball, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/incubator/tephra/0.14.0-incubating-rc1/src

The tag to be voted upon is v0.14.0-incubating:
https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=shortlog;h=refs/tags/v0.14.0-incubating

The release hash is e93942adae0ece286157a8f6a2e5c63b53669e03:
https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=e93942adae0ece286157a8f6a2e5c63b53669e03

The Nexus Staging URL:
https://repository.apache.org/content/repositories/orgapachetephra-1011

Release artifacts are signed with the following key:
http://people.apache.org/keys/committer/jamestaylor

KEYS file available:
https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS

For information about the contents of this release, see:
https://dist.apache.org/repos/dist/dev/incubator/tephra/0.14.0-incubating-rc1/CHANGES.txt

Please vote on releasing this package as Apache Tephra 0.14.0-incubating

The vote will be open for 72 hours.

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

Thanks,
James

Re: [VOTE] Release Apache Omid 0.9.0.0 (incubating)

[James Taylor]

+1 (transferring my vote over from dev list vote)

On Mon, May 21, 2018 at 12:39 PM, Ohad Shacham 
wrote:

> Hi,
>
>
> The Apache Omid community has voted on and approved a proposal
> to release Apache Omid 0.9.0.0-incubating.
>
> PPMC Vote Call:http://mail-archives.apache.org/mod_mbox/omid-dev/
> 201805.mbox/%3cCAHuxFyOJZ8=Ud2xUQ2DRbGPZZnoQpVAUnBxPXwYO5
> gs_xr+...@mail.gmail.com%3e
>
>
> PPMC Vote Result:
>
> http://mail-archives.apache.org/mod_mbox/omid-dev/201805.
> mbox/%3cCANQiJeUua0BiH+MAsqPirN2UTRFnF7dcE+iPyLYjA6eA03txLg@mail.gmail.
> com%3e
>
>
> PPMC Vote Summary:
> 3 binding (IPMC member) +1 votes
> 0 non-binding PPMC member +1 votes
> No -1 votes
>
> Release notes for the 0.9.0.0
> release:https://dist.apache.org/repos/dist/dev/incubator/
> omid/0.9.0.0-rc3/RELEASE_NOTES.html
>
>
> Git tag for the release:
>
> https://git-wip-us.apache.org/repos/asf/incubator-omid.git/?
> p=incubator-omid.git;a=tag;h=229831bc377e47431cc7cbc211803069158b5711
>
>
> Sources for the release:
>
> https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.
> 0-rc3/apache-omid-incubating-0.9.0.0-src.tar.gz
>
>
> Source release verification: PGP Signature:
>
> https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.
> 0-rc3/apache-omid-incubating-0.9.0.0-src.tar.gz.asc
>
>
> SHA512 Hash:
>
> https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.
> 0-rc3/apache-omid-incubating-0.9.0.0-src.tar.gz.sha512
>
>
> Keys to verify the signature of the release artifact are available at:
>
> https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.0-rc3/KEYS
>
>
> We request the permission of IPMC to publish the above release candidate as
> Apache Omid 0.9.0.0-incubating. Please try out the package and vote. The
> vote is open for a minimum of 72 hours or until the necessary number of
> votes (3 binding +1s) is reached. [ ] +1 Release this package as Apache
> Omid 0.9.0.0-incubating [ ] 0 I don't feel strongly about it, but I'm okay
> with the release [ ] -1 Do not release this package because... Please add
> (binding) if your vote is binding.
>
>
> Thanks,
> Ohad
>

Re: [VOTE] Release Apache Omid 0.9.0.0 (incubating)

[James Taylor]

@Justin - thanks for taking the time to review. Really appreciate it. Looks
like there's some confusion, though. Prior to starting this vote, you
approved the change on the JIRA here[1], but now you've -1'ed the release.
At this point, we're trying to get clarification on OMID-44 so that when we
go through another vote, we make sure we've done it correctly.

Would you have time to please review the change on the JIRA so we can spin
up the next RC?

Thanks,
James


[1]
https://issues.apache.org/jira/browse/OMID-44?focusedCommentId=16424626=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16424626

On Fri, Apr 13, 2018 at 8:47 AM, Matt Sicker  wrote:

> The protobuf issue I was able to fix locally by installing protobuf@2.6
> (homebrew) and modifying my PATH for the build command. I still had failing
> tests, though.
>
> On 12 April 2018 at 19:23, Justin Mclean  wrote:
>
> > Hi,
> >
> > -1 binding as NOTICE is incorrect. The NOTICE file need to be keep as
> > small as possible [1]
> >
> > I checked:
> > - incubating in file name
> > - signatures good although it would be best to sign with an apache.org
> > email address
> > - LICENSE is fine
> > - NOTICE file contains wrong year (2016) and incorrectly lists files that
> > have 3rd party ALv2 headers. Where did these files come from? It looks
> like
> > here [4] which has a NOTICE file [4]
> > - a couple of files are missing ASF headers [2][3]
> > - no unexpected binary files
> > - Can't compile from source. Looks like I have a newer version of
> > protobuf. May be an issue for other people as well?
> >
> > Not 100% certain but I think that the NOTICE file [5] needs to be taken
> > into account, however it may be that the version of the files you have
> were
> > taken when no NOTICE files existed? (It was committed in 2014? and the
> > copyright is 2010 on those files.)
> >
> > Thanks,
> > Justin
> >
> > 1. http://www.apache.org/dev/licensing-howto.html#mod-notice
> > 2. apache-omid-incubating-0.9.0.0-src/tso-server/src/main/
> > resources/default-omid-server-configuration.yml
> > 3. apache-omid-incubating-0.9.0.0-src/benchmarks/src/main/
> > resources/default-tso-server-benchmark-config.yml
> > 4.https://github.com/linkedin/MTBT/
> > 5. https://github.com/linkedin/MTBT/blob/master/NOTICE
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
>
> --
> Matt Sicker 
>

Re: [VOTE] Release Apache Omid 0.9.0.0 (incubating)

[James Taylor]

Forwarding my +1 from the dev list.

James

On Thu, Mar 22, 2018 at 8:31 AM Henk P. Penning  wrote:

> On Thu, 22 Mar 2018, Ohad Shacham wrote:
>
> > Date: Thu, 22 Mar 2018 13:29:55 +0100
> > From: Ohad Shacham 
> > To: general@incubator.apache.org
> > Subject: [VOTE] Release Apache Omid 0.9.0.0 (incubating)
> >
> > Hi,
> >
> >
> > The Apache Omid community has voted on and approved a proposal
> > to release Apache Omid 0.9.0.0-incubating.
>
> > MD5 Hash:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/omid/0.9.0.0-rc1/apache-omid-incubating-0.9.0.0-src.tar.gz.md5
>
>Please do NOT publish .md5's anymore.
>Please DO publish a .sha1, .sha256 or .sha512 instead.
>
>https://www.apache.org/dev/release-distribution#sigs-and-sums
>
>There is no need to re-vote ; just fix dist/dev/incubator/omid/
>before you publish.
>
> > Ohad
>
>Regards,
>
>Henk Penning
>
>    _
> Henk P. Penning, ICT-beta R Uithof MG-403_/ \_
> Faculty of Science, Utrecht UniversityT +31 30 253 4106 / \_/ \
> Leuvenlaan 4, 3584CE Utrecht, NL  F +31 30 253 4553 \_/ \_/
> http://www.staff.science.uu.nl/~penni101/ M penn...@uu.nl \_/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Accept Druid into the Apache Incubator

[James Taylor]

+1 (binding)

On Thu, Feb 22, 2018 at 2:55 PM, Andrew Purtell  wrote:

> +1 (binding)
>
>
> On Thu, Feb 22, 2018 at 11:03 AM, Julian Hyde  wrote:
>
> > Hi all,
> >
> > After some discussion on the Druid proposal[1], I'd like to
> > start a vote on accepting Druid into the Apache Incubator,
> > per the ASF policy[2] and voting rules[3].
> >
> > A vote for accepting a new Apache Incubator podling is a
> > majority vote for which only Incubator PMC member votes are
> > binding. Votes from other people are also welcome as an
> > indication of people's enthusiasm (or lack thereof).
> >
> > Please do not use this VOTE thread for discussions.  If
> > needed, start a new thread instead.
> >
> > This vote will run for at least 72 hours. Please VOTE as
> > follows:
> >  [ ] +1 Accept Druid into the Apache Incubator
> >  [ ] +0 Abstain
> >  [ ] -1 Do not accept Druid into the Apache Incubator
> > because ...
> >
> > The proposal is listed below, but you can also access it on
> > the wiki[4].
> >
> > Julian
> >
> > [1] https://lists.apache.org/thread.html/b95f90a30b6e8587e9b108f368b07c
> > 1b3e23e25ca592448d9c9f81e2@%3Cgeneral.incubator.apache.org%3E
> >
> > [2] https://incubator.apache.org/policy/incubation.html#
> > approval_of_proposal_by_sponsor
> >
> > [3] http://www.apache.org/foundation/voting.html
> >
> > [4] https://wiki.apache.org/incubator/DruidProposal
> >
> >
> >
> >
> >
> > = Druid Proposal =
> >
> > == Abstract ==
> >
> > Druid is a high-performance, column-oriented, distributed
> > data store.
> >
> > == Proposal ==
> >
> > Druid is an open source data store designed for real-time
> > exploratory analytics on large data sets. Druid's key
> > features are a column-oriented storage layout, a distributed
> > shared-nothing architecture, and ability to generate and
> > leverage indexing and caching structures. Druid is typically
> > deployed in clusters of tens to hundreds of nodes, and has
> > the ability to load data from Apache Kafka and Apache
> > Hadoop, among other data sources. Druid offers two query
> > languages: a SQL dialect (powered by Apache Calcite) and a
> > JSON-over-HTTP API.
> >
> > Druid was originally developed to power a slice-and-dice
> > analytical UI built on top of large event streams. The
> > original use case for Druid targeted ingest rates of
> > millions of records/sec, retention of over a year of data,
> > and query latencies of sub-second to a few seconds. Many
> > people can benefit from such capability, and many already
> > have (see http://druid.io/druid-powered.html). In addition,
> > new use cases have emerged since Druid's original
> > development, such as OLAP acceleration of data warehouse
> > tables and more highly concurrent applications operating
> > with relatively narrower queries.
> >
> > == Background ==
> >
> > Druid is a data store designed for fast analytics. It would
> > typically be used in lieu of more general purpose query
> > systems like Hadoop MapReduce or Spark when query latency is
> > of the utmost importance. Druid is often used as a data
> > store for powering GUI analytical applications.
> >
> > The buzzwordy description of Druid is a high-performance,
> > column-oriented, distributed data store. What we mean by
> > this is:
> >
> > * "high performance": Druid aims to provide low query
> >   latency and high ingest rates possible.
> > * "column-oriented": Druid stores data in a column-oriented
> >   format, like most other systems designed for analytics. It
> >   can also store indexes along with the columns.
> > * "distributed": Druid is deployed in clusters, typically of
> >   tens to hundreds of nodes.
> > * "data store": Druid loads your data and stores a copy of
> >   it on the cluster's local disks (and may cache it in
> >   memory). It doesn't query your data from some other
> >   storage system.
> >
> > == Rationale ==
> >
> > Druid is a mature, active project with a large number of
> > production installations, dozens of contributors to each
> > release, and multiple vendors offering professional
> > support. Given Druid's strong community, its close
> > integration with many other Apache projects (such as Kafka,
> > Hadoop, and Calcite), and its pre-existing Apache-inspired
> > governance structure, we feel that Apache is the best home
> > for the project on a long-term basis.
> >
> > == Current Status ==
> >
> > === Meritocracy ===
> >
> > Since Druid was first open sourced the original developers
> > have solicited contributions from others, including through
> > our blog, the project mailing lists, and through accepting
> > GitHub pull requests. We have an Apache-inspired governance
> > structure with a PMC and committers, and our committer ranks
> > include a good number of people from outside the original
> > development team.
> >
> > === Community ===
> >
> > The Druid core developers have sought to nurture a community
> > throughout the life of the project. We use GitHub as the
> > 

Re: [VOTE] Release of Apache Tephra-0.13.0-incubating [rc2]

[James Taylor]

John - there appears to be some confusion. Would you mind clearing up
whether you voted or not? Sorry for bugging you.

Thanks,
James

On Thu, Sep 21, 2017 at 1:30 PM, James Taylor <jamestay...@apache.org>
wrote:

> I thought John already changed his vote to +1 based on this comment, no?
>
> > On Wed, Sep 20, 2017 at 7:56 PM, John D. Ament <johndam...@apache.org>
>> > wrote:
>> >
>> >> I'm fine with giving a +1 assuming the NOTICE issue is fixed for next
>> >> release.  Please feel free to ping me if you want a review of the
>> NOTICE
>> >> contents before release.
>> >>
>> >> John
>>
>

Re: [VOTE] Release of Apache Tephra-0.13.0-incubating [rc2]

[James Taylor]

I thought John already changed his vote to +1 based on this comment, no?

> On Wed, Sep 20, 2017 at 7:56 PM, John D. Ament 
> > wrote:
> >
> >> I'm fine with giving a +1 assuming the NOTICE issue is fixed for next
> >> release.  Please feel free to ping me if you want a review of the NOTICE
> >> contents before release.
> >>
> >> John
>

Re: [VOTE] Release of Apache Tephra-0.13.0-incubating [rc2]

[James Taylor]

John - thanks for the review. If things look acceptable now, would you be
willing to cast a vote?

Anyone else?

Thanks,
James

On Wed, Sep 20, 2017 at 11:58 AM Gokul Gunasekaran  wrote:

> Thanks, John! Is there anything else that we can do to address
> concerns/issues regarding the release candidate?
>
> On Wed, Sep 20, 2017 at 11:26 AM, John D. Ament 
> wrote:
>
> > On Wed, Sep 20, 2017 at 2:21 PM Gokul Gunasekaran 
> > wrote:
> >
> > > Hi John,
> > >
> > > Regarding your comment,
> > >
> > > > > I don't see any of this text in your NOTICE file.  Likewise, I
> don't
> > > see
> > > > > where the contents of the NOTICE are coming from
> > > > >
> > >
> > > The LICENSE and NOTICE files that, are in the distribution, are present
> > in
> > > the tephra-distribution directory (named LICENSE_BINARY,
> NOTICE_BINARY).
> > > Please let us know if they should be placed in a different location
> and I
> > > can address the same in the JIRA mentioned below.
> > >
> >
> > It's fine to keep the binary copy of the NOTICE and LICENSE in your
> source
> > release.  Clearly marking them this way works fine.
> >
> >
> > >
> > > Also, let us know if you think we can proceed with the release. I have
> > > opened JIRA (https://issues.apache.org/jira/browse/TEPHRA-265) to
> > address
> > > the issue with the NOTICE file.
> > >
> > > Thanks,
> > > Gokul
> > >
> > > On Mon, Sep 18, 2017 at 7:24 PM, Andreas Neumann 
> > wrote:
> > >
> > > > John, is this a show stopper, or would it be ok if we address that
> Jira
> > > in
> > > > the next release?
> > > >
> > > > On Mon, Sep 18, 2017 at 6:47 PM, Gokul Gunasekaran  >
> > > > wrote:
> > > >
> > > > > Thanks so much for the explanation, John! Really appreciate it.
> > > > >
> > > > > I have opened a JIRA (https://issues.apache.org/
> > jira/browse/TEPHRA-265
> > > )
> > > > to
> > > > > fix this issue. Please let me know if you have any questions or
> > > comments
> > > > > about the same.
> > > > >
> > > > > On Mon, Sep 18, 2017 at 6:30 PM, John D. Ament <
> > johndam...@apache.org>
> > > > > wrote:
> > > > >
> > > > > > Gokul,
> > > > > >
> > > > > > On Mon, Sep 18, 2017 at 9:14 PM Gokul Gunasekaran <
> > go...@apache.org>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi John,
> > > > > > >
> > > > > > > Thanks for the review of the release candidate.
> > > > > > >
> > > > > > > - NOTICE file for Guice: The NOTICE_BINARY file under
> > > > > > tephra-distribution,
> > > > > > > contains the notice for Guice. Please let us how we can fix it
> > and
> > > we
> > > > > > will
> > > > > > > create a JIRA to fix this issue. We had followed the example of
> > > > > including
> > > > > > > libraries that has Apache License 2.0 in NOTICE, similar to the
> > > > > Fineract
> > > > > > > project.
> > > > > > >
> > > > > >
> > > > > > Do you have an example?  This is what your NOTICE file says:
> > > > > >
> > > > > > Apache Tephra includes Guice v3.0 and Guice Assisted Inject v3.0.
> > > > Tephra
> > > > > > elects to include this software in this distribution under the
> > Apache
> > > > > > License.
> > > > > > You can obtain a copy of the License at:
> > > > > > http://apache.org/licenses/LICENSE-2.0
> > > > > >
> > > > > > NOTICE files are meant to copy verbatim the existing NOTICE file.
> > > This
> > > > > is
> > > > > > what I see in the Guice 3 NOTICE files:
> > > > > >
> > > > > > Google Guice - Core Library
> > > > > > Copyright 2006-2011 Google, Inc.
> > > > > >
> > > > > > This product includes software developed at
> > > > > > The Apache Software Foundation (http://www.apache.org/).
> > > > > >
> > > > > >
> > > > > > Google Guice - Extensions - AssistedInject
> > > > > > Copyright 2006-2011 Google, Inc.
> > > > > >
> > > > > > This product includes software developed at
> > > > > > The Apache Software Foundation (http://www.apache.org/).
> > > > > >
> > > > > > I don't see any of this text in your NOTICE file.  Likewise, I
> > don't
> > > > see
> > > > > > where the contents of the NOTICE are coming from
> > > > > >
> > > > > > RE Fineract.  The last release I have of theres locally is 0.6.0
> > and
> > > it
> > > > > > does not have these issues, so not sure where you're getting this
> > > from.
> > > > > >
> > > > > > John
> > > > > >
> > > > > >
> > > > > > >
> > > > > > > - LGPL License: The Release Candidate - 2 doesn't include the
> > LGPL
> > > > > > license
> > > > > > > at all. Do you see LGPL license included anywhere (this might
> > have
> > > > been
> > > > > > > present in the Release Candidate - 1 which was fixed in Release
> > > > > > Candidate -
> > > > > > > 2)?
> > > > > > >
> > > > > > > Thanks,
> > > > > > > Gokul
> > > > > > >
> > > > > > > On Mon, Sep 18, 2017 at 5:08 PM, John D. Ament <
> > > > johndam...@apache.org>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi,
> > > > > > > >
> > > > > > > > I'm inclined to vote -1 unless someone convinces me
> 

Re: [VOTE] Graduate Apache Mnemonic project from Incubator

[James Taylor]

+1 (binding)

On Tue, Sep 19, 2017 at 1:45 PM, Luke Han  wrote:

> +1 (binding)
>
>
> Best Regards!
> -
>
> Luke Han
>
> On Tue, Sep 19, 2017 at 11:58 AM, Debo Dutta (dedutta) 
> wrote:
>
> > +1
> >
> > Sent from my iPhone
> >
> > > On Sep 19, 2017, at 11:58 AM, Johnu George  wrote:
> > >
> > > +1
> > >
> > > On Tue, Sep 19, 2017 at 10:23 AM, Gangumalla, Uma <
> > uma.ganguma...@intel.com>
> > > wrote:
> > >
> > >> +1 (binding)
> > >>
> > >> Regards,
> > >> Uma
> > >>
> > >>> On 9/19/17, 10:16 AM, "Gang(Gary) Wang"  wrote:
> > >>>
> > >>> Hello IPMC and everyone,
> > >>>
> > >>> The Mnemonic community has voted on its Dev list to graduate, The
> vote
> > >>> passed with
> > >>> 14 +1s (including  +9s from the PPMC) and 0 -1s.
> > >>>
> > >>> Here is the vote result thread in the Dev list:
> > >>> https://lists.apache.org/thread.html/bbc187108b73d57fddec0d6a6c2945
> > >> 27b626c
> > >>> 7c439a7cdab991ea84e@%3Cdev.mnemonic.apache.org%3E
> > >>>
> > >>> and the vote thread:
> > >>> https://lists.apache.org/thread.html/a49e82d507bb00839413e90b05cb8b
> > >> 9448ea2
> > >>> 42aeb021622f5deb323@%3Cdev.mnemonic.apache.org%3E
> > >>>
> > >>> With the discussion having settled down, I would now like to call for
> > >>> a recommendation VOTE to present the ASF board with the following
> > >>> resolution
> > >>> to graduate from incubation and establish Apache Mnemonic
> > >>> as a top-level project (TLP).
> > >>> https://lists.apache.org/thread.html/94664579041db58bfe2893af6e9d54
> > >> 9576526
> > >>> 53b278d4007e914c672@%3Cgeneral.incubator.apache.org%3E
> > >>>
> > >>> Apache Mnemonic entered incubation in March 2016. Since then there
> have
> > >>> been nine releases and four committers and two PMC candidate members
> > >>> have been added to the project. For each release, source artifacts
> > >>> have been made available. Based on the completed maturity evaluation,
> > >>> we believe that the project is ready to graduate from the incubator.
> > >>> More checklist info about graduation, please refer to
> > >>> https://cwiki.apache.org/confluence/display/MNEMONIC/
> > Maturity+Evaluation
> > >>>
> > >>> Please vote on whether to graduate Mnemonic from incubator and
> > >>> recommend the following graduation resolution to the ASF Board.
> > >>>
> > >>> [ ] +1 Graduate Apache Mnemonic from the Incubator
> > >>> [ ] +0 Don't care
> > >>> [ ] -1 Don't graduate Apache Mnemonic from the Incubator because...
> > >>>
> > >>> This VOTE will be open for at least 72 hours.
> > >>> Thanks to all Mentors and Apache Mnemonic Project members
> > >>> for their support and contributions again.
> > >>>
> > >>> The full text of the resolution is below.
> > >>> If approved by the Apache Incubator PMC members,
> > >>> the proposed resolution will be submitted to
> > >>> the Board of Directors for their consideration.
> > >>> --
> > >>> Establish the Apache Mnemonic Project
> > >>>
> > >>> WHEREAS, the Board of Directors deems it to be in the best interests
> of
> > >>> the Foundation and consistent with the Foundation's purpose to
> > establish
> > >>> a Project Management Committee charged with the creation and
> > maintenance
> > >>> of open-source software, for distribution at no charge to the public,
> > >>> related to a transparent nonvolatile hybrid memory oriented library
> for
> > >>> Big data, High-performance computing, and Analytics.
> > >>>
> > >>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > >>> (PMC), to be known as the "Apache Mnemonic Project", be and hereby is
> > >>> established pursuant to Bylaws of the Foundation, and be it further
> > >>>
> > >>> RESOLVED, that the Apache Mnemonic Project be and hereby is
> responsible
> > >>> for the creation and maintenance of software related to a transparent
> > >>> nonvolatile hybrid memory oriented library for Big data,
> > >>> High-performance computing and Analytics; and be it further
> > >>>
> > >>> RESOLVED, that the office of "Vice President, Apache Mnemonic" be and
> > >>> hereby is created, the person holding such office to serve at the
> > >>> direction of the Board of Directors as the chair of the Apache
> Mnemonic
> > >>> Project, and to have primary responsibility for management of the
> > >>> projects within the scope of responsibility of the Apache Mnemonic
> > >>> Project, and be it further
> > >>>
> > >>> RESOLVED, that the persons listed immediately below be and hereby are
> > >>> appointed to serve as the initial members of the Apache Mnemonic
> > >>> Project:
> > >>>
> > >>> * Andrew Kyle Purtell  
> > >>> * Debojyoti Dutta  
> > >>> * Gang Wang
> > >>> * Hao Cheng
> > >>> * James R. Taylor  
> > >>> * Johnu George 
> > 

Re: [VOTE] Release of Apache Tephra-0.13.0-incubating [rc2]

[James Taylor]

+1. Transferring my vote over from the dev list vote.

On Mon, Sep 18, 2017 at 10:13 AM, Andreas Neumann  wrote:

> Hi all,
>
> This is a call for a vote on releasing Apache Tephra 0.13.0-incubating,
> release candidate 2. This is the sixth release of Tephra.
>
> The Apache Tephra community has voted and approved the release.
>
> Vote thread:
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-
> dev/201709.mbox/%
> 3CCANpmDOfN7MPHYjKt-PqNd3yY1KtgyNn6L1ANT63xxPEdSsXQuA%40mail.gmail.com%3E
>
> Result thread:
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-
> dev/201709.mbox/%
> 3CCANpmDOe8T70zU4h%2BgknSJ%2B%3DTOAkUw9praf46GTtuz-5Cr2-7jA%
> 40mail.gmail.com%3E
>
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.13
> .0-incubating-rc2/src
>
> The tag to be voted upon is v0.13.0-incubating:
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
> it;a=shortlog;h=refs/tags/v0.13.0-incubating
>
> The release hash is 37467ce63934aca86f84eb61493733bb470450d7:
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
> it;a=commit;h=37467ce63934aca86f84eb61493733bb470450d7
>
> The Nexus Staging URL:
> https://repository.apache.org/content/repositories/orgapachetephra-1010
>
> Release artifacts are signed with the following key:
> http://people.apache.org/keys/committer/anew
>
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
>
> For information about the contents of this release, see:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.13
> .0-incubating-rc2/CHANGES.txt
>
> Please vote on releasing this package as Apache Tephra 0.13.0-incubating
>
> The vote will be open for 72 hours.
>
> [ ] +1 Release this package as Apache Tephra 0.13.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Andreas
>

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

[James Taylor]

+1. The RC passes all Phoenix unit tests.

On Fri, May 26, 2017 at 3:22 PM, Alan Gates  wrote:

> Forwarding my +1 from the dev list.
>
> Alan.
>
> On Fri, May 26, 2017 at 2:12 PM, Gokul Gunasekaran 
> wrote:
>
> > Hi all,
> >
> > This is a call for a vote on releasing Apache Tephra 0.12.0-incubating,
> > release candidate 1. This is the fifth release of Tephra.
> >
> > Apache Tephra community has voted and approved the release.
> >
> > Vote thread:
> > http://mail-archives.apache.org/mod_mbox/incubator-tephra-
> > dev/201705.mbox/%
> > 3CCAFgkoWGFt1m4puB-T83i0QCgbyqpR7SEiMqJHL8b%3DxVCcSmvng%40mail.gmail.com
> %
> > 3E
> >
> > Result thread:
> > http://mail-archives.apache.org/mod_mbox/incubator-tephra-
> > dev/201705.mbox/%3CCAFgkoWG5%3Dz9Fuu2xzLTiEOgFmTmZs53VRij7a
> > k3Zu2YY%2B2kciw%40mail.gmail.com%3E
> >
> > The source tarball, including signatures, digests, etc. can be found at:
> > https://dist.apache.org/repos/dist/dev/incubator/tephra/0.12
> > .0-incubating-rc1/src
> >
> > The tag to be voted upon is v0.12.0-incubating:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
> > it;a=shortlog;h=refs/tags/v0.12.0-incubating
> >
> > The release hash is 2bc62de4498bdb1d6b4647d6f102649d3f9d5df7:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
> > it;a=commit;h=2bc62de4498bdb1d6b4647d6f102649d3f9d5df7
> >
> > The Nexus Staging URL:
> > https://repository.apache.org/content/repositories/orgapachetephra-1008/
> >
> > Release artifacts are signed by:
> > http://people.apache.org/keys/committer/gokul
> >
> > KEYS file available:
> > https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
> >
> > For information about the contents of this release, see:
> > *https://dist.apache.org/repos/dist/dev/incubator/
> > tephra/0.12.0-incubating-rc1/CHANGES.txt
> >  > tephra/0.12.0-incubating-rc1/CHANGES.txt>*
> >
> > The vote will be open for 72 hours.
> >
> > [ ] +1 Release this package as Apache Tephra 0.12.0-incubating
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because ...
> >
> > Thanks,
> > Gokul
> >
>

Re: [VOTE] Release of Apache Tephra-0.11.0-incubating [rc2]

[James Taylor]

Forwarding my +1 from dev list too.

On Sat, Mar 11, 2017 at 8:53 AM Alan Gates  wrote:

> Forwarding my +1 from the dev list.
>
> Alan.
>
> > On Mar 10, 2017, at 5:18 PM, Gokul Gunasekaran  wrote:
> >
> > Hi all,
> >
> > This is a call for a vote on releasing Apache Tephra 0.11.0-incubating,
> > release candidate 2. This is the fourth release of Tephra.
> >
> > Apache Tephra community has voted and approved the release.
> >
> > Vote thread:
> >
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201703.mbox/%3CCAFgkoWEhJrFB5WdUJBh3qe5v9UqYxPHLRQRJQBKUr7gD%2BHOCEA%40mail.gmail.com%3E
> >
> > Result thread:
> >
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201703.mbox/%3CCAFgkoWHo6bQ6sN_X64_%3Df5PYV2SLhdswZ%2BbBbpp-jHK3smpALw%40mail.gmail.com%3E
> >
> > The source tarball, including signatures, digests, etc. can be found at:
> >
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.11.0-incubating-rc2/src
> >
> > The tag to be voted upon is v0.11.0-incubating:
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=shortlog;h=refs/tags/v0.11.0-incubating
> >
> > The release hash is 6c0ba4da1597394d9d24bfde7f50a8793ac85e67:
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=6c0ba4da1597394d9d24bfde7f50a8793ac85e67
> >
> > The Nexus Staging URL:
> > https://repository.apache.org/content/repositories/orgapachetephra-1007/
> >
> > Release artifacts are signed by:
> > http://people.apache.org/keys/committer/gokul
> >
> > KEYS file available:
> > https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
> >
> > For information about the contents of this release, see:
> >
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.11.0-incubating-rc2/CHANGES.txt
> >
> > Please vote on releasing this package as Apache Tephra 0.11.0-incubating.
> > Note that the vote for rc1 was canceled due to the bug
> > https://issues.apache.org/jira/browse/TEPHRA-223. This bug is fixed in
> rc2.
> >
> > The vote will be open for 72 hours.
> >
> > [ ] +1 Release this package as Apache Tephra 0.11.0-incubating
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because ...
> >
> > Thanks,
> > Gokul
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

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

[James Taylor]

IMHO, this bug is serious enough to be a showstopper. There's no workaround
for it in depent projects such as Phoenix. How about we roll another RC
with a fix today?

Other non Apache projects don't need to wait until the release closes (or
could even rely on non released bits).

James

On Mon, Feb 20, 2017 at 3:21 PM Poorna Chandra <poo...@apache.org> wrote:

> Hey James,
>
> There are other projects that depend on the 0.11.0 release, and need it in
> the next couple of days. This bug can be worked around in the dependent
> projects.
>
> I suggest letting this release go through by marking TEPHRA-223 as a known
> issue. We can do a 0.11.1 release immediately after fixing TEPHRA-223.
>
> Thanks,
> Poorna.
>
>
>
> On Mon, Feb 20, 2017 at 2:37 PM, James Taylor <jamestay...@apache.org>
> wrote:
>
> > Looks like a serious issue was found with TEPHRA-223, so switching my
> vote
> > to -1. Hopefully we can get a quick fix with a new RC very soon.
> >
> > James
> >
> > On Fri, Feb 17, 2017 at 12:12 PM, Alan Gates <alanfga...@gmail.com>
> wrote:
> >
> > > Forwarding my +1 from the dev list.
> > >
> > > Alan.
> > >
> > > > On Feb 17, 2017, at 11:52 AM, James Taylor <jamestay...@apache.org>
> > > wrote:
> > > >
> > > > Transferring my +1 from the dev list vote over here.
> > > >
> > > > On Fri, Feb 17, 2017 at 11:40 AM, Gokul Gunasekaran <
> go...@apache.org>
> > > > wrote:
> > > >
> > > >> Hi all,
> > > >>
> > > >> This is a call for a vote on releasing Apache Tephra
> > 0.11.0-incubating,
> > > >> release candidate 1. This is the fourth release of Tephra.
> > > >>
> > > >> Apache Tephra community has voted and approved the release.
> > > >>
> > > >> Vote thread:
> > > >> http://mail-archives.apache.org/mod_mbox/incubator-tephra-
> > > >> dev/201702.mbox/%
> > > >> 3CCAFgkoWEmagPPMPLREsK2CvWmS97_g0AE_1Bd7P1UWXbc3wYv-g%40mail
> > .gmail.com
> > > %3E
> > > >>
> > > >> Result thread:
> > > >> http://mail-archives.apache.org/mod_mbox/incubator-tephra-
> > > >> dev/201702.mbox/%3CCAFgkoWE4T5PoieC4aPQWK040i5L
> > > >> VHwbvnZ%2BH%3DnqwGu_O96Yf9A%40mail.gmail.com%3E
> > > >>
> > > >>
> > > >> The source tarball, including signatures, digests, etc. can be found
> > at:
> > > >> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.11
> > > >> .0-incubating-rc1/src
> > > >>
> > > >> The tag to be voted upon is v0.11.0-incubating:
> > > >> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
> > > >> it;a=shortlog;h=refs/tags/v0.11.0-incubating
> > > >>
> > > >> The release hash is d6327007b6240c9b2605c2e8d91ca9ac92ecedfc:
> > > >> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
> > > >> it;a=commit;h=d6327007b6240c9b2605c2e8d91ca9ac92ecedfc
> > > >>
> > > >> The Nexus Staging URL:
> > > >> https://repository.apache.org/content/repositories/
> > orgapachetephra-1006
> > > >>
> > > >> Release artifacts are signed with the following key:
> > > >> http://people.apache.org/keys/committer/gokul
> > > >>
> > > >> KEYS file available:
> > > >> https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
> > > >>
> > > >> For information about the contents of this release, see:
> > > >> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.11
> > > >> .0-incubating-rc1/CHANGES.txt
> > > >>
> > > >> Please vote on releasing this package as Apache Tephra
> > 0.11.0-incubating
> > > >>
> > > >> The vote will be open for 72 hours.
> > > >>
> > > >> [ ] +1 Release this package as Apache Tephra 0.11.0-incubating
> > > >> [ ] +0 no opinion
> > > >> [ ] -1 Do not release this package because ...
> > > >>
> > > >> Thanks,
> > > >> Gokul
> > > >>
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

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

[James Taylor]

Looks like a serious issue was found with TEPHRA-223, so switching my vote
to -1. Hopefully we can get a quick fix with a new RC very soon.

James

On Fri, Feb 17, 2017 at 12:12 PM, Alan Gates <alanfga...@gmail.com> wrote:

> Forwarding my +1 from the dev list.
>
> Alan.
>
> > On Feb 17, 2017, at 11:52 AM, James Taylor <jamestay...@apache.org>
> wrote:
> >
> > Transferring my +1 from the dev list vote over here.
> >
> > On Fri, Feb 17, 2017 at 11:40 AM, Gokul Gunasekaran <go...@apache.org>
> > wrote:
> >
> >> Hi all,
> >>
> >> This is a call for a vote on releasing Apache Tephra 0.11.0-incubating,
> >> release candidate 1. This is the fourth release of Tephra.
> >>
> >> Apache Tephra community has voted and approved the release.
> >>
> >> Vote thread:
> >> http://mail-archives.apache.org/mod_mbox/incubator-tephra-
> >> dev/201702.mbox/%
> >> 3CCAFgkoWEmagPPMPLREsK2CvWmS97_g0AE_1Bd7P1UWXbc3wYv-g%40mail.gmail.com
> %3E
> >>
> >> Result thread:
> >> http://mail-archives.apache.org/mod_mbox/incubator-tephra-
> >> dev/201702.mbox/%3CCAFgkoWE4T5PoieC4aPQWK040i5L
> >> VHwbvnZ%2BH%3DnqwGu_O96Yf9A%40mail.gmail.com%3E
> >>
> >>
> >> The source tarball, including signatures, digests, etc. can be found at:
> >> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.11
> >> .0-incubating-rc1/src
> >>
> >> The tag to be voted upon is v0.11.0-incubating:
> >> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
> >> it;a=shortlog;h=refs/tags/v0.11.0-incubating
> >>
> >> The release hash is d6327007b6240c9b2605c2e8d91ca9ac92ecedfc:
> >> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
> >> it;a=commit;h=d6327007b6240c9b2605c2e8d91ca9ac92ecedfc
> >>
> >> The Nexus Staging URL:
> >> https://repository.apache.org/content/repositories/orgapachetephra-1006
> >>
> >> Release artifacts are signed with the following key:
> >> http://people.apache.org/keys/committer/gokul
> >>
> >> KEYS file available:
> >> https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
> >>
> >> For information about the contents of this release, see:
> >> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.11
> >> .0-incubating-rc1/CHANGES.txt
> >>
> >> Please vote on releasing this package as Apache Tephra 0.11.0-incubating
> >>
> >> The vote will be open for 72 hours.
> >>
> >> [ ] +1 Release this package as Apache Tephra 0.11.0-incubating
> >> [ ] +0 no opinion
> >> [ ] -1 Do not release this package because ...
> >>
> >> Thanks,
> >> Gokul
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

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

[James Taylor]

Transferring my +1 from the dev list vote over here.

On Fri, Feb 17, 2017 at 11:40 AM, Gokul Gunasekaran 
wrote:

> Hi all,
>
> This is a call for a vote on releasing Apache Tephra 0.11.0-incubating,
> release candidate 1. This is the fourth release of Tephra.
>
> Apache Tephra community has voted and approved the release.
>
> Vote thread:
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-
> dev/201702.mbox/%
> 3CCAFgkoWEmagPPMPLREsK2CvWmS97_g0AE_1Bd7P1UWXbc3wYv-g%40mail.gmail.com%3E
>
> Result thread:
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-
> dev/201702.mbox/%3CCAFgkoWE4T5PoieC4aPQWK040i5L
> VHwbvnZ%2BH%3DnqwGu_O96Yf9A%40mail.gmail.com%3E
>
>
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.11
> .0-incubating-rc1/src
>
> The tag to be voted upon is v0.11.0-incubating:
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
> it;a=shortlog;h=refs/tags/v0.11.0-incubating
>
> The release hash is d6327007b6240c9b2605c2e8d91ca9ac92ecedfc:
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.g
> it;a=commit;h=d6327007b6240c9b2605c2e8d91ca9ac92ecedfc
>
> The Nexus Staging URL:
> https://repository.apache.org/content/repositories/orgapachetephra-1006
>
> Release artifacts are signed with the following key:
> http://people.apache.org/keys/committer/gokul
>
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
>
> For information about the contents of this release, see:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.11
> .0-incubating-rc1/CHANGES.txt
>
> Please vote on releasing this package as Apache Tephra 0.11.0-incubating
>
> The vote will be open for 72 hours.
>
> [ ] +1 Release this package as Apache Tephra 0.11.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Gokul
>

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

[James Taylor]

Transferring my +1 from dev vote here.

On Thu, Sep 15, 2016 at 10:44 PM, Poorna Chandra  wrote:

> Hi all,
>
> This is a call for a vote on releasing Apache Tephra 0.9.0-incubating,
> release candidate 1. This is the second release of Tephra.
>
> Apache Tephra community has voted and approved the release.
>
> Vote thread:
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-
> dev/201609.mbox/%3CCAC9o21R4KR-e%3DmzCsefvokpQWykOXTTnWt%
> 2BZwt0CjiZz1MsqAg%40mail.gmail.com%3E
>
> Result thread:
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-
> dev/201609.mbox/%3CCAC9o21Q9RJqDAo9n_AJWKaPm9_9iM4JoOL0bK9uh2thhS5Jn1g%
> 40mail.gmail.com%3E
>
> The source tarball, including signatures, digests, etc. can be found at:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.9.
> 0-incubating-rc1/src
>
> The tag to be voted upon is v0.9.0-incubating:
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.
> git;a=shortlog;h=refs/tags/v0.9.0-incubating
>
> The release hash is db235cdfa0d40d4e31bcd19ab350e9961719c79e:
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=
> db235cdfa0d40d4e31bcd19ab350e9961719c79e
>
> The Nexus Staging URL:
> https://repository.apache.org/content/repositories/orgapachetephra-1004
>
> Release artifacts are signed with the following key:
> http://people.apache.org/keys/committer/poorna
>
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
>
> For information about the contents of this release, see:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.9.
> 0-incubating-rc1/CHANGES.txt
>
> Please vote on releasing this package as Apache Tephra 0.9.0-incubating
>
> The vote will be open for 72 hours.
>
> [ ] +1 Release this package as Apache Tephra 0.9.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Poorna.
>

Re: [VOTE] Graduate Apache Twill as Top Level Project

[James Taylor]

+1 (binding)

On Thursday, June 2, 2016, Andrew Purtell  wrote:

> +1 (binding)
>
> On Thu, Jun 2, 2016 at 3:06 PM, Henry Saputra  >
> wrote:
>
> > Hi All,
> >
> > Following the DISCUSS thread about Apache Twill graduating as TLP, I
> would
> > like to send VOTE request thread.
> >
> > All the +1 binding votes sent in the DISCUSS will be counted in the final
> > tally unless the individual request otherwise.
> >
> > Here is the link to the VOTE in dev@ list:
> >
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6ZB1DZVWZJNd+-ib0NXZwyWebSBE0evs0Yp8uthe+=o...@mail.gmail.com%3e
> >
> >
> > Here is link to the VOTE result summary in the dev@list :
> >
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-twill-dev/201605.mbox/%3cCALuGr6aSYs=daVpeeYO0GPKdfu=dkhvyhw12jdj66-dpzsq...@mail.gmail.com%3e
> >
> >
> > The VOTE will run until June 6, 2016 4pm PST
> >
> > +1 [  ]
> > 0 [  ]
> > -1 [  ]
> >
> >
> >
> > Thanks,
> >
> > - Henry
> > On behalf of Apache Twill PPMC
> >
> >
> > PS:
> >
> > Here is my vote:
> >
> > +1 (binding)
> >
> >
> >
> >
> > ## Resolution to create a TLP from graduating Incubator podling
> >
> >
> > X. Establish the Apache Twill Project
> >
> >
> >WHEREAS, the Board of Directors deems it to be in the best
> >
> >interests of the Foundation and consistent with the
> >
> >Foundation's purpose to establish a Project Management
> >
> >Committee charged with the creation and maintenance of
> >
> >open-source software, for distribution at no charge to
> >
> >the public, related to providing a set of libraries as
> > abstraction to develop
> >
> >distributed applications, with a programming model that is similar
> > to
> >
> >running threads, inside compute cluster such as Apache Hadoop YARN
> >
> >NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> >
> >Committee (PMC), to be known as the "Apache Twill Project",
> >
> >be and hereby is established pursuant to Bylaws of the
> >
> >Foundation; and be it further
> >
> >
> >RESOLVED, that the Apache Twill Project be and hereby is
> >
> >responsible for the creation and maintenance of software
> >
> >related to providing a set of libraries as abstraction to develop
> >
> >distributed applications, with a programming model that is similar
> > to
> >
> >running threads, inside compute cluster such as Apache Hadoop YARN
> >
> >and be it further
> >
> >
> >RESOLVED, that the office of "Vice President, Apache Twill" be
> >
> >and hereby is created, the person holding such office to
> >
> >serve at the direction of the Board of Directors as the chair
> >
> >of the Apache Twill Project, and to have primary responsibility
> >
> >for management of the projects within the scope of
> >
> >responsibility of the Apache Twill Project; and be it further
> >
> >
> >RESOLVED, that the persons listed immediately below be and
> >
> >hereby are appointed to serve as the initial members of the
> >
> >Apache Twill Project:
> >
> >
> >  * Terence Yim >
> >
> >  * Andreas Neumann >
> >
> >  * Gary Helmling >
> >
> >  * Albert Shau >
> >
> >  * Poorna Chandra >
> >
> >  * Henry Saputra >
> >
> >
> >NOW, THEREFORE, BE IT FURTHER RESOLVED, that Terence Yim
> >
> >be appointed to the office of Vice President, Apache Twill, to
> >
> >serve in accordance with and subject to the direction of the
> >
> >Board of Directors and the Bylaws of the Foundation until
> >
> >death, resignation, retirement, removal or disqualification,
> >
> >or until a successor is appointed; and be it further
> >
> >
> >RESOLVED, that the initial Apache Twill PMC be and hereby is
> >
> >tasked with the creation of a set of bylaws intended to
> >
> >encourage open development and increased participation in the
> >
> >Apache Twill Project; and be it further
> >
> >
> >RESOLVED, that the Apache Twill Project be and hereby
> >
> >is tasked with the migration and rationalization of the Apache
> >
> >Incubator Twill podling; and be it further
> >
> >
> >RESOLVED, that all responsibilities pertaining to the Apache
> >
> >Incubator Twill podling encumbered upon the Apache Incubator
> >
> >Project are hereafter discharged.
> >
>
>
>
> --
> Best regards,
>
>- Andy
>
> Problems worthy of attack prove their worth by hitting back. - Piet Hein
> (via Tom White)
>

Re: [VOTE] Accept Pony Mail into the Apache Incubator

[James Taylor]

+1 (binding)

On Tue, May 24, 2016 at 7:48 AM, Billie Rinaldi  wrote:

> +1 (binding)
>
> On Tue, May 24, 2016 at 7:56 AM, Daniel Gruno 
> wrote:
> > Since it seems the discussion has died down, I am now calling a vote on
> > accepting Pony Mail into the Incubator. Sorry in advance for potato.
> >
> > This vote will run for the usual 72 hours.
> >
> > ### PROPOSAL BELOW ###
> >
> > Abstract
> >
> > Pony Mail is a mail-archiving, archive viewing, and interaction service,
> > that can be integrated with many email platforms.
> >
> > Proposal
> >
> > Background
> >
> > Pony Mail began as a response to two things; the lack of diversity in
> > mailing list archives that are less bureaucratic all-or-nothing and more
> > fluid way to interact with mailing lists than what is typically offered,
> > and the lack of a performant system that solves this issue. Modern users
> > of software want to jump right into a discussion they see, but cannot
> > normally do so in a mailing list driven environment because of the rules
> > generally surrounding said environment. Pony Mail, along with a select
> > handful of newer archive systems, provides an interface that allows
> > people to just hop into a thread, and take part. Without the need to
> > subscribe, download the mbox archive, load it into your MTA, and respond.
> >
> > As Rich writes in a very short essay:
> >
> > You see a thread in which someone is WRONG ON THE INTERNET! You need to
> > correct them. How do you do this today? You kinda don't. If you really
> > wanted, you could download mbox files (and who the hell knows where they
> > are?) and then try to get them into your mail client (which never works)
> > and then reply to it. Which will break threading, because you did
> > something wrong. Then you tear out your hair. PONY MAIL TO THE RESCUE!!!
> > (sound of hoof beats)
> >
> > Rationale
> >
> > One of the oft-heard complaints about Apache's development model is that
> > mailing lists are an old person's tool, and web-based communication -
> > forums - are the way to go in the 21st Century. Providing a
> > full-featured forum-like interface to mailing lists is one goal,while
> > keeping all of the enormous benefits that mailing lists already provide.
> > Asecond goal is to provide the ability to "jump in" to a mailing list
> > conversation - even one that was a while back, without the convolutions
> > that a mailing list requires. That is, to join this conversation the old
> > way, one would have had to subscribe to the mailing list, download an
> > mbox, and import it into ones mail client, in order that I be able to
> > reply to this message with correct threading. With Pony Mail, one has to
> > do none of those things, but can simply reply using the Web UI. To us,
> > this is a HUGE benefit for building community. The requirement to jump
> > through hoops to join a mailing list conversation drives away a lot of
> > people (at least, anecdotally, it does) and if we can remove that
> > barrier I think we'll have an easier time of drawing a new generation
> > into our projects.
> >
> > Initial Goals
> >
> > The initial goals of transitioning to the ASF is to expand and grow both
> > the Pony codebase and community, and ensure the project's continued
> > growth and stability through forming a diverse and reliable community,
> > in which the various facets of developers and contributors help keep the
> > project up to date with latest developments and technical as well as
> > social needs.
> >
> > Current Status
> >
> > Meritocracy:
> >
> > The bulk of the code has been written by Daniel Gruno to date, but has
> > had oversight from other committers, and mentors.
> >
> > All members of the Pony project and wider community have a deep
> > understanding and appreciation for the ASF meritocracy ideals, and are
> > almost solely current ASF Members.
> >
> > Community:
> > The community is currently heavily focused within the ASF, and
> > more specifically the Infrastructure group. This is to be expected given
> > the nature of how the code came into existence in the first place. It
> > should be noted that we have started reaching out to other groups who we
> > know are using mailing list systems and therefore also rely on mailing
> > list archive interfaces.
> >
> > Core Developers:
> >
> > Almost all core developers are ASF members, and are already intimately
> > familiar with the Apache Way.
> >
> > Alignment:
> >
> > Pony will be very in line with ASF practices and processes as many of
> > the founding members are long term ASF members and committers.
> >
> > Known Risks
> >
> > Orphaned products:
> >
> > We are not aware of any issues with orphaned products related to this
> > project.
> >
> > Pony Mail relies on a set of CSS3 templates as well as some very
> stable
> > programming languages. We have no reason to believe these would
> > be 

Re: [VOTE] Accept PredictionIO into the Apache Incubator

[James Taylor]

ncubator, we would begin a thorough analysis of
> > all transitive dependencies to verify this information and introduce
> > license checking into the build and release process by integrating with
> > Apache RAT.
> >
> > Cryptography
> >
> > PredictionIO does not include cryptographic code. We utilize standard
> > JCE and JSSE APIs provided by the Java Runtime Environment.
> >
> > Required Resources
> >
> > We request that following resources be created for the project to use
> >
> > Mailing lists
> >
> >   predictionio-priv...@incubator.apache.org (with moderated
> subscriptions)
> >   predictionio-dev
> >   predictionio-user
> >   predictionio-commits
> >
> >   We will migrate the existing PredictionIO mailing lists.
> >
> > Git repository
> >
> >   The PredictionIO team would like to use Git for source control, due to
> > our
> >   current use of GitHub.
> >
> >   git://git.apache.org/incubator-predictionio
> >
> > Documentation
> >
> >   https://predictionio.incubator.apache.org/docs/
> >
> > JIRA instance
> >
> >   PredictionIO currently uses the GitHub issue tracking system associated
> >   with its repository:
> https://github.com/PredictionIO/PredictionIO/issues
> > .
> >   We will migrate to Apache JIRA.
> >
> >   JIRA PREDICTIONIO
> >   https://issues.apache.org/jira/browse/PREDICTIONIO
> >
> > Other Resources
> >
> >   TravisCI for builds and test running.
> >
> >   PredictionIO's documentation, included in the code repo (docs/manual
> >   directory), is built with Middleman and publicly hosted at
> >   https://docs.prediction.io
> >
> >   A blog to drive adoption and excitement at https://blog.prediction.io
> >
> > Initial Committers
> >
> >   Pat Ferrell
> >   Tamas Jambor
> >   Justin Yip
> >   Xusen Yin
> >   Lee Moon Soo
> >   Donald Szeto
> >   Kenneth Chan
> >   Tom Chan
> >   Simon Chan
> >   Marco Vivero
> >   Matthew Tovbin
> >   Yevgeny Khodorkovsky
> >   Felipe Oliveira
> >   Vitaly Gordon
> >   Alex Merritt
> >
> > Affiliations
> >
> >   Pat Ferrell - ActionML
> >   Tamas Jambor - Channel4
> >   Justin Yip - independent
> >   Xusen Yin - USC
> >   Lee Moon Soo - NFLabs
> >   Donald Szeto - Salesforce
> >   Kenneth Chan - Salesforce
> >   Tom Chan - Salesforce
> >   Simon Chan - Salesforce
> >   Marco Vivero - Salesforce
> >   Matthew Tovbin - Salesforce
> >   Yevgeny Khodorkovsky - Salesforce
> >   Felipe Oliveira - Salesforce
> >   Vitaly Gordon - Salesforce
> >   Alex Merritt - ActionML
> >
> > Sponsors
> >
> > Champion
> >
> >   Andrew Purtell 
> >
> > Nominated Mentors
> >
> >   Andrew Purtell 
> >   James Taylor 
> >   Lars Hofhansl 
> >   Suneel Marthi 
> >   Xiangrui Meng 
> >   Luciano Resende 
> >
> > Sponsoring Entity
> >
> >   Apache Incubator PMC
> >
> >
> > --
> > Best regards,
> >
> >- Andy
> >
> > Problems worthy of attack prove their worth by hitting back. - Piet Hein
> > (via Tom White)
> >
>
>
>
> --
> Luciano Resende
> http://twitter.com/lresende1975
> http://lresende.blogspot.com/
>

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

[James Taylor]

Lars - Would you consider changing your vote given the additional
information from Justin and myself? There is no third party code bundled in
the source release.

Thanks,
James

On Fri, May 20, 2016 at 10:45 PM, <la...@apache.org> wrote:

> Hmm...
> The source code still shows "Copyright © 2015 Cask Data, Inc." notices.The
> code is still organized in co.cask.tephra... packages. That should be
> org.apache.tephra..., right?
> There is no NOTICE file, and the LICENSE file only contains the Apache 2.0
> license. Is there any 3rd party code included under other (open source)
> licenses that we would need to include?
> I realize this may sound like nit-picking. But it is an important aspect
> of the incubation time.
>
> I have to vote  -1 .
>
> -- Lars
>
>   From: James Taylor <jamestay...@apache.org>
>  To: "general@incubator.apache.org" <general@incubator.apache.org>
>  Sent: Friday, May 20, 2016 3:48 PM
>  Subject: Re: [VOTE] Release of Apache Tephra-0.8.0-incubating [rc1]
>
> +1. Transferring my vote over from the previous vote thread.
>
> On Fri, May 20, 2016 at 3:47 PM, Poorna Chandra <poo...@apache.org> wrote:
>
> > Hi all,
> >
> > This is a call for a vote on releasing Apache Tephra 0.8.0-incubating,
> > release candidate 1. This
> > is the first release of Tephra.
> >
> > Apache Tephra community has voted and approved the release.
> >
> > Vote thread:
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201605.mbox/%3CCAC9o21R1x-m1%2BbaV3oK39RmPbf2pToBQrSGkfzBmWz%3Dp8Ez5JQ%40mail.gmail.com%3E
> >
> > Result thread:
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201605.mbox/%3CCAC9o21TR5Ur4nu%2BxOoXB74vHSvRujtj1C6%2BsA2N75YQf4DXd8w%40mail.gmail.com%3E
> >
> > The source tarball, including signatures, digests, etc. can be found at:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.8.0-incubating-rc1/src
> >
> > The tag to be voted upon is v0.8.0-incubating:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=shortlog;h=refs/tags/v0.8.0-incubating
> >
> > The release hash is 0db528e3603393221472b89fa9bb30312cfd5470:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=0db528e3603393221472b89fa9bb30312cfd5470
> >
> > The Nexus Staging URL:
> > https://repository.apache.org/content/repositories/orgapachetephra-1001
> >
> > Release artifacts are signed with the following key:
> > http://pgp.mit.edu/pks/lookup?op=get=0x8EC4A2C60990A464
> >
> > KEYS file available:
> > https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
> >
> > For information about the contents of this release, see:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.8.0-incubating-rc1/CHANGES.txt
> >
> > Please vote on releasing this package as Apache Tephra 0.8.0-incubating
> >
> > The vote will be open for 72 hours.
> >
> > [ ] +1 Release this package as Apache Tephra 0.8.0-incubating
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because ...
> >
> > Thanks,
> > Poorna.
> >
>
>
>
>

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

[James Taylor]

@John - try appending your host name in /etc/host on the localhost line. I
forgot about that work around (there may be other alternatives) on the Mac.

On Saturday, May 21, 2016, Andrew Purtell <andrew.purt...@gmail.com> wrote:

> This test failure looks like it could be a failure to set up the
> minicluster. If so, that can be a networking problem on Macs unless using a
> very recent version of the JDK, or any number of reasons really
> (minicluster is as complex as it sounds). Anyway, perhaps posting the
> complete test output from surefire to the project JIRA is in order?
>
>
> > On May 21, 2016, at 8:08 AM, James Taylor <jamestay...@apache.org
> <javascript:;>> wrote:
> >
> > Thanks for the testing, John. It builds on my MacBook Pro:
> >
> >OS X Version 10.11.4
> >java version 1.7.0_80
> >
> > What's your system look like?
> >
> > On Sat, May 21, 2016 at 6:53 AM, John D. Ament <john.d.am...@gmail.com
> <javascript:;>>
> > wrote:
> >
> >> Hi,
> >>
> >> I'm +0 for right now unless there's a way to make the code build and
> test
> >> on a mac and I'm not sure what it is.  Ran mvn clean install from the
> root
> >> and this is the eventual output:
> >>
> >> Tests in error:
> >>
> >>  TransactionAwareHTableTest.setupBeforeClass:164 » IO Shutting down
> >>
> >>  TransactionAwareHTableTest.shutdownAfterClass:174 NullPointer
> >>
> >>
> >> Tests run: 15, Failures: 0, Errors: 2, Skipped: 0
> >>
> >>
> >>> On Fri, May 20, 2016 at 6:47 PM Poorna Chandra <poo...@apache.org
> <javascript:;>> wrote:
> >>>
> >>> Hi all,
> >>>
> >>> This is a call for a vote on releasing Apache Tephra 0.8.0-incubating,
> >>> release candidate 1. This
> >>> is the first release of Tephra.
> >>>
> >>> Apache Tephra community has voted and approved the release.
> >>>
> >>> Vote thread:
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201605.mbox/%3CCAC9o21R1x-m1%2BbaV3oK39RmPbf2pToBQrSGkfzBmWz%3Dp8Ez5JQ%40mail.gmail.com%3E
> >>>
> >>> Result thread:
> >>
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201605.mbox/%3CCAC9o21TR5Ur4nu%2BxOoXB74vHSvRujtj1C6%2BsA2N75YQf4DXd8w%40mail.gmail.com%3E
> >>>
> >>> The source tarball, including signatures, digests, etc. can be found
> at:
> >>
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.8.0-incubating-rc1/src
> >>>
> >>> The tag to be voted upon is v0.8.0-incubating:
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=shortlog;h=refs/tags/v0.8.0-incubating
> >>>
> >>> The release hash is 0db528e3603393221472b89fa9bb30312cfd5470:
> >>
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=0db528e3603393221472b89fa9bb30312cfd5470
> >>>
> >>> The Nexus Staging URL:
> >>>
> https://repository.apache.org/content/repositories/orgapachetephra-1001
> >>>
> >>> Release artifacts are signed with the following key:
> >>> http://pgp.mit.edu/pks/lookup?op=get=0x8EC4A2C60990A464
> >>>
> >>> KEYS file available:
> >>> https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
> >>>
> >>> For information about the contents of this release, see:
> >>
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.8.0-incubating-rc1/CHANGES.txt
> >>>
> >>> Please vote on releasing this package as Apache Tephra 0.8.0-incubating
> >>>
> >>> The vote will be open for 72 hours.
> >>>
> >>> [ ] +1 Release this package as Apache Tephra 0.8.0-incubating
> >>> [ ] +0 no opinion
> >>> [ ] -1 Do not release this package because ...
> >>>
> >>> Thanks,
> >>> Poorna.
> >>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> <javascript:;>
> For additional commands, e-mail: general-h...@incubator.apache.org
> <javascript:;>
>
>

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

[James Taylor]

Thanks for the testing, John. It builds on my MacBook Pro:

OS X Version 10.11.4
java version 1.7.0_80

What's your system look like?

On Sat, May 21, 2016 at 6:53 AM, John D. Ament 
wrote:

> Hi,
>
> I'm +0 for right now unless there's a way to make the code build and test
> on a mac and I'm not sure what it is.  Ran mvn clean install from the root
> and this is the eventual output:
>
> Tests in error:
>
>   TransactionAwareHTableTest.setupBeforeClass:164 » IO Shutting down
>
>   TransactionAwareHTableTest.shutdownAfterClass:174 NullPointer
>
>
> Tests run: 15, Failures: 0, Errors: 2, Skipped: 0
>
>
> On Fri, May 20, 2016 at 6:47 PM Poorna Chandra  wrote:
>
> > Hi all,
> >
> > This is a call for a vote on releasing Apache Tephra 0.8.0-incubating,
> > release candidate 1. This
> > is the first release of Tephra.
> >
> > Apache Tephra community has voted and approved the release.
> >
> > Vote thread:
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201605.mbox/%3CCAC9o21R1x-m1%2BbaV3oK39RmPbf2pToBQrSGkfzBmWz%3Dp8Ez5JQ%40mail.gmail.com%3E
> >
> > Result thread:
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201605.mbox/%3CCAC9o21TR5Ur4nu%2BxOoXB74vHSvRujtj1C6%2BsA2N75YQf4DXd8w%40mail.gmail.com%3E
> >
> > The source tarball, including signatures, digests, etc. can be found at:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.8.0-incubating-rc1/src
> >
> > The tag to be voted upon is v0.8.0-incubating:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=shortlog;h=refs/tags/v0.8.0-incubating
> >
> > The release hash is 0db528e3603393221472b89fa9bb30312cfd5470:
> >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=0db528e3603393221472b89fa9bb30312cfd5470
> >
> > The Nexus Staging URL:
> > https://repository.apache.org/content/repositories/orgapachetephra-1001
> >
> > Release artifacts are signed with the following key:
> > http://pgp.mit.edu/pks/lookup?op=get=0x8EC4A2C60990A464
> >
> > KEYS file available:
> > https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
> >
> > For information about the contents of this release, see:
> >
> >
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.8.0-incubating-rc1/CHANGES.txt
> >
> > Please vote on releasing this package as Apache Tephra 0.8.0-incubating
> >
> > The vote will be open for 72 hours.
> >
> > [ ] +1 Release this package as Apache Tephra 0.8.0-incubating
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because ...
> >
> > Thanks,
> > Poorna.
> >
>

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

[James Taylor]

Thanks for the reviews. There are a few files with a package
of co.cask.tephra in order to maintain backward compatibility with pre
Apache-based releases. These will be removed in a follow on release.

James

On Fri, May 20, 2016 at 10:55 PM, Justin Mclean 
wrote:

> Hi,
>
> > The source code still shows "Copyright © 2015 Cask Data, Inc." notices.
>
> Are you sure you are looking at the source release bundle? I can’t see
> copyright Cask Data anywhere.
>
> > The code is still organized in co.cask.tephra... packages. That should
> be org.apache.tephra..., right?
>
> That a nice to have but not a must have  requirement for an incubating
> release.
>
> > There is no NOTICE file
>
> There is in the source release that I looked at. On reflection it could
> also have a line saying “Original software developed at Cask Data” if some
> of the files had that above copyright removed.
>
> >  Is there any 3rd party code included under other (open source) licenses
> that we would need to include?
>
> AFAIK there no 3rd party code bundled in this source release, no no need
> to add anything to LICENSE or NOTICE.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

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

[James Taylor]

+1. Transferring my vote over from the previous vote thread.

On Fri, May 20, 2016 at 3:47 PM, Poorna Chandra  wrote:

> Hi all,
>
> This is a call for a vote on releasing Apache Tephra 0.8.0-incubating,
> release candidate 1. This
> is the first release of Tephra.
>
> Apache Tephra community has voted and approved the release.
>
> Vote thread:
>
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201605.mbox/%3CCAC9o21R1x-m1%2BbaV3oK39RmPbf2pToBQrSGkfzBmWz%3Dp8Ez5JQ%40mail.gmail.com%3E
>
> Result thread:
>
> http://mail-archives.apache.org/mod_mbox/incubator-tephra-dev/201605.mbox/%3CCAC9o21TR5Ur4nu%2BxOoXB74vHSvRujtj1C6%2BsA2N75YQf4DXd8w%40mail.gmail.com%3E
>
> The source tarball, including signatures, digests, etc. can be found at:
>
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.8.0-incubating-rc1/src
>
> The tag to be voted upon is v0.8.0-incubating:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=shortlog;h=refs/tags/v0.8.0-incubating
>
> The release hash is 0db528e3603393221472b89fa9bb30312cfd5470:
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-tephra.git;a=commit;h=0db528e3603393221472b89fa9bb30312cfd5470
>
> The Nexus Staging URL:
> https://repository.apache.org/content/repositories/orgapachetephra-1001
>
> Release artifacts are signed with the following key:
> http://pgp.mit.edu/pks/lookup?op=get=0x8EC4A2C60990A464
>
> KEYS file available:
> https://dist.apache.org/repos/dist/dev/incubator/tephra/KEYS
>
> For information about the contents of this release, see:
>
> https://dist.apache.org/repos/dist/dev/incubator/tephra/0.8.0-incubating-rc1/CHANGES.txt
>
> Please vote on releasing this package as Apache Tephra 0.8.0-incubating
>
> The vote will be open for 72 hours.
>
> [ ] +1 Release this package as Apache Tephra 0.8.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
>
> Thanks,
> Poorna.
>

Re: [VOTE] Accept Fluo into the Apache Incubator

[James Taylor]

+1 (binding)

On Sat, May 14, 2016 at 9:31 AM, Roman Shaposhnik 
wrote:

> On Fri, May 13, 2016 at 11:22 AM, Billie Rinaldi 
> wrote:
> > Since discussion has died down, I would like to call a VOTE on accepting
> > Fluo into the Apache Incubator.
> >
> > Proposal: http://wiki.apache.org/incubator/FluoProposal
> >
> > [ ] +1 Accept Fluo into the Apache Incubator
> > [ ] +0 Abstain.
> > [ ] -1 Do not accept Fluo into the Apache Incubator because…
>
> +1 (binding)
>
> Thanks,
> Roman.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Final draft of the Incubator Board Report - April 2016

[James Taylor]

Me too - my bad. So sorry. I'm embarrassed to admit I can't find an email
for it.

On Tuesday, April 12, 2016, Henry Saputra  wrote:

> No need to be curious too much, mea culpa from me for missing signing off
> the report :)
>
> I had the impression I did sign off the report for Mnemonic, sincerely
> apologize.
>
> - Henry
>
> On Tue, Apr 12, 2016 at 4:38 PM, Wang, Yanping  >
> wrote:
>
> > Hi, John
> >
> > I think our mentors are busy during the day.
> > Patrick was on vacation last week. I'd suggest give them a few more hours
> > to signoff the report.
> >
> > Thanks,
> > Yanping
> >
> > -Original Message-
> > From: John D. Ament [mailto:johndam...@apache.org ]
> > Sent: Tuesday, April 12, 2016 4:32 PM
> > To: general@incubator.apache.org 
> > Subject: Re: Final draft of the Incubator Board Report - April 2016
> >
> > I'm a bit curious about how we should handle Mnemonic.  I've received no
> > response thus far from the podling.  I'd rather not kick them out of the
> > monthly report.
> >
> > John
> >
> > On Mon, Apr 11, 2016 at 11:28 PM Marvin Humphrey  >
> > wrote:
> >
> > > On Mon, Apr 11, 2016 at 3:56 AM, John D. Ament  >
> > > wrote:
> > >
> > > > Below is the final draft of the board report.
> > >
> > > The report looks good to me!  Comments inline.
> > >
> > > >   - Airflow
> > > >   - Gearpump
> > > >   - Mnemonic
> > > >   - Omid
> > > >   - Tephra
> > > >
> > > > * Graduations
> > > >
> > > >   The board has motions for the following:
> > > >
> > > >   - Apex
> > > >   - Johnzon
> > > >   - TinkerPop
> > > >   - AsterixDB
> > >
> > > What turnover!  I see that with the addition of Quickstep that's *six*
> > new
> > > podlings in one month, which has to be a record.
> > >
> > > Congrats to all the entrants and graduates!
> > >
> > > > * Credits
> > > >
> > > >   - Report Manager:
> > >
> > > I added the credit for this month's erstwhile Report Manager. :)
> > >
> > > > * Did not report, expected next month
> > > >
> > > >   - Concerted
> > > >   - OpenAz
> > > >   - Tephra
> > >
> > > The OpenAZ report was due in January and is thus 4 months late, which I
> > > have
> > > now noted on the wiki.  OpenAZ's status has been raised on
> > > private@incubator
> > > and we just have to keep raising it each month until a report gets
> filed.
> > >
> > > > 
> > > > Fineract
> > > >
> > > > Fineract is an open source system for core banking as a platform.
> > > >
> > > > Fineract has been incubating since 2015-12-15.
> > > >
> > > > Three most important issues to address in the move towards
> graduation:
> > > >
> > > >   1. Finalising the initial release
> > > >   2. Improve the communication around the differences between the
> > > previous
> > > >  MifosX project and the new Fineract project, especially in the
> > > MifosX
> > > >  community, website etc.
> > > >   3. With the first initial release, encourage the community to use
> the
> > > >  proper infastructure (mailing lists, issue tracker) for the
> > ongoing
> > > >  collaboration within the community.
> > > >   4. Change management towards less 'key-man' dependency on previous
> > > >  tech/community leaders from MifosX, more towards community
> driven
> > > >  consensus.
> > > >   5. Reduce clutter on mailinglist from JIRA updates etc.
> > > >
> > > > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > > > aware of?
> > > >
> > > >   On the mailinglist there have been discussions around the lack of
> > > traffic
> > > >   on it. This is part of the switchover from the current MifosX
> > community
> > > >   and mailinglists towards the new Fineract lists. At the same time
> the
> > > >   recent meet-up of Mifosx and Fineract devs and people interested in
> > it
> > > >   (see community development), has also triggered a lot of offline
> > > >   interaction.
> > > >
> > > > How has the community developed since the last report?
> > > >
> > > >   While activity on the mailinglist has been pretty low, we've had a
> > > great
> > > >   meet-up in Amsterdam where a nice mix of existing MifosX community
> > > members
> > > >   and a group of new interested people was present. This has boosted
> > > >   interest in Fineract.
> > > >
> > > >   We have a high level of interest from new contributors throughout
> > > Africa -
> > > >   we are working to properly engage them and guide them to the
> correct
> > > >   collaboration channels in our Fineract community.
> > > >
> > > > How has the project developed since the last report?
> > > >
> > > >   Individual members of the leading partner organizations building
> > > solutions
> > > >   using the Fineract platform have begun to effectively use the
> > Fineract
> > > >   issue tracker to communicate and track the requirements and
> > > enhancements
> > > >   

Re: [VOTE] Accept Omid into the Apache Incubator

[James Taylor]

xecution of main
> >components.
> >
> >The code will be moved to Apache http://git.apache.org/ if accepted as
> >an Incubator project.
> >
> >=== Source and Intellectual Property Submission Plan ===
> >The current Omid License for the code published in Github is Apache
> >2.0. If Omid fulfills and passes the conditions for being an Incubator
> >project in the ASF, the source code will be transitioned via the
> >Software Grant Agreement onto the ASF infrastructure and in turn made
> >available under the Apache License, version 2.0.
> >
> >=== External Dependencies ===
> >
> >The required external dependencies that are not Apache projects are
> >all Apache licenses or other compatible Licenses:
> >
> >
> >Maven & Maven plugins (http://maven.apache.org/) [Apache 2.0]
> >JDK7 or OpenJDK 7 (http://java.com/) [Oracle or Openjdk JDK License]
> >Google Guava v11.0.2 (https://github.com/google/guava) [Apache 2.0]
> >Google Guice v3.0 (https://github.com/google/guice/wiki) [Apache 2.0]
> >Testng v6.8.8  (http://testng.org) [Apache 2.0]
> >SLF4J (http://www.slf4j.org/) v1.7.7 [MIT License]
> >Netty (http://netty.io) v3.2.6.Final [Apache 2.0]
> >Google Protocol Buffers v2.5.0
> >(https://developers.google.com/protocol-buffers/) [BSD License]
> >Mockito (http://mockito.org/) v1.9.5 [MIT License]
> >LMAX Disruptor v3.2.0 (https://lmax-exchange.github.io/disruptor/)
> >[Apache 2.0]
> >Coda Hale/Yammer.com Dropwizard Metrics v3.0.1
> >(http://metrics.dropwizard.io/3.1.0/) [Apache 2.0]
> >C.Beust, JCommander v1.35 (http://jcommander.org/) [Apache 2.0]
> >Hamcrest v1.3 (http://hamcrest.org/JavaHamcrest/) [BSD License]
> >
> >=== Cryptography ===
> >Omid project does not use cryptography itself. However, Apache HBase
> >-the datastore on top of which Omid works in its current version- uses
> >standard APIs and tools for SSH and SSL communication where necessary.
> >
> >=== Required Resources ===
> >We request that following resources be created for the project to use:
> >
> > Mailing lists 
> >omid-private (moderated subscriptions)
> >omid-commits (commit notification)
> >omid-dev (technical discussions)
> >
> > Git repository 
> >https://github.com/apache/incubator-omid
> >
> > Documentation 
> >https://omid.incubator.apache.org/docs/
> >
> > JIRA instance 
> >https://issues.apache.org/jira/browse/omid
> >
> >=== Initial Committers ===
> >* Daniel Dai, Hortonworks (daijyhortonworkscom)
> >
> >* Alan Gates, Hortonworks, (gateshortonworkscom)
> >
> >* Lars Hofhansl, Salesforce (larshapacheorg)
> >
> >* Flavio P. Junqueira, Confluent (fpjapacheorg)
> >
> >* Igor Katkov (katkoviyahoo-inccom)
> >
> >* Francis C. Liu (fcliuyahoo-inccom)
> >
> >
> >* Thejas Nair, Hortonworks (thejashortonworkscom)
> >
> >* Francisco Perez-Sorrosal (fperezyahoo-inccom)
> >
> >* Sameer Paranjpye (sparanjpyeyahoocom)
> >
> >* Ohad Shacham (ohadsyahoo-inccom)
> >
> >
> >* James Taylor, Salesforce (jamestaylorapacheorg>)
> >
> >=== Additional Interested Contributors ===
> >* Ivan Kelly (ivankapacheorg)
> >* Maysam Yabandeh (myabandehdropboxcom)
> >
> >=== Affiliations ===
> >* Edward Bortnikov, Yahoo Inc.
> >
> >* Daniel Dai, Hortonworks
> >
> >* Flavio P. Junqueira, Confluent
> >
> >* Igor Katkov, Yahoo Inc.
> >
> >* Ivan Kelly, Midokura
> >
> >* Francis C. Liu, Yahoo Inc.
> >
> >* Sameer Paranjpye, Arimo
> >
> >* Francisco Perez-Sorrosal, Yahoo Inc.
> >
> >* Ohad Shacham, Yahoo Inc.
> >
> >* Maysam Yabandeh, Dropbox Inc.
> >
> >=== Sponsors ===
> >
> >
> > Champion 
> >Daniel Dai, Hortonworks (daijyhortonworkscom)
> >
> > Nominated Mentors 
> >Alan Gates, Hortonworks, (gateshortonworkscom)
> >Lars Hofhansl, Salesforce (larshapacheorg)
> >Flavio P. Junqueira, Confluent (fpjapacheorg)
> >Thejas Nair, Hortonworks (thejashortonworkscom)
> >James Taylor, Salesforce (jamestaylorapacheorg>)
> >
> > Sponsoring Entity 
> >Apache Incubator PMC
> >
> >-
> >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: [DISCUSS] [PROPOSAL] Omid for Apache Incubator

[James Taylor]

we believe that there’s room for both proposals
> > > > as the design of each of them is based on different principles (e.g.
> > > > Omid does not require to maintain the state of ongoing transactions
> on
> > > > the server-side component) and due to the fact that both -Tephra and
> > > > Omid- have also gained certain traction in the open-source community.
> > > >
> > > >
> > > > With regard to the Apache projects that Omid uses, apart from HBase,
> > > > Omid relies on Apache Zookeeper and Curator projects in order to
> > > > coordinate the (re)connection of transaction managers (acting as
> > > > clients) to the conflict resolution component for transactions
> (server
> > > > side.) They’re also used in order to coordinate the master and backup
> > > > replicas in high availability scenarios.
> > > >
> > > >
> > > >  An Excessive Fascination with the Apache Brand 
> > > >
> > > > We are applying to the Incubator process because we think that it is
> > > > the logical next step for the  Omid project after we open-sourced the
> > > > code in Github some years ago. Yahoo has a long-standing history of
> > > > contributing to Apache projects. The developers and contributors
> > > > understand the implications of making it an Apache project, and
> > > > strongly believe that the growing community can benefit from the
> > > > Apache environment, ecosystem, and infrastrastructure.
> > > >
> > > >
> > > > === Documentation ===
> > > > Current documentation about the project is available in the wiki of
> > > > Omid’s Github repository: https://github.com/yahoo/omid/wiki . It
> will
> > > > be moved under https://omid.incubator.apache.org/docs if the project
> > > > is accepted as an Apache Incubator.
> > > >
> > > > === Initial Source ===
> > > > Initial source code is currently hosted in Github for general viewing
> > > > and contribution:
> > > >
> > > > https://github.com/yahoo/omid.git
> > > >
> > > >
> > > > Omid source code is written in Java code (99%) mixed with some shell
> > > > script (1%) in order to configure and trigger the execution of main
> > > > components.
> > > >
> > > >
> > > > The code will be moved to Apache http://git.apache.org/ if accepted
> as
> > > > an Incubator project.
> > > >
> > > > === Source and Intellectual Property Submission Plan ===
> > > >
> > > > The current Omid License for the code published in Github is Apache
> > > > 2.0. If Omid fulfills and passes the conditions for being an
> Incubator
> > > > project in the ASF, the source code will be transitioned via the
> > > > Software Grant Agreement onto the ASF infrastructure and in turn made
> > > > available under the Apache License, version 2.0.
> > > >
> > > > === External Dependencies ===
> > > >
> > > >
> > > > The required external dependencies that are not Apache projects are
> > > > all Apache licenses or other compatible Licenses:
> > > >
> > > > Maven & Maven plugins (http://maven.apache.org/) [Apache 2.0]
> > > >
> > > > JDK7 or OpenJDK 7 (http://java.com/) [Oracle or Openjdk JDK License]
> > > >
> > > > Google Guava v11.0.2 (https://github.com/google/guava) [Apache 2.0]
> > > >
> > > > Google Guice v3.0 (https://github.com/google/guice/wiki) [Apache
> 2.0]
> > > >
> > > > Testng v6.8.8  (http://testng.org) [Apache 2.0]
> > > >
> > > > SLF4J (http://www.slf4j.org/) v1.7.7 [MIT License]
> > > >
> > > > Netty (http://netty.io) v3.2.6.Final [Apache 2.0]
> > > >
> > > > Google Protocol Buffers v2.5.0
> > > > (https://developers.google.com/protocol-buffers/) [BSD License]
> > > >
> > > > Mockito (http://mockito.org/) v1.9.5 [MIT License]
> > > >
> > > > LMAX Disruptor v3.2.0 (https://lmax-exchange.github.io/disruptor/)
> > > > [Apache 2.0]
> > > >
> > > > Coda Hale/Yammer.com Dropwizard Metrics v3.0.1
> > > > (http://metrics.dropwizard.io/3.1.0/) [Apache 2.0]
> > > >
> > > > C.Beust, JCommander v1.35 (http://jcommander.org/) [Apache 2.0]
> > > >
> > > > Hamcrest v1.3 (http://hamcrest.org/JavaHamcrest/) [BSD License]
> > > >
> > > >
> > > > === Cryptography ===
> > > > Omid project does not use cryptography itself. However, Apache HBase
> > > > -the datastore on top of which Omid works in its current version-
> uses
> > > > standard APIs and tools for SSH and SSL communication where
> necessary.
> > > >
> > > > === Required Resources ===
> > > > We request that following resources be created for the project to
> use:
> > > >
> > > >  Mailing lists 
> > > >
> > > > omid-private (moderated subscriptions)
> > > >
> > > > omid-commits (commit notification)
> > > > omid-dev (technical discussions)
> > > >
> > > >  Git repository 
> > > > https://github.com/apache/incubator-omid
> > > >
> > > >  Documentation 
> > > > https://omid.incubator.apache.org/docs/
> > > >
> > > >  JIRA instance 
> > > > https://issues.apache.org/jira/browse/omid
> > > >
> > > > === Initial Committers ===
> > > >
> > > > * Daniel Dai, Hortonworks (daijyhortonworkscom)
> > > >
> > > >
> > > > * Alan Gates, Hortonworks, (gateshortonworkscom)
> > > >
> > > >
> > > > * Lars Hofhansl, Salesforce (larshapacheorg)
> > > >
> > > >
> > > > * Flavio P. Junqueira, Confluent (fpjapacheorg)
> > > >
> > > >
> > > > * Igor Katkov (katkoviyahoo-inccom)
> > > >
> > > >
> > > > * Francis C. Liu (fcliuyahoo-inccom)
> > > >
> > > > * Thejas Nair, Hortonworks (thejashortonworkscom)
> > > >
> > > >
> > > > * Francisco Perez-Sorrosal (fperezyahoo-inccom)
> > > >
> > > >
> > > > * Sameer Paranjpye (sparanjpyeyahoocom)
> > > >
> > > >
> > > > * Ohad Shacham (ohadsyahoo-inccom)
> > > >
> > > > * James Taylor, Salesforce (jamestaylorapacheorg>)
> > > >
> > > >
> > > > === Additional Interested Contributors ===
> > > > * Ivan Kelly (ivankapacheorg)
> > > >
> > > > * Maysam Yabandeh (myabandehdropboxcom)
> > > >
> > > >
> > > > === Affiliations ===
> > > >
> > > > * Edward Bortnikov, Yahoo Inc.
> > > >
> > > >
> > > > * Daniel Dai, Hortonworks
> > > >
> > > >
> > > > * Flavio P. Junqueira, Confluent
> > > >
> > > >
> > > > * Igor Katkov, Yahoo Inc.
> > > >
> > > >
> > > > * Ivan Kelly, Midokura
> > > >
> > > >
> > > > * Francis C. Liu, Yahoo Inc.
> > > >
> > > >
> > > > * Sameer Paranjpye, Arimo
> > > >
> > > > * Francisco Perez-Sorrosal, Yahoo Inc.
> > > >
> > > >
> > > > * Ohad Shacham, Yahoo Inc.
> > > >
> > > >
> > > > * Maysam Yabandeh, Dropbox Inc.
> > > >
> > > >
> > > > === Sponsors ===
> > > >
> > > >  Champion 
> > > >
> > > > Daniel Dai, Hortonworks (daijyhortonworkscom)
> > > >
> > > >  Nominated Mentors 
> > > >
> > > > Alan Gates, Hortonworks, (gateshortonworkscom)
> > > >
> > > > Lars Hofhansl, Salesforce (larshapacheorg)
> > > >
> > > > Flavio P. Junqueira, Confluent (fpjapacheorg)
> > > >
> > > > Thejas Nair, Hortonworks (thejashortonworkscom)
> > > >
> > > > James Taylor, Salesforce (jamestaylorapacheorg>)
> > > >
> > > >
> > > >  Sponsoring Entity 
> > > > Apache Incubator PMC
> > > >
> > > > -
> > > > 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

[James Taylor]

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 proximity to them.
> >
> > = Known Risks =
> >
> > == Orphaned Products ==
> >
> > There is very little risk of Tephra being orphaned, as it is a key part
> of
> > Cask Data’s products. The core Tephra developers plan to continue to work
> > on Tephra, and Cask Data has funding in place to support their efforts
> > going forward.
> > Also with Phoenix using Tephra for transactions, Phoenix developers are
> > keen on contributing to Tephra.
> >
> >
> > == Inexperience with Open Source ==
> >
> > Several of the core developers have experience with open source
> > development. Andreas Neumann is an Apache committer for Oozie and Twill.
> > Terence Yim is an Apache committer for Helix and Twill. Poorna Chandra
> > is an Apache committer for Twill. Gary Helmling is a committer for
> > Apache Twill and a committer and PMC member for Apache HBase.
> > James Taylor is PMC chair for Apache Phoenix, PMC member of Apache
> Calcite,
> > and an IPMC member.
> >
> > == Homogeneous Developers ==
> >
> > The current core developers are all Cask Data employees. However, we
> > intend to establish a developer community that includes independent and
> > corporate contributors. We are encouraging new contributors via our
> mailing
> > lists, public presentations, and personal contacts, and we will continue
> to
> > do so.
> >
> > Apache Phoenix developers have already contributed several patches to
> > Tephra,
> > and have expressed interest in becoming long term contributors.
> >
> > == Reliance on Salaried Developers ==
> >
> > Currently, these developers are paid to work on Tephra. Once the project
> > has
> > built a community, we expect to attract committers, developers and
> > community
> > other than the current core developers. However, because Cask Data
> > products use Tephra internally, the reliance on salaried developers is
> > unlikely to change, at least in the near term.
> >
> > == Relationships with Other Apache Products ==
> >
> > Tephra is deeply integrated with Apache projects. Tephra provides
> > transactions
> > over Apache HBase, and uses Apache Twill and Apache Zookeeper for
> > coordination.
> > A number of other Apache projects are Tephra dependencies, and are
> > listed in the External Dependencies section.
> >
> > In addition, Apache Phoenix is using Tephra as the transaction engine.
> >
> > == An Excessive Fascination with the Apache Brand ==
> >
> > While we respect the reputation of the Apache brand and have no doubt
> that
> > it will attract contributors and users, our interest is primarily to give
> > Tephra a solid home as an open source project following an established
> > development model. We have also given additional reasons in the Rationale
> > and Alignment sections.
> >
> > = Documentation =
> >
> > The current documentation for Tephra is at
> > https://github.com/caskdata/tephra.
> >
> > = Initial Source =
> >
> > Tephra codebase is currently hosted at
> https://github.com/caskdata/tephra.
> >
> > = Source and Intellectual Property Submission Plan =
> >
> > Tephra codebase is currently licensed under Apache 2.0 license.
> > Cask Data owns the trademark for "Tephra". As part of the incubation
> > pro

Re: [VOTE] Accept Gearpump into the Apache Incubator

[James Taylor]

+1 (binding)

On Tue, Mar 1, 2016 at 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.
>
> === Initial Goals ===
> 1. Migrate the existing codebase to Apache.
>
> 2. Setup Jira, website and other development tools by following Apache best
> practices.
>
> 3. Start the first release per Apache guidelines as soon as possible.
>
> === Current Status ===
> Gearpump is hosted on Github. It has 1922 commits, 38284 line of code, and
> 31 major or minor releases, with release notes highlighting the changes for
> every release. It is licensed under Apache License Version 2. There is 

Re: [VOTE] Accept Mnemonic into the Apache Incubator

[James Taylor]

s, we expect the Apache Software
> > > Foundation to increase interaction with the larger community as well.
> > >
> > > === Documentation ===
> > > The documentation is currently available at Intel and will be posted
> > > under: https://mnemonic.incubator.apache.org/docs
> > >
> > > === Initial Source ===
> > > Initial source code is temporary hosted Github for general viewing:
> > > https://github.com/NonVolatileComputing/Mnemonic.git
> > > It will be moved to Apache http://git.apache.org/ after podling.
> > >
> > > The initial Source is written in Java code (88%) and mixed with JNI C
> > > code (11%) and shell script (1%) for underlying native allocation
> > > libraries.
> > >
> > > === Source and Intellectual Property Submission Plan ===
> > > As soon as Mnemonic is approved to join the Incubator, the source code
> > > will be transitioned via the Software Grant Agreement onto ASF
> > > infrastructure and in turn made available under the Apache License,
> > > version 2.0.
> > >
> > > === External Dependencies ===
> > > The required external dependencies are all Apache licenses or other
> > > compatible Licenses
> > > Note: The runtime dependent licenses of Mnemonic are all declared as
> > > Apache 2.0, the GNU licensed components are used for Mnemonic build
> > > and deployment. The Mnemonic JNI libraries are built using the GNU
> > > tools.
> > >
> > > maven and its plugins (http://maven.apache.org/ ) [Apache 2.0]
> > > JDK8 or OpenJDK 8 (http://java.com/) [Oracle or Openjdk JDK License]
> > > Nvml (http://pmem.io ) [optional] [Open Source]
> > > PMalloc (https://github.com/bigdata-memory/pmalloc ) [optional]
> [Apache
> > > 2.0]
> > >
> > > Build and test dependencies:
> > > org.testng.testng v6.8.17  (http://testng.org) [Apache 2.0]
> > > org.flowcomputing.commons.commons-resgc v0.8.7 [Apache 2.0]
> > > org.flowcomputing.commons.commons-primitives v.0.6.0 [Apache 2.0]
> > > com.squareup.javapoet v1.3.1-SNAPSHOT [Apache 2.0]
> > > JDK8 or OpenJDK 8 (http://java.com/) [Oracle or Openjdk JDK License]
> > >
> > > === Cryptography ===
> > > Project Mnemonic does not use cryptography itself, however, Hadoop
> > > projects use standard APIs and tools for SSH and SSL communication
> > > where necessary.
> > >
> > > === Required Resources ===
> > > We request that following resources be created for the project to use
> > >
> > >  Mailing lists 
> > > priv...@mnemonic.incubator.apache.org (moderated subscriptions)
> > > comm...@mnemonic.incubator.apache.org
> > > d...@mnemonic.incubator.apache.org
> > >
> > >  Git repository 
> > > https://github.com/apache/incubator-mnemonic
> > >
> > >  Documentation 
> > > https://mnemonic.incubator.apache.org/docs/
> > >
> > >  JIRA instance 
> > > https://issues.apache.org/jira/browse/mnemonic
> > >
> > > === Initial Committers ===
> > > * Gang (Gary) Wang (gang1 dot wang at intel dot com)
> > >
> > > * Yanping Wang (yanping dot wang at intel dot com)
> > >
> > > * Uma Maheswara Rao G (umamahesh at apache dot org)
> > >
> > > * Kai Zheng (drankye at apache dot org)
> > >
> > > * Rakesh Radhakrishnan Potty  (rakeshr at apache dot org)
> > >
> > > * Sean Zhong  (seanzhong at apache dot org)
> > >
> > > * Henry Saputra  (hsaputra at apache dot org)
> > >
> > > * Hao Cheng (hao dot cheng at intel dot com)
> > >
> > > === Additional Interested Contributors ===
> > > * Debo Dutta (dedutta at cisco dot com)
> > >
> > > * Liang Chen (chenliang613 at Huawei dot com)
> > >
> > > === Affiliations ===
> > > * Gang (Gary) Wang, Intel
> > >
> > > * Yanping Wang, Intel
> > >
> > > * Uma Maheswara Rao G, Intel
> > >
> > > * Kai Zheng, Intel
> > >
> > > * Rakesh Radhakrishnan Potty, Intel
> > >
> > > * Sean Zhong, Intel
> > >
> > > * Henry Saputra, Independent
> > >
> > > * Hao Cheng, Intel
> > >
> > > === Sponsors ===
> > >  Champion 
> > > Patrick Hunt
> > >
> > >  Nominated Mentors 
> > > * Patrick Hunt  - Apache IPMC member
> > >
> > > * Andrew Purtell  - Apache IPMC member
> > >
> > > * James Taylor  - Apache IPMC member
> > >
> > > * Henry Saputra  - Apache IPMC member
> > >
> > >  Sponsoring Entity 
> > > Apache Incubator PMC
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

Re: [VOTE] Accept Quarks into the Apache Incubator

[James Taylor]

+1

On Fri, Feb 26, 2016 at 8:47 AM, Arvind Prabhakar  wrote:

> +1 (binding)
>
> Regards,
> Arvind
>
> On Wed, Feb 24, 2016 at 9:01 AM, Katherine Marsden 
> wrote:
>
> > The Quarks proposal has been discussed on the incubator list.  The
> > discussion thread is at:
> >
> >
> http://mail-archives.apache.org/mod_mbox/incubator-general/201602.mbox/%3c56c27489.7090...@apache.org%3E
> >
> > Feedback from the discussion including addition of mentor Justin Mclean
> > has been incorporated into the proposal below and available on the wiki
> at:
> > https://wiki.apache.org/incubator/QuarksProposal
> >
> > Please cast your vote to:
> > [] +1 - accept Quarks as a new incubating project
> > []  0 - not sure
> > [] -1 - do not accept the Quarks project (because: ...)
> >
> > Thanks,
> >
> > Kathey Marsden
> >
> > = Quarks Proposal =
> > === Abstract ===
> > Quarks is a stream processing programming model and lightweight runtime
> to
> > execute analytics at devices on the edge or at the gateway.
> >
> > === Proposal ===
> >  . Quarks  is a programming model and runtime for streaming analytics at
> > the edge.   Applications are developed using a functional flow api to
> > define operations on data streams that is executed as a graph of "oplets"
> > in a lightweight embeddable runtime.   The SDK provides capabilities like
> > windowing, aggregation  and connectors with an extensible model for the
> > community to expand its  capabilities.
> >
> > === Background ===
> >  . Stream processing systems are commonly used to process  data from edge
> > devices and there is a need to push some of the  streaming analytics to
> the
> > edge to reduce communication costs, react  locally and offload processing
> > from the central systems.  Quarks was developed by IBM as an entirely new
> > project to provide an SDK  and lightweight embeddable runtime for
> streaming
> > analytics at the edge.   Quarks was created to be an open source project
> > that could provide edge  analytics to a broad community and foster
> > collaboration on common  analytics and connectors across a broad
> ecosystem
> > of devices.
> >
> > === Rationale ===
> >  . With the growth in number of connected devices (Internet of Things)
> > there is a need to execute analytics at the edge in order to take local
> > actions based upon sensor information and/or reduce the volume of data
> > sent to back-end analytic systems to reduce communication cost.
> >  Quarks rationale is to provide  consistent and easy to use programming
> > models to allow application developers to focus on their  application
> > rather than issues like device connectivity, threading etc.   Quarks'
> > functional data flow programming model is similar to systems  like Apache
> > Flink, Beam (An incubating Apache project), Java 8 Streams & Apache
> Spark.
> >  The API currently has language bindings for Java8, Java7 and Android.
> > Quarks was developed to address requirements for analytics at the  edge
> for
> > IoT use cases that were not addressed by central analytic  solutions.  We
> > believe that these capabilities will be useful to many  organizations and
> > that the diverse nature of edge devices and use cases  is best addressed
> by
> > an open community. Therefore, we would like to contribute Quarks to the
> ASF
> > as an open source project and begin developing a community of developers
> > and users within Apache.
> >
> > === Initial Goals ===
> >  . Quarks initial code contribution provides:
> >
> >  * APIs for developing applications that execute  analytics using a
> > per-event (data item) streaming paradigm including  support for windows
> > against a stream for aggregation
> >  * A micro-kernel style runtime for execution.
> >  * Connectors for MQTT, HTTP, JDBC, File, Apache Kafka &  IBM Watson IoT
> > Platform
> >  * Simple analytics aimed at device sensors (using Apache Common Math)
> >  * Development mode including a web-console to view the graph of running
> > applications
> >  * Testing mechanism for Quarks applications that integrates with
> > assertion based testing systems like JUnit
> >  * Android specific functionality such as producing a stream that
> contains
> > a phone's sensor events (e.g. ambient temperature, pressure)
> >  * JUnit tests
> >  .
> >  . All of the initial code is implemented using Java 8 and when built
> > produces jars that can execute on Java 8, Java 7 and Android. The goal is
> > to encourage community contributions in any area of Quarks, to  expand
> the
> > community (including new committers) and use of Quarks. We  expect
> > contributions will be driven by real-world use of Quarks by  anyone
> active
> > in the IoT space such as auto manufactures, insurance  companies, etc. as
> > well as individuals experimenting with devices such  as Raspberry Pis,
> > Arduinos and/or smart phone apps etc. Contributions would be welcomed in
> > any aspect of Quarks including:
> >  .
> >  * Support for 

Re: [VOTE] Accept Beam into the Apache Incubator

[James Taylor]

+1 (binding)

On Thu, Jan 28, 2016 at 6:28 AM, Jean-Baptiste Onofré 
wrote:

> Hi,
>
> the Beam proposal (initially Dataflow) was proposed last week.
>
> The complete discussion thread is available here:
>
>
> http://mail-archives.apache.org/mod_mbox/incubator-general/201601.mbox/%3CCA%2B%3DKJmvj4wyosNTXVpnsH8PhS7jEyzkZngc682rGgZ3p28L42Q%40mail.gmail.com%3E
>
> As reminder the BeamProposal is here:
>
> https://wiki.apache.org/incubator/BeamProposal
>
> Regarding all the great feedbacks we received on the mailing list, we
> think it's time to call a vote to accept Beam into the Incubator.
>
> Please cast your vote to:
> [] +1 - accept Apache Beam as a new incubating project
> []  0 - not sure
> [] -1 - do not accept the Apache Beam project (because: ...)
>
> Thanks,
> Regards
> JB
> 
> ## page was renamed from DataflowProposal
> = Apache Beam =
>
> == Abstract ==
>
> Apache Beam is an open source, unified model and set of language-specific
> SDKs for defining and executing data processing workflows, and also data
> ingestion and integration flows, supporting Enterprise Integration Patterns
> (EIPs) and Domain Specific Languages (DSLs). Dataflow pipelines simplify
> the mechanics of large-scale batch and streaming data processing and can
> run on a number of runtimes like Apache Flink, Apache Spark, and Google
> Cloud Dataflow (a cloud service). Beam also brings DSL in different
> languages, allowing users to easily implement their data integration
> processes.
>
> == Proposal ==
>
> Beam is a simple, flexible, and powerful system for distributed data
> processing at any scale. Beam provides a unified programming model, a
> software development kit to define and construct data processing pipelines,
> and runners to execute Beam pipelines in several runtime engines, like
> Apache Spark, Apache Flink, or Google Cloud Dataflow. Beam can be used for
> a variety of streaming or batch data processing goals including ETL, stream
> analysis, and aggregate computation. The underlying programming model for
> Beam provides MapReduce-like parallelism, combined with support for
> powerful data windowing, and fine-grained correctness control.
>
> == Background ==
>
> Beam started as a set of Google projects (Google Cloud Dataflow) focused
> on making data processing easier, faster, and less costly. The Beam model
> is a successor to MapReduce, FlumeJava, and Millwheel inside Google and is
> focused on providing a unified solution for batch and stream processing.
> These projects on which Beam is based have been published in several papers
> made available to the public:
>
>  * MapReduce - http://research.google.com/archive/mapreduce.html
>  * Dataflow model  - http://www.vldb.org/pvldb/vol8/p1792-Akidau.pdf
>  * FlumeJava - http://research.google.com/pubs/pub35650.html
>  * MillWheel - http://research.google.com/pubs/pub41378.html
>
> Beam was designed from the start to provide a portable programming layer.
> When you define a data processing pipeline with the Beam model, you are
> creating a job which is capable of being processed by any number of Beam
> processing engines. Several engines have been developed to run Beam
> pipelines in other open source runtimes, including a Beam runner for Apache
> Flink and Apache Spark. There is also a “direct runner”, for execution on
> the developer machine (mainly for dev/debug purposes). Another runner
> allows a Beam program to run on a managed service, Google Cloud Dataflow,
> in Google Cloud Platform. The Dataflow Java SDK is already available on
> GitHub, and independent from the Google Cloud Dataflow service. Another
> Python SDK is currently in active development.
>
> In this proposal, the Beam SDKs, model, and a set of runners will be
> submitted as an OSS project under the ASF. The runners which are a part of
> this proposal include those for Spark (from Cloudera), Flink (from data
> Artisans), and local development (from Google); the Google Cloud Dataflow
> service runner is not included in this proposal. Further references to Beam
> will refer to the Dataflow model, SDKs, and runners which are a part of
> this proposal (Apache Beam) only. The initial submission will contain the
> already-released Java SDK; Google intends to submit the Python SDK later in
> the incubation process. The Google Cloud Dataflow service will continue to
> be one of many runners for Beam, built on Google Cloud Platform, to run
> Beam pipelines. Necessarily, Cloud Dataflow will develop against the Apache
> project additions, updates, and changes. Google Cloud Dataflow will become
> one user of Apache Beam and will participate in the project openly and
> publicly.
>
> The Beam programming model has been designed with simplicity, scalability,
> and speed as key tenants. In the Beam model, you only need to think about
> four top-level concepts when constructing your data processing job:
>
>  * Pipelines - The data processing job made of a series of computations
> including 

Re: [VOTE] Accept the iota project into the Apache Incubator

[James Taylor]

+1 (binding). Interesting proposal and I love the name.

On Wed, Jan 20, 2016 at 12:58 PM, Seetharam Venkatesh <
venkat...@innerzeal.com> wrote:

> +1 (binding).
>
> Thanks!
>
> On Wed, Jan 20, 2016 at 8:49 AM Julian Hyde  wrote:
>
> > +1 (binding)
> >
> > Julian
> >
> > > On Jan 19, 2016, at 10:43 PM, Jean-Baptiste Onofré 
> > wrote:
> > >
> > > +1 (binding)
> > >
> > > Regards
> > > JB
> > >
> > > On 01/19/2016 01:25 PM, Hadrian Zbarcea wrote:
> > >> I want to encourage more IPMC members to cast a vote, in case this
> > >> thread went unnoticed.
> > >>
> > >> Cheers,
> > >> Hadrian
> > >>
> > >> On 01/16/2016 03:40 PM, Hadrian Zbarcea wrote:
> > >>> The vote is as usually open for at least 72 hours.
> > >>>
> > >>> Here's my +1.
> > >>>
> > >>> Hadrian
> > >>>
> > >>>
> > >>> On 01/16/2016 03:12 PM, Hadrian Zbarcea wrote:
> >  Hi,
> > 
> >  The iota proposal [1] (initially Tempo) was proposed about 6 weeks
> > ago.
> > 
> >  Because of the naming conflict that would have likely required to
> > change
> >  name at graduation, the project name was changed to "Apache iota"
> (the
> >  greek letter), which resonates better with the IoT field the project
> >  targets and passed a summary podling name search.
> > 
> >  The code was made available in December for our review and answers
> on
> >  the general@ list have been answered.
> > 
> >  We think it's time to move to the next step, a formal vote.
> > Therefore...
> > 
> >  Please cast your vote to:
> >  [] +1 - accept Apache iota as a new incubating project
> >  []  0 - not sure
> >  [] -1 - do not accept the Apache iota project (because: ...)
> > 
> >  Thanks,
> >  Hadrian
> > 
> > 
> >  [1] https://wiki.apache.org/incubator/IotaProposal
> >  [2] https://en.wikipedia.org/wiki/Iota
> > 
> > 
> >  -
> > 
> >  iota Proposal
> > 
> >  Abstract
> > 
> >  The Apache Foundation has been very successful in bringing together
> > key
> >  software components that have enabled people to interact with each
> > other
> >  via a variety of content platforms and it will no doubt continue to
> do
> >  so. At the same time modern society is becoming increasingly
> dependent
> >  on devices that interact with each other and with people. The amount
> > of
> >  data that will be produced by devices will be orders of magnitude
> >  greater than what has been produced by humans in the past. In
> > addition,
> >  the orchestration of devices and people will be an important area of
> >  growth for the foreseeable future. This new dynamic will eventually
> >  become manifest in a growing number of Apache projects that enable
> > this
> >  to occur. Our wish is to contribute to this movement by contributing
> > the
> >  iota system to the Open Source Community via the Apache Foundation.
> >  Apache iota is an open platform to interconnect any and all devices,
> >  sensors, people, and applications, henceforth referred to as points,
> >  through a scalable, secure, and modular architecture, enabling
> >  applications to generate analysis, create actions and/or add
> >  intelligence to their behaviors and patterns.
> > 
> >  Proposal
> > 
> >  Perhaps you are a homeowner configuring the interaction between your
> >  family and all the smart devices in your home. Or you might be a
> > global
> >  company orchestrating millions of devices and people across
> different
> >  continents. Either way you face the same fundamental problem;
> namely,
> >  how do you manage many points in a secure robust and meaningful
> > manner?
> >  Apache iota is an open source software system that enables
> homeowners
> >  and global companies to download a software system that provides
> > secure
> >  and robust orchestration.
> > 
> >  The iota system consists of a variety of components:
> > 
> >  A basic but extensible desktop
> >  An extensible mechanism for capturing data from a variety of sources
> >  A set of translators that feed the data capture mechanism and a
> >  framework for the development of additional translators
> >  A secure means of moving data using digital envelopes based on
> > symmetric
> >  and asymmetric encryption and decryption via Apache Kafka
> >  Optionally maintaining data encrypted in a datastore
> >  Support for a variety of data repositories
> >  Authentication and authorization using OAuth2
> >  Secure APIs for access to data and the system information
> >  User management
> >  Device management
> >  Automated software upgrades via Salt
> >  Configuration management
> >  Robust basic infrastructure based on Apache Mesos that enables
> >  scalability
> >  Dockerized applications
> >  

interested in joining the IPMC

[James Taylor]

Hello,
I'm the PMC Chair for Apache Phoenix and a PMC member of Apache Calcite,
both top level project and both of which I went through the incubation
process. Recently several projects interested in going through incubation
approached me to be a mentor, hence my interest in joining - so that I can
help guide them through this process. I understand that the process for non
ASF members is to initiate a vote on the private list. I'd appreciate it if
that could start at your earliest convenience.

Please let me know if I need to perform any further action before a vote is
started.

Thanks,
James

Re: interested in joining the IPMC

[James Taylor]

My apologies, Marvin, and thanks for clarifying the procedure. I'll follow
up on the private list.

James

On Sat, Dec 12, 2015 at 11:33 AM, Marvin Humphrey <mar...@rectangular.com>
wrote:

> On Sat, Dec 12, 2015 at 11:04 AM, James Taylor <jamestay...@apache.org>
> wrote:
> > Hello,
> > I'm the PMC Chair for Apache Phoenix and a PMC member of Apache Calcite,
> > both top level project and both of which I went through the incubation
> > process. Recently several projects interested in going through incubation
> > approached me to be a mentor, hence my interest in joining - so that I
> can
> > help guide them through this process. I understand that the process for
> non
> > ASF members is to initiate a vote on the private list. I'd appreciate it
> if
> > that could start at your earliest convenience.
> >
> > Please let me know if I need to perform any further action before a vote
> is
> > started.
>
> Hi James, thanks for your interest. For what it's worth, there's no
> reason you couldn't help out a podling without being a Mentor.  And
> the process for non-ASF-Members joining the Incubator PMC is actually
> the same as for any other Apache PMC -- someone earns merit and then
> is invited to join.
>
> Regardless of what happens in this specific case, if people are going
> to initiate direct requests like this, I wish they would use the
> private list.  Every once in a while somebody who has not earned merit
> makes a request to join a PMC; it is awkward to rebuff such requests
> discreetly when the request is public.  Apache private lists are not
> supposed to be used a lot, but personnel discussions are one of the
> main reasons we have them.
>
> Marvin Humphrey
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Incubator PMC/Board report for Jun 2014 ([ppmc])

[James Taylor]

FYI, Phoenix has graduated as reported last month.
Thanks,
James

On Wednesday, May 28, 2014, Marvin no-re...@apache.org wrote:



 Dear podling,

 This email was sent by an automated system on behalf of the Apache
 Incubator PMC.
 It is an initial reminder to give you plenty of time to prepare your
 quarterly
 board report.

 The board meeting is scheduled for Wed, 18 June 2014, 10:30:30:00 PST. The
 report
 for your podling will form a part of the Incubator PMC report. The
 Incubator PMC
 requires your report to be submitted 2 weeks before the board meeting, to
 allow
 sufficient time for review and submission (Wed, Jun 4th).

 Please submit your report with sufficient time to allow the incubator PMC,
 and
 subsequently board members to review and digest. Again, the very latest you
 should submit your report is 2 weeks prior to the board meeting.

 Thanks,

 The Apache Incubator PMC

 Submitting your Report
 --

 Your report should contain the following:

  * Your project name
  * A brief description of your project, which assumes no knowledge of the
 project
or necessarily of its field
  * A list of the three most important issues to address in the move towards
graduation.
  * Any issues that the Incubator PMC or ASF Board might wish/need to be
 aware of
  * How has the community developed since the last report
  * How has the project developed since the last report.

 This should be appended to the Incubator Wiki page at:

   http://wiki.apache.org/incubator/June2014

 Note: This manually populated. You may need to wait a little before this
 page is
   created from a template.

 Mentors
 ---
 Mentors should review reports for their project(s) and sign them off on the
 Incubator wiki page. Signing off reports shows that you are following the
 project - projects that are not signed may raise alarms for the Incubator
 PMC.

 Incubator PMC


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

Re: Incubator PMC/Board report for Jun 2014 ([ppmc])

[James Taylor]

Thanks, Jake. I updated it. FWIW, I found I had to use this URL to find the
podlings.xml file:
https://svn.apache.org/repos/asf/incubator/public/trunk/content
(instead of the incubator/trunk/content mentioned in the guide).

James



On Wed, May 28, 2014 at 10:57 AM, Jake Farrell jfarr...@apache.org wrote:

 Hey James
 Looks like some steps where missed in the graduation guide [1], Apache
 Phoenix is still listed to report in group 1 and not as a TLP in the
 podlings.xml file. Can you or someone else from the Phoenix project please
 finish the graduation process, appreciate your help

 -Jake

 [1]: http://incubator.apache.org/guides/graduation.html#unincubate


 On Wed, May 28, 2014 at 1:41 PM, James Taylor jamestay...@apache.org
 wrote:

  FYI, Phoenix has graduated as reported last month.
  Thanks,
  James
 
  On Wednesday, May 28, 2014, Marvin no-re...@apache.org wrote:
 
  
  
   Dear podling,
  
   This email was sent by an automated system on behalf of the Apache
   Incubator PMC.
   It is an initial reminder to give you plenty of time to prepare your
   quarterly
   board report.
  
   The board meeting is scheduled for Wed, 18 June 2014, 10:30:30:00 PST.
  The
   report
   for your podling will form a part of the Incubator PMC report. The
   Incubator PMC
   requires your report to be submitted 2 weeks before the board meeting,
 to
   allow
   sufficient time for review and submission (Wed, Jun 4th).
  
   Please submit your report with sufficient time to allow the incubator
  PMC,
   and
   subsequently board members to review and digest. Again, the very latest
  you
   should submit your report is 2 weeks prior to the board meeting.
  
   Thanks,
  
   The Apache Incubator PMC
  
   Submitting your Report
   --
  
   Your report should contain the following:
  
* Your project name
* A brief description of your project, which assumes no knowledge of
 the
   project
  or necessarily of its field
* A list of the three most important issues to address in the move
  towards
  graduation.
* Any issues that the Incubator PMC or ASF Board might wish/need to be
   aware of
* How has the community developed since the last report
* How has the project developed since the last report.
  
   This should be appended to the Incubator Wiki page at:
  
 http://wiki.apache.org/incubator/June2014
  
   Note: This manually populated. You may need to wait a little before
 this
   page is
 created from a template.
  
   Mentors
   ---
   Mentors should review reports for their project(s) and sign them off on
  the
   Incubator wiki page. Signing off reports shows that you are following
 the
   project - projects that are not signed may raise alarms for the
 Incubator
   PMC.
  
   Incubator PMC
  
  
   -
   To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
  javascript:;
   For additional commands, e-mail: general-h...@incubator.apache.org
  javascript:;
  
  
 

Re: [VOTE] Graduation of Apache Phoenix from the Incubator

[James Taylor]

+1


On Fri, May 2, 2014 at 5:00 PM, Enis Söztutar e...@apache.org wrote:

 +1 (binding)

 Enis


 On Fri, May 2, 2014 at 4:51 PM, Devaraj Das d...@hortonworks.com wrote:

  +1
 
  On Wed, Apr 30, 2014 at 10:44 PM, James Taylor jamestay...@apache.org
  wrote:
   Hi everyone,
  
   The Apache Phoenix podling has has discussed and voted to graduate from
  the
   incubator with 22 +1 votes, 5 of which were IPMC vote [1]. We've made
  three
   releases, increased our contributor and committer list [2], and have an
   active, thriving community.
  
   Please VOTE below on the graduation of Apache Phoenix from the
   Incubator. The graduation resolution is pasted below.
  
   The VOTE will be open for at least 72 hours:
  
   [ ] +1 Graduate Apache Phoenix from the Incubator.
   [ ] +0 Don't care.
   [ ] -1 Don't graduate Apache Phoenix from the Incubator because
  
   [1]
  
 
 http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201405.mbox/%3CCAAF1JdgX_0nc7hgSrx9v1wJGKG0C3LBjO2ceZpGYsW1Z%3DsSaYw%40mail.gmail.com%3E
   [2] https://incubator.apache.org/projects/phoenix.html
  
  
   X. Establish the Apache Phoenix Project
  
  WHEREAS, the Board of Directors deems it to be in the best
  interests of the Foundation and consistent with the
  Foundation's purpose to establish a Project Management
  Committee charged with the creation and maintenance of
  open-source software, for distribution at no charge to
  the public, related to a SQL database for NoSQL data stores
  such as Apache HBase.
  
  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
  Committee (PMC), to be known as the Apache Phoenix Project,
  be and hereby is established pursuant to Bylaws of the
  Foundation; and be it further
  
  RESOLVED, that the Apache Phoenix Project be and hereby is
  responsible for the creation and maintenance of software
  related to a SQL database for NoSQL data stores such as Apache
  HBase; and be it further
  
  RESOLVED, that the office of Vice President, Apache Phoenix be
  and hereby is created, the person holding such office to
  serve at the direction of the Board of Directors as the chair
  of the Apache Phoenix Project, and to have primary
 responsibility
  for management of the projects within the scope of
  responsibility of the Apache Phoenix Project; and be it further
  
  RESOLVED, that the persons listed immediately below be and
  hereby are appointed to serve as the initial members of the
  Apache Phoenix Project:
  
* Andrew Purtellapurt...@apache.org
* Anoop Sam Johnanoopsamj...@apache.org
* Devaraj Das   d...@apache.org
* Eli Levineelilev...@apache.org
* Enis Soztutar e...@apache.org
* Gabriel Reid  gr...@apache.org
* James R. Taylor   jamestay...@apache.org
* Jeffrey Zhong jeffr...@apache.org
* Jesse Yates   jya...@apache.org
* Lars Hofhansl la...@apache.org
* Maryann Xue   maryann...@apache.org
* Michael Stack st...@apache.org
* Mujtaba Chohanmujt...@apache.org
* Nick Dimiduk  ndimi...@apache.org
* Ramkrishna Vasudevan  ramkris...@apache.org
* Simon Toens   sto...@apache.org
* Steven Noels  stev...@apache.org
  
  NOW, THEREFORE, BE IT FURTHER RESOLVED, that James R. Taylor
  be appointed to the office of Vice President, Apache Phoenix, to
  serve in accordance with and subject to the direction of the
  Board of Directors and the Bylaws of the Foundation until
  death, resignation, retirement, removal or disqualification,
  or until a successor is appointed; and be it further
  
  RESOLVED, that the initial Apache Phoenix PMC be and hereby is
  tasked with the creation of a set of bylaws intended to
  encourage open development and increased participation in the
  Apache Phoenix Project; and be it further
  
  RESOLVED, that the Apache Phoenix Project be and hereby
  is tasked with the migration and rationalization of the Apache
  Incubator Phoenix podling; and be it further
  
  RESOLVED, that all responsibilities pertaining to the Apache
  Incubator Phoenix podling encumbered upon the Apache Incubator
  Project are hereafter discharged.
 
  --
  CONFIDENTIALITY NOTICE
  NOTICE: This message is intended for the use of the individual or entity
 to
  which it is addressed and may contain information that is confidential,
  privileged and exempt from disclosure under applicable law. If the reader
  of this message is not the intended

[RESULT][VOTE] Graduation of Apache Phoenix from the Incubator

[James Taylor]

Hello everyone,

I'm pleased to report that this VOTE has passed with the 9 +1 votes (7
binding):

+1
Eli Levine
Steven Noels*
Michael Stack*
Andrew Purtell*
Roman Shaposhnik*
Lars Hofhansl*
Devaraj Das*
Enis Söztutar*
James Taylor

* - indicates IPMC

I will add the resolution to the board agenda for May 2014. Thank you to
the IPMC, as we've learned a lot on our journey through the incubator.

Cheers,
James


On Fri, May 2, 2014 at 5:00 PM, Enis Söztutar e...@apache.org wrote:

 +1 (binding)

 Enis


 On Fri, May 2, 2014 at 4:51 PM, Devaraj Das d...@hortonworks.com wrote:

  +1
 
  On Wed, Apr 30, 2014 at 10:44 PM, James Taylor jamestay...@apache.org
  wrote:
   Hi everyone,
  
   The Apache Phoenix podling has has discussed and voted to graduate from
  the
   incubator with 22 +1 votes, 5 of which were IPMC vote [1]. We've made
  three
   releases, increased our contributor and committer list [2], and have an
   active, thriving community.
  
   Please VOTE below on the graduation of Apache Phoenix from the
   Incubator. The graduation resolution is pasted below.
  
   The VOTE will be open for at least 72 hours:
  
   [ ] +1 Graduate Apache Phoenix from the Incubator.
   [ ] +0 Don't care.
   [ ] -1 Don't graduate Apache Phoenix from the Incubator because
  
   [1]
  
 
 http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201405.mbox/%3CCAAF1JdgX_0nc7hgSrx9v1wJGKG0C3LBjO2ceZpGYsW1Z%3DsSaYw%40mail.gmail.com%3E
   [2] https://incubator.apache.org/projects/phoenix.html
  
  
   X. Establish the Apache Phoenix Project
  
  WHEREAS, the Board of Directors deems it to be in the best
  interests of the Foundation and consistent with the
  Foundation's purpose to establish a Project Management
  Committee charged with the creation and maintenance of
  open-source software, for distribution at no charge to
  the public, related to a SQL database for NoSQL data stores
  such as Apache HBase.
  
  NOW, THEREFORE, BE IT RESOLVED, that a Project Management
  Committee (PMC), to be known as the Apache Phoenix Project,
  be and hereby is established pursuant to Bylaws of the
  Foundation; and be it further
  
  RESOLVED, that the Apache Phoenix Project be and hereby is
  responsible for the creation and maintenance of software
  related to a SQL database for NoSQL data stores such as Apache
  HBase; and be it further
  
  RESOLVED, that the office of Vice President, Apache Phoenix be
  and hereby is created, the person holding such office to
  serve at the direction of the Board of Directors as the chair
  of the Apache Phoenix Project, and to have primary
 responsibility
  for management of the projects within the scope of
  responsibility of the Apache Phoenix Project; and be it further
  
  RESOLVED, that the persons listed immediately below be and
  hereby are appointed to serve as the initial members of the
  Apache Phoenix Project:
  
* Andrew Purtellapurt...@apache.org
* Anoop Sam Johnanoopsamj...@apache.org
* Devaraj Das   d...@apache.org
* Eli Levineelilev...@apache.org
* Enis Soztutar e...@apache.org
* Gabriel Reid  gr...@apache.org
* James R. Taylor   jamestay...@apache.org
* Jeffrey Zhong jeffr...@apache.org
* Jesse Yates   jya...@apache.org
* Lars Hofhansl la...@apache.org
* Maryann Xue   maryann...@apache.org
* Michael Stack st...@apache.org
* Mujtaba Chohanmujt...@apache.org
* Nick Dimiduk  ndimi...@apache.org
* Ramkrishna Vasudevan  ramkris...@apache.org
* Simon Toens   sto...@apache.org
* Steven Noels  stev...@apache.org
  
  NOW, THEREFORE, BE IT FURTHER RESOLVED, that James R. Taylor
  be appointed to the office of Vice President, Apache Phoenix, to
  serve in accordance with and subject to the direction of the
  Board of Directors and the Bylaws of the Foundation until
  death, resignation, retirement, removal or disqualification,
  or until a successor is appointed; and be it further
  
  RESOLVED, that the initial Apache Phoenix PMC be and hereby is
  tasked with the creation of a set of bylaws intended to
  encourage open development and increased participation in the
  Apache Phoenix Project; and be it further
  
  RESOLVED, that the Apache Phoenix Project be and hereby
  is tasked with the migration and rationalization of the Apache
  Incubator Phoenix podling; and be it further
  
  RESOLVED, that all responsibilities pertaining to the Apache

[VOTE] Graduation of Apache Phoenix from the Incubator

[James Taylor]

Hi everyone,

The Apache Phoenix podling has has discussed and voted to graduate from the
incubator with 22 +1 votes, 5 of which were IPMC vote [1]. We've made three
releases, increased our contributor and committer list [2], and have an
active, thriving community.

Please VOTE below on the graduation of Apache Phoenix from the
Incubator. The graduation resolution is pasted below.

The VOTE will be open for at least 72 hours:

[ ] +1 Graduate Apache Phoenix from the Incubator.
[ ] +0 Don't care.
[ ] -1 Don't graduate Apache Phoenix from the Incubator because

[1]
http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201405.mbox/%3CCAAF1JdgX_0nc7hgSrx9v1wJGKG0C3LBjO2ceZpGYsW1Z%3DsSaYw%40mail.gmail.com%3E
[2] https://incubator.apache.org/projects/phoenix.html


X. Establish the Apache Phoenix Project

   WHEREAS, the Board of Directors deems it to be in the best
   interests of the Foundation and consistent with the
   Foundation's purpose to establish a Project Management
   Committee charged with the creation and maintenance of
   open-source software, for distribution at no charge to
   the public, related to a SQL database for NoSQL data stores
   such as Apache HBase.

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

   RESOLVED, that the Apache Phoenix Project be and hereby is
   responsible for the creation and maintenance of software
   related to a SQL database for NoSQL data stores such as Apache
   HBase; and be it further

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

   RESOLVED, that the persons listed immediately below be and
   hereby are appointed to serve as the initial members of the
   Apache Phoenix Project:

 * Andrew Purtellapurt...@apache.org
 * Anoop Sam Johnanoopsamj...@apache.org
 * Devaraj Das   d...@apache.org
 * Eli Levineelilev...@apache.org
 * Enis Soztutar e...@apache.org
 * Gabriel Reid  gr...@apache.org
 * James R. Taylor   jamestay...@apache.org
 * Jeffrey Zhong jeffr...@apache.org
 * Jesse Yates   jya...@apache.org
 * Lars Hofhansl la...@apache.org
 * Maryann Xue   maryann...@apache.org
 * Michael Stack st...@apache.org
 * Mujtaba Chohanmujt...@apache.org
 * Nick Dimiduk  ndimi...@apache.org
 * Ramkrishna Vasudevan  ramkris...@apache.org
 * Simon Toens   sto...@apache.org
 * Steven Noels  stev...@apache.org

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

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

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

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

[ANNOUNCE] Apache Phoenix 4.0.0-incubating released

[James Taylor]

Hello everyone,
The Apache Phoenix team is pleased to announce the release of version
4.0.0-incubating from the Apache Incubator. Phoenix is a SQL query engine
for Apache HBase, a NoSQL data store. It is accessed as a JDBC driver and
enables querying and managing HBase tables using SQL.
This is the next major release of Phoenix compatible with the 0.98 branch
of Apache HBase (0.98.1+) and having feature parity with our 3.0.0 release. It
includes the following new features:- Equi-joins through broadcast hash
join- Shared tables over same physical HBase table- Read-only and updatable
views- Multi-tenancy- JDBC ARRAY type- Sequence creation and usage
The source and binaries for the release may be downloaded here:
http://phoenix.incubator.apache.org/download.html
Link to release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315120version=12326145
For general information on Apache Phoenix, please visit the project website:
http://phoenix.incubator.apache.org/index.html
Disclaimer:Apache Phoenix is an effort undergoing incubation at The Apache
Software Foundation (ASF), sponsored by the Apache Incubator PMC.
Incubation is required of all newly accepted projects until a further
review indicates that the infrastructure, communications, and decision
making process have stabilized in a manner consistent with other successful
ASF projects. While incubation status is not necessarily a reflection of
the completeness or stability of the code, it does indicate that the
project has yet to be fully endorsed by the ASF.
Regards,The Apache Phoenix team

[ANNOUNCE] Apache Phoenix 3.0.0-incubating released

[James Taylor]

Hello everyone,

The Apache Phoenix team is pleased to announce the release of version
3.0.0-incubating from the Apache Incubator. Phoenix is a SQL query engine
for Apache HBase, a NoSQL data store. It is accessed as a JDBC driver and
enables querying and managing HBase tables using SQL.

Major new features include:
- Equi-joins through broadcast hash join
- Shared tables over same physical HBase table
- Read-only and updatable views
- Multi-tenancy
- JDBC ARRAY type
- Sequence creation and usage

The source and binaries for the release may be downloaded here:
http://phoenix.incubator.apache.org/download.html

Link to release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315120version=12326145

For general information on Apache Phoenix, please visit the project website:
http://phoenix.incubator.apache.org/index.html

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

Regards,
The Apache Phoenix team

[RESULT][VOTE] Release of Apache Phoenix 3.0.0 incubating RC3

[James Taylor]

Voting is now closed. This vote passes with 3 +1 votes and no 0 or -1
votes. Thank you to everyone who voted. Totals:

+1:
Lars Hofhansl*
Devaraj Das*
Steven Noels*

* = IPMC

I'll send out an announcement and we'll push the release out.
Thanks,
James


On Thu, Apr 3, 2014 at 10:31 AM, Steven Noels stev...@apache.org wrote:

 On Mon, Mar 31, 2014, at 10:40 PM, James Taylor wrote:


  Vote will be open for at least 72 hours. Please vote:
 
  [ ] +1 approve
  [ ] +0 no opinion
  [ ] -1 disapprove (and reason why)


 +1 (binding)

 Doing great, Phoenix team!

 Steven.

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

[RESULT][VOTE] Release of Apache Phoenix 4.0.0 incubating RC3

[James Taylor]

Voting is now closed. This vote passes with 4 +1 votes and no 0 or -1
votes. Thank you to everyone who voted. Totals:

+1:
Michael Stack*
Steven Noels*
Enis Söztutar*
Devaraj Das*

* = IPMC

I'll send out an announcement and we'll push the release out once HBase
0.98.1 is released.

Thanks,
James


On Fri, Apr 4, 2014 at 3:29 PM, Devaraj Das d...@hortonworks.com wrote:

 +1

 On Thu, Apr 3, 2014 at 4:06 PM, Enis Söztutar enis@gmail.com wrote:
  +1
 
  On Thursday, April 3, 2014, Steven Noels stev...@apache.org wrote:
 
  On Wed, Apr 2, 2014, at 08:53 AM, Stack wrote:
   +1
  
   (Promoting my phoenix dev list +1 here)
 
  +1
 
  (ditto)
 
  Keep up the great work.
 
  Steven.
 
  -
  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 javascript:;
  For additional commands, e-mail: general-h...@incubator.apache.org
 javascript:;
 
 

 --
 CONFIDENTIALITY NOTICE
 NOTICE: This message is intended for the use of the individual or entity to
 which it is addressed and may contain information that is confidential,
 privileged and exempt from disclosure under applicable law. If the reader
 of this message is not the intended recipient, you are hereby notified that
 any printing, copying, dissemination, distribution, disclosure or
 forwarding of this communication is strictly prohibited. If you have
 received this communication in error, please contact the sender immediately
 and delete it from your system. Thank You.

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

[VOTE] Release of Apache Phoenix 3.0.0 incubating RC3

[James Taylor]

Hi everyone,
This is a call for a vote on Apache Phoenix 3.0.0 incubating RC3. Phoenix
is a SQL query engine for Apache HBase, a NoSQL data store. It is accessed
as a JDBC driver and enables querying and managing HBase tables using SQL. This
is the next major release of Phoenix compatible with the 0.94 branch of
Apache HBase and will be our second release in the incubator. The release
includes both a source-only release and a convenience binary release.

New features include:
- Equi-joins through broadcast hash join
- Shared tables over same physical HBase table
- Read-only and updatable views
- Multi-tenancy
- JDBC ARRAY type
- Sequence creation and usage

The dev list thread for the passing vote (8 +1s with 2 IPMC votes) can be
found at:
http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201404.mbox/%3CCAAF1JdiaQHkaT7FeMW9R343j4mbZLOr0Qxn2ZeP9EoXVv4%3DGZQ%40mail.gmail.com%3E

The source tarball, including signatures, digests, etc can be found at:
https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-3.0.0-incubating-rc3/src/

The binary artifacts can be found at:
https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-3.0.0-incubating-rc3/bin/

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

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

The hash and tag to be voted on:
https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=commit;h=363e71bfd7cf6576657dddb484c6a48de9b8de61
https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=tag;h=refs/tags/v3.0.0-incubating-rc3

For information about the contents of this release see:
https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=log;h=refs/tags/v3.0.0-incubating-rc3

Vote will be open for at least 72 hours. Please vote:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
The Apache Phoenix Team

[VOTE] Release of Apache Phoenix 4.0.0 incubating RC3

[James Taylor]

Hi everyone,
This is a call for a vote on Apache Phoenix 4.0.0 incubating RC3. Phoenix
is a SQL query engine for Apache HBase, a NoSQL data store. It is accessed
as a JDBC driver and enables querying and managing HBase tables using SQL. This
is the next major release of Phoenix compatible with the 0.98 branch of
Apache HBase (0.98.1+) and will be our third release in the incubator. The
release includes both a source-only release and a convenience binary
release.

The 4.0.0 release has feature parity with our pending 3.0.0 release. New
features include:
- Equi-joins through broadcast hash join
- Shared tables over same physical HBase table
- Read-only and updatable views
- Multi-tenancy
- JDBC ARRAY type
- Sequence creation and usage

The dev list thread for the passing vote (7 +1s with 2 IPMC votes) can be
found at:
http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201404.mbox/%3CCAAF1JdjJ_3%2B%2B2y3TYFNUDJSt9UVJngQjqg5dU6qnTUW%2BamhBag%40mail.gmail.com%3E

The source tarball, including signatures, digests, etc can be found at:
https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-4.0.0-incubating-rc3/src/

The binary artifacts can be found at:
https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-4.0.0-incubating-rc3/bin/

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

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

The hash and tag to be voted on:
https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=commit;h=4d90a49dd375da984a9db195d517ef26166745f0
https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=tag;h=refs/tags/v4.0.0-incubating-rc3

For information about the contents of this release see:
https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=log;h=refs/tags/v4.0.0-incubating-rc3

Vote will be open for at least 72 hours. Please vote:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
The Apache Phoenix Team

Re: [DISCUSS] Where does copyright information go for a binary distribution?

[James Taylor]

Hi Justin,
Yes, our source and binary releases have different NOTICE/LICENSE files.
The source ones are simple, as we have no dependencies. It's the binary one
I'm trying to get clarity on.
Thanks,
James


On Wed, Mar 26, 2014 at 5:09 PM, Justin Mclean jus...@classsoftware.comwrote:

 Hi,

 I assuming you source and binary releases will require different
 NOTICE/LICENSE files?

 For the upcoming Apache FlexUnit release I created a NOTICE and LICENCE
 for the source release (which is included in the source zip/tar) and a
 NOTICE.bin and LICENCE.bin for the binary release (which is included in the
 binary source zip/tar).

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

Re: [DISCUSS] Where does copyright information go for a binary distribution?

[James Taylor]

Thank you, Marvin. This is very valuable, especially the way you walked
through your thought process. We'll try to apply the same logic for our
other bundled dependencies in our binary distribution with our next RC.

Cheers,
James

On Thu, Mar 27, 2014 at 8:30 PM, Marvin Humphrey mar...@rectangular.comwrote:

 On Wed, Mar 26, 2014 at 6:06 PM, James Taylor jamestay...@apache.org
 wrote:
  The copyright for the bits we're bundling. See the LICENSE file I
 included
  at the end of my email. For example:
 
  Guava, version 12.0.1, http://code.google.com/p/guava-libraries/
  Copyright 2008 Google Inc.
 
  Is that the correct way to include the Copyright? Or is this not
 required?

 First, I had to do some recon on Guava.

 *   The repo at https://code.google.com/p/guava-libraries/source/browse/
 has a file at the top level called `COPYING` which contains the ALv2.
 *   Guava source releases 12.0.1 and the current 16.0.1 do not include the
 file `COPYING`.  Individual source files have headers as spec'd at the
 end of the ALv2 (which is slightly different from the ASF's headers).
 These have Google copyright notices as above.
 *   Guava binary releases contain no licensing info in `META-INF` -- no
 `COPYING`, no `LICENSE`, no `NOTICE`.

 With that information available, I can now answer your question:

 The copyright information in the license headers of Guava source files does
 not need to be propagated into the top-level licensing files for Apache
 Phoenix for either source or binary redistributions.  For source
 redistributions, the ALv2 is satisfied by retaining such copyright notices
 in
 the original dependency source files.  The relevant clause is 4c:

 http://www.apache.org/licenses/LICENSE-2.0.html#redistribution

 c.  You must retain, in the Source form of any Derivative Works that
 You
 distribute, all copyright, patent, trademark, and attribution
 notices
 from the Source form of the Work, excluding those notices that do
 not
 pertain to any part of the Derivative Works; and

 Had the copyright notice been in a file called `NOTICE`, however, then it
 would have been required to propagate it per clause 4d of the ALv2
 for **both** source and binary redistributions.

 d.  If the Work includes a NOTICE text file as part of its
 distribution,
 then any Derivative Works that You distribute must include a
 readable
 copy of the attribution notices contained within such NOTICE file,
 excluding those notices that do not pertain to any part of the
 Derivative Works, in at least one of the following places: within a
 NOTICE text file distributed as part of the Derivative Works;
 within
 the Source form or documentation, if provided along with the
 Derivative Works; or, within a display generated by the Derivative
 Works, if and wherever such third-party notices normally appear.
 [...]

 But since Guava provides no NOTICE file, you don't need to worry about
 that.

  Also, how do I know if something is a required attributions?

 Whether there are required attributions which must be propagated into
 LICENSE or NOTICE depends on the license of the dependency, and also
 whether
 the redistribution is source or binary.

 This is a complicated question, and we ultimately ought to compose and
 maintain a table as suggested at http://s.apache.org/Et4.

 For ALv2 dependencies, see analysis of section 4 above.

 For source redistributions, the MIT, 2-clause BSD, and 3-clause BSD
 licenses
 are all satisfied by retaining the license text and copyright notice
 embedded
 in each dependency source file.

 Unfortunately, the ASF does not provide solid guidance with regards to
 binary
 redistributions bundling MIT, 2-clause BSD and 3-clause BSD dependencies.
  My
 layperson's read of the BSD licenses is that since the source files are no
 longer present, the entire license would need to be propagated *somewhere*
 and
 that either LICENSE or NOTICE inside META-INF would do.

 http://opensource.org/licenses/BSD-3-Clause

 2.  Redistributions in binary form must reproduce the above copyright
 notice, this list of conditions and the following disclaimer in the
 documentation and/or other materials provided with the
 distribution.

 Note that any binaries you produce as RM are your own responsibility.
  IANAL,
 the PMC vote only applies to the source artifacts, and only the source
 release
 is an act of the Foundation.

 Nevertheless, it might make sense for us to ask ASF Legal Affairs to start
 maintaining non-binding best-practice guidance on how to compose licensing
 documentation for binary redistributions.

 Marvin Humphrey

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

Re: [VOTE] Release of Apache Phoenix 3.0.0 incubating RC1

[James Taylor]

Thanks for all the feedback. We'll spin up another RC shortly for our 3.0
and 4.0 release with the corrections to our NOTICE and LICENSE files, along
with ensuring that our source release matches the source bundle exactly.

One question: given that we'll indicate the bundled products and their
licenses in our LICENSE file, where does the copyright info go? If I
understand this section:
http://www.apache.org/dev/licensing-howto.html#mod-notice, then we should
still include the copyrights in our NOTICE file, since our binary
distribution does not have the original NOTICE for the bundled binary jars.

Thanks,
James


On Tue, Mar 25, 2014 at 4:21 PM, Justin Mclean jus...@classsoftware.comwrote:

 Hi,

 There are several files missing license headers - is this a concern?
   ./dev/phoenix.importorder
   ./examples/STOCK_SYMBOL.csv
   ./examples/WEB_STAT.csv
   ./examples/pig/test.pig
   ./examples/pig/testdata
   ./phoenix-core/src/main/resources/java.sql.Driver

 (ignoring CHANGES and rat.txt files)

 Some very minor issues that you may want to fix/change:
 - build.txt has copyright 2010 in it
 - build.text should probably be called BUILDING
 - there's no .zip package - not require but convenient for users
 - source package name doesn't include apache, not required you may want
 to consider adding this for trademark protection

 Thanks,
 Justin

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

Re: [VOTE] Release of Apache Phoenix 3.0.0 incubating RC1

[James Taylor]

Below is our updated NOTICE (which includes the copyright for the bundled
bits) and LICENSE (minus the standard Apache 2.0 part).

Would appreciate a review.

Thanks,
James

* NOTICE **

Apache Phoenix (Incubating)
Copyright 2014 The Apache Software Foundation

This product includes software developed at
The Apache Software Foundation (http://www.apache.org/).

In addition, this product includes the following software:

JLine (http://jline.sourceforge.net/),
Copyright (c) 2002-2007, Marc Prud'hommeaux m...@cornell.edu

SQLLine (https://github.com/julianhyde/sqlline/),
Copyright (c) 2002,2003,2004,2005,2006,2007 Marc Prud'hommeaux
Copyright (c) 2004-2010 The Eigenbase Project
Copyright (c) 2013-2014 Julian Hyde

SLF4J (http://www.slf4j.org/),
Copyright (c) 2004-2008 QOS.ch

ANTLR (http://www.antlr.org/),
Copyright (c) 2003-2008, Terrence Parr.

Snappy (http://code.google.com/p/snappy/)
Copyright 2008 Google Inc.

JAnsi (http://jansi.fusesource.org/)
Copyright (c) 2009-2013 FuseSource, Corp

HawtJNI (http://fusesource.com/forge/sites/hawtjni/)
Copyright (C) 2009-2011 FuseSource Corp.

Jackson (http://jackson.codehaus.org/)
Copyright (c) 2007- Tatu Saloranta, tatu.salora...@iki.fi

Protobuf (https://code.google.com/p/protobuf/)
Copyright 2008 Google Inc.

Guava (http://code.google.com/p/guava-libraries/)
Copyright 2008 Google Inc.


* LICENSE *

The Apache License, Version 2.0, also applies to the following bundled
libraries:

JAnsi, http://jansi.fusesource.org/
HawtJNI, http://fusesource.com/forge/sites/hawtjni/
Jackson, http://jackson.codehaus.org/
Guava, http://code.google.com/p/guava-libraries/

==

BSD Clause 3/New BSD License, applies to the following bundled libraries:

Snappy, http://code.google.com/p/snappy/
Protobuf, https://code.google.com/p/protobuf/
SQLLine, https://github.com/julianhyde/sqlline/

Full license included below:

--

BSD Clause 3/New BSD License

Redistribution and use in source and binary forms, with or without
modification, are permitted provided that the following conditions are met:
* Redistributions of source code must retain the above copyright
  notice, this list of conditions and the following disclaimer.
* Redistributions in binary form must reproduce the above copyright
  notice, this list of conditions and the following disclaimer in the
  documentation and/or other materials provided with the distribution.
* Neither the name of the organization nor the
  names of its contributors may be used to endorse or promote products
  derived from this software without specific prior written permission.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS
AND
ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED
WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
DISCLAIMED. IN NO EVENT SHALL COPYRIGHT HOLDER BE LIABLE FOR ANY
DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES
(INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES;
LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND
ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT
(INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
THIS
SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.

==

BSD Clause 2 License, applies to the following bundled libraries:

JLine, http://jline.sourceforge.net/
ANTLR, http://www.antlr.org/

Full license included below:

--

The BSD 2-Clause License

Redistribution and use in source and binary forms, with or without
modification,
are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice,
this list of conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright
notice,
this list of conditions and the following disclaimer in the documentation
and/or other materials provided with the distribution.

THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS IS
AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER OR CONTRIBUTORS BE
LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR
CONSEQUENTIAL
DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER
CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
LIABILITY,
OR 

Re: [VOTE] Release of Apache Phoenix 3.0.0 incubating RC1

[James Taylor]

Thanks, Marvin. So remove the copyrights from NOTICE. Are they required
anywhere then, as their not in the LICENSE file?


On Wed, Mar 26, 2014 at 2:57 PM, Marvin Humphrey mar...@rectangular.comwrote:

 On Wed, Mar 26, 2014 at 12:59 PM, James Taylor jamestay...@apache.org
 wrote:
  Below is our updated NOTICE (which includes the copyright for the bundled
  bits) and LICENSE (minus the standard Apache 2.0 part).
 
  Would appreciate a review.

 What follows is a superficial review of what I see in this email thread --
 I
 have not checked the distribution to see whether or not bits are actually
 bundled, nor have I checked the Phoenix mailing list archives.

 The proposed LICENSE file looks OK.  It is not necessary to embed the
 complete
 text for MIT, 2-clause BSD and 3-clause BSD -- pointers suffice -- but it
 is
 not forbidden, either.

 The proposed NOTICE file contains a bunch of extraneous copyright notices.
 Their presence in NOTICE constitutes a licensing documentation bug and they
 should be removed.  See the licensing how-to, as well as this mail for
 additional explanation:

 http://markmail.org/message/shez7ys3qnnewl4a

 Because the file is named NOTICE, people tend to think it's for
 anything
 notice-ish. This is a pernicious misconception which keeps coming back
 over and over like a weed...

 Best,

 Marvin Humphrey

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

Re: [VOTE] Release of Apache Phoenix 3.0.0 incubating RC1

[James Taylor]

Marvin -
The one example in that email thread (airavata), has a bunch of copyright
notices in there NOTICE file:
https://github.com/apache/airavata/blob/master/modules/distribution/airavata-server/src/main/resources/NOTICE

Is that correct or incorrect?

I think the reason this comes up a lot is because most of us are software
developers, not IP lawyers. My interpretation of the license howto is that
you include the copyright info, since those bits are bundled in our binary
distribution and their original NOTICE files are no longer present. Is that
the incorrect way to interpret this:

Copyright notifications which have been
relocatedhttp://www.apache.org/legal/src-headers.html#headers from
source files (rather than removed) must be preserved in NOTICE. However,
elements such as the copyright notifications embedded within BSD and MIT
licenses need https://issues.apache.org/jira/browse/LEGAL-59
nothttps://issues.apache.org/jira/browse/LEGAL-62 be
duplicated in NOTICE -- it suffices to leave those notices in their
original locations.
When I read the Apache 2.0, BSD 2-clause, BSD 3-clause, and MIT licenses,
they all state this:
* Redistributions of source code must retain the above copyright
  notice, this list of conditions and the following disclaimer.

Doesn't that mean that the copyright notice is required? Again, I'm an
engineers, so I'm not sure how to interpret this language. I'm just trying
to get a release out.

Thanks,
James



On Wed, Mar 26, 2014 at 3:04 PM, James Taylor jamestay...@apache.orgwrote:

 Thanks, Marvin. So remove the copyrights from NOTICE. Are they required
 anywhere then, as their not in the LICENSE file?


 On Wed, Mar 26, 2014 at 2:57 PM, Marvin Humphrey 
 mar...@rectangular.comwrote:

 On Wed, Mar 26, 2014 at 12:59 PM, James Taylor jamestay...@apache.org
 wrote:
  Below is our updated NOTICE (which includes the copyright for the
 bundled
  bits) and LICENSE (minus the standard Apache 2.0 part).
 
  Would appreciate a review.

 What follows is a superficial review of what I see in this email thread
 -- I
 have not checked the distribution to see whether or not bits are actually
 bundled, nor have I checked the Phoenix mailing list archives.

 The proposed LICENSE file looks OK.  It is not necessary to embed the
 complete
 text for MIT, 2-clause BSD and 3-clause BSD -- pointers suffice -- but it
 is
 not forbidden, either.

 The proposed NOTICE file contains a bunch of extraneous copyright notices.
 Their presence in NOTICE constitutes a licensing documentation bug and
 they
 should be removed.  See the licensing how-to, as well as this mail for
 additional explanation:

 http://markmail.org/message/shez7ys3qnnewl4a

 Because the file is named NOTICE, people tend to think it's for
 anything
 notice-ish. This is a pernicious misconception which keeps coming back
 over and over like a weed...

 Best,

 Marvin Humphrey

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

[DISCUSS] Where does copyright information go for a binary distribution?

[James Taylor]

Hello,
I'm getting a release ready for Apache Phoenix (incubating) and have a
question about where copyright information should go for our binary
distribution. It seems that there's quite a bit of variation, as all
projects are different. So I'll describe our binary distribution, and
perhaps others who have a similar situation can learn from this.

Our binary distribution bundles numerous modules with the following
licenses:
1) Apache 2 licensed bits whose home is the ASF
2) Apache 2 licensed bits whose home is not the ASF
3) BSD Clause 3 licensed bits
4) BSD 2-Clause licensed bits
5) MIT licensed bits

We bundle all these bits together into a single jar, so the original NOTICE
from these bundled modules is no longer present.

Is the follow the correct way to do this?
a) Create a LICENSE file that includes the Apache 2 license text
b) Since all of the bits we bundle have permissive licenses, we do not
include anything extra in our NOTICE file. It'll be the bare minimum as
outlined here: http://www.apache.org/dev/licensing-howto.html#simple
c) Instead, we append to our LICENSE file the following for each module
that we bundle (including transitive dependencies):
   i) the copyright information for the module
   ii) a link to the license text

Below is an example (minus the standard Apache 2 license).

Please let me know if we're doing this correctly.

Thanks,
James
-
Apache 2.0 license text here

The Apache License, Version 2.0, also applies to the following bundled
libraries:

JAnsi, version 1.11, http://jansi.fusesource.org/
Copyright (c) 2009-2013 FuseSource, Corp

HawtJNI, version 1.8, http://fusesource.com/forge/sites/hawtjni/
Copyright (C) 2009-2011 FuseSource Corp.

Jackson, version 1.8.8, http://jackson.codehaus.org/
Copyright (c) 2007- Tatu Saloranta, tatu.salora...@iki.fi

Guava, version 12.0.1, http://code.google.com/p/guava-libraries/
Copyright 2008 Google Inc.

==

BSD Clause 3/New BSD License, applies to the following bundled libraries:
LICENSE: http://opensource.org/licenses/BSD-3-Clause

Snappy, version 1.1.0.1, http://code.google.com/p/snappy/
Copyright 2008 Google Inc.

Protobuf, version 2.4.0, https://code.google.com/p/protobuf/
Copyright 2008 Google Inc.

SQLLine, version 1.1.2, https://github.com/julianhyde/sqlline/
Copyright (c) 2002,2003,2004,2005,2006,2007 Marc Prud'hommeaux
Copyright (c) 2004-2010 The Eigenbase Project
Copyright (c) 2013-2014 Julian Hyde

==

BSD Clause 2 License, applies to the following bundled libraries:
LICENSE: http://opensource.org/licenses/BSD-2-Clause

JLine, version 2.11, http://jline.sourceforge.net/
Copyright (c) 2002-2007, Marc Prud'hommeaux m...@cornell.edu

ANTLR, version 3.5, http://www.antlr.org/
Copyright (c) 2003-2008, Terrence Parr.

==

MIT License, applies to the following bundled library:
LICENSE: http://opensource.org/licenses/MIT

SLF4J, version 1.4.3, http://www.slf4j.org/
Copyright (c) 2004-2008 QOS.ch

--

Re: [VOTE] Release of Apache Phoenix 3.0.0 incubating RC1

[James Taylor]

Thanks, Sebb. I added the version info and the copyright to the LICENSE
file and based on feedback from Marvin removed the copyright info from our
NOTICE file. See this thread:
http://mail-archives.apache.org/mod_mbox/incubator-general/201403.mbox/%3CCAAF1JdgvRpJXBetp9xCgOfE7CEwvnaVcxeE%3D-q3mNMRQqC2vTA%40mail.gmail.com%3E




On Wed, Mar 26, 2014 at 5:38 PM, sebb seb...@gmail.com wrote:

 On 26 March 2014 19:59, James Taylor jamestay...@apache.org wrote:
  Below is our updated NOTICE (which includes the copyright for the bundled
  bits) and LICENSE (minus the standard Apache 2.0 part).
 
  Would appreciate a review.
 
  Thanks,
  James
 
  * NOTICE **
 
  Apache Phoenix (Incubating)
  Copyright 2014 The Apache Software Foundation
 
  This product includes software developed at
  The Apache Software Foundation (http://www.apache.org/).
 
  In addition, this product includes the following software:

 The following lines are almost certainly not necessary.

  JLine (http://jline.sourceforge.net/),
  Copyright (c) 2002-2007, Marc Prud'hommeaux m...@cornell.edu
 
  SQLLine (https://github.com/julianhyde/sqlline/),
  Copyright (c) 2002,2003,2004,2005,2006,2007 Marc Prud'hommeaux
  Copyright (c) 2004-2010 The Eigenbase Project
  Copyright (c) 2013-2014 Julian Hyde
 
  SLF4J (http://www.slf4j.org/),
  Copyright (c) 2004-2008 QOS.ch
 
  ANTLR (http://www.antlr.org/),
  Copyright (c) 2003-2008, Terrence Parr.
 
  Snappy (http://code.google.com/p/snappy/)
  Copyright 2008 Google Inc.
 
  JAnsi (http://jansi.fusesource.org/)
  Copyright (c) 2009-2013 FuseSource, Corp
 
  HawtJNI (http://fusesource.com/forge/sites/hawtjni/)
  Copyright (C) 2009-2011 FuseSource Corp.
 
  Jackson (http://jackson.codehaus.org/)
  Copyright (c) 2007- Tatu Saloranta, tatu.salora...@iki.fi
 
  Protobuf (https://code.google.com/p/protobuf/)
  Copyright 2008 Google Inc.
 
  Guava (http://code.google.com/p/guava-libraries/)
  Copyright 2008 Google Inc.
 
 
  * LICENSE *
 
  The Apache License, Version 2.0, also applies to the following bundled
  libraries:

 As already mentioned elsethread - and in the web-page - please quote
 the VERSIONS of the bundled software.
 Licenses may change between versions.

  JAnsi, http://jansi.fusesource.org/
  HawtJNI, http://fusesource.com/forge/sites/hawtjni/
  Jackson, http://jackson.codehaus.org/
  Guava, http://code.google.com/p/guava-libraries/
 
  ==
 
  BSD Clause 3/New BSD License, applies to the following bundled libraries:

 Again, VERSIONS are needed

  Snappy, http://code.google.com/p/snappy/
  Protobuf, https://code.google.com/p/protobuf/
  SQLLine, https://github.com/julianhyde/sqlline/
 
  Full license included below:
 
  --
 
  BSD Clause 3/New BSD License
 
  Redistribution and use in source and binary forms, with or without
  modification, are permitted provided that the following conditions are
 met:
  * Redistributions of source code must retain the above copyright
notice, this list of conditions and the following disclaimer.
  * Redistributions in binary form must reproduce the above copyright
notice, this list of conditions and the following disclaimer in the
documentation and/or other materials provided with the
 distribution.
  * Neither the name of the organization nor the
names of its contributors may be used to endorse or promote
 products
derived from this software without specific prior written
 permission.
 
  THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS AS
 IS
  AND
  ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
  IMPLIED
  WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE
  DISCLAIMED. IN NO EVENT SHALL COPYRIGHT HOLDER BE LIABLE FOR ANY
  DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
 DAMAGES
  (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR
 SERVICES;
  LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED
 AND
  ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR
 TORT
  (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF
  THIS
  SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
 
  ==
 
  BSD Clause 2 License, applies to the following bundled libraries:
 

 Again, VERSIONS are needed

  JLine, http://jline.sourceforge.net/
  ANTLR, http://www.antlr.org/
 
  Full license included below:
 
  --
 
  The BSD 2-Clause License
 
  Redistribution and use in source and binary forms, with or without
  modification,
  are permitted provided that the following conditions are met:
 
  1

Re: [DISCUSS] Where does copyright information go for a binary distribution?

[James Taylor]

Where does the copyright information go in our case?


On Wed, Mar 26, 2014 at 5:48 PM, sebb seb...@gmail.com wrote:

 On 26 March 2014 23:55, James Taylor jamestay...@apache.org wrote:
  Hello,
  I'm getting a release ready for Apache Phoenix (incubating) and have a
  question about where copyright information should go for our binary
  distribution. It seems that there's quite a bit of variation, as all
  projects are different. So I'll describe our binary distribution, and
  perhaps others who have a similar situation can learn from this.
 
  Our binary distribution bundles numerous modules with the following
  licenses:
  1) Apache 2 licensed bits whose home is the ASF
  2) Apache 2 licensed bits whose home is not the ASF
  3) BSD Clause 3 licensed bits
  4) BSD 2-Clause licensed bits
  5) MIT licensed bits
 
  We bundle all these bits together into a single jar, so the original
 NOTICE
  from these bundled modules is no longer present.
 
  Is the follow the correct way to do this?
  a) Create a LICENSE file that includes the Apache 2 license text

 +1

  b) Since all of the bits we bundle have permissive licenses, we do not
  include anything extra in our NOTICE file. It'll be the bare minimum as
  outlined here: http://www.apache.org/dev/licensing-howto.html#simple

 Not necessarily, that depends on what is present in the NOTICE/LICENSE
 files that are included in the bundled jars.

 NOTICE files in particular must be examined to see if they contain
 attributions that apply to the bits you are bundling.
 In which case the attributions must be carried forward into the new NOTICE
 file

 This is all described here:

 http://www.apache.org/dev/licensing-howto.html#alv2-dep (et seq.)

  c) Instead, we append to our LICENSE file the following for each module
  that we bundle (including transitive dependencies):
 i) the copyright information for the module
 ii) a link to the license text

 LICENSE and NOTICE are not alternates.

 LICENSE files have to contain licenses/pointers for ALL bundled bits.

 NOTICE files have to contain required attributions only.

  Below is an example (minus the standard Apache 2 license).
 
  Please let me know if we're doing this correctly.
 
  Thanks,
  James
  -
  Apache 2.0 license text here
 
  The Apache License, Version 2.0, also applies to the following bundled
  libraries:
 
  JAnsi, version 1.11, http://jansi.fusesource.org/
  Copyright (c) 2009-2013 FuseSource, Corp
 
  HawtJNI, version 1.8, http://fusesource.com/forge/sites/hawtjni/
  Copyright (C) 2009-2011 FuseSource Corp.
 
  Jackson, version 1.8.8, http://jackson.codehaus.org/
  Copyright (c) 2007- Tatu Saloranta, tatu.salora...@iki.fi
 
  Guava, version 12.0.1, http://code.google.com/p/guava-libraries/
  Copyright 2008 Google Inc.
 
  ==
 
  BSD Clause 3/New BSD License, applies to the following bundled libraries:
  LICENSE: http://opensource.org/licenses/BSD-3-Clause
 
  Snappy, version 1.1.0.1, http://code.google.com/p/snappy/
  Copyright 2008 Google Inc.
 
  Protobuf, version 2.4.0, https://code.google.com/p/protobuf/
  Copyright 2008 Google Inc.
 
  SQLLine, version 1.1.2, https://github.com/julianhyde/sqlline/
  Copyright (c) 2002,2003,2004,2005,2006,2007 Marc Prud'hommeaux
  Copyright (c) 2004-2010 The Eigenbase Project
  Copyright (c) 2013-2014 Julian Hyde
 
  ==
 
  BSD Clause 2 License, applies to the following bundled libraries:
  LICENSE: http://opensource.org/licenses/BSD-2-Clause
 
  JLine, version 2.11, http://jline.sourceforge.net/
  Copyright (c) 2002-2007, Marc Prud'hommeaux m...@cornell.edu
 
  ANTLR, version 3.5, http://www.antlr.org/
  Copyright (c) 2003-2008, Terrence Parr.
 
  ==
 
  MIT License, applies to the following bundled library:
  LICENSE: http://opensource.org/licenses/MIT
 
  SLF4J, version 1.4.3, http://www.slf4j.org/
  Copyright (c) 2004-2008 QOS.ch
 
  --

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

Re: [DISCUSS] Where does copyright information go for a binary distribution?

[James Taylor]

The copyright for the bits we're bundling. See the LICENSE file I included
at the end of my email. For example:

Guava, version 12.0.1, http://code.google.com/p/guava-libraries/
Copyright 2008 Google Inc.

Is that the correct way to include the Copyright? Or is this not required?

Also, how do I know if something is a required attributions?


On Wed, Mar 26, 2014 at 6:02 PM, sebb seb...@gmail.com wrote:

 On 27 March 2014 00:52, James Taylor jamestay...@apache.org wrote:
  Where does the copyright information go in our case?

 What copyright information?
 Where was it originally?

 
  On Wed, Mar 26, 2014 at 5:48 PM, sebb seb...@gmail.com wrote:
 
  On 26 March 2014 23:55, James Taylor jamestay...@apache.org wrote:
   Hello,
   I'm getting a release ready for Apache Phoenix (incubating) and have a
   question about where copyright information should go for our binary
   distribution. It seems that there's quite a bit of variation, as all
   projects are different. So I'll describe our binary distribution, and
   perhaps others who have a similar situation can learn from this.
  
   Our binary distribution bundles numerous modules with the following
   licenses:
   1) Apache 2 licensed bits whose home is the ASF
   2) Apache 2 licensed bits whose home is not the ASF
   3) BSD Clause 3 licensed bits
   4) BSD 2-Clause licensed bits
   5) MIT licensed bits
  
   We bundle all these bits together into a single jar, so the original
  NOTICE
   from these bundled modules is no longer present.
  
   Is the follow the correct way to do this?
   a) Create a LICENSE file that includes the Apache 2 license text
 
  +1
 
   b) Since all of the bits we bundle have permissive licenses, we do
 not
   include anything extra in our NOTICE file. It'll be the bare minimum
 as
   outlined here: http://www.apache.org/dev/licensing-howto.html#simple
 
  Not necessarily, that depends on what is present in the NOTICE/LICENSE
  files that are included in the bundled jars.
 
  NOTICE files in particular must be examined to see if they contain
  attributions that apply to the bits you are bundling.
  In which case the attributions must be carried forward into the new
 NOTICE
  file
 
  This is all described here:
 
  http://www.apache.org/dev/licensing-howto.html#alv2-dep (et seq.)
 
   c) Instead, we append to our LICENSE file the following for each
 module
   that we bundle (including transitive dependencies):
  i) the copyright information for the module
  ii) a link to the license text
 
  LICENSE and NOTICE are not alternates.
 
  LICENSE files have to contain licenses/pointers for ALL bundled bits.
 
  NOTICE files have to contain required attributions only.
 
   Below is an example (minus the standard Apache 2 license).
  
   Please let me know if we're doing this correctly.
  
   Thanks,
   James
   -
   Apache 2.0 license text here
  
   The Apache License, Version 2.0, also applies to the following bundled
   libraries:
  
   JAnsi, version 1.11, http://jansi.fusesource.org/
   Copyright (c) 2009-2013 FuseSource, Corp
  
   HawtJNI, version 1.8, http://fusesource.com/forge/sites/hawtjni/
   Copyright (C) 2009-2011 FuseSource Corp.
  
   Jackson, version 1.8.8, http://jackson.codehaus.org/
   Copyright (c) 2007- Tatu Saloranta, tatu.salora...@iki.fi
  
   Guava, version 12.0.1, http://code.google.com/p/guava-libraries/
   Copyright 2008 Google Inc.
  
   ==
  
   BSD Clause 3/New BSD License, applies to the following bundled
 libraries:
   LICENSE: http://opensource.org/licenses/BSD-3-Clause
  
   Snappy, version 1.1.0.1, http://code.google.com/p/snappy/
   Copyright 2008 Google Inc.
  
   Protobuf, version 2.4.0, https://code.google.com/p/protobuf/
   Copyright 2008 Google Inc.
  
   SQLLine, version 1.1.2, https://github.com/julianhyde/sqlline/
   Copyright (c) 2002,2003,2004,2005,2006,2007 Marc Prud'hommeaux
   Copyright (c) 2004-2010 The Eigenbase Project
   Copyright (c) 2013-2014 Julian Hyde
  
   ==
  
   BSD Clause 2 License, applies to the following bundled libraries:
   LICENSE: http://opensource.org/licenses/BSD-2-Clause
  
   JLine, version 2.11, http://jline.sourceforge.net/
   Copyright (c) 2002-2007, Marc Prud'hommeaux m...@cornell.edu
  
   ANTLR, version 3.5, http://www.antlr.org/
   Copyright (c) 2003-2008, Terrence Parr.
  
   ==
  
   MIT License, applies to the following bundled library:
   LICENSE: http://opensource.org/licenses/MIT
  
   SLF4J, version 1.4.3, http://www.slf4j.org/
   Copyright (c) 2004-2008 QOS.ch
  
   --
 
  -
  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
  For additional commands, e-mail

[VOTE] Release of Apache Phoenix 3.0.0 incubating RC1

[James Taylor]

Hi everyone,
This is a call for a vote on Apache Phoenix 3.0.0 incubating RC1. Phoenix
is a SQL query engine for Apache HBase, a NoSQL data store. It is accessed
as a JDBC driver and enables querying and managing HBase tables using SQL. This
is the next major release of Phoenix compatible with the 0.94 branch of
Apache HBase and will be our second release in the incubator. The release
includes both a source-only release and a convenience binary release.

New features include:
- Equi-joins through broadcast hash join
- Shared tables over same physical HBase table
- Read-only and updatable views
- Multi-tenancy
- JDBC ARRAY type
- Sequence creation and usage

The dev list thread for the passing vote (10 +1s with 3 IPMC votes) can be
found at:
http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201403.mbox/%3CCAAF1Jdg4x1Fo6xtX%3DEzWiGrQsxLkgGUJTAm7Dcb-M8NTR9MJgw%40mail.gmail.com%3E

The source tarball, including signatures, digests, etc can be found at:
https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-3.0.0-incubating-rc1/src/

The binary artifacts can be found at:
https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-3.0.0-incubating-rc1/bin/

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

KEYS file available here:
https://dist.apache.org/repos/dist/dev/incubator/phoenix/KEYS

The tag to be voted upon:
https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=tag;h=refs/tags/v3.0.0-incubating-rc1

For information about the contents of this release see:
https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=log;h=refs/tags/v3.0.0-incubating-rc1

Release notes
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12326145styleName=TextprojectId=12315120Create=Createatl_token=A5KQ-2QAV-T4JA-FDED%7C34a706e780c7e8f198c9ca903e80572b560599b6%7Clin

Vote will be open for at least 72 hours. Please vote:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
James

[VOTE] Release of Apache Phoenix 4.0.0 incubating RC1

[James Taylor]

Hi everyone,
This is a call for a vote on Apache Phoenix 4.0.0 incubating RC1. Phoenix
is a SQL query engine for Apache HBase, a NoSQL data store. It is accessed
as a JDBC driver and enables querying and managing HBase tables using SQL. This
is the next major release of Phoenix compatible with the 0.98 branch of
Apache HBase (0.98.1+) and will be our third release in the incubator. The
release includes both a source-only release and a convenience binary
release.

The 4.0.0 release has feature parity with our pending 3.0.0 release. New
features include:
- Equi-joins through broadcast hash join
- Shared tables over same physical HBase table
- Read-only and updatable views
- Multi-tenancy
- JDBC ARRAY type
- Sequence creation and usage

The dev list thread for the passing vote (9 +1s with 2 IPMC votes) can be
found at:
http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201403.mbox/%3CCAAF1JdiQaaWRzgwXF9d7XR%2B3jrv4OtSEFiQX%3DZfszfqz6L9REg%40mail.gmail.com%3E

The source tarball, including signatures, digests, etc can be found at:
https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-4.0.0-incubating-rc1/src/

The binary artifacts can be found at:
https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-4.0.0-incubating-rc1/bin/

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

KEYS file available here:
https://dist.apache.org/repos/dist/dev/incubator/phoenix/KEYS

The tag to be voted upon:
https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=tag;h=refs/tags/v4.0.0-incubating-rc1

For information about the contents of this release see:
https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=log;h=refs/tags/v4.0.0-incubating-rc1

Release notes
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12326145styleName=TextprojectId=12315120Create=Createatl_token=A5KQ-2QAV-T4JA-FDED%7C34a706e780c7e8f198c9ca903e80572b560599b6%7Clin

Vote will be open for at least 72 hours. Please vote:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
James

Re: [VOTE] Release of Apache Phoenix 3.0.0 incubating RC1

[James Taylor]

Thanks for the detailed review, Sebb. We really appreciate you spending
your time going through this. Here's the list of TODOs for us:
1) In the binary bundle:
a) Fix the copy/paste error for the URL to SQLLine in the NOTICE file
in the binary bundle as noted by Gabriel here[1].
   b) Change developed by to developed at in the NOTICE file
   c) In answer to your question, yes all those projects listed are bundled
with our binary distribution.
2) In the source bundle:
a) The target dir and rat.txt files should be removed from the src
bundle
b) There were the following changes made to the src bundle not
reflected in git:
  - the docs/phoenix.csv file was removed (it's part of our website so
should not be included in our git repo)
  - the build.txt file was modified slightly in the src bundle.
  - the CHANGES file is bundled with the src bundle, but not checked
into git.
 - the README.md file is not included in the src bundle, but instead a
README file is included instead.

For the source binary changes, we could commit and push those changes to
git and update our 3.0.0 tag. Would that be an acceptable solution?

Are there more changes necessary to the NOTICE file in the binary bundle?
Would it be acceptable to fix the URL in the next release? If not, would we
need to go through a dev vote again for the NOTICE file change?

FWIW, we'll automate the generation of our release bundles for our next
release (and make sure the source matches exactly as well).

Thanks,
James

[1]
http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201403.mbox/%3CCAA5C_puNoy74jniWMTbx%3DZFyc1itf0w6E4kCHvCOTK_OTfBgmg%40mail.gmail.com%3E


On Tue, Mar 25, 2014 at 3:16 PM, Andrew Purtell apurt...@apache.org wrote:

 James, Mujtaba, et. al.,

 Can we add a Releasing page to http://phoenix.incubator.apache.org/ that
 includes step by step instructions for packaging a Phoenix release. We can
 fine tune this process according to feedback received during RCs. This
 could/should include shell commands captured one time through your process
 for generating a source tarball from a Git checkout at an exact SHA, saving
 off a clean source tarball before running release checks, generating binary
 release tarballs, calculating checksums over the tarballs, signing the
 tarballs, etc.


 On Tue, Mar 25, 2014 at 3:09 PM, sebb seb...@gmail.com wrote:

  On 25 March 2014 22:01, Andrew Purtell apurt...@apache.org wrote:
   Pardon, got -bin and -src crossed mentally, indeed they are there.
  
   Looks like src was packaged after running the RAT check.  Does this
  require
   a new RC?
 
  If I were the RM I would respin the RC for this sort of packaging error.
 
  But in this case there are other more serious errors, the binary NOTICE
  file.
 
  And most important, please establish why the Git tag does not agree
  with the source archive, otherwise the new RC may also be faulty in
  that regard.
 
  It's vital that all files in the source bundle can be traced back to
  the source code control system.
 
   On Tue, Mar 25, 2014 at 2:59 PM, sebb seb...@gmail.com wrote:
  
   On 25 March 2014 21:56, Andrew Purtell apurt...@apache.org wrote:
On Tue, Mar 25, 2014 at 11:54 AM, sebb seb...@gmail.com wrote:
   
On 25 March 2014 16:39, James Taylor jamestay...@apache.org
 wrote:
[...]
   
 The source tarball, including signatures, digests, etc can be
 found
   at:

   
  
 
 https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-3.0.0-incubating-rc1/src/
   
The source bundle includes directories and files not in Git.
   
There should be no target directories in the source bundle, and
 no
Rat.txt files.
   
   
Where are those?
  
   In the source bundle.
  
$ wget
   
  
 
 https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-3.0.0-incubating-rc1/bin/phoenix-3.0.0-incubating.tar.gz
  
   That's the binary bundle.
 

 --
 Best regards,

- Andy

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

Re: [VOTE] Release of Apache Phoenix 4.0.0 incubating RC1

[James Taylor]

Yes, Henry - that's correct - two releases. The releases are functionally
equivalent, but support two different major versions of HBase.
Thanks,
James


On Tue, Mar 25, 2014 at 3:04 PM, Henry Saputra henry.sapu...@gmail.comwrote:

 Just clarifying that Phoenix is trying to do two releases (3.0.0 and
 4.0.0) at the same time?
 Or maybe my gmail thread history is messed up.

 - Henry

 On Tue, Mar 25, 2014 at 9:46 AM, James Taylor jamestay...@apache.org
 wrote:
  Hi everyone,
  This is a call for a vote on Apache Phoenix 4.0.0 incubating RC1. Phoenix
  is a SQL query engine for Apache HBase, a NoSQL data store. It is
 accessed
  as a JDBC driver and enables querying and managing HBase tables using
 SQL. This
  is the next major release of Phoenix compatible with the 0.98 branch of
  Apache HBase (0.98.1+) and will be our third release in the incubator.
 The
  release includes both a source-only release and a convenience binary
  release.
 
  The 4.0.0 release has feature parity with our pending 3.0.0 release. New
  features include:
  - Equi-joins through broadcast hash join
  - Shared tables over same physical HBase table
  - Read-only and updatable views
  - Multi-tenancy
  - JDBC ARRAY type
  - Sequence creation and usage
 
  The dev list thread for the passing vote (9 +1s with 2 IPMC votes) can be
  found at:
 
 http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201403.mbox/%3CCAAF1JdiQaaWRzgwXF9d7XR%2B3jrv4OtSEFiQX%3DZfszfqz6L9REg%40mail.gmail.com%3E
 
  The source tarball, including signatures, digests, etc can be found at:
 
 https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-4.0.0-incubating-rc1/src/
 
  The binary artifacts can be found at:
 
 https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-4.0.0-incubating-rc1/bin/
 
  Release artifacts are signed with the following key:
  https://people.apache.org/keys/committer/mujtaba.asc
 
  KEYS file available here:
  https://dist.apache.org/repos/dist/dev/incubator/phoenix/KEYS
 
  The tag to be voted upon:
 
 https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=tag;h=refs/tags/v4.0.0-incubating-rc1
 
  For information about the contents of this release see:
 
 https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=log;h=refs/tags/v4.0.0-incubating-rc1
 
  Release notes
 
 https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12326145styleName=TextprojectId=12315120Create=Createatl_token=A5KQ-2QAV-T4JA-FDED%7C34a706e780c7e8f198c9ca903e80572b560599b6%7Clin
 
  Vote will be open for at least 72 hours. Please vote:
 
  [ ] +1 approve
  [ ] +0 no opinion
  [ ] -1 disapprove (and reason why)
 
  Thanks,
  James

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

Re: [VOTE] Release of Apache Phoenix 3.0.0 incubating RC1

[James Taylor]

Our binary distribution bundles sqlline which has a BSD Clause 3 license.
We've included this license with the Apache 2 license in our LICENSE file.
Do we need to include sqlline in the NOTICE file?

Yes, we bundle ANTLR in our binary distribution. Most of the other items
are pulled in based on the transitive dependencies of other jars we've
bundled in our binary distribution. That's why we included them in the
NOTICE file. Is this correct?

Our LICENSE file includes the licenses of all bundled software - either
Apache 2 or BSD Clause 3.

Please advise, as we're trying to follow the guidelines listed here[1].

Thanks,
James

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



On Tue, Mar 25, 2014 at 3:48 PM, sebb seb...@gmail.com wrote:

 On 25 March 2014 22:27, James Taylor jamestay...@apache.org wrote:
  Thanks for the detailed review, Sebb. We really appreciate you spending
  your time going through this. Here's the list of TODOs for us:
  1) In the binary bundle:
  a) Fix the copy/paste error for the URL to SQLLine in the NOTICE file
  in the binary bundle as noted by Gabriel here[1].

 It's not clear to me that the SQLLine attribution should even be in
 the NOTICE file.
 Though of course if it must be included, the URL should be correct.

 b) Change developed by to developed at in the NOTICE file
 c) In answer to your question, yes all those projects listed are
 bundled
  with our binary distribution.

 Are you sure?
 Even JUnit and ANTLR?

 Even if they are included, that only means that a LICENSE file entry
 is needed, not necessarily a NOTICE entry.

  2) In the source bundle:
  a) The target dir and rat.txt files should be removed from the src
  bundle

 Yes.

  b) There were the following changes made to the src bundle not
  reflected in git:
- the docs/phoenix.csv file was removed (it's part of our website
 so
  should not be included in our git repo)

 OK

- the build.txt file was modified slightly in the src bundle.

 Not OK.

- the CHANGES file is bundled with the src bundle, but not checked
  into git.

 The source bundle must only contain files contained in the Git tag.

 The point is that the only practical way to ensure that the source
 bundle contains only files that have the appropriate license and are
 allowed to be included in a release is to compare the files with Git
 (or SVN). Otherwise it's impossible to establish provenance and
 difficult to determine if the file has a suitable license.

   - the README.md file is not included in the src bundle, but instead
 a
  README file is included instead.

 The ASF releases source, so source files to create documentation
 should be included.

  For the source binary changes, we could commit and push those changes to
  git and update our 3.0.0 tag. Would that be an acceptable solution?

 Not sure what you are proposing.

 The RC reviewers need to be able to check that the source bundle
 agrees with the tag.
 Also that the NOTICE and LICENSE files in the bundles agree with the
 contents of those bundles and that any bundled code can be released
 under the Apache License.

  Are there more changes necessary to the NOTICE file in the binary bundle?
  Would it be acceptable to fix the URL in the next release? If not, would
 we
  need to go through a dev vote again for the NOTICE file change?

 See above.

  FWIW, we'll automate the generation of our release bundles for our next
  release (and make sure the source matches exactly as well).

  Thanks,
  James
 
  [1]
 
 http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201403.mbox/%3CCAA5C_puNoy74jniWMTbx%3DZFyc1itf0w6E4kCHvCOTK_OTfBgmg%40mail.gmail.com%3E
 
 
  On Tue, Mar 25, 2014 at 3:16 PM, Andrew Purtell apurt...@apache.org
 wrote:
 
  James, Mujtaba, et. al.,
 
  Can we add a Releasing page to http://phoenix.incubator.apache.org/that
  includes step by step instructions for packaging a Phoenix release. We
 can
  fine tune this process according to feedback received during RCs. This
  could/should include shell commands captured one time through your
 process
  for generating a source tarball from a Git checkout at an exact SHA,
 saving
  off a clean source tarball before running release checks, generating
 binary
  release tarballs, calculating checksums over the tarballs, signing the
  tarballs, etc.
 
 
  On Tue, Mar 25, 2014 at 3:09 PM, sebb seb...@gmail.com wrote:
 
   On 25 March 2014 22:01, Andrew Purtell apurt...@apache.org wrote:
Pardon, got -bin and -src crossed mentally, indeed they are there.
   
Looks like src was packaged after running the RAT check.  Does this
   require
a new RC?
  
   If I were the RM I would respin the RC for this sort of packaging
 error.
  
   But in this case there are other more serious errors, the binary
 NOTICE
   file.
  
   And most important, please establish why the Git tag does not agree
   with the source archive, otherwise the new RC may also be faulty in
   that regard

Re: [VOTE] Release of Apache Phoenix 3.0.0 incubating RC1

[James Taylor]

Ah, I see. Thanks, Sebb. So we should modify our LICENSE file as indicated
in http://www.apache.org/dev/licensing-howto.html#permissive-deps instead
of listing these in our LICENSE file. Since all licenses are either Apache
or BSD, this should be fine.

I'm still a bit confused about one thing, though. The above link says add
a pointer to the dependency's location within the source tree. For
sqlline, we bundle it, but have no source dependencies on it. It's used as
a command line terminal interface. Is this pointer optional then? We could
point to the python script that invokes it - would that be correct?

For our HBase dependencies, we have many places in the source that call
HBase APIs. Do we just list one of them?


On Tue, Mar 25, 2014 at 4:25 PM, sebb seb...@gmail.com wrote:

 On 25 March 2014 23:06, James Taylor jamestay...@apache.org wrote:
  Our binary distribution bundles sqlline which has a BSD Clause 3 license.
  We've included this license with the Apache 2 license in our LICENSE
 file.
  Do we need to include sqlline in the NOTICE file?

 Depends on its license.

  Yes, we bundle ANTLR in our binary distribution. Most of the other items
  are pulled in based on the transitive dependencies of other jars we've
  bundled in our binary distribution.

 I see now why I did not notice the 3rd party binaries.
 They seem to have been merged into jars which look like phoenix code -
 and indeed also contain phoenix code.

 That is a very non-standard way to do things, and I think could
 mislead end-users as to the provenance of the code.

 It's OK to bundle separate jars in a binary release (assuming
 licensing etc is OK), but I don't think it's OK to merge 3rd party
 code with ASF code in a single jar.
 Apart from anything, that will play havoc with Maven and possibly
 other dependency management systems.

  That's why we included them in the NOTICE file. Is this correct?

 As I already wrote, not necessarily.
 You can only include certain license types; in all cases the licenses
 must be included in the bundle - either actually included in the
 LICENSE file or locally linked from it.
 Some licenses may require attribution in the NOTICE file.

 See for example

 http://www.apache.org/dev/licensing-howto.html#permissive-deps

  Our LICENSE file includes the licenses of all bundled software - either
  Apache 2 or BSD Clause 3.

 But there is no indication as to which 3rd party software uses what
 license.

 again, see

 http://www.apache.org/dev/licensing-howto.html#permissive-deps

  Please advise, as we're trying to follow the guidelines listed here[1].

 As am I ...

  Thanks,
  James
 
  [1] http://www.apache.org/dev/licensing-howto.html
 
 
 
  On Tue, Mar 25, 2014 at 3:48 PM, sebb seb...@gmail.com wrote:
 
  On 25 March 2014 22:27, James Taylor jamestay...@apache.org wrote:
   Thanks for the detailed review, Sebb. We really appreciate you
 spending
   your time going through this. Here's the list of TODOs for us:
   1) In the binary bundle:
   a) Fix the copy/paste error for the URL to SQLLine in the NOTICE
 file
   in the binary bundle as noted by Gabriel here[1].
 
  It's not clear to me that the SQLLine attribution should even be in
  the NOTICE file.
  Though of course if it must be included, the URL should be correct.
 
  b) Change developed by to developed at in the NOTICE file
  c) In answer to your question, yes all those projects listed are
  bundled
   with our binary distribution.
 
  Are you sure?
  Even JUnit and ANTLR?
 
  Even if they are included, that only means that a LICENSE file entry
  is needed, not necessarily a NOTICE entry.
 
   2) In the source bundle:
   a) The target dir and rat.txt files should be removed from the src
   bundle
 
  Yes.
 
   b) There were the following changes made to the src bundle not
   reflected in git:
 - the docs/phoenix.csv file was removed (it's part of our
 website
  so
   should not be included in our git repo)
 
  OK
 
 - the build.txt file was modified slightly in the src bundle.
 
  Not OK.
 
 - the CHANGES file is bundled with the src bundle, but not
 checked
   into git.
 
  The source bundle must only contain files contained in the Git tag.
 
  The point is that the only practical way to ensure that the source
  bundle contains only files that have the appropriate license and are
  allowed to be included in a release is to compare the files with Git
  (or SVN). Otherwise it's impossible to establish provenance and
  difficult to determine if the file has a suitable license.
 
- the README.md file is not included in the src bundle, but
 instead
  a
   README file is included instead.
 
  The ASF releases source, so source files to create documentation
  should be included.
 
   For the source binary changes, we could commit and push those changes
 to
   git and update our 3.0.0 tag. Would that be an acceptable solution?
 
  Not sure what you are proposing.
 
  The RC reviewers need

Re: [VOTE] Release of Apache Phoenix 3.0.0 incubating RC1

[James Taylor]

(sorry, meant instead of listing these in our NOTICE file)


On Tue, Mar 25, 2014 at 4:48 PM, James Taylor jamestay...@apache.orgwrote:

 Ah, I see. Thanks, Sebb. So we should modify our LICENSE file as indicated
 in http://www.apache.org/dev/licensing-howto.html#permissive-deps instead
 of listing these in our LICENSE file. Since all licenses are either Apache
 or BSD, this should be fine.

 I'm still a bit confused about one thing, though. The above link says add
 a pointer to the dependency's location within the source tree. For
 sqlline, we bundle it, but have no source dependencies on it. It's used as
 a command line terminal interface. Is this pointer optional then? We could
 point to the python script that invokes it - would that be correct?

 For our HBase dependencies, we have many places in the source that call
 HBase APIs. Do we just list one of them?


 On Tue, Mar 25, 2014 at 4:25 PM, sebb seb...@gmail.com wrote:

 On 25 March 2014 23:06, James Taylor jamestay...@apache.org wrote:
  Our binary distribution bundles sqlline which has a BSD Clause 3
 license.
  We've included this license with the Apache 2 license in our LICENSE
 file.
  Do we need to include sqlline in the NOTICE file?

 Depends on its license.

  Yes, we bundle ANTLR in our binary distribution. Most of the other items
  are pulled in based on the transitive dependencies of other jars we've
  bundled in our binary distribution.

 I see now why I did not notice the 3rd party binaries.
 They seem to have been merged into jars which look like phoenix code -
 and indeed also contain phoenix code.

 That is a very non-standard way to do things, and I think could
 mislead end-users as to the provenance of the code.

 It's OK to bundle separate jars in a binary release (assuming
 licensing etc is OK), but I don't think it's OK to merge 3rd party
 code with ASF code in a single jar.
 Apart from anything, that will play havoc with Maven and possibly
 other dependency management systems.

  That's why we included them in the NOTICE file. Is this correct?

 As I already wrote, not necessarily.
 You can only include certain license types; in all cases the licenses
 must be included in the bundle - either actually included in the
 LICENSE file or locally linked from it.
 Some licenses may require attribution in the NOTICE file.

 See for example

 http://www.apache.org/dev/licensing-howto.html#permissive-deps

  Our LICENSE file includes the licenses of all bundled software - either
  Apache 2 or BSD Clause 3.

 But there is no indication as to which 3rd party software uses what
 license.

 again, see

 http://www.apache.org/dev/licensing-howto.html#permissive-deps

  Please advise, as we're trying to follow the guidelines listed here[1].

 As am I ...

  Thanks,
  James
 
  [1] http://www.apache.org/dev/licensing-howto.html
 
 
 
  On Tue, Mar 25, 2014 at 3:48 PM, sebb seb...@gmail.com wrote:
 
  On 25 March 2014 22:27, James Taylor jamestay...@apache.org wrote:
   Thanks for the detailed review, Sebb. We really appreciate you
 spending
   your time going through this. Here's the list of TODOs for us:
   1) In the binary bundle:
   a) Fix the copy/paste error for the URL to SQLLine in the NOTICE
 file
   in the binary bundle as noted by Gabriel here[1].
 
  It's not clear to me that the SQLLine attribution should even be in
  the NOTICE file.
  Though of course if it must be included, the URL should be correct.
 
  b) Change developed by to developed at in the NOTICE file
  c) In answer to your question, yes all those projects listed are
  bundled
   with our binary distribution.
 
  Are you sure?
  Even JUnit and ANTLR?
 
  Even if they are included, that only means that a LICENSE file entry
  is needed, not necessarily a NOTICE entry.
 
   2) In the source bundle:
   a) The target dir and rat.txt files should be removed from the
 src
   bundle
 
  Yes.
 
   b) There were the following changes made to the src bundle not
   reflected in git:
 - the docs/phoenix.csv file was removed (it's part of our
 website
  so
   should not be included in our git repo)
 
  OK
 
 - the build.txt file was modified slightly in the src bundle.
 
  Not OK.
 
 - the CHANGES file is bundled with the src bundle, but not
 checked
   into git.
 
  The source bundle must only contain files contained in the Git tag.
 
  The point is that the only practical way to ensure that the source
  bundle contains only files that have the appropriate license and are
  allowed to be included in a release is to compare the files with Git
  (or SVN). Otherwise it's impossible to establish provenance and
  difficult to determine if the file has a suitable license.
 
- the README.md file is not included in the src bundle, but
 instead
  a
   README file is included instead.
 
  The ASF releases source, so source files to create documentation
  should be included.
 
   For the source binary changes, we could commit and push those

Re: [VOTE] Release of Apache Phoenix 3.0.0 incubating RC1

[James Taylor]

On Tue, Mar 25, 2014 at 5:07 PM, sebb seb...@gmail.com wrote:


 HBase is ASF code surely?
 So why does it need mentioning? - unless its NOTICE file has some
 attributions that relate to what you are bundling


Yes, HBase is ASF code. The other stuff we've listed are the transitive
dependencies of HBase. Do we list then only the non ASF transitive
dependencies in our LICENSE file? I think I was confused by the
http://www.apache.org/dev/licensing-howto.html#deps-of-deps instructions.

Would it be ok if I attached a modified LICENSE file for review here? Our
NOTICE file will be modified to include only the bare minimum as described
here: http://www.apache.org/dev/licensing-howto.html#simple

Thanks,
James

Re: [VOTE] Release of Apache Phoenix 3.0.0 incubating RC1

[James Taylor]

On Tue, Mar 25, 2014 at 5:28 PM, sebb seb...@gmail.com wrote:

 On 26 March 2014 00:23, James Taylor jamestay...@apache.org wrote:
  I think I was confused by the
  http://www.apache.org/dev/licensing-howto.html#deps-of-depsinstructions.

 What is confusing about that?
 If it is not clear, how could it be made clearer?

 The instructions are clear. It's just not simple to get right. Maybe it's
just one of those things you have to do wrong once. Maybe a simple
end-2-end example would help for a example project with both:
- a non ASF dependency and
- an ASF dependency that include a non ASF dependency

Re: [VOTE] Release of Apache Phoenix 3.0.0 incubating RC1

[James Taylor]

On Tue, Mar 25, 2014 at 5:35 PM, Andrew Purtell apurt...@apache.org wrote:

 On Tue, Mar 25, 2014 at 4:25 PM, sebb seb...@gmail.com wrote:

   Yes, we bundle ANTLR in our binary distribution. Most of the other
 items
   are pulled in based on the transitive dependencies of other jars we've
   bundled in our binary distribution.
 
  I see now why I did not notice the 3rd party binaries.
  They seem to have been merged into jars which look like phoenix code -
  and indeed also contain phoenix code.
 
  That is a very non-standard way to do things, and I think could
  mislead end-users as to the provenance of the code.
 
  It's OK to bundle separate jars in a binary release (assuming
  licensing etc is OK), but I don't think it's OK to merge 3rd party
  code with ASF code in a single jar.
  Apart from anything, that will play havoc with Maven and possibly
  other dependency management systems.


 I believe this is done because Phoenix is a JDBC client, and JDBC drivers
 are usually packaged as single JARs for convenience. James could confirm or
 refute. I concluded this is acceptable practice having seen it elsewhere at
 Apache, for example in Apache Pig, their convenience fatjar artifact.

 Yes, that's correct. It's because then a third-party tool (such as a SQL
client GUI) then only need to pull in a single jar to be able to connect
through the Phoenix JDBC driver to HBase. Our initial (pre-Apache) releases
didn't do this and it was almost impossible to get the classpath correct
for the minimal client-side dependencies.

So the remaining question: should we spin up a new RC for these changes and
if so, should we go through a vote again on our dev list as well?

Thanks again for all the help.

James

[ANNOUNCE] Apache Phoenix 2.2.3-incubating released

[James Taylor]

Hello,

The Apache Phoenix team is pleased to announce the release of version
2.2.3-incubating from the Apache Incubator. Phoenix is a SQL query engine
for Apache HBase, a NoSQL data store. It is accessed as a JDBC driver and
enables querying and managing HBase tables using SQL.

The source and binaries for the release may be downloaded here:
http://phoenix.incubator.apache.org/download.html

Link to release notes:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12325748styleName=TextprojectId=12315120Create=Createatl_token=A5KQ-2QAV-T4JA-FDED%7Ca7a6d3045efbe3f42c7483fd29510c92a7227195%7Clout

For general information on Apache Phoenix, please visit the project website:
http://phoenix.incubator.apache.org/index.html

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

Regards,
The Apache Phoenix team

[RESULT][VOTE] Release of Apache Phoenix 2.2.3 incubating RC4

[James Taylor]

Voting is now closed. This vote passes with 4 binding +1 votes and no 0
or -1 votes. Thank you to everyone who voted. Totals:

+1:
Michael Stack *
Henry Saputra *
Enis Söztutar *
Andrew Purtell *

0:

-1:

* = binding

Thanks,
James

On Thu, Mar 13, 2014 at 8:58 AM, Henry Saputra henry.sapu...@gmail.comwrote:

 Hi Enis, thx for the Vote.

 There was already commitment from James to fix the disclaimer so I would
 not think this should be a release blocker.

 Thx,

 Henry

 On Wednesday, March 12, 2014, Enis Söztutar enis@gmail.com wrote:

  +1 (binding).
 
  - Checked the src and binary artifacts.
  - Checked sigs
  - Checked CRCs
  - Built the src artifacts
 
  If the DISCLAIMER file will not sink the RC, lets go ahead with releasing
  this. Otherwise we would need a new RC.
 
  Enis
 
 
  On Tue, Mar 11, 2014 at 11:11 AM, James Taylor jamestay...@apache.org
 javascript:;
  wrote:
 
   Thanks, Marvin. We'll update this in our next release too, as we'd like
  to
   follow the preferred path.
  
   With these changes for our next release, are we good to go for this
   release?
  
   Thanks,
   James
  
  
   On Tue, Mar 11, 2014 at 9:40 AM, Marvin Humphrey 
 mar...@rectangular.comjavascript:;
   wrote:
  
On Tue, Mar 11, 2014 at 9:18 AM, James Taylor 
 jamestay...@apache.orgjavascript:;
  
wrote:
 Also, should we drop the .txt
 extension on the NOTICE and LICENSE files for our next release?
   
  http://www.apache.org/dev/apply-license.html#license-file-name
   
  Can the LICENSE and NOTICE files be called LICENSE.txt and
  NOTICE.txt?
   
This is permitted. However the preference is that the files be
  called
LICENSE and NOTICE.
   
Marvin Humphrey
   
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 javascript:;
For additional commands, e-mail: general-h...@incubator.apache.org
 javascript:;
   
   
  
 

Re: [RESULT][VOTE] Release of Apache Phoenix 2.2.3 incubating RC4

[James Taylor]

Filed this: https://issues.apache.org/jira/browse/PHOENIX-830
And David Nalley send us a patch already (thanks, David!) which will be
applied shortly:  https://github.com/apache/incubator-phoenix/pull/20

Thanks,
James


On Thu, Mar 13, 2014 at 11:16 AM, Henry Saputra henry.sapu...@gmail.comwrote:

 Please do file the ticket to address the Disclaimer file for the release.

 On Thursday, March 13, 2014, James Taylor jamestay...@apache.org wrote:

  Voting is now closed. This vote passes with 4 binding +1 votes and no 0
  or -1 votes. Thank you to everyone who voted. Totals:
 
  +1:
  Michael Stack *
  Henry Saputra *
  Enis Söztutar *
  Andrew Purtell *
 
  0:
 
  -1:
 
  * = binding
 
  Thanks,
  James
 
  On Thu, Mar 13, 2014 at 8:58 AM, Henry Saputra henry.sapu...@gmail.com
 javascript:;
  wrote:
 
   Hi Enis, thx for the Vote.
  
   There was already commitment from James to fix the disclaimer so I
  would
   not think this should be a release blocker.
  
   Thx,
  
   Henry
  
   On Wednesday, March 12, 2014, Enis Söztutar enis@gmail.com
 javascript:;
  wrote:
  
+1 (binding).
   
- Checked the src and binary artifacts.
- Checked sigs
- Checked CRCs
- Built the src artifacts
   
If the DISCLAIMER file will not sink the RC, lets go ahead with
  releasing
this. Otherwise we would need a new RC.
   
Enis
   
   
On Tue, Mar 11, 2014 at 11:11 AM, James Taylor 
 jamestay...@apache.orgjavascript:;
   javascript:;
wrote:
   
 Thanks, Marvin. We'll update this in our next release too, as we'd
  like
to
 follow the preferred path.

 With these changes for our next release, are we good to go for this
 release?

 Thanks,
 James


 On Tue, Mar 11, 2014 at 9:40 AM, Marvin Humphrey 
   mar...@rectangular.com javascript:;javascript:;
 wrote:

  On Tue, Mar 11, 2014 at 9:18 AM, James Taylor 
   jamestay...@apache.org javascript:;javascript:;

  wrote:
   Also, should we drop the .txt
   extension on the NOTICE and LICENSE files for our next release?
 
http://www.apache.org/dev/apply-license.html#license-file-name
 
Can the LICENSE and NOTICE files be called LICENSE.txt and
NOTICE.txt?
 
  This is permitted. However the preference is that the files
 be
called
  LICENSE and NOTICE.
 
  Marvin Humphrey
 
 
  -
  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
 javascript:;
   javascript:;
  For additional commands, e-mail:
 general-h...@incubator.apache.orgjavascript:;
   javascript:;
 
 

   
  
 

Re: [VOTE] Release of Apache Phoenix 2.2.3 incubating RC4

[James Taylor]

Would it be possible for an IPMC member to clarify if you're waiting on us
for something and if so what?

Thanks,
James


On Tue, Mar 11, 2014 at 11:11 AM, James Taylor jamestay...@apache.orgwrote:

 Thanks, Marvin. We'll update this in our next release too, as we'd like to
 follow the preferred path.

 With these changes for our next release, are we good to go for this
 release?

 Thanks,
 James


 On Tue, Mar 11, 2014 at 9:40 AM, Marvin Humphrey 
 mar...@rectangular.comwrote:

 On Tue, Mar 11, 2014 at 9:18 AM, James Taylor jamestay...@apache.org
 wrote:
  Also, should we drop the .txt
  extension on the NOTICE and LICENSE files for our next release?

   http://www.apache.org/dev/apply-license.html#license-file-name

   Can the LICENSE and NOTICE files be called LICENSE.txt and NOTICE.txt?

 This is permitted. However the preference is that the files be called
 LICENSE and NOTICE.

 Marvin Humphrey

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

Re: [VOTE] Release of Apache Phoenix 2.2.3 incubating RC4

[James Taylor]

David,
Would it be possible to get a +1 for this release provided we add the
DISCLAIMER file in our next release? Also, should we drop the .txt
extension on the NOTICE and LICENSE files for our next release?
Thanks,
James


On Tue, Mar 11, 2014 at 4:55 AM, David Nalley da...@gnsa.us wrote:

 On Mon, Mar 10, 2014 at 10:33 PM, James Taylor jamestay...@apache.org
 wrote:
  Thanks for the review, David. We do have a NOTICE.txt in both the source
  and binary tar ball (in the phoenix-2.2.3-incubating directory). Is that
  the correct way to do it?
 
  We'll add the missing license headers in those couple of example files
  where it's missing for our next release.
 
  Thanks,
  James
 

 Hi James:

 The Disclaimer (typically found in a file named DISCLAIMER) has the
 following content:

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

 I thought there was a requirement that this same file be in the top
 level of your git repo as well, but don't find anything that suggests
 this in the documentation, perhaps that has changed.

 I couldn't find that in my brief looking - and don't see it contained
 in the NOTICE file.

 --David

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

Re: [VOTE] Release of Apache Phoenix 2.2.3 incubating RC4

[James Taylor]

Thanks, Marvin. We'll update this in our next release too, as we'd like to
follow the preferred path.

With these changes for our next release, are we good to go for this release?

Thanks,
James


On Tue, Mar 11, 2014 at 9:40 AM, Marvin Humphrey mar...@rectangular.comwrote:

 On Tue, Mar 11, 2014 at 9:18 AM, James Taylor jamestay...@apache.org
 wrote:
  Also, should we drop the .txt
  extension on the NOTICE and LICENSE files for our next release?

   http://www.apache.org/dev/apply-license.html#license-file-name

   Can the LICENSE and NOTICE files be called LICENSE.txt and NOTICE.txt?

 This is permitted. However the preference is that the files be called
 LICENSE and NOTICE.

 Marvin Humphrey

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

Re: [VOTE] Release of Apache Phoenix 2.2.3 incubating RC4

[James Taylor]

Thanks for the review, David. We do have a NOTICE.txt in both the source
and binary tar ball (in the phoenix-2.2.3-incubating directory). Is that
the correct way to do it?

We'll add the missing license headers in those couple of example files
where it's missing for our next release.

Thanks,
James


On Mon, Mar 10, 2014 at 6:18 PM, David Nalley da...@gnsa.us wrote:

 On Fri, Mar 7, 2014 at 1:43 PM, James Taylor jamestay...@apache.org
 wrote:
  Hello Everyone,
  This is a call for a vote on Apache Phoenix 2.2.3 incubating RC4. Phoenix
  is a SQL query engine for Apache HBase, a NoSQL data store. It is
 accessed
  as a JDBC driver and enables querying and managing HBase tables using
 SQL. This
  will be our first release in the incubator. The release includes both a
  source-only release and a convenience binary release. The last RC was
 sunk
  because of errors in the LICENSE and NOTICE files.
 
  The source tarball, including signatures, digests, etc can be found at:
 
 https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-2.2.3-incubating-rc4/src/
 
  The binary artifacts can be found at:
 
 https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-2.2.3-incubating-rc4/bin/
 
  The dev list thread for the passing vote (3 +1s with 1 IPMC vote) can be
  found at:
 
 http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201403.mbox/%3CCAAF1JdiOuwWisUGRFDMChB_bpiALz1HVrJDEtk9-pAdwDVLchA%40mail.gmail.com%3E
 
  Release artifacts are signed with the following key:
  https://people.apache.org/keys/committer/mujtaba.asc
 
  KEYS file available here:
  https://dist.apache.org/repos/dist/dev/incubator/phoenix/KEYS
 
  The tag to be voted upon is v2.2.3:
 
 https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=tag;h=refs/tags/v2.2.3
 
  For information about the contents of this release see:
 
 https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=log;h=refs/tags/v2.2.3
 
  Vote will be open for at least 72 hours. Please vote:
 
  [ ] +1 approve
  [ ] +0 no opinion
  [ ] -1 disapprove (and reason why)
 
  Thanks,
  James

 Hi James:

 I went through the source and binary tarballs and can't seem to find a
 DISCLAIMER file, or a notice as required by [1]. I note that a
 DISCLAIMER file is only a SHOULD[2], but the notice MUST be present
 somewhere[1]. Did I miss it somewhere? It seems to be the only problem
 keeping me from issuing a positive vote.

 I also note that a small number of files are missing license headers,
 which I don't personally hold be blocking a release, but should be
 fixed.

 --David 'hating to be the bearer of bad news'

 [1] http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
 [2] http://incubator.apache.org/guides/branding.html

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

[CANCEL][VOTE] Release of Apache Phoenix 2.2.3 incubating

[James Taylor]

Cancelling this vote due to mistakes in the LICENSE and NOTICE files. Will
start a new vote shortly.
Thanks,
James

On Wed, Feb 26, 2014 at 11:08 AM, David Nalley da...@gnsa.us wrote:

 On Wed, Feb 26, 2014 at 1:43 PM, James Taylor jamestay...@apache.org
 wrote:
  Thanks so much, David for the review and words of encouragement. Don't
  worry, we won't get discouraged - we just want to get this right.
 
  See below for more questions/comments.
 
  Regards,
  James
 
  On Tue, Feb 25, 2014 at 9:26 PM, David Nalley da...@gnsa.us wrote:
 
  On Mon, Feb 24, 2014 at 9:37 PM, James Taylor jamestay...@apache.org
  wrote:
   Hello everyone,
  
   This is a call for a vote on Apache Phoenix 2.2.3 incubating. Phoenix
 is
  a
   SQL query engine for Apache HBase, a NoSQL data store.  It is accessed
  as a
   JDBC driver and enables querying and managing HBase tables using SQL.
  This
   will be our first release in the incubator.
  
   The RC is available for download at
   http://people.apache.org/~jamestaylor/phoenix-2.2.3-incubating-RC3/and
  is
   signed with my code signing key 5F5F3233. The source code may be
 found in
  
 
 http://people.apache.org/~jamestaylor/phoenix-2.2.3-incubating-RC3/phoenix-2.2.3-incubating-src.tar.gzwhile
   a convenience, pre-built binary may be found in
  
 
 http://people.apache.org/~jamestaylor/phoenix-2.2.3-incubating-RC3/phoenix-2.2.3-incubating.tar.gz
   .
  
   GIT source tag:
  
 
 https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=log;h=refs/tags/v2.2.3
   GIT commit:
  
 
 https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=commit;h=5e7d071693b6ad4adb758b94d53808a75feeae26
  
 
  Hi James:
 
  Nice to see phoenix working on a release so rapidly.
  This vote is missing a lot of information that makes it much harder to
  work with.
  Has your dev list seen this vote? If so a link to the [RESULT] of that
  vote would be nice. If not, why not? (I couldn't find an RC3 vote in
  my hasty look at your archives)
 
 
  A vote was held on developer mailing list  for the previous release
  candidate, RC2, and it passed with 4 +1's, and no -1's or +0's (2 votes
  were from IPMC members). The thread is here:
 
 http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201402.mbox/%3CCAAF1JdjsiHGFYQjkMVSWJmGaRJQd0fJJRVAB7J70-i2tLR2UkA%40mail.gmail.com%3E
 
  This release candidate, RC3, has one additional bug fix and a separate
  source-only tar ball. I proposed on our dev list not to hold a new vote,
  but rather start a vote on the general list instead, since the changes
 were
  minimal and no one objected.
 
  Is that ok?
 

 It is probably technically acceptable from a very strict
 interpretation of the release guidelines since it's a release of the
 incubator. I think socially and from a incubator learning process that
 you are shortchanging yourself. Keep in mind the IPMC wants to see
 that the community can function on its own, and iterating over RCs is
 just part of the process.

   How many binding IPMC votes did you get on your dev list vote? (If you
  have enough binding votes, I might not expend the time, while if you
  are lacking votes I might be willing to invest the time to help)
  The RC2 vote email was a bit better in the last two regards.
  Please put the RC# in the subject - this was threaded in my mail
  client under an RC2 mail.
 
 
  I'll make sure to include the RC# in the subject next time.
 
 

 Thanks - that dramatically improves readability.

 
  Where is your KEYS file? (does phoenix have a space on dist.a.o?) Even
  having your key in your LDAP profile would be ok, but you don't link
  to the key, which is extra work. You'll need a KEYS file when you
  publish anyway.
 
 
  I will generate the KEYS file and include in the same directory. We'll
 put
  our next release/release candidate in dist.a.o, as that seems the norm.
 
 

 Good.


 
  The NOTICE and LICENSE files are problematic. NOTICE in the source
  tarball contains notices for software that simply doesn't exist in the
  source tarball. And LICENSE in the convenience binary seems to be
  missing licenses for software that is included.
  Have a look here:
  http://www.apache.org/dev/licensing-howto.html#mod-notice for more
  details.
 
 
  The NOTICE file of our source-only distribution matches the one from our
  binary distribution which is a mistake. Our source-only distribution does
  not include source from any other projects. Does that mean we don't need
 a
  NOTICE file for our source-only distribution?

 You need a NOTICE file, but it only need contain the notice for the
 ASF (in the source distribution)
 http://www.apache.org/legal/src-headers.html#notice

 
  For our binary distribution, we'll make another pass through our indirect
  dependencies and update the NOTICE and LICENSE as needed.
 
  Should we roll a new RC and start a new thread after these changes?

 Yep, I'd roll a new RC, kick a vote off on your dev list and bring it
 back here when done

[VOTE] Release of Apache Phoenix 2.2.3 incubating RC4

[James Taylor]

Hello Everyone,
This is a call for a vote on Apache Phoenix 2.2.3 incubating RC4. Phoenix
is a SQL query engine for Apache HBase, a NoSQL data store. It is accessed
as a JDBC driver and enables querying and managing HBase tables using SQL. This
will be our first release in the incubator. The release includes both a
source-only release and a convenience binary release. The last RC was sunk
because of errors in the LICENSE and NOTICE files.

The source tarball, including signatures, digests, etc can be found at:
https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-2.2.3-incubating-rc4/src/

The binary artifacts can be found at:
https://dist.apache.org/repos/dist/dev/incubator/phoenix/phoenix-2.2.3-incubating-rc4/bin/

The dev list thread for the passing vote (3 +1s with 1 IPMC vote) can be
found at:
http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201403.mbox/%3CCAAF1JdiOuwWisUGRFDMChB_bpiALz1HVrJDEtk9-pAdwDVLchA%40mail.gmail.com%3E

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

KEYS file available here:
https://dist.apache.org/repos/dist/dev/incubator/phoenix/KEYS

The tag to be voted upon is v2.2.3:
https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=tag;h=refs/tags/v2.2.3

For information about the contents of this release see:
https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=log;h=refs/tags/v2.2.3

Vote will be open for at least 72 hours. Please vote:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks,
James

Re: [VOTE] Release of Apache Phoenix 2.2.3 incubating

[James Taylor]

Thanks so much, David for the review and words of encouragement. Don't
worry, we won't get discouraged - we just want to get this right.

See below for more questions/comments.

Regards,
James

On Tue, Feb 25, 2014 at 9:26 PM, David Nalley da...@gnsa.us wrote:

 On Mon, Feb 24, 2014 at 9:37 PM, James Taylor jamestay...@apache.org
 wrote:
  Hello everyone,
 
  This is a call for a vote on Apache Phoenix 2.2.3 incubating. Phoenix is
 a
  SQL query engine for Apache HBase, a NoSQL data store.  It is accessed
 as a
  JDBC driver and enables querying and managing HBase tables using SQL.
 This
  will be our first release in the incubator.
 
  The RC is available for download at
  http://people.apache.org/~jamestaylor/phoenix-2.2.3-incubating-RC3/ and
 is
  signed with my code signing key 5F5F3233. The source code may be found in
 
 http://people.apache.org/~jamestaylor/phoenix-2.2.3-incubating-RC3/phoenix-2.2.3-incubating-src.tar.gzwhile
  a convenience, pre-built binary may be found in
 
 http://people.apache.org/~jamestaylor/phoenix-2.2.3-incubating-RC3/phoenix-2.2.3-incubating.tar.gz
  .
 
  GIT source tag:
 
 https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=log;h=refs/tags/v2.2.3
  GIT commit:
 
 https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=commit;h=5e7d071693b6ad4adb758b94d53808a75feeae26
 

 Hi James:

 Nice to see phoenix working on a release so rapidly.
 This vote is missing a lot of information that makes it much harder to
 work with.
 Has your dev list seen this vote? If so a link to the [RESULT] of that
 vote would be nice. If not, why not? (I couldn't find an RC3 vote in
 my hasty look at your archives)


A vote was held on developer mailing list  for the previous release
candidate, RC2, and it passed with 4 +1's, and no -1's or +0's (2 votes
were from IPMC members). The thread is here:
http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201402.mbox/%3CCAAF1JdjsiHGFYQjkMVSWJmGaRJQd0fJJRVAB7J70-i2tLR2UkA%40mail.gmail.com%3E

This release candidate, RC3, has one additional bug fix and a separate
source-only tar ball. I proposed on our dev list not to hold a new vote,
but rather start a vote on the general list instead, since the changes were
minimal and no one objected.

Is that ok?

 How many binding IPMC votes did you get on your dev list vote? (If you
 have enough binding votes, I might not expend the time, while if you
 are lacking votes I might be willing to invest the time to help)
 The RC2 vote email was a bit better in the last two regards.
 Please put the RC# in the subject - this was threaded in my mail
 client under an RC2 mail.


I'll make sure to include the RC# in the subject next time.



 Where is your KEYS file? (does phoenix have a space on dist.a.o?) Even
 having your key in your LDAP profile would be ok, but you don't link
 to the key, which is extra work. You'll need a KEYS file when you
 publish anyway.


I will generate the KEYS file and include in the same directory. We'll put
our next release/release candidate in dist.a.o, as that seems the norm.



 The NOTICE and LICENSE files are problematic. NOTICE in the source
 tarball contains notices for software that simply doesn't exist in the
 source tarball. And LICENSE in the convenience binary seems to be
 missing licenses for software that is included.
 Have a look here:
 http://www.apache.org/dev/licensing-howto.html#mod-notice for more
 details.


The NOTICE file of our source-only distribution matches the one from our
binary distribution which is a mistake. Our source-only distribution does
not include source from any other projects. Does that mean we don't need a
NOTICE file for our source-only distribution?

For our binary distribution, we'll make another pass through our indirect
dependencies and update the NOTICE and LICENSE as needed.

Should we roll a new RC and start a new thread after these changes?

Re: [VOTE] Release of Apache Phoenix 2.2.3 incubating

[James Taylor]

I'll cancel this vote and start a vote on a new RC shortly. There was a
pretty serious bug that was found in this one anyway.

Is it best practice to have a separate source-only tar bar and not include
the source in the binary tar ball? Or should it be included in both?

Thanks,
James


On Mon, Feb 24, 2014 at 10:11 AM, Andrew Purtell apurt...@apache.orgwrote:

 Hi Sebb,

 On Sat, Feb 22, 2014 at 2:19 AM, sebb seb...@gmail.com wrote:

  I've had a quick look at the (sole) archive, and it contains both
  source and compiled jars.
  Although it is OK to release convenience binaries, there must be a
  source only release, as that is the ASF mission - to release open
  source.
 

 The what must every release contain doc says:

 Every ASF release *must* contain a source package, which must be sufficient
 for a user to build and test the release provided they have access to the
 appropriate platform and tools. The source package must be
 cryptographically
 signed http://www.apache.org/dev/release-signing.html by the Release
 Manager with a detached signature; and that package together with its
 signature must be tested prior to voting +1 for release.


 We can mentor the podling to produce a separate source only tarball, but
 this might be a point of confusion, because the candidate tarball here
 conforms to the above language, I have personally built and tested this
 release from the properly signed tarball. It is a source tarball also
 containing compiled binaries.


 --
 Best regards,

- Andy

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

[CANCEL][VOTE] Release of Apache Phoenix 2.2.3 incubating

[James Taylor]

This vote is being cancelled because the RC did not include a source-only
tar ball. A new vote thread will be started with one that does.

Regards,
James

On Fri, Feb 21, 2014 at 5:12 PM, James Taylor jamestay...@apache.orgwrote:

 Hello everyone,

 This is a call for a vote on Apache Phoenix 2.2.3 incubating. Phoenix is
 a SQL query engine for Apache HBase, a NoSQL data store.  It is accessed as
 a JDBC driver and enables querying and managing HBase tables using SQL.
 This will be our first release in the incubator.

 The RC is available for download at
 http://people.apache.org/~jamestaylor/phoenix-2.2.3-incubating-RC2/ and
 is signed with my code signing key 5F5F3233.

 A vote was held on developer mailing list [1] and it passed with 4 +1's,
 and no
 -1's or +0's (2 votes were from IPMC members).

 Vote will be open for at least 72 hours:

 [ ] +1 approve
 [ ] +0 no opinion
 [ ] -1 disapprove (and reason why)

 Thanks!
 James

 [1] Vote thread:
 http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201402.mbox/%3CCAAF1JdjsiHGFYQjkMVSWJmGaRJQd0fJJRVAB7J70-i2tLR2UkA%40mail.gmail.com%3E

[VOTE] Release of Apache Phoenix 2.2.3 incubating

[James Taylor]

Hello everyone,

This is a call for a vote on Apache Phoenix 2.2.3 incubating. Phoenix is a
SQL query engine for Apache HBase, a NoSQL data store.  It is accessed as a
JDBC driver and enables querying and managing HBase tables using SQL. This
will be our first release in the incubator.

The RC is available for download at
http://people.apache.org/~jamestaylor/phoenix-2.2.3-incubating-RC3/ and is
signed with my code signing key 5F5F3233. The source code may be found in
http://people.apache.org/~jamestaylor/phoenix-2.2.3-incubating-RC3/phoenix-2.2.3-incubating-src.tar.gzwhile
a convenience, pre-built binary may be found in
http://people.apache.org/~jamestaylor/phoenix-2.2.3-incubating-RC3/phoenix-2.2.3-incubating.tar.gz
.

GIT source tag:
https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=log;h=refs/tags/v2.2.3
GIT commit:
https://git-wip-us.apache.org/repos/asf?p=incubator-phoenix.git;a=commit;h=5e7d071693b6ad4adb758b94d53808a75feeae26

Vote will be open for at least 72 hours:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks!
James

[VOTE] Release of Apache Phoenix 2.2.3 incubating

[James Taylor]

Hello everyone,

This is a call for a vote on Apache Phoenix 2.2.3 incubating. Phoenix is a
SQL query engine for Apache HBase, a NoSQL data store.  It is accessed as a
JDBC driver and enables querying and managing HBase tables using SQL. This
will be our first release in the incubator.

The RC is available for download at
http://people.apache.org/~jamestaylor/phoenix-2.2.3-incubating-RC2/ and is
signed with my code signing key 5F5F3233.

A vote was held on developer mailing list [1] and it passed with 4 +1's,
and no
-1's or +0's (2 votes were from IPMC members).

Vote will be open for at least 72 hours:

[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove (and reason why)

Thanks!
James

[1] Vote thread:
http://mail-archives.apache.org/mod_mbox/incubator-phoenix-dev/201402.mbox/%3CCAAF1JdjsiHGFYQjkMVSWJmGaRJQd0fJJRVAB7J70-i2tLR2UkA%40mail.gmail.com%3E

Re: [VOTE] Graduation of Apache Spark from the Incubator

[James Taylor]

FYI, we have an on-going thread for the git/github discussion here:
http://mail-archives.apache.org/mod_mbox/incubator-general/201402.mbox/%3CCAEWfVJ%3D_wtDRTNEz4ojvUBf50_VdLDUhiQ15q5rfvFi5eh76uw%40mail.gmail.com%3E

For Phoenix, we'll likely mimic what JClouds is doing, but I live Lar's
ideas as an improvement.

Thanks,
James


On Thu, Feb 6, 2014 at 11:04 AM, lars hofhansl la...@apache.org wrote:

 I agree with Marvin. In addition I find it odd to rely in two sources of
 truth (and two sets of infrastructure, etc) as far as code goes just so we
 do code reviews on GitHub.
 Anybody who wants to commit now needs to have both the Github repo and the
 Apache repo cloned; you can merge a pull request on GitHub, as that is not
 authoritative source control.
 Github will be behind sometimes, etc, etc.

 What if there are issues with Github (unlikely, I know, but would be out
 of Apache's control)?

 Can't we add necessary Apache Infrastructure? Would Apache be able to get
 a free GitHub license - ala Jira - to run it as part of Apache (or maybe
 buy a license)?
 On the Phoenix mailing Gerret was mentioned for git-style code review.

 -- Lars



 
  From: Marvin Humphrey mar...@rectangular.com
 To: general@incubator.apache.org general@incubator.apache.org
 Sent: Thursday, February 6, 2014 9:53 AM
 Subject: Re: [VOTE] Graduation of Apache Spark from the Incubator


 On Thu, Feb 6, 2014 at 9:08 AM, Michael Joyce jo...@apache.org wrote:
  How is doing a review on Github any different than doing a review on
 Review
  Board?

 One is captured to Apache controlled channels and the other is not.

  If there's concern that work on Github isn't being adequately mirrored on
  the mailing lists then that sounds like an Infra problem to me.

 It's not an Infra problem.  It's the problem of any PMC which fails to
 ensure
 that all of its communications are properly archived.

 If anyone here is interested in contributing towards this feature, I
 encourage
 you to subscribe to the infrastructure-dev@apache list.  I also encourage
 everyone to ponder carefully:

 *   How to ensure that no information is lost when capturing communications
 in GitHub channels through notifications to our dev lists.
 *   The impact of adding GitHub integration features on long-term ASF Infra
 labor costs.

  There are plenty of hooks [1] that makes this easy to do and, if I'm not
  mistaken, pull requests through Github are already supposed to mail dev@
 .

 That's right.  I've actually worked on the specific hook that does
 that[1][2].

  I would assume that any comment on them should as well.

 Why would you assume that GitHub comments are being mailed to dev lists?
 They are not.

 Every Apache PMC member is tasked with oversight of their project, and that
 includes ensuring that all decisions happen on the dev list and are
 properly
 documented.  It is not enough to assume that Infra is taking care of
 archival -- ensuring that the archival actually happens is the PMC's direct
 responsibility.

 Marvin Humphrey

 [1] https://issues.apache.org/jira/browse/INFRA-4651
 [2] Thread on legal-discuss@apache: http://s.apache.org/Nhx


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

best development methodology for Apache git?

[James Taylor]

The Phoenix project has recently come into incubation from it's former life
as a Github project. I believe other projects have made this same
transition, so I'm looking to get some advice from them. What's the best
development methodology folks have found for collaborative development when
your source of truth is an Apache git repo? Something like the Github model
that combines a) the ability for managing branches and visually reviewing
patches and b) a means to gate commits against the single source of truth,
the git repo.

Gerrit meets this requirement and based on INFRA-2205 used to be setup. If
that's not an option, what have folks found that works well?

Thanks,
James

Re: transferring Github issues to JIRA?

[James Taylor]

Thanks, Jake. I filed https://issues.apache.org/jira/browse/INFRA-7179 and
attached the CSV. Do you know what the turnaround time typically is? Please
let me know if I can help in any way.

James


On Wed, Jan 8, 2014 at 1:45 PM, Jake Farrell jfarr...@apache.org wrote:

 The github plugin is not installed in our jira, I would recommend that you
 go with the csv route as Steve mentioned

 -Jake


 On Wed, Jan 8, 2014 at 4:24 PM, Steve Rowe sar...@gmail.com wrote:

  Sorry Andy, I don’t know if Infrastructure can/will assist with using
 that
  plugin, but it can’t hurt to ask, and making an INFRA ticket should work
  for that.
 
  I searched INFRA issues for github issue migration and found none that
  involved the Atlassian plugin - they all used github CSV export when was
  then imported to JIRA by Infrastructure (AFAICT):
 
  https://issues.apache.org/jira/browse/INFRA-3596
  https://issues.apache.org/jira/browse/INFRA-3761
  https://issues.apache.org/jira/browse/INFRA-5951
 
  I see you already have the PHOENIX project set up in JIRA (
  https://issues.apache.org/jira/browse/PHOENIX), so that should simplify
  the import task whichever way you end up going.
 
  Good luck,
  Steve
 
  On Jan 7, 2014, at 3:20 PM, Andrew Purtell apurt...@apache.org wrote:
 
   So that means we need an INFRA ticket to plug that in and run an
 import?
  
  
   On Mon, Jan 6, 2014 at 4:16 PM, Steve Rowe sar...@gmail.com wrote:
  
   Atlassian provides a plugin for that:
  
  
 
 https://marketplace.atlassian.com/plugins/com.atlassian.jira.plugins.jira-importers-github-plugin
  
  
   On Mon, Jan 6, 2014 at 6:55 PM, James Taylor jamestay...@apache.org
   wrote:
  
   Hello,
   Anyone out there know of an automated way of transferring over Github
   issues to JIRA? We're in the process of transferring over our
 existing
   Phoenix Github-based open source project to our Apache incubator
  project
   and automating the seeding of the initial JIRAs would be very
 helpful.
   Thanks,
   James
  
  
  
  
  
   --
   Best regards,
  
 - Andy
  
   Problems worthy of attack prove their worth by hitting back. - Piet
 Hein
   (via Tom White)
 
 
  -
  To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
  For additional commands, e-mail: general-h...@incubator.apache.org
 
 

transferring Github issues to JIRA?

[James Taylor]

Hello,
Anyone out there know of an automated way of transferring over Github
issues to JIRA? We're in the process of transferring over our existing
Phoenix Github-based open source project to our Apache incubator project
and automating the seeding of the initial JIRAs would be very helpful.
Thanks,
James