Re: [RESULT] [VOTE] Accept TubeMQ into the Apache Incubator

[Justin Mclean]

Hi,

> Can you point me where are the instructions to set up podling.xml?

It in the mentor section [1]


> I didn’t find any details here:
> http://incubator.apache.org/cookbook/#podling_infrastructure_setup. 

Cookbook is a fairly need page and doesn’t;t include everything.

Thanks,
Justin

1. http://incubator.apache.org/guides/mentor.html#add_to_incubation_summary_file
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [RESULT] [VOTE] Accept TubeMQ into the Apache Incubator

[俊平堵]

Thanks Justin for reminding on this.
Can you point me where are the instructions to set up podling.xml? I didn't
find any details here:
http://incubator.apache.org/cookbook/#podling_infrastructure_setup. Do I
miss something?

Thanks,

Junping

Justin Mclean  于2019年12月12日周四 上午7:01写道：

> Hi,
>
> > Looks like infra/resource hasn't been setup for TubeMQ. I just open
> > https://jira.apache.org/jira/browse/INFRA-19549
>
> The podling needs to exist in the podling.xml file first, before the LDAP
> and DNS can be created.
>
> Thanks,
> Justin

Re: [RESULT] [VOTE] Accept TubeMQ into the Apache Incubator

[Justin Mclean]

Hi,

> Looks like infra/resource hasn't been setup for TubeMQ. I just open
> https://jira.apache.org/jira/browse/INFRA-19549

The podling needs to exist in the podling.xml file first, before the LDAP and 
DNS can be created.

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

Re: [DISCUSS] YuniKorn Proposal

[Felix Cheung]

+1 ;)


On Wed, Dec 11, 2019 at 12:08 PM Dave Fisher  wrote:

> Hi -
>
> Very interesting proposal. +1.
>
> Please note that two of your nominated mentors will need to ask to join
> the IPMC by request at private@i.a.o
>
> Regards,
> Dave
>
> > On Dec 11, 2019, at 11:50 AM, Weiwei Yang  wrote:
> >
> > Greetings folks:
> >
> > Please consider the following proposal, which is also on the wiki
> > 
> > [1].
> > I look forward to hearing feedback from you.
> >
> >
> > *YuniKorn - An Unified Resource Scheduler*
> >
> > 1. Abstract
> > YuniKorn is a standalone resource scheduler responsible for scheduling
> > batch jobs and long-running services on large scale distributed systems
> > running in on-premises environments as well as different public clouds.
> >
> > 2. Proposal
> > YuniKorn ['ju:nikɔ:n] is a unified resource scheduler aiming to achieve
> > fine-grained resource sharing for various workloads efficiently on a
> large
> > scale, multi-tenant and cloud-native environments. YuniKorn brings a
> > unified, cross-platform scheduling experience for mixed workloads, with
> > support for but not limited to, Apache™ Hadoop® YARN and Kubernetes.
> >
> > Currently, YuniKorn is an open-source project with Apache 2.0 license.
> The
> > source code is hosted as a git-repo under the github.com/cloudera
> domain.
> > We would like to share it with the ASF and expand the community to a
> wider
> > range of users and contributors.
> >
> > 2.1 Background
> > Enterprise users run their workloads on different platforms such as
> Apache™
> > Hadoop® YARN and Kubernetes. They need to work with different resource
> > schedulers in order to plan their workloads to run on these platforms
> > efficiently. The scheduler implementations are fragmented, and not
> > optimized to balance existing use-cases like batch workloads along with
> new
> > needs such as cloud-native architecture, autoscaling, etc. We need a
> single
> > resource planning/management framework to manage resources on different
> > platforms using the same semantics, in order to address all the important
> > resource management requirements.
> >
> > 2.2 Rationale
> > There is no solution that exists now to address the needs of having a
> > unified resource scheduling experiences across platforms. That makes it
> > difficult to manage workloads running on different environments, from
> > on-premise to Cloud. YuniKorn aims to satisfy these needs. YuniKorn is
> > designed around the following principles:
> >
> > 1) Support different environments
> > As the compute platforms are evolving quickly, there are more and more
> > challenges appear in on-prem, cloud or hybrid environments. YuniKorn aims
> > to bring unified scheduling experiences across multiple environments with
> > enhanced scheduling capabilities.
> >
> > 2) Support extensive types of workloads
> > To improve the efficiency of the computing platform, a key idea is to run
> > different types of applications, like long-running services and batch
> jobs,
> > on shared resources. YuniKorn is an effort to address all the scheduling
> > features needed for such mixed workload environments.
> >
> > 3) Benefit both big-data and cloud-native communities
> > A resource scheduler needs to be capable of supporting mixed workloads,
> > both batch, and long-running services. This is the key to improving
> cluster
> > utilization, and to reduce the complexity of dev-ops. By creating a
> common
> > scheduler that is decoupled from the container platforms underneath, it
> can
> > benefit both Apache™ Hadoop® YARN and the Kubernetes communities.
> >
> > 2.3 Initial Goals
> > Initial goals are:
> > - Move the existing codebase, documentation to Apache hosted repo
> > - Set up mailing lists, website, CI/CD pipeline under Apache
> infrastructure
> > - Setup JIRA for issue tracking
> > - Incremental development and releases according to Apache guidelines
> > - Expand the community and bring more diversified contributors/users to
> > the community
> >
> > 2.4 Current Status
> >
> > 2.4.1 Meritocracy
> > Many of the initial developers of YuniKorn are already Apache committers
> > and PMC members from other Apache projects, such as Apache Hadoop and
> > Apache Submarine. Many of us have worked in the Apache Hadoop community
> for
> > years and know the Apache way well. We believe strongly in meritocracy in
> > electing committers and PMC members. We believe that contributions can
> come
> > in forms other than just code: for example, one of our initial proposed
> > committers has contributed solely in the area of project documentation.
> We
> > will encourage contributions and participation of all types, and ensure
> > that contributors are appropriately recognized.
> >
> > 2.4.2 Community
> > YuniKorn is a relatively new open source project, Cloudera is the
> original
> > development sponsor for YuniKorn. From the beginning of the project
> itself,
> > we 

