[VOTE] Resolution to graduate Apache Impala to TLP

[Jim Apple]

The graduation of Impala to a TLP has been discussed[0] on dev@impala,
voted on[1] on dev@impala, and discussed[2] on general@incubator. All
threads were open 72 hours or more, and all seem to have quiesced.

This is a call for a VOTE to graduate Impala to a TLP. The draft resolution
is below. Please select from:

[ ] +1: Graduate Impala to a TLP
[ ] +-0: Neither graduate nor do not graduate Impala to a TLP
[ ] -1: Do NOT graduate Impala to a TLP, because ...



[0]: <
https://lists.apache.org/thread.html/2f5db4788aff9b0557354b9106c0328a29c1f90c1a74a228163949d2@%3Cdev.impala.apache.org%3E
>

[1]: <
https://lists.apache.org/thread.html/a5a7c6895b3e019347d6e4e4cf49d67d094d31b8f2c7b4d59200f3e4@%3Cdev.impala.apache.org%3E
>

[2]: <
https://lists.apache.org/thread.html/6b8598408f76a472532923c5a7fc510470b21671677ba3486568c57e@%3Cgeneral.incubator.apache.org%3E
>



Establish the Apache Impala Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to a high-performance distributed SQL engine.

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

RESOLVED, that the Apache Impala Project be and hereby is responsible
for the creation and maintenance of software related to a
high-performance distributed SQL engine; and be it further

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

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

* Alex Behm 
* Bharath Vissapragada 
* Brock Noland 
* Carl Steinbach 
* Casey Ching 
* Daniel Hecht 
* Dimitris Tsirogiannis 
* Henry Robinson 
* Ishaan Joshi 
* Jim Apple 
* John Russell 
* Juan Yu 
* Lars Volker 
* Lenni Kuff 
* Marcel Kornacker 
* Martin Grund 
* Matthew Jacobs 
* Michael Brown 
* Michael Ho 
* Sailesh Mukil 
* Skye Wanderman-Milne 
* Taras Bobrovytsky 
* Tim Armstrong 
* Todd Lipcon 

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

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

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

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

Re: Incubator wiki write access

[John D. Ament]

Added! Happy editing!

On Wed, Nov 8, 2017 at 10:31 PM mohit soni  wrote:

> I need write access to the incubator wiki to add a podling report for
> Myriad. Can I get karma/access for user "MohitSoni"?
>
> Thanks
>

Incubator wiki write access

[mohit soni]

I need write access to the incubator wiki to add a podling report for
Myriad. Can I get karma/access for user "MohitSoni"?

Thanks

RE: [DISCUSSION] Graduation of The (incubating) Apache Trafodion Project

[Liu, Ming (Ming)]

+1
Let's move forward.
I asked help @general@incubator.apache.org to vote on Release 2.2 , if 
Trafodion is TLP , it may attract more attention.

thanks,
Ming

-Original Message-
From: Selva Govindarajan [mailto:selva.govindara...@esgyn.com] 
Sent: Thursday, November 09, 2017 7:06 AM
To: d...@trafodion.incubator.apache.org
Subject: RE: [DISCUSSION] Graduation of The (incubating) Apache Trafodion 
Project

+1. 

Thanks a ton Pierre Smith for moving forward with the graduation process. 

Selva 

-Original Message-
From: Pierre Smits [mailto:pierre.sm...@gmail.com] 
Sent: Wednesday, November 8, 2017 2:13 PM
To: d...@trafodion.incubator.apache.org
Subject: [DISCUSSION] Graduation of The (incubating) Apache Trafodion Project

Hi all

Soon our 900th day incubating will pass. During the past period since our start 
in the incubator we - the community - have established an Apache project that 
has shown that:

   - its members collaborate to create software for the public good in
   accordance with the Apache Way;
   - it can produce releases of its main product in compliance with the
   requirements of the Apache Software foundation;
   - it operates independently of any external party or parties.

