Re: [VOTE] Accept Zipkin into the Apache Incubator

[Mike Drob]

+1 (non-binding)

On Mon, Aug 27, 2018 at 11:44 AM, Matt Sicker  wrote:

> +1 (binding)
>
> On Mon, 27 Aug 2018 at 10:20, Andrey Redko  wrote:
>
> > +1 to Accept (non binding)
> >
> > Best Regards,
> > Andriy Redko
> >
> > On Sun, Aug 26, 2018, 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/54798a5059db1d5716ed9910a15c92
> 945509a25ec3b7ccb6b1215c53@%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 alongsid

Re: [PROPOSAL] Zipkin for Apache Incubator

[Mike Drob]

+1

As a former PPMC on Apache Htrace during incubation, I hope to see Zipkin
succeed!

Mike

On Sun, Aug 19, 2018, 9:10 PM Byung-Gon Chun  wrote:

> +1
>
> We've been using Zipkin. It's great to see this incubation proposal.
>
>
> On Mon, Aug 20, 2018 at 3:09 AM, Davor Bonaci  wrote:
>
> > +1; this sounds great.
> >
> > On Sun, Aug 19, 2018 at 6:34 AM, 吴晟 Sheng Wu 
> wrote:
> >
> > > > I think Skywalking may face the same issue, few people register the
> > > mailing
> > > list because lots of discussion happen in the github issues.
> > >
> > > Yes. Many people used to discuss on GitHub. We are OK with that. We
> have
> > > 38 discussion issues[1] in this 5.0.0-RC development iteration(only a
> > > month).
> > >
> > >
> > > > I'd be happy to be the mentor of this project if you are interested.I
> > > guess
> > > there is still a room for additional mentor.
> > > As some part of my daily work[2] is based on the work of zipkin, I can
> > > devote more time on this project.
> > >
> > >
> > > I added you in the mentor list. Thanks.
> > >
> > >
> > > [1] https://github.com/apache/incubator-skywalking/issues?q=
> > > is%3Aissue+is%3Aclosed+label%3Aquestion+milestone%3A5.0.0-RC
> > >
> > >
> > > --
> > > Sheng Wu
> > > Apache SkyWalking
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > > -- Original --
> > > From:  "willem.jiang";
> > > Date:  Sun, Aug 19, 2018 07:36 AM
> > > To:  "general";
> > >
> > > Subject:  Re: [PROPOSAL] Zipkin for Apache Incubator
> > >
> > >
> > >
> > > +1. It's great that Zipkin can be a part of Apache Incubator project.
> > >
> > > After going through the discussion here[1], I can see Zipkin leverage
> > > Github infrastructure  a lot, we may need to figure out if we need to
> > setup
> > > the user mailing list for this project.
> > > I agree with what John has said, you may consider twice for migration
> > user
> > > discussion from github to apache mailing list.
> > > I think Skywalking may face the same issue, few people register the
> > mailing
> > > list because lots of discussion happen in the github issues.
> > >
> > > I'd be happy to be the mentor of this project if you are interested.I
> > guess
> > > there is still a room for additional mentor.
> > > As some part of my daily work[2] is based on the work of zipkin, I can
> > > devote more time on this project.
> > >
> > > [1] https://github.com/openzipkin/openzipkin.github.io/issues/51
> > > [2] https://github.com/apache/incubator-servicecomb-saga
> > >
> > > Willem Jiang
> > >
> > > Twitter: willemjiang
> > > Weibo: 姜宁willem
> > >
> > > On Fri, Aug 17, 2018 at 5:29 PM, 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 promot

Re: Podling announcing releases

[Mike Drob]

Greg,

I'm confused about this warning. It looks like Pierre was explicitly
telling people not to do the wrong thing, and spot checking their website
the download links point to the mirror page for at least their latest
release.

Mike

On Sun, Mar 18, 2018, 4:09 PM Greg Stein  wrote:

> On Sun, Mar 18, 2018, 08:18 Pierre Smits  wrote:
>
> > High Nick, all,
> >
> > Who am I to tell how a community - incubating or not - constructs their
> web
> > presence in general and their download links/page in particular.
> >
>
> Well, Infra *can* coerce you to fix Trafodion's download Page's incorrect
> link. I don't think we would edit your page, but we *can* stop your misuse
> of www.a.o/dist, and recommend you switch to using the mirror network, per
> release policy.
>
> Consider Trafodion officially warned. cc:dev@trafodion
>
> Regards,
> Greg Stein
> Infrastructure Administrator
>

Re: [DRAFT] Incubator PMC Board Report - March 2018

[Mike Drob]

On Mon, Mar 12, 2018 at 10:58 AM, Dave Fisher  wrote:

> Hi John -
>
> I did my mentor signoffs.
>
> > On Mar 12, 2018, at 6:49 AM, John D. Ament 
> wrote:
> >
> > All,
> >
> > Below is the current draft of the Incubator board report.  We are still
> > missing reports from many podlings, and several missing sign off.  I have
> > CC'd the podlings missing sign off, and separately notified the ones
> > missing reports.
> >
> > John
> >
> > Incubator PMC report for March 2018
> >
> > The Apache Incubator is the entry path into the ASF for projects and
> > codebases wishing to become part of the Foundation's efforts.
> >
> > There are currently 54 podlings under incubation.  We added 1 new IPMC
> > member, 3 new podlings and executed on 4 releases.  The HTrace report
> > indicates retirement in flight.
>
> I think some discussion will be needed with HTrace as AFAIK - Podlings
> typically aren't allowed to retire to the Attic.
>

https://incubator.apache.org/projects/#retired indicates that podlings do
retire? If not to the attic, then where?