Re: [DISCUSS] YuniKorn Proposal

[Dave Fisher]

Hi -

Very interesting proposal. +1.

Please note that two of your nominated mentors will need to ask to join the 
IPMC by request at private@i.a.o

Regards,
Dave

> On Dec 11, 2019, at 11:50 AM, Weiwei Yang  wrote:
> 
> Greetings folks:
> 
> Please consider the following proposal, which is also on the wiki
> 
> [1].
> I look forward to hearing feedback from you.
> 
> 
> *YuniKorn - An Unified Resource Scheduler*
> 
> 1. Abstract
> YuniKorn is a standalone resource scheduler responsible for scheduling
> batch jobs and long-running services on large scale distributed systems
> running in on-premises environments as well as different public clouds.
> 
> 2. Proposal
> YuniKorn ['ju:nikɔ:n] is a unified resource scheduler aiming to achieve
> fine-grained resource sharing for various workloads efficiently on a large
> scale, multi-tenant and cloud-native environments. YuniKorn brings a
> unified, cross-platform scheduling experience for mixed workloads, with
> support for but not limited to, Apache™ Hadoop® YARN and Kubernetes.
> 
> Currently, YuniKorn is an open-source project with Apache 2.0 license. The
> source code is hosted as a git-repo under the github.com/cloudera domain.
> We would like to share it with the ASF and expand the community to a wider
> range of users and contributors.
> 
> 2.1 Background
> Enterprise users run their workloads on different platforms such as Apache™
> Hadoop® YARN and Kubernetes. They need to work with different resource
> schedulers in order to plan their workloads to run on these platforms
> efficiently. The scheduler implementations are fragmented, and not
> optimized to balance existing use-cases like batch workloads along with new
> needs such as cloud-native architecture, autoscaling, etc. We need a single
> resource planning/management framework to manage resources on different
> platforms using the same semantics, in order to address all the important
> resource management requirements.
> 
> 2.2 Rationale
> There is no solution that exists now to address the needs of having a
> unified resource scheduling experiences across platforms. That makes it
> difficult to manage workloads running on different environments, from
> on-premise to Cloud. YuniKorn aims to satisfy these needs. YuniKorn is
> designed around the following principles:
> 
> 1) Support different environments
> As the compute platforms are evolving quickly, there are more and more
> challenges appear in on-prem, cloud or hybrid environments. YuniKorn aims
> to bring unified scheduling experiences across multiple environments with
> enhanced scheduling capabilities.
> 
> 2) Support extensive types of workloads
> To improve the efficiency of the computing platform, a key idea is to run
> different types of applications, like long-running services and batch jobs,
> on shared resources. YuniKorn is an effort to address all the scheduling
> features needed for such mixed workload environments.
> 
> 3) Benefit both big-data and cloud-native communities
> A resource scheduler needs to be capable of supporting mixed workloads,
> both batch, and long-running services. This is the key to improving cluster
> utilization, and to reduce the complexity of dev-ops. By creating a common
> scheduler that is decoupled from the container platforms underneath, it can
> benefit both Apache™ Hadoop® YARN and the Kubernetes communities.
> 
> 2.3 Initial Goals
> Initial goals are:
> - Move the existing codebase, documentation to Apache hosted repo
> - Set up mailing lists, website, CI/CD pipeline under Apache infrastructure
> - Setup JIRA for issue tracking
> - Incremental development and releases according to Apache guidelines
> - Expand the community and bring more diversified contributors/users to
> the community
> 
> 2.4 Current Status
> 
> 2.4.1 Meritocracy
> Many of the initial developers of YuniKorn are already Apache committers
> and PMC members from other Apache projects, such as Apache Hadoop and
> Apache Submarine. Many of us have worked in the Apache Hadoop community for
> years and know the Apache way well. We believe strongly in meritocracy in
> electing committers and PMC members. We believe that contributions can come
> in forms other than just code: for example, one of our initial proposed
> committers has contributed solely in the area of project documentation. We
> will encourage contributions and participation of all types, and ensure
> that contributors are appropriately recognized.
> 
> 2.4.2 Community
> YuniKorn is a relatively new open source project, Cloudera is the original
> development sponsor for YuniKorn. From the beginning of the project itself,
> we had clearly aimed to have this as an open-source project, so we started
> to build the community from the very early stages. We received a lot of
> feedback and valuable suggestions from other community members while the
> project was hosted as an open-source project on GitHub. 