During the period we have seen our community grow, and any contributor willing 
to do more has submitted its iCLAs and completed details on the Contributor 
page in our WIKI [1]. Several of those contributors have accepted the 
invitation of the PPMC to join the our committer pool.

[1] https://cwiki.apache.org/confluence/display/TRAFODION/Contributors

At the moment the PPMC feels that our project has taken in everything it could 
benefit from being under the umbrella of the Apache Incubator Project. We wish 
to express our gratitude and respect to our Mentors (present and past) and any 
other Apache contributor that provided insights, viewpoints and guidance.

Now the time is upon all of us to look at the road ahead and way forward.
We, the PPMC, feel that our Apache Trafodion Project is ready to graduate from 
the incubator. A graduation process consists of following steps:

   1. a internal discussion on the path forward of our incubating Apache
   project and the proposed draft graduation resolution;
   2. vote within the incubating Apache project on the path forward (as per
   presented draft graduation process, when the internal discussion has come
   to its end);
   3. if 2 has a positive outcome: a discussion thread started in
   general@incubator.a.o with as subject and content the intent to graduate
   from the incubator and the draft graduation resolution of the incubating
   Apache Trafodion Project;
   4. If 3 has come to its end, call for a vote (within the
   general@incubator.a.o) on graduation of the Apache Trafodion Project
   with the draft graduation resolution as content;
   5. If the call for the vote in the general@incubator.a.o results in a) a
   quorum of binding votes participating in the vote, and b) the normal
   majority of that quorum expresses the +1 vote, then  the request to
   graduate (with the draft graduation resolution) will be brought before the
   Board of The Apache Software Foundation to have the Members of the Board to
   vote upon.


We therefore present you our draft graduation resolution below, and invite you 
to share your viewpoints and ask any question relating to its content and the 
graduation process as per item 1 of the list of steps presented above.

Please keep in mind: this draft graduation resolution will be the subject of a 
vote on graduation, which will be held:

   1. if and when the PPMC feels that the discussion has died down and a
   vote will gather a normal majority of voters expressing a +1;
   2. but not before the obligatory minimum period of 72 hrs has passed


*Draft graduation resolution of the (incubating) Apache Trafodion Project:*

Establish the Apache Trafodion 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 Apache 
Trafodion is a webscale SQL-on-Hadoop solution enabling transactional or 
operational workloads on Hadoop. Trafodion builds on the scalability, 
elasticity, and flexibility of Hadoop.
Trafodion extends Hadoop to provide guaranteed transactional integrity, 
enabling new kinds of big data applications to run on Hadoop.

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

RESOLVED, that the Apache Trafodion Project be and hereby is responsible for 
the creation and maintenance of software related to Apache Trafodion is a 
webscale SQL-on-Hadoop solution enabling transactional or operational workloads 
on 

RE: [VOTE] Apache Trafodion (incubating) release 2.2.0 RC 1

[Liu, Ming (Ming)]

Hello community,

Could anyone help to vote on this release request? We need your help to 
process. 
Really, Apache Trafodion (incubating) project is in request for your kindly 
help.

thanks,
Ming

-Original Message-
From: Liu, Ming (Ming) [mailto:ming@esgyn.cn] 
Sent: Monday, November 06, 2017 7:51 PM
To: general@incubator.apache.org
Subject: [VOTE] Apache Trafodion (incubating) release 2.2.0 RC 1

Hello ,

This is a call to vote on  Apache Trafodion (incubating)  release 2.2.0 RC1 
(Release Candidate 3)

Apache Trafodion is a webscale SQL-on-Hadoop solution enabling transactional or 
operational
workloads on Hadoop. Trafodion builds on the scalability,
elasticity, and flexibility of Hadoop. Trafodion extends Hadoop to provide 
guaranteed transactional
integrity, enabling new kinds of big data applications to run on Hadoop.

The Trafodion community has  voted and approved this release. Original email 
thread :
https://lists.apache.org/thread.html/836bff9c2a5c529223fdc17b82c21f47e4c6a02eee1a2a557a58cb9b@%3Cdev.trafodion.apache.org%3E