>
> Regards,
> Dave
>
>
> >
> > * Community
> >
> >  New IPMC members:
> >
> >  - Timothy Chen
> >
> >  People who left the IPMC:
> >
> >
> >
> > * New Podlings
> >
> >  - Druid
> >  - Dubbo
> >  - Nemo
> >
> > * Podlings that failed to report, expected next month
> >
> >  - Gearpump
> >  - Milagro
> >  - OpenWhisk
> >  - Pony Mail
> >  - Quickstep
> >
> > * Podling Reports Missing Sign off
> >  - Hivemall
> >  - Myriad
> >  - Samoa
> >  - Service Comb
> >  - SINGA
> >  - Slider
> >  - Spot
> >  - Superset
> >
> > * Graduations
> >
> >  The board has motions for the following:
> >
> >  - Your podling here?
> >  - Your podling here?
> >
> > * Releases
> >
> >  The following releases entered distribution during the month of
> >  February:
> >
> >  - 2018-02-05 Apache Livy 0.5.0
> >  - 2018-02-15 Apache Netbeans 9.0 beta
> >  - 2018-02-19 Apache PonyMail 0.10.0
> >  - 2018-02-19 Apache MXNet 1.1.0
> >
> > * IP Clearance
> >
> >
> >
> > * Legal / Trademarks
> >
> >  - See Daffodil's report related to open legal questions.
> >  - See SkyWalking's report for open questions around optional modules
> > under discussion on legal lists.
> >
> > * Infrastructure
> >
> >
> >
> > * Miscellaneous
> >
> >
> >
> > * Credits
> >
> > --
> >   Table of Contents
> > AriaTosca
> > Crail
> > Druid
> > Dubbo
> > ECharts
> > Gearpump
> > Griffin
> > Hivemall
> > HTrace
> > Milagro
> > Myriad
> > Nemo
> > Omid
> > OpenWhisk
> > PLC4X
> > Pony Mail
> > Pulsar
> > Quickstep
> > SAMOA
> > ServiceComb
> > SINGA
> > SkyWalking
> > Slider
> > Spot
> > Superset
> > Taverna
> > Tephra
> >
> > --
> >
> > 
> > AriaTosca
> >
> > ARIA TOSCA project offers an easily consumable Software Development
> Kit(SDK)
> > and a Command Line Interface(CLI) to implement TOSCA(Topology and
> > Orchestration Specification of Cloud Applications) based solutions.
> >
> > AriaTosca has been incubating since 2016-08-27.
> >
> > Three most important issues to address in the move towards graduation:
> >
> >  1. Grow the community and enroll new committers.
> >  2. Have (more) frequent Release cycles to be compliant with the Apache
> > Way.
> >  3. Grow the project’s contributions from existing community of
> > contributors
> >
> > Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> > aware of?
> >
> > 1. The project issued its third release (0.2.0) as far as the code is
> > concerned.  Some considerable functionality has been added since the last
> > release in addition to a growth in diversity of contributions.
> >
> > How has the community developed since the last report?
> >
> > * All project communication now takes place on either the mailing list or
> > ASF's Slack, and is open for everybody.  We have worked hard to make this
> > the normal operating mode of the community. There have been some hiccups,
> > but in general the majority of discourse has taken place on the list.
> >
> > * Increased chatter on the mailing list including new subscribers who ask
> > questions, make suggestions and are likely to become contributors
> > themselves in the near future.
> >
> > * Weekly grooming meetings are now attended by the majority of the
> > community. This is not only a forum to review the weekly work items list,
> > but also as a place for open discussion about issues, questions as well
> as
> > for the community to get to better know each other.
> >
> >
> > How has the community developed since the last report?
> >
> > Over the last 3 months we have seen a significant increase in
> contributions
> > as well as a few new contributors, particularly from the Ericsson
> > contingent.
> >
> >
> > How has the project developed since the last report?
> >
> > ARIA now has two new patches considerably extend the parser's
> > plugin/extensions

Re: [DISCUSS] Dr. Elephant Incubator Proposal

[Mike Drob]

Thanks for explaining your thoughts, Carl! Those answers all sound great to
me.

Best of luck!


On Tue, Mar 6, 2018, 5:58 PM Carl Steinbach  wrote:

> Hi Mike,
>
> Why does Dr. Elephant make sense as a separate project instead of
> > contributing to Hadoop directly?
> >
>
> Here are a couple reasons why I think Dr. Elephant is more likely to
> succeed as a separate project:
>
> * Dr. Elephant supports Hadoop *and* Spark, and may support other
>   execution layers in the future. If we make Dr. Elephant a part of
>   Hadoop I expect that it will discourage contributions from people
>   who are interested mainly in Spark support, and vice versa.
>
> * If Dr. Elephant is added to Hadoop it will be necessary for the
>   Hadoop project to declare a dependency on Spark. I doubt this change
>   will get approved.
>
> * We don't want to tie Dr. Elephant to a specific version of Hadoop or
>   Spark, or tie the Dr. Elephant release cycle to the Hadoop or Spark
>   release cycles.
>
> * None of the current Dr. Elephant committers are Hadoop committers,
>   and I doubt that the Hadoop PMC is going to give them a commit bit
>   just to work on Dr. Elephant. As a result the existing committers
>   would be effectively forfeiting their right to continue maintaining
>   their own project. I think this is one of the reasons why many
>   Hadoop contrib projects are poorly maintained.
>
>
>
> > What is the relationship between Dr. Elephant and the (now seemingly
> > defunct) Hadoop Vaidya?
> >
>
> Vaidya was a command line tool for tuning Hadoop jobs. Dr. Elephant is
> an always-on service for tuning Hadoop and Spark jobs. We were unaware
> of Vaidya when we started working on Dr. Elephant.
>
> - Carl
>

Re: [DISCUSS] Dr. Elephant Incubator Proposal

[Mike Drob]

Why does Dr. Elephant make sense as a separate project instead of
contributing to Hadoop directly?

What is the relationship between Dr. Elephant and the (now seemingly
defunct) Hadoop Vaidya?

On Tue, Mar 6, 2018 at 5:08 PM, Carl Steinbach  wrote:

> Hi,
>
> I would like to propose Dr. Elephant as an Apache Incubator
> project. The proposal is available as a draft at
> https://wiki.apache.org/incubator/DrElephantProposal. I have also
> included the text of the proposal below.
>
> Any feedback from the community is much appreciated.
>
> Thanks.
>
> - Carl
>
>
> = ABSTRACT =
>
> Dr. Elephant is a performance monitoring and tuning service for Apache
> Hadoop and Apache Spark jobs and workflows. While the system is
> primarily aimed at developers, we have discovered that it is also
> popular with cluster operators who use it to monitor the health of
> workloads running on their clusters.
>
> = PROPOSAL =
>
> Dr. Elephant was open sourced by LinkedIn in 2016 and is currently
> hosted on GitHub. We believe that being a part of the Apache Software
> Foundation will improve the diversity and help form a strong community
> around the project.
>
> LinkedIn submits this proposal to donate the code base to the Apache
> Software Foundation. The code is already under Apache License 2.0.
> Both the source code and documentation are hosted on Github.
>
>  * Code: http://github.com/linkedin/dr-elephant
>  * Documentation: https://github.com/linkedin/dr-elephant/wiki
>
> = Background =
>
> Dr. Elephant is a service that helps users of Apache Hadoop and Apache
> Spark understand, analyze, and improve the performance of jobs and
> workflows running on their clusters. It automatically gathers metrics,
> performs analysis, and presents the results along with actionable
> advice. The goal of the project is to improve developer productivity
> and increase cluster efficiency by reducing the time and domain
> expertise required to diagnose and treat sick jobs. It analyzes Hadoop
> and Spark jobs using a set of configurable, extensible, rule-based
> heuristics that provide insights on job performance, and then uses
> this information to provide recommendations about how to tune jobs to
> make them run more efficiently.
>
> Dr. Elephant was open sourced in 2016 after two years of
> successful production use at Linkedin. In the time since many new
> features have been added including support for the Oozie and Airflow
> workflow schedulers, improved metrics, and enhancements to the Spark
> history fetcher and Spark heuristics. It is also important to note
> that many of these contributions came from developers outside of
> LinkedIn. We have also been happy to see that many people have been
> able to benefit from running Dr. Elephant including companies like
> Airbnb, Foursquare, Hulu, and Pinterest.
>
> = RATIONALE =
>
> Dr. Elephant's entry to the ASF will be beneficial to both the
> Dr. Elephant and Apache communities. Dr. Elephant has greatly
> benefited from its open source roots. Its community and adoption has
> grown greatly as a result. More importantly, the feedback from the
> community, whether through interactions at meetups or through the
> mailing list, have allowed for a rich exchange of ideas. We believe a
> partnership with the Apache Foundation is the logical next step. The
> Dr. Elephant community will greatly benefit from the established
> development and consensus processes that have worked well for other
> projects. The Apache process has served many other open source
> projects well and we believe that the Dr. Elephant community will
> greatly benefit from these practices as well.
>
> = CURRENT STATUS =
>
> Dr. Elephant is currently open sourced under the Apache License
> Version 2.0 and is available at github.com/linkedin/dr-elephant. All
> of the development is done using GitHub Pull Requests.
>
> We are aware of at least 10 organizations that are running
> Dr. Elephant, and many of these organizations have also contributed
> code. Dr. Elephant has also been integrated into commercial products
> such as Pepperdata's Application Profiler.
>
> = INITIAL GOALS =
>
> Our initial goals are as follows:
>
>  * Migrate the existing codebase to Apache
>  * Study and integrate with the Apache development process
>  * Ensure all dependencies are compliant with Apache License version 2.0
>  * Incremental development and releases per Apache guidelines
>  * Diversify the set of core developers and committers
>
> = MERITOCRACY =
>
> Following the Apache meritocracy model, we intend to build an open and
> diverse community around Dr. Elephant. We will encourage the community to
> contribute to discussions and the codebase.
>
> = COMMUNITY =
>
> The need for a simple and understandable performance monitoring and
> tuning service for Hadoop and Spark is tremendous. Dr. Elephant is
> currently being used by at least 10 organizations worldwide (some
> examples are listed here). We hope to extend the contributor base
> significantly

Re: [PROPOSAL] PLC4X - proposal for Apache Incubation

[Mike Drob]

> Can’t enter incubation without having code.

I think this has been done before, but it's not relevant now. I agree with
John that you should expect to need an SGA.

Good luck and good coding!

On Tue, Dec 12, 2017, 3:42 PM Justin Mclean 
wrote:

> Hi,
>
> Anyone have feedback or see any issues with this proposal?
>
> If there are none in the next couple of days I'll go ahead and call a vote.
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Resolution to graduate Apache Impala to TLP

[Mike Drob]

Hi Jim, have you verified with all of the proposed members that they would
like to continue on with the project once it completes incubation?

On Tue, Oct 31, 2017 at 11:38 PM, Jim Apple  wrote:

> The Impala community has discussed and voted positively on graduating
> to a TLP. Following the instructions from the graduation guide, this
> thread is for discussion.
>
> Community Discussion:
> https://lists.apache.org/thread.html/2f5db4788aff9b0557354b9106c032
> 8a29c1f90c1a74a228163949d2@%3Cdev.impala.apache.org%3E
>
> Community Vote:
> https://lists.apache.org/thread.html/a5a7c6895b3e019347d6e4e4cf49d6
> 7d094d31b8f2c7b4d59200f3e4@%3Cdev.impala.apache.org%3E
>
> Resolution:
>
> Establish the Apache Impala 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 high-performance distributed SQL engine.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Impala Project", be and hereby is
> established pursuant to Bylaws of the Foundation; and be it further
>
> RESOLVED, that the Apache Impala Project be and hereby is responsible
> for the creation and maintenance of software related to a
> high-performance distributed SQL engine; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Impala" 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 Impala
> Project, and to have primary responsibility for management of the
> projects within the scope of responsibility of the Apache Impala
> 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 Impala Project:
>
> * Alex Behm 
> * Bharath Vissapragada 
> * Brock Noland 
> * Carl Steinbach 
> * Casey Ching 
> * Daniel Hecht 
> * Dimitris Tsirogiannis 
> * Henry Robinson 
> * Ishaan Joshi 
> * Jim Apple 
> * John Russell 
> * Juan Yu 
> * Lars Volker 
> * Lenni Kuff 
> * Marcel Kornacker 
> * Martin Grund 
> * Matthew Jacobs 
> * Michael Brown 
> * Michael Ho 
> * Sailesh Mukil 
> * Skye Wanderman-Milne 
> * Taras Bobrovytsky 
> * Tim Armstrong 
> * Todd Lipcon 
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Jim Apple be appointed to
> the office of Vice President, Apache Impala, 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 Impala 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 Impala Project;
> and be it further
>
> RESOLVED, that the Apache Impala Project be and hereby is tasked with
> the migration and rationalization of the Apache Incubator Impala
> podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Impala podling encumbered upon the Apache Incubator PMC are hereafter
> discharged.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [LAZY] Letting anyone invite on Slack

[Mike Drob]

Anybody with an @apache.org email address can self-register

On Thu, Oct 19, 2017 at 2:38 PM, Gang(Gary) Wang  wrote:

> Can I get an invitation? Thanks.
>
> On Thu, Oct 19, 2017 at 12:14 PM, Anu Engineer 
> wrote:
>
> > Thank you very much, greatly appreciate it.
> >
> > We are using slack and this allows even non-committers to participate,
> > which was an issue earlier
> >
> > Thanks
> > Anu
> >
> >
> >
> >
> > On 10/19/17, 11:47 AM, "Hen"  wrote:
> >
> > Done. Anyone on TheAsf slack workspace can invite someone to the
> > workspace.
> >
> > On Sat, Oct 14, 2017 at 03:28 Greg Stein  wrote:
> >
> > > Fair enough... then open it up. Not even sure why that's a question
> > :-)
> > >
> > > On Sat, Oct 14, 2017 at 1:52 AM, Hen  wrote:
> > >
> > > > While I lean to the 'not seeing the value of Slack', we have many
> > > channels
> > > > on Slack now (mostly driven by Incubator projects I think; John
> > seems to
> > > > have taken the lead on the workspace), so this isn't a thread for
> > getting
> > > > rid of slack :)
> > > >
> > > > Hen
> > > >
> > > > On Fri, Oct 13, 2017 at 11:06 PM, Craig Russell <
> > apache@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi Henri,
> > > > >
> > > > > We tried to use slack with the Juneau project and never got it
> > to work
> > > > > "the Apache Way". Inviting people instead of self-service, no
> > ability
> > > to
> > > > > monitor discussions, no archive of discussions.
> > > > >
> > > > > We gave up and now use the wiki whenever mail doesn't serve.
> > Common
> > > > > editing of documents, diagrams, etc. are all easily done on
> > confluence
> > > > > where email doesn't allow sharing documents.
> > > > >
> > > > > I frankly do not see slack filling a need here.
> > > > >
> > > > > Craig
> > > > >
> > > > > > On Oct 13, 2017, at 9:51 PM, Henri Yandell <
> bay...@apache.org>
> > > wrote:
> > > > > >
> > > > > > Currently only 'admins' can invite people to the ASF Slack:
> > > > > >
> > > > > >  https://the-asf.slack.com/
> > > > > >
> > > > > > If we view it as an IRC equivalent, having to invite people
> at
> > all is
> > > > > > weird. We can, via a checkbox, change it so anyone on the ASF
> > Slack
> > > > > (except
> > > > > > 'guests') can invite someone to the Slack workspace:
> > > > > >
> > > > > > 
> > > > > >
> > > > > > Invitations
> > > > > >
> > > > > > Choose whether to allow non-admins to invite new people to
> > *ASF*.
> > > > > >
> > > > > > Allow everyone (except guests) to invite new members.
> > > > > > 
> > > > > >
> > > > > > I can't see why we'd have an issue there, so I'm planning to
> > turn
> > > that
> > > > > > checkbox on at the end of next week (Thursday or whenever I
> > remember
> > > to
> > > > > > after that :) ).
> > > > > >
> > > > > > If this is a bad idea, please object and let me know why :)
> > > > > >
> > > > > > Hen
> > > > >
> > > > > Craig L Russell
> > > > > c...@apache.org
> > > > >
> > > > >
> > > > > 
> > -
> > > > > To unsubscribe, e-mail: general-unsubscribe@incubator.
> apache.org
> > > > > For additional commands, e-mail: general-help@incubator.apache.
> > org
> > > > >
> > > > >
> > > >
> > >
> >
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>

Re: [DISCUSS] Accept Science Data Analytics Platform (SDAP) into Apache Incubator

[Mike Drob]

Why is this one incubator proposal instead of four?

On Tue, Oct 17, 2017 at 3:49 PM, lewis john mcgibbney 
wrote:

> Hi Raphael,
> Thank you, your interest has been registered.
> Lewis
>
> On Fri, Oct 13, 2017 at 10:52 AM,  incubator.apache.org>
> wrote:
>
> >
> > From: Raphael Bircher 
> > To: general@incubator.apache.org
> > Cc:
> > Bcc:
> > Date: Thu, 12 Oct 2017 22:20:29 +0200
> > Subject: Re: [DISCUSS] Accept Science Data Analytics Platform (SDAP) into
> > Apache Incubator
> > Hi all
> >
> > I offer my mentorship
> >
> > Regards, Raphael
> >
>
> --
> http://home.apache.org/~lewismc/
> @hectorMcSpector
> http://www.linkedin.com/in/lmcgibbney
>

Re: [DISCUSSION] Apache DataFu podling graduation

[Mike Drob]

I would go through the list of committers once (i.e. now, nearing
graduation) and ask folks if they would like to remain committers
post-graduation. If anybody responds in the negative or doesn't respond at
all, then remove them from the list and move on. I think this is your one
chance to shorten the list.

Going forward, I would either remove that section entirely, or reword it to
facilitate rejoining more easily. You can do this by adding language for an
"emeritus committer" status or something similar, or by adding instructions
for returning folks on what they need to do, and it should be relatively
frictionless, or some other way I haven't thought of. Please don't make
this a process that involves filing INFRA jiras. :)

Mike

On Tue, Oct 3, 2017 at 5:43 PM, Matthew Hayes <
matthew.terence.ha...@gmail.com> wrote:

> Regarding Raphael's comment:
>
> You have 14 Committers, but only 4 for the proposed PMC?
>
>
> The project began incubation with 10 committers.  If I recall correctly,
> the proposed list of committers was drawn largely from contributors in the
> git commit history in order to be inclusive and give them a chance to
> continue contributing as committers.  Some of these people are not actively
> involved at this time.  The list of committers has so far not been reduced
> in size.  4 additional committers were later added, bringing the total to
> 14.  The 4 proposed PMC members were committers who volunteered when asked
> who was willing to commit time to be on PMC.
>
> Regarding Mike's comment:
>
> >
> > I have concern about the DataFu process of removing committers due to
> > inactivity, as outlined on this wiki page -
> > https://cwiki.apache.org/confluence/display/DATAFU/Becoming+a+Committer
>
> How often has this process been used?
>
>
> This process hasn't been used so far.  This page was created earlier this
> year as we were going through the maturity evaluation.  This was largely
> based on Fineract's wiki page
> <https://cwiki.apache.org/confluence/display/FINERACT/Becoming+a+Committer
> >
> on the same subject, which seemed well written.  For the Apache DataFu page
> we increased the time frame from 6 months to 1 year actually.  For myself
> at least and probably others on the project the concept of "merit is
> considered to never expire" is shared.  Do you think we should add a bullet
> point to the page that if someone were removed from the committer list that
> their past contributions would be considered if they expressed interest in
> joining again?  If so I can propose that we update the page with this
> language.
>
> -Matt
>
>
>
> On Tue, Oct 3, 2017 at 2:21 PM, Mike Drob  wrote:
>
> > I have concern about the DataFu process of removing committers due to
> > inactivity, as outlined on this wiki page -
> > https://cwiki.apache.org/confluence/display/DATAFU/Becoming+a+Committer
> >
> > How often has this process been used?
> >
> > At many Apache projects, merit is considered to never expire.
> Circumstances
> > can pull people away from projects for a period of time, I would hope
> that
> > if somebody is able to return they are warmly welcomed back.
> >
> >
> > Mike
> >
> > On Tue, Oct 3, 2017 at 4:13 PM, Raphael Bircher <
> rbircherapa...@gmail.com>
> > wrote:
> >
> > > Hi Matthew
> > >
> > > You have 14 Committers, but only 4 for the proposed PMC?
> > >
> > > Regards Raphael
> > >
> > >
> > > Am .10.2017, 22:45 Uhr, schrieb Matthew Hayes :
> > >
> > > Hi,
> > >>
> > >> I would like to kick off a discussion regarding Apache DataFu's
> > graduation
> > >> from incubator.  In the community vote
> > >> <http://mail-archives.apache.org/mod_mbox/incubator-datafu-d
> > >> ev/201708.mbox/%3CCAA4Vo8CNf0sVw0veP2GdV9VN%3DaP5-Q8kstgY%
> > >> 2B0xM48kNuJMFWw%40mail.gmail.com%3E>
> > >> there was consensus to graduate to TLP status.
> > >>
> > >> Apache DataFu began incubating Jan 5th, 2014.  Since then we have
> made 3
> > >> releases and added 4 committers.  The Apache DataFu website
> > >> <http://datafu.incubator.apache.org/> includes documentation such as
> a
> > >> getting started page and guides for various methods.
> > >>
> > >> Project status:
> > >> http://incubator.apache.org/projects/datafu.html
> > >>
> > >> Project website:
> > >> http://datafu.incubator.apache.org/
> > >>
> > >> JIRA:
> >