[DISCUSS] YuniKorn Proposal

[Weiwei Yang]

Greetings folks:

Please consider the following proposal, which is also on the wiki

 [1].
I look forward to hearing feedback from you.


*YuniKorn - An Unified Resource Scheduler*

1. Abstract
YuniKorn is a standalone resource scheduler responsible for scheduling
batch jobs and long-running services on large scale distributed systems
running in on-premises environments as well as different public clouds.

2. Proposal
YuniKorn ['ju:nikɔ:n] is a unified resource scheduler aiming to achieve
fine-grained resource sharing for various workloads efficiently on a large
scale, multi-tenant and cloud-native environments. YuniKorn brings a
unified, cross-platform scheduling experience for mixed workloads, with
support for but not limited to, Apache™ Hadoop® YARN and Kubernetes.

Currently, YuniKorn is an open-source project with Apache 2.0 license. The
source code is hosted as a git-repo under the github.com/cloudera domain.
We would like to share it with the ASF and expand the community to a wider
range of users and contributors.

2.1 Background
Enterprise users run their workloads on different platforms such as Apache™
Hadoop® YARN and Kubernetes. They need to work with different resource
schedulers in order to plan their workloads to run on these platforms
efficiently. The scheduler implementations are fragmented, and not
optimized to balance existing use-cases like batch workloads along with new
needs such as cloud-native architecture, autoscaling, etc. We need a single
resource planning/management framework to manage resources on different
platforms using the same semantics, in order to address all the important
resource management requirements.

2.2 Rationale
There is no solution that exists now to address the needs of having a
unified resource scheduling experiences across platforms. That makes it
difficult to manage workloads running on different environments, from
on-premise to Cloud. YuniKorn aims to satisfy these needs. YuniKorn is
designed around the following principles:

1) Support different environments
As the compute platforms are evolving quickly, there are more and more
challenges appear in on-prem, cloud or hybrid environments. YuniKorn aims
to bring unified scheduling experiences across multiple environments with
enhanced scheduling capabilities.