This is a major release and includes over 100 fixes and some important features.

The highlights are all documented here in the Release Notes : Trafodion 2.2 
Release Notes

They include :
  *   DTM enhancements by porting EsgynDB DTM changes to Trafodion
  *   jdbcT4 for publish to maven central
  *   Trafodion Elasticity enhancements
  *   LOB support in JDBC
  *   RMS enhancements
  *   100+ Bug fixes resolved

JIRA Release Notes :
Trafodion 2.2 JIRA Release Noteshttps://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318620=12338559>

GIT info:
The tag for this candidate is "2.2.0rc1". Git repository: git:// 
git.apache.org/incubator-trafodion.git

Release artifacts :
https://dist.apache.org/repos/dist/dev/incubator/trafodion/trafodion-2.2.0-RC1
Artifacts are signed with my key :  E1502B16  which is in 
https://dist.apache.org/repos/dist/release/incubator/trafodion/KEYS

Instructions :

Setting up build environment and building from source :
* 
https://cwiki.apache.org/confluence/display/TRAFODION/Create+Build+Environment
* https://cwiki.apache.org/confluence/display/TRAFODION/Build+Source

Installing Trafodion using convenience binaries:
* Follow requirements in Section 4 : 
http://trafodion.incubator.apache.org/docs/provisioning_guide/index.html#requirements
* Download Trafodion Binaries : 
http://trafodion.incubator.apache.org/docs/provisioning_guide/index.html#_download_binaries

* Ambari Install on HDP platform : 
http://trafodion.incubator.apache.org/docs/provisioning_guide/index.html#install-ambari
* Python Installer : 
http://trafodion.incubator.apache.org/docs/provisioning_guide/index.html#install



[ ] +1 approve

[ ] +0 no opinion

[ ] -1 disapprove (and reason why)

Vote will be open for at least 72 hours unless cancelled.

Thanks!

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

Re: [DRAFT] Incubator PMC Board Report - November 2017

[John D. Ament]

Hi,