Re: [DISCUSSION] Apache DataFu podling graduation

[Mike Drob]

I have concern about the DataFu process of removing committers due to
inactivity, as outlined on this wiki page -
https://cwiki.apache.org/confluence/display/DATAFU/Becoming+a+Committer

How often has this process been used?

At many Apache projects, merit is considered to never expire. Circumstances
can pull people away from projects for a period of time, I would hope that
if somebody is able to return they are warmly welcomed back.


Mike

On Tue, Oct 3, 2017 at 4:13 PM, Raphael Bircher 
wrote:

> Hi Matthew
>
> You have 14 Committers, but only 4 for the proposed PMC?
>
> Regards Raphael
>
>
> Am .10.2017, 22:45 Uhr, schrieb Matthew Hayes :
>
> Hi,
>>
>> I would like to kick off a discussion regarding Apache DataFu's graduation
>> from incubator.  In the community vote
>> > ev/201708.mbox/%3CCAA4Vo8CNf0sVw0veP2GdV9VN%3DaP5-Q8kstgY%
>> 2B0xM48kNuJMFWw%40mail.gmail.com%3E>
>> there was consensus to graduate to TLP status.
>>
>> Apache DataFu began incubating Jan 5th, 2014.  Since then we have made 3
>> releases and added 4 committers.  The Apache DataFu website
>>  includes documentation such as a
>> getting started page and guides for various methods.
>>
>> Project status:
>> http://incubator.apache.org/projects/datafu.html
>>
>> Project website:
>> http://datafu.incubator.apache.org/
>>
>> JIRA:
>> https://issues.apache.org/jira/projects/DATAFU
>>
>> Maturity Evaluation:
>> https://cwiki.apache.org/confluence/display/DATAFU/Maturity+
>> Evaluation
>>
>> A draft of the board resolution can be found at the bottom of this email.
>>
>> Proposed PMC size: 4
>> Total number of committers: 14
>>
>> PMC affiliation (* indicates chair):
>>
>> Paypal:
>>   - Eyal Allweil
>>
>> Pivotal:
>> - Roman Shaposhnik
>>
>> SkipFlag:
>>   - (*) Matthew Hayes
>> - Sam Shah
>>
>> Here are some project statistics since entering graduation on Jan 5th,
>> 2014:
>>
>> - 131 commits
>> - 3 releases
>> - 21 unique contributors
>> - 4 committers added
>> - 130 issues created
>> - 82 issues closed
>>
>> Resolution:
>>
>> 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, consisting of well-tested libraries that help developers
>>
>> solve common data problems in Hadoop and similar distributed
>>
>> systems.
>>
>>
>>
>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
>>
>> Committee (PMC), to be known as the "Apache DataFu Project",
>>
>> be and hereby is established pursuant to Bylaws of the
>>
>> Foundation; and be it further
>>
>>
>>
>> RESOLVED, that the Apache DataFu Project be and hereby is
>>
>> responsible for the creation and maintenance of libraries that
>>
>>  help solve common data problems and work with large-scale data
>>
>> in Hadoop and similar distributed systems; and be it further RESOLVED,
>>
>> that the office of Vice President, Apache DataFu" 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 DataFu Project,
>>
>> and to have primary responsibility for management of the projects
>>
>> within the scope of responsibility of the Apache DataFu 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 DataFu Project:
>>
>>- Eyal Allweil eyal at apache dot org
>>- Matthew Hayes mhayes at apache dot org
>>- Roman Shaposhnik rvs at apache dot org
>>- Sam Shah samshah at apache dot org
>>
>>
>> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Matthew Hayes
>>
>> be appointed to the office of Vice President, Apache DataFu, 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 DataFu 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 DataFu Project; and be it further
>>
>>
>>
>> RESOLVED, that the Apache DataFu Project be and hereby
>>
>> is tasked with the migration and rationalization of the Apache
>>
>> Incubator DataFu podling; and be it further
>>
>>
>>
>> RESOLVED, that all responsibilities pertaining to the Apache
>>
>> Incubator DataFu podling encumbered upon the Apache Incubator
>>
>> Project are hereafter discharged.
>>
>
>
> --
> My introduction https://youtu.be/Ln4vly5sxYU
>
> -

Re: [RESULT][VOTE] Apache HTrace 4.3.0 incubating release (rc3)

[Mike Drob]

HTRACE-400

On Wed, Aug 16, 2017 at 2:11 PM, John D. Ament 
wrote:

> Mike
>
> Did you see my notes about the war file?
>
> On Aug 16, 2017 12:51 PM, "Mike Drob"  wrote:
>
> > Sorry for the long turnaround, realized I never sent the tally email.
> >
> > This vote passes with 3 +1: Billie, Justin, and Josh.
> >
> > Thanks all for taking a look!
> >
> > On 2017-06-02 15:11, Mike Drob  wrote:
> > > Hi IPMC,
> > >
> > > Please consider the release of Apache HTrace 4.3.0 Incubating
> > >
> > >
> > >
> > > Project [VOTE]:
> > >
> > > https://lists.apache.org/thread.html/6e60ba2574a853da59c3a150f18cd9
> > bbd52051785380a7cc837b583e@%3Cdev.htrace.apache.org%3E
> > >
> > > Project [RESULT][VOTE]:
> > >
> > > https://lists.apache.org/thread.html/fb2a68fcd9c80d9db4a483794112ae
> > cde486ca263384dec0bad38c34@%3Cdev.htrace.apache.org%3E
> > >
> > > Artifacts staged at:
> > >
> > > http://people.apache.org/~mdrob/htrace-4.3.0-incubating-rc3/
> > >
> > > Staging maven repository at:
> > >
> > > https://repository.apache.org/content/repositories/
> orgapachehtrace-1029
> > >
> > > Source tree:
> > >
> > > https://git-wip-us.apache.org/repos/asf?p=incubator-htrace.
> git;a=tree;h=
> > 2ca8767b38c83f0d2f46ce7f91373d9df69f7fb8;hb=
> a47398aea8d65fb544faba150beb49
> > bb7654cb49
> > >
> > >
> > > Please download and evaluate the release candidate.
> > >
> > > This vote will remain open for minimum 5 days
> > >
> > > [ ] +1 Approve the release
> > >
> > > [ ] +0 No opinion
> > >
> > > [ ] -1 Do not approve the release because ...
> > >
> > >
> > > Thanks,
> > >
> > > Mike
> > >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [RESULT][VOTE] Apache HTrace 4.3.0 incubating release (rc3)

[Mike Drob]

Sorry for the long turnaround, realized I never sent the tally email.