2) Support extensive types of workloads
To improve the efficiency of the computing platform, a key idea is to run
different types of applications, like long-running services and batch jobs,
on shared resources. YuniKorn is an effort to address all the scheduling
features needed for such mixed workload environments.

3) Benefit both big-data and cloud-native communities
A resource scheduler needs to be capable of supporting mixed workloads,
both batch, and long-running services. This is the key to improving cluster
utilization, and to reduce the complexity of dev-ops. By creating a common
scheduler that is decoupled from the container platforms underneath, it can
benefit both Apache™ Hadoop® YARN and the Kubernetes communities.

2.3 Initial Goals
Initial goals are:
 - Move the existing codebase, documentation to Apache hosted repo
 - Set up mailing lists, website, CI/CD pipeline under Apache infrastructure
 - Setup JIRA for issue tracking
 - Incremental development and releases according to Apache guidelines
 - Expand the community and bring more diversified contributors/users to
the community

2.4 Current Status

2.4.1 Meritocracy
Many of the initial developers of YuniKorn are already Apache committers
and PMC members from other Apache projects, such as Apache Hadoop and
Apache Submarine. Many of us have worked in the Apache Hadoop community for
years and know the Apache way well. We believe strongly in meritocracy in
electing committers and PMC members. We believe that contributions can come
in forms other than just code: for example, one of our initial proposed
committers has contributed solely in the area of project documentation. We
will encourage contributions and participation of all types, and ensure
that contributors are appropriately recognized.

2.4.2 Community
YuniKorn is a relatively new open source project, Cloudera is the original
development sponsor for YuniKorn. From the beginning of the project itself,
we had clearly aimed to have this as an open-source project, so we started
to build the community from the very early stages. We received a lot of
feedback and valuable suggestions from other community members while the
project was hosted as an open-source project on GitHub. This feedback has
greatly influenced some of our designs. For e.g, developers from Alibaba
had been involved in the very early stage of development, lots of effort
related to performance/throughput enhancement were contributed by them.
Lots of other organizations further showed their interest to join the
community once we started talking about it in meetups, conferences, etc.

2.4.3 Core 

Re: [Vote] Release Apache IoTDB 0.8.2

[Kevin A. McGrail]

I vote +1 binding as well.

+1 (binding)

I checked the same with one exception:
- Incubating in the name of source and binary kit
- DISCLAIMER exists
- LICENSE and NOTICE are fine
- No unexpected binary files
- Checked PGP signatures
- Checked Checksums
- I used the binaries for testing.

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, Dec 11, 2019 at 6:30 AM Willem Jiang  wrote:

> +1 (binding)
>
> I checked
> - Incubating in the name of source and binary kit
> - DISCLAIMER exists
> - LICENSE and NOTICE are fine
> - No unexpected binary files
> - Checked PGP signatures
> - Checked Checksums
> - Build the source without any issue
>
> Willem Jiang
>
> Twitter: willemjiang
> Weibo: 姜宁willem
>
> On Sun, Dec 8, 2019 at 10:10 PM Xiangdong Huang 
> wrote:
> >
> > Hello all,
> >
> > This is a call for vote to release Apache IoTDB (Incubating) version
> 0.8.2,
> > which is a bug fix version of 0.8.1.
> >
> > The Apache IoTDB community has voted on and approved a proposal to
> release
> > Apache IoTDB (Incubating) version 0.8.2.
> >
> > We now kindly request the Incubator PMC members review and vote on this
> > incubator release.
> >
> > Apache IoTDB (incubating) (Database for Internet of Things) is an
> > integrated data management engine designed for timeseries data. It
> provides
> > users with services for data collection, storage and analysis.
> >
> > IoTDB community vote and result thread:
> > Result:
> >
> https://lists.apache.org/thread.html/918d52d0fd306aa92b9ad3f0510611e73dc843d65c6747bd28c6a143%40%3Cdev.iotdb.apache.org%3E
> > Vote:
> >
> https://lists.apache.org/thread.html/dadba801d3e72b97d997d17470bcf98bdfd217cde14434c8db847ca4%40%3Cdev.iotdb.apache.org%3E
> >
> > The release candidates (RC2):
> > https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.2/rc2
> >
> > Git tag for the release (RC2):
> > https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.8.2
> >
> > Hash for the release tag:
> > 09a94f2c02dec27f483a2ccb41a8265331be193d
> >
> > Release Notes:
> >
> https://github.com/apache/incubator-iotdb/blob/release/0.8.2/RELEASE_NOTES.md
> >
> > The artifacts have been signed with Key : 2206EF8F64C35889, which can be
> >
> > found in the keys file:
> > https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
> >
> > Look at here for how to verify this release candidate:
> >
> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
> >
> > The vote will be open for at least 72 hours.
> >
> >
> > From the PPMC Vote we carry over 1 binding IPMC Votes:
> >
> > +1 from Justin Mclean
> >
> > The vote will be passed if there is more than 2 +1 votes (except for
> Justin
> > Mclean)  and no -1 votes.
> >
> > Look forward to all IPMCs' vote for it.
> >
> > Please vote accordingly:
> > [ ] +1 approve
> > [ ] +0 no opinion
> > [ ] -1 disapprove with the reason
> >
> > Yours Sincerely,
> > Xiangdong Huang
> > Apache IoTDB (incubating)
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] Recommend 'Apache Druid graduation to Top Level Project' resolution to the board

[Woonsan Ko]

+1 (binding)

Regards,

Woonsan

On Sat, Dec 7, 2019 at 4:55 PM Gian Merlino  wrote:
>
> Earlier this year, Druid voted to graduate to a top level project. The vote
> passed in the Druid community and the Incubator, and a resolution was
> submitted to the Board, but needed to be shelved at the last minute. We are
> now ready to proceed to graduation once again, and so I would like to call
> another vote. The Druid project has re-voted and has notified the Board of
> these developments. We now seek consent from the Incubator community to
> propose a graduation resolution for the Dec 18 board meeting.
>
> The proposed graduation resolution is nearly the same as last time; the
> only changes are the addition of four new initial members (fokko, furkan,
> qmm, and vogievetsky).
>
> For reference,
>
> 1) The Druid vote that was just held:
> https://lists.apache.org/thread.html/3b1432780b8d841fffce3033cd5cc39fe1fe0f46feccb96f036dbf01%40%3Cdev.druid.apache.org%3E
>
> 2) Our prior Incubator graduation vote, which passed earlier this year:
> https://lists.apache.org/thread.html/19b703fdf192ddf8e31bda57264e03113c7e44b5954a56886e05@%3Cgeneral.incubator.apache.org%3E
>
> Please take a minute to vote on whether or not Apache Druid should graduate
> to a Top Level Project by responding with one of the following:
>
> [ ] +1 Apache Druid should graduate
> [ ]  0 No opinion
> [ ] -1 Apache Druid should not graduate because...
>
> The VOTE is open for a minimum of 72 hours.
>
> ---
>
> Establish Apache Druid 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 analytical database
> software, for distribution at no charge to the public.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "The Apache Druid Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that The Apache Druid Project be and hereby is
> responsible for the creation and maintenance of an analytical
> database software project; and be it further
>
> RESOLVED, that the office of "Vice President, Druid" 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
> Druid Project, and to have primary responsibility for
> management of the projects within the scope of responsibility of
> The Apache Druid 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 Druid Project:
>
>   * Benedict Jin (asdf2...@apache.org)
>   * Charles Allen(cral...@apache.org)
>   * Clint Wylie  (cwy...@apache.org)
>   * David Lim(david...@apache.org)
>   * Dylan Wylie  (dylanwy...@apache.org)
>   * Eric Tschetter   (ched...@apache.org)
>   * Fangjin Yang (f...@apache.org)
>   * Fokko Driesprong (fo...@apache.org)
>   * Furkan Kamaci(kam...@apache.org)
>   * Gian Merlino (g...@apache.org)
>   * Himanshu Gupta   (himans...@apache.org)
>   * Jihoon Son   (jihoon...@apache.org)
>   * Jonathan Wei (jon...@apache.org)
>   * Julian Hyde  (jh...@apache.org)
>   * Kurt Young   (k...@apache.org)
>   * Lijin Bin(binli...@apache.org)
>   * Maxime Beauchemin(maximebeauche...@apache.org)
>   * Mingming Qiu (q...@apache.org)
>   * Niketh Sabbineni (nik...@apache.org)
>   * Nishant Bangarwa (nish...@apache.org)
>   * P. Taylor Goetz  (ptgo...@apache.org)
>   * Parag Jain   (pja...@apache.org)
>   * Roman Leventov   (leven...@apache.org)
>   * Slim Bouguerra   (bs...@apache.org)
>   * Surekha Saharan  (sure...@apache.org)
>   * Xavier Léauté(x...@apache.org)
>   * Vadim Ogievetsky (vogievet...@apache.org)
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gian Merlino
> be and hereby is appointed to the office of Vice President,
> Druid, 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 Druid Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Druid podling; and be it further
>
> RESOLVED, that all responsibility pertaining to the Apache
> Incubator Druid podling encumbered upon the Apache Incubator
> PMC are hereafter discharged.

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

