Re: [QUESTION] Rewriting history

[Kevin A. McGrail]

To me, binaries not released by the ASF should not be necessary to keep 
in multiple repos so this is a project PMC decision.


On 11/20/2015 11:02 AM, Hadrian Zbarcea wrote:

Probably a bad subject in the context of other things going on :).

Apache Brooklyn is faced with the tasks of migrating it's repo(s) post 
graduation and there are some very large *pre-incubation* artifacts in 
the git repo that we would like removed.


The question was asked on general@ [1] many moons ago, but received no 
answer (the original thread [1] indicates the offenders). We'd like to 
use this occasion to split the git repo into multiple smaller once 
(more naturally tailored to the project), so one idea would be, I 
think, to leave incubator-brooklyn.git as is and just extract what we 
need (everything except the large binaries) in new repos. Note: 
afaiui, those artifacts we're never part of an ASF release.


I am not sure what would be acceptable per ASF (intensely debated) 
policies.


Thoughts?
Hadrain


[1] 
https://mail-archives.apache.org/mod_mbox/incubator-brooklyn-dev/201506.mbox/%3c556f0973.7030...@cloudsoftcorp.com%3E




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

[VOTE] Accept ECharts for Apache Incubation

[Kevin A. McGrail]

sang shenyi@gmail.com )

    Zhang Wenli (https://github.com/Ovilia m...@zhangwenli.com )

    Li Deqing (https://github.com/deqingli annong...@gmail.com)

    Dong Rui (https://github.com/erik168 error...@gmail.com)

Alignment

ECharts is popular in data visualization and charting on web projects. 
And ASF has many famous web projects and big data related projects. We 
believe that ASF is a perfect choice to help ECharts project to attract 
more developers and have more cooperation with existing projects.


Known Risks

Orphaned products

Given the current level of investment in ECharts and the stakeholders 
using it - the risk of the project being abandoned is minimal. Baidu, 
for example, is in active development to use ECharts in many of its 
services and many large corporations including Alibaba, Tencent, Huawei, 
Sina, Lenovo use it in their production applications.


Inexperience with Open Source

ECharts has been an active open source project for more than 4 years. 
During that time, the project has attracted 50+ contributors.


Homogenous Developers

The most of core developers are from Baidu, but after ECharts was open 
sourced, ECharts received a lot of bug fixes and enhancements from other 
developers not working at Baidu. And the founder of ECharts,Lin Zhifeng 
still contributes a lot after he left Baidu.


Reliance on Salaried Developers

Although some of the developers are salaried, the project is personally 
initiated from the beginning. The core developers have been dedicated to 
this project for four years and have kept the project independent with 
developers around the world involved.


Relationships with Other Apache Products

There are several existing Apache projects that using ECharts already, 
including:


    Apache Eagle
    Apache Griffin (Incubating)
    Apache Kylin

    Apache SkyWalking (Incubating)

A Excessive Fascination with the Apache Brand

Our interests and motivations are based on the factors mentioned in the 
Rationale section rather than the publicity. Furthermore, the brand of 
ECharts has been successful in the past years on their own and we would 
be happy to keep on this path. We are honored at getting the opportunity 
to join the ASF, with the understanding to ensure its brand policies are 
respected.Also we expect that Apache brand will help to attract more 
contributors.


Documentation

[1] Data Visualization: https://en.wikipedia.org/wiki/Data_visualization

[2] ECharts Extensions: https://github.com/ecomfe/ECharts#resources

[3] ECharts Information: https://github.com/ecomfe/ECharts 
https://ecomfe.github.io/echarts-doc/public/en/index.html


[4] ECharts in NPM: https://www.npmjs.com/package/echarts

[5] GitHub Data Visualization Topic: 
https://github.com/topics/data-visualization


Initial Source

ECharts has been developed since 2013. It currently has an active 
developer and user community with a codebase in JavaScript. We currently 
use Github to maintain our source code and track issues at 
https://github.com/ecomfe/ECharts We need to move our respository to 
Apache infrastructure.


Source and Intellectual Property Submission Plan

ECharts source code is available under BSD-3 license and owned by Baidu. 
We will work with the committers to get ICLAs signed. We will provide a 
Software Grant Agreement from an authorized signer per 
https://www.apache.org/licenses/software-grant-template.pdf


External Dependencies

All The dependencies are released under Apache compatible licenses, 
including BSD and MIT.


Required Resources

Mailing List:

There are currently no mailing lists. The usual mailing lists are 
expected to be set up when entering incubation:


priv...@echarts.incubator.apache.org

d...@echarts.incubator.apache.org

comm...@echarts.incubator.apache.org

Git Repositories:

Upon entering incubation: https://github.com/apache/incubator-echarts 
After incubation, we want to move the existing repo from 
github/ecomfe/echarts to Apache infrastructure.


Issue Tracking:

ECharts currently uses GitHub to track issues. there are more than 7k 
issues. Would like to continue to do so while we discuss migration 
possibilities with the ASF Infra committee.


URL:

Currently the website url is 
https://ecomfe.github.io/echarts-doc/public/en/index.html. It will be 
moved to http://echarts.incubator.apache.org/ to follow incubator 
conventions.


Initial Committers

    Lin Zhifeng (https://github.com/kener kener.linf...@gmail.com)

    Su Shuang (https://github.com/100pah sushuang0...@gmail.com)

    Shen Yi (https://github.com/pissang shenyi@gmail.com)

    Zhang Wenli (https://github.com/Ovilia m...@zhangwenli.com)

    Li Deqing (https://github.com/deqingli annong...@gmail.com)
    Wang Junting

    Dong Rui (https://github.com/erik168 error...@gmail.com)

    Huang Houjin (https://github.com/chriswong w...@foxmail.com)

Sponsors:

Champion:

    Kevin A. McGrail

Mentors:

    Daniel Gruno

    Kevin A. McGrail
    Dave Fisher
    John D. A

[RESULT] was [VOTE] Accept ECharts for Apache Incubation

[Kevin A. McGrail]

All,

Voting is now closed.  There were 19 +1's, 5 +1's that are binding.  No 
0 or -1's were received.


I look forward to helping ECharts and thank you again for your time and 
attention.


I am working through the process at 
https://incubator.apache.org/guides/mentor.html


Regards,
KAM

On 1/12/2018 8:09 AM, Kevin A. McGrail wrote:

Hi All,

I would like to start a VOTE & I vote +1 to bring the ECharts project 
in as an Apache incubator podling.


The ASF voting rules are described:

https://www.apache.org/foundation/voting.html

A vote for accepting a new Apache Incubator podling is a majority vote 
for which only Incubator PMC member votes are binding.


This vote will run for at least 72 hours. Please VOTE as follows
[ ] +1 Accept ECharts into the Apache Incubator
[ ] +0 Abstain.
[ ] -1 Do not accept ECharts into the Apache Incubator because ...

The proposal is listed below, but you can also access it on the wiki: 
https://wiki.apache.org/incubator/EChartsProposal


Regards,
KAM


ECharts Proposal

Abstract

ECharts is a charting and data visualization library written in 
JavaScript.


Proposal

ECharts provides a powerful, interactive charting and data 
visualization library and framework for web browser, mobile App and 
backend usage.


Background

A primary goal of data visualization is to communicate information 
clearly and efficiently via statistical graphics, plots and other 
graphics.


Numerical data may be presented in dots, lines, or bars, to visually 
communicate a quantitative message. Effective visualization helps 
users to analyze data .It makes complex data more readable, 
understandable.[1]


Now data visualization concerns mainly about presentation and 
propagation in web, ECharts uses JavaScript as its basic programing 
language. It brings great compatibility across multiple platforms, not 
only in web browsers, but also in mobile Apps via embedded web engine 
or in backend environment via the techniques of headless browser.


Rationale

ECharts encapsulates the underlying data transformation, control flow, 
visual encoding and rendering, receiving the visualization 
requirements with declarative language, and produces interactive 
charts and components. We will highlight the features below to 
illustrate the power that ECharts already has, and our concerns and 
our visions:


    User Diversity:

ECharts expects that its users are not only web developers, but also 
people with lesser programing skills. So ECharts enables users to 
describe data and settings with declarative language, which lowers the 
barrier but without losing the power, and benefit to transfer and store.


    Configurable Interactions:

ECharts has provided plenty of interactions and aims at providing 
more. Both human interactions and the interactions with upper program 
are supported and can be configurable.


    Large Data:

Although the browser environment and JavaScript bring some performance 
limits in visualizing large data or performing animations, ECharts 
have been adopting various optimization techniques to rise the upper 
limit of the amount of data that it can process, and keep improving 
the fluency of interactions and animations.


    Cross-Platform:

The underlying render engine of ECharts can be switched between 
HTMLCanvas, SVG, or VML, which provides good compatibility and brings 
opportunities to optimize performance according to different platform 
and usage scenarios. Besides, ECharts can also works in backend 
environment via headless techniques.


ECharts can be created using headless browsers to pregenerate reports 
on more powerful machines for better performance on resource-limited 
devices


    Extension and Customization:

ECharts provides extension mechanisms to make new types of chart and 
components, adopt other layout algorithms, or even adopt other render 
techniques. Various developers have contributed different types of 
extensions based on ECharts.[2]


Current Status

ECharts has been an open source project on GitHub[3] since 2013. 
Currently it has more than 20k stars, more than 50k monthly 
downloads[4] in NPM, and is one of the most popular repositories in 
topic of data visualization category in GitHub.[5] And it has been 
used in many products of Baidu and other companies such as Alibaba, 
Tencent, Netease, XinHua News Agency,National Bureau of Statistics of 
China, Sina, State Grid Corporation of China, Lenovo, Ctrip etc.


Meritocracy

The ECharts project already operates on meritocratic principles. It 
was originally created by Lin Zhifeng in 2013,adding developers 
worldwide and has accepted multiple major patches from a diverse set 
of contributors.


We will follow ASF meritocratic principles to encourage more 
developers to contribute in this project. We know that only active and 
committed developers from a diverse set of backgrounds can make 
ECharts a successful project. We are also improving the project 
documentation and code to 

Re: [VOTE] Accept Coral into the Apache Incubator

[Kevin A. McGrail]

 many useful
development tools including Apache Maven, Apache Log4J, and multiple
Apache Commons components. Coral supports the Apache Beam programming
model for user applications. We are currently working on supporting
the Apache Spark programming APIs as well.

=== An Excessive Fascination with the Apache Brand ===
We hope to make Coral a powerful system for data processing, meeting
various needs for different deployment characteristics, under a more
variety of environments. We see the limitations of simply putting code
on GitHub, and we believe the Apache community will help the growth of
Coral for the project to become a positively impactful and innovative
open source software. We believe Coral is a great fit for the Apache
Software Foundation due to the collaboration it aims to achieve from
the big data processing community.

== Documentation ==
The current documentation for Coral is at https://snuspl.github.io/coral/.

== Initial Source ==
The Coral codebase is currently hosted at https://github.com/snuspl/coral.

== External Dependencies ==
To the best of our knowledge, all Coral dependencies are distributed
under Apache compatible licenses. Upon acceptance to the incubator, we
would begin a thorough analysis of all transitive dependencies to
verify this fact and further introduce license checking into the build
and release process.

== Cryptography ==
Not applicable.

== Required Resources ==
=== Mailing Lists ===
We will operate two mailing lists as follows:
* Coral PMC discussions: priv...@coral.incubator.apache.org
* Coral developers: d...@coral.incubator.apache.org

=== Git Repositories ===
Upon incubation: https://github.com/apache/incubator-coral.
After the incubation, we would like to move the existing repo
https://github.com/snuspl/coral to the Apache infrastructure

=== Issue Tracking ===
Coral currently tracks its issues using the Github issue tracker:
https://github.com/snuspl/coral/issues. We plan to migrate to Apache
JIRA.

== Initial Committers ==
   * Byung-Gon Chun
   * Jeongyoon Eo
   * Geon-Woo Kim
   * Joo Yeon Kim
   * Gyewon Lee
   * Jung-Gil Lee
   * Sanha Lee
   * Wooyeon Lee
   * Yunseong Lee
   * JangHo Seo
   * Won Wook Song
   * Taegeon Um
   * Youngseok Yang

== Affiliations ==
   * SNU (Seoul National University)
 * Byung-Gon Chun
 * Jeongyoon Eo
 * Geon-Woo Kim
 * Gyewon Lee
 * Sanha Lee
 * Wooyeon Lee
 * Yunseong Lee
 * JangHo Seo
 * Won Wook Song
 * Taegeon Um
 * Youngseok Yang

   * LG
 * Jung-Gil Lee

   * Samsung
 * Joo Yeon Kim

   * Viva Republica
 * Geon-Woo Kim

== Sponsors ==
=== Champions ===
Byung-Gon Chun

=== Mentors ===
   * Hyunsik Choi
   * Byung-Gon Chun
   * Jean-Baptiste Onofré
   * Markus Weimer
   * Reynold Xin

=== Sponsoring Entity ===
The Apache Incubator


Thanks!
Byung-Gon Chun



--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project


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

Re: [PROPOSAL] Dubbo - proposal for Apache Incubation

[Kevin A. McGrail]

+1 binding

On 2/4/2018 10:28 PM, dongeforever wrote:

+1

2018-02-05 11:26 GMT+08:00 Jeff Zhang :


+1


Adam Feng 于2018年2月5日周一 上午11:00写道：


+1



Thanks.
Adam Feng

On 3 Feb 2018, 7:45 PM +0800, Huxing Zhang , wrote:

Dear Apache Incubator Community,

Please accept the following proposal for presentation and discussion:
https://wiki.apache.org/incubator/DubboProposal

Dubbo is a high-performance, lightweight, Java based RPC framework.
Dubbo offers three key features, which includes interface based remote
call, fault tolerance & load balancing, and automatic service
registration & discovery.

Any feedback from the incubator community is much appreciated.

I've attached the proposal below.

Best Regards,
Huxing

= Dubbo Proposal =

== Abstract ==

Dubbo is a high-performance, lightweight, java based RPC framework
open-sourced by Alibaba. As in many RPC systems, Dubbo is based around
the idea of defining a service, specifying the methods that can be
called remotely with their parameters and return types. On the server
side, the server implements this interface and runs a Dubbo server to
handle client calls. On the client side, the client has a stub that
provides the same methods as the server.

== Proposal ==

Dubbo has a fairly huge community today, and is widely adopted by many
companies and organizations, but most of them are in China. We believe
running Dubbo in Apache Software Foundation can facilitate development
of a stronger and more diverse community.

Alibaba submits this proposal to donate Dubbo's source code and its
side projects to the Apache Software Foundation. The code is already
under the Apache License Version 2.0. Dubbo source code and its side
projects are hosted on github right now:

* Dubbo code base: https://github.com/alibaba/dubbo
* Web site: https://github.com/dubbo/dubbo.github.io
* Documentations: User
Guide(http://dubbo.io/books/dubbo-user-book-en), Development
Guide(http://dubbo.io/books/dubbo-dev-book-en), Admin
Manual(http://dubbo.io/books/dubbo-admin-book-en)
* Other side projects hosted under dubbo group(

https://github.com/dubbo)

== Background ==

Dubbo was developed at Alibaba in 2011 and has been widely used in
many production lines there since then. Dubbo offers three key
features, which include interface based remote call, fault tolerance &
load balancing, and automatic service registration & discovery. Since
Dubbo is open-sourced on github, it's been received up to 15k stars,
and has been forked for more than 10k times. Besides being widely
adopted inside Alibaba, Dubbo is also used in approximately 80% of
internet companies in China, including JingDong(http://www.jd.com),
DangDang(http://www.dangdang.com), Qunar(https://www.qunar.com),
NetEase Kaola(https://www.kaola.com), etc. In 2017, Dubbo has won the
TOP 10 most popular open source projects in China for 2 consecutive
years since 2016.

We'd like to share this outstanding framework at the Apache Software
Foundation, and start developing a wider community through the Apache
way. We believe more people and organizations can be benefit from it
by doing so.

== Rationale ==

Remote procedure call (RPC) is one of the cornerstones to build
distributed systems, especially useful in today's e-commercial
industry and cloud computing providers. Dubbo is the java-based RPC
implementation. By using Dubbo, developers can call the remote service
just like call a local method but without worrying about the details
for the remote interaction. We expect more interesting features and
use cases to emerge from the community ranging from microservices to
cloud computing, and many other areas.

== Current Status ==

=== Meritocracy ===

The intent of this proposal is to start building a diverse developer
and user community around Dubbo following the ASF meritocracy model.
Since Dubbo was open sourced, many companies in China adopted Dubbo to
build up their own contributing system, moreover, we received many
enhancements or issue reports from them at the same time. The codebase
is now mainly managed by the development team inside Alibaba who's
responsible for building internal distributed system too. Any
suggestion or issue is discussed on
https://github.com/alibaba/dubbo/issues and more casual talk happens
in gitter channel (https://gitter.im/alibaba/dubbo). We plan to invite
more people as committers if they contribute to this project.

=== Community ===

Dubbo is currently being developed by the development team inside
Alibaba who's responsible for building internal distributed system
too. Since it's open-sourced, Dubbo is widely adopted by many other
companies including CNUCC (China Nets Union Clearing Corporation),
ICBC (Industrial and Commercial Bank of China), China Life Insurance,
DiDi, Qunar, Dangdang, NetEase Kaola, Maoyan Movie, GOME, Haier, CSDC
(China Securities Depository and Clearing Corporation Limited),
AsiaInfo, and many more. We hope to grow the base of contributors by
inviting all those who offer contributions and

Re: [IP CLEARANCE] Apache RocketMQ - RocketMQ CPP SDK project donation

[Kevin A. McGrail]

+1

On 2/8/2018 9:08 AM, Jim Jagielski wrote:

+1


On Feb 8, 2018, at 8:41 AM, yukon  wrote:

Hi all,

Apache RocketMQ has received a donation of RocketMQ CPP SDK.

RocketMQ CPP SDK is a stable, widely used C++ client SDK of Apache
RocketMQ, for Linux and Windows platform. It supports full features of
RocketMQ Java client and has played an important role in many distributed
applications of Alibaba Group.

The IP clearance form can be found here:

http://incubator.apache.org/ip-clearance/rocketmq-cpp-sdk.html

Please vote to approve this contribution. Lazy consensus applies: if
no -1 votes are cast within the next 72 hours, the vote passes.

Regards,
yukon


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



--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project


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

Re: [VOTE] Accept Dubbo into the Apache Incubator

[Kevin A. McGrail]

+1 binding (I may have voted twice.)
Regards,
KAM

On February 8, 2018 11:48:37 PM EST, Wang Xin  wrote:
>+1
>Xin Wang
>lovep...@hotmail.com
>
>
>
>在 2018年2月9日，上午11:02，vongosling
>mailto:fengji...@gmail.com>> 写道：
>
>+1 (non-binding)
>
>Great project, new journey round-the-world :-)
>
>Best Regards,
>Von Gosling
>
>2018-02-09 10:46 GMT+08:00 John D. Ament
>mailto:johndam...@apache.org>>:
>
>+1
>
>On Thu, Feb 8, 2018 at 9:10 PM Huxing Zhang
>mailto:hux...@apache.org>> wrote:
>
>Hi All,
>
>After some discussion on the Dubbo proposal, I'd like to start a
>vote on accepting Dubbo into the Apache Incubator.
>
>
>https://lists.apache.org/thread.html/1e4a74cc5af9cd0e298dc6085d5be5
>7da8dfd02fef1ebd33829a6084@%3Cgeneral.incubator.apache.org%3E
>
>The ASF voting rules are described:
>
>https://www.apache.org/foundation/voting.html
>
>A vote for accepting a new Apache Incubator podling is a majority vote
>for which only Incubator PMC member votes are binding.
>
>This vote will run for at least 72 hours. Please VOTE as follows
>[ ] +1 Accept Dubbo into the Apache Incubator
>[ ] +0 Abstain.
>[ ] -1 Do not accept Dubbo into the Apache Incubator because ...
>
>The proposal is listed below, but you can also access it on the wiki:
>https://wiki.apache.org/incubator/DubboProposal
>
>= Dubbo Proposal =
>
>== Abstract ==
>
>Dubbo is a high-performance, lightweight, java based RPC framework
>open-sourced by Alibaba. As in many RPC systems, Dubbo is based around
>the idea of defining a service, specifying the methods that can be
>called remotely with their parameters and return types. On the server
>side, the server implements this interface and runs a Dubbo server to
>handle client calls. On the client side, the client has a stub that
>provides the same methods as the server.
>
>== Proposal ==
>
>Dubbo has a fairly huge community today, and is widely adopted by many
>companies and organizations, but most of them are in China. We believe
>running Dubbo in Apache Software Foundation can facilitate development
>of a stronger and more diverse community.
>
>Alibaba submits this proposal to donate Dubbo's source code and its
>side projects to the Apache Software Foundation. The code is already
>under the Apache License Version 2.0.  Dubbo source code and its side
>projects are hosted on Github right now:
>
>* Dubbo code base: https://github.com/alibaba/dubbo
>* Web site: https://github.com/dubbo/dubbo.github.io
>* Documentations: User
>Guide(http://dubbo.io/books/dubbo-user-book-en), Development
>Guide(http://dubbo.io/books/dubbo-dev-book-en), Admin
>Manual(http://dubbo.io/books/dubbo-admin-book-en)
>* Other side projects hosted under dubbo group(https://github.com/dubbo
>)
>
>== Background ==
>
>Dubbo was developed at Alibaba in 2011 and has been widely used in
>many production lines there since then. Dubbo offers three key
>features, which include interface based remote call, fault tolerance &
>load balancing, and automatic service registration & discovery. Since
>Dubbo is open-sourced on github, it's been received up to 15k stars,
>and has been forked for more than 10k times. Besides being widely
>adopted inside Alibaba, Dubbo is also used in approximately 80% of
>internet companies in China, including JingDong(http://www.jd.com),
>DangDang(http://www.dangdang.com), Qunar(https://www.qunar.com),
>NetEase Kaola(https://www.kaola.com), etc. In 2017, Dubbo has won the
>TOP 10 most popular open source projects in China for 2 consecutive
>years since 2016.
>
>We'd like to share this outstanding framework at the Apache Software
>Foundation, and start developing a wider community through the Apache
>way. We believe more people and organizations can be benefit from it
>by doing so.
>
>== Rationale ==
>
>Remote procedure call (RPC) is one of the cornerstones to build
>distributed systems, especially useful in today's e-commercial
>industry and cloud computing providers. Dubbo is the java-based RPC
>implementation. By using Dubbo, developers can call the remote service
>just like call a local method but without worrying about the details
>for the remote interaction. We expect more interesting features and
>use cases to emerge from the community ranging from microservices to
>cloud computing, and many other areas.
>
>== Current Status ==
>
>=== Meritocracy ===
>
>The intent of this proposal is to start building a diverse developer
>and user community around Dubbo following the ASF meritocracy model.
>Since Dubbo was open sourced, many companies in China adopted Dubbo to
>build up their own contributing system, moreover, we received many
>enhancements or issue reports from them at the same time. The codebase
>is now mainly managed by the development team inside Alibaba who's
>responsible for building internal distributed system too. Any
>suggestion or issue is discussed on
>https://github.com/alibaba/dubbo/issues and more casual talk happens
>in gitter channel (https://gitte

Re: [DISCUSS] Apache Pinot Incubator Proposal

[Kevin A. McGrail]

Agreed.  It could use more mentors from ASF which I'm too overloaded to 
help with but I'd be inclined to +1 this.  Do you have some thoughts on 
getting more community people outside of LI and Uber to help?


On 2/13/2018 7:07 PM, Dave Fisher wrote:

Noir or Blanc? Gris or Grigio? What’s the vintage?

All kidding aside this looks interesting.

Regards,
Dave

Sent from my iPhone


On Feb 13, 2018, at 12:10 AM, kishore g  wrote:

Hello,

I would like to propose Pinot as an Apache Incubator project. The proposal
is available as a draft at https://wiki.apache.org/incubator/PinotProposal. I
have also included the text of the proposal below.

Any feedback from the community is much appreciated.

Regards,
Kishore G

= Pinot Proposal =

== Abstract ==

Pinot is a distributed columnar storage engine that can ingest data in
real-time and serve analytical queries at low latency. There are two modes
of data ingestion - batch and/or realtime. Batch mode allows users to
generate pinot segments externally using systems such as Hadoop. These
segments can be uploaded into Pinot via simple curl calls. Pinot can ingest
data in near real-time from streaming sources such as Kafka. Data ingested
into Pinot is stored in a columnar format. Pinot provides a SQL like
interface (PQL) that supports filters, aggregations, and group by
operations. It does not support joins by design, in order to guarantee
predictable latency. It leverages other Apache projects such as Zookeeper,
Kafka, and Helix, along with many libraries from the ASF.

== Proposal ==

Pinot was open sourced by LinkedIn and hosted on GitHub. Majority of the
development happens at LinkedIn with other contributions from Uber and
Slack. We believe that being a part of 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 Apache Software
Foundation. The code is already under Apache License 2.0.  Code and the
documentation are hosted on Github.
* Code: http://github.com/linkedin/pinot
* Documentation: https://github.com/linkedin/pinot/wiki


== Background ==

LinkedIn, similar to other companies, has many applications that provide
rich real-time insights to members and customers (internal and external).
The workload characteristics for these applications vary a lot. Some
internal applications simply need ad-hoc query capabilities with sub-second
to multiple seconds latency. But external site facing applications require
strong SLA even very high workloads. Prior to Pinot, LinkedIn had multiple
solutions depending on the workload generated by the application and this
was inefficient. Pinot was developed to be the one single platform that
addresses all classes of applications. Today at LinkedIn, Pinot powers more
than 50 site facing products with workload ranging from few queries per
second to 1000’s of queries per second while maintaining the 99th
percentile latency which can be as low as few milliseconds. All internal
dashboards at LinkedIn are powered by Pinot.

== Rationale ==

We believe that requirement to develop rich real-time analytic applications
is applicable to other organizations. Both Pinot and the interested
communities would benefit from this work being openly available.

== Current Status ==

Pinot is currently open sourced under the Apache License Version 2.0 and
available at github.com/linkedin/pinot. All the development is done using
GitHub Pull Requests. We cut releases on a weekly basis and deploy it at
LinkedIn. mp-0.1.468 is the latest release tag that is deployed in
production.

== Meritocracy ==

Following the Apache meritocracy model, we intend to build an open and
diverse community around Pinot. We will encourage the community to
contribute to discussion and codebase.

== Community ==

Pinot is currently used extensively at LinkedIn and Uber. Several companies
have expressed interest in the project. We hope to extend the contributor
base significantly by bringing Pinot into Apache.

== Core Developers ==

Pinot was started by engineers at LinkedIn, and now has committers from
Uber.

== Alignment ==

Apache is the most natural home for taking Pinot forward. Pinot leverages
several existing Apache Projects such as Kafka, Helix, Zookeeper, and Avro.
As Pinot gains adoption, we plan to add support for the ORC and Parquet
formats, as well as adding integration with Yarn and Mesos.

== Known Risks ==

=== Orphaned Products ===

The risk of the Pinot project being abandoned is minimal. The teams at
LinkedIn and Uber are highly incentivized to continue development of Pinot
as it is a critical part of their infrastructure.

=== Inexperience with Open Source ===

Post open sourcing, Pinot was completely developed on GitHub. All the
current developers on Pinot are well aware of the open source development
process. However, most of the developers are new to the Apache process.
Kishore Gopalakrishna, one of the lead developers in Pinot, is VP and
comm

Re: [VOTE] Resolution to graduate Apache FreeMarker to TLP

[Kevin A. McGrail]

+1 (binding)

On 2/20/2018 1:09 AM, Apache wrote:

+1 (binding)

Ralph


On Feb 19, 2018, at 3:45 AM, Jacopo Cappellato  wrote:

Hi all,

The FreeMarker community has discussed [1] and voted [2] positively on
graduating to a top level project (TLP). The resolution for the graduation
has been proposed and discussed in this list [3].
Information about FreeMarker can be found in the status page [4],
in the project maturity model [5] and in the website [6].

I am now calling a VOTE to ask the IPMC to recommend the resolution to the
ASF Board:
the proposed resolution can be found at the bottom of this email.
The vote will be open for 72 hours.

[ ] +1 recommend to the Board the resolution to graduate Apache FreeMarker
to a TLP
[ ] +0 no opinion
[ ] -1 don't graduate Apache FreeMarker to a TLP (please specify a reason)

Thanks,
Jacopo Cappellato

References:
[1] Community graduation discussion: https://s.apache.org/gYMw
[2] Community graduation vote: https://s.apache.org/MNdd
[3] Incubator resolution discussion: https://s.apache.org/xdI3
[4] Project status page:
http://incubator.apache.org/projects/freemarker.html
[5] Project maturity model: https://s.apache.org/ixlR
[6] Freemarker website: https://freemarker.apache.org/

The proposed Resolution of the Apache FreeMarker project:

--

Establish the Apache FreeMarker 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 template engine.

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

RESOLVED, that the Apache FreeMarker Project be and hereby is
responsible for the creation and maintenance of software
related to a template engine, and be it further

RESOLVED, that the office of "Vice President, Apache FreeMarker" 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 FreeMarker Project, and to have primary responsibility
for management of the projects within the scope of
responsibility of the Apache FreeMarker 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 FreeMarker Project:

  * Dániel Dékány   
  * David E. Jones
  * Jacopo Cappellato   
  * Jacques Le Roux 
  * Nan Lei 
  * Sergio Fernández
  * Woonsan Ko  

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Dániel Dékány
be appointed to the office of Vice President, Apache FreeMarker,
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 FreeMarker Project be and hereby
is tasked with the migration and rationalization of the Apache
Incubator FreeMarker podling; and be it further

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

--



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




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

Re: [DISCUSS] Dr. Elephant Incubator Proposal

[Kevin A. McGrail]

I'm intrigued by the proposal and the product. I'm a 0.5+.

I'd love to know more about why LI put it on GitHub and what problems it's
having that are leading to a foundation.

--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Tue, Mar 6, 2018 at 8:27 PM, Gangumalla, Uma 
wrote:

> I would +1 to have as a separate project instead of pushing under Hadoop.
> When a project can sustain by having potential to build community on its
> own and can run logically as independent module, I feel that’s good enough
> to start as separate project.
>
> I could not recall the discussions on removal of Vaidya package from
> Hadoop. If someone remembers, it would be great to know the reasons for
> removal of that package from Hadoop base. [ probably at the time of
> mavenization ? ]
>
> Regards,
> Uma
>
> On 3/6/18, 3:17 PM, "md...@cloudera.com on behalf of Mike Drob" <
> md...@cloudera.com on behalf of md...@apache.org> wrote:
>
> 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
> >

Re: [DISCUSS] Dr. Elephant Incubator Proposal

[Kevin A. McGrail]

I do not believe an SGA is needed as Dr. Elephant is licensed under ASF.
https://github.com/linkedin/dr-elephant/blob/master/LICENSE

Regards,
KAM

--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Wed, Mar 7, 2018 at 6:59 AM, Bertrand Delacretaz <
bdelacre...@codeconsult.ch> wrote:

> Hi,
>
> On Wed, Mar 7, 2018 at 12:08 AM, Carl Steinbach  wrote:
> > = Source and Intellectual Property Submission Plan =
> > ...The Dr. Elephant source code is already licensed under
> > Apache License Version 2.0. Going forward, we will continue to have
> > all the contributions licensed directly to the Apache Software
> > Foundation through our signed Individual Contributor License
> > Agreements for all of the committers on the project
>
> Note that whoever owns the code (LinkedIn IIUC) will have to submit a
> Software Grant to donate it to the ASF:
>
> https://www.apache.org/licenses/software-grant.txt
>
> I think it's prudent to verify that the owners of the code are ready
> to sign and submit that document, and mention that in the above
> section, before entering incubation.
>
> -Bertrand
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Dr. Elephant Incubator Proposal

[Kevin A. McGrail]

Fair enough but it would be procedural not legal.  Who would sign said
SGA?  LI or representatives of the GH project?

--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Wed, Mar 7, 2018 at 1:55 PM, Craig Russell  wrote:

> If Dr. Elephant *becomes* an Apache project, it needs a SGA. This is part
> of the incubation process, although as Bertrand notes, it's good to know
> ahead of time whether all of the current owners of the code are willing to
> grant an explicit license to Apache.
>
> Please see http://www.apache.org/licenses/#provenance for details.
>
> If Dr. Elephant is only *used* as a dependency by an Apache project, no
> SGA is needed.
>
> Craig
>
> > On Mar 7, 2018, at 5:51 AM, Kevin A. McGrail 
> wrote:
> >
> > I do not believe an SGA is needed as Dr. Elephant is licensed under ASF.
> > https://github.com/linkedin/dr-elephant/blob/master/LICENSE
> >
> > Regards,
> > KAM
> >
> > --
> > Kevin A. McGrail
> > Asst. Treasurer & VP Fundraising, Apache Software Foundation
> > Chair Emeritus Apache SpamAssassin Project
> > https://www.linkedin.com/in/kmcgrail - 703.798.0171
> >
> > On Wed, Mar 7, 2018 at 6:59 AM, Bertrand Delacretaz <
> > bdelacre...@codeconsult.ch> wrote:
> >
> >> Hi,
> >>
> >> On Wed, Mar 7, 2018 at 12:08 AM, Carl Steinbach  wrote:
> >>> = Source and Intellectual Property Submission Plan =
> >>> ...The Dr. Elephant source code is already licensed under
> >>> Apache License Version 2.0. Going forward, we will continue to have
> >>> all the contributions licensed directly to the Apache Software
> >>> Foundation through our signed Individual Contributor License
> >>> Agreements for all of the committers on the project
> >>
> >> Note that whoever owns the code (LinkedIn IIUC) will have to submit a
> >> Software Grant to donate it to the ASF:
> >>
> >> https://www.apache.org/licenses/software-grant.txt
> >>
> >> I think it's prudent to verify that the owners of the code are ready
> >> to sign and submit that document, and mention that in the above
> >> section, before entering incubation.
> >>
> >> -Bertrand
> >>
> >> -
> >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> >> For additional commands, e-mail: general-h...@incubator.apache.org
> >>
> >>
>
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org http://db.apache.org/jdo
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] Dr. Elephant Incubator Proposal

[Kevin A. McGrail]

Sorry, I missed the copyright and checked only the LICENSE.  Agree
completely with you and Craig an SGA is needed.

--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Wed, Mar 7, 2018 at 2:19 PM, John D. Ament  wrote:

> On Wed, Mar 7, 2018 at 2:17 PM Kevin A. McGrail 
> wrote:
>
> > Fair enough but it would be procedural not legal.  Who would sign said
> > SGA?  LI or representatives of the GH project?
> >
>
> LinkedIn.  And it is a legal need.  Right now, the source files have
> Copyright LinkedIn on them.  The SGA grants us the ability to remove that
> copyright header.  The CCLA would allow the individual contributors to
> submit the code to us with the appropriate header.  Hence why either works
> in this case.
>
>
> >
> > --
> > Kevin A. McGrail
> > Asst. Treasurer & VP Fundraising, Apache Software Foundation
> > Chair Emeritus Apache SpamAssassin Project
> > https://www.linkedin.com/in/kmcgrail - 703.798.0171 <(703)%20798-0171>
> >
> > On Wed, Mar 7, 2018 at 1:55 PM, Craig Russell 
> > wrote:
> >
> > > If Dr. Elephant *becomes* an Apache project, it needs a SGA. This is
> part
> > > of the incubation process, although as Bertrand notes, it's good to
> know
> > > ahead of time whether all of the current owners of the code are willing
> > to
> > > grant an explicit license to Apache.
> > >
> > > Please see http://www.apache.org/licenses/#provenance for details.
> > >
> > > If Dr. Elephant is only *used* as a dependency by an Apache project, no
> > > SGA is needed.
> > >
> > > Craig
> > >
> > > > On Mar 7, 2018, at 5:51 AM, Kevin A. McGrail 
> > > wrote:
> > > >
> > > > I do not believe an SGA is needed as Dr. Elephant is licensed under
> > ASF.
> > > > https://github.com/linkedin/dr-elephant/blob/master/LICENSE
> > > >
> > > > Regards,
> > > > KAM
> > > >
> > > > --
> > > > Kevin A. McGrail
> > > > Asst. Treasurer & VP Fundraising, Apache Software Foundation
> > > > Chair Emeritus Apache SpamAssassin Project
> > > > https://www.linkedin.com/in/kmcgrail - 703.798.0171
> <(703)%20798-0171>
> > > >
> > > > On Wed, Mar 7, 2018 at 6:59 AM, Bertrand Delacretaz <
> > > > bdelacre...@codeconsult.ch> wrote:
> > > >
> > > >> Hi,
> > > >>
> > > >> On Wed, Mar 7, 2018 at 12:08 AM, Carl Steinbach 
> > wrote:
> > > >>> = Source and Intellectual Property Submission Plan =
> > > >>> ...The Dr. Elephant source code is already licensed under
> > > >>> Apache License Version 2.0. Going forward, we will continue to have
> > > >>> all the contributions licensed directly to the Apache Software
> > > >>> Foundation through our signed Individual Contributor License
> > > >>> Agreements for all of the committers on the project
> > > >>
> > > >> Note that whoever owns the code (LinkedIn IIUC) will have to submit
> a
> > > >> Software Grant to donate it to the ASF:
> > > >>
> > > >> https://www.apache.org/licenses/software-grant.txt
> > > >>
> > > >> I think it's prudent to verify that the owners of the code are ready
> > > >> to sign and submit that document, and mention that in the above
> > > >> section, before entering incubation.
> > > >>
> > > >> -Bertrand
> > > >>
> > > >> 
> -
> > > >> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > >> For additional commands, e-mail: general-h...@incubator.apache.org
> > > >>
> > > >>
> > >
> > > Craig L Russell
> > > Secretary, Apache Software Foundation
> > > c...@apache.org http://db.apache.org/jdo
> > >
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
>

Re: [DISCUSS] Dr. Elephant Incubator Proposal

[Kevin A. McGrail]

I vote for Apache L.E.Font, MD :-)

--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Thu, Mar 8, 2018 at 6:43 AM, Pierre Smits  wrote:

> Hi All,
>
> While i believe, based on the proposal, it may the works may be a nice
> addition to the portfolio of the ASF, I have concerns with the name.
>
> Are we going to call this (if and when onboarded/graduated):
>
>- Apache DrElephant?
>- Apache Doctor Elephant?
>- Apache Dr-Elephant?
>- etc
>
> While it is understandable that existing parties want to retain the name of
> where code and team originally came from, I believe the name of the
> podling, its community and its works should not always hang to much to
> references in the past. Joining the ASF as a podling offers an opportunity
> to retain the best from the past (often the code and pre-joining
> contributors) and have a do-over for remainder.
>
> Best regards,
>
>
> Best regards,
>
> Pierre Smits
>
> V.P. Apache Trafodion
>
> On Thu, Mar 8, 2018 at 3:35 AM, Carl Steinbach  wrote:
>
> > Timothy Chen has volunteered to be a mentor. I have updated
> > the proposal on the wiki to reflect this.
> >
> > Thanks Timothy!
> >
> > - Carl
> >
> > On Wed, Mar 7, 2018 at 12:47 PM, Carl Steinbach  wrote:
> >
> > > I also wanted to add that we are looking for more mentors.
> > > Please email me if you are interested.
> > >
> > > Thanks.
> > >
> > > - Carl
> > >
> > > On Wed, Mar 7, 2018 at 12:46 PM, Carl Steinbach 
> wrote:
> > >
> > >> I will followup with LinkedIn's legal team regarding getting an SGA. I
> > >> don't
> > >> think this will be a problem since the same team has already reviewed
> > Dr.
> > >> Elephant
> > >> and approved it for contribution to the Apache incubator.
> > >>
> > >> - Carl
> > >>
> > >> On Wed, Mar 7, 2018 at 11:20 AM, Kevin A. McGrail <
> kmcgr...@apache.org>
> > >> wrote:
> > >>
> > >>> Sorry, I missed the copyright and checked only the LICENSE.  Agree
> > >>> completely with you and Craig an SGA is needed.
> > >>>
> > >>> --
> > >>> Kevin A. McGrail
> > >>> Asst. Treasurer & VP Fundraising, Apache Software Foundation
> > >>> Chair Emeritus Apache SpamAssassin Project
> > >>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
> > >>>
> > >>> On Wed, Mar 7, 2018 at 2:19 PM, John D. Ament  >
> > >>> wrote:
> > >>>
> > >>> > On Wed, Mar 7, 2018 at 2:17 PM Kevin A. McGrail <
> kmcgr...@apache.org
> > >
> > >>> > wrote:
> > >>> >
> > >>> > > Fair enough but it would be procedural not legal.  Who would sign
> > >>> said
> > >>> > > SGA?  LI or representatives of the GH project?
> > >>> > >
> > >>> >
> > >>> > LinkedIn.  And it is a legal need.  Right now, the source files
> have
> > >>> > Copyright LinkedIn on them.  The SGA grants us the ability to
> remove
> > >>> that
> > >>> > copyright header.  The CCLA would allow the individual contributors
> > to
> > >>> > submit the code to us with the appropriate header.  Hence why
> either
> > >>> works
> > >>> > in this case.
> > >>> >
> > >>> >
> > >>> > >
> > >>> > > --
> > >>> > > Kevin A. McGrail
> > >>> > > Asst. Treasurer & VP Fundraising, Apache Software Foundation
> > >>> > > Chair Emeritus Apache SpamAssassin Project
> > >>> > > https://www.linkedin.com/in/kmcgrail - 703.798.0171
> > >>> <(703)%20798-0171>
> > >>> > >
> > >>> > > On Wed, Mar 7, 2018 at 1:55 PM, Craig Russell <
> > apache@gmail.com>
> > >>> > > wrote:
> > >>> > >
> > >>> > > > If Dr. Elephant *becomes* an Apache project, it needs a SGA.
> This
> > >>> is
> > >>> > part
> > >>> > > > of the incubation process, although as Bertrand notes, it's
> good
> > to
> > >

Re: [VOTE] Accept Pinot into Apache Incubator

[Kevin A. McGrail]

+1 binding.  Apologies if this is a dupe.  I thought I voted days ago.

On Mar 9, 2018 02:11, "kishore g"  wrote:

> Hi all,
>
> I would like to call a VOTE to accept Pinot into the Apache Incubator. The
> full proposal is available on the wiki
> 
>
> Please cast your vote:
>
>   [ ] +1, bring Pinot into Incubator
>   [ ] +0, I don't care either way,
>   [ ] -1, do not bring Pinot into Incubator, because...
>
> The vote will open at least for 72 hours and only votes from the Incubator
> PMC are binding.
>
> Thanks,
> Kishore G
>
> Discussion thread:
> https://lists.apache.org/thread.html/8119f9478ea1811371f1bf6685290b
> 22b57b1a3e0849d1d778d77dcb@%3Cgeneral.incubator.apache.org
>
>
> = Pinot Proposal =
>
> == Abstract ==
>
> Pinot is a distributed columnar storage engine that can ingest data in
> real-time and serve analytical queries at low latency. There are two modes
> of data ingestion - batch and/or realtime. Batch mode allows users to
> generate pinot segments externally using systems such as Hadoop. These
> segments can be uploaded into Pinot via simple curl calls. Pinot can ingest
> data in near real-time from streaming sources such as Kafka. Data ingested
> into Pinot is stored in a columnar format. Pinot provides a SQL like
> interface (PQL) that supports filters, aggregations, and group by
> operations. It does not support joins by design, in order to guarantee
> predictable latency. It leverages other Apache projects such as Zookeeper,
> Kafka, and Helix, along with many libraries from the ASF.
>
> == Proposal ==
>
> Pinot was open sourced by LinkedIn and hosted on GitHub. Majority of the
> development happens at LinkedIn with other contributions from Uber and
> Slack. We believe that being a part of 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 Apache Software
> Foundation. The code is already under Apache License 2.0.  Code and the
> documentation are hosted on Github.
>  * Code: http://github.com/linkedin/pinot
>  * Documentation: https://github.com/linkedin/pinot/wiki
>
>
> == Background ==
>
> LinkedIn, similar to other companies, has many applications that provide
> rich real-time insights to members and customers (internal and external).
> The workload characteristics for these applications vary a lot. Some
> internal applications simply need ad-hoc query capabilities with sub-second
> to multiple seconds latency. But external site facing applications require
> strong SLA even very high workloads. Prior to Pinot, LinkedIn had multiple
> solutions depending on the workload generated by the application and this
> was inefficient. Pinot was developed to be the one single platform that
> addresses all classes of applications. Today at LinkedIn, Pinot powers more
> than 50 site facing products with workload ranging from few queries per
> second to 1000’s of queries per second while maintaining the 99th
> percentile latency which can be as low as few milliseconds. All internal
> dashboards at LinkedIn are powered by Pinot.
>
> == Rationale ==
>
> We believe that requirement to develop rich real-time analytic applications
> is applicable to other organizations. Both Pinot and the interested
> communities would benefit from this work being openly available.
>
> == Current Status ==
>
> Pinot is currently open sourced under the Apache License Version 2.0 and
> available at github.com/linkedin/pinot. All the development is done using
> GitHub Pull Requests. We cut releases on a weekly basis and deploy it at
> LinkedIn. mp-0.1.468 is the latest release tag that is deployed in
> production.
>
> == Meritocracy ==
>
> Following the Apache meritocracy model, we intend to build an open and
> diverse community around Pinot. We will encourage the community to
> contribute to discussion and codebase.
>
> == Community ==
>
> Pinot is currently used extensively at LinkedIn and Uber. Several companies
> have expressed interest in the project. We hope to extend the contributor
> base significantly by bringing Pinot into Apache.
>
> == Core Developers ==
>
> Pinot was started by engineers at LinkedIn, and now has committers from
> Uber.
>
> == Alignment ==
>
> Apache is the most natural home for taking Pinot forward. Pinot leverages
> several existing Apache Projects such as Kafka, Helix, Zookeeper, and Avro.
> As Pinot gains adoption, we plan to add support for the ORC and Parquet
> formats, as well as adding integration with Yarn and Mesos.
>
> == Known Risks ==
>
> === Orphaned Products ===
>
> The risk of the Pinot project being abandoned is minimal. The teams at
> LinkedIn and Uber are highly incentivized to continue development of Pinot
> as it is a critical part of their infrastructure.
>
> === Inexperience with Open Source ===
>
> Post open sourcing, Pinot was completely developed on GitHub. All the
> current developers on Pinot are

Re: The role of a mentor

[Kevin A. McGrail]

Adding to the responses:

- One of the duties I try and fill as a champion / mentor is to liaison
concerns and introduce them to the way the project should self-service
their own requests.

- I also try and quell the "this stinks" because there can be push back to
the way we do things.  I have said it takes about 2-3 years for people to
really appreciate the Apache Way and making sure they don't get too
frustrated in the meantime.

Regards,
KAM

--
Kevin A. McGrail
Asst. Treasurer & VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Tue, Apr 3, 2018 at 5:42 AM, Mark Struberg 
wrote:

> +1
>
> I'd also add to the list: explaining the reasons behind some of the things
> how projects at ASF works.
> Often people new to the ASF complain about the release checks and
> procedure. When you explain them the legal impact and our quality goals and
> the community aspects then they quickly understand and even actively
> support the way we run projects.
>
> People should not do it 'the Apache way' because it is some ceremony, but
> because it actually makes a lot of sense!
>
>
> Some the interpretation of the mentor role also depends on whether oneself
> is using the project as well.
> There are projects (like NetBeans, ISIS) where I mainly help with/focus on
> legal and infra stuff.
> And there are other projects where I'm also an active committer.
> Both cases are fine. But of course as committing mentor one has a way
> deeper insight into the projects health!
>
> LieGrue,
> strub
>
>
> > Am 03.04.2018 um 08:05 schrieb Romain Manni-Bucau  >:
> >
> > Hi John,
> >
> > for me it is close to what JB described:
> >
> > 1. be there when needed (how do I create a git repo? how do I ask a
> > JIRA?Why do I need X?). Even documented, having somebody you can ask
> > more directly is often valuable.
> > 2. ensure the releases are legal (+ respect mandatory ASF rules + point
> out
> > not mandatory but recommanded rules)
> > 3. be there to remind community is important and not only code to
> prepare a
> > good graduation
> >
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau <https://twitter.com/rmannibucau> |  Blog
> > <https://rmannibucau.metawerx.net/> | Old Blog
> > <http://rmannibucau.wordpress.com> | Github <https://github.com/
> rmannibucau> |
> > LinkedIn <https://www.linkedin.com/in/rmannibucau> | Book
> > <https://www.packtpub.com/application-development/java-
> ee-8-high-performance>
> >
> > 2018-04-03 7:31 GMT+02:00 Jean-Baptiste Onofré :
> >
> >> Hi John,
> >>
> >> IMHO, a mentor is not necessary involved in the project
> technics/codebase
> >> (it's
> >> actually a bonus).
> >>
> >> As a mentor, I'm focusing:
> >> 1. Insure of the legal aspect of the project (ICLA/CCLA, SGA, ...)
> >> 2. Help around infra and release preparation according to Apache rules
> >> 3. Help to promote the project and build communities around
> >> 4. See if there's potential interaction with other podlings and existing
> >> TLPs
> >> 5. Help to go to graduation (following the graduation checklist)
> >> 6. (optional) Help on the contribution (codebase, website, ...)
> >>
> >> My $0.01
> >>
> >> Regards
> >> JB
> >>
> >> On 04/03/2018 12:54 AM, John D. Ament wrote:
> >>> I've been following along the absent mentors discussion.  But I'm
> >> curious,
> >>> from both an IPMC member's perspective as well as a member of a
> podling,
> >>> what roles do you see for a mentor?  What are their responsibilities to
> >> the
> >>> podling?
> >>>
> >>> We have a few things written down, and I'm not too interested in
> >> rehashing
> >>> the written version.  But what do podlings need from their mentors?
> >> Point
> >>> you in a direction to run with?  Do the apache work for the podling?
> Do
> >> we
> >>> (the ASF) need mentors to ensure that podlings are operating within
> >> certain
> >>> bounds?  Do we rely on mentors to be a read of the pulse of a podling?
> >>>
> >>> John
> >>>
> >>
> >> --
> >> Jean-Baptiste Onofré
> >> jbono...@apache.org
> >> http://blog.nanthrax.net
> >> Talend - http://www.talend.com
> >>
> >> -
> >> 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: Default webpages for new podlings

[Kevin A. McGrail]

I think this is a great day one idea but by 3 months,.the project should be
having a website to start that ball rolling.  This might be too much of a
crutch.

On Sun, Apr 15, 2018, 11:10 John D. Ament  wrote:

> Based on some of the on going discussions, wanted to get opinions on how to
> get podling websites bootstrapped a bit easier.
>
> When I review https://incubator.apache.org/guides/sites.html it seems
> pretty clear what we expect on a podling website.  I'm wondering if during
> the bootstrapping phase (first 3 months or so of the project at Apache, in
> my mind at least) it would be OK if the podlings website just redirected to
> their status page.
>
> This avoid unnecessary 404's for the project, and gives them some time to
> move their infrastructure over.  Once they have their website up and
> running (either migrated or created from scratch) then they can switch the
> redirect to point to their actual content.
>
> I would imagine this can be done with a .htaccess file, similar to what's
> done for retired podlings.
>
> Thoughts?
>

Re: [VOTE] Graduate Traffic Control to a top level project

[Kevin A. McGrail]

+1 binding

On Fri, Apr 20, 2018, 14:02 Dave Neuman  wrote:

> Hello IPMC,
> The Traffic Control PMC would like to call a vote to graduate from the
> incubator to a top level Apache project!  The traffic control community has
> voted to graduate [1], voted on our resolution [2], and opened a thread to
> discuss our resolution on this list [3].
>
> Traffic Control entered the incubator on July 12, 2016.  Since then we have
> announced 4 releases, nominated 4 new committers, organized 4 summits, had
> more than 8,000 commits from 63 different contributors, and -- most
> importantly -- we have grown and diversified our community.  Apache Traffic
> Control is a healthy project that is already acting like an Apache top
> level project, and we are ready to take the next step.
>
> I would like to ask that you please take a moment to vote on our
> resolution.  Please respond with one of the following:
>
> [ ] +1 Graduate Traffic Control from the incubator
> [ ] +0 No Opinion
> [ ] -1 Do not graduate Traffic Control from the incubator (please provide a
> reason)
>
> The vote is open for a minimum of 72 hours and will need at least 3 more +1
> votes than -1 votes from IPMC members to succeed.
>
> Please do not hesitate to let us know if you have any questions.
>
> Thanks,
> Dave
>
> [1]
>
> https://lists.apache.org/thread.html/fb1fae0785feb6568cef6deb6fa20723eba54ed63a445462d44564d3@%3Cdev.trafficcontrol.apache.org%3E
> [2]
>
> https://lists.apache.org/thread.html/53c51f3eab45525c4e6c1bc52072659c751fd9c59001006791e4b0e3@%3Cdev.trafficcontrol.apache.org%3E
> [3]
>
> https://lists.apache.org/thread.html/837b7bfd090d84632fe1f314484c32f18cddf5030b21289879753403@%3Cgeneral.incubator.apache.org%3E
>
>
>
> ---
>
> Establish the Apache Traffic Control 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 building, monitoring, configuring, and provisioning a large
> scale content delivery network (CDN)..
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> (PMC), to be known as the "Apache Traffic Control Project", be and
> hereby is established pursuant to Bylaws of the Foundation; and be it
> further
>
> RESOLVED, that the Apache Traffic Control Project be and hereby is
> responsible for the creation and maintenance of software related to
> building, monitoring, configuring, and provisioning a large scale
> content delivery network (CDN).; and be it further
>
> RESOLVED, that the office of "Vice President, Apache Traffic Control" 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 Traffic
> Control Project, and to have primary responsibility for management of
> the projects within the scope of responsibility of the Apache Traffic
> Control 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 Traffic Control
> Project:
>
>  * Dan Kirkwood   
>  * David Neuman   
>  * Dewayne Richardson 
>  * Eric Covener   
>  * Eric Friedrich 
>  * Hank Beatty
>  * Jan van Doorn  
>  * Jeff Elsloo
>  * Jeremy Mitchell
>  * Leif Hedstrom  
>  * Mark Torluemke 
>  * Phil Sorber
>  * Steve Malenfant
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that David Neuman be appointed
> to the office of Vice President, Apache Traffic Control, 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 Traffic Control 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 Traffic Control
> Project; and be it further
>
> RESOLVED, that the Apache Traffic Control Project be and hereby is
> tasked with the migration and rationalization of the Apache Incubator
> Traffic Control podling; and be it further
>
> RESOLVED, that all responsibilities pertaining to the Apache Incubator
> Traffic Control podling encumbered upon the Apache Incubator PMC are
> hereafter discharged.
>

Re: [VOTE] Release Apache ECharts (incubating) 4.1.0.rc3

[Kevin A. McGrail]

If the release candidate isn't correct for the artifacts you need to roll
an rc4 which might be two files not one and send that for a vote.

On Sat, May 19, 2018, 22:34 Willem Jiang  wrote:

> Hi,
>
> As there is only one zip file, I guess it just the src distribution.
> But after went through the file, I found lot of echart js files in the dist
> directory and the rat jar.
>
> So I'm confused what's the purpose of apache-echarts-4.1.0.rc3-
> incubating.zip
>
> Normally we distribute the src and binary files separately.
>
>
>
> Willem Jiang
>
> Blog: http://willemjiang.blogspot.com (English)
>   http://jnn.iteye.com  (Chinese)
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Thu, May 17, 2018 at 7:42 PM, SHUANG SU  wrote:
>
> > I am pleased to be calling this vote for the release of Apache ECharts
> > 4.1.0.rc3.
> >
> > Apache ECharts community has voted and approved the release.
> >
> > Vote thread:
> > https://lists.apache.org/thread.html/67dffef28ecffd66689ac991ca027c
> > 0868d734629949d958e7b12dd3@%3Cdev.echarts.apache.org%3E
> >
> > Results thread:
> > https://lists.apache.org/thread.html/3a6e627a7e07d5de0856296d44bb40
> > 8e17ee6795cc74ef190a7a5d23@%3Cdev.echarts.apache.org%3E
> >
> > The release candidate to be voted over is available at:
> > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.1.0.rc3/
> >
> > The release candidate is signed with a GPG key available at:
> > https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
> >
> > A tagged git repository is available for review at:
> > https://github.com/apache/incubator-echarts/releases/tag/4.1.0.rc3
> >
> > The Git commit for this release is:
> > https://gitbox.apache.org/repos/asf?p=incubator-echarts.
> > git;a=commit;h=f98eb21
> >
> > The Release Note is available in:
> > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.
> > 1.0.rc3/RELEASE_NOTE.txt
> >
> > Some shell commands for validating the release:
> >
> > ```shell
> > # Download the release:
> > curl
> > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.
> > 1.0.rc3/apache-echarts-4.1.0.rc3-incubating.zip
> > -o apache-echarts-4.1.0.rc3-incubating.zip
> > unzip apache-echarts-4.1.0.rc3-incubating.zip -d
> > apache-echarts-4.1.0.rc3-incubating > /dev/null
> >
> > # Rebuild the project:
> > cd "apache-echarts-4.1.0.rc3-incubating" && npm install && cd ..
> > node "apache-echarts-4.1.0.rc3-incubating/build/build.js" --release
> > # (See help: `node "apache-echarts-4.1.0.rc3-incubating/build/build.js"
> > --help`)
> >
> > # Run Apache Rat:
> > java -jar "apache-echarts-4.1.0.rc3-incubating/build/rat/runrat.jar" |
> > less
> > # (See help: `java -jar
> > "apache-echarts-4.1.0.rc3-incubating/build/rat/runrat.jar" --help`)
> > ```
> >
> >
> > Please vote on releasing this package as:
> > Apache ECharts 4.1.0.rc3
> >
> > This vote will be open until "2018-05-20T12:33:24.955Z".
> >
> > [ ] +1 Release this package
> > [ ] 0 I don't feel strongly about it, but don't object
> > [ ] -1 Do not release this package because...
> >
> > Anyone can participate in testing and voting, not just committers, please
> > feel free to try out the release candidate and provide your votes.
> >
> >
> > --
> >  Su Shuang (100pah)
> > --
> >
>

Re: [VOTE] Release Apache ECharts (incubating) 4.1.0.rc4

[Kevin A. McGrail]

Su, I would think you would remove the rc4 (release candidate) and it would
be released as 4.1.0.  Also, I think your vote already passed so I'm not
sure why you need another round of votes.  Am I confused?

--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Tue, May 29, 2018 at 5:09 AM, SHUANG SU  wrote:

> After removing some generated files and bin files from 4.1.0.rc3, only
> source code kept in the artifact.
> I am pleased to be calling this vote for the release of Apache ECharts
> 4.1.0.rc4.
>
>
> Apache ECharts community has voted and approved the release.
>
> Vote thread:
> https://lists.apache.org/thread.html/8ebfdd7219cbfed40cd2350e487b99
> be58ec169fb7c5673e21e10dea@%3Cdev.echarts.apache.org%3E
>
> Results thread:
> https://lists.apache.org/thread.html/238ae37a82e2a71698f41a4d878e32
> 5601b88c665f9951d3bf912db4@%3Cdev.echarts.apache.org%3E
>
> The release candidate to be voted over is available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.1.0.rc4/
>
> The release candidate is signed with a GPG key available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
>
> The Git commit for this release is:
> https://gitbox.apache.org/repos/asf?p=incubator-echarts.
> git;a=commit;h=02842e2
>
> The Release Note is available in:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.
> 1.0.rc4/RELEASE_NOTE.txt
>
> Some shell commands for validating the release:
>
> ```shell
> # Download the release:
> curl
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.
> 1.0.rc4/apache-echarts-4.1.0.rc4-incubating-src.zip
> -o apache-echarts-4.1.0.rc4-incubating-src.zip
> unzip apache-echarts-4.1.0.rc4-incubating-src.zip -d
> apache-echarts-4.1.0.rc4-incubating-src > /dev/null
>
> # Rebuild the project (Node.js environment is required):
> cd "apache-echarts-4.1.0.rc4-incubating-src" && npm install && cd ..
> node "apache-echarts-4.1.0.rc4-incubating-src/build/build.js" --release
> # (See help: `node "apache-echarts-4.1.0.rc4-
> incubating-src/build/build.js"
> --help`)
> ```
>
>
> Please vote on releasing this package as:
> Apache ECharts 4.1.0.rc4
>
> This vote will be open until "2018-06-01T10:02:35.437Z".
>
> [ ] +1 Release this package
> [ ] 0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
>
> Anyone can participate in testing and voting, not just committers, please
> feel free to try out the release candidate and provide your votes.
>
> --
>  Su Shuang (100pah)
> --
>

Re: [VOTE] Release Apache ECharts (incubating) 4.1.0.rc4

[Kevin A. McGrail]

You are likely correct.  Just a lot of rcs and I thought you would have
canceled some of the votes.

You don't have to finish the votes if you know you aren't going to release
it.  And by an rc4 with a minor change like removing files, you could ask
your group how they feel about the voting process. I certainly would say it
makes sense as long as you have consensus.

When it is released, my point is that the rc4 is removed so some of ypur
text says you are releasing 4.1.0rc4.  I would have it say release 4.1.0
and here is release candidate 4.

In fact I like to write the release notice as the voting notice so the
notice is effectively viewed at the same time as the vote for the release.

Then when the vote passes it's a cut and paste to announce.

KAM
On Wed, May 30, 2018, 05:31 SHUANG SU  wrote:

> Kevin,
>
> Sorry, I am being confused with the voting progress:
>
> Firstly, I called a vote for 4.1.0.rc3 on "general@incubator.apache.org",
> and then received some comments.
> Then, I fixed the artifact according to those comments, and called a vote
> for 4.1.0.rc4 on "d...@echarts.apache.org",
> and then the vote passed.
> Then, I am calling a vote for 4.1.0.rc4 on "general@incubator.apache.org"
> now.
>
> Did I do it correctly?
> Or, maybe, I should have skipped the vote for 4.1.0.rc4 on "
> d...@echarts.apache.org",
> but call a vote for 4.1.0.rc4 on "general@incubator.apache.org" directly
> after I fixed the 4.1.0.rc3?
>
>
>
>
> --
>  Su Shuang (100pah)
> --
>
>
> 2018-05-29 22:41 GMT+08:00 Kevin A. McGrail :
>
> > Su, I would think you would remove the rc4 (release candidate) and it
> would
> > be released as 4.1.0.  Also, I think your vote already passed so I'm not
> > sure why you need another round of votes.  Am I confused?
> >
> > --
> > Kevin A. McGrail
> > VP Fundraising, Apache Software Foundation
> > Chair Emeritus Apache SpamAssassin Project
> > https://www.linkedin.com/in/kmcgrail - 703.798.0171
> >
> > On Tue, May 29, 2018 at 5:09 AM, SHUANG SU 
> wrote:
> >
> > > After removing some generated files and bin files from 4.1.0.rc3, only
> > > source code kept in the artifact.
> > > I am pleased to be calling this vote for the release of Apache ECharts
> > > 4.1.0.rc4.
> > >
> > >
> > > Apache ECharts community has voted and approved the release.
> > >
> > > Vote thread:
> > > https://lists.apache.org/thread.html/8ebfdd7219cbfed40cd2350e487b99
> > > be58ec169fb7c5673e21e10dea@%3Cdev.echarts.apache.org%3E
> > >
> > > Results thread:
> > > https://lists.apache.org/thread.html/238ae37a82e2a71698f41a4d878e32
> > > 5601b88c665f9951d3bf912db4@%3Cdev.echarts.apache.org%3E
> > >
> > > The release candidate to be voted over is available at:
> > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.1.0.rc4/
> > >
> > > The release candidate is signed with a GPG key available at:
> > > https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
> > >
> > > The Git commit for this release is:
> > > https://gitbox.apache.org/repos/asf?p=incubator-echarts.
> > > git;a=commit;h=02842e2
> > >
> > > The Release Note is available in:
> > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.
> > > 1.0.rc4/RELEASE_NOTE.txt
> > >
> > > Some shell commands for validating the release:
> > >
> > > ```shell
> > > # Download the release:
> > > curl
> > > https://dist.apache.org/repos/dist/dev/incubator/echarts/4.
> > > 1.0.rc4/apache-echarts-4.1.0.rc4-incubating-src.zip
> > > -o apache-echarts-4.1.0.rc4-incubating-src.zip
> > > unzip apache-echarts-4.1.0.rc4-incubating-src.zip -d
> > > apache-echarts-4.1.0.rc4-incubating-src > /dev/null
> > >
> > > # Rebuild the project (Node.js environment is required):
> > > cd "apache-echarts-4.1.0.rc4-incubating-src" && npm install && cd ..
> > > node "apache-echarts-4.1.0.rc4-incubating-src/build/build.js" --release
> > > # (See help: `node "apache-echarts-4.1.0.rc4-
> > > incubating-src/build/build.js"
> > > --help`)
> > > ```
> > >
> > >
> > > Please vote on releasing this package as:
> > > Apache ECharts 4.1.0.rc4
> > >
> > > This vote will be open until "2018-06-01T10:02:35.437Z".
> > >
> > > [ ] +1 Release this package
> > > [ ] 0 I don't feel strongly about it, but don't object
> > > [ ] -1 Do not release this package because...
> > >
> > > Anyone can participate in testing and voting, not just committers,
> please
> > > feel free to try out the release candidate and provide your votes.
> > >
> > > --
> > >  Su Shuang (100pah)
> > > --
> > >
> >
>

Re: [VOTE] Release Apache ECharts (incubating) 4.1.0.rc4

[Kevin A. McGrail]

Ty.  I am +1 binding on rc4

On Wed, May 30, 2018, 13:11 SHUANG SU  wrote:

> > When it is released, my point is that the rc4 is removed so some of ypur
> > text says you are releasing 4.1.0rc4.  I would have it say release 4.1.0
> > and here is release candidate 4.
>
> Yes, it is the vote for the release of 4.1.0, release candidate 4. I should
> have made it clearly
> in text.
>
> > That is the right process but you also need to cancel the previous vote.
>
> Thanks, I have canceled the previous vote just now.
>
>
>
>
> --
>  Su Shuang (100pah)
> --
>
>
> 2018-05-30 19:47 GMT+08:00 Justin Mclean :
>
> > Hi,
> >
> > > Firstly, I called a vote for 4.1.0.rc3 on "
> general@incubator.apache.org"
> > ,
> > > and then received some comments.
> > > Then, I fixed the artifact according to those comments, and called a
> vote
> > > for 4.1.0.rc4 on "d...@echarts.apache.org",
> > > and then the vote passed.
> > > Then, I am calling a vote for 4.1.0.rc4 on "
> general@incubator.apache.org
> > "
> > > now.
> >
> >
> > That is the right process but you also need to cancel the previous vote.
> >
> > Thanks,
> > Justin
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: graphviz as a potential apache project

[Kevin A. McGrail]

License is an issue with GraphViz but I'm +1 to help them come under the
ASF umbrella!

--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Sun, Jun 3, 2018 at 3:01 PM, Dave Fisher  wrote:

>
>
> Sent from my iPhone
>
> > On Jun 3, 2018, at 9:03 AM, Nick Kew  wrote:
> >
> >
> >> On 3 Jun 2018, at 16:29, sha...@apache.org wrote:
> >>
> >> Hi All
> >>
> >> I received this request from Stephen so am forwarding to the general
> incubator mailing list for discussion and any suggestions for options.
> >
> > I don't know enough about the project to comment on that.
> >
> > Just to say, if it's to become an Apache project, I'd expect to see its
> community
> > approach our community.  One project individual approaching one ASF
> individual
> > is hopefully a one-off, 'cos it's not how projects work at Apache.
> Though I expect
> > Stephen is evaluating an option, which is just fine.
> >
> >> We are looking for a more stable institutional home for Graphviz.
> Apache seems like
> >> a great match. Is this possible?  How is a decision like that made?
> I’m not sure a mature
> >> project like this fits the incubator model. Are there other ways?
> >
> > Many mature projects go through the Incubator.
> >
> > What discussions have you had within your project community?  Probably
> the
> > single most important criterion for you is to have your own community
> firmly
> > on board, and not dragging anyone reluctantly along.  Once you have
> that, you
> > find someone to champion your project within Apache, and submit a
> proposal.
> >
> > Romain wrote:
> >> Also it will let Graphviz time to handle the license switch.
> >
> > That's the kind of issue that could be quite big.  If it has a long
> history under another
> > license, you may have lots of contributors with a stake in it who would
> have to agree
> > to the re-licensing.
>
> The project is licensed as Common Public License  [1] which is Class B.
> [2] It will take some work to relicense.
>
> Regards,
> Dave
>
> [1] http://www.graphviz.org/license/
> [2] https://www.apache.org/legal/resolved.html
>
>
> >
> > --
> > Nick Kew
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>

Re: [ANN] Please welcome Justin Mclean as the new Incubator PMC chair!

[Kevin A. McGrail]

Congrats!

--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Mon, Jun 4, 2018 at 10:34 AM, Juan P  wrote:

> Congratulations and thanks, Justin!
> Thanks Jhon for the effort!!
>
> On 4 June 2018 at 16:17, Makoto Yui  wrote:
>
> > Congratulations Justin! Happy to have a very active chair.
> > And, thank you for John for the hard work you have done.
> >
> > Makoto
> > 2018年6月4日(月) 22:49 Geertjan Wielenga :
> > >
> > > Congratulations and thanks for your great work and support of the
> Apache
> > > NetBeans (incubating) project, looking forward to even more
> interactions
> > > with you.
> > >
> > > Gj
> > >
> > > On Mon, Jun 4, 2018 at 3:10 PM, Sharan Foga  wrote:
> > >
> > > > Congratulations Justin and thanks John for all the hard work you have
> > done!
> > > >
> > > > On 2018/06/04 10:12:21, Bertrand Delacretaz 
> > > > wrote:
> > > > > Hi,
> > > > >
> > > > > John D. Ament recently announced his desire to step down from the
> > > > > Incubator PMC chair role. Thank you so much John for your efficient
> > > > > service here, "retiring" from that is certainly well deserved!
> > > > >
> > > > > The Incubator PMC had the difficult task of choosing between a
> > handful
> > > > > of excellent candidates and has selected Justin as our new chair.
> The
> > > > > ASF's Board of Directors has ratified this choice at our May
> meeting.
> > > > >
> > > > > Please join me in welcoming Jusin as our new PMC chair! Justin's
> been
> > > > > very active in the Incubator in the last few years, it's great to
> see
> > > > > him step up to this role.
> > > > >
> > > > > -Bertrand
> > > > >
> > > > > 
> > -
> > > > > 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
> > > >
> > > >
> >
> > --
> > Makoto YUI 
> > Research Engineer, Treasure Data, Inc.
> > http://myui.github.io/
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [VOTE] Accept Doris into the Apache Incubator

[Kevin A. McGrail]

+1 Binding

A minor note:  Things like MPP should be spelled out at least once.  Your
proposal was technical and it helps if you think about trying to explain it
to an engineer who doesn't now Impala or Mesos or SQL, etc.

--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Thu, Jul 5, 2018 at 3:22 PM, Dave Fisher  wrote:

> Hi All,
>
> I would like to start a VOTE to bring the Doris project as an Apache
> incubator podling.
>
> The ASF voting rules are described:
>
> https://www.apache.org/foundation/voting.html
>
> A vote for accepting a new Apache Incubator podling is a majority vote for 
> which
> only Incubator PMC member votes are binding.
>
> This vote will run for at least 72 hours. Please VOTE as follows
> [] +1 Accept Doris into the Apache Incubator
> [] +0 Abstain.
> [] -1 Do not accept Doris into the Apache Incubator because ...
>
> The proposal is listed below, but you can also access it on the wiki:
>
> https://wiki.apache.org/incubator/DorisProposal
>
> Best regards,
> Dave
>
> = Apache Doris =
>
> == Abstract ==
>
> Doris is a MPP-based interactive SQL data warehousing for reporting and
> analysis.
>
> == Proposal ==
>
> We propose to contribute the Doris codebase and associated artifacts (e.g.
> documentation, web-site content etc.) to the Apache Software Foundation,
> and aim to build an open community around Doris’s continued development in
> the ‘Apache Way’.
>
> === Overview of Doris ===
>
> Doris’s implementation consists of two daemons: Frontend (FE) and Backend
> (BE).
>
> **Frontend daemon** consists of query coordinator and catalog manager.
> Query coordinator is responsible for receiving users’ sql queries,
> compiling queries and managing queries execution. Catalog manager is
> responsible for managing metadata such as databases, tables, partitions,
> replicas and etc. Several frontend daemons could be deployed to guarantee
> fault-tolerance, and load balancing.
>
> **Backend daemon** stores the data and executes the query fragments. Many
> backend daemons could also be deployed to provide scalability and
> fault-tolerance.
>
> A typical Doris cluster generally composes of several frontend daemons and
> dozens to hundreds of backend daemons.
>
> Users can use MySQL client tools to connect any frontend daemon to submit
> SQL query. Frontend receives the query and compiles it into query plans
> executable by the Backend. Then Frontend sends the query plan fragments to
> Backend. Backend will build a query execution DAG. Data is fetched and
> pipelined into the DAG. The final result response is sent to client via
> Frontend. The distribution of query fragment execution takes minimizing
> data movement and maximizing scan locality as the main goal.
>
> == Background ==
>
> At Baidu, Prior to Doris, different tools were deployed to solve diverse
> requirements in many ways. And when a use case requires the simultaneous
> availability of capabilities that cannot all be provided by a single tool,
> users were forced to build hybrid architectures that stitch multiple tools
> together, but we believe that they shouldn’t need to accept such inherent
> complexity. A storage system built to provide great performance across a
> broad range of workloads provides a more elegant solution to the problems
> that hybrid architectures aim to solve. Doris is the solution.
>
> Doris is designed to be a simple and single tightly coupled system, not
> depending on other systems. Doris provides high concurrent low latency
> point query performance, but also provides high throughput queries of
> ad-hoc analysis. Doris provides bulk-batch data loading, but also provides
> near real-time mini-batch data loading. Doris also provides high
> availability, reliability, fault tolerance, and scalability.
>
> == Rationale ==
>
> Doris mainly integrates the technology of Google Mesa and Apache Impala.
>
> Mesa is a highly scalable analytic data storage system that stores
> critical measurement data related to Google's Internet advertising
> business. Mesa is designed to satisfy complex and challenging set of users’
> and systems’ requirements, including near real-time data ingestion and
> query ability, as well as high availability, reliability, fault tolerance,
> and scalability for large data and query volumes.
>
> Impala is a modern, open-source MPP SQL engine architected from the ground
> up for the Hadoop data processing environment. At present, by virtue of its
> superior performance and rich functionality， Impala has been comparable to
> many commercial MPP database query engine. Mesa can satisf

Re: 20k Github stars for Dubbo

[Kevin A. McGrail]

+20k more stars!

--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Mon, Jul 9, 2018 at 12:40 PM, 吴晟 Sheng Wu  wrote:

> Good for the project and community. Congrats.
>
>
> If you are going to do service mesh component, let's discuss how
> SkyWalking works on your Mesher control panel, even data panel. I have
> already started to discuss this with Ant Finance team and Istio team. I
> heard some rumors that you are doing this right now. Glad to work together.
>
>
> And Congrats again. Wonderful work.
>
>
> --
> Sheng Wu
> Apache SkyWalking
>
>
>
>
>
>
>
> -- Original --
> From:  "Li,De(BDG)";
> Date:  Mon, Jul 9, 2018 04:49 PM
> To:  "general@incubator.apache.org";
> Cc:  "d...@dubbo.apache.org"; "hux...@apache.org"<
> hux...@apache.org>; "d...@community.apache.org";
> Subject:  Re: 20k Github stars for Dubbo
>
>
>
> It’s great, congratulations!
>
> On 2018/7/9 下午3:22， "Xin Wang"  wrote:
>
> >Awesome
> >
> >Zhanhui Li  于2018年7月9日周一 下午2:52写道：
> >
> >> Congratulations!
> >>
> >> > 在 2018年7月9日，下午2:42，Mercy  写道：
> >> >
> >> > Great Job!
> >> >
> >> >
> >> > Kind regards,
> >> >
> >> > Mercy
> >> >
> >> >
> >> > 在 2018/7/9 上午11:51, Huxing Zhang 写道:
> >> >> Hi All,
> >> >>
> >> >> I am happy to announce that Dubbo has reached 20k Github stars
> >> >> today[1], an important milestone for Dubbo.
> >> >>
> >> >> Dubbo is the first Java project that reaches 20k Github stars[2] in
> >> >> Apache Software Foundation, the second most[3] in terms of all
> >> >> languages in the foundation.
> >> >>
> >> >> Dubbo is open sources in 2012, till now, it is the most popular RPC
> >> >> framework in China, and has been adopted by many companies for their
> >> >> production system, including:
> >> >>
> >> >> Internet companies:
> >> >> * Alibaba
> >> >> * Dangdang
> >> >> * Qunar
> >> >> * Netease
> >> >> * etc.
> >> >>
> >> >> State-owned enterprises:
> >> >> * Industrial and Commercial Bank of China
> >> >> * China Telecom
> >> >> * China Life
> >> >> * etc.
> >> >>
> >> >> More use case can be found at the homepage:
> >> http://dubbo.incubator.apache.org/
> >> >>
> >> >> As an incubator project, the Dubbo PPMC will continue to make the
> >> >> community open and diverse, and we are more than happy to have
> >> >> everyone come to contribute, any question can be discussed on dev
> >> >> mailing list.
> >> >>
> >> >> [1] https://github.com/apache/incubator-dubbo
> >> >> [2]
> >>
> >>https://github.com/search?l=Java&o=desc&q=org%3Aapache&s=
> stars&type=Repos
> >>itories
> >> >> [3]
> >>
> >>https://github.com/search?o=desc&q=org%3Aapache&s=stars&;
> type=Repositories
> >> >>
> >> >
> >> >
> >> >
> >> > -
> >> > 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: [RESULT] [VOTE] Graduate Apache HAWQ (incubating)

[Kevin A. McGrail]

Very well said, Roman.  I didn't vote because I'm new to the IPMC and still
getting overwhelmed but you look like a great example of what I hope to
achieve!

--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

On Fri, Aug 3, 2018 at 8:54 AM, Lei Chang  wrote:

> Awesome. Thanks much Roman and all mentors.  :-)
>
> Cheers
> Lei
>
>
> On Fri, Aug 3, 2018 at 10:07 AM, Roman Shaposhnik  wrote:
>
> > On Fri, Jul 27, 2018 at 7:13 PM, Roman Shaposhnik 
> wrote:
> > > Hi!
> > >
> > > after a very positive discussion in the HAWQ community
> > > and at the IPMC level:
> > >  https://lists.apache.org/thread.html/67a2d52ef29cbf9e93d8050ed0193c
> > c110a919962dd92f8436b343b7@%3Cdev.hawq.apache.org%3E
> > >  https://lists.apache.org/thread.html/3a142d758ef5ae119e42107189
> > 3615992ea5ee937b5d02007f5e@%3Cgeneral.incubator.apache.org%3E
> > >
> > > I'd like to bring the following resolution for a formal vote.
> > >
> > > Please vote on the resolution pasted below to graduate
> > > Apache HAWQ from the incubator to top level project.
> > >
> > > [ ] +1 Graduate Apache HAWQ from the Incubator.
> > > [ ] +0 Don't care.
> > > [ ] -1 Don't graduate Apache HAWQ from the Incubator because...
> > >
> > > This vote will be open for at least 72 hours.
> > >
> > > Many thanks to our mentors and everyone else for the support,
> > > Roman (on behalf of the Apache HAWQ PPMC).
> > >
> > > ## Resolution to create a TLP from graduating Incubator podling
> > >
> > > X. Establish the Apache HAWQ 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 Hadoop native SQL query engine that
> > >combines the key technological advantages of MPP database
> > >with the scalability and convenience of Hadoop.
> > >
> > >NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> > >Committee (PMC), to be known as the "Apache HAWQ Project",
> > >be and hereby is established pursuant to Bylaws of the
> > >Foundation; and be it further
> > >
> > >RESOLVED, that the Apache HAWQ Project be and hereby is
> > >responsible for the creation and maintenance of software
> > >related to Hadoop native SQL query engine that
> > >combines the key technological advantages of MPP database
> > >with the scalability and convenience of Hadoop;
> > >and be it further
> > >
> > >RESOLVED, that the office of "Vice President, Apache HAWQ" 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 HAWQ Project, and to have primary responsibility
> > >for management of the projects within the scope of
> > >responsibility of the Apache HAWQ 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 HAWQ Project:
> > >
> > > * Alan Gates   
> > > * Alexander Denissov   
> > > * Amy Bai  
> > > * Atri Sharma  
> > > * Bhuvnesh Chaudhary   
> > > * Bosco
> > > * Chunling Wang
> > > * David Yozie  
> > > * Ed Espino
> > > * Entong Shen  
> > > * Foyzur Rahman
> > > * Goden Yao
> > > * Gregory Chase
> > > * Hong Wu  
> > > * Hongxu Ma
> > > * Hubert Zhang 
> > > * Ivan Weng
> > > * Jesse Zhang  
> > > * Jiali Yao
> > > * Jun Aoki 

Re: [PROPOSAL] Zipkin for Apache Incubator

[Kevin A. McGrail]

Have to say this made me chuckle:


  A Excessive Fascination with the Apache Brand

I'm +1 on this proposal.

Re: [PROPOSAL] Zipkin for Apache Incubator

[Kevin A. McGrail]

That's less chucklesome then but still a good proposal. 

5 points from Gryffindor for not changing boilerplate.

On 8/20/2018 7:56 AM, Jim Jagielski wrote:
> That's boilerplate:
>
>https://incubator.apache.org/guides/proposal.html
>https://wiki.apache.org/incubator/ProjectProposals
>
>> On Aug 17, 2018, at 9:58 AM, Kevin A. McGrail  wrote:
>>
>> Have to say this made me chuckle:
>>
>>
>>  A Excessive Fascination with the Apache Brand
>>
>> I'm +1 on this proposal.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>


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

Re: [VOTE] Accept Zipkin into the Apache Incubator

[Kevin A. McGrail]

+1 (binding)
On 8/27/2018 3:27 PM, Josh Elser wrote:
> +1 (binding)
>
> On 8/26/18 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 collaborative process, it lacks
>> formality around

Re: Graduation Resolutions Should Not Include Project Bylaws Clause

[Kevin A. McGrail]

Good point, Dave.  +board as this was an issue with emeritus pmc and
project bylaws

On Sun, Sep 2, 2018, 12:37 Dave Fisher  wrote:

> Hi -
>
> Pulsar is currently discussing a graduation proposal and Taylor noticed
> the following that came out of the whimsy boilerplate.
>
> Quick question:
>
> RESOLVED, that the initial Apache Pulsar PMC be and hereby is tasked
> with the creation of a set of bylaws intended to encourage open
> development and increased participation in the Apache Pulsar Project;
> and be it further
>
>
> Does the Pulsar PPMC feel the need to adopt bylaws (it’s not required), or
> are the Apache defaults acceptable?
>
> One option is to simply not have bylaws, which means you would simply
> adhere to [1] and [2], and put any clarifications in a contributors’ guide
> (which you’ve done).
>
> -Taylor
>
> [1] http://www.apache.org/foundation/voting.html
> [2] http://www.apache.org/dev/pmc.html
>
>
> I think that this clause needs to be removed from the template.
>
> Regards,
> Dave
>
>

Re: Graduation Resolutions Should Not Include Project Bylaws Clause

[Kevin A. McGrail]

Apologies.  Did not know general@ was a private list.

On Sun, Sep 2, 2018, 14:29 Dave Fisher  wrote:

> Note the cross-posting between public and private mailing lists.
>
> Sent from my iPhone
>
> > On Sep 2, 2018, at 11:22 AM, Kevin A. McGrail 
> wrote:
> >
> > Good point, Dave.  +board as this was an issue with emeritus pmc and
> > project bylaws
> >
> >> On Sun, Sep 2, 2018, 12:37 Dave Fisher  wrote:
> >>
> >> Hi -
> >>
> >> Pulsar is currently discussing a graduation proposal and Taylor noticed
> >> the following that came out of the whimsy boilerplate.
> >>
> >> Quick question:
> >>
> >> RESOLVED, that the initial Apache Pulsar PMC be and hereby is tasked
> >> with the creation of a set of bylaws intended to encourage open
> >> development and increased participation in the Apache Pulsar Project;
> >> and be it further
> >>
> >>
> >> Does the Pulsar PPMC feel the need to adopt bylaws (it’s not required),
> or
> >> are the Apache defaults acceptable?
> >>
> >> One option is to simply not have bylaws, which means you would simply
> >> adhere to [1] and [2], and put any clarifications in a contributors’
> guide
> >> (which you’ve done).
> >>
> >> -Taylor
> >>
> >> [1] http://www.apache.org/foundation/voting.html
> >> [2] http://www.apache.org/dev/pmc.html
> >>
> >>
> >> I think that this clause needs to be removed from the template.
> >>
> >> Regards,
> >> Dave
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: We want to contribute brpc to ASF, looking for champion and mentor ,please help

[Kevin A. McGrail]

example, Baidu is extensively using it in their production
>>>>>> environment
>>>>>> and many large corporations including Iqiyi, Didi, Sougou, BiliBili
>>>>>> use
>>>>>> it in their production applications.
>>>>>>
>>>>>>
>>>>>> ### Inexperience with Open Source
>>>>>>
>>>>>> brpc has been an active open source project for more than one year.
>>>>>> During that time, the project has attracted 30+ contributors and
>>>>>> gained
>>>>>> a lot of attention.
>>>>>> The core developers are all active users and followers of open source.
>>>>>>
>>>>>> ### Homogenous Developers
>>>>>>
>>>>>> brpc was created inside Baidu, but after brpc was open sourced, it
>>>>>> received a lot of bug fixes and enhancements from other developers not
>>>>>> working at Baidu.
>>>>>> And the core developers now are from different companies now.
>>>>>>
>>>>>> ### Reliance on Salaried Developers
>>>>>>
>>>>>> Baidu invested in brpc as a general rpc framework used in company
>>>>>> widely.
>>>>>> The core developers have been dedicated to this project for about four
>>>>>> years.
>>>>>> And after its open source, developers around the world have involved
>>>>>> in.
>>>>>> Besides, we want more developers and researchers to contribute to the
>>>>>> project.
>>>>>>
>>>>>> ### An Excessive Fascination with the Apache Brand
>>>>>>
>>>>>> The mission of brpc is to help developers build reliable and
>>>>>> high-performance services quickly and easily.
>>>>>> It has been widely used in production environment throughout Baidu and
>>>>>> after opensource, it has gained much attention and attracted
>>>>>> developers
>>>>>> all over the world.
>>>>>> Apache Brand is very respected. We are very honored to have the
>>>>>> opportunity to join ASF, with the understanding that its brand
>>>>>> policies
>>>>>> being respected.
>>>>>> And we hope Apache can help us build the ecosystem around brpc and
>>>>>> attract more developers.
>>>>>>
>>>>>>
>>>>>> ## Documentation
>>>>>>
>>>>>> The following links provide more information about brpc in open
>>>>>> source:
>>>>>>
>>>>>> Codebase at Github: https://github.com/brpc/brpc
>>>>>> Issue Tracking: https://github.com/brpc/brpc/issues
>>>>>> Overview: https://github.com/brpc/brpc/blob/master/docs/en/overview.md
>>>>>>
>>>>>> ## Initial Source
>>>>>>
>>>>>> brpc has been developed since 2014 by a team of engineers at Baidu
>>>>>> Inc.
>>>>>> We currently use Github to maintain our source code and track issues
>>>>>> at
>>>>>> https://github.com/brpc/brpc.
>>>>>> We need to move our repository to Apache infrastructure.
>>>>>>
>>>>>> ## Source and Intellectual Property Submission Plan
>>>>>>
>>>>>> brpc source code is available under Apache V2 license and owned by
>>>>>> Baidu.
>>>>>> We will work with the committers to get ICLAs signed. We will provide
>>>>>> a
>>>>>> Software Grant Agreement from an authorized signer per
>>>>>> https://www.apache.org/licenses/software-grant-template.pdf
>>>>>>
>>>>>> ## External Dependencies
>>>>>>
>>>>>> brpc has the following external dependencies.
>>>>>>
>>>>>> * Google gflags (BSD)
>>>>>> * Google protobuf (BSD)
>>>>>> * Google leveldb (BSD)
>>>>>>
>>>>>> ## Required Resources
>>>>>>
>>>>>> ### Mailing List
>>>>>>
>>>>>> There are currently no mailing lists. The usual mailing lists are
>>>>>> expected to be set up when entering incubation:
>>>>>>
>>>>>> * priv...@brpc.incubator.apache.org
>>>>>> * d...@brpc.incubator.apache.org
>>>>>> * comm...@brpc.incubator.apache.org
>>>>>>
>>>>>> ### Git Repositories:
>>>>>>
>>>>>> Upon entering incubation, we want to transfer the existing repo from
>>>>>> https://github.com/brpc/brpc to Apache infrastructure like
>>>>>> https://github.com/apache/incubator-brpc.
>>>>>>
>>>>>> ### Issue Tracking:
>>>>>>
>>>>>> brpc currently uses GitHub to track issues. Would like to continue to
>>>>>> do so while we discuss migration possibilities with the ASF Infra
>>>>>> committee.
>>>>>>
>>>>>> ### Other Resources:
>>>>>>
>>>>>> Currently brpc has no dedicated website except Github homepage. In the
>>>>>> future the website url should be http://brpc.incubator.apache.org/ to
>>>>>> follow apache incubator conventions.
>>>>>>
>>>>>> ## Sponsors
>>>>>>
>>>>>> ### Champion
>>>>>>
>>>>>> * todo
>>>>>>
>>>>>> ### Mentors
>>>>>>
>>>>>> * todo
>>>>>>
>>>>>> ### Sponsoring Entity
>>>>>>
>>>>>> We are requesting the Incubator to sponsor this project.
>>>>>>
>>>>> -- 
>>>>> Jean-Baptiste Onofré
>>>>> jbono...@apache.org
>>>>> http://blog.nanthrax.net
>>>>> Talend - http://www.talend.com
>>>>>
>>>>> -
>>>>> 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
>>>>
>>> -- 
>>> Jean-Baptiste Onofré
>>> jbono...@apache.org
>>> http://blog.nanthrax.net
>>> Talend - http://www.talend.com
>>>
>>> -
>>> 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
>>

-- 
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: We want to contribute brpc to ASF, looking for champion and mentor ,please help

[Kevin A. McGrail]

On 9/18/2018 12:11 AM, Tan,Zhongyi wrote:
> Thanks，Kevin.
>
Thanks, Tan.

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

Re: We want to contribute brpc to ASF, looking for champion and mentor ,please help

[Kevin A. McGrail]

.
>>>>>>>>>
>>>>>>>>> ### Homogenous Developers
>>>>>>>>>
>>>>>>>>> brpc was created inside Baidu, but after brpc was open sourced, it
>>>>>>>>> received a lot of bug fixes and enhancements from other developers
>>>>>>>>> not
>>>>>>>>> working at Baidu.
>>>>>>>>> And the core developers now are from different companies now.
>>>>>>>>>
>>>>>>>>> ### Reliance on Salaried Developers
>>>>>>>>>
>>>>>>>>> Baidu invested in brpc as a general rpc framework used in company
>>>>>>>>> widely.
>>>>>>>>> The core developers have been dedicated to this project for about
>>>>>>>>> four
>>>>>>>>> years.
>>>>>>>>> And after its open source, developers around the world have
>>>>>>>>> involved
>>>>>>>>> in.
>>>>>>>>> Besides, we want more developers and researchers to contribute to
>>>>>>>>> the
>>>>>>>>> project.
>>>>>>>>>
>>>>>>>>> ### An Excessive Fascination with the Apache Brand
>>>>>>>>>
>>>>>>>>> The mission of brpc is to help developers build reliable and
>>>>>>>>> high-performance services quickly and easily.
>>>>>>>>> It has been widely used in production environment throughout Baidu
>>>>>>>>> and
>>>>>>>>> after opensource, it has gained much attention and attracted
>>>>>>>>> developers
>>>>>>>>> all over the world.
>>>>>>>>> Apache Brand is very respected. We are very honored to have the
>>>>>>>>> opportunity to join ASF, with the understanding that its brand
>>>>>>>>> policies
>>>>>>>>> being respected.
>>>>>>>>> And we hope Apache can help us build the ecosystem around brpc and
>>>>>>>>> attract more developers.
>>>>>>>>>
>>>>>>>>>
>>>>>>>>> ## Documentation
>>>>>>>>>
>>>>>>>>> The following links provide more information about brpc in open
>>>>>>>>> source:
>>>>>>>>>
>>>>>>>>> Codebase at Github: https://github.com/brpc/brpc
>>>>>>>>> Issue Tracking: https://github.com/brpc/brpc/issues
>>>>>>>>> Overview: 
>>>>>>>>> https://github.com/brpc/brpc/blob/master/docs/en/overview.md
>>>>>>>>>
>>>>>>>>> ## Initial Source
>>>>>>>>>
>>>>>>>>> brpc has been developed since 2014 by a team of engineers at Baidu
>>>>>>>>> Inc.
>>>>>>>>> We currently use Github to maintain our source code and track
>>>>>>>>> issues
>>>>>>>>> at
>>>>>>>>> https://github.com/brpc/brpc.
>>>>>>>>> We need to move our repository to Apache infrastructure.
>>>>>>>>>
>>>>>>>>> ## Source and Intellectual Property Submission Plan
>>>>>>>>>
>>>>>>>>> brpc source code is available under Apache V2 license and owned by
>>>>>>>>> Baidu.
>>>>>>>>> We will work with the committers to get ICLAs signed. We will
>>>>>>>>> provide
>>>>>>>>> a
>>>>>>>>> Software Grant Agreement from an authorized signer per
>>>>>>>>> https://www.apache.org/licenses/software-grant-template.pdf
>>>>>>>>>
>>>>>>>>> ## External Dependencies
>>>>>>>>>
>>>>>>>>> brpc has the following external dependencies.
>>>>>>>>>
>>>>>>>>> * Google gflags (BSD)
>>>>>>>>> * Google protobuf (BSD)
>>>>>>>>> * Google leveldb (BSD)
>>>>>>>>>
>>>>>>>>> ## Required Resources
>>>>>>>>>
>>>>>>>>> ### Mailing List
>>>>>>>>>
>>>>>>>>> There are currently no mailing lists. The usual mailing lists are
>>>>>>>>> expected to be set up when entering incubation:
>>>>>>>>>
>>>>>>>>> * priv...@brpc.incubator.apache.org
>>>>>>>>> * d...@brpc.incubator.apache.org
>>>>>>>>> * comm...@brpc.incubator.apache.org
>>>>>>>>>
>>>>>>>>> ### Git Repositories:
>>>>>>>>>
>>>>>>>>> Upon entering incubation, we want to transfer the existing repo
>>>>>>>>> from
>>>>>>>>> https://github.com/brpc/brpc to Apache infrastructure like
>>>>>>>>> https://github.com/apache/incubator-brpc.
>>>>>>>>>
>>>>>>>>> ### Issue Tracking:
>>>>>>>>>
>>>>>>>>> brpc currently uses GitHub to track issues. Would like to continue
>>>>>>>>> to
>>>>>>>>> do so while we discuss migration possibilities with the ASF Infra
>>>>>>>>> committee.
>>>>>>>>>
>>>>>>>>> ### Other Resources:
>>>>>>>>>
>>>>>>>>> Currently brpc has no dedicated website except Github homepage. In
>>>>>>>>> the
>>>>>>>>> future the website url should be http://brpc.incubator.apache.org/
>>>>>>>>> to
>>>>>>>>> follow apache incubator conventions.
>>>>>>>>>
>>>>>>>>> ## Sponsors
>>>>>>>>>
>>>>>>>>> ### Champion
>>>>>>>>>
>>>>>>>>> * todo
>>>>>>>>>
>>>>>>>>> ### Mentors
>>>>>>>>>
>>>>>>>>> * todo
>>>>>>>>>
>>>>>>>>> ### Sponsoring Entity
>>>>>>>>>
>>>>>>>>> We are requesting the Incubator to sponsor this project.
>>>>>>>>>
>>>>>>>> -- 
>>>>>>>> Jean-Baptiste Onofré
>>>>>>>> jbono...@apache.org
>>>>>>>> http://blog.nanthrax.net
>>>>>>>> Talend - http://www.talend.com
>>>>>>>>
>>>>>>>>
>>>>>>>> 
>>>>>>>> -
>>>>>>>> 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
>>>>>>>
>>>>>> -- 
>>>>>> Jean-Baptiste Onofré
>>>>>> jbono...@apache.org
>>>>>> http://blog.nanthrax.net
>>>>>> Talend - http://www.talend.com
>>>>>>
>>>>>> -
>>>>>> 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
>>>>>
>>>> -- 
>>>> Jean-Baptiste Onofré
>>>> jbono...@apache.org
>>>> http://blog.nanthrax.net
>>>> Talend - http://www.talend.com
>>>>
>>>> -
>>>> 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
>>>
>> -- 
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>> -
>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> For additional commands, e-mail: general-h...@incubator.apache.org
>>

-- 
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: [Question] Is a mirror website of skywalking project allowed?

[Kevin A. McGrail]

It would be better if the skywalking.io just redirected to the official *.
apache.org page
See https://www.apache.org/foundation/marks/pmcs

Regards,
KAM
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Tue, Oct 23, 2018 at 8:28 AM 吴晟 Sheng Wu  wrote:

> Hi,
>
>
> SkyWalking has official Apache website[1], also SkyWalking has another
> website[2] which uses the same codebases of our Apache website(same
> content), but hosted in GitHub(not a redirect).
>
>
> I want to ask, is this allowed by Apache? We are talking about graduation
> now, our mentor Mick suggests us to ask at here.
>
>
> [1] http://skywalking.apache.org/
> [2] http://skywalking.io/
>
>
> --
> Sheng Wu
> Apache SkyWalking

Re: Draft email to member list to try and recruit some new mentors

[Kevin A. McGrail]

On 10/26/2018 8:53 PM, Justin Mclean wrote:
> I’m planning an sending an email to members@ to try and help get a few more 
> mentors on board.
I'm +1 for anything to try and cajole more mentors!



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

Re: UNICEF Open Source project- Apache Foundation

[Kevin A. McGrail]

In addition to the list responses, I'm happy to chat especially with my VP
Fundraising duties. Love UNICEF and love what you do especially around
Halloween.  Happy to jump on a call and give you some guidance!

Regards,
KAM
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Sun, Oct 28, 2018 at 1:39 AM Dave Fisher  wrote:

> Exactly as Kellen describes!
>
> If for whatever reason you require an offline discussion to start then I’m
> sure someone here may be willing to “champion” your proposal.
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Oct 27, 2018, at 9:43 PM, kellen sunderland <
> kellen.sunderl...@gmail.com> wrote:
> >
> > Hello Ariam, reading through the sites in your signature it looks like
> > you're doing interesting work.  I'm always happy to see governments and
> > NGOs using / contributing to open source.
> >
> > Speaking for myself, I would be happy to set aside some time to chat.  At
> > Apache we do try to keep as much communication as possible on public
> email
> > lists.  Would you be able to give a little more detail about your project
> > via this list?  Were you interested in collaborating with Apache?  Did
> you
> > want to participate in the Apache Incubator program?
> >
> > -Kellen
> >
> >> On Sat, Oct 27, 2018 at 9:42 AM Ariam Mogos  wrote:
> >>
> >> Hi there,
> >>
> >> I work in UNICEF’s Office of Innovation and was hoping to speak to
> someone
> >> about a fantastic open source project in which we’re interested in
> working
> >> with the Apache Foundation.
> >>
> >> Look forward to hearing from you.
> >>
> >> Best,
> >> Ariam
> >>
> >> -
> >> Ariam Mogos
> >> Learning Lead
> >> UNICEF Ventures
> >> Office of Innovation
> >> skype: ariammogos
> >> mobile: +1 917-974-5997
> >>
> >> www.unicefstories.org<http://www.unicefstories.org/>
> >> www.unicefinnovationfund.org<http://www.unicefinnovationfund.org/>
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [DISCUSS] IoTDB Incubation Proposal

[Kevin A. McGrail]

Thanks Justin.  That's awesome.

I'd like to mention that I've worked closely with the IoTDB team for a few
weeks on improving the proposal after they gave an excellent initial
presentation as well.

Regards,
KAM
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Sun, Oct 28, 2018 at 10:42 PM Justin Mclean 
wrote:

> Hi,
>
> I'm interested in your project and would like to be a mentor if you'll have
> me. I'm the mentor fur a number of IoT projects here at the ASF.
>
> Thanks,
> Justin
>
> On Mon., 29 Oct. 2018, 11:35 am Xiangdong Huang,  wrote:
>
> > Dear Apache Incubator Community,
> >
> >
> > I would like to open up a discussion about incubating IoTDB at Apache.
> > IoTDB is a database for managing large amounts of time series data  from
> > IoT sensors in industrial applications.
> >
> >
> > The proposal is available as a draft at
> > https://wiki.apache.org/incubator/IoTDBProposal . I have also included
> > the text of the proposal below.
> >
> >
> >
> >
> > = IoTDB Proposal  =
> > v0.1
> >
> >
> > == Abstract ==
> > IoTDB is a database for managing large amounts of time series data such
> as
> > timestamped data from IoT sensors in industrial applications.
> >
> >
> > == Proposal ==
> > IoTDB is a database for managing large amount of time series data with
> > columnar storage, data encoding, pre-computation, and index techniques.
> It
> > has SQL-like interface to write millions of data points per second per
> node
> > and is optimized to get query results in few seconds over trillions of
> data
> > points. It can also be easily integrated with Apache Hadoop MapReduce and
> > Apache Spark for analytics.
> >
> >
> > == Background ==
> >
> >
> > A new class of data management system requirements is becoming
> > increasingly important with the rise of the Internet of Things. There are
> > some database systems and technologies aimed at time series data
> > management.  For example, Gorilla and InfluxDB which are mainly built for
> > data centers and monitoring application metrics. Other systems, for
> > example, OpenTSDB and KairosDB, are built on Apache HBase and Apache
> > Cassandra, respectively.
> >
> >
> > However, many applications for time series data management have more
> > requirements especially in industrial applications as follows:
> >
> >
> >  * Supporting time series data which has high data frequency. For
> example,
> > a turbine engine may generate 1000 points per second (i.e., 1000Hz),
> while
> > each CPU only reports 1 data points per 5 seconds in a data center
> > monitoring application.
> >
> >
> >  * Supporting scanning data multi-resolutionally. For example,
> aggregation
> > operation is important for time series data.
> >
> >
> >  * Supporting special queries for time series, such as pattern matching,
> > time series segmentation, time-frequency transformation and frequency
> query.
> >
> >
> >  * Supporting a large number of monitoring targets (i.e. time series). An
> > excavator may report more than 1000 time series, for example, revolving
> > speed of the motor-engine, the speed of the excavator, the accelerated
> > speed, the temperature of the water tank and so on, while a CPU or an
> > application monitor has much fewer time series.
> >
> >
> >  * Optimization for out-of-order data points. In the industrial sector,
> it
> > is common that equipment sends data using the UDP protocol rather than
> the
> > TCP protocol. Sometimes, the network connect is unstable and parts of the
> > data will be buffered for later sending.
> >
> >
> >  * Supporting long-term storage. Historical data is precious for
> equipment
> > manufacturers. Therefore, removing or unloading historical data is highly
> > desired for most industrial applications. The database system must not
> only
> > support fast retrieval of historical data, but also should guarantee that
> > the historical data does not impact the processing speed for “hot” or
> > current data.
> >
> >
> >  * Supporting online transaction processing (OLTP) as well as complex
> > analytics. It is obvious that supporting analyzing from the data files
> > using Apache Spark/Apache Hadoop MapReduce directly is better than
> > transforming data files to another file format for Big Data analytics.
> >
> &

Re: UNICEF Open Source project- Apache Foundation

[Kevin A. McGrail]

Thanks Ariam,

I have a child with Autism so this is very interesting to me and I also
helped found the largest support group in the Washington DC area.  I
have done grants for curriculum to teach children with autism to swim
with Autism Speaks and I can talk intelligently about AT/PECS.  We also
just had our keynote from Cliff Schmidt at Amplio which has some
crossover.  Anyway, enough about me, I'd like to setup a call, nothing
long and talk about our incubator and how we work/what we do.

Regards,
KAM


On 10/29/2018 3:53 PM, Ariam Mogos wrote:
>
> Thanks so much Kellen, Dave and Kevin!
>
> (copying Aditi from our partnerships team)
>
> (copying David Banes and EA Draffan, two of our advisors on AAC)
>
>  
>
> Yes we’d be interested in collaborating with Apache and learning more
> about the incubator program.
>
>  
>
> We’re very excited to share about this project. I’ve created a google
> doc with some information here:
>
>  
>
> https://docs.google.com/document/d/1fMY5_YgqqE5VfqNCDwQ0HQe8ozkz1v7kpjQpimVsjuI/edit
>
>  
>
> Please feel free to leave any comments, questions, recommendations in
> the document.
>
>  
>
> Cheers,
> Ariam
>
>  
>
> *From: *"Kevin A. McGrail" 
> *Date: *Sunday, October 28, 2018 at 4:51 PM
> *To: *"general@incubator.apache.org" 
> *Cc: *Ariam Mogos 
> *Subject: *Re: UNICEF Open Source project- Apache Foundation
>
>  
>
> In addition to the list responses, I'm happy to chat especially with
> my VP Fundraising duties. Love UNICEF and love what you do especially
> around Halloween.  Happy to jump on a call and give you some guidance!
>
>  
>
> Regards,
>
> KAM
>
> --
>
> Kevin A. McGrail
>
> VP Fundraising, Apache Software Foundation
>
> Chair Emeritus Apache SpamAssassin Project
>
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>  
>
>  
>
> On Sun, Oct 28, 2018 at 1:39 AM Dave Fisher  <mailto:dave2w...@comcast.net>> wrote:
>
> Exactly as Kellen describes!
>
> If for whatever reason you require an offline discussion to start
> then I’m sure someone here may be willing to “champion” your proposal.
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Oct 27, 2018, at 9:43 PM, kellen sunderland
> mailto:kellen.sunderl...@gmail.com>>
> wrote:
> >
> > Hello Ariam, reading through the sites in your signature it
> looks like
> > you're doing interesting work.  I'm always happy to see
> governments and
> > NGOs using / contributing to open source.
> >
> > Speaking for myself, I would be happy to set aside some time to
> chat.  At
> > Apache we do try to keep as much communication as possible on
> public email
> > lists.  Would you be able to give a little more detail about
> your project
> > via this list?  Were you interested in collaborating with
> Apache?  Did you
> > want to participate in the Apache Incubator program?
> >
> > -Kellen
> >
> >> On Sat, Oct 27, 2018 at 9:42 AM Ariam Mogos  <mailto:amo...@unicef.org>> wrote:
> >>
> >> Hi there,
> >>
> >> I work in UNICEF’s Office of Innovation and was hoping to speak
> to someone
> >> about a fantastic open source project in which we’re interested
> in working
> >> with the Apache Foundation.
> >>
> >> Look forward to hearing from you.
> >>
> >> Best,
> >> Ariam
> >>
> >> -
> >> Ariam Mogos
> >> Learning Lead
> >> UNICEF Ventures
> >> Office of Innovation
> >> skype: ariammogos
> >> mobile: +1 917-974-5997
> >>
> >> www.unicefstories.org
> <http://www.unicefstories.org><http://www.unicefstories.org/>
> >> www.unicefinnovationfund.org
> 
> <http://www.unicefinnovationfund.org><http://www.unicefinnovationfund.org/>
> >>
> >>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> <mailto:general-unsubscr...@incubator.apache.org>
> For additional commands, e-mail: general-h...@incubator.apache.org
> <mailto:general-h...@incubator.apache.org>
>

-- 
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

Re: UNICEF Open Source project- Apache Foundation

[Kevin A. McGrail]

Thanks David for the introduction.  Ariam, I am located in Fairfax so a
meeting in DC is more than possible.

Can I give you a call to coordinate?  If so, what's a good number to reach
you?
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Mon, Oct 29, 2018 at 4:57 PM  wrote:

> Just to quickly introduce EA and myself – we work together in a not for
> profit at globalsymbols.com
>
>
>
> We are very much committed to both open licence and working in the open,
> and have a special interest in seeking to ensure that AAC reaches those
> communities that have been most under served in this field
>
>
>
> One of our first projects was in the Middle East where we collaborated to
> develop Tawasol, the Arabic open symbol set, designed to reflect both
> language and culture within the Middle East and especially the gulf. To do
> that we created a system that democratised symbol design, allowing a range
> of stakeholder to determine the design and selection of symbols to
> represent concepts.
>
>
>
> Very much hope to continue discussions together about collaboration around
> the paper Ariam has distributed
>
>
>
> Best regards
>
>
>
> David
>
>
>
> *From:* Kevin A. McGrail 
> *Sent:* 29 October 2018 20:49
> *To:* Ariam Mogos ; general@incubator.apache.org
> *Cc:* Aditi Poddar ; da...@davebanesaccess.org; EA
> Draffan 
> *Subject:* Re: UNICEF Open Source project- Apache Foundation
>
>
>
> Thanks Ariam,
>
> I have a child with Autism so this is very interesting to me and I also
> helped found the largest support group in the Washington DC area.  I have
> done grants for curriculum to teach children with autism to swim with
> Autism Speaks and I can talk intelligently about AT/PECS.  We also just had
> our keynote from Cliff Schmidt at Amplio which has some crossover.  Anyway,
> enough about me, I'd like to setup a call, nothing long and talk about our
> incubator and how we work/what we do.
>
> Regards,
> KAM
>
>
> On 10/29/2018 3:53 PM, Ariam Mogos wrote:
>
> Thanks so much Kellen, Dave and Kevin!
>
> (copying Aditi from our partnerships team)
>
> (copying David Banes and EA Draffan, two of our advisors on AAC)
>
>
>
> Yes we’d be interested in collaborating with Apache and learning more
> about the incubator program.
>
>
>
> We’re very excited to share about this project. I’ve created a google doc
> with some information here:
>
>
>
>
> https://docs.google.com/document/d/1fMY5_YgqqE5VfqNCDwQ0HQe8ozkz1v7kpjQpimVsjuI/edit
>
>
>
> Please feel free to leave any comments, questions, recommendations in the
> document.
>
>
>
> Cheers,
> Ariam
>
>
>
> *From: *"Kevin A. McGrail"  
> *Date: *Sunday, October 28, 2018 at 4:51 PM
> *To: *"general@incubator.apache.org" 
>  
> *Cc: *Ariam Mogos  
> *Subject: *Re: UNICEF Open Source project- Apache Foundation
>
>
>
> In addition to the list responses, I'm happy to chat especially with my VP
> Fundraising duties. Love UNICEF and love what you do especially around
> Halloween.  Happy to jump on a call and give you some guidance!
>
>
>
> Regards,
>
> KAM
>
> --
>
> Kevin A. McGrail
>
> VP Fundraising, Apache Software Foundation
>
> Chair Emeritus Apache SpamAssassin Project
>
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>
>
>
>
> On Sun, Oct 28, 2018 at 1:39 AM Dave Fisher  wrote:
>
> Exactly as Kellen describes!
>
> If for whatever reason you require an offline discussion to start then I’m
> sure someone here may be willing to “champion” your proposal.
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Oct 27, 2018, at 9:43 PM, kellen sunderland <
> kellen.sunderl...@gmail.com> wrote:
> >
> > Hello Ariam, reading through the sites in your signature it looks like
> > you're doing interesting work.  I'm always happy to see governments and
> > NGOs using / contributing to open source.
> >
> > Speaking for myself, I would be happy to set aside some time to chat.  At
> > Apache we do try to keep as much communication as possible on public
> email
> > lists.  Would you be able to give a little more detail about your project
> > via this list?  Were you interested in collaborating with Apache?  Did
> you
> > want to participate in the Apache Incubator program?
> >
> > -Kellen
> >
> >> On Sat, Oct 27, 2018 at 9:42 AM Ariam Mogos  wrote:
> >>
> >> Hi there,
> >>
> >> I 

Re: UNICEF Open Source project- Apache Foundation

[Kevin A. McGrail]

Thanks Ariam, got your v/m.  Feel free to call me back at 703 798 0171.
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Tue, Oct 30, 2018 at 11:44 AM Ariam Mogos  wrote:

> Sure, sounds good Kevin. You can reach me at 917.974.5997.
>
>
>
> *From: *"Kevin A. McGrail" 
> *Date: *Monday, October 29, 2018 at 6:27 PM
> *To: *"da...@davebanesaccess.org" 
> *Cc: *Ariam Mogos , "general@incubator.apache.org" <
> general@incubator.apache.org>, Aditi Poddar , "
> e...@ecs.soton.ac.uk" 
> *Subject: *Re: UNICEF Open Source project- Apache Foundation
>
>
>
> Thanks David for the introduction.  Ariam, I am located in Fairfax so a
> meeting in DC is more than possible.
>
>
>
> Can I give you a call to coordinate?  If so, what's a good number to reach
> you?
>
> --
>
> Kevin A. McGrail
>
> VP Fundraising, Apache Software Foundation
>
> Chair Emeritus Apache SpamAssassin Project
>
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>
>
>
>
> On Mon, Oct 29, 2018 at 4:57 PM  wrote:
>
> Just to quickly introduce EA and myself – we work together in a not for
> profit at globalsymbols.com
>
>
>
> We are very much committed to both open licence and working in the open,
> and have a special interest in seeking to ensure that AAC reaches those
> communities that have been most under served in this field
>
>
>
> One of our first projects was in the Middle East where we collaborated to
> develop Tawasol, the Arabic open symbol set, designed to reflect both
> language and culture within the Middle East and especially the gulf. To do
> that we created a system that democratised symbol design, allowing a range
> of stakeholder to determine the design and selection of symbols to
> represent concepts.
>
>
>
> Very much hope to continue discussions together about collaboration around
> the paper Ariam has distributed
>
>
>
> Best regards
>
>
>
> David
>
>
>
> *From:* Kevin A. McGrail 
> *Sent:* 29 October 2018 20:49
> *To:* Ariam Mogos ; general@incubator.apache.org
> *Cc:* Aditi Poddar ; da...@davebanesaccess.org; EA
> Draffan 
> *Subject:* Re: UNICEF Open Source project- Apache Foundation
>
>
>
> Thanks Ariam,
>
> I have a child with Autism so this is very interesting to me and I also
> helped found the largest support group in the Washington DC area.  I have
> done grants for curriculum to teach children with autism to swim with
> Autism Speaks and I can talk intelligently about AT/PECS.  We also just had
> our keynote from Cliff Schmidt at Amplio which has some crossover.  Anyway,
> enough about me, I'd like to setup a call, nothing long and talk about our
> incubator and how we work/what we do.
>
> Regards,
> KAM
>
>
> On 10/29/2018 3:53 PM, Ariam Mogos wrote:
>
> Thanks so much Kellen, Dave and Kevin!
>
> (copying Aditi from our partnerships team)
>
> (copying David Banes and EA Draffan, two of our advisors on AAC)
>
>
>
> Yes we’d be interested in collaborating with Apache and learning more
> about the incubator program.
>
>
>
> We’re very excited to share about this project. I’ve created a google doc
> with some information here:
>
>
>
>
> https://docs.google.com/document/d/1fMY5_YgqqE5VfqNCDwQ0HQe8ozkz1v7kpjQpimVsjuI/edit
>
>
>
> Please feel free to leave any comments, questions, recommendations in the
> document.
>
>
>
> Cheers,
> Ariam
>
>
>
> *From: *"Kevin A. McGrail"  
> *Date: *Sunday, October 28, 2018 at 4:51 PM
> *To: *"general@incubator.apache.org" 
>  
> *Cc: *Ariam Mogos  
> *Subject: *Re: UNICEF Open Source project- Apache Foundation
>
>
>
> In addition to the list responses, I'm happy to chat especially with my VP
> Fundraising duties. Love UNICEF and love what you do especially around
> Halloween.  Happy to jump on a call and give you some guidance!
>
>
>
> Regards,
>
> KAM
>
> --
>
> Kevin A. McGrail
>
> VP Fundraising, Apache Software Foundation
>
> Chair Emeritus Apache SpamAssassin Project
>
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>
>
>
>
> On Sun, Oct 28, 2018 at 1:39 AM Dave Fisher  wrote:
>
> Exactly as Kellen describes!
>
> If for whatever reason you require an offline discussion to start then I’m
> sure someone here may be willing to “champion” your proposal.
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Oct 27, 2018, at 9:43 PM, kellen sunderland <
>

Re: Approaching Apache's 200th top level project and more than 300 projects have gone through the incubator

[Kevin A. McGrail]

Awesome.  PR material!

On 11/2/2018 6:48 PM, Justin Mclean wrote:
> Hi,
>
> It looks like the next project to graduate after Griffin will be the ASF’s 
> 200th top level project!
>
> We’ll also recently passed the 300th project to go through the incubator. [1]
>
> Thanks,
> Justin
>
> 1. https://whimsy.apache.org/roster/
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-- 
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: How widely read is the incubator report?

[Kevin A. McGrail]

I typically read the submitted version. I am still ramping up on how I can
help the incubator but will make a point of reading them.

On Sat, Nov 3, 2018, 6:19 PM Justin Mclean  Hi,
>
> > I read the entire report every month.  Then again, I'm a director so I'm
> > supposed to.
>
> :-)
>
> >   I'd bet most PPMC members never read the report as submitted;
>
> I would assume the is the case, with a few exceptions.
>
> > Sending the whole report to all podlings monthly is overbearing.
>
> I was thinking the same, despite it being useful for a few podlngs.
>
> > One thing that feels useful would be a post-board meeting meta-summary,
> > kind of like Phil now does as Chairman.  Phil has taken part of the
> > Chairman's report and made it about common issues between projects, or
> > even just which projects wrote great reports and why.  Something like
> > that is hard to produce - extra work for our few IPMC report organizing
> > volunteers - but could be high-impact since it's short enough with
> > focused commentary that PPMCs might read and learn from it.
>
> Good idea. Lets see if we can do that.
>
> Thanks,
> Justin
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [PROPOSAL] Changing requirements for IPMC

[Kevin A. McGrail]

I agree.  This is a policy for the IPMC to determine and I think this will
increase inclusion.  We need mentors and of all types.  +1
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Tue, Nov 6, 2018 at 7:27 AM Shane Curcuru  wrote:

> Great ideas, thanks Justin!
>
> Justin Mclean wrote on 11/6/18 3:20 AM:
> > Hi,
> >
> > I looked at the board resolution for the creation of the IPMC [1] and it
> says nothing about how IPMC members should be added so from that I take it
> that the IPMC can decide how it wants to do that.
>
> The IPMC is a PMC just like any other PMC.  How the PMC decides to
> choose new PMC members to recommend for a board ACK is up to the PMC, as
> long as it's documented clearly.
>
> > Currently the IPMC can vote people in (which is not so common) or an ASF
> member can request it. I’m not sure where the ASF member requirement came
> from and wasn’t able to find the discussion about this on the incubator
> list. (If anyone knows please point me to it.)
>
> IMO the "ASF Members can request recommendation without vote" is because
> of two factors: experience and oversight.  We (hope) Members have the
> skills as you note as well.  Separately, since the IPMC is overseeing a
> wide range of communities with an eye to inviting them to become an
> official Apache project, we should allow Members to formally join the
> IPMC to help oversee this process, since
>
> ...snip...
> > Then they can ask the IPMC to join to IPMC by sending an email to
> private@ listing what they have been involved in. The IPMC would VOTE on
> them, and there’s a chance they could be rejected, but given it’s a private
> vote I don’t think any harm is done if that happens. Also people could
> nominate other people who fit into this above group.
>
> +1, having a clear criteria as you list (to ensure it's people who
> really have productively helped, and not just people status-seeking) and
> an explicit call to "this is how you can *ask* to get voted into the
> IPMC" is a great idea.  I agree, we definitely need a larger pool of
> mentors for podlings, and helping committed non-Members be able to do
> this is a great thing.
>
>
> --
>
> - Shane
>   Director & Member
>   The Apache Software Foundation
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

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

[Kevin A. McGrail]

tps://github.com/thulab/iotdb), while its subproject TsFile (a file format 
> for storing time series data) is open sourced on Github 
> (https://github.com/thulab/tsfile).
>
> == Core Developers ==
> IoTDB was initially developed by 2 dozen of students and teachers at Tsinghua 
> University. Now, more and more developers have joined coming from other 
> universities: Fudan University, Northwestern Polytechnical University and 
> Harbin Institute of Technology in China.  Other developers come from business 
> companies such as Lenovo and Microsoft. We will be working to bring more and 
> more developers into the project making contributions to IoTDB.
>
> == Relationships with Other Apache Products ==
> IoTDB requires some Apache products (Apache Thrift, commons, collections, 
> httpclient). 
>
> IoTDB-Spark-connector and IoTDB-Hadoop-connector have been developed for 
> supporting analysing time series data by using Apache Spark and MapReduce. 
>
> Overall, IoTDB is designed as an open architecture, and it can be integrated 
> with many other systems in the future.
>
> As mentioned before, in the IoTDB project, we designed a new columnar file 
> format, called TsFile, which is similar to Apache Parquet. However, the new 
> file format is optimized for time series data. 
>
>
>
> == Known Risks ==
>
> === Orphaned Products ===
> Given the current level of investment in IoTDB, the risk of the project being 
> abandoned is minimal. Time series data is more and more important and there 
> are several constituents who are highly inspired to continue development. 
> Tsinghua and NEL-BDS Lab relies on IoTDB as a platform for a large number of 
> long-term research projects. We have deployed IoTDB in some company's staging 
> environments for future applications.
>
> === Inexperience with Open Source ===
> Students and researchers in Tsinghua University have been developing and 
> using open source software for a long time. It is wonderful to be guided to 
> join a formal open-source process for students. Some of our committers
> have  experiences contributing to open source, for example:
>
>  * druid: 
> https://github.com/druid-io/druid/commit/f18cc5df97e5826c2dd8ffafba9fcb69d10a4d44
>  * druid: 
> https://github.com/druid-io/druid/commit/aa7aee53ce524b7887b218333166941654788794
>  * YCSB: https://github.com/brianfrankcooper/YCSB/pull/776
>
> Additionally, several ASF veterans and industry veterans have agreed to 
> mentor the project and are listed in this proposal. The project will rely on 
> their guidance and collective wisdom to quickly transition the entire team of 
> initial committers towards practicing the Apache Way.
>
>
> === Reliance on Salaried Developers ===
> Most of current developers are students and researchers/professors in 
> universities, and their researches focus on big data management and 
> analytics. It is unlikely that they will change their research focus away 
> from big data management.  We will work to ensure that the ability for the 
> project to continuously be stewarded and to proceed forward independent of 
> salaried developers is continued.
>
> === An Excessive Fascination with the Apache Brand ===
> Most of the initial developers come from Tsinghua University with no intent 
> to use the Apache brand for profit. We have no plans for making use of Apache 
> brand in press releases nor posting billboards advertising acceptance of 
> IoTDB into Apache Incubator.
>
>
> == Initial Source ==
> IoTDB's github address and some required dependencies: 
>
>  * The storage file format: https://github.com/thulab/tsfile
>  * Adaptor for Apache Hadoop MapReduce: 
> https://github.com/thulab/tsfile-hadoop-connector
>  * Adaptor for Apache Spark: https://github.com/thulab/tsfile-spark-connector
>  * Adaptor for Grafana: https://github.com/thulab/iotdb-grafana
>  * The database engine: https://github.com/thulab/iotdb (private project up 
> to now)
>  * The client driver: https://github.com/thulab/iotdb-jdbc
>
>
> === External Dependencies ===
> To the best of our knowledge, all dependencies of IoTDB are distributed under 
> Apache compatible licenses. Upon acceptance to the incubator, we would begin 
> a thorough analysis of all transitive dependencies to verify this fact and 
> introduce license checking into the build and release process.
>
> == Documentation ==
>  * Documentation for TsFile: https://github.com/thulab/tsfile/wiki
>  * Documentation for IoTDB and its JDBC:  http://tsfile.org/document (Chinese 
> only. An English version is in progress.)
>
> == Required Resources ==
> === Mailing Lists ===
>  * priv...@iotdb.incubator.apache.org
>  * d...@iotdb.incubator.apache.org
>  * co

Re: UNICEF Open Source project- Apache Foundation

[Kevin A. McGrail]

Hi Ariam, I got your voicemail again  Feel free to ping me back at
703.798.0171 and we can coordinate a face to face meeting.  Regards,
KAM
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Wed, Oct 31, 2018 at 12:57 PM Kevin A. McGrail 
wrote:

> Thanks Ariam, got your v/m.  Feel free to call me back at 703 798 0171.
> --
> Kevin A. McGrail
> VP Fundraising, Apache Software Foundation
> Chair Emeritus Apache SpamAssassin Project
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>
> On Tue, Oct 30, 2018 at 11:44 AM Ariam Mogos  wrote:
>
>> Sure, sounds good Kevin. You can reach me at 917.974.5997.
>>
>>
>>
>> *From: *"Kevin A. McGrail" 
>> *Date: *Monday, October 29, 2018 at 6:27 PM
>> *To: *"da...@davebanesaccess.org" 
>> *Cc: *Ariam Mogos , "general@incubator.apache.org" <
>> general@incubator.apache.org>, Aditi Poddar , "
>> e...@ecs.soton.ac.uk" 
>> *Subject: *Re: UNICEF Open Source project- Apache Foundation
>>
>>
>>
>> Thanks David for the introduction.  Ariam, I am located in Fairfax so a
>> meeting in DC is more than possible.
>>
>>
>>
>> Can I give you a call to coordinate?  If so, what's a good number to
>> reach you?
>>
>> --
>>
>> Kevin A. McGrail
>>
>> VP Fundraising, Apache Software Foundation
>>
>> Chair Emeritus Apache SpamAssassin Project
>>
>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>
>>
>>
>>
>>
>> On Mon, Oct 29, 2018 at 4:57 PM  wrote:
>>
>> Just to quickly introduce EA and myself – we work together in a not for
>> profit at globalsymbols.com
>>
>>
>>
>> We are very much committed to both open licence and working in the open,
>> and have a special interest in seeking to ensure that AAC reaches those
>> communities that have been most under served in this field
>>
>>
>>
>> One of our first projects was in the Middle East where we collaborated to
>> develop Tawasol, the Arabic open symbol set, designed to reflect both
>> language and culture within the Middle East and especially the gulf. To do
>> that we created a system that democratised symbol design, allowing a range
>> of stakeholder to determine the design and selection of symbols to
>> represent concepts.
>>
>>
>>
>> Very much hope to continue discussions together about collaboration
>> around the paper Ariam has distributed
>>
>>
>>
>> Best regards
>>
>>
>>
>> David
>>
>>
>>
>> *From:* Kevin A. McGrail 
>> *Sent:* 29 October 2018 20:49
>> *To:* Ariam Mogos ; general@incubator.apache.org
>> *Cc:* Aditi Poddar ; da...@davebanesaccess.org; EA
>> Draffan 
>> *Subject:* Re: UNICEF Open Source project- Apache Foundation
>>
>>
>>
>> Thanks Ariam,
>>
>> I have a child with Autism so this is very interesting to me and I also
>> helped found the largest support group in the Washington DC area.  I have
>> done grants for curriculum to teach children with autism to swim with
>> Autism Speaks and I can talk intelligently about AT/PECS.  We also just had
>> our keynote from Cliff Schmidt at Amplio which has some crossover.  Anyway,
>> enough about me, I'd like to setup a call, nothing long and talk about our
>> incubator and how we work/what we do.
>>
>> Regards,
>> KAM
>>
>>
>> On 10/29/2018 3:53 PM, Ariam Mogos wrote:
>>
>> Thanks so much Kellen, Dave and Kevin!
>>
>> (copying Aditi from our partnerships team)
>>
>> (copying David Banes and EA Draffan, two of our advisors on AAC)
>>
>>
>>
>> Yes we’d be interested in collaborating with Apache and learning more
>> about the incubator program.
>>
>>
>>
>> We’re very excited to share about this project. I’ve created a google doc
>> with some information here:
>>
>>
>>
>>
>> https://docs.google.com/document/d/1fMY5_YgqqE5VfqNCDwQ0HQe8ozkz1v7kpjQpimVsjuI/edit
>>
>>
>>
>> Please feel free to leave any comments, questions, recommendations in the
>> document.
>>
>>
>>
>> Cheers,
>> Ariam
>>
>>
>>
>> *From: *"Kevin A. McGrail"  
>> *Date: *Sunday, October 28, 2018 at 4:51 PM
>> *To: *"general@incubator.apache.org" 
>>  
>> *Cc: *Ariam Mogos  
>> *Subject: *Re: UNICEF

Re: [VOTE] Accept the brpc Project into the Apache Incubator.

[Kevin A. McGrail]

oogle gflags (BSD)
>>>> * Google protobuf (BSD)
>>>> * Google leveldb (BSD)
>>>>
>>>> brpc also includes third party code in the source tree.
>>>>
>>>> * https://github.com/brpc/brpc/tree/master/src/butil/third_party <
>> https://github.com/brpc/brpc/tree/master/src/butil/third_party> (BSD,
>> MIT, MPL, and Public Domain)
>>>> === Required Resources ===
>>>>
>>>>  Mailing List: 
>>>> There are currently no mailing lists.
>>>> The usual mailing lists are expected to be set up when entering
>> incubation:
>>>> * priv...@brpc.incubator.apache.org > priv...@brpc.incubator.apache.org>
>>>> * d...@brpc.incubator.apache.org <mailto:d...@brpc.incubator.apache.org>
>>>> * comm...@brpc.incubator.apache.org > comm...@brpc.incubator.apache.org>
>>>>  Git Repositories: 
>>>>
>>>> Upon entering incubation, we want to transfer the existing repo from
>> https://github.com/brpc/brpc <https://github.com/brpc/brpc> to Apache
>> infrastructure like https://github.com/apache/incubator-brpc <
>> https://github.com/apache/incubator-brpc>.
>>>>  Issue Tracking: 
>>>>
>>>> brpc currently uses GitHub to track issues. Would like to continue to
>> do so while we discuss migration possibilities with the ASF Infra committee.
>>>>  URL: 
>>>> Currently brpc has no dedicated website except Github homepage. In the
>> future the website url should be http://brpc.incubator.apache.org/ <
>> http://brpc.incubator.apache.org/> to follow apache incubator conventions.
>>>>
>>>> === Initial Committers ===
>>>>
>>>> * Ge Jun(https://github.com/jamesge <https://github.com/jamesge>
>> jge...@gmail.com <mailto:jge...@gmail.com>)
>>>> * Chen Zhangyi(https://github.com/chenzhangyi <
>> https://github.com/chenzhangyi> frozen@gmail.com > frozen@gmail.com>)
>>>> * Jiang Rujie(https://github.com/old-bear <https://github.com/old-bear>
>> jrjb...@gmail.com <mailto:jrjb...@gmail.com>)
>>>> * Zhu Jiashun(http://github.com/zyearn <http://github.com/zyearn>
>> zhujiashun2...@gmail.com <mailto:zhujiashun2...@gmail.com>)
>>>> * Wang Yao(https://github.com/ipconfigme <https://github.com/ipconfigme>
>> ipconfi...@gmail.com <mailto:ipconfi...@gmail.com>)
>>>> === Sponsors: ===
>>>>
>>>>  Champion: 
>>>> * Dave Fisher
>>>>
>>>>  Mentors: 
>>>>
>>>> * Kevin A. McGrail
>>>> * Jean-Baptiste Onofré
>>>>
>>>>  Sponsoring Entity 
>>>> We are requesting the Incubator to sponsor this project.
>>>>
>>>>
>>>> -
>>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>> <mailto:general-unsubscr...@incubator.apache.org>
>>>> For additional commands, e-mail: general-h...@incubator.apache.org
>> <mailto: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
>>
>>

-- 
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: [DISCUSS] Iceberg proposal for incubation

[Kevin A. McGrail]

On 11/12/2018 3:17 PM, Ryan Blue wrote:
> Thanks for pointing that out, Dave. That section was accidentally not
> updated after I copied the markup template. I'll fix it.
Looks good to me.  That's a lot of data to query!

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

Re: UNICEF Open Source project- Apache Foundation

[Kevin A. McGrail]

Sounds good, thanks. If you get my v/m I'll do my best to reach you back
ASAP.
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Mon, Nov 12, 2018 at 12:39 AM Ariam Mogos  wrote:

> Hi Kevin,
>
>
>
> I’m sorry, last week in DC ended up being very difficult, but will give
> you ring first thing tomorrow.
>
>
>
> Best,
> Ariam
>
>
>
> *From: *"Kevin A. McGrail" 
> *Date: *Thursday, November 8, 2018 at 10:18 AM
> *To: *Ariam Mogos 
> *Cc: *David Banes , "
> general@incubator.apache.org" , Aditi
> Poddar , "E.A. Draffan" 
> *Subject: *Re: UNICEF Open Source project- Apache Foundation
>
>
>
> Hi Ariam, I got your voicemail again  Feel free to ping me back at
> 703.798.0171 and we can coordinate a face to face meeting.  Regards,
>
> KAM
>
> --
>
> Kevin A. McGrail
>
> VP Fundraising, Apache Software Foundation
>
> Chair Emeritus Apache SpamAssassin Project
>
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>
>
>
>
> On Wed, Oct 31, 2018 at 12:57 PM Kevin A. McGrail 
> wrote:
>
> Thanks Ariam, got your v/m.  Feel free to call me back at 703 798 0171.
>
> --
>
> Kevin A. McGrail
>
> VP Fundraising, Apache Software Foundation
>
> Chair Emeritus Apache SpamAssassin Project
>
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>
>
> On Tue, Oct 30, 2018 at 11:44 AM Ariam Mogos  wrote:
>
> Sure, sounds good Kevin. You can reach me at 917.974.5997.
>
>
>
> *From: *"Kevin A. McGrail" 
> *Date: *Monday, October 29, 2018 at 6:27 PM
> *To: *"da...@davebanesaccess.org" 
> *Cc: *Ariam Mogos , "general@incubator.apache.org" <
> general@incubator.apache.org>, Aditi Poddar , "
> e...@ecs.soton.ac.uk" 
> *Subject: *Re: UNICEF Open Source project- Apache Foundation
>
>
>
> Thanks David for the introduction.  Ariam, I am located in Fairfax so a
> meeting in DC is more than possible.
>
>
>
> Can I give you a call to coordinate?  If so, what's a good number to reach
> you?
>
> --
>
> Kevin A. McGrail
>
> VP Fundraising, Apache Software Foundation
>
> Chair Emeritus Apache SpamAssassin Project
>
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>
>
>
>
> On Mon, Oct 29, 2018 at 4:57 PM  wrote:
>
> Just to quickly introduce EA and myself – we work together in a not for
> profit at globalsymbols.com
>
>
>
> We are very much committed to both open licence and working in the open,
> and have a special interest in seeking to ensure that AAC reaches those
> communities that have been most under served in this field
>
>
>
> One of our first projects was in the Middle East where we collaborated to
> develop Tawasol, the Arabic open symbol set, designed to reflect both
> language and culture within the Middle East and especially the gulf. To do
> that we created a system that democratised symbol design, allowing a range
> of stakeholder to determine the design and selection of symbols to
> represent concepts.
>
>
>
> Very much hope to continue discussions together about collaboration around
> the paper Ariam has distributed
>
>
>
> Best regards
>
>
>
> David
>
>
>
> *From:* Kevin A. McGrail 
> *Sent:* 29 October 2018 20:49
> *To:* Ariam Mogos ; general@incubator.apache.org
> *Cc:* Aditi Poddar ; da...@davebanesaccess.org; EA
> Draffan 
> *Subject:* Re: UNICEF Open Source project- Apache Foundation
>
>
>
> Thanks Ariam,
>
> I have a child with Autism so this is very interesting to me and I also
> helped found the largest support group in the Washington DC area.  I have
> done grants for curriculum to teach children with autism to swim with
> Autism Speaks and I can talk intelligently about AT/PECS.  We also just had
> our keynote from Cliff Schmidt at Amplio which has some crossover.  Anyway,
> enough about me, I'd like to setup a call, nothing long and talk about our
> incubator and how we work/what we do.
>
> Regards,
> KAM
>
>
> On 10/29/2018 3:53 PM, Ariam Mogos wrote:
>
> Thanks so much Kellen, Dave and Kevin!
>
> (copying Aditi from our partnerships team)
>
> (copying David Banes and EA Draffan, two of our advisors on AAC)
>
>
>
> Yes we’d be interested in collaborating with Apache and learning more
> about the incubator program.
>
>
>
> We’re very excited to share about this project. I’ve created a google doc
> with some information here:
>
>
>
>
> https://docs.google.com/document/d/1

Re: [VOTE] Accept the Iceberg project for incubation

[Kevin A. McGrail]

the Iceberg community and interest in the project grows.
>>>>>>>> Known Risks Orphaned Products
>>>>>>>>
>>>>>>>> Netflix is committed to the future development of Iceberg and
>>>>> understands
>>>>>>>> that graduation to a TLP, while preferable, is not the only positive
>>>>>>>> outcome of incubation.
>>>>>>>>
>>>>>>>> Should the Iceberg project be accepted by the Incubator, the
>>>>> prospective
>>>>>>>> PPMC would be willing to agree to a target incubation period of 2
>>> years
>>>>>>> or
>>>>>>>> less, knowing that every Incubator project incurs a certain cost in
>>>>> terms
>>>>>>>> of ASF infrastructure and volunteer time.
>>>>>>>> Inexperience with Open Source
>>>>>>>>
>>>>>>>> Three of the initial committers are Apache members and Incubator PMC
>>>>>>>> members. They will work with the other community members to teach
>>> them
>>>>>>> the
>>>>>>>> Apache Way.
>>>>>>>> Homogenous Developers
>>>>>>>>
>>>>>>>> The majority of the committers work at Netflix, though we are
>>> committed
>>>>>>> to
>>>>>>>> recruiting and developing additional committers from a wide spectrum
>>> of
>>>>>>>> industries and backgrounds.
>>>>>>>> Reliance on Salaried Developers
>>>>>>>>
>>>>>>>> It is expected that Iceberg development will occur on both salaried
>>>>> time
>>>>>>>> and on volunteer time, after hours. Most of the initial committers
>>> are
>>>>>>> paid
>>>>>>>> by Netflix to contribute to this project. However, they are all
>>>>>>> passionate
>>>>>>>> about the project, and we are both confident and hopeful that the
>>>>> project
>>>>>>>> will continue even if no salaried developers contribute to the
>>> project.
>>>>>>>> Relationships with Other Apache Products
>>>>>>>>
>>>>>>>> As mentioned in the Rationale section, Iceberg utilizes a number of
>>>>>>>> existing Apache projects (Avro, Hadoop, Hive, ORC, Parquet, Pig, &
>>>>>>> Spark),
>>>>>>>> and we expect that list to expand as the community grows and
>>>>> diversifies.
>>>>>>>> Any Apache project in the big data space that needs to store or
>>> process
>>>>>>>> tabular data would be potentially relevant.
>>>>>>>> An Excessive Fascination with the Apache Brand
>>>>>>>>
>>>>>>>> We are applying to the Incubator process because we think it is the
>>>>> next
>>>>>>>> logical step for the Iceberg project after open-sourcing the code.
>>> This
>>>>>>>> proposal is not for the purpose of generating publicity. Rather, we
>>>>> want
>>>>>>> to
>>>>>>>> make sure to create a very inclusive and meritocratic community,
>>>>> outside
>>>>>>>> the umbrella of a single company. Netflix has a long history of
>>>>>>>> contributing to Apache projects and the Iceberg developers and
>>>>>>> contributors
>>>>>>>> understand the implication of making it an Apache project.
>>>>>>>> Required Resources Mailing lists
>>>>>>>>
>>>>>>>> - d...@iceberg.incubator.apache.org
>>>>>>>> - comm...@iceberg.incubator.apache.org
>>>>>>>> - priv...@iceberg.incubator.apache.org
>>>>>>>>
>>>>>>>> The podling may also create a user mailing list, if needed.
>>>>>>>> Source Control and Issue Tracking
>>>>>>>>
>>>>>>>> The Iceberg podling would use Apache’s gitbox integration to sync
>>>>> between
>>>>>>>> github and Apache infrastructure. The podling would use github issues
>>>>> and
>>>>>>>> pull requests for community engagement.
>>>>>>>> Current Resources
>>>>>>>>
>>>>>>>> - Initial source: https://github.com/Netflix/iceberg
>>>>>>>> - Java documentation:
>>>>>>>>
>>> https://netflix.github.io/iceberg/current/javadoc/index.html?com/netflix/iceberg/package-summary.html
>>>>>>>> - Table specification:
>>>>>>>>
>>> https://docs.google.com/document/d/1Q-zL5lSCle6NEEdyfiYsXYzX_Q8Qf0ctMyGBKslOswA/edit
>>>>>>>> Source and Intellectual Property Submission Plan
>>>>>>>>
>>>>>>>> The Iceberg source code in Github is currently licensed under Apache
>>>>>>>> License v2.0 and the copyright is assigned to Netflix. If Iceberg
>>>>> becomes
>>>>>>>> an Incubator project at the ASF, Netflix will transfer the source
>>> code
>>>>>>> and
>>>>>>>> trademark ownership to the Apache Software Foundation via a Software
>>>>>>> Grant
>>>>>>>> Agreement.
>>>>>>>> External Dependencies
>>>>>>>>
>>>>>>>> External dependencies licensed under Apache License 2.0
>>>>>>>>
>>>>>>>> - Guava https://github.com/google/guava
>>>>>>>> - Jackson https://github.com/FasterXML/jackson-core
>>>>>>>> - Joda-Time http://www.joda.org/joda-time/
>>>>>>>>
>>>>>>>> External dependencies licensed under the MIT License
>>>>>>>>
>>>>>>>> - SLF4J https://www.slf4j.org/
>>>>>>>> - Mockito https://github.com/mockito/mockito
>>>>>>>>
>>>>>>>> ASF Projects
>>>>>>>>
>>>>>>>> - Apache Avro
>>>>>>>> - Apache Hadoop
>>>>>>>> - Apache Hive
>>>>>>>> - Apache ORC
>>>>>>>> - Apache Parquet
>>>>>>>> - Apache Pig
>>>>>>>> - Apache Spark
>>>>>>>>
>>>>>>>> Cryptography
>>>>>>>>
>>>>>>>> We do not expect Iceberg to be a controlled export item due to the
>>> use
>>>>> of
>>>>>>>> encryption.
>>>>>>>> Initial Committers and Affiliations
>>>>>>>>
>>>>>>>> - Ryan Blue b...@apache.org (Netflix)
>>>>>>>> - Parth Brahmbhatt pa...@apache.org (Netflix)
>>>>>>>> - Julien Le Dem jul...@apache.org (WeWork)
>>>>>>>> - Owen O’Malley omal...@apache.org (Hortonworks)
>>>>>>>> - Daniel Weeks dwe...@apache.org (Netflix)
>>>>>>>>
>>>>>>>> Sponsors and Nominated Mentors
>>>>>>>>
>>>>>>>> - Champion and mentor: Owen O’Malley omal...@apache.org
>>>>>>>> - Mentor: Ryan Blue b...@apache.org
>>>>>>>> - Mentor: Julien Le Dem jul...@apache.org
>>>>>>>>
>>>>>>>> Sponsoring Entity
>>>>>>>>
>>>>>>>> The Apache Incubator
>>>>>>>> --
>>>>>>>> Ryan Blue
>>>>>>>>
>>>>>>>
>>>>>>> --
>>>>>>> Ryan Blue
>>>>>>>
>>>>>>
>>>>>> --
>>>>>> Matt Sicker 
>>>>>
>>>>> -
>>>>> 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
>

-- 
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: UNICEF Open Source project- Apache Foundation

[Kevin A. McGrail]

Hi Ariam, thanks for your chat.  Please let us know if you have more
questions about the incubator or if we can help with any other avenues. 
It's a great project!

KAM

   On 11/12/2018 12:38 AM, Ariam Mogos wrote:
>
> Hi Kevin,
>
>  
>
> I’m sorry, last week in DC ended up being very difficult, but will
> give you ring first thing tomorrow.
>
>  
>
> Best,
> Ariam
>
>  
>
> *From: *"Kevin A. McGrail" 
> *Date: *Thursday, November 8, 2018 at 10:18 AM
> *To: *Ariam Mogos 
> *Cc: *David Banes ,
> "general@incubator.apache.org" , Aditi
> Poddar , "E.A. Draffan" 
> *Subject: *Re: UNICEF Open Source project- Apache Foundation
>
>  
>
> Hi Ariam, I got your voicemail again  Feel free to ping me back at
> 703.798.0171 and we can coordinate a face to face meeting.  Regards,
>
> KAM
>
> --
>
> Kevin A. McGrail
>
> VP Fundraising, Apache Software Foundation
>
> Chair Emeritus Apache SpamAssassin Project
>
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>  
>
>  
>
> On Wed, Oct 31, 2018 at 12:57 PM Kevin A. McGrail  <mailto:kmcgr...@apache.org>> wrote:
>
> Thanks Ariam, got your v/m.  Feel free to call me back at 703 798
> 0171.
>
> --
>
> Kevin A. McGrail
>
> VP Fundraising, Apache Software Foundation
>
> Chair Emeritus Apache SpamAssassin Project
>
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>  
>
> On Tue, Oct 30, 2018 at 11:44 AM Ariam Mogos  <mailto:amo...@unicef.org>> wrote:
>
> Sure, sounds good Kevin. You can reach me at 917.974.5997.
>
>  
>
> *From: *"Kevin A. McGrail"  <mailto:kmcgr...@apache.org>>
> *Date: *Monday, October 29, 2018 at 6:27 PM
> *To: *"da...@davebanesaccess.org
> <mailto:da...@davebanesaccess.org>"  <mailto:da...@davebanesaccess.org>>
> *Cc: *Ariam Mogos  <mailto:amo...@unicef.org>>, "general@incubator.apache.org
> <mailto:general@incubator.apache.org>"
>  <mailto:general@incubator.apache.org>>, Aditi Poddar
> mailto:apod...@unicef.org>>,
> "e...@ecs.soton.ac.uk <mailto:e...@ecs.soton.ac.uk>"
> mailto:e...@ecs.soton.ac.uk>>
> *Subject: *Re: UNICEF Open Source project- Apache Foundation
>
>  
>
> Thanks David for the introduction.  Ariam, I am located in
> Fairfax so a meeting in DC is more than possible.
>
>  
>
> Can I give you a call to coordinate?  If so, what's a good
> number to reach you?
>
> --
>
> Kevin A. McGrail
>
> VP Fundraising, Apache Software Foundation
>
> Chair Emeritus Apache SpamAssassin Project
>
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>  
>
>  
>
> On Mon, Oct 29, 2018 at 4:57 PM  <mailto:da...@davebanesaccess.org>> wrote:
>
> Just to quickly introduce EA and myself – we work together
> in a not for profit at globalsymbols.com
> <http://globalsymbols.com>
>
>  
>
> We are very much committed to both open licence and
> working in the open, and have a special interest in
> seeking to ensure that AAC reaches those communities that
> have been most under served in this field
>
>  
>
> One of our first projects was in the Middle East where we
> collaborated to develop Tawasol, the Arabic open symbol
> set, designed to reflect both language and culture within
>     the Middle East and especially the gulf. To do that we
> created a system that democratised symbol design, allowing
> a range of stakeholder to determine the design and
> selection of symbols to represent concepts.
>
>  
>
> Very much hope to continue discussions together about
> collaboration around the paper Ariam has distributed  
>
>  
>
> Best regards
>
>  
>
> David
>
>  
>
> *From:* Kevin A. McGrail  <mailto:kmcgr...@apache.org>>
> *Sent:* 29 October 2018 20:49
> *To:* Ariam Mogos  <mailto:amo...@unicef.org>>; general@incubator.apache.org
> <mailto:general@incubator.apache.org>
> *Cc:*

Re: [Result][Vote] vote for IoTDB incubation proposal

[Kevin A. McGrail]

Congratulations!  As champion, I think the next steps are:

1 - Xiangdong, Can you confirm the list of mentors on the proposal is
accurate?

2 - Also Xiangdong, Is there anyone else that stepped forward as a mentor
during the voting process that the project wants the IPMC to approve?

3 - Justin, I think you have to request the creation of the podling and
then I as champion work on things like the meta data file from this page,
https://incubator.apache.org/policy/incubation.html, correct?

Regards,
KAM




--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Wed, Nov 14, 2018 at 6:29 AM hxd  wrote:

> Hi,
>
> With 8 +1 binding votes,  2 +1 non-binding votes and No +/-0 or -1 votes,
> this VOTE passes.
>
> Thanks to everyone who voted!
>
> Bellow is a voting tally:
>
> Binding
> Von Gosling
>  Christofer Dutz
>  Kevin A. McGrail
>  Felix Cheung
>  Matt Sticker
>  Joe Witt
>  Justin Mclean
>  Willem Jiang
>
>
> Non-binding
>  Sheng Wu
>  Yang Bo
>
> The vote thread:
> https://lists.apache.org/thread.html/077f029ab2b52a2b19fc8d41c07438f660a8e93dd87b3895d262263c@%3Cgeneral.incubator.apache.org%3E
> <
> https://lists.apache.org/thread.html/077f029ab2b52a2b19fc8d41c07438f660a8e93dd87b3895d262263c@%3Cgeneral.incubator.apache.org%3E>
>
> The proposal: https://wiki.apache.org/incubator/IoTDBProposal <
> https://wiki.apache.org/incubator/IoTDBProposal>
>
> Thanks,
>
> Xiangdong Huang
>
>
> > 在 2018年11月7日，下午3:46，hxd  写道：
> >
> > Hi,
> >
> > Sorry for the previous mail with bad format.
> > I'd like to call a VOTE to accept IoTDB project, a database for managing
> large amounts of time series data  from IoT sensors in industrial
> applications, into the Apache Incubator.
> > The full proposal is available on the wiki:
> https://wiki.apache.org/incubator/IoTDBProposal
> > and it is also attached below for your convenience.
> >
> > Please cast your vote:
> >
> >   [ ] +1, bring IoTDB into Incubator
> >   [ ] +0, I don't care either way,
> >   [ ] -1, do not bring IoTDB into Incubator, because...
> >
> > The vote will open at least for 72 hours.
> >
> > Thanks,
> > Xiangdong Huang.
> >
> >
> > = IoTDB Proposal  =
> > v0.1.1
> >
> >
> > == Abstract ==
> > IoTDB is a data store for managing large amounts of time series data
> such as timestamped data from IoT sensors in industrial applications.
> >
> > == Proposal ==
> > IoTDB is a database for managing large amount of time series data with
> columnar storage, data encoding, pre-computation, and index techniques. It
> has SQL-like interface to write millions of data points per second per node
> and is optimized to get query results in few seconds over trillions of data
> points. It can also be easily integrated with Apache Hadoop MapReduce and
> Apache Spark for analytics.
> >
> > == Background ==
> >
> > A new class of data management system requirements is becoming
> increasingly important with the rise of the Internet of Things. There are
> some database systems and technologies aimed at time series data
> management.  For example, Gorilla and InfluxDB which are mainly built for
> data centers and monitoring application metrics. Other systems, for
> example, OpenTSDB and KairosDB, are built on Apache HBase and Apache
> Cassandra, respectively.
> >
> > However, many applications for time series data management have more
> requirements especially in industrial applications as follows:
> >
> >  * Supporting time series data which has high data frequency. For
> example, a turbine engine may generate 1000 points per second (i.e.,
> 1000Hz), while each CPU only reports 1 data points per 5 seconds in a data
> center monitoring application.
> >
> >  * Supporting scanning data multi-resolutionally. For example,
> aggregation operation is important for time series data.
> >
> >  * Supporting special queries for time series, such as pattern matching,
> time series segmentation, time-frequency transformation and frequency query.
> >
> >  * Supporting a large number of monitoring targets (i.e. time series).
> An excavator may report more than 1000 time series, for example, revolving
> speed of the motor-engine, the speed of the excavator, the accelerated
> speed, the temperature of the water tank and so on, while a CPU or an
> application monitor has much fewer time series.
> >
> >  * Optimization for out-of-order data points. In the industrial sector,
> it is common that equipment sends data 

Re: [Result][Vote] vote for IoTDB incubation proposal

[Kevin A. McGrail]

Well, first, let's ask some questions:

- When you say "open source" repo, do you mean private repo vs public
repo?

- I believe Craig as Secretary will say an SGA never hurts but isn't
everything already licensed ASLv2?  It's been a few weeks and a few
proposals reviewed so it could be my memory.

Regards,
KAM

--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Thu, Nov 15, 2018 at 7:27 AM hxd  wrote:

> Currently, there are 6 repositories (IoTDB, IoTDB-JDBC, TsFile,
> Spark-Connector, Hive-Connector, and Grafana-Connector) totally and we will
> merge them all in one repositories.
>
> Only the first one is private.
>
> Actually we are lack of experiences about how to open source.
>
> Should we open all the source now or after all the Apache legal documents
> are done?
>
> Best,
>
> Xiangdong Huang
>
> > 在 2018年11月15日，下午5:06，Willem Jiang  写道：
> >
> > Here is a question for the source code repository
> >
> > The main source git repo[1] is still a private repo.  I think we need
> > to open source the repo before sending the SGA?
> >
> >
> > [1]https://github.com/thulab/iotdb
> >
> > Willem Jiang
> >
> > Twitter: willemjiang
> > Weibo: 姜宁willem
> > On Thu, Nov 15, 2018 at 4:08 PM hxd  wrote:
> >>
> >> Hi,
> >>
> >> In the proposal discussion process, we got 3 mentors,  Justin Mclean,
> Christofer Dutz, and Willem Ning Jiang.
> >>
> >> In the vote process, we got a new mentor, Joe Witt.
> >>
> >> Totally, there are one Champion and four mentors, they are:
> >>
> >> Kevin A. McGrail (the Champion),
> >> Justin Mclean,
> >> Christofer Dutz,
> >> Willem Ning Jiang, and
> >> Joe Witt
> >>
> >> I have checked their name on
> http://people.apache.org/committer-index.html, and they are accurate now.
> >> The name list on the proposal list (
> https://wiki.apache.org/incubator/IoTDBProposal) is also correct.
> >>
> >> Regards,
> >> Xiangdong Huang
> >>
> >>
> >>
> >> 在 2018年11月15日，上午12:51，Kevin A. McGrail  写道：
> >>
> >> Congratulations!  As champion, I think the next steps are:
> >>
> >> 1 - Xiangdong, Can you confirm the list of mentors on the proposal is
> accurate?
> >>
> >> 2 - Also Xiangdong, Is there anyone else that stepped forward as a
> mentor during the voting process that the project wants the IPMC to approve?
> >>
> >> 3 - Justin, I think you have to request the creation of the podling and
> then I as champion work on things like the meta data file from this page,
> >> https://incubator.apache.org/policy/incubation.html, correct?
> >>
> >> Regards,
> >> KAM
> >>
> >>
> >>
> >>
> >> --
> >> Kevin A. McGrail
> >> VP Fundraising, Apache Software Foundation
> >> Chair Emeritus Apache SpamAssassin Project
> >> https://www.linkedin.com/in/kmcgrail - 703.798.0171
> >>
> >>
> >> On Wed, Nov 14, 2018 at 6:29 AM hxd  wrote:
> >>>
> >>> Hi,
> >>>
> >>> With 8 +1 binding votes,  2 +1 non-binding votes and No +/-0 or -1
> votes, this VOTE passes.
> >>>
> >>> Thanks to everyone who voted!
> >>>
> >>> Bellow is a voting tally:
> >>>
> >>> Binding
> >>> Von Gosling
> >>> Christofer Dutz
> >>> Kevin A. McGrail
> >>> Felix Cheung
> >>> Matt Sticker
> >>> Joe Witt
> >>> Justin Mclean
> >>> Willem Jiang
> >>>
> >>>
> >>> Non-binding
> >>> Sheng Wu
> >>> Yang Bo
> >>>
> >>> The vote thread:
> https://lists.apache.org/thread.html/077f029ab2b52a2b19fc8d41c07438f660a8e93dd87b3895d262263c@%3Cgeneral.incubator.apache.org%3E
> <
> https://lists.apache.org/thread.html/077f029ab2b52a2b19fc8d41c07438f660a8e93dd87b3895d262263c@%3Cgeneral.incubator.apache.org%3E
> >
> >>> The proposal: https://wiki.apache.org/incubator/IoTDBProposal <
> https://wiki.apache.org/incubator/IoTDBProposal>
> >>>
> >>> Thanks,
> >>>
> >>> Xiangdong Huang
> >>>
> >>>
> >>>> 在 2018年11月7日，下午3:46，hxd  写道：
> >>>>
> >>>> Hi,
> >>>>
> >>>> Sorry for the previous mail with bad fo

Re: [Result][Vote] vote for IoTDB incubation proposal

[Kevin A. McGrail]

I will defer the intake of code to the secretary.

On Thu, Nov 15, 2018, 12:20 黄向东  > - When you say "open source" repo, do you mean private repo vs public
> > repo?
>
> Yes.
>
> >
> > - I believe Craig as Secretary will say an SGA never hurts but isn't
> > everything already licensed ASLv2?  It's been a few weeks and a few
> > proposals reviewed so it could be my memory.
>
> Currently, the licenses of the dependency libs of IoTDB includes:
> Apache2.0, BSD (antlr3), EPL1.0 (logback) and EPL2.0 (junit).
> We are working on checking all the licenses once again for avoiding
> mistakes.
>
> Regards,
> Xiangdong Huang
>
>
> > 在 2018年11月15日，下午10:43，Kevin A. McGrail  写道：
> >
> > Well, first, let's ask some questions:
> >
> > - When you say "open source" repo, do you mean private repo vs public
> > repo?
> >
> > - I believe Craig as Secretary will say an SGA never hurts but isn't
> > everything already licensed ASLv2?  It's been a few weeks and a few
> > proposals reviewed so it could be my memory.
> >
> > Regards,
> > KAM
> >
> > --
> > Kevin A. McGrail
> > VP Fundraising, Apache Software Foundation
> > Chair Emeritus Apache SpamAssassin Project
> > https://www.linkedin.com/in/kmcgrail - 703.798.0171
> >
> >
> > On Thu, Nov 15, 2018 at 7:27 AM hxd  wrote:
> >
> >> Currently, there are 6 repositories (IoTDB, IoTDB-JDBC, TsFile,
> >> Spark-Connector, Hive-Connector, and Grafana-Connector) totally and we
> will
> >> merge them all in one repositories.
> >>
> >> Only the first one is private.
> >>
> >> Actually we are lack of experiences about how to open source.
> >>
> >> Should we open all the source now or after all the Apache legal
> documents
> >> are done?
> >>
> >> Best,
> >>
> >> Xiangdong Huang
> >>
> >>> 在 2018年11月15日，下午5:06，Willem Jiang  写道：
> >>>
> >>> Here is a question for the source code repository
> >>>
> >>> The main source git repo[1] is still a private repo.  I think we need
> >>> to open source the repo before sending the SGA?
> >>>
> >>>
> >>> [1]https://github.com/thulab/iotdb
> >>>
> >>> Willem Jiang
> >>>
> >>> Twitter: willemjiang
> >>> Weibo: 姜宁willem
> >>> On Thu, Nov 15, 2018 at 4:08 PM hxd  wrote:
> >>>>
> >>>> Hi,
> >>>>
> >>>> In the proposal discussion process, we got 3 mentors,  Justin Mclean,
> >> Christofer Dutz, and Willem Ning Jiang.
> >>>>
> >>>> In the vote process, we got a new mentor, Joe Witt.
> >>>>
> >>>> Totally, there are one Champion and four mentors, they are:
> >>>>
> >>>> Kevin A. McGrail (the Champion),
> >>>> Justin Mclean,
> >>>> Christofer Dutz,
> >>>> Willem Ning Jiang, and
> >>>> Joe Witt
> >>>>
> >>>> I have checked their name on
> >> http://people.apache.org/committer-index.html, and they are accurate
> now.
> >>>> The name list on the proposal list (
> >> https://wiki.apache.org/incubator/IoTDBProposal) is also correct.
> >>>>
> >>>> Regards,
> >>>> Xiangdong Huang
> >>>>
> >>>>
> >>>>
> >>>> 在 2018年11月15日，上午12:51，Kevin A. McGrail  写道：
> >>>>
> >>>> Congratulations!  As champion, I think the next steps are:
> >>>>
> >>>> 1 - Xiangdong, Can you confirm the list of mentors on the proposal is
> >> accurate?
> >>>>
> >>>> 2 - Also Xiangdong, Is there anyone else that stepped forward as a
> >> mentor during the voting process that the project wants the IPMC to
> approve?
> >>>>
> >>>> 3 - Justin, I think you have to request the creation of the podling
> and
> >> then I as champion work on things like the meta data file from this
> page,
> >>>> https://incubator.apache.org/policy/incubation.html, correct?
> >>>>
> >>>> Regards,
> >>>> KAM
> >>>>
> >>>>
> >>>>
> >>>>
> >>>> --
> >>>> Kevin A. McGrail
> >>>> VP Fundraising, Apache Software Foundation
> >>>> Chair Emeritus Apache SpamAssas

Re: UNICEF Open Source project- Apache Foundation

[Kevin A. McGrail]

Sure Ariam.

The Incubator is the process by which projects come into the Apache
Software Foundation and learn how to be a successful open source project.

The process is pretty well documented at
https://incubator.apache.org/policy/incubation.html and would start with
the preparation of a proposal which I'd be happy to review for you.

Regards,
KAM
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Tue, Nov 27, 2018 at 2:15 PM Ariam Mogos  wrote:

> Thanks Kevin, great connecting with you too. Could you send me more about
> the incubator and the proposal process?
>
>
>
> Thanks!
> Ariam
>
>
>
>
>
> *From: *"Kevin A. McGrail" 
> *Date: *Tuesday, November 13, 2018 at 4:19 PM
> *To: *Ariam Mogos 
> *Cc: *David Banes , "
> general@incubator.apache.org" , Aditi
> Poddar , "E.A. Draffan" 
> *Subject: *Re: UNICEF Open Source project- Apache Foundation
>
>
>
> Hi Ariam, thanks for your chat.  Please let us know if you have more
> questions about the incubator or if we can help with any other avenues.
> It's a great project!
>
> KAM
>
>On 11/12/2018 12:38 AM, Ariam Mogos wrote:
>
> Hi Kevin,
>
>
>
> I’m sorry, last week in DC ended up being very difficult, but will give
> you ring first thing tomorrow.
>
>
>
> Best,
> Ariam
>
>
>
> *From: *"Kevin A. McGrail"  
> *Date: *Thursday, November 8, 2018 at 10:18 AM
> *To: *Ariam Mogos  
> *Cc: *David Banes  ,
> "general@incubator.apache.org" 
>  , Aditi
> Poddar  , "E.A. Draffan"
>  
> *Subject: *Re: UNICEF Open Source project- Apache Foundation
>
>
>
> Hi Ariam, I got your voicemail again  Feel free to ping me back at
> 703.798.0171 and we can coordinate a face to face meeting.  Regards,
>
> KAM
>
> --
>
> Kevin A. McGrail
>
> VP Fundraising, Apache Software Foundation
>
> Chair Emeritus Apache SpamAssassin Project
>
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>
>
>
>
> On Wed, Oct 31, 2018 at 12:57 PM Kevin A. McGrail 
> wrote:
>
> Thanks Ariam, got your v/m.  Feel free to call me back at 703 798 0171.
>
> --
>
> Kevin A. McGrail
>
> VP Fundraising, Apache Software Foundation
>
> Chair Emeritus Apache SpamAssassin Project
>
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>
>
> On Tue, Oct 30, 2018 at 11:44 AM Ariam Mogos  wrote:
>
> Sure, sounds good Kevin. You can reach me at 917.974.5997.
>
>
>
> *From: *"Kevin A. McGrail" 
> *Date: *Monday, October 29, 2018 at 6:27 PM
> *To: *"da...@davebanesaccess.org" 
> *Cc: *Ariam Mogos , "general@incubator.apache.org" <
> general@incubator.apache.org>, Aditi Poddar , "
> e...@ecs.soton.ac.uk" 
> *Subject: *Re: UNICEF Open Source project- Apache Foundation
>
>
>
> Thanks David for the introduction.  Ariam, I am located in Fairfax so a
> meeting in DC is more than possible.
>
>
>
> Can I give you a call to coordinate?  If so, what's a good number to reach
> you?
>
> --
>
> Kevin A. McGrail
>
> VP Fundraising, Apache Software Foundation
>
> Chair Emeritus Apache SpamAssassin Project
>
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>
>
>
>
> On Mon, Oct 29, 2018 at 4:57 PM  wrote:
>
> Just to quickly introduce EA and myself – we work together in a not for
> profit at globalsymbols.com
>
>
>
> We are very much committed to both open licence and working in the open,
> and have a special interest in seeking to ensure that AAC reaches those
> communities that have been most under served in this field
>
>
>
> One of our first projects was in the Middle East where we collaborated to
> develop Tawasol, the Arabic open symbol set, designed to reflect both
> language and culture within the Middle East and especially the gulf. To do
> that we created a system that democratised symbol design, allowing a range
> of stakeholder to determine the design and selection of symbols to
> represent concepts.
>
>
>
> Very much hope to continue discussions together about collaboration around
> the paper Ariam has distributed
>
>
>
> Best regards
>
>
>
> David
>
>
>
> *From:* Kevin A. McGrail 
> *Sent:* 29 October 2018 20:49
> *To:* Ariam Mogos ; general@incubator.apache.org
> *Cc:* Aditi Poddar ; da...@davebanesaccess.org; EA
> Draffan 
> *Subject:* Re: UNICEF Open Source project- Apache Foundation
>
>
>
> Thanks Ariam,
>
> I have a child with Autism so this is very in

Re: brpc project setup

[Kevin A. McGrail]

On 11/29/2018 4:26 PM, Justin Mclean wrote:
> I notice this podling was voted in 2 weeks ago but the email lists have not 
> been created yet. 
>
> Does the podling need help with on-boarding / bootstrapping? Are your mentors 
> helping out (presumably off ist)?
>
> Thanks,
> Justin
>
> P.S You have a board report due in a week, and while it may not contain much 
> other then “still setting up stuff” it’s still needed.


I'll try and step up more and help on this.  Thanks for the kick.

-- 
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: [VOTE] - Release Apache OpenWhisk (Incubating) Composer module 0.9.0 (rc1)

[Kevin A. McGrail]

+1 Binding.
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Mon, Dec 3, 2018 at 9:59 AM Dave Grove  wrote:

> After 7 days, this vote still needs two additional +1 binding votes to
> pass.
> (Bertrand Delacretaz's binding +1 from the Podling PPMC vote [1] carries
> to this VOTE).
>
> The OpenWhisk podling only has two mentors (Bertrand Delacretaz and Jim
> Jagielski), so we need at least one vote beyond our mentors to be able to
> close this voting thread.
>
> thank you,
>
> --dave
>
> [1]
> https://lists.apache.org/thread.html/8b182e4b0ad7e402f4be61500285abedf44067215a5d351bdaeb005b@%3Cdev.openwhisk.apache.org%3E
>
> On 2018/11/26 18:59:23, "David P Grove"  wrote:
> >
> >
> > Dear IPMC members,
> >
> > This is a call for the vote to release Apache OpenWhisk (Incubating):
> > Composer module, 0.9.0.
> >
> > The Apache OpenWhisk community has voted on and approved a proposal to
> > release Apache OpenWhisk (Incubating): Composer module 0.9.0.
> >
> > We now request the Incubator PMC members to review and vote on this
> > incubator release.
> >
> > Apache OpenWhisk Composer is a programming model for composing cloud
> > functions built on Apache OpenWhisk.
> >
> > OpenWhisk Composer vote thread:
> >
> https://lists.apache.org/thread.html/5bc79c5f16661d46cd77557b2b1a4ec7d41d184c7dc44026fd92a3de@%3Cdev.openwhisk.apache.org%3E
> >
> > OpenWhisk Composer vote result email:
> >
> https://lists.apache.org/thread.html/0962026eef420586a482b7fbe29c0db1fb28bad38a7ad5cbe943aba1@%3Cdev.openwhisk.apache.org%3E
> >
> > This release comprises of source code distribution only. There is only
> one
> > module within this release number 0.9.0. The artifact were built from the
> > following Git commit IDs:
> > * openwhisk-composer: 7ae7f08,
> >
> > The source code artifact of openwhisk composer can be found at:
> >
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-composer-0.9.0-incubating-sources.tar.gz
> >
> > The SHA-512 checksum for the artifact of openwhisk composer is
> > openwhisk-composer-0.9.0-incubating-sources.tar.gz:
> > 7D5ECB65 DF653840 C8A33C7B DDF346AD 2AA36507 DD1D6DE6 8CB99238 BDC93EF6
> > 425B5BAF
> >  1371C4BE 6F1E0DEF 01D60D18 03AADC33 B0B7BD95 40724450 5FF6D131
> > which can can be found via:
> >
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-composer-0.9.0-incubating-sources.tar.gz.sha512
> >
> > The signature of the artifact of openwhisk composer can be found via:
> >
> https://dist.apache.org/repos/dist/dev/incubator/openwhisk/apache-openwhisk-0.9.0-incubating-rc1/openwhisk-composer-0.9.0-incubating-sources.tar.gz.asc
> >
> > This release was signed with key 147F886E.
> > KEYS file is available here:
> > https://dist.apache.org/repos/dist/dev/incubator/openwhisk/KEYS
> >
> > This is the first release of Apache OpenWhisk, Composer module. so there
> is
> > no CHANGELOG file.
> >
> > How to verify the artifacts can be found at:
> > https://cwiki.apache.org/confluence/display/OPENWHISK/How+to+verify+the
> > +release+checklist+and+vote+on+OpenWhisk+modules+under+Apache
> >
> > We are currently using the tool called openwhisk-release
> > (https://github.com/apache/incubator-openwhisk-release) to release all
> the
> > modules of OpenWhisk. The instruction for release managers can be found
> at:
> >
> https://github.com/apache/incubator-openwhisk-release/blob/master/docs/release_instructions.md
> .
> >  This tool
> > supports  both manual and automated modes to package the source code,
> sign
> > the  artifacts and upload the artifacts into Apache SVN repositories.
> >
> > The vote will be open for at least 72 hours or until necessary number of
> > votes are reached.
> >
> > Please vote accordingly:
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Regards,
> >
> > --dave
> >
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: UNICEF Open Source project- Apache Foundation

[Kevin A. McGrail]

Thanks Ariam!
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Mon, Dec 3, 2018 at 11:36 AM Ariam Mogos  wrote:

> Thanks Kevin this is great. I’m going to go through the documentation and
> set-up a follow-up call with you.
>
>
>
> *From: *"Kevin A. McGrail" 
> *Date: *Tuesday, November 27, 2018 at 5:29 PM
> *To: *Ariam Mogos 
> *Cc: *David Banes , "
> general@incubator.apache.org" , Aditi
> Poddar , "E.A. Draffan" 
> *Subject: *Re: UNICEF Open Source project- Apache Foundation
>
>
>
> Sure Ariam.
>
>
>
> The Incubator is the process by which projects come into the Apache
> Software Foundation and learn how to be a successful open source project.
>
>
>
> The process is pretty well documented at
> https://incubator.apache.org/policy/incubation.html and would start with
> the preparation of a proposal which I'd be happy to review for you.
>
>
> Regards,
>
> KAM
>
> --
>
> Kevin A. McGrail
>
> VP Fundraising, Apache Software Foundation
>
> Chair Emeritus Apache SpamAssassin Project
>
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>
>
>
>
> On Tue, Nov 27, 2018 at 2:15 PM Ariam Mogos  wrote:
>
> Thanks Kevin, great connecting with you too. Could you send me more about
> the incubator and the proposal process?
>
>
>
> Thanks!
> Ariam
>
>
>
>
>
> *From: *"Kevin A. McGrail" 
> *Date: *Tuesday, November 13, 2018 at 4:19 PM
> *To: *Ariam Mogos 
> *Cc: *David Banes , "
> general@incubator.apache.org" , Aditi
> Poddar , "E.A. Draffan" 
> *Subject: *Re: UNICEF Open Source project- Apache Foundation
>
>
>
> Hi Ariam, thanks for your chat.  Please let us know if you have more
> questions about the incubator or if we can help with any other avenues.
> It's a great project!
>
> KAM
>
>On 11/12/2018 12:38 AM, Ariam Mogos wrote:
>
> Hi Kevin,
>
>
>
> I’m sorry, last week in DC ended up being very difficult, but will give
> you ring first thing tomorrow.
>
>
>
> Best,
> Ariam
>
>
>
> *From: *"Kevin A. McGrail"  
> *Date: *Thursday, November 8, 2018 at 10:18 AM
> *To: *Ariam Mogos  
> *Cc: *David Banes  ,
> "general@incubator.apache.org" 
>  , Aditi
> Poddar  , "E.A. Draffan"
>  
> *Subject: *Re: UNICEF Open Source project- Apache Foundation
>
>
>
> Hi Ariam, I got your voicemail again  Feel free to ping me back at
> 703.798.0171 and we can coordinate a face to face meeting.  Regards,
>
> KAM
>
> --
>
> Kevin A. McGrail
>
> VP Fundraising, Apache Software Foundation
>
> Chair Emeritus Apache SpamAssassin Project
>
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>
>
>
>
> On Wed, Oct 31, 2018 at 12:57 PM Kevin A. McGrail 
> wrote:
>
> Thanks Ariam, got your v/m.  Feel free to call me back at 703 798 0171.
>
> --
>
> Kevin A. McGrail
>
> VP Fundraising, Apache Software Foundation
>
> Chair Emeritus Apache SpamAssassin Project
>
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>
>
> On Tue, Oct 30, 2018 at 11:44 AM Ariam Mogos  wrote:
>
> Sure, sounds good Kevin. You can reach me at 917.974.5997.
>
>
>
> *From: *"Kevin A. McGrail" 
> *Date: *Monday, October 29, 2018 at 6:27 PM
> *To: *"da...@davebanesaccess.org" 
> *Cc: *Ariam Mogos , "general@incubator.apache.org" <
> general@incubator.apache.org>, Aditi Poddar , "
> e...@ecs.soton.ac.uk" 
> *Subject: *Re: UNICEF Open Source project- Apache Foundation
>
>
>
> Thanks David for the introduction.  Ariam, I am located in Fairfax so a
> meeting in DC is more than possible.
>
>
>
> Can I give you a call to coordinate?  If so, what's a good number to reach
> you?
>
> --
>
> Kevin A. McGrail
>
> VP Fundraising, Apache Software Foundation
>
> Chair Emeritus Apache SpamAssassin Project
>
> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>
>
>
>
>
> On Mon, Oct 29, 2018 at 4:57 PM  wrote:
>
> Just to quickly introduce EA and myself – we work together in a not for
> profit at globalsymbols.com
>
>
>
> We are very much committed to both open licence and working in the open,
> and have a special interest in seeking to ensure that AAC reaches those
> communities that have been most under served in this field
>
>
>
> One of our first projects was in the Middle East where we collaborated to
> develop Tawasol, the Arabic open symbo

Re: December report - Mentor sign off due end of today

[Kevin A. McGrail]

Thanks for the heads-up.  A sing-off sounds like we are an acappella group!

I'll ask BRPC if they have a report.  This is one of their first so I'm
sort of expecting it to be short.
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Mon, Dec 10, 2018 at 3:47 PM Justin Mclean 
wrote:

> Hi,
>
> Just a reminder mentor sign-off is due today and some projects still have
> no sing-offs and will be asked to report next month if they don’t get any.
>
> These projects are:
> BRPC
> Myriad
>
> Projects that could do with more sign-offs (as they only have one
> sign-off) include:
> DLab
> Daffodil
> Hivemall
> Ponytail
> Samoa
> Singa
> Superset
> Taverna
> Warble
>
> The board likes to see more than one sign off and it’s a good indicator if
> mentors are paying attention.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: December report - Mentor sign off due end of today

[Kevin A. McGrail]

Additionally, if I was pinged, I did not receive the email.   I'm signing
off on the BRPC report as soon as I can with the wiki.  Just got karma a
few minutes ago.
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Mon, Dec 10, 2018 at 10:38 PM Gosling Von  wrote:

> Hi,
>
> I have noticed in brpc incubator comments:
>
>
> IPMC/Shepherd notes:
> Dave Fisher: I wrote up this report and made the mailing list request.
> Justin Mclean: LDAP and DNS also feel between the cracks. Mentors were
>  pinged but no response. I think it would be good for this project to
>  have an extra mentor.
>
> I have signed my name in mentor roster and contacted the brpc teams
> offline to learn more about the start status in podling.
>
>
> Best Regards,
> Von Gosling
>
> > 在 2018年12月11日，上午4:47，Justin Mclean  写道：
> >
> > Hi,
> >
> > Just a reminder mentor sign-off is due today and some projects still
> have no sing-offs and will be asked to report next month if they don’t get
> any.
> >
> > These projects are:
> > BRPC
> > Myriad
> >
> > Projects that could do with more sign-offs (as they only have one
> sign-off) include:
> > DLab
> > Daffodil
> > Hivemall
> > Ponytail
> > Samoa
> > Singa
> > Superset
> > Taverna
> > Warble
> >
> > The board likes to see more than one sign off and it’s a good indicator
> if mentors are paying attention.
> >
> > Thanks,
> > Justin
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Trouble Reaching mentors?

[Kevin A. McGrail]

Zhongyi, I just signed off on the BRPC report. Nicely done.

However, I saw a note you were having trouble getting responses from
mentors.  My apologies!  I don't think I'm getting the emails.  Can you
resend any emails you have not received a response from me?  I'll
acknowledge them so we can confirm I have them.

Also, we want to start getting people using the brpc-dev@ and brpc-private@
lists for the project.  Can you ask people to subscribe please?

Regards,
KAM

Re: Establishing an ASF project for training

[Kevin A. McGrail]

Hi Lars,

Just a note that this might tie in nicely to the proposal I sent to a
number of online companies: Coursera, Pluralsight, Udemy, & Udacity re:
setting up a PMC for Training.  I got only one response which so far
hasn't materialized with much.  However, I think the idea has a lot of
merit and thought I would share what I wrote back in October.

Regards,
KAM

Invitation to a Discussion Panel re: the Apache Way and a PMC Proposal
for Online Training

Kevin A. McGrail 
Tue, Oct 16, 12:46 PM

Hello All,

Over the past few years, the ASF has been approached a number of times
regarding online training/certification and working with several players
in the industry.  To date, we haven't had much luck finding a way that
works but just recently, we had another firm reach out to us.

With this additional firm and combining it with recent ASF discussions
about "central service" projects at the ASF to embrace things that are
non-code related like graphics and documentation, we might have a way
forward.

In broad strokes, the idea of creating training material presents itself
as an interesting idea for a project in the Apache Incubator.  The
Incubator is where we grow and cultivate interesting ideas towards being
top level projects.

The plan at this stage is to get interested parties to discuss the
idea.  What is needed is for a team of people to create a proposal for a
project management committee to produce this training material just like
how we produce OSS software in a vendor neutral, collaborative manner
using the Apache Way.

It's important to note that the ASF wouldn't drive this ship.  We'd help
steer it with tugboats but we have a lot of experience with successful
projects involving lots of different vendors that create value through
open source.

If the companies you represent might be able to help in doing that, I'd
like to see if it's feasible and guide you.  The first step is to setup
a meeting with interested parties to discuss things further.  Please let
me know if you would be interested and if you recommend anyone else is
invited for the meeting.

Thanks for your time.

Regards,

KAM
On 12/17/2018 8:22 AM, Lars Francke wrote:
> Hi,
>
> I'd like to start a discussion around establishing a project (or Central
> Service) at the ASF to host and develop training and related materials for
> ASF (and possibly others, where it makes sense) projects.
>
> I'm a committer and contributor to a few projects and make money doing
> consulting work. Naturally people do contact us for training, and we have
> developed our own slideware etc. but we find it incredibly hard work to
> keep those up-to-date.
>
> We also work with lots of other companies and they all face the same
> challenges. At the same time, we do not believe that a slide-deck is worth
> that much on its own (others disagree, as we used to). We believe the
> instructor is the real selling-point and especially when that person is
> deeply embedded in the projects itself as a committer or PMC.
>
> So, we as a company[0] would like to donate our slide decks and other
> resources we have and establish an ASF wide training project in the hopes
> that we as a community can collaborate on those resources. We are currently
> talking to partners to assess whether they are interested in joining us in
> open sourcing their material.
>
> I'm not sure if this is a "Central Services" kind of thing or if it should
> be an Incubator project to begin with. I'm posting this here because I
> think there are good arguments for it being a project (e.g. it appears as a
> “project” in all lists that others can contribute to, it follows a familiar
> structure etc.). It might be a bit different than other projects though
> (e.g. maybe there are no real releases?).
>
> This is also not limited to just slides obviously but also accompanying
> code and potentially other media forms.
>
> One concern I have is that the material should be as objective as possible,
> but our clients especially value our (often subjective) input on the
> matureness of tools (third-party as well as ASF), processes and
> communities. So, we usually include that in our slides. I guess anyone
> using this material would need to customize it.
>
> This is how I see it but I'm happy to change based on feedback.
> In scope:
> * Develop shared material that can be used for trainings
> * Develop “labs” or “hands-on” exercises
> * Develop or document an infrastructure that can be used for those labs
> * Potentially develop tools to manage the material (e.g. ideally a slide
> repository that contains “modules” that can be easily reused and combined)
>
> Out of scope (for now at least)
> * Something like what the CNCF has with their “Kubernetes Training
> Program”[1] with cert

Re: Establishing an ASF project for training

[Kevin A. McGrail]

On 12/17/2018 2:14 PM, Lars Francke wrote:
> thanks for the heads up and for the support. I'd love for those
> companies to contribute but I think there's no need to wait for them, no?
>
> I understand that a meeting can be useful but if you have one it'd be
> great if it could be an online meetup/call so I (from Germany) can
> also participate. That said: I believe we can probably hash out most
> details on the list as well?

Hi Lars, I had hoped they were interested more than just for financial
and proprietary benefit.  However, the fact that only 1 responded tells
me they didn't like the idea.

If you wanted to lead a PMC for this project, I'm happy to re-engage
with them and try and get them involved in your efforts.


Regards,
KAM


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

Re: Establishing an ASF project for training

[Kevin A. McGrail]

On 12/18/2018 11:43 AM, Lars Francke wrote:
> You, Rich and KAM talk about a TLP/Central Service so let's start
> discussing that. I'm fairly well informed about the Incubator but I have no
> ideas about the direct-to-TLP/Central Services path. Any pointers/mentors
> would be great. If no one objects I'd like to start the process of DISCUSS
> and potentially VOTE in the right place then. Would that be members@ or
> board@ or something else entirely? All documentation I can find is about
> new Incubator projects.

Lars, I would recommend you create a proposal to become a podling in the
incubator with you as the champion.  See
https://wiki.apache.org/incubator/ and perhaps an example proposal like
https://wiki.apache.org/incubator/IoTDBProposal

Regards,
KAM

-- 
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: Establishing an ASF project for training

[Kevin A. McGrail]

I'm also +1 on a proposal on incubator even if it's voted on direct to
TLP.  It will help you significantly in understanding the goals of the
PMC and get others involved.  And if I can get the companies like
Udacity, Udemy, Coursera, Pluralsight, etc. to come to the table and
help, they will likely need the incubation process to understand the
Apache Way.

-- 
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: Feedback requested: New committer invitation template

[Kevin A. McGrail]

Craig, having seen the hundreds of templates you process, I am +1 to any
process improvements you suggest.  -KAM

On Sat, Dec 29, 2018, 18:29 Craig Russell  Hi,
>
> In order to simplify the process of granting new committers write access
> to a project's repository, I'd like to propose a change in the invitation
> letter sent to candidates after the PMC has voted to accept them as
> committers.
>
> The original is at
> https://community.apache.org/newcommitter.html#committer-invite-template
>
> It does not distinguish among these three cases: already have an Apache
> id, already filed an ICLA, and have not filed an ICLA. There are many cases
> where unnecessary work is done because of improper guidance.
>
> 
> To: joeblo...@foo.net
> Cc: private@[PROJECT].apache.org
> Subject: Invitation to become [PROJECT] committer: Joe Bloggs
>
> Hello [invitee name],
>
> The [Project] Project Management Committee] (PMC)
> hereby offers you committer privileges to the project
> [as well as membership in the PMC]. These privileges are
> offered on the understanding that you'll use them
> reasonably and with common sense. We like to work on trust
> rather than unnecessary constraints.
>
> Being a committer enables you to more easily make
> changes without needing to go through the patch
> submission process. [Being a PMC member enables you
> to guide the direction of the project.]
>
> Being a committer does not require you to
> participate any more than you already do. It does
> tend to make one even more committed.  You will
> probably find that you spend more time here.
>
> Of course, you can decline and instead remain as a
> contributor, participating as you do now.
>
> A. This personal invitation is a chance for you to
> accept or decline in private.  Either way, please
> let us know in reply to the [priv...@project.apache.org]
> address only.
>
> [check http://people.apache.org/committer-index.html]
> [B. If you accept, since you already have an Apache id,
> the PMC will grant you write access to the repository.
> ]
>
> [check http://people.apache.org/unlistedclas.html]
> [B. If you accept, since you already have an iCLA on file,
> the PMC will request an Apache id for you. In your response,
> please choose an id that is not already in use. See
> http://people.apache.org/committer-index.html
> ]
>
> [B. If you accept, the next step is to register an iCLA:
> 1. Details of the iCLA and the forms are found
> through this link: http://www.apache.org/licenses/#clas
>
> 2. Instructions for its completion and return to
> the Secretary of the ASF are found at
> http://www.apache.org/licenses/#submitting
> Do not submit ICLAs to anyone but secretary, but
> please do cc: [priv...@project.apache.org]
>
> 3. When you transmit the completed iCLA, request
> to notify the Apache [Project] and choose a
> unique Apache id. Look to see if your preferred
> id is already taken at
> http://people.apache.org/committer-index.html
> This will allow the Secretary to notify the PMC
> when your iCLA has been recorded.
> ]
>
> When your reply to this invitation is received, you will
> receive a follow-up message with the next steps for
> establishing you as a committer.
>
> Craig L Russell
> Secretary, Apache Software Foundation
> c...@apache.org http://db.apache.org/jdo
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Incubator exit interview

[Kevin A. McGrail]

On 1/14/2019 1:01 PM, Julian Hyde wrote:
> I don’t think the “decisions should be made on-list” principle applies to all 
> communication. (Otherwise why would we allow hallway conversations at 
> conferences?) I’d rather that we make better decisions than be slave to 
> principle.
>
It really does apply to everything.  Even if you have the best meeting
in the world, you bring back minutes and decisions made off list for
ratification.  That way there is then an archive of the decision and
everyone can participate.

Regards,
KAM


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

Re: [VOTE] Shut down unused/inactive incubator lists

[Kevin A. McGrail]

+1
--
Kevin A. McGrail
VP Fundraising, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Sun, Jan 20, 2019 at 7:21 PM 吴晟 Sheng Wu  wrote:

> +1
>
>
>
> Sheng Wu
> Apache SkyWalking, ShardingSphere, Zipkin
>
> From Wu Sheng 's phone.
>
>
> -- Original --
> From: sebb 
> Date: Mon,Jan 21,2019 8:12 AM
> To: general 
> Subject: Re: [VOTE] Shut down unused/inactive incubator lists
>
>
>
> The following lists are all but inactive:
>
> announce@ Last post Jan 2008
> android-interest@ Last post Mar 2011
> dev@ - only general circulars
> jaxws-tck@ (private) Last post 2012
> projects@ Last post Jul 2011
> user@ - only general circulars
>
> I think they should be shut down.
>
> Please vote so an Infra Jira can be raised to shut them down.
> They can have a bounce message added to direct posters to
> general@/private@ as appropriate
>
> [  ] +1
> [  ] -1 - give a reason please
>
> Please vote by end January 2019
>
> Sebb.
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org

Re: [DISCUSS] Training (incubating) Proposal

[Kevin A. McGrail]

+1 for Justin

On Fri, Jan 25, 2019, 18:35 Justin Mclean  Hi,
>
> I’ll comment on the other parts of the proposal once I’ve thought about it
> a bit, but I’m also have a decent amount of training and course creation
> experience and would like to be on the (P)PMC / initial committer list if
> you'll have me. Assuming you go down the IPMC I’d also happy to be a
> mentor. I also have some material I can donate around the Apache Way and
> the Incubator.
>
> JFYI I’m currently teaching at a university (on computational design) and
> teaching/assessing at an online collage 2 1/2 days a week on programming. I
> finished a qualification in teaching last year and starting another one in
> a month time.
>
> Thanks,
> Justin
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Draft incubator report

[Kevin A. McGrail]

On 2/5/2019 6:27 AM, Justin Mclean wrote:
> Hi,
>
>>> As long as these are not available to the general public all is fine. [1]
>> s/available/advertised/
> Thanks that’s a better way of putting it. Obviously any published artefact is 
> available to the general public if and when they discover it.


Thanks Justin.  The advertised vs available was a big concern for me
when I read that this morning.


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

Re: [VOTE] Accept Training into the Apache Incubator

[Kevin A. McGrail]

+1 Binding.  I'll also try again to get  Udacity, Udemy, Coursera,
Pluralsight involved now that this is going to a formal incubator podling.
I am hoping once a domino falls, more will help.

Regards,
KAM
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Wed, Feb 13, 2019 at 7:00 AM Vinayakumar B 
wrote:

> +1 (binding)
>
> -Vinay
>
>
> On Wed, Feb 13, 2019 at 4:58 PM Hans-Peter Zorn  wrote:
>
> > +1 (non-binding)
> >
> > Looking forward to work on this!
> > Thanks,
> > Hans-Peter
> >
> > > Am 13.02.2019 um 08:57 schrieb Lars Francke :
> > >
> > > Hi everyone,
> > >
> > > we've discussed the proposal for the Training project in [1] and [2].
> The
> > > proposal itself can be found on the wiki[3].
> > >
> > > According to the Incubator rules[4] I'd like to call a vote to accept
> the
> > > new "Training" project as a podling in the Apache Incubator.
> > >
> > > A vote for accepting a new Apache Incubator podling is a majority vote.
> > > Everyone is welcome to vote, only Incubator PMC member votes are
> binding.
> > > It would be helpful (but not required) if you could add a comment
> stating
> > > whether your vote is binding or non-binding.
> > >
> > > This vote will run for at least 72 hours (but I expect to keep it open
> > for
> > > longer). Please VOTE as follows:
> > >
> > > [ ] +1 Accept Training into the Apache Incubator
> > > [ ] +0 Abstain
> > > [ ] -1 Do not accept Training into the Apache Incubator because ...
> > >
> > > Thank you for everyone who decided to join in in the past discussions!
> > > Lars
> > >
> > > [1] <
> > >
> >
> https://lists.apache.org/thread.html/5c00016b769135cc302bb2ce4e5f6bbfeeda933a07e9c38b5017d651@%3Cgeneral.incubator.apache.org%3E
> > >>
> > >
> > > [2] <
> > >
> >
> https://lists.apache.org/thread.html/9cb4d7eef73e0d526e0124944c3d37325aa892675351a1eed0a25de3@%3Cgeneral.incubator.apache.org%3E
> > >>
> > >
> > > [3] <https://wiki.apache.org/incubator/TrainingProposal#preview>
> > >
> > > [4] <
> > >
> >
> https://incubator.apache.org/policy/incubation.html#approval_of_proposal_by_sponsor
> > >>
> >
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Re: [Proposal] Apache TVM

[Kevin A. McGrail]

+1 binding with a caveat:

You need mentors and champions from Apache who are available and ideally
active in the incubator.  Markus had to step down on hivemail last year.
Has his situation changed?

Some comments:
The hardware artifacts being donated is interesting and something I would
support helping.  We might want to loop in the secretary and legal vps to
discuss.

The reviewer status is something the pmc can elect to do.  They might end
up with the same karma as committers on any repos if they need that karma
is the only hurdle I can think of.  But we like a model of trust for people
so it should be a good thing.

But otherwise looks like a great start!
KAM
On Fri, Feb 15, 2019, 13:42 Markus Weimer  Hi,
>
> we'd like to start the discussion of accepting TVM into the incubator.
> Please see the proposal below. I'd like to highlight a few things for
> our discussion:
>
> (1) The project already follows many Apache ways like meritocracy,
> open development and such.
>
> (2) The project recognizes an in-between state of "reviewer" that it
> nominates people for between contributor and committer status. We'd
> like to learn if and how to maintain that in the future.
>
> (3) The project contains hardware as a software artifact. We are not
> aware of another ASF project like that and wonder if and how it
> affects its acceptance into the incubator.
>
> Thanks!
>
> Markus
>
> === Proposal ===
>
> We propose to incubate the TVM project the Apache Software Foundation. TVM
> is a
> full stack open deep learning compiler stack for CPUs, GPUs, and
> specialized
> accelerators. It aims to close the gap between the productivity-focused
> deep
> learning frameworks, and the performance- or efficiency-oriented hardware
> backends.
>
> === Background ===
>
> There is an increasing need to bring machine learning to a wide diversity
> of
> hardware devices. Current frameworks rely on vendor-specific operator
> libraries
> and optimize for a narrow range of server-class GPUs. Deploying workloads
> to new
> platforms -- such as mobile phones, embedded devices, and accelerators
> (e.g.,
> FPGAs, ASICs) -- requires significant manual effort. TVM is an end to end
> deep
> learning a compiler that exposes graph-level and operator-level
> optimizations to
> provide performance portability to deep learning workloads across diverse
> hardware back-ends. TVM solves optimization challenges specific to deep
> learning, such as high-level operator fusion, mapping to arbitrary hardware
> primitives, and memory latency hiding. It also automates optimization of
> low-level programs to hardware characteristics by employing a novel,
> learning-based cost modeling method for rapid exploration of program
> optimizations.
>
> Moreover, there is increasing interest in designing specialized hardware
> which
> accelerates machine learning. Towards this goal, TVM introduces VTA, an
> open
> source deep learning accelerator as part of its stack. The open source VTA
> driver and hardware design is a crucial step toward building software
> support
> for future ASICs. The TVM-VTA flow acts as a is the great frontier for
> researchers and practitioners to explore specialized hardware designs.
>
>
> === Rationale ===
>
> Deep learning compilation will be the next frontier of machine learning
> systems.
> TVM is already one of the leading open source projects pursuing this
> direction.
>
> Specifically, TVM provides infrastructure to use machine learning to
> automatically optimize deployment of deep learning programs on diverse
> hardware
> backends.
>
>
> === VTA: Open Source Hardware Design ===
>
> TVM also contains open source hardware as part of its stack. The VTA
> hardware
> design is a fully open sourced deep learning accelerator that allows us to
> experiment with compiler, driver, runtime, and execute the code on FPGA.
> VTA
> provides a path to target future ASICs, and build software-driven
> solutions to
> co-design future deep learning accelerators.
>
> Having an open source hardware design in an ASF project is rare and perhaps
> unprecedented. We put some of our rationale on why it is necessary for the
> community.
>
> Deep learning specialized ASICs are going to be at the center of the AI
> revolution. However, given its early shape, there is no open standard, or
> even
> any available information hardware interface that allows an open source
> software
> to target to. VTA provides such open source hardware abstraction layer and
> allows us to build in abstractions that can be effectively used to target
> other
> deep learning accelerators.
>
> Moreover, there is an increasing need for co-designing future of machine
> learning systems with the hardware abstraction. Having a co-designed open
> source
> hardware stack along with the software creates a path for this route. In
> short,
> we need open-source hardware to build the best open source software.
>
> Finally, we can still view VTA design as “software”, as its source code is
> writ

Re: Starting at the incubator and releases

[Kevin A. McGrail]

I think this might be a really important faq on the top of the list of
OK, now we are voted in, what's next?  and a FAQ about releases.

On 2/19/2019 5:38 PM, Justin Mclean wrote:
> Hi,
>
> Looking at some of the situations we currently have I think we may need some 
> more general guidance for incubating projects and making releases after just 
> joining the incubator. In this context “non approved” means releases or 
> distributions not approved by the PPPM and IPMC (usually by voting) and 
> available and promoted to the general public. This doesn’t cover snapshots, 
> RCs or nightly which are not advertised to the general public. Feedback / 
> changes / thoughts from the rest of the IPMC members welcome.
>
> 1. Can the PPMC can distrubite artefacts in other places that are based on 
> approved releases. 
>
> Yes.
>
> 2. Can the PPMC make unapproved releases in other places after joining the 
> incubator?
>
> No but 3rd parties can and someone from the PPMC can act as a 3rd party, it 
> must be clear that:
> a) These are produced by a 3rd party and not the PPMC and follow Apache's 
> branding and trademark policy. 
> b) This is not being used as a mechanism to avoid making Apache releases.
>
> 3. Can the PPMC make unapproved releases in their Apache repo after the code 
> has been moved to the incubator repo?
>
> No.
>
> 4. Can the PPMC make unapproved release in other places after the code has 
> been moved to the incubator repo?
>
> No but 3rd parties can. See 2.
>
> 5. Can the PPMC keep two repos and continue to make releases in the non 
> Apache one after the code has been moved to the incubator repo?
>
> No but 3rd parties can. See 2. It’s likely that the old repo name may need to 
> change to avoid confusion with the Apache project.
>
> 6. Can the PPMC link to unapproved releases or distributions from their 
> website or download pages.
>
> No, unless these are clearly marked as 3rd party releases and not endorsed by 
> the PPMC.
>
> 7. When should the first ASF release be made.
>
> Ideally within six months of joining the incubator. Remember this first 
> release doesn’t have to be perfect.
>
> There may be the occasional exception to these guidelines, this would need to 
> be discussed and approved by your mentors and the IPMC informed.
>
> Thanks,
> Justin
>
>
>
> -------------
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: Starting at the incubator and releases

[Kevin A. McGrail]

On 2/19/2019 6:07 PM, Dave Fisher wrote:
> (5) Go and develop in The Apache Way!
>
> Only once these four things happen can we start any timer on the first Apache 
> Release.

Four, no FIVE things!  Don't forget the Spanish Inquisition.

Agreed.  We need to setup the reason hurdles with a carrot so that
podlings understand these steps are necessary for releases to resume.

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: [VOTE] Accept Cava into the Apache Incubator

[Kevin A. McGrail]

+1 binding with the condition that a new name is picked before the
onboarding starts to lighten the load on the foundation (especially Infra).

On 2/20/2019 2:50 PM, Antoine Toulme wrote:
> Hi everyone,
>
> we've discussed the proposal for the Cava project in [1] and [2]. The
> proposal itself can be found on the wiki[3].
>
> We discussed how to go about finding a suitable name for the project in [2].
> I will kick off a vote to pick a name based on the proposals made there.
>
> According to the Incubator rules[4] I'd like to call a vote to accept the
> new "Cava" project as a podling in the Apache Incubator.
>
> A vote for accepting a new Apache Incubator podling is a majority vote.
> Everyone is welcome to vote, only Incubator PMC member votes are binding.
> It would be helpful (but not required) if you could add a comment stating
> whether your vote is binding or non-binding.
>
> This vote will run for at least 72 hours (but I expect to keep it open for
> longer). Please VOTE as follows:
>
> [ ] +1 Accept Cava into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept Cava into the Apache Incubator because ...
>
> Thank you for everyone who decided to join in in the past discussions!
> Antoine
>
> [1]: 
> https://lists.apache.org/thread.html/5a7f6a218b11a1cac61fbd53f4c995fd7716f8ad3751cf9f171ebd57@%3Cgeneral.incubator.apache.org%3E
> [2]: 
> https://lists.apache.org/thread.html/8d8014f53f140a3ccdd517c3c303de1d45cc04afdaee5961ac43e7fc@%3Cgeneral.incubator.apache.org%3E
> [3]: https://wiki.apache.org/incubator/CavaProposal?action=recall&rev=14
> [4]: https://incubator.apache.org/guides/proposal.html#the_vote
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: Incubator release votes

[Kevin A. McGrail]

On 2/26/2019 8:20 AM, David P Grove wrote:
> 
> Or in the case of the current OpenWhisk podling voting thread [1], our only
> mentor has already voted +1, but after a week we still need two more IPMC
> votes to be able to proceed.
>
> Please help
> 

Sorry, I was not aware of that issue.  I'm monitoring for the podlings I
help with but not as much with general@

I vote +1.

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: [Cava] Suitable name search - choosing a name

[Kevin A. McGrail]

Antoine,

I hate to throw a wrench in the works but there has been so much traffic
here, I missed that thread.  Jal (just another language) is a
programming language:https://en.wikipedia.org/wiki/JAL_(compiler) &
http://justanotherlanguage.org/

I don't think it's going to be appropriate for us to step on another
open source project name.

Regards,
KAM

On 2/26/2019 5:02 PM, Antoine Toulme wrote:
> Thanks all.
>
> We have a clear winner with “Jal”, with 4 +1 votes and no votes for other 
> names.
> Thank you for your participation!
>
> I will make mention of the result of this consultation on the proposal.
>
> We are now set to open the podling.
>
> Cheers,
>
> Antoine
>
>> On Feb 25, 2019, at 1:38 AM, Jean-Baptiste Onofré  wrote:
>>
>> +1 for Jal
>>
>> Regards
>> JB
>>
>> On 22/02/2019 23:47, Antoine Toulme wrote:
>>> Hi all,
>>>
>>> I have opened a thread to vote the Cava proposal into the incubator [0].
>>>
>>> At the same time, I have engaged with the list on searching a better name 
>>> for the project [1].
>>>
>>> Out of this initial thread, we have singled out a list of names.
>>>
>>> Here are the names:
>>> - Rainbow (after the name of my kid’s favorite toy, and in line with the 
>>> crypto community unicorn punk theme [2].
>>> - Winch (a mechanical device used to wind up or wind out wires (Wikipedia) 
>>> , in the chain theme)
>>> - Sprocket (a profiled wheel with teeth, or cogs, that mesh with a chain, 
>>> track or other perforated or indented material. (Wikipedia), in the chain 
>>> theme as well)
>>> - “Jal”, in reference to Indra’s net (or Indra jal) (with a quote from [3]: 
>>> "Imagine a multidimensional spider's web in the early morning covered with 
>>> dew drops. And every dew drop contains the reflection of all the other dew 
>>> drops. 
>>> And, in each reflected dew drop, the reflections of all the other dew drops 
>>> in that reflection. And so ad infinitum. That is the Buddhist conception of 
>>> the universe in an image." –Alan Watts)
>>>
>>> In this thread, please indicate the one name you like most. Please feel 
>>> free to justify your choice.
>>> Based on your input, the project will adopt the name. In absence of a 
>>> strong contender, I'll work with the Champion (Jim Jagielski) to pick a 
>>> name.
>>>
>>> I'll keep the thread open for 72 hours - that gives us until Tuesday 
>>> afternoon PST time.
>>>
>>> Cheers,
>>>
>>> Antoine
>>>
>>> [0]: 
>>> https://lists.apache.org/thread.html/5634b8f24cf552da4cba12ab4b59647bfa6800b7380833d8131331e9@%3Cgeneral.incubator.apache.org%3E
>>> [1]: 
>>> https://lists.apache.org/thread.html/8d8014f53f140a3ccdd517c3c303de1d45cc04afdaee5961ac43e7fc@%3Cgeneral.incubator.apache.org%3E
>>> [2]: https://www.urbandictionary.com/define.php?term=unicorn%20punk
>>> [3]: https://en.wikipedia.org/wiki/Indra%27s_net
>>> -
>>> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
>>> For additional commands, e-mail: general-h...@incubator.apache.org
>>>
>> -- 
>> Jean-Baptiste Onofré
>> jbono...@apache.org
>> http://blog.nanthrax.net
>> Talend - http://www.talend.com
>>
>> -
>> 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
>

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: [Cava] Suitable name search - choosing a name

[Kevin A. McGrail]

Thanks Antoine,

I am happy to help and vote but I want to make sure I'm right before we get
to that stage.

I don't know if branding or legal (or press) would oppose the name Jal.  My
$0.02 is that if this were a corporate entity, the likelihood for confusion
would be very high with two OSS projects named Jal.  And while JAL, the
programming language, might not have a Trademark, it would be rude IMO to a
long standing project to just hijack the name.

If they have trademarks, it would be almost certainly a torpedo to the
name.  My assumption is that the name suitability is rooted in finding a
trademarkable, unique, defendable, and brandable name.

With Jal being an existing OSS project (
https://en.wikipedia.org/wiki/JAL_(compiler) &
http://justanotherlanguage.org/), I'm certainly not excited by using that
name.  For now, consider me a -0.5 and I welcome the opportunity to be
convinced differently.

Sorry, I'm really working hard to make the incubator process positive so my
apologies again for a last minute monkey wrench.  I just happened to catch
the subject on the thread and I know some PIC programming in JAL and so
here we are...

Regards,
KAM


--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Tue, Feb 26, 2019 at 5:20 PM Antoine Toulme  wrote:

> I am aware of those uses, but they don’t seem to cross with the domain of
> the project.
> The suitable name search guide [0] expresses a lot of subtlety about name
> uniqueness which gave me this interpretation.
>
> Nevertheless, let’s then reopen the thread:
>
> Would you like to vote for another name in the list proposed?
>
> [0]: https://incubator.apache.org/guides/names.html#what_makes_a_name_good
>
>
> > On Feb 26, 2019, at 2:11 PM, Kevin A. McGrail 
> wrote:
> >
> > Antoine,
> >
> > I hate to throw a wrench in the works but there has been so much traffic
> > here, I missed that thread.  Jal (just another language) is a
> > programming language:https://en.wikipedia.org/wiki/JAL_(compiler) &
> > http://justanotherlanguage.org/
> >
> > I don't think it's going to be appropriate for us to step on another
> > open source project name.
> >
> > Regards,
> > KAM
> >
> > On 2/26/2019 5:02 PM, Antoine Toulme wrote:
> >> Thanks all.
> >>
> >> We have a clear winner with “Jal”, with 4 +1 votes and no votes for
> other names.
> >> Thank you for your participation!
> >>
> >> I will make mention of the result of this consultation on the proposal.
> >>
> >> We are now set to open the podling.
> >>
> >> Cheers,
> >>
> >> Antoine
> >>
> >>> On Feb 25, 2019, at 1:38 AM, Jean-Baptiste Onofré 
> wrote:
> >>>
> >>> +1 for Jal
> >>>
> >>> Regards
> >>> JB
> >>>
> >>> On 22/02/2019 23:47, Antoine Toulme wrote:
> >>>> Hi all,
> >>>>
> >>>> I have opened a thread to vote the Cava proposal into the incubator
> [0].
> >>>>
> >>>> At the same time, I have engaged with the list on searching a better
> name for the project [1].
> >>>>
> >>>> Out of this initial thread, we have singled out a list of names.
> >>>>
> >>>> Here are the names:
> >>>> - Rainbow (after the name of my kid’s favorite toy, and in line with
> the crypto community unicorn punk theme [2].
> >>>> - Winch (a mechanical device used to wind up or wind out wires
> (Wikipedia) , in the chain theme)
> >>>> - Sprocket (a profiled wheel with teeth, or cogs, that mesh with a
> chain, track or other perforated or indented material. (Wikipedia), in the
> chain theme as well)
> >>>> - “Jal”, in reference to Indra’s net (or Indra jal) (with a quote
> from [3]: "Imagine a multidimensional spider's web in the early morning
> covered with dew drops. And every dew drop contains the reflection of all
> the other dew drops.
> >>>> And, in each reflected dew drop, the reflections of all the other dew
> drops in that reflection. And so ad infinitum. That is the Buddhist
> conception of the universe in an image." –Alan Watts)
> >>>>
> >>>> In this thread, please indicate the one name you like most. Please
> feel free to justify your choice.
> >>>> Based on your input, the project will adopt the name. In absence of a
> strong contender, I'll work with the Champion (Jim Jagielski) to pick a
> name.
> >>>>
> >>

Re: [Cava] Suitable name search - choosing a name

[Kevin A. McGrail]

On 2/26/2019 6:24 PM, Kenneth Knowles wrote:
> I searched for "Jal" and came up with Japan Air Lines, which is clearly a
> really different field of use.
>
> I also found the Wikipedia article on JAL but was hasty in presuming it
> described a historical language. If it is an active open source project,
> let's not collide.
>
> So I'll change my vote to "Winch". I again did a quick search, but sounds
> like someone should check my work...

Re: JAL, the airline is just not an issue.  The programming language I
think is as there are books on Amazon less than 6 years old on PAL
(https://www.amazon.com/PIC-Microcontroller-Programming-captivating-lessons/dp/190792017X)
 
I don't think it's legacy just perhaps mature and things like Raspberry
Pi's overtaking the field.

Re: Winch, might be a common name and undefendable as a trademark, etc. 
Otherwise, though, I couldn't find much relevant in OSS spaces except a
company called winch gate. 

http://tmsearch.uspto.gov/ might help

Regards,

KAM



-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: [Cava] Suitable name search - choosing a name

[Kevin A. McGrail]

Not an objection per se but two comments:

1 - Rainbow is associated with LGBTQ communities and there have been
concerns about it being co-opted for other uses.  For example,
https://www.theguardian.com/commentisfree/2017/jul/02/brands-rainbow-queasy-but-bring-lgbt-lives-into-mainstream-skittles-gay

2 - I cannot speak for the LGBTQ community and I support them so I would
say rainbow would be something I would avoid.

In the business world I often recommend people consider made up words. 
Less chance of conflictions.

Regards,
KAM

On 2/28/2019 3:28 AM, Antoine Toulme wrote:
> Hey folks, just checking in.
>
> I would like to establish rough consensus. If you’re still following, we have 
> narrowed down the list to rainbow, sprocket and winch.
>
> We have one vote for rainbow, and one for winch.
>
> When establishing rough consensus, it’s a good idea to push proposals to hear 
> objections.
>
> At this time, I’d like to push for the name rainbow. Any objections?
>
>> On Feb 26, 2019, at 10:10 PM, Antoine Toulme  wrote:
>>
>> I ran searches for rainbow, sprocket and winch and didn’t find OSS projects 
>> with those names.
>>
>> I personally would like to vouch for Rainbow. It does fit the whimsical 
>> requirement of Apache project names.
>>
>>> On Feb 26, 2019, at 3:57 PM, Kevin A. McGrail  wrote:
>>>
>>> On 2/26/2019 6:24 PM, Kenneth Knowles wrote:
>>>> I searched for "Jal" and came up with Japan Air Lines, which is clearly a
>>>> really different field of use.
>>>>
>>>> I also found the Wikipedia article on JAL but was hasty in presuming it
>>>> described a historical language. If it is an active open source project,
>>>> let's not collide.
>>>>
>>>> So I'll change my vote to "Winch". I again did a quick search, but sounds
>>>> like someone should check my work...
>>> Re: JAL, the airline is just not an issue.  The programming language I
>>> think is as there are books on Amazon less than 6 years old on PAL
>>> (https://www.amazon.com/PIC-Microcontroller-Programming-captivating-lessons/dp/190792017X)
>>>  
>>> I don't think it's legacy just perhaps mature and things like Raspberry
>>> Pi's overtaking the field.
>>>
>>> Re: Winch, might be a common name and undefendable as a trademark, etc. 
>>> Otherwise, though, I couldn't find much relevant in OSS spaces except a
>>> company called winch gate. 
>>>
>>> http://tmsearch.uspto.gov/ might help
>>>
>>> Regards,
>>>
>>> KAM
>>>
>>>
>>>
>>> -- 
>>> Kevin A. McGrail
>>> Member, Apache Software Foundation
>>> Chair Emeritus Apache SpamAssassin Project
>>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>>
>>>
>>> -
>>> 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
>

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: [Cava] Suitable name search - choosing a name

[Kevin A. McGrail]

Jim, I don't read https://incubator.apache.org/guides/names.html to lead
me to believe we are at that stage yet.  I think we want to have
discussions about a provisional name first.  Specifically, "A podling
needs to discover whether a name is suitable."

Regards,
KAM

On 2/28/2019 9:42 AM, Jim Jagielski wrote:
> We should simply file a standard Jira request for a podling namecheck.
>
>> On Feb 28, 2019, at 9:36 AM, Kevin A. McGrail  wrote:
>>
>> Not an objection per se but two comments:
>>
>> 1 - Rainbow is associated with LGBTQ communities and there have been
>> concerns about it being co-opted for other uses.  For example,
>> https://www.theguardian.com/commentisfree/2017/jul/02/brands-rainbow-queasy-but-bring-lgbt-lives-into-mainstream-skittles-gay
>>
>> 2 - I cannot speak for the LGBTQ community and I support them so I would
>> say rainbow would be something I would avoid.
>>
>> In the business world I often recommend people consider made up words. 
>> Less chance of conflictions.
>>
>> Regards,
>> KAM
>>
>> On 2/28/2019 3:28 AM, Antoine Toulme wrote:
>>> Hey folks, just checking in.
>>>
>>> I would like to establish rough consensus. If you’re still following, we 
>>> have narrowed down the list to rainbow, sprocket and winch.
>>>
>>> We have one vote for rainbow, and one for winch.
>>>
>>> When establishing rough consensus, it’s a good idea to push proposals to 
>>> hear objections.
>>>
>>> At this time, I’d like to push for the name rainbow. Any objections?
>>>
>>>> On Feb 26, 2019, at 10:10 PM, Antoine Toulme  wrote:
>>>>
>>>> I ran searches for rainbow, sprocket and winch and didn’t find OSS 
>>>> projects with those names.
>>>>
>>>> I personally would like to vouch for Rainbow. It does fit the whimsical 
>>>> requirement of Apache project names.
>>>>
>>>>> On Feb 26, 2019, at 3:57 PM, Kevin A. McGrail  wrote:
>>>>>
>>>>> On 2/26/2019 6:24 PM, Kenneth Knowles wrote:
>>>>>> I searched for "Jal" and came up with Japan Air Lines, which is clearly a
>>>>>> really different field of use.
>>>>>>
>>>>>> I also found the Wikipedia article on JAL but was hasty in presuming it
>>>>>> described a historical language. If it is an active open source project,
>>>>>> let's not collide.
>>>>>>
>>>>>> So I'll change my vote to "Winch". I again did a quick search, but sounds
>>>>>> like someone should check my work...
>>>>> Re: JAL, the airline is just not an issue.  The programming language I
>>>>> think is as there are books on Amazon less than 6 years old on PAL
>>>>> (https://www.amazon.com/PIC-Microcontroller-Programming-captivating-lessons/dp/190792017X)
>>>>>  
>>>>> I don't think it's legacy just perhaps mature and things like Raspberry
>>>>> Pi's overtaking the field.
>>>>>
>>>>> Re: Winch, might be a common name and undefendable as a trademark, etc. 
>>>>> Otherwise, though, I couldn't find much relevant in OSS spaces except a
>>>>> company called winch gate. 
>>>>>
>>>>> http://tmsearch.uspto.gov/ might help
>>>>>
>>>>> Regards,
>>>>>
>>>>> KAM
>>>>>
>>>>>
>>>>>
>>>>> -- 
>>>>> Kevin A. McGrail
>>>>> Member, Apache Software Foundation
>>>>> Chair Emeritus Apache SpamAssassin Project
>>>>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>>>>
>>>>>
>>>>> -
>>>>> 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
>>>
>> -- 
>> Kevin A. McGrail
>> Member, Apache Software Foundation
>> Chair Emeritus Apache SpamAssassin Project
>> https://www.linkedin.com/in/kmcgrail - 703.798.0171
>>
>>
>> -
>> 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
>

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: [Cava] Suitable name search - choosing a name

[Kevin A. McGrail]

A rose by any other name would still be as sweet so I am +1 on the
proposal.  Just trying to help with the naming issue and to save the
project and infra grief of it needs to change.

But I am here to support and feel bad to throw any gunk in your sprockets.

Best, KAM

On Thu, Feb 28, 2019, 13:59 Antoine Toulme  For context Jim is the champion of the Cava proposal.
>
> The point of rough consensus is to bring about strong objections and move
> past non-votes.
> I believe we are at that point, and I will move forward to consider this
> thread closed with the name Rainbow.
> I will open a pooling namecheck and move to the next step there.
>
> Thanks,
>
> Antoine
>
> > On Feb 28, 2019, at 7:41 AM, Jim Jagielski  wrote:
> >
> > Well, I have no doubt that the proposal is going to pass, so we might as
> well progress on w/ that assumption. ;)
> >
> >> On Feb 28, 2019, at 10:09 AM, Kevin A. McGrail 
> wrote:
> >>
> >> Jim, I don't read https://incubator.apache.org/guides/names.html to
> lead
> >> me to believe we are at that stage yet.  I think we want to have
> >> discussions about a provisional name first.  Specifically, "A podling
> >> needs to discover whether a name is suitable."
> >>
> >> Regards,
> >> KAM
> >>
> >> On 2/28/2019 9:42 AM, Jim Jagielski wrote:
> >>> We should simply file a standard Jira request for a podling namecheck.
> >>>
> >>>> On Feb 28, 2019, at 9:36 AM, Kevin A. McGrail 
> wrote:
> >>>>
> >>>> Not an objection per se but two comments:
> >>>>
> >>>> 1 - Rainbow is associated with LGBTQ communities and there have been
> >>>> concerns about it being co-opted for other uses.  For example,
> >>>>
> https://www.theguardian.com/commentisfree/2017/jul/02/brands-rainbow-queasy-but-bring-lgbt-lives-into-mainstream-skittles-gay
> >>>>
> >>>> 2 - I cannot speak for the LGBTQ community and I support them so I
> would
> >>>> say rainbow would be something I would avoid.
> >>>>
> >>>> In the business world I often recommend people consider made up
> words.
> >>>> Less chance of conflictions.
> >>>>
> >>>> Regards,
> >>>> KAM
> >>>>
> >>>> On 2/28/2019 3:28 AM, Antoine Toulme wrote:
> >>>>> Hey folks, just checking in.
> >>>>>
> >>>>> I would like to establish rough consensus. If you’re still
> following, we have narrowed down the list to rainbow, sprocket and winch.
> >>>>>
> >>>>> We have one vote for rainbow, and one for winch.
> >>>>>
> >>>>> When establishing rough consensus, it’s a good idea to push
> proposals to hear objections.
> >>>>>
> >>>>> At this time, I’d like to push for the name rainbow. Any objections?
> >>>>>
> >>>>>> On Feb 26, 2019, at 10:10 PM, Antoine Toulme 
> wrote:
> >>>>>>
> >>>>>> I ran searches for rainbow, sprocket and winch and didn’t find OSS
> projects with those names.
> >>>>>>
> >>>>>> I personally would like to vouch for Rainbow. It does fit the
> whimsical requirement of Apache project names.
> >>>>>>
> >>>>>>> On Feb 26, 2019, at 3:57 PM, Kevin A. McGrail 
> wrote:
> >>>>>>>
> >>>>>>> On 2/26/2019 6:24 PM, Kenneth Knowles wrote:
> >>>>>>>> I searched for "Jal" and came up with Japan Air Lines, which is
> clearly a
> >>>>>>>> really different field of use.
> >>>>>>>>
> >>>>>>>> I also found the Wikipedia article on JAL but was hasty in
> presuming it
> >>>>>>>> described a historical language. If it is an active open source
> project,
> >>>>>>>> let's not collide.
> >>>>>>>>
> >>>>>>>> So I'll change my vote to "Winch". I again did a quick search,
> but sounds
> >>>>>>>> like someone should check my work...
> >>>>>>> Re: JAL, the airline is just not an issue.  The programming
> language I
> >>>>>>> think is as there are books on Amazon less than 6 years old on PAL
> >>>>>>> (
> https://www.amazon

Re: [Cava] Suitable name search - choosing a name

[Kevin A. McGrail]

On 2/28/2019 3:24 PM, Daniel Gruno wrote:
>>
>> It also seems to imply that usage of the name rainbow would somehow
>> be offensive or insensitive. Again, I'm not sure how. Nor am I aware
>> of situations where the LGBT+ community "has expressed concerns"
>> about usage *of the name* Rainbow.
>
> +1
>
> Anyone could hypothetically be offended by anything, I could list a
> large number of theoretical offenses in project names. Let's please
> stick to *actual* feedback and not preemptively censor ourselves. If
> such feedback exists, fair enough, but I am also not aware of any such. 

I have asked off-list for someone I trust in the LGBTQ community who is
also an ASF member to weigh in on this but I am aware that this is a
concern.  I just can't articulate how much of a concern it is.  I will
work to get that better clarified for the podling.

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

Re: [Cava] Suitable name search - choosing a name

[Kevin A. McGrail]

On 2/28/2019 4:28 PM, Jim Jagielski wrote:
> I am aware of various members of the LGBT+ community being offended by 
> companies
> trying to *co-opt* the rainbow *symbol* specifically and explicitly in 
> relation to a cheap
> and easy way to show "support" or a way to be "hip" or "cool"... heck, I'm 
> offended by it as well.
>
> But that's not what we're talking about.

A) I don't speak for the LGBTQ community and hence I can only say it's a
concern and not how much of a concern it is.  Just that I'm aware of the
issue in general.

B) I think the Apache Rainbow project would inevitably have a Rainbow in
it's logo which is where I see a possible concern but again see A)

As I mentioned, I've asked if an ASF member with a better grasp of the
potential issue to weigh in.  Not much else I can say about the issue.


-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: [Cava] Suitable name search - choosing a name

[Kevin A. McGrail]

On 2/28/2019 4:37 PM, Jim Jagielski wrote:
> What about Bava? Blockchain Java and no offensive meanings that I can find.
>
No trademark concerns I see or commercial / OSS uses that conflict that
I see.

Note: From the USPTO TESS: "*BAVA*" is an Italian word that means
"slobber" or "drool".  Not sure if this will permalink:
http://tmsearch.uspto.gov/bin/showfield?f=doc&state=4804:rx7o71.2.7

So I'm totally +1 for Apache Slobber :-)

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

Re: Whimsy general@ subs check (was: [DISCUSS] introduce "[DISCUSS]" threads for podling non-ASF release candidates)

[Kevin A. McGrail]

On 3/1/2019 5:12 AM, Justin Mclean wrote:
>> The Board isn't gonna worry about something like that.
> I wasn’t expecting the board to say anything re that, but the IPMC could of.

I personally don't know the impact of that statement either.  Sometimes
opinion in a report and a call to action is helpful.

What can I do to help fix this issue?

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171

Re: A smaller IPMC

[Kevin A. McGrail]

I am not aware of the problem we are trying to fix.  I don't even know if I
am a mentor not subscribed to private@.

Without knowing what we are trying to solve, it is hard to weigh in on
fixes.

So my ask is what is the issue?

On Thu, Mar 7, 2019, 19:25 Liang Chen  Hi
>
> One more suggestion: How about maintaining one table, and ask IPMC to
> freely
> provide info by them-self which part they are mentoring or will be going to
> mentor as volunteer.
> For example myself : Helping new project (DataSketches)  to prepare
> incubator proposal. and participate in some vote for new releases and new
> projects.
>
> Regards
> Liang
>
>
> Ted Dunning wrote
> > I don't think that the number of inactive IPMC members is a factor in
> > anything. They are, by definition, inactive.
> >
> > So I would vote for the no-op action (#4, I think).
> >
> >
> >
> > On Thu, Mar 7, 2019 at 3:39 PM Roman Shaposhnik <
>
> > roman@
>
> > >
> > wrote:
> >
> >> On Thu, Mar 7, 2019 at 3:33 PM Justin Mclean <
>
> > justin@
>
> > >
> >> wrote:
> >> >
> >> > Hi,
> >> >
> >> > It’s been suggested that the IPMC is too large, what do other IPMC
> >> members think might be a way to address this?
> >>
> >> Personally, I believe that "IPMC is too large" argument is only
> >> applicable
> >> to
> >> how quickly/easily consensus can be built. That's literally the only
> >> situation
> >> when the size of IPMC gets in the way (sometimes).
> >>
> >> Is anyone aware of any other situations where "IPMC is too large"
> >> argument
> >> is actually legit?
> >>
> >> At any rate, the rest of my feedback will be from that single
> >> perspective:
> >>
> >> > Please discuss and indicate +1 what you would think would help, you
> can
> >> vote for more than one.
> >> >
> >> > Some suggestions:
> >> > 1. Ask all inactive IPMC if they want to continue being on the IPMC
> and
> >> see who steps down. Being inactive they are probably not following this
> >> list so we need to identify and send each one email them personally.
> >> > 2. There were some questions around merit raised, remove all IPMC
> >> members who were not on the initial proposal and who were voted in.
> Those
> >> left on the IPMC vote back in those who are currently active.
> >> > 3. Get rid of all IPMC members, and vote (with ASF members vote being
> >> binding - not sure how else it could be done?) currently active ones
> back
> >> in.
> >> > 4. Do nothing as this is not actually a problem but instead address
> >> other underlying issues. e.g. lack of mentor engagement.
> >>
> >> I would like to suggest a 5th alternative (again this is from the
> >> above's perspective):
> >>* Don't change anything, but for any situation that requires
> >> consensus building just be a tad more formal with how we close loops
> >> and track if we really get as many obstructionists as we thing that
> >> the size of the IPMC allows. If not -- we don't have a problem.
> >>
> >> > Also re point 2 do you think we should drop that ASF members can
> >> automatically get IPMC membership and change it to requiring a vote by
> >> the
> >> IPMC? It’s has always seem odd to me that this is the case. We’ve
> >> recently
> >> voted more people in that we’ve had requests from ASF members.
> >> >
> >> > Any other sugestions?
> >> >
> >> > Options 2 and 3 may cause some issues around mentors, but if they were
> >> not active then I guess it’s no big loss.
> >> >
> >> > And any suggestions on level of activity? Such as:
> >> > - Emailed the list in the last year.
> >> > - Reviewed at least one release in that time.
> >> >
> >> > It’s already been determined that some (about 15%) of the less than
> >> active PMC members (out of the 100 odd that are not signed up to the
> IPMC
> >> private list) do help out infrequently but that help is very useful.
> That
> >> may also apply to other inactive IPMC members, so I would suggest the
> bar
> >> for what consider active be kept low.
> >>
> >> I honestly don't see how all of these options of getting people in and
> >> out of IPMC can actually help with this consensus building thing. So
> >> yeah -- I'd say #5.
> >>
> >> Thanks,
> >> Roman.
> >>
> >> -
> >> To unsubscribe, e-mail:
>
> > general-unsubscribe@.apache
>
> >> For additional commands, e-mail:
>
> > general-help@.apache
>
> >>
> >>
>
>
>
>
>
> --
> Sent from: http://apache-incubator-general.996316.n3.nabble.com/
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Release Apache ECharts (incubating) 4.2.1 (release candidate 3)

[Kevin A. McGrail]

I apologize that I am very busy preparing for the road show and cannot
weigh in on this release.  I will work harder to have a system ready for
this for the next time.

Regards,
KAM

On 3/6/2019 1:58 AM, SHUANG SU wrote:
> I am pleased to be calling this vote for the release of Apache ECharts
> (incubating) 4.2.1 (release candidate 3).
>
> Apache ECharts community has voted and approved the release.
>
> Vote thread:
> https://lists.apache.org/thread.html/6f555bdb3bdc23ac9e260116738af779d4dff7b7e21f77c0a3369905@%3Cdev.echarts.apache.org%3E
>
> Results thread:
> https://lists.apache.org/thread.html/54a63e2208330dd68c39bdcb5bd444301d0eb8580d433d1ac3fe4500@%3Cdev.echarts.apache.org%3E
>
> The release candidate to be voted over is available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.3/
>
> The release candidate is signed with a GPG key available at:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/KEYS
>
> The Git commit for this release is:
> https://gitbox.apache.org/repos/asf?p=incubator-echarts.git;a=commit;h=1a2e990
>
> The Release Note is available in:
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.3/RELEASE_NOTE.txt
>
> Some shell commands for validating the release:
>
> ```shell
> # Download the release:
> curl
> https://dist.apache.org/repos/dist/dev/incubator/echarts/4.2.1-rc.3/apache-echarts-4.2.1-rc.3-incubating-src.zip
> -o apache-echarts-4.2.1-rc.3-incubating-src.zip
> unzip apache-echarts-4.2.1-rc.3-incubating-src.zip -d
> apache-echarts-4.2.1-rc.3-incubating-src > /dev/null
>
> # Rebuild the project (Node.js environment is required):
> cd "apache-echarts-4.2.1-rc.3-incubating-src" && npm install && cd ..
> node "apache-echarts-4.2.1-rc.3-incubating-src/build/build.js" --release
> # (See help: `node
> "apache-echarts-4.2.1-rc.3-incubating-src/build/build.js" --help`)
> ```
>
>
> Please vote on releasing this package as:
> Apache ECharts (incubating) 4.2.1 (release candidate 3)
> by "2019-03-09T07:42:38.040Z".
>
> [ ] +1 Release this package
> [ ] 0 I don't feel strongly about it, but don't object
> [ ] -1 Do not release this package because...
>
> Anyone can participate in testing and voting, not just committers, please
> feel free to try out the release candidate and provide your votes.
>
>
> --
>  Su Shuang (100pah)
> --
>

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Fossbytes: The Linux Foundation Announces CHIPS Alliance To Open-source Chip Designs

[Kevin A. McGrail]

I thought this was interesting regarding discussions about ASLv2 and
hardware:

Fossbytes: The Linux Foundation Announces CHIPS Alliance To Open-source
Chip Designs.
https://fossbytes.com/linux-foundation-announces-chips-alliance/

Re: [VOTE] Accept DataSketches into the Apache Incubator

[Kevin A. McGrail]

I'd like to vote -1 since you made me look up the word "stochastic" and
that feels like homework but I will vote +1 (binding).  Please don't
make me do any math.

On 3/14/2019 5:23 PM, Kenneth Knowles wrote:
> Hi all,
>
> We've discussed the proposal for the DataSketches project in [1] and [2].
> The
> proposal itself has been put on the wiki [3].
>
> Per incubator rules [4] I'd like to call a vote to accept the new
> "DataSketches" project as a podling in the Apache Incubator.
>
> A vote for accepting a new Apache Incubator podling is a majority vote.
> Everyone is welcome to vote, only Incubator PMC member votes are binding.
> It would be helpful (but not required) if you could add a comment stating
> whether your vote is binding or non-binding.
>
> This vote will run for at least 72 hours (but I expect to keep it open for
> longer). Please VOTE as follows:
>
> [ ] +1 Accept DataSketches into the Apache Incubator
> [ ] +0 Abstain
> [ ] -1 Do not accept DataSketches into the Apache Incubator because ...
>
> Thanks to everyone who contributed to the proposal and discussions.
>
> Kenn
>
> [1]
> https://lists.apache.org/thread.html/329354bd6a463dab56c2539972cfa2d6c6da7c75900216d785db4e3b@%3Cgeneral.incubator.apache.org%3E
> [2]
> https://lists.apache.org/thread.html/c9873cd4fcdc6367bcf530d8fa1ef09f3035f38e7c435e1a79a93885@%3Cgeneral.incubator.apache.org%3E
> [3] https://wiki.apache.org/incubator/DataSketchesProposal
> [4] https://incubator.apache.org/guides/proposal.html#the_vote
>

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: [Cava] Suitable name search - choosing a name

[Kevin A. McGrail]

On 3/19/2019 8:19 AM, Jim Jagielski wrote:
> What is somewhat funny is that the "SkyWalking" podling is on the cusp of 
> graduation. :)

I would say that's irrelevant.  Skywalking is a term that is from the
iron workers from ~100 years ago.  Obi-wan, however, is likely unique
and defendable to the Star Wars works. 

Was Skywalking able to get a mark? They have TM on their logo.  However,
I would say the possibility people will use Star Wars references with
Skywalking is relevant and should be warned to them.

Regrds,
KAM


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

Re: USPTO links (was: [Cava] Suitable name search - choosing a name)

[Kevin A. McGrail]

On 3/19/2019 8:32 PM, Shane Curcuru wrote:
> Kevin A. McGrail wrote on 2/28/19 7:58 PM:
> ...snip...
>> Note: From the USPTO TESS: "*BAVA*" is an Italian word that means
>> "slobber" or "drool".  Not sure if this will permalink:
>> http://tmsearch.uspto.gov/bin/showfield?f=doc&state=4804:rx7o71.2.7
> No, most links from the USPTO website don't work, sadly.  I've updated
> the trademark docs to note the only reliable way to share a link there:
>
>   https://www.apache.org/foundation/marks/naming#regsearch
>
> Click through to a specific trademark page, then click the TSDR blue
> button, which provides a stable URL, like this for sparkling wine:
>
> https://tsdr.uspto.gov/#caseNumber=87442162&caseType=SERIAL_NO&searchType=statusSearch
Thanks.  Next time I'll do a PDF to at least try and capture the data.

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: [VOTE] Recommend 'Apache SkyWalking graduation to Top LevelProject' resolution to board

[Kevin A. McGrail]

I am +1 (binding) contingent on the current release being added back and
Dave/Sebb are happy with your incorrect releases being removed.
--
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


On Fri, Mar 22, 2019 at 6:44 PM sebb  wrote:

> On Fri, 22 Mar 2019 at 16:41, 吴晟 Sheng Wu  wrote:
> >
> > Hi Dave
> >
> >
> > Thanks for the remind.
> > I just removed all releases from a.o/dist[1], and checked all of them
> exist in archive.a.o[2].
>
> Did you really intend to remove the current release as well?
>
> That does not seem right; the current release is normally left until
> the TLP makes its first release.
>
> Also the download page needs to be updated to use the archive server
> for the *old* releases (6.0.0-beta and 6.0.0-alpha).
> [These should already have been removed from dist and the links
> changed to point to the archive server when 6.0.0-GA was released]
>
> >
> > [1] https://www.apache.org/dist/incubator/skywalking/
> > [2] http://archive.apache.org/dist/incubator/skywalking/
> >
> >
> > --
> > Sheng Wu
> > Apache SkyWalking, ShardingSphere, Zipkin
> > Twitter, wusheng1108
> >
> >
> >
> >
> >
> >
> >
> > -- Original --
> > From:  "Dave Fisher";
> > Date:  Fri, Mar 22, 2019 07:55 AM
> > To:  "general";
> >
> > Subject:  Re: [VOTE] Recommend 'Apache SkyWalking graduation to Top
> LevelProject' resolution to board
> >
> >
> >
> > +1 (binding)
> >
> > If you look at the new
> https://incubator.apache.org/clutch/skywalking.html <
> https://incubator.apache.org/clutch/skywalking.html> analysis you will
> see activity in all repositories and that
> https://skywalking.apache.org/downloads/ <
> https://skywalking.apache.org/downloads/> corresponds to the list on the
> clutch analysis.
> >
> > I’ll note that only current releases on supported versions should be on
> the distribution area. Older releases should be referenced from
> archives.apache.org <http://archives.apache.org/> - here I am referring
> to the RC, Beta, and Alpha releases. Please take care of this.
> >
> > I don’t view this as blocking since as a TLP the policy is the same.
> >
> > Regards,
> > Dave
> >
> > > On Mar 18, 2019, at 10:21 PM, Mick Semb Wever  wrote:
> > >
> > >
> > >
> > > After the latest discussion amongst this dev community on this dev
> mailing list[1],  presenting Sheng Wu as the PMC Chair and the maturity
> model[2], and then the discussion again on the incubator list[3],  a vote
> for Apache SkyWalking graduating to a top level project was called and has
> passed[4]. From the past incubator discussions the PPMC altered the draft
> graduation proposal, specifically the proposed PMC list: removing some
> inactive people and adding all the podling Committers.
> > >
> > >
> > > Apache SkyWalking entered the incubator on December of 2017.
> SkyWalking has delivered 8 releases so far in total, and now shows a good
> cadence of successful releases.
> > >
> > > During the podling's time in the Apache Incubator there has been
> > > 3200+ commits on development of the project,
> > >  378 Issues tagged as question in GitHub created, 373 resolved,
> > >  850+ Pull request created and resolved,
> > >  97 different contributors,
> > >9 elected new committers, and
> > >3 elected new PPMC members.
> > >
> > > And the dev ML has had 72 participants:
> https://lists.apache.org/trends.html?d...@skywalking.apache.org:2019
> > >
> > > Attached is the draft Resolution for the PPMC and IPMC to vote upon.
> > >
> > > Please take a minute to vote on whether or not Apache SkyWalking should
> > > graduate to a Top Level Project by responding with one of the
> following:
> > >
> > > [ ] +1 Apache SkyWalking should graduate.
> > > [ ] +0 No opinion
> > > [ ] -1 Apache SkyWalking should not graduate (please provide the
> reason)
> > >
> > > The VOTE is open for a minimum of 72 hours. As there has been previous
> discussions on past versions of this proposal, I have not preluded the vote
> with a DISCUSS email. If feedback arises the vote period will be extended
> in good faith.
> > >
> > > regards,
> > > Mick
> > >
> > >
> > > [1]
> https://lists.apache.org/thread.html/9

Re: [VOTE] Recommend 'Apache SkyWalking graduation to Top LevelProject' resolution to board

[Kevin A. McGrail]

ered 8 releases so far in total, and now shows a good cadence of 
>>>> successful releases.
>>>>
>>>> During the podling's time in the Apache Incubator there has been
>>>> 3200+ commits on development of the project,
>>>>  378 Issues tagged as question in GitHub created, 373 resolved,
>>>>  850+ Pull request created and resolved,
>>>>  97 different contributors,
>>>>9 elected new committers, and
>>>>3 elected new PPMC members.
>>>>
>>>> And the dev ML has had 72 participants: 
>>>> https://lists.apache.org/trends.html?d...@skywalking.apache.org:2019
>>>>
>>>> Attached is the draft Resolution for the PPMC and IPMC to vote upon.
>>>>
>>>> Please take a minute to vote on whether or not Apache SkyWalking should
>>>> graduate to a Top Level Project by responding with one of the following:
>>>>
>>>> [ ] +1 Apache SkyWalking should graduate.
>>>> [ ] +0 No opinion
>>>> [ ] -1 Apache SkyWalking should not graduate (please provide the reason)
>>>>
>>>> The VOTE is open for a minimum of 72 hours. As there has been previous 
>>>> discussions on past versions of this proposal, I have not preluded the 
>>>> vote with a DISCUSS email. If feedback arises the vote period will be 
>>>> extended in good faith.
>>>>
>>>> regards,
>>>> Mick
>>>>
>>>>
>>>> [1] 
>>>> https://lists.apache.org/thread.html/9aab116a5df46d10a655bbf243f525260bad7763f6f65bce19ec33bd@%3Cdev.skywalking.apache.org%3E
>>>> [2] 
>>>> https://cwiki.apache.org/confluence/display/SKYWALKING/Apache+Maturity+Model+Assessment+for+SkyWalking
>>>> [3] 
>>>> https://lists.apache.org/thread.html/68b06b2efdcd4f519cd9aa3df55d46bf0dade28002065fbad75d4195@%3Cdev.skywalking.apache.org%3E
>>>> [4] 
>>>> https://lists.apache.org/thread.html/9f05862dffb40a967f867ba0fee4ab8549b08736cde27571e303ab30@%3Cdev.skywalking.apache.org%3E
>>>>
>>>> 
>>>>
>>>>
>>>> Establish the Apache SkyWalking 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 application performance management and monitoring (APM).
>>>>
>>>> NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
>>>> (PMC), to be known as the "Apache SkyWalking Project", be and hereby is
>>>> established pursuant to Bylaws of the Foundation; and be it further
>>>>
>>>> RESOLVED, that the Apache SkyWalking Project be and hereby is
>>>> responsible for the creation and maintenance of software related to
>>>> application performance management and monitoring (APM); and
>>>> be it further
>>>>
>>>> RESOLVED, that the office of "Vice President, Apache SkyWalking" 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
>>>> SkyWalking Project, and to have primary responsibility for management of
>>>> the projects within the scope of responsibility of the Apache SkyWalking
>>>> 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 SkyWalking
>>>> Project:
>>>>
>>>>  * Haoyang Liu  (??)  
>>>>  * Hongtao Gao  (??)  
>>>>  * Ignasi Barrera  
>>>>  * Mick Semb Wever 
>>>>  * Sheng Wu  ()  
>>>>  * Shinn Zhang  ()   
>>>>  * Willem Ning Jiang  ()
>>>>  * Yongsheng Peng  (??)   
>>>>  * DongXue Si (??)
>>>>  * Jian Tan ()       
>>>>  * Kai Wang ()   
>>>>  * Yang Bai ()   
>>>>  * Yao Wang ()   
>>>>  * Zhang Kewei (??) 

Re: Incubator Wiki spring clean

[Kevin A. McGrail]

Nice work.

On Sun, Apr 21, 2019, 20:14 Justin Mclean  wrote:

> Hi,
>
> I’ve went through and organised teh incubator wiki a little;
> - Reports page have been organised user [1]. Some are missing I’ve raise
> an INFRA JIRA for this.
> - A lot off pages can be deleted I’ve moved these to “To Delete” [2]
> - People have been moved to [3]. I think the majority of these can be
> deleted.
> - Pages of historical interest I’ve moved to here [4]
> - Proposals I’ve moved to here [5]
> - I’ve updated the front page to remove outdated information and fix the
> report table but more could be done here.
>
> It still needs a little clean up. If anyone notices any other missing
> pages please speak up. Please feel free to update or point out anything
> that is duplicated elsewhere or is out of date.
>
> Thanks,
> Justin
>
> 1. https://cwiki.apache.org/confluence/display/INCUBATOR/Reports
> 2,.https://cwiki.apache.org/confluence/display/INCUBATOR/To+Delete
> 3. https://cwiki.apache.org/confluence/display/INCUBATOR/People
> 4.
> https://cwiki.apache.org/confluence/display/INCUBATOR/Historical+Interest
> 5. https://cwiki.apache.org/confluence/display/INCUBATOR/Proposals
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Draft Incubator report for May

[Kevin A. McGrail]

On 5/7/2019 7:50 PM, Nick Kew wrote:
>> On 5 May 2019, at 23:21, Justin Mclean  wrote:
>>
>> 1. https://cwiki.apache.org/confluence/display/INCUBATOR/May2019
> Anyone else having trouble with that?
>
> I can see it from here, but I was unable to log in.  Tried a password reset,
> whereupon I'm no longer permitted even to view the report on the browser
> that's logged in!
>
The new cwiki is tied into ASF LDAP. Use your committer username and
password.  I did not have trouble with it.

Regards,

KAM

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: General@ Moderation

[Kevin A. McGrail]

There is a group that does moderation for a few lists using a Google
shared inbox.

It might be a good avenue to pursue instead of rolling our own.  They
handle fundraising's moderation, for example as well as trademarks.

Email mod-priv...@gsuite.cloud.apache.org if interested.

I think we could create a moderation PMC and try and centralize this
foundation wide as well.

On 5/8/2019 10:39 AM, Dave Fisher wrote:
> Hi -
>
> It looks like we need two or three new volunteers to help moderate this 
> mailing list. Many of the five moderators are not very active in the 
> incubator at this time.
>
> (I’d volunteer, but I’m currently moderating some 22 lists…)
>
> Regards,
> Dave
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: Incubator Proposal

[Kevin A. McGrail]

On 5/8/2019 11:31 AM, Matthew Houston wrote:
> At the end, the intention in the initial use case is to equate three
> scriptures to Aramaic, and in so doing eliminate a large portion of Al
> Qaida's ability to recruit.

I'm afraid that this would disqualify me from supporting this proposal
not because it's a bad idea but because it's not compatible with the
mission of an apolitical NPO like the ASF.

Regards,
KAM

-- 
Kevin A. McGrail
Member, Apache Software Foundation
Chair Emeritus Apache SpamAssassin Project
https://www.linkedin.com/in/kmcgrail - 703.798.0171


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

Re: Missing Mentors

[Kevin A. McGrail]

I am twice on the report of I am one of the 13.  I can't figure out how to
read this report very well.

On Thu, May 9, 2019, 23:33 Justin Mclean  wrote:

> Hi,
>
> A while back we went though the process of identifying missing mentors and
> t was discussion that there a good correlation between not signing off
> reports and being missing. Whimsey has a page that tracks this [1].
>
> From  [1] I can see a number of mentors that have not been signing off
> reports. Do people think it time to ask those mentor who are not being
> active to either become more involved or step down?
>
> The good news is that with some mentors standing down (who appear on that
> list), and some projects graduating there’s only only 13 mentors I’ve
> identified that we need to check if they still want to continue or have the
> time to help their podling out. That’s huge improvement over last time.
>
> There also seems to be another (slightly weaker correlation) that more
> than 1/2 of these people have not signed up to the podlings private list.
> Now mails can be read on list.apache.org but that’s probably another good
> indicator along with not signing or reports and not checking releases.
>
> Thanks,
> Justin
>
>
> 1. https://whimsy.apache.org/incubator/signoff.cgi
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>