This vote passes with 3 +1: Billie, Justin, and Josh.

Thanks all for taking a look!

On 2017-06-02 15:11, Mike Drob  wrote: 
> Hi IPMC,
> 
> Please consider the release of Apache HTrace 4.3.0 Incubating
> 
> 
> 
> Project [VOTE]:
> 
> https://lists.apache.org/thread.html/6e60ba2574a853da59c3a150f18cd9bbd52051785380a7cc837b583e@%3Cdev.htrace.apache.org%3E
> 
> Project [RESULT][VOTE]:
> 
> https://lists.apache.org/thread.html/fb2a68fcd9c80d9db4a483794112aecde486ca263384dec0bad38c34@%3Cdev.htrace.apache.org%3E
> 
> Artifacts staged at:
> 
> http://people.apache.org/~mdrob/htrace-4.3.0-incubating-rc3/
> 
> Staging maven repository at:
> 
> https://repository.apache.org/content/repositories/orgapachehtrace-1029
> 
> Source tree:
> 
> https://git-wip-us.apache.org/repos/asf?p=incubator-htrace.git;a=tree;h=2ca8767b38c83f0d2f46ce7f91373d9df69f7fb8;hb=a47398aea8d65fb544faba150beb49bb7654cb49
> 
> 
> Please download and evaluate the release candidate.
> 
> This vote will remain open for minimum 5 days
> 
> [ ] +1 Approve the release
> 
> [ ] +0 No opinion
> 
> [ ] -1 Do not approve the release because ...
> 
> 
> Thanks,
> 
> Mike
> 

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

Re: [DISCUSS] Daffodil Incubation Proposal

[Mike Drob]

What is the relationship between Daffodil and something like Apache Tika's
extraction engine?

On Mon, Jul 24, 2017 at 9:53 AM, Steve Lawrence <
stephen.d.lawre...@gmail.com> wrote:

> Dear Apache Incubator Community,
>
> We would like to start a discussion around a proposal to bring Daffodil
> into the Apache Incubator. Daffodil is a implementation of the DFDL
> specification used to convert between fixed format data and XML/JSON.
>
> The draft proposal can be found in the wiki at the following URL:
>
> https://wiki.apache.org/incubator/DaffodilProposal
>
> We do not yet have a champion or mentors, but it was recommended that we
> create a proposal and send it to this list to potentially find those
> that might be interested. The text for the draft proposal is found
> below. We look forward to your input.
>
> Thanks,
> -Steve
>
>
> = Daffodil Proposal =
>
> == Abstract ==
>
> Daffodil is an implementation of the Data Format Description Language
> (DFDL) used to convert between fixed format data and XML/JSON.
>
> == Proposal ==
>
> The Data Format Description Language (DFDL) is a specification,
> developed by the Open Grid Forum, capable of describing many data
> formats, including both textual and binary, scientific and numeric,
> legacy and modern, commercial record-oriented, and many industry and
> military standards. It defines a language that is a subset of W3C XML
> schema to describe the logical format of the data, and annotations
> within the schema to describe the physical representation.
>
> Daffodil is an open source implementation of the DFDL specification that
> uses these DFDL schemas to parse fixed format data into an infoset,
> which is most commonly represented as either XML or JSON. This allows
> the use of well-established XML or JSON technologies and libraries to
> consume, inspect, and manipulate fixed format data in existing
> solutions. Daffodil is also capable of the reverse by serializing or
> "unparsing" an XML or JSON infoset back to the original data format.
>
> == Background ==
>
> Many different software solutions need to consume and manage data,
> including data directed routing, databases, data analysis, data
> cleansing, data visualizing, and more. A key aspect of such solutions is
> the need to transform the data into an easily consumable format.
> Usually, this means that for each unique data format, one develops a
> tool that can read and extract the necessary information, often leading
> to ad-hoc and data-format-specific description systems. Such systems are
> often proprietary, not well tested, and incompatible, leading to vendor
> lock-in, flawed software, and increased training costs. DFDL is a new
> standard, with version 1.0 completed in October of 2016, that solves
> these problems by defining an open standard to describe many different
> data formats and how to parse and unparse between the data and XML/JSON.
>
> Two closed source implementations of DFDL currently exist. The first was
> created by IBM and is now part of their IBM® Integration Bus product.
> The second was created by the European Space Agency, called DFDL4S or
> "DFDL for Space" targeted at the challenges of their satellite data
> processing.
>
> Around 2005, Pacific Northwest National Lab created Defuddle, built as
> an open source implementation and proof of concept of the draft DFDL
> specification and a test bed to feed new concepts into specification
> development. Primary development of Defuddle was eventually taken over
> by the National Center for Supercomputing Applications (NCSA). However,
> due to evolution of the DFDL specification and architectural and
> performance issues with Defuddle, around 2009, NCSA restarted the
> project with the new name of Daffodil, with a goal of implementing the
> complete DFDL specification. Daffodil development continued at NCSA
> until around 2012, at which point development slowed due to budget
> limitations. Shortly thereafter, primary development was picked up by
> Tresys Technology where it continues today, with contributions from
> other entities such as the Navy Research Lab, the Air Force Research
> Lab, MITRE, and Booz Allen Hamilton. In February of 2015, Daffodil
> version 1.0.0 was released, including support for the DFDL features
> needed to parse many common file formats. Daffodil version 2.0.0 is
> expected to be released in August of 2017, which will include unparse
> support with one-to-one parsing feature parity.
>
> Entities including IBM, MITRE, NATO NCI Agency, Northrop-Grumman, Quark
> Security, Raytheon, and Tresys Technology have developed DFDL schemas
> for many data formats from varying technology domains, including PNG,
> GIF, BMP, PCAP, HL7, EDIFACT, NACHA, vCard, iCalendar, and MIL-STD-2045,
> many of which are publicly available on the DFDL Schemas github. There
> are also a number of military-application data formats, the
> specifications of which are not public, which have historically been
> very difficult and expensive t

Re: podling artifacts in maven: GAV names, disclaimer?

[Mike Drob]

I've often seen that the version includes -incubating.

On Tue, Jul 18, 2017 at 11:05 AM, John D. Ament 
wrote:

> Dale,
>
> My stance is that only the source artifact has to include "-incubating",
> the maven convenience binaries do not.
>
> John
>
> On Tue, Jul 18, 2017 at 11:10 AM Dale LaBossiere 
> wrote:
>
> > Hi,
> >
> > What are the requirements on group, artifact, version coordinates for
> > podling artifacts in a maven repo with respect to “incubating” tagging?
> >
> > Generally, [1] indicates a requirement to include “incubating” in release
> > bundle names.
> > We (Edgent) did that for our convenience binary bundle too, but not the
> > jars in the bundle.
> >
> > We’re now working towards releasing individual convenience binaries
> (jars)
> > in maven central.
> > The general info on maven repo artifacts [2] and [3] doesn’t add any
> > clarity and I can’t locate any incubator specific info on the
> coordinates.
> >
> > Also, must each binary release artifact jar contain the disclaimer?
> >
> > Thanks,
> > — Dale
> >
> > [1] http://incubator.apache.org/policy/incubation.html#releases <
> > http://incubator.apache.org/policy/incubation.html#releases>
> > [2] http://www.apache.org/dev/repository-faq.html <
> > http://www.apache.org/dev/repository-faq.html>
> > [3] http://www.apache.org/dev/publishing-maven-artifacts.html <
> > http://www.apache.org/dev/publishing-maven-artifacts.html>
>