Re: [VOTE] Recommend 'Apache Druid graduation to Top Level Project' resolution to the board

[Willem Jiang]

+1 (binding)

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sun, Dec 8, 2019 at 5:55 AM Gian Merlino  wrote:
>
> Earlier this year, Druid voted to graduate to a top level project. The vote
> passed in the Druid community and the Incubator, and a resolution was
> submitted to the Board, but needed to be shelved at the last minute. We are
> now ready to proceed to graduation once again, and so I would like to call
> another vote. The Druid project has re-voted and has notified the Board of
> these developments. We now seek consent from the Incubator community to
> propose a graduation resolution for the Dec 18 board meeting.
>
> The proposed graduation resolution is nearly the same as last time; the
> only changes are the addition of four new initial members (fokko, furkan,
> qmm, and vogievetsky).
>
> For reference,
>
> 1) The Druid vote that was just held:
> https://lists.apache.org/thread.html/3b1432780b8d841fffce3033cd5cc39fe1fe0f46feccb96f036dbf01%40%3Cdev.druid.apache.org%3E
>
> 2) Our prior Incubator graduation vote, which passed earlier this year:
> https://lists.apache.org/thread.html/19b703fdf192ddf8e31bda57264e03113c7e44b5954a56886e05@%3Cgeneral.incubator.apache.org%3E
>
> Please take a minute to vote on whether or not Apache Druid should graduate
> to a Top Level Project by responding with one of the following:
>
> [ ] +1 Apache Druid should graduate
> [ ]  0 No opinion
> [ ] -1 Apache Druid should not graduate because...
>
> The VOTE is open for a minimum of 72 hours.
>
> ---
>
> Establish Apache Druid 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 analytical database
> software, for distribution at no charge to the public.
>
> NOW, THEREFORE, BE IT RESOLVED, that a Project Management
> Committee (PMC), to be known as the "The Apache Druid Project",
> be and hereby is established pursuant to Bylaws of the
> Foundation; and be it further
>
> RESOLVED, that The Apache Druid Project be and hereby is
> responsible for the creation and maintenance of an analytical
> database software project; and be it further
>
> RESOLVED, that the office of "Vice President, Druid" 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
> Druid Project, and to have primary responsibility for
> management of the projects within the scope of responsibility of
> The Apache Druid 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 Druid Project:
>
>   * Benedict Jin (asdf2...@apache.org)
>   * Charles Allen(cral...@apache.org)
>   * Clint Wylie  (cwy...@apache.org)
>   * David Lim(david...@apache.org)
>   * Dylan Wylie  (dylanwy...@apache.org)
>   * Eric Tschetter   (ched...@apache.org)
>   * Fangjin Yang (f...@apache.org)
>   * Fokko Driesprong (fo...@apache.org)
>   * Furkan Kamaci(kam...@apache.org)
>   * Gian Merlino (g...@apache.org)
>   * Himanshu Gupta   (himans...@apache.org)
>   * Jihoon Son   (jihoon...@apache.org)
>   * Jonathan Wei (jon...@apache.org)
>   * Julian Hyde  (jh...@apache.org)
>   * Kurt Young   (k...@apache.org)
>   * Lijin Bin(binli...@apache.org)
>   * Maxime Beauchemin(maximebeauche...@apache.org)
>   * Mingming Qiu (q...@apache.org)
>   * Niketh Sabbineni (nik...@apache.org)
>   * Nishant Bangarwa (nish...@apache.org)
>   * P. Taylor Goetz  (ptgo...@apache.org)
>   * Parag Jain   (pja...@apache.org)
>   * Roman Leventov   (leven...@apache.org)
>   * Slim Bouguerra   (bs...@apache.org)
>   * Surekha Saharan  (sure...@apache.org)
>   * Xavier Léauté(x...@apache.org)
>   * Vadim Ogievetsky (vogievet...@apache.org)
>
> NOW, THEREFORE, BE IT FURTHER RESOLVED, that Gian Merlino
> be and hereby is appointed to the office of Vice President,
> Druid, 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 Druid Project be and hereby
> is tasked with the migration and rationalization of the Apache
> Incubator Druid podling; and be it further
>
> RESOLVED, that all responsibility pertaining to the Apache
> Incubator Druid podling encumbered upon the Apache Incubator
> PMC are hereafter discharged.

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