Still missing sign off from: Guacamole and Ratis.  Please get these in
ASAP, to avoid being marked monthly (especially concerning for Guacamole
who's possibly graduating this month).

The following reports have not been filed, at this point I am assuming they
will be missed and roll over: iota (likely to retire), Milagro, Myriad
(also likely to retire).

John

On Mon, Nov 6, 2017 at 2:46 PM John D. Ament  wrote:

> All,
>
> Below is the current draft.  We have 7 podling reports missing/not signed
> off.  Hopefully they can come soon.
>
> Incubator PMC report for November 2017
>
> The Apache Incubator is the entry path into the ASF for projects and
> codebases wishing to become part of the Foundation's efforts.
>
> October was a quieter month in the incubator.  We executed 4 podling
> releases, had no changes in staff.  One new podling joined, and are having
> graduation discussions for two podlings.  We expect Mnemonic to fully
> graduate this month.
>
> * Community
>
>   New IPMC members:
>
>   - None
>
>   People who left the IPMC:
>
>   - None
>
> * New Podlings
>
>   - SDAP
>
> * Podlings that failed to report, expected next month
>
>
>
> * Graduations
>
>   The board has motions for the following:
>
>   - Guacamole?
>   - Impala?
>   - Mnemonic
>   - Your podling here?
>   - Your podling here?
>
> * Releases
>
>   The following releases entered distribution during the month of
>   October:
>
>   - 2017-10-04 Apache Juneau 6.4.0
>   - 2017-10-11 Apache Rya 3.2.11
>   - 2017-10-13 Apache Pulsar 1.20.0
>   - 2017-10-30 Apache MXNet 0.12.0
>
> * IP Clearance
>
>
>
> * Legal / Trademarks
>
>
>
> * Infrastructure
>
>
>
> * Miscellaneous
>
>
>
> * Credits
>
> --
>Table of Contents
> Amaterasu
> Daffodil
> Edgent
> Guacamole
> Heron
> Impala
> iota
> Joshua
> Milagro
> Myriad
> PageSpeed
> Ratis
> S2Graph
> Slider
> Tamaya
> Toree
> Unomi
>
> --
>
> 
> Amaterasu
>
> Apache Amaterasu is a framework providing continuous deployment for Big
> Data Pipelines.
>
> It provides the following capabilities:
>
> Continuous integration tools to package pipelines and run tests.
> A repository to store those packaged applications: the applications
> repository.
> A repository to store the pipelines, and engine configuration (for
> instance, the location of the Spark master, etc.): per environment - the
> configuration repository.
> A dashboard to monitor the pipelines.
> A DSL and integration hooks allowing third parties to easily integrate.
>
> Amaterasu has been incubating since 2017-09.
>
> Three most important issues to address in the move towards graduation:
>
>   1. Prepare the first release
>   2. Grow up user and contributor communities
>   3. Prepare documentation
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
>   None
>
> How has the community developed since the last report?
>
>   * Talks have been given in different events to promote and give
> visibility to Amaterasu
>
> How has the project developed since the last report?
>
>   * Code based was moved to the ASFs git box
>   * One new pull request was issued
>
> Date of last release:
>
>   N/A
>
> When were the last committers or PMC members elected?
>
>   N/A
>
>
>   [X] Initial setup
>   [ ] Working towards first release
>   [ ] Community building
>   [ ] Nearing graduation
>   [ ] Other:
>
> Date of last release:
>
>   N/A
>
> Signed-off-by:
>
>   [X](amaterasu) Jean-Baptiste Onofré
>  Comments:
>   [ ](amaterasu) Olivier Lamy
>  Comments:
>   [X](amaterasu) Davor Bonaci
>  Comments: Initial setup continues: codebase has moved to the ASF
> repository.
>
> IPMC/Shepherd notes:
>
>
>
> 
> Daffodil
>
> Apache Daffodil is an implementation of the Data Format Description
> Language
> (DFDL) used to convert between fixed format data and XML/JSON.
>
> Daffodil has been incubating since 2017-08-27.
>
> Three most important issues to address in the move towards graduation:
>
>   1. Obtaining SGAs
>   2. Establishing new apache-centric infrastructure
>   3. Broadening base of contributors
>
> Any issues that the Incubator PMC (IPMC) or ASF Board wish/need to be
> aware of?
>
> - Only that chasing the SGAs down is going to take some time, though
> this may be typical.
>
> How has the community developed since the last report?
>
> - Users: No change.
>
> - Developers/Contributors: No change.
>
> How has the project developed since the last report?
>
> - Completed setup of the git repo.
> - Started process of transfer of existing JIRA
> tickets to Apache.
> - Established our contributor/branch workflow and
> published to wiki.
> - Submitted Tresys SGA.
> - Progress is being made on obtaining organizational
> SGAs from NCSA and IBM.
>
> How would you assess the podling's maturity?
> Please feel 

Re: [RESULT]: [VOTE] Release 1.5 of NetBeans HTML/Java API

[Jaroslav Tulach]

OK, the bits are now in
https://dist.apache.org/repos/dist/release/incubator/netbeans/incubating-netbeans-html4j/
directory since revision 23014.

Since revision 23015 the files are removed from the
https://dist.apache.org/repos/dist/dev/incubator/netbeans/
directory.

The release 1.5 is out! Time to prepare 1.5.1...
-jt



2017-11-07 17:20 GMT+01:00 Bertrand Delacretaz :

> On Mon, Nov 6, 2017 at 4:54 PM, Jaroslav Tulach
>  wrote:
> > ...Does it still make sense to do official release of
> > version 1.5 or can we skip that?...
>
> IIUC the only thing left is to move that release under
> /dist/release/incubator/netbeans - I think you should do it to
> demonstrate the complete process.
>
> If you don't expect people to use that release it's fine to avoid
> "advertising" it.
>
> -Bertrand
>