Re: Images in source code.

[Mike Drob]

Project logos are Apache Licensed, but cannot be used for "any purpose" I
thought? They're specifically called out and most uses of trademark logos
need to be approved by VP Brand.

https://www.apache.org/foundation/marks/

On Sun, Jun 4, 2017 at 9:09 AM, Ted Dunning  wrote:

> What does subverted by Salesforce even mean here?
>
> Any Apache licensed material can be "subverted" by pretty much anybody if
> subverted means use for any purpose they feel like.
>
> On Jun 4, 2017 14:49, "Martin Gainty"  wrote:
>
> > is there anyway to run maven-rat-plugin to make sure ASF licensed assets
> > are *not* being subverted by salesforce
> >
> >
> > http://creadur.apache.org/rat/apache-rat-plugin/rat-mojo.html
> >
> >
> > Apache Rat™ Plugin for Apache Maven – apache-rat:rat > apache.org/rat/apache-rat-plugin/rat-mojo.html>
> > creadur.apache.org
> > apache-rat:rat. Note:This goal should be used as a Maven report. Full
> > name: org.apache.rat:apache-rat-plugin:0.13-SNAPSHOT:rat. Description:
> >
> > ?
> >
> > Martin
> > __
> >
> >
> >
> > 
> > From: John D. Ament 
> > Sent: Saturday, June 3, 2017 9:46 AM
> > To: general@incubator.apache.org
> > Subject: Re: Images in source code.
> >
> > On Fri, Jun 2, 2017 at 8:20 PM Craig Russell 
> wrote:
> >
> > > Hi James,
> > >
> > > Everything that is not explicitly called out in the top level NOTICE
> and
> > > LICENSE files are licensed under the Apache 2.0 license.
> > >
> > > Adding a file to this directory might mislead people into thinking that
> > > they need to perform more due diligence with other files in other
> > > directories.
> > >
> > > My advice is to *not* add anything. Let the images be licensed per the
> > > terms the top level LICENSE file.
> > >
> >
> > Agreed.  What we do like to make sure is called out is if there is
> > provenance that these images came from somewhere else.  If these images
> > were not created by you and were not already under apache license, then
> we
> > would have a concern.
> >
> >
> > >
> > > Craig
> > >
> > > > On Jun 2, 2017, at 2:20 PM, James Bognar <
> james.bog...@salesforce.com>
> > > wrote:
> > > >
> > > > Thanks!
> > > >
> > > > I haven't found a metadata editor that works yet, so I'll just add a
> > > > LICENSE.txt file to the directory.  Hopefully that's enough.
> > > >
> > > > On Fri, Jun 2, 2017 at 4:48 PM, Josh Elser 
> wrote:
> > > >
> > > >> On 6/2/17 1:15 PM, James Bognar wrote:
> > > >>
> > > >>> I just added several png files to the source tree of our podling.
> I
> > > >>> created them myself.  Are there any best-practices on how to mark
> > > these as
> > > >>> Apache licensed?
> > > >>>
> > > >>>
> > > >> I'm not sure of a good way to track this. I'm not sure if png
> supports
> > > >> arbitrary metadata which could be edited. Some ways I've seen used
> > > >> elsewhere to try to better propagate license/ownership:
> > > >>
> > > >> * Comments on the issue-tracker issue that introduced them citing
> > > >> origin/source (typically for images that are copied, not created)
> > > >> * Entry in LICENSE/NOTICE (shouldn't be done unnecessarily, of
> course)
> > > >> * A README in the same directory with relevant info
> > > >>
> > > >> If the images are of the podling's creation, I wouldn't be
> > particularly
> > > >> worried. The copyright notice on your source-release and LICENSE are
> > > >> sufficient to inform downstream consumers.
> > > >>
> > > >> Probably not the answer you're looking for, but hope it helps :)
> > > >>
> > > >> - Josh
> > > >>
> > > >> 
> -
> > > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > >> For additional commands, e-mail: general-h...@incubator.apache.org
> > > >>
> > > >>
> > > >
> > > >
> > > > --
> > > > James Bognar
> > >
> > > Craig L Russell
> > > c...@apache.org
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

[VOTE] Apache HTrace 4.3.0 incubating release (rc3)

[Mike Drob]

Hi IPMC,

Please consider the release of Apache HTrace 4.3.0 Incubating



Project [VOTE]:

https://lists.apache.org/thread.html/6e60ba2574a853da59c3a150f18cd9bbd52051785380a7cc837b583e@%3Cdev.htrace.apache.org%3E

Project [RESULT][VOTE]:

https://lists.apache.org/thread.html/fb2a68fcd9c80d9db4a483794112aecde486ca263384dec0bad38c34@%3Cdev.htrace.apache.org%3E

Artifacts staged at:

http://people.apache.org/~mdrob/htrace-4.3.0-incubating-rc3/

Staging maven repository at:

https://repository.apache.org/content/repositories/orgapachehtrace-1029

Source tree:

https://git-wip-us.apache.org/repos/asf?p=incubator-htrace.git;a=tree;h=2ca8767b38c83f0d2f46ce7f91373d9df69f7fb8;hb=a47398aea8d65fb544faba150beb49bb7654cb49


Please download and evaluate the release candidate.

This vote will remain open for minimum 5 days

[ ] +1 Approve the release

[ ] +0 No opinion

[ ] -1 Do not approve the release because ...


Thanks,

Mike

[RESULT][VOTE] HTrace 4.2-incubating release

[Mike Drob]

This vote passes with 5 +1 votes as follows:

4 IPMC +1 this vote (John D. Ament, Jake Farrell, Justin Mclean, Jean-Baptiste 
Onofre)
1 IPMC +1 on the previous vote (Michael Stack)

Thank you to those who have participated!

Mike