Re: [Vote] Release Apache IoTDB 0.8.2

[Willem Jiang]

+1 (binding)

I checked
- Incubating in the name of source and binary kit
- DISCLAIMER exists
- LICENSE and NOTICE are fine
- No unexpected binary files
- Checked PGP signatures
- Checked Checksums
- Build the source without any issue

Willem Jiang

Twitter: willemjiang
Weibo: 姜宁willem

On Sun, Dec 8, 2019 at 10:10 PM Xiangdong Huang  wrote:
>
> Hello all,
>
> This is a call for vote to release Apache IoTDB (Incubating) version 0.8.2,
> which is a bug fix version of 0.8.1.
>
> The Apache IoTDB community has voted on and approved a proposal to release
> Apache IoTDB (Incubating) version 0.8.2.
>
> We now kindly request the Incubator PMC members review and vote on this
> incubator release.
>
> Apache IoTDB (incubating) (Database for Internet of Things) is an
> integrated data management engine designed for timeseries data. It provides
> users with services for data collection, storage and analysis.
>
> IoTDB community vote and result thread:
> Result:
> https://lists.apache.org/thread.html/918d52d0fd306aa92b9ad3f0510611e73dc843d65c6747bd28c6a143%40%3Cdev.iotdb.apache.org%3E
> Vote:
> https://lists.apache.org/thread.html/dadba801d3e72b97d997d17470bcf98bdfd217cde14434c8db847ca4%40%3Cdev.iotdb.apache.org%3E
>
> The release candidates (RC2):
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/0.8.2/rc2
>
> Git tag for the release (RC2):
> https://github.com/apache/incubator-iotdb/releases/tag/release%2F0.8.2
>
> Hash for the release tag:
> 09a94f2c02dec27f483a2ccb41a8265331be193d
>
> Release Notes:
> https://github.com/apache/incubator-iotdb/blob/release/0.8.2/RELEASE_NOTES.md
>
> The artifacts have been signed with Key : 2206EF8F64C35889, which can be
>
> found in the keys file:
> https://dist.apache.org/repos/dist/dev/incubator/iotdb/KEYS
>
> Look at here for how to verify this release candidate:
> https://cwiki.apache.org/confluence/display/IOTDB/Validating+a+staged+Release
>
> The vote will be open for at least 72 hours.
>
>
> From the PPMC Vote we carry over 1 binding IPMC Votes:
>
> +1 from Justin Mclean
>
> The vote will be passed if there is more than 2 +1 votes (except for Justin
> Mclean)  and no -1 votes.
>
> Look forward to all IPMCs' vote for it.
>
> Please vote accordingly:
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason
>
> Yours Sincerely,
> Xiangdong Huang
> Apache IoTDB (incubating)

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