On 2016-09-30 12:16 (-0500), "Mike Drob" wrote: 
> Resending this after being told that I used an incorrect subject format.
> 
> On 2016-09-29 21:20 (-0500), "Mike Drob" wrote: 
> > Dear IPMC, please vote on our latest release candidate as an Apache 
> > Incubator project.
> > 
> > Apache HTrace (incubating), has voted to release the below referenced 
> > Apache HTrace 4.2.0-incubating release candidate.
> > 
> > Vote thread here:
> > https://lists.apache.org/thread.html/4123e994c752eabaf3f11d5ca13af4182530f001f7a5cbd52862@%3Cdev.htrace.apache.org%3E
> > 
> > And results thread here:
> > https://lists.apache.org/thread.html/6dfe32eaa84ff36519816029e730e7a5ae9d5ab13ecc1d686fff@%3Cdev.htrace.apache.org%3E
> > 
> > The source tarball, hashes, and signing are here:
> > https://dist.apache.org/repos/dist/dev/incubator/htrace/htrace-4.2.0RC0/
> > 
> > Related maven artifacts are posted here:
> > https://repository.apache.org/content/repositories/orgapachehtrace-1017
> > 
> > The tag for the RC is here:
> > https://git-wip-us.apache.org/repos/asf?p=incubator-htrace.git;a=tree;h=7db3ed8cd93ed49366b518474a44d9267742960e;hb=7c0ae16b71683b71908cae0e59472f3a92074c19
> > 
> > The KEYS file with the key used signing is available here:
> > https://dist.apache.org/repos/dist/dev/incubator/htrace/KEYS
> > 
> > The vote will be open for 72 hours.
> > 
> > [ ] +1 Release this package as Apache HTrace 4.2.0-incubating
> > [ ] +0 no opinion
> > [ ] -1 Do not release this package because ...
> > 
> > Thanks,
> > Mike
> > 
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> > 
> > 
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 
> 

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

Re: [VOTE] HTrace 4.2-incubating release

[Mike Drob]

Justin,

Yes, the compilation issue is MSHADE-148, also captured in HTRACE-236. [1]

Although MSHADE-148 is resolved, you can see discussion towards the end of the 
JIRA that identifies it as still a problem for HTrace and others. For now, the 
workaround is to either build with Maven 3.0.4, which I will agree is 
inconvenient and needs to be better documented.

I will file JIRA issues for your other suggestions shortly.

Mike

[1]: https://issues.apache.org/jira/browse/HTRACE-236 

On 2016-09-30 21:40 (-0500), Justin Mclean  wrote: 
> Hi,
> 
> +0 binding as I had issues compiling (see below). Happy to change to +1 if I 
> can compile everything else is good.
> 
> I checked:
> - incubating in name
> - signature and hashes good
> - DISCLAIMER exists
> - LICENSE is missing MIT licensed normalise.css bundled in several bootstrap 
> files. e.g. [2]. Please fix for net release.
> - NOTICE good
> - All Apache files have ASF header
> - No unexpended binary files
> - Can’t compile
> 
> You may want to remove the copyright line from this ASF header [1]
> 
> The compile seem to get stuck in an infinite loop at this point:
> [INFO] Replacing original artifact with shaded artifact.
> [INFO] Replacing 
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/target/htrace-hbase-4.2.0-incubating.jar
>  with 
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/target/htrace-hbase-4.2.0-incubating-shaded.jar
> [INFO] Dependency-reduced POM written at: 
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/dependency-reduced-pom.xml
> [INFO] Dependency-reduced POM written at: 
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/dependency-reduced-pom.xml
> [INFO] Dependency-reduced POM written at: 
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/dependency-reduced-pom.xml
> [INFO] Dependency-reduced POM written at: 
> /Users/justinmclean/Downloads/ApacheHtrace/htrace-4.2.0-incubating/htrace-hbase/dependency-reduced-pom.xml
> …
> 
> Issue may be related to this bug? [3] However changing the pom to use shade 
> 2.4.1 didn’t fix the issue.
> 
> Thanks,
> Justin
> 
> 1. ./bin/gen_thrift.sh
> 2. ./htrace-htraced/go/web/lib/bootstrap-3.3.1/css/bootstrap.css
> 3. https://issues.apache.org/jira/browse/MSHADE-148
> 
> 
> -
> 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

[VOTE] HTrace 4.2-incubating release

[Mike Drob]

Resending this after being told that I used an incorrect subject format.

On 2016-09-29 21:20 (-0500), "Mike Drob" wrote: 
> Dear IPMC, please vote on our latest release candidate as an Apache Incubator 
> project.
> 
> Apache HTrace (incubating), has voted to release the below referenced Apache 
> HTrace 4.2.0-incubating release candidate.
> 
> Vote thread here:
> https://lists.apache.org/thread.html/4123e994c752eabaf3f11d5ca13af4182530f001f7a5cbd52862@%3Cdev.htrace.apache.org%3E
> 
> And results thread here:
> https://lists.apache.org/thread.html/6dfe32eaa84ff36519816029e730e7a5ae9d5ab13ecc1d686fff@%3Cdev.htrace.apache.org%3E
> 
> The source tarball, hashes, and signing are here:
> https://dist.apache.org/repos/dist/dev/incubator/htrace/htrace-4.2.0RC0/
> 
> Related maven artifacts are posted here:
> https://repository.apache.org/content/repositories/orgapachehtrace-1017
> 
> The tag for the RC is here:
> https://git-wip-us.apache.org/repos/asf?p=incubator-htrace.git;a=tree;h=7db3ed8cd93ed49366b518474a44d9267742960e;hb=7c0ae16b71683b71908cae0e59472f3a92074c19
> 
> The KEYS file with the key used signing is available here:
> https://dist.apache.org/repos/dist/dev/incubator/htrace/KEYS
> 
> The vote will be open for 72 hours.
> 
> [ ] +1 Release this package as Apache HTrace 4.2.0-incubating
> [ ] +0 no opinion
> [ ] -1 Do not release this package because ...
> 
> Thanks,
> Mike
> 
> -
> 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

VOTE: HTrace 4.2-incubating release

[Mike Drob]

Dear IPMC, please vote on our latest release candidate as an Apache Incubator 
project.

Apache HTrace (incubating), has voted to release the below referenced Apache 
HTrace 4.2.0-incubating release candidate.

Vote thread here:
https://lists.apache.org/thread.html/4123e994c752eabaf3f11d5ca13af4182530f001f7a5cbd52862@%3Cdev.htrace.apache.org%3E

And results thread here:
https://lists.apache.org/thread.html/6dfe32eaa84ff36519816029e730e7a5ae9d5ab13ecc1d686fff@%3Cdev.htrace.apache.org%3E

The source tarball, hashes, and signing are here:
https://dist.apache.org/repos/dist/dev/incubator/htrace/htrace-4.2.0RC0/

Related maven artifacts are posted here:
https://repository.apache.org/content/repositories/orgapachehtrace-1017

The tag for the RC is here:
https://git-wip-us.apache.org/repos/asf?p=incubator-htrace.git;a=tree;h=7db3ed8cd93ed49366b518474a44d9267742960e;hb=7c0ae16b71683b71908cae0e59472f3a92074c19

The KEYS file with the key used signing is available here:
https://dist.apache.org/repos/dist/dev/incubator/htrace/KEYS

The vote will be open for 72 hours.

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

Thanks,
Mike

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