Fwd: Looking for a Champion: FuzzyLite

[PJ Fanning]

Resending and including OP, just in case.

-- Forwarded message -
From: PJ Fanning 
Date: Tue, 20 Dec 2022 at 13:02
Subject: Re: Looking for a Champion: FuzzyLite
To: 


Thanks Juan for your interest in contributing this work to the ASF.

I have a question about whether there are any other people who have
contributed to FuzzyLite and if they would be interested in continuing
to contribute as part of a FuzzyLite PMC?

One of the most important aspects of an ASF project is building a community.

On Tue, 20 Dec 2022 at 08:29, Juan Rada-Vilela  wrote:
>
> Hi,
>
> I have created over the past years three projects: fuzzylite (C++),
> jfuzzylite (Java), and pyfuzzylite (Python), which are well designed and
> engineered libraries for fuzzy logic controllers, a field within Artificial
> Intelligence. Their repositories are in github.com/fuzzylite, and the home
> page is fuzzylite.com
>
> I am considering having them for incubation at Apache, so I am looking for
> a Champion to first find  if there is interest in the ASF, and maybe start
> with one?
>
> Kind regards,
>
> Juan.

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

Fwd: [VOTE] Accept StreamPark into the Apache Incubator

[tksonjk tk]

-1,  (non-binding)

Hmmm how does it differentiate to what StreamPipes does? Can you explain in
detail, thanks. and if you work for
a company, do you need to prove that this project is not company-related?


On 2022/08/24 03:55:26 tison wrote:
> Hi all,
>
> Following up on the [DISCUSS] thread on StreamPark[1], I would like to
call
> a VOTE to accept StreamPark into the Apache Incubator, please check out
the
> StreamPark Proposal from the incubator wiki[2].
>
> Please cast your vote:
>
> [ ] +1, bring StreamPark into the Incubator
> [ ] +0, I don't care either way
> [ ] -1, do not bring StreamPark into the Incubator, because...
>
> The vote will open at least for 72 hours, and only votes from the
Incubator
> PMC are binding, but votes from everyone are welcome.
>
> Best,
> tison.
>
> [1] https://lists.apache.org/thread/ns5n6ozl1mdvdbhmkfol67lt163m74v3
> [2]
> https://cwiki.apache.org/confluence/display/INCUBATOR/StreamPark+Proposal
>

[FWD] [VOTE] Graduate Apache MXNet (incubating) to a Top Level Project

[Joe Evans]

Hello Incubator Community,

After community discussions[1][2], the Apache MXNet (incubating) project is
currently having a community vote[3] to graduate to a top level project. We
welcome any feedback.

References:

[1] https://github.com/apache/incubator-mxnet/issues/20984

[2] https://lists.apache.org/thread/l9h2qgb2vqs2y0cm46wh83sgomr9w190

[3] https://lists.apache.org/thread/py1nw6whov78sch5kkm1gcg7cv3zb2sv


-- Forwarded message -
From: Joe Evans 
Date: Tue, Apr 26, 2022 at 1:56 PM
Subject: [VOTE] Graduate Apache MXNet (incubating) to a Top Level Project
To: 


Hi MXNet Community,

Apache MXNet (incubating) has been an incubating project since January,
2017. Since then, the project has matured and adopted the Apache Software
Foundation’s principles and philosophy around building and maintaining open
source software. There is a thriving community of developers and users from
all over the world that regularly contribute to the project.

Based on the positive responses in the graduation RFC[1] and discussion
thread[2], we would like to have a community vote on graduating MXNet to an
Apache Top Level project.

Here is a brief overview of the progress of the Apache MXNet (incubating)
project and community since entering the incubator:

Community

   -

   37 new PPMC members were added, bringing the total number of PPMC
   members to 50
   -

   56 new committers were added (which include new PPMC members), bringing
   the total number of committers to 87
   -

   The total number of contributors is now 870 and growing.

Project

   -

   18 releases[3] by 13 different release managers. All compliance issues
   have been resolved with the 1.9.0 and 2.0.beta releases.
   -

   MXNet website[4] is now compliant with Apache Project Website
   requirements[5]
   -

   MXNet has completed the project maturity self assessment[6]


Here is the proposed resolution:

—--

Establish the Apache MXNet 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 flexible and efficient library for Deep Learning.

NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee

(PMC), to be known as the "Apache MXNet Project", be and hereby is

established pursuant to Bylaws of the Foundation; and be it further

RESOLVED, that the Apache MXNet Project be and hereby is responsible for

the creation and maintenance of software related to a flexible and

efficient library for Deep Learning; and be it further

RESOLVED, that the office of "Vice President, Apache MXNet" 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 MXNet

Project, and to have primary responsibility for management of the

projects within the scope of responsibility of the Apache MXNet 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 MXNet Project:

* Anirudh Subramanian 

* Bing Xu 

* Bob Paulin 

* Carin Meier 

* Chiyuan Zhang 

* Chris Olivier 

* Dick Carter 

* Eric Xie 

* Furkan Kamaci 

* Haibin Lin 

* Henri Yandell 

* Hongliang Liu 

* Indhu Bharathi 

* Jackie Wu 

* Jason Dai 

* Jian Zhang 

* Joe Spisak 

* Jun Wu 

* Leonard Lausen 

* Liang Depeng 

* Ly Nguyen 

* Madan Jampani 

* Marco de Abreu 

* Markus Weimer 

* Mu Li 

* Nan Zhu 

* Naveen Swamy 

* Przemysław Trędak 

* Qiang Kou 

* Qing Lan 

* Sandeep Krishnamurthy 

* Sergey Kolychev 

* Sheng Zha 

* Shiwen Hu 

* Tao Lv 

* Terry Chen 

* Thomas Delteil 

* Tianqi Chen 

* Tong He 

* Tsuyoshi Ozawa 

* Xingjian Shi 

* YiZhi Liu 

* Yifeng Geng 

* Yu Zhang 

* Yuan Tang 

* Yutian Li 

* Zhi Zhang 

* Zihao Zheng 

* Ziheng Jiang 

* Ziyue Huang 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sheng Zha be appointed to

the office of Vice President, Apache MXNet, 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 MXNet Project be and hereby is tasked with the

migration and rationalization of the Apache Incubator MXNet podling; and

be it further

RESOLVED, that all responsibilities pertaining to the Apache Incubator

MXNet podling encumbered upon the Apache Incubator PMC are hereafter

Discharged.

—--

If this vote passes, our next step will be to start a graduation discussion
and subsequent vote on the general@incubator list.

Please vote on graduating Apache MXNet (incubating) as a Top Level 

Fwd: [VOTE]Release Apache Liminal (incubating) 0.0.4rc2-incubating

[Goson zhang]

Hi all:

See @sebb   mentioned that many project voting emails
have incorrect KEYS links, including our InLong project.

I think if there are so many duplicates of the same problem in
non-individual cases, it is likely that there is a need for improvement
somewhere, such as whether it needs to be emphasized in the novice
template, whether the Mentors or IPMCs of projects pay attention to this
problem, etc.

Perhaps,  it will be effective to resolve the question from the source.

FYI.

Thanks!

-- Forwarded message -
发件人： sebb 
Date: 2022年2月16日周三 00:41
Subject: Re: [VOTE]Release Apache Liminal (incubating) 0.0.4rc2-incubating
To: general 


On Tue, 15 Feb 2022 at 16:28, Lior Schachter  wrote:
>
> Hi All,
>
> We would like to vote on RC2 of version 0.0.4. The main purpose of V
> 0.0.4 is to provide a clear extensibility API for developers to add
> their own implementations of liminal abstractions - executor, task,
> image builder. In addition this version supports Apache Airflow 2.0.
>
> Liminal community vote and result threads:
> Vote:
> https://lists.apache.org/thread/1sw1zvyq45ozml09l7g2lhbdcd995lqw
>
> Result:
> https://lists.apache.org/thread/tcn3bmkc76hjx1f39p06xsq8jz9b2hgs
>
> Installation and testing instructions can be found in the README included.
>
> The release files, including signatures, digests, etc. can be found at:
>
>
https://dist.apache.org/repos/dist/dev/incubator/liminal/0.0.4rc2-INCUBATING/
>
> The tag to be voted on:
>
>
https://github.com/apache/incubator-liminal/releases/tag/0.0.4rc2-incubating
>
> The SHA512 Checksum for these artifacts is:
>
> apache-liminal-0.0.4rc2-incubating-source.tar.gz:
> BEC25A76 9E5C12BD F262FF95 3AE3E26D 8F19294C 16E45605 49F027F1
> 6A31ECC5 62BD7001 2E63D66B BEBBE319 D829FA04 B1051C1A DFC9A13D
> 6C861E62 5796B396
>
> Release artifacts are signed with the following key:
>
> https://dist.apache.org/repos/dist/dev/incubator/liminal/KEYS

Please don't use the above URL for KEYS in vote emails or download pages.

Use https://downloads.apache.org/incubator/liminal/KEYS instead.

The copy of KEYS at
https://dist.apache.org/repos/dist/dev/incubator/liminal/KEYS is
redundant.

It should be maintained instead at:
https://dist.apache.org/repos/dist/release/incubator/liminal/KEYS
(this is the source for downloads.apache.org)

> For more information about the contents of this release,
> see:https://issues.apache.org/jira/projects/LIMINAL/versions/12350079
>
> Please vote on releasing this package as Apache Liminal
> 0.0.4-INCUBATING. A majority of at least 3 +1 PMC votes are cast.
>
> [ ] +1 Release this package as Apache Liminal 0.0.4
> [ ] +0 No opinion
> [ ] -1 Do not release this package because ...
>
> Regards,
> Lior Schachter

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

Fwd: [VOTE] Release Apache Pegasus (Incubating) 2.2.0-RC0

[Yingchun Lai]

Gentle reminder for voting on Pegasus 2.2.0-RC0.

Best regards,
Yingchun Lai


-- Forwarded message -
发件人： Yingchun Lai 
Date: 2021年6月12日周六 下午7:38
Subject: [VOTE] Release Apache Pegasus (Incubating) 2.2.0-RC0
To: 


Hi, all

This is a call for a vote to release Apache Pegasus (Incubating) version
2.2.0-RC0.

Pegasus is a distributed key-value storage system that is designed
to be simple, horizontally scalable, strongly consistent, and
high-performance.

The Apache Pegasus community has voted on and approved a proposal to
release Apache Pegasus 2.2.0-RC0.
Apache Pegasus community vote thread:
https://lists.apache.org/thread.html/r5f045c9f82e67c01bc23504b66960fb07afdd72875b8e1c808a05e31%40%3Cdev.pegasus.apache.org%3EVote
Result thread:
https://lists.apache.org/thread.html/r89ca7e3caf0790c9244480db6a105611b00732dd81b9da934b1fbc82%40%3Cdev.pegasus.apache.org%3E

The source tarball, including signatures, digests, etc. can be found at:
https://dist.apache.org/repos/dist/dev/incubator/pegasus/2.2.0-RC0/

It is tagged in Git as v2.2.0-RC0 and the corresponding hash is the
following:
https://gitbox.apache.org/repos/asf?p=incubator-pegasus.git;a=commit;h=a81b6c78cca29d679ae51d7cf5287334c914e3dd

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

For information about the contents of this release, see:
https://docs.google.com/document/d/167M4R063FYcMXOahaInxkjJ8MBYBpzQ1ijeh0qC9SrE/edit?usp=sharing

The vote will be open for 72 hours.
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Best regards,
Yingchun Lai

Fwd: [VOTE] Contributors - Graduate Apache Daffodil (Incubating) to a top-level project

[Mike Beckerle]

This is an FYI notification that the Apache Daffodil contributors have
started a community vote about graduation from the incubator.  You will
hear more about this of course if this vote passes.

-mike beckerle

-- Forwarded message -
From: Mike Beckerle 
Date: Thu, Jan 28, 2021 at 6:08 PM
Subject: [VOTE] Contributors - Graduate Apache Daffodil (Incubating) to a
top-level project
To: 


One of the first steps in graduating from the Apache incubator to top level
is making sure we have consensus among our contributors that this makes
sense now. This is an initial first step.

Please reply with your vote (+1, 0, or -1 with reasons)

This vote will be open for at least 72 hours (non-weekend), so until at
least 5pm US.ET (UTC-5) on Tuesday, Feb 2.

You can review our wiki page about how we meet the ASF project maturity
model which is something projects do to self-assess before moving forward.
Your comments on this wiki page are also welcome.

https://cwiki.apache.org/confluence/display/DAFFODIL/Apache+Daffodil+Maturity+Model+Assesment

About voting: see The Apache Voting Process:
https://www.apache.org/foundation/voting.html if you'd like to review the
process/guidance.

My vote +1.

Fwd: [VOTE] (Round 2) Graduate Apache ECharts (incubating) as a top level project

[Ovilia]

Hi,

We are running a new round of community graduation vote of making
Apache ECharts (incubating) as a top level project in ECharts's mailing
list.

Thanks

*Ovilia*


-- Forwarded message -
From: Ovilia 
Date: Wed, Nov 4, 2020 at 5:33 PM
Subject: [VOTE] (Round 2) Graduate Apache ECharts (incubating) as a top
level project
To: dev 


Hi all,

In the last few weeks, we have discussed and voted about graduating
Apache ECharts (incubating) as a top level project. Since it has been
blocked by the branding issue of the "gallery" for several weeks, I'm
going to call on a new round of vote now.

If this vote passes, the next step would be to submit the resolution below
to the Incubator PMC, who would vote on sending it on to the Apache Board.

Vote:
[ ] +1 - Recommend graduation of Apache ECharts as a TLP
[ ]  0 - I don't feel strongly about it, but don't object
[ ] -1 - Do not recommend graduation of Apache ECharts because...

The VOTE will open for at least 72 hours and ends at
https://www.timeanddate.com/countdown/vote?iso=20201107T1735=237=cursive=1
.



The "gallery" is a third-party tool so it should not use a domain name
containing "echarts" to mislead visitors to believe this is an official
product. So a new domain name makeapie.com is used for it and the
previous URL gallery.echartsjs.com redirect to it. See more information
at [1].

Previous graduation discussion can be found at [2] and the previous
vote is at [3].
Our maturity model is available at [4] and checklist is [5].


[1]
https://lists.apache.org/thread.html/r3713fa95086b3faafb86c29ad5b8221c9a885c9de2c99edae60d42fd%40%3Cdev.echarts.apache.org%3E
[2]
https://lists.apache.org/thread.html/rf05e9dfa1aec1ac072c71c9cba882a59c9c57f4f89723da68e96de01%40%3Cdev.echarts.apache.org%3E
[3]
https://lists.apache.org/thread.html/ref7acdd692feb444996dc9a8e22a232bf3079adcc918d6cc5a530556%40%3Cdev.echarts.apache.org%3E
[4]
https://cwiki.apache.org/confluence/display/ECHARTS/Apache+Maturity+Model+Assessment+for+ECharts
[5]
https://cwiki.apache.org/confluence/display/ECHARTS/ECharts+Graduation+Check+List

-

X. Establish the Apache ECharts 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 charting and data visualization
library written in JavaScript.

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

RESOLVED, that the Apache ECharts Project be and hereby is
responsible for the creation and maintenance of software
related to a charting and data visualization
library written in JavaScript; and be it further

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

* Houjin Huang  
* Deqing Li 
* Dong Rui  
* Kener Linfeng 
* Kevin A. McGrail  
* Wenli Zhang   
* Shen Yi   
* Shuang Su 
* Siwen Su  
* Junting Wang  
* Zhongxiang Wang   
* Dave Fisher   
* Sheng Wu  
* Zak Wu

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Wenli Zhang
be appointed to the office of Vice President, Apache ECharts, 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 ECharts 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 ECharts Project; and be it further

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

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

Thanks

*Ovilia*

Fwd: Logo

[Antoine Toulme]

Hello folks,

I started this thread on our dev list and one of our mentors mentioned we could 
maybe get help “create a better one”. Anyone? Any ideas?

Cheers,

Antoine

> Begin forwarded message:
> 
> From: Antoine Toulme 
> Subject: Logo
> Date: September 20, 2020 at 12:22:27 PM PDT
> To: d...@tuweni.apache.org
> 
> Folks,
> 
> I put down some of my own money to get a logo for Apache Tuweni. In the end, 
> I didn’t like what the person produced and I tried to build one myself.
> 
> Here is the PR with the changes:
> https://github.com/apache/incubator-tuweni/pull/149 
> 
> 
> There are in effect a few logos:
> * The main one is in SVG and has animation, so the face represented by the 
> logo changes over 10s cycles.
> * There is a square one with just the face and no label, that can be used for 
> favicon.
> * I have a png in the PR that can be used when SVGs cannot be used.
> 
> Note the SVG uses the Apache font Montserrat and therefore if displayed 
> requires that font to be around. I have changed the website with a PR to add 
> that font and it seems to render ok.
> 
> The color of the logo is taken straight from the Apache feather. Same for the 
> text.
> 
> https://github.com/apache/incubator-tuweni-website/pull/5 
> 
> 
> Please let me know what you think!
> 
> Cheers,
> 
> Antoine
> 

FWD: [VOTE] graduate Apache Superset from the Apache Incubator

[Maxime Beauchemin]

FYI - we just started a VOTE to graduate Apache Superset from the Apache
Incubator (!!!)

-- Forwarded message -
From: Maxime Beauchemin 
Date: Tue, Sep 15, 2020 at 5:46 PM
Subject: [VOTE] graduate Apache Superset from the Apache Incubator
To: 


Hi all!

Over the past few months/years, the Apache Superset community has met all
the requirements to graduate from the Apache Incubator. Given that, I
believe we are ready for graduation and I'm excited to kick off the process
with a community vote at this time.

For the record, we have been incubating since 2017-05-02, have had 8
official Apache-approved releases, and have voted in 20 PMC members and 11
committers. See our Incubation Status File for more details:
https://incubator.apache.org/projects/superset.html

For reference, you can find out everything you need to know about the
graduation requirements and process here:
https://incubator.apache.org/guides/graduation.html

Consider this an implicit +1 from me.

Cheers!

Max

Fwd: [apache/incubator-tvm] [VOTE] Apache TVM Graduation (#6332)

[Tianqi Chen]

Dear IPMC:

FYI,  following a heated discussion with great support from our mentors,
committers and community members.
The  Apache(incubating) TVM is starting a vote to graduate as TLP

- [1] community DISCUSS thread:
https://lists.apache.org/thread.html/r91b8f469c6a54769869bb2435b7334a28bcff885ae078ab5612dae00%40%3Cdev.tvm.apache.org%3E
- [2] voting thread:
https://lists.apache.org/thread.html/rd5b8eefe49af09a2d0913758a5e5737b3fdb9072bc0becf4a2b2c7ee%40%3Cdev.tvm.apache.org%3E

TQ

-- Forwarded message -
From: Tianqi Chen 
Date: Mon, Aug 24, 2020 at 1:51 PM
Subject: [apache/incubator-tvm] [VOTE] Apache TVM Graduation (#6332)
To: apache/incubator-tvm 
Cc: Subscribed 


Dear Community:

Thanks  to everyone who participated in the discussion about graduation[1].
This is a formal voting thread for Apache TVM’s graduation.

If this vote passes, the next step would be to submit the resolution below
to the Incubator PMC, who would vote on sending it on to the Apache Board.

Vote:
[ ] +1 - Recommend graduation of Apache TVM as a TLP
[ ]  0 - I don't feel strongly about it, but don't object
[ ] -1 - Do not recommend graduation of Apache TVM because...

The VOTE will open for at least 72 hours.

This thread is mirrored to dev@, please vote by replying to this thread

--
The TVM project has been an Apache incubator project for nearly 1.5 year
now. In the past one and half year, the community grew healthily under the
Apache way. Some highlights include:

- A successful developer conference that we are continuing to host this year
- Great community growth, as of now, the community contains 16 PPMC
members, 31 committers, from a diverse list of organizations. We are
actively growing the list monthly.
- Active contributions: ~ 150 PRs merged each month.

The community has produced two formal apache releases. While we could also
wait until more releases. We feel that the community is mature enough that
we can push for graduation as it is, and continue to push for high quality
releases concurrently.

For reference, we also put together a maturity evaluation doc[2] under the
Apache maturity model.

Some additional note about the resolution below: the current PPMC will be
transitioned to the PMC. We have invited all the mentors in the current
PPMC who like to stay involved.

-

Establish the Apache TVM 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 compilation of machine learning models to run on a wide range of
hardware platforms...

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

RESOLVED, that the Apache TVM Project be and hereby is responsible for the
creation and maintenance of software related to compilation of machine
learning models to run on a wide range of hardware platforms; and be it
further

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

 * Tianqi Chen 
 * Timothy Chen 
 * Zhi Chen 
 * Byung-Gon Chun 
 * Ziheng Jiang 
 * Furkan Kamaci 
 * YiZhi Liu 
 * Masahiro Masuda 
 * Thierry Moreau 
 * Jared Roesch 
 * Henry Saputra 
 * Haichen Shen 
 * Markus Weimer 
 * Eddie Yan 
 * Lianmin Zheng 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Tianqi Chen be appointed to
the office of Vice President, Apache TVM, 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 TVM Project be and hereby is tasked with
the migration and rationalization of the Apache Incubator TVM
podling; and be it further

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

- [1]
https://lists.apache.org/thread.html/r91b8f469c6a54769869bb2435b7334a28bcff885ae078ab5612dae00%40%3Cdev.tvm.apache.org%3E
- [2]
https://docs.google.com/document/d/18nyAH-fcptVezAxPQe6H3FeTKPRkujOp1tc1YRSPLok/edit?usp=sharing

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:

Fwd: [VOTE] Graduate Apache ECharts (incubating) as a top level project

[Ovilia]

FYI.
Apache ECharts (incubating) is running a community graduation vote now.

Thanks

*Ovilia*

Forwarded Conversation
Subject: [VOTE] Graduate Apache ECharts (incubating) as a top level project


From: Ovilia 
Date: Mon, Aug 17, 2020 at 11:36 AM
To: dev 


Hi all,

Hello all,
After our discussion about readiness for graduation to TLP on the dev
mailing list [8], I would like to call a VOTE for Apache ECharts graduating
as a top level project.

If this vote passes, the next step would be to submit the resolution below
to the Incubator PMC, who would vote on sending it on to the Apache Board.

Vote:
[ ] +1 - Recommend graduation of Apache ECharts as a TLP
[ ]  0 - I don't feel strongly about it, but don't object
[ ] -1 - Do not recommend graduation of Apache ECharts because...

The VOTE will open for at least 72 hours.

-

X. Establish the Apache ECharts 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 charting and data visualization
library written in JavaScript.

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

RESOLVED, that the Apache ECharts Project be and hereby is
responsible for the creation and maintenance of software
related to a charting and data visualization
library written in JavaScript; and be it further

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

* Houjin Huang  
* Deqing Li 
* Dong Rui  
* Kener Linfeng 
* Kevin A. McGrail  
* Wenli Zhang   
* Shen Yi   
* Shuang Su 
* Siwen Su  
* Junting Wang  
* Zhongxiang Wang   
* Dave Fisher   
* Sheng Wu  
* Zak Wu

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Wenli Zhang
be appointed to the office of Vice President, Apache ECharts, 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 ECharts 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 ECharts Project; and be it further

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

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


-

More information:

- Assessment of the maturity model is available at [5].
- A checklist of graduation is available at [6].
- 3 new PPMCs and 6 new committers were elected and joined the community [1]
since incubation and now we have committers working for more than 6
different
companies.
- Our mailing list [2] is very active and we have 81 people subscribed to
it.
- Released 8 versions by 3 release managers [3] (and another version by
another release manager is under voting stage); release guide is at [4].
- 73 people have contributed to the project during incubation [10].
- Branding issues have been solved and name searching has been completed
[7].
- Website [9] has been updated to meet up with Apache regulations.

-


[1] https://echarts.apache.org/en/committers.html
[2] https://lists.apache.org/list.html?d...@echarts.apache.org
[3] https://dist.apache.org/repos/dist/release/incubator/echarts/
[4]
https://cwiki.apache.org/confluence/display/ECHARTS/Apache+ECharts+Release+Guide
[5]
https://cwiki.apache.org/confluence/display/ECHARTS/Apache+Maturity+Model+Assessment+for+ECharts
[6]
https://cwiki.apache.org/confluence/display/ECHARTS/ECharts+Graduation+Check+List
[7] https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-153
[8]
https://lists.apache.org/thread.html/rf05e9dfa1aec1ac072c71c9cba882a59c9c57f4f89723da68e96de01%40%3Cdev.echarts.apache.org%3E
[9] http://echarts.apache.org/
[10] 

Fwd: [IMPORTANT] - Migration to ci-builds.a.o

[Dave Fisher]

Hi -

This migration has been completed for the Incubator clutch analysis and site 
build.

It’s crunch time now. Some podlings have managed to move their builds, but 
others have not.

(1) Request a Folder for your project from Infra. We are no longer putting 
podling builds in the Incubator folder.
(2) There is a script to move build ”projects”.

https://cwiki.apache.org/confluence/display/INFRA/Migrating+jobs+from+Jenkins+to+Cloudbees
(3) Request missing plugins from Infra on builds@a.o mailing list.
(4) Fix any GitHub credential issues.

Ask for help.

Start yesterday!

Regards,
Dave

> Begin forwarded message:
> 
> From: Gavin McDonald 
> Subject: [IMPORTANT] - Migration to ci-builds.a.o
> Date: July 16, 2020 at 9:33:08 AM PDT
> To: builds 
> Reply-To: bui...@apache.org
> Reply-To: gmcdon...@apache.org
> 
> Hi All,
> 
> This NOTICE is for everyone on builds.apache.org. We are migrating to a new
> Cloudbees based Client Master called https://ci-builds.apache.org. The
> migrations of all jobs needs to be done before the switch off date of 15th
> August 2020, so you have a maximum of 4 weeks.
> 
> There is no tool or automated way of migrating your jobs, the
> differences in the platforms, the plugins and the setup makes it impossible
> to do in a safe way. So, you all need to start creating new jobs on
> ci-infra.a.o and then , when you are happy, turn off your old builds on
> builds.a.o.
> 
> There are currently 4 agents over there ready to take jobs, plus a floating
> agent which is shared amongst many masters (more to come). I will migrate
> away 2 more agents from builds.a.o to ci-builds.a.o every few days, and
> will keep an eye of load across both and adjust accordingly.
> 
> If needed, create a ticket on INFRA jira for any issues that crop up, or
> email here on builds@a.o. there may be one or two plugins we need to
> install/tweak etc.
> 
> We will be not using 'Views' at the top level, but rather we will take
> advantage of 'Folders Plus' - each project will get its own Folder and have
> authorisation access to create/edit jobs etc within that folder. I will
> create these folders as you ask for them to start with. This setup allows
> for credentials isolation amongst other benefits, including but not limited
> to exclusive agents (Controlled Agents) for your own use , should you have
> any project targeted donations of agents.
> 
> As with other aspects of the ASF, projects can choose to just enable all
> committers access to their folder, just ask.
> 
> We will re-use builds.apache.org as a CNAME to ci-builds.a.o but will not
> be setting up any forwarding rules or anything like that.
> 
> So, please, get started *now *on this so you can be sure we are all
> completed before the final cutoff date of 15th August 2020.
> 
> Any questions - I expect a few (dozen :) ) - ask away and/or file INFRA
> tickets.
> 
> Hadoop and related projects have their own migration path to follow, same
> cut off date, Cassandra, Beam, CouchDB have already migrated and are doing
> very well in their new homes.
> 
> Lets get going ...
> 
> -- 
> 
> *Gavin McDonald*
> Systems Administrator
> ASF Infrastructure Team

Fwd: [VOTE] Release Apache NuttX (Incubating) 9.1.0 [RC2]

[Nathan Hartman]

Hello IPMC,

Ping!!

Apache NuttX (Incubating) 9.1.0 [RC2] is awaiting your review and vote.

If we could please get a show of support from IPMC members and our
mentors, that would be great!

Cheers,
Nathan


-- Forwarded message -
From: Brennan Ashton 
Date: Sun, Jul 12, 2020 at 7:42 PM
Subject: [VOTE] Release Apache NuttX (Incubating) 9.1.0 [RC2]
To: 


Hello all,

This is a call for a vote to release Apache NuttX (Incubating) version
9.1.0.

The Apache NuttX community has voted on and approved a proposal to
release
Apache NuttX (Incubating) version 9.1.0.

We now kindly request the Incubator PMC members review and vote on this
incubator release.

NuttX is a real-time operating system (RTOS) with an emphasis on
standards
compliance and small footprint. Scalable from 8-bit to 64-bit
microcontroller
environments, the primary governing standards in NuttX are Posix and
ANSI
standards. Additional standard APIs from Unix and other common RTOS’s
(such as VxWorks) are adopted for functionality not available under
these
standards, or for functionality that is not appropriate for deeply-
embedded
environments (such as fork()).

Because this project targets embedded systems there is more complexity
involved in the build process. Two starting points:
 * README.txt -- This is found in the Apache NuttX source and is
extensive.
 * Unofficial NuttX Companion --
https://nuttx-companion.readthedocs.io/en/latest/user/install.html,
this is a currently unofficial opinionated guide maintained by some of
the project committers.

Apache NuttX community vote and result thread:
Result:
https://lists.apache.org/thread.html/r1a30e5cba2dab57556605fb6570fd722de1eee69244c1b4092579033%40%3Cdev.nuttx.apache.org%3E
Vote:
https://lists.apache.org/thread.html/r751f7ce05b1f0485b5dc9ca7bfb1c5f52abc5676fd81b9fb92910c64%40%3Cdev.nuttx.apache.org%3E

The release candidates (RC2):
https://dist.apache.org/repos/dist/dev/incubator/nuttx/9.1.0-RC2/

Git tag for the release (RC2):
https://github.com/apache/incubator-nuttx/releases/tag/nuttx-9.1.0-RC2
https://github.com/apache/incubator-nuttx-apps/releases/tag/nuttx-9.1.0-RC2

Hash for the release incubating-nuttx tag:
  e4e4cce6962430e2b07336d2c564b14298995661
Hash for the release incubating-nuttx-apps tag:
  4fac1c185c01adfa84f04618af9be7b9c4b884f5

Release Notes:
https://raw.githubusercontent.com/apache/incubator-nuttx/nuttx-9.1.0-RC2/ReleaseNotes


The artifacts have been signed with Key :
3554D78458CEB6954B020E12E1B6E30DB05D6280, which can be found in the
keys file:
https://dist.apache.org/repos/dist/dev/incubator/nuttx/KEYS

Look at here for how to verify this release candidate:
https://cwiki.apache.org/confluence/display/NUTTX/Validating+a+staged+Release

The vote will be open for at least 72 hours.

Please vote accordingly:
[ ] +1 approve
[ ] +0 no opinion
[ ] -1 disapprove with the reason

Brennan Ashton
Apache NuttX

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

Fwd: [VOTE] Graduate to a top-level project

[Ryan Blue]

Forwarding the graduation vote thread from the Iceberg community to let
everyone here know, per [1].

[1]:
https://incubator.apache.org/guides/graduation.html#community_graduation_vote

-- Forwarded message -
From: Ryan Blue 
Date: Tue, May 12, 2020 at 2:16 PM
Subject: [VOTE] Graduate to a top-level project
To: Iceberg Dev List 


Hi everyone,

I propose that the Iceberg community should petition to graduate from the
Apache Incubator to a top-level project.

Here is the draft board resolution:

Establish the Apache Iceberg Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to managing huge analytic datasets using a standard at-rest
table format that is designed for high performance and ease of use..

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

RESOLVED, that the Apache Iceberg Project be and hereby is responsible
for the creation and maintenance of software related to managing huge
analytic datasets using a standard at-rest table format that is designed
for high performance and ease of use; and be it further

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

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

 * Anton Okolnychyi 
 * Carl Steinbach   
 * Daniel C. Weeks  
 * James R. Taylor  
 * Julien Le Dem
 * Owen O'Malley
 * Parth Brahmbhatt 
 * Ratandeep Ratti  
 * Ryan Blue

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

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

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

Please vote in the next 72 hours.

[ ] +1 Petition the IPMC to graduate to top-level project
[ ] +0
[ ] -1 Wait to graduate because . . .
-- 
Ryan Blue


-- 
Ryan Blue

Fwd: [REQUEST] Apache Project promotion factoids: deadline 25 March

[Justin Mclean]

HI,

Any podlings have something they could add to this?

Thanks,
Justin

> Begin forwarded message:
> 
> From: "Sally Khudairi" 
> Subject: [REQUEST] Apache Project promotion factoids: deadline 25 March
> Date: 22 March 2020 at 7:24:49 am AEDT
> To: "ASF Marketing & Publicity" 
> Reply-To: priv...@dubbo.apache.org
> 
> Hello Apache PMCs and pPMCs --I hope you are all doing well and staying safe 
> during this daunting pandemic.
> 
> I have a request: would you be able to please share 3-5 impressive things 
> your project/podling does or highly-visible  implementations/deployments?
> 
> For example: 
> 
> 1) Apple Siri completes full ring replication around the world in 10 seconds 
> using Apache HBase.
> 
> 2) More than 60% of Apache projects use Apache Maven for build management.
> 
> 3) Netflix uses Apache Druid to manage its 1.5 trillion-row data warehouse 
> requirements that include what users see when tapping the Netflix icon or 
> logging in from a browser across platforms.
> 
> 
> **IMPORTANT: if any of your projects are part of any solution involving the 
> COVID-19 coronavirus, please let me know ASAP 
> 
> Deadline: 6AM ET (UTC -4) on Wednesday 25 March. Your submissions could be 
> used in ASF's anniversary promotions next or our weekly "Did You Know?" 
> promotions. 
> 
> Ongoing: we need as many as we can get, so I'll be keeping the survey open 
> year-round for you to share your highlights with us so we can share with the 
> world :-)
> 
> Submit today at: https://s.surveyplanet.com/jZlP5gwnD
> 
> Thank you in advance for your help with this. As always, feel free to let me 
> know if you have any questions.
> 
> Best,
> Sally
> 
> - - - 
> Vice President Marketing & Publicity
> Vice President Sponsor Relations
> The Apache Software Foundation
> 
> Tel +1 617 921 8656 | s...@apache.org

Fwd: svn commit: r1873757 - /incubator/public/trunk/content/ip-clearance/index.xml

[Dave Fisher]

> +Weex UI

You need to fix this.

Thanks,
Dave

> Begin forwarded message:
> 
> From: pa...@apache.org
> Subject: svn commit: r1873757 - 
> /incubator/public/trunk/content/ip-clearance/index.xml
> Date: February 7, 2020 at 5:28:20 PM EST
> To: c...@incubator.apache.org
> Reply-To: general@incubator.apache.org
> 
> Author: pauls
> Date: Fri Feb  7 22:28:20 2020
> New Revision: 1873757
> 
> URL: http://svn.apache.org/viewvc?rev=1873757=rev
> Log:
> Add the Apache Felix Atomos contribution ip-clearance form.
> 
> Modified:
>incubator/public/trunk/content/ip-clearance/index.xml
> 
> Modified: incubator/public/trunk/content/ip-clearance/index.xml
> URL: 
> http://svn.apache.org/viewvc/incubator/public/trunk/content/ip-clearance/index.xml?rev=1873757=1873756=1873757=diff
> ==
> --- incubator/public/trunk/content/ip-clearance/index.xml [utf-8] (original)
> +++ incubator/public/trunk/content/ip-clearance/index.xml [utf-8] Fri Feb  7 
> 22:28:20 2020
> @@ -48,6 +48,13 @@
> 
> 
>   
> +Weex UI
> +  
> +Apache Felix
> +2020-02-07
> +
> +
> +  
> Weex UI
>   
> Apache Weex (Incubating)
> 
> 
> 
> -
> To unsubscribe, e-mail: cvs-unsubscr...@incubator.apache.org
> For additional commands, e-mail: cvs-h...@incubator.apache.org
> 

Re: Fwd: [IP CLEARANCE] Maven Wrapper

[Robert Scholte]

And vote of acceptance
https://lists.apache.org/thread.html/97054be79cede23c792c1db91f0fd73129ce969fea26bd12a1bf38f5%40%3Cprivate.maven.apache.org%3E

On 6-1-2020 22:06:52, Robert Scholte  wrote:
Distribution rights:
https://github.com/takari/maven-wrapper/blob/master/LICENSE.txt

https://github.com/takari/takari-maven-plugin/blob/master/LICENSE.txt


Confirmed IP Clearance from all active committers:
https://lists.apache.org/thread.html/7c8fc7fa0fc677c24504d948d7d71e6cdebdb952c9ca0a2183460726%40%3Cprivate.maven.apache.org%3E

https://lists.apache.org/thread.html/bd38cce5904d805b8526593996fcfec17ba4c8b6d8a18d66261d072c%40%3Cprivate.maven.apache.org%3E

https://lists.apache.org/thread.html/00102361655d35ea939d44e522d9dd1fb4894af20ac418a1ef5973be%40%3Cprivate.maven.apache.org%3E

https://lists.apache.org/thread.html/7459ee80b46bef0c2f4640700a3ee4bad46ae64bb3dad54f8c7896a3%40%3Cprivate.maven.apache.org%3E

https://lists.apache.org/thread.html/0a9e690562ffe25ede5b601600e6b7edd5f1c70a2aaffddabbf5f85f%40%3Cprivate.maven.apache.org%3E

with this we have secured all IP for both repositories.

The repositories of takari.io are owned by Walmart Labs. We had good 
conversation with them and they were willing to donate.
However, they had trouble with the text of the clearance document. Legal@ASF 
was involved to help, but still without result.
Walmart Labs is aware of the situation, and said that if needed they could try 
to get the signatures.

I hope this answers your questions.
Robert
On 6-1-2020 21:37:35, Justin Mclean  wrote:
forwarding to maven private list as I forgot to CC

The IP clearance form is also missing a link to vote of acceptance


Begin forwarded message:

From: Justin Mclean mailto:jus...@classsoftware.com]>

Subject: Re: [IP CLEARANCE] Maven Wrapper

Date: 7 January 2020 at 7:32:18 am AEDT

To: general@incubator.apache.org [mailto:general@incubator.apache.org]

Reply-To: general@incubator.apache.org [mailto:general@incubator.apache.org]


Hi,

I don’t see that distribution rights have been confirmed. i.e Has takari (see 
takari.io [http://takari.io]) given permission to do this? I assume that takari 
is the owner of the code? If not does it belong to all of the contributors? If 
that’s the case have they aggreed to this?

Thanks,.
Justin
-
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]

Re: Fwd: [IP CLEARANCE] Maven Wrapper

[Robert Scholte]

Distribution rights:
https://github.com/takari/maven-wrapper/blob/master/LICENSE.txt

https://github.com/takari/takari-maven-plugin/blob/master/LICENSE.txt


Confirmed IP Clearance from all active committers:
https://lists.apache.org/thread.html/7c8fc7fa0fc677c24504d948d7d71e6cdebdb952c9ca0a2183460726%40%3Cprivate.maven.apache.org%3E

https://lists.apache.org/thread.html/bd38cce5904d805b8526593996fcfec17ba4c8b6d8a18d66261d072c%40%3Cprivate.maven.apache.org%3E

https://lists.apache.org/thread.html/00102361655d35ea939d44e522d9dd1fb4894af20ac418a1ef5973be%40%3Cprivate.maven.apache.org%3E

https://lists.apache.org/thread.html/7459ee80b46bef0c2f4640700a3ee4bad46ae64bb3dad54f8c7896a3%40%3Cprivate.maven.apache.org%3E

https://lists.apache.org/thread.html/0a9e690562ffe25ede5b601600e6b7edd5f1c70a2aaffddabbf5f85f%40%3Cprivate.maven.apache.org%3E

with this we have secured all IP for both repositories.

The repositories of takari.io are owned by Walmart Labs. We had good 
conversation with them and they were willing to donate.
However, they had trouble with the text of the clearance document. Legal@ASF 
was involved to help, but still without result.
Walmart Labs is aware of the situation, and said that if needed they could try 
to get the signatures.

I hope this answers your questions.
Robert
On 6-1-2020 21:37:35, Justin Mclean  wrote:
forwarding to maven private list as I forgot to CC

The IP clearance form is also missing a link to vote of acceptance


Begin forwarded message:

From: Justin Mclean mailto:jus...@classsoftware.com]>

Subject: Re: [IP CLEARANCE] Maven Wrapper

Date: 7 January 2020 at 7:32:18 am AEDT

To: general@incubator.apache.org [mailto:general@incubator.apache.org]

Reply-To: general@incubator.apache.org [mailto:general@incubator.apache.org]


Hi,

I don’t see that distribution rights have been confirmed. i.e Has takari (see 
takari.io [http://takari.io]) given permission to do this? I assume that takari 
is the owner of the code? If not does it belong to all of the contributors? If 
that’s the case have they aggreed to this?

Thanks,.
Justin
-
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]

Fwd: [IP CLEARANCE] Accepting Donation from Weex UI to Apache Weex

[申远]

I am forwarding this message to d...@weex.asf as Weex UI is under IP
clearance [1] process now.

We have some concerns about Weex branding, and I think donation like this
would solve this kinds of concern.

The organization using the mark must do nothing that would, in conjunction
> with the mark, suggest sponsorship or endorsement by the trademark holder.
> [2]
>

FYI: Weex is a trademark of Apache Software Foundation, any the combination
of Weex UI is a violation of ASF's branding, and Weex PMC is responsible
for solving this kinds of problems. By donating, the author of Weex UI will
have the right of using the trademark of Weex.

There are some other projects may violate the trademark of ASF, I'm really
appreciated if someone could help append the list [3] I created.

[1] https://incubator.apache.org/ip-clearance/
[2] http://www.apache.org/foundation/marks/
[3]
https://cwiki.apache.org/confluence/display/WEEX/CheckList#third-party-ip-solved

Best Regards,
YorkShen

申远


-- Forwarded message -
发件人： 申远 
Date: 2019年11月6日周三 下午8:28
Subject: [IP CLEARANCE] Accepting Donation from Weex UI to Apache Weex
To: 


Hi community,

The Weex community has made consensus about accepting donation of Weex UI
[1].

Weex UI is a rich interaction, lightweight, high performance UI library
based for Apache Weex.

The IP clearance form can be found at:
https://incubator.apache.org/ip-clearance/weex_ui.html once the website
updates. One can view the xml version at:
https://svn.apache.org/repos/asf/incubator/public/trunk/content/ip-clearance/weex_ui.xml

The git commit containing the donation can be found
https://github.com/alibaba/weex-ui/commit/cb845a41e1b7cb9acff133f152996d8d03d05beb
. The git repo will be transferred to ASF at the end of the process.

Please vote to approve this contribution. Lazy consensus applies:

If no -1, votes are being cast within the next 72 hours, the vote passes.

[1]
https://mail-archives.apache.org/mod_mbox/weex-dev/201910.mbox/%3Ctencent_52455495A38322341536DC76283B69A47607%40qq.com%3E

Best Regards,
YorkShen

申远

Fwd: [VOTE] Graudate Apache Weex (Incubating) as a Top Level Project

[YorkShen]

Weex community is currently voting on graduation to a TLP, and this is a
notification to IPMC according to graduation guidelines [1]

[1]
https://incubator.apache.org/guides/graduation.html#community_graduation_vote

Best Regards,
YorkShen

申远


-- Forwarded message -
发件人： YorkShen 
Date: 2019年10月25日周五 下午4:45
Subject: [VOTE] Graudate Apache Weex (Incubating) as a Top Level Project
To: dev 


Dear all,

Apache Weex entered the Incubator on Nov, 2016. Since that, the community
has moved to ASF infratructure, grown, diversed and learned a lot about
Apache Way. Some of our achievement is list below:

   - Published 6 release by 5 release manager [1]
   - There are 11 PPMC members, 8 committers (excluding PPMC members) [2],
   and 192 Github contributors [3]
   - There are 13.1 stars [4] and 1.7k forks on our Github Repo [5], with
   2274 closed PR[6] and 581 closed issues [7]
   - Two IP clearance forms are submitted and accepted already [8] [9].
   - All the Incubator report can be viewd in here [10], and the last
   Incubator report marked Weex as nearing graduation.

There are lots of issues need to solve before we move this vote to IPMC,
like preparing graduation resolution, form Weex PMC and PMC chair, even the
website configuration mentioned before [11]. But it's better if we could
discuss those issues in other threads, IMO.

Please take a minute to vote on whether or not Apache Weex should graduate
as a Top Level Project by responding to one of the following opinions.

   - [ ] +1 Apache Weex should graduate
   - [ ] +0 No opinions
   - [ ] -1 Apache Weex should not graduate (and why)

The vote is open for a minimum of 120 hours (considering there is a
weekend).

And I will prepare other stuffs listed above in other threads during the
voting period.

[1] https://weex.apache.org/download/download.html
[2]
https://cwiki.apache.org/confluence/display/WEEX/Mentor%2C+PPMCs+and+Committers
[3] https://github.com/apache/incubator-weex/graphs/contributors
[4] https://github.com/apache/incubator-weex/stargazers
[5] https://github.com/apache/incubator-weex/network/members
[6] https://github.com/apache/incubator-weex/pulls?q=is%3Apr+is%3Aclosed
[7] https://github.com/apache/incubator-weex/issues?q=is%3Aissue+is%3Aclosed
[8] https://incubator.apache.org/ip-clearance/weex_cli.html
[9] https://incubator.apache.org/ip-clearance/weex_loader.html
[10] https://cwiki.apache.org/confluence/display/WEEX/Poddling+report
[11]
https://lists.apache.org/thread.html/23c01be05276b073877e004180faf67208cf7a6362d38147bc529748@%3Cdev.weex.apache.org%3E

Best Regards,
YorkShen

申远

Fwd: [ASK helps from mentors] How to transfer/add the moderators for mail list

[Sheng Wu]

Hi IPMC

How to transfer or add the moderator of the mail list, today, I am still
the only one, because I created for the new project and PPMC.

I am guessing from some mail list command?

Sheng Wu 吴晟

Apache SkyWalking
Apache Incubator
Apache ShardingSphere, ECharts, DolphinScheduler podlings
Zipkin
Twitter, wusheng1108

Fwd: [VOTE] Apache Rya (incubating) graduation to Top Level Project

[Adina Crainiceanu]

Dear all,

This is a notification that a community vote to graduate is currently in
progress for Apache Rya (incubating)

Best regards
Adina

-- Forwarded message -
From: Adina Crainiceanu 
Date: Tue, Aug 27, 2019 at 11:48 AM
Subject: [VOTE] Apache Rya (incubating) graduation to Top Level Project
To: 


Dear all,

Following our discussion on the dev mailing list [1] I would like to call a
vote for Apache Rya graduating to a top level project.

If this vote passes, the next step would be to submit the resolution below
to the Incubator PMC, who would vote on sending it on to the ASF Board.

Vote:
[ ] +1 - Recommend graduation of Apache Rya as a TLP
[] 0 - No opinion
[ ] -1 - Do not recommend graduation of Apache Rya because...

The VOTE is open for a minimum of 72 hours.

[1]
https://lists.apache.org/thread.html/dd09c2060a754e69e093404e0d57239a555ab5e7d702cf76fd02f820@%3Cdev.rya.apache.org%3E

---

Establish the Apache Rya 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 scalable storage, retrieval, and analysis of RDF data.

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

RESOLVED, that the Apache Rya Project be and hereby is responsible for
the creation and maintenance of software related to scalable storage,
retrieval, and analysis of RDF data; and be it further

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

 * Aaron Mihalik 
 * Adina Crainiceanu 
 * Billie Rinaldi
 * Caleb Meier   
 * David Lotts   
 * David Rapp
 * Jennifer Brown
 * Josh Elser
 * Puja Valiyil  
 * Roshan Punnoose   
 * Steve R Wagner

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Adina Crainiceanu be
appointed to the office of Vice President, Apache Rya, 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 Rya Project be and hereby is tasked with the
migration and rationalization of the Apache Incubator Rya podling; and
be it further

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

Fwd: [VOTE] Graduate Apache SINGA as TLP

[Moaz Reyad]

Dear All,

I would like to notify the incubator general list that the SINGA community
has started the vote for graduation few days ago.

This notification is recommended by the graduation guide (
https://incubator.apache.org/guides/graduation.html#community_graduation_vote
).

Best regards,
Moaz

-- Forwarded message -
From: Moaz Reyad 
Date: Sat, Aug 24, 2019 at 6:01 PM
Subject: Re: [VOTE] Graduate Apache SINGA as TLP
To: 
Cc: 


+1 from me also.

The vote can be closed and I will send the RESULT email soon.

But it will be useful if the mentors participate in this voting before we
close it.

best regards,
Moaz

On Thu, Aug 22, 2019 at 4:34 AM zhongle  wrote:

> +1
>
> Best,
> zl
>
> > On Aug 22, 2019, at 10:24, Beng Chin OOI  wrote:
> >
> >
> > +1
> >
> > regards
> > Beng Chin
> >
> >
> >> On 2019-08-22 10:22, Wang Wei wrote:
> >> +1
> >> Thanks, Moaz!
> >> Regards,
> >> Wei
> >>> On Wed, Aug 21, 2019 at 8:53 PM Moaz Reyad  wrote:
> >>> Dear All,
> >>> Apache SINGA entered the incubator on March 2015. Since then, the
> community
> >>> has grown and several releases were published.
> >>> The last incubator report listed SINGA as "Nearing graduation":
> >>> https://cwiki.apache.org/confluence/display/INCUBATOR/June2019
> >>> The maturity assessment of SINGA can be found here:
> >>>
> https://cwiki.apache.org/confluence/display/SINGA/Maturity+model+assessment
> >>> The graduation resolution can be found here:
> >>>
> https://cwiki.apache.org/confluence/display/SINGA/Graduation+Resolution
> >>> Please take a minute to vote on whether or not Apache SINGA should
> graduate
> >>> to a Top Level Project by responding with one of the following:
> >>> [ ] +1 Apache SINGA should graduate.
> >>> [ ] +0 No opinion
> >>> [ ] -1 Apache SINGA should not graduate (please provide the reason)
> >>> The VOTE is open for a minimum of 72 hours.
> >>> Thank you,
> >>> Moaz
>
>

FWD: [VOTE] Apache OpenWhisk graduation to Top Level Project

[Rodric Rabbah]

This email is to notify general@i.a.o that a graduation community
[VOTE] is in progress for Apache OpenWhisk (incubating).

-r

-- Forwarded message -
From: Rodric Rabbah 
Date: Tue, Jun 4, 2019 at 5:25 PM
Subject: [VOTE] Apache OpenWhisk graduation to Top Level Project
To: 


Hi all,

After a discussion among the Apache OpenWhisk community on the dev
mailing list [1], we have completed all Trademark transfers, and we
are now in the process of pruning the PMC roster, completing the
podling status page and completing the project maturity model [2].

Apache OpenWhisk entered the incubator on November 23 2016. Since
then, we have grown to be in the top 25 list of Apache projects by
GitHub Stars at 4041, have 229 unique contributors across all our
project repos, more than 2500 commits, and most importantly, our
community has grown and is diversified beyond the initial founding
contributors and organization.

The project has come a long way in embracing The Apache Way, in no
small part to our dedicated mentors and the community spirit that has
grown along this journey. We are operating well as an Apache project
and so we should take the next step.

As such, I am calling a vote for Apache OpenWhisk to graduate to a top
level project. If we agree that we should graduate to a top level
project, the next step will be to draft a Resolution [3] for the PPMC
and IPMC to vote upon.

Please take a minute to vote on whether or not Apache OpenWhisk should
graduate to a Top Level Project by responding with one of the
following:

 [ ] +1 Apache OpenWhisk should graduate.
 [ ] +0 No opinion
 [ ] -1 Apache OpenWhisk should not graduate (please provide the reason)

The VOTE is open for a minimum of 72 hours. Per Apache guidelines [4]
I will notify the incubator mailing list that a community vote is
under way.

Thank you.
-r
(on behalf of the Apache OpenWhisk PPMC)

[1] 
https://lists.apache.org/thread.html/8daa3a05148f54ca82458777e2b2b5e25ba99d39dcf8ce7dd85d0188@%3Cdev.openwhisk.apache.org%3E
[2] https://cwiki.apache.org/confluence/display/OPENWHISK/Project+Maturity+Model
[3] https://cwiki.apache.org/confluence/pages/viewpage.action?pageId=115526932
[4] 
https://incubator.apache.org/guides/graduation.html#community_graduation_vote

Fwd: [ANNOUNCE] Apache Ratis (incubating) 0.3.0 release is available

[Tsz Wo Sze]

The Apache Ratis team is proud to announce the release of Apache Ratis
(incubating) 0.3.0.  Please see the download page:
https://ratis.incubator.apache.org/#download

Apache Ratis is a high-performance Raft library written in Java, where
Raft, as an alternative to Paxos, is a consensus algorithm that is
designed to be easy to understand.  Apache Ratis has implemented all
the standard Raft features, including leader election, log
replication, membership change and log compaction.  Moreover, it is
designed with data intensive applications in mind and fully supports
asynchronous event-driven applications. It is highly customizable --
allows pluggable state machine, pluggable RPC and pluggable Raft log.
It has been implemented to provide low latency and high throughput on
transactions.

The release contains new features such as multi-raft and watch
request, as well contains 73 improvements and 72 bug fixes.  See the
complete change list between 0.2.0 and 0.3.0 releases:
https://github.com/apache/incubator-ratis/compare/ratis-0.2.0...ratis-0.3.0

Regards,
Tsz-Wo Sze
on behalf of Apache Ratis PPMC

=
*Disclaimer*

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

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

Fwd: Re: [VOTE]: Release Apache Dubbo Admin(Incubating) 0.2.0 [RC3]

[Minxuan Zhuang]

-- Forwarded message -
From: Minxuan Zhuang 
Date: Mon, Apr 22, 2019 at 4:08 PM
Subject: Re: Re: [VOTE]: Release Apache Dubbo Admin(Incubating) 0.2.0 [RC3]
To: 


Hi, this LGPL License issue has been fixed, thanks kezhenxu94, I'll cancel
this vote and start a new one

On Mon, Apr 22, 2019 at 3:09 PM Huxing Zhang  wrote:

> Hi,
>
> On Mon, Apr 22, 2019 at 1:38 PM kezhenxu94  wrote:
> >
> > Hi All,
> >   I've excluded the `hibernate-core` dependency and verified as follows:
> >
> >
> > $ mvn license:add-third-party -Dlicense.useMissingFile
> > $ cat
> dubbo-admin-server/target/generated-sources/license/THIRD-PARTY.txt | grep
> "General Public License"
> >
> >
> > here is the output
> >
> >
> >  (Eclipse Public License - v 1.0) (GNU Lesser General Public
> License) Logback Classic Module (ch.qos.logback:logback-classic:1.2.3 -
> http://logback.qos.ch/logback-classic)
> >  (Eclipse Public License - v 1.0) (GNU Lesser General Public
> License) Logback Core Module (ch.qos.logback:logback-core:1.2.3 -
> http://logback.qos.ch/logback-core)
> >
>
> These are dual licensed dependencies, so we can choose the most
> permissive one. In this case EPL is compatible with Apache so no issue
> here.
> Be aware that General Public License is just on of the keyword, other
> keywords might also be check like GPL.
>
> >
> > also, I've tested that the functionality introduced together with this
> dependency[1] works well.
> >
> >
> > I'll check the license next time when I need to introduce new
> dependencies.
> > [1] https://github.com/apache/incubator-dubbo-admin/pull/324
> >
> >
> > Thanks
>
>

Fwd: [VOTE] Apache NetBeans graduation to Top Level Project

[Geertjan Wielenga]

As stated in the Apache guidelines[1], I am being wise and am notifying the
incubator general list that the community vote for graduating Apache
NetBeans has started by FWD-ing the [VOTE] e-mail to the general list.

Thanks,

Gj

[1]
https://incubator.apache.org/guides/graduation.html#community_graduation_vote

-- Forwarded message -
From: Geertjan Wielenga 
Date: Mon, Mar 11, 2019 at 11:47 AM
Subject: [VOTE] Apache NetBeans graduation to Top Level Project
To: dev , dev 


Hi all,

After a discussion amongst the Apache NetBeans community on the dev mailing
list[1], voting on a PMC chair[2], checking the podling status page[3], and
working through the maturity model[4], I would like to call a vote for
Apache NetBeans graduating to a top level project.

Apache NetBeans entered the incubator on October 1, 2016. Since then, we
have announced 2 releases, nominated several new committers, participated
in conferences and events, have 99 contributors with 2,423 commits, and --
most importantly -- have grown and diversified our community. Apache
NetBeans is a healthy project that is already acting like an Apache top
level project, so we should take the next step.

If we agree that we should graduate to a top level project, the next step
will be to draft a Resolution for the PPMC and IPMC to vote upon.

Please take a minute to vote on whether or not Apache NetBeans should
graduate to a Top Level Project by responding with one of the following:

[ ] +1 Apache NetBeans should graduate.
[ ] +0 No opinion
[ ] -1 Apache NetBeans should not graduate (please provide the reason)

The VOTE is open for a minimum of 72 hours. Per Apache guidelines[5] I will
also be notifying the incubator mailing list that a community vote is under
way.

Thanks,

Geertjan
on behalf of the Apache NetBeans PPMC

[1]
https://lists.apache.org/thread.html/8724c66eb22c1ceea81160968cb5ae68fdc2180f46fbbfaab16b4ce9@%3Cdev.netbeans.apache.org%3E
[2]
https://lists.apache.org/thread.html/e0ecae84ac6e4a097a34ce7b2afe0e987e403fe32269fb3903895bbc@%3Cdev.netbeans.apache.org%3E
[3] https://whimsy.apache.org/pods/project/netbeans
[4]
https://cwiki.apache.org/confluence/display/NETBEANS/Apache+Maturity+Model+Assessment+for+NetBeans
[5]
https://incubator.apache.org/guides/graduation.html#community_graduation_vote

Fwd: [jira] [Resolved] (PODLINGNAMESEARCH-154) Establish Whether "Apache Flagon" is a Suitable Name

[Joshua Poore]

Hello, 

Apache SensSoft’s PODLINGNAMESEARCH for a new podling name has successfully 
concluded (see below). The name our community most prefers—Apache Flagon—has 
been approved by the VP of Brand. As we understand it, our next steps are to 
work with INFRA to change the name of some of our various assets. However, we 
wanted to reach out to IPMC to alert them of our name change status and confirm 
that there were no additional steps or approvals needed before we begin working 
with INFRA. Please let us know if there are additional steps.

Many Thanks!

Josh

> Begin forwarded message:
> 
> From: "Mark Thomas (JIRA)" 
> Subject: [jira] [Resolved] (PODLINGNAMESEARCH-154) Establish Whether "Apache 
> Flagon" is a Suitable Name
> Date: February 20, 2019 at 11:59:00 AM EST
> To: poor...@me.com
> 
> 
> [ 
> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
>  ]
> 
> Mark Thomas resolved PODLINGNAMESEARCH-154.
> ---
>Resolution: Fixed
> 
> Approved.
> 
> Mark
> 
>> Establish Whether "Apache Flagon" is a Suitable Name
>> 
>> 
>>Key: PODLINGNAMESEARCH-154
>>URL: 
>> https://issues.apache.org/jira/browse/PODLINGNAMESEARCH-154
>>Project: Podling Suitable Names Search
>> Issue Type: Suitable Name Search
>>   Reporter: Joshua Poore
>> 
>> Related to "Apache SensSoft" renaming. Investigating the suitability of new 
>> names nominated by our community: 
>> https://lists.apache.org/list.html?d...@senssoft.apache.org. Apache SensSoft 
>> is a generalized behavioral logging package for thin-client applications for 
>> user analytics. 
> 
> 
> 
> --
> This message was sent by Atlassian JIRA
> (v7.6.3#76005)

Re: Fwd: [DISCUSS] can we use weex.io as the short domain namefortheapache project

[Mark Thomas]

All,

ASF policy states that:

"Apache projects must host official website content on an apache.org domain"

That said, if there are issues with access speeds from some locations 
I'd strongly urge affected projects to engage with our infrastructure 
team to find a solution. Maybe we can set up a www/TLP mirror in China. 
I have no idea how practical that is or if a better solution is 
available. The infrastructure folks are the ones to talk to.


Mark



On 18/02/2019 13:02, 申远 wrote:
Actually, with the tool provided by https://ping.chinaz.com/, there is 
huge difference of network speed between https://weex.apache.org/ and 
https://weex.io/ , though their content is totally the same.


The average speed for https://weex.io/ is *65ms* from 142 different IP 
address, while it is *271ms* for https://weex.apache.org/


But if using another domain is against the rule of Apache, I think I can 
live with it and redirect https://weex.io/ to https://weex.apache.org/


Best Regards,
YorkShen

申远


吴晟 Sheng Wu mailto:wu.sh...@foxmail.com>> 于 
2019年2月18日周一 下午5:16写道：


 > weex.apache.org <http://weex.apache.org> is fast too from my
network environment now.


The Chinese network status is strange, we all know. :) Right?

 > We had received several complaint years ago from Chinese users that
weex.apache.org <http://weex.apache.org> is slow, so we launched
weex-project.io <http://weex-project.io> with the same
content of weex.apache.org <http://weex.apache.org>. If this is
against rules, I think we can make
it redirect to weex.apache.org <http://weex.apache.org>, not sure
whether we would receive complaint
again.

In my mind, redirect is better. You could try, and listen to the
community.


If really need some another, I suggest you to talk with Brand
Management Committee.[1]


Maybe publish an website, but don't use `weex` in name and say
clearly, this is not Apache Weex official documents,
just documents maintained by volunteers. This is not so cool, I know.


[1] https://www.apache.org/foundation/marks/#whoweare


--
Sheng Wu
Apache SkyWalking, ShardingSphere, Zipkin
Twitter, wusheng1108







-- Original --
From:  "申远"mailto:shenyua...@gmail.com>>;
Date:  Mon, Feb 18, 2019 05:07 PM
To:  "general"mailto:general@incubator.apache.org>>;

Subject:  Re: Fwd: [DISCUSS] can we use weex.io <http://weex.io> as
the short domain namefortheapache project



weex.apache.org <http://weex.apache.org> is fast too from my network
environment now.

We had received several complaint years ago from Chinese users that
weex.apache.org <http://weex.apache.org> is slow, so we launched
weex-project.io <http://weex-project.io> with the same
content of weex.apache.org <http://weex.apache.org>. If this is
against rules, I think we can make
it redirect to weex.apache.org <http://weex.apache.org>, not sure
whether we would receive complaint
again.

Best Regards,
YorkShen

申远


吴晟 Sheng Wu mailto:wu.sh...@foxmail.com>>
于2019年2月18日周一 下午4:56写道：

 > Hi
 >
 >
 > I don't know why it is slow, I just tried, very quickly.
 >
 >
 >
 >
 > --
 > Sheng Wu
 > Apache SkyWalking, ShardingSphere, Zipkin
 > Twitter, wusheng1108
 >
 >
 >
 >
 >
 >
 >
 > -- Original ------
 > From:  "申远"mailto:shenyua...@gmail.com>>;
 > Date:  Mon, Feb 18, 2019 04:33 PM
 > To:  "general"mailto:general@incubator.apache.org>>;
 >
 > Subject:  Re: Fwd: [DISCUSS] can we use weex.io <http://weex.io>
as the short domain name
 > fortheapache project
 >
 >
 >
 > >
 > > 3. I don't think ASF websites are facing GFW issue.
 >
 > ASF website is quite slow when accessing from China, I am not
sure whether
 > this is a GFW issue or simply the server is on another continent
without a
 > CDN.
 >
 > We received complains about weex.apache.org
<http://weex.apache.org> from China mainland years ago,
 > so we deploy website to weex-project.io <http://weex-project.io>
for fast access in China, as many
 > of our users are from China and there is CDN for weex-project.io
<http://weex-project.io> .  If
 > there is a solution for this issue, please let me know.
 >
 > Best Regards,
 > YorkShen
 >
 > 申远
 >
 >
 > 吴晟 Sheng Wu mailto:wu.sh...@foxmail.com>> 于2019年2月18日周一 下午3:52写道：
 >
 > >

Re: Fwd: [DISCUSS] can we use weex.io as the short domainnamefortheapache project

[???? Sheng Wu]

Thanks for the feedback. Sadly, It looks like really get the network issue. 


In my mind, hosting `weex.io` site out ASF is not right.


--
Sheng Wu
Apache SkyWalking, ShardingSphere, Zipkin
Twitter, wusheng1108


 




-- Original --
From:  "";
Date:  Mon, Feb 18, 2019 09:02 PM
To:  "general";

Subject:  Re: Fwd: [DISCUSS] can we use weex.io as the short 
domainnamefortheapache project



Actually, with the tool provided by https://ping.chinaz.com/, there is huge 
difference of network speed between https://weex.apache.org/ and 
https://weex.io/ , though their content is totally the same.


The average speed for https://weex.io/ is 65ms from 142 different IP address, 
while it is 271ms for https://weex.apache.org/


But if using another domain is against the rule of Apache, I think I can live 
with it and redirect https://weex.io/ to https://weex.apache.org/


Best Regards,
YorkShen






 Sheng Wu  ??2019??2??18?? 5:16??

> weex.apache.org is fast too from my network environment now.
 
 
 The Chinese network status is strange, we all know. :) Right?
 
 > We had received several complaint years ago from Chinese users that
 weex.apache.org is slow, so we launched weex-project.io with the same
 content of weex.apache.org. If this is against rules, I think we can make
 it redirect to weex.apache.org, not sure whether we would receive complaint
 again.
 
 In my mind, redirect is better. You could try, and listen to the community. 
 
 
 If really need some another, I suggest you to talk with Brand Management 
Committee.[1]
 
 
 Maybe publish an website, but don't use `weex` in name and say clearly, this 
is not Apache Weex official documents, 
 just documents maintained by volunteers. This is not so cool, I know.
 
 
 [1] https://www.apache.org/foundation/marks/#whoweare
 
 
 --
 Sheng Wu
 Apache SkyWalking, ShardingSphere, Zipkin
 Twitter, wusheng1108
 
 
 
 
 
 
 
 -- Original --
 From:  "";
 Date:  Mon, Feb 18, 2019 05:07 PM
 To:  "general";
 
 Subject:  Re: Fwd: [DISCUSS] can we use weex.io as the short domain 
namefortheapache project
 
 
 
 weex.apache.org is fast too from my network environment now.
 
 We had received several complaint years ago from Chinese users that
 weex.apache.org is slow, so we launched weex-project.io with the same
 content of weex.apache.org. If this is against rules, I think we can make
 it redirect to weex.apache.org, not sure whether we would receive complaint
 again.
 
 Best Regards,
 YorkShen
 
 
 
 
  Sheng Wu  ??2019??2??18?? 4:56??
 
 > Hi
 >
 >
 > I don't know why it is slow, I just tried, very quickly.
 >
 >
 >
 >
 > --
 > Sheng Wu
 > Apache SkyWalking, ShardingSphere, Zipkin
 > Twitter, wusheng1108
 >
 >
 >
 >
 >
 >
 >
 > -- Original ------
 > From:  "";
 > Date:  Mon, Feb 18, 2019 04:33 PM
 > To:  "general";
 >
 > Subject:  Re: Fwd: [DISCUSS] can we use weex.io as the short domain name
 > fortheapache project
 >
 >
 >
 > >
 > > 3. I don't think ASF websites are facing GFW issue.
 >
 > ASF website is quite slow when accessing from China, I am not sure whether
 > this is a GFW issue or simply the server is on another continent without a
 > CDN.
 >
 > We received complains about weex.apache.org from China mainland years ago,
 > so we deploy website to weex-project.io for fast access in China, as many
 > of our users are from China and there is CDN for weex-project.io .  If
 > there is a solution for this issue, please let me know.
 >
 > Best Regards,
 > YorkShen
 >
 > 
 >
 >
 >  Sheng Wu  ??2019??2??18?? 3:52??
 >
 > > Hi YorkShen
 > >
 > >
 > > From my understanding, weex project, including branding and logo, should
 > > be donated to ASF(at least before Graduation).
 > > The basic policy is, weex.apache.org should be the only official website
 > > for the project.
 > > And project's website should be hosted in Apache Infra.
 > >
 > >
 > > If you have others, let's say weex.io and weex-project.io, and run by
 > > your committers team, I suggest
 > > 1. Set redirect for `weex.io` to `weex.apache.org`, for the end user
 > > convenience.
 > > 2. For the Chinese documents, if your committers/contributors maintain
 > > this, put it in `http://weex.apache.org/cn/`makes
 > <http://weex.apache.org/cn/makes>
 > > <http://weex.apache.org/cn/makes> sense.
 > > 3. I don't think ASF websites are facing GFW issue.
 > >
 > >
 > > If you want to publish another domain/website for ecosystem, you should
 > > avoid 

Re: Fwd: [DISCUSS] can we use weex.io as the short domain namefortheapache project

[吴晟 Sheng Wu]

> weex.apache.org is fast too from my network environment now.


The Chinese network status is strange, we all know. :) Right?

> We had received several complaint years ago from Chinese users that
weex.apache.org is slow, so we launched weex-project.io with the same
content of weex.apache.org. If this is against rules, I think we can make
it redirect to weex.apache.org, not sure whether we would receive complaint
again.

In my mind, redirect is better. You could try, and listen to the community. 


If really need some another, I suggest you to talk with Brand Management 
Committee.[1]


Maybe publish an website, but don't use `weex` in name and say clearly, this is 
not Apache Weex official documents, 
just documents maintained by volunteers. This is not so cool, I know.


[1] https://www.apache.org/foundation/marks/#whoweare


--
Sheng Wu
Apache SkyWalking, ShardingSphere, Zipkin
Twitter, wusheng1108


 




-- Original --
From:  "申远";
Date:  Mon, Feb 18, 2019 05:07 PM
To:  "general";

Subject:  Re: Fwd: [DISCUSS] can we use weex.io as the short domain 
namefortheapache project



weex.apache.org is fast too from my network environment now.

We had received several complaint years ago from Chinese users that
weex.apache.org is slow, so we launched weex-project.io with the same
content of weex.apache.org. If this is against rules, I think we can make
it redirect to weex.apache.org, not sure whether we would receive complaint
again.

Best Regards,
YorkShen

申远


吴晟 Sheng Wu  于2019年2月18日周一 下午4:56写道：

> Hi
>
>
> I don't know why it is slow, I just tried, very quickly.
>
>
>
>
> --
> Sheng Wu
> Apache SkyWalking, ShardingSphere, Zipkin
> Twitter, wusheng1108
>
>
>
>
>
>
>
> -- Original --
> From:  "申远";
> Date:  Mon, Feb 18, 2019 04:33 PM
> To:  "general";
>
> Subject:  Re: Fwd: [DISCUSS] can we use weex.io as the short domain name
> fortheapache project
>
>
>
> >
> > 3. I don't think ASF websites are facing GFW issue.
>
> ASF website is quite slow when accessing from China, I am not sure whether
> this is a GFW issue or simply the server is on another continent without a
> CDN.
>
> We received complains about weex.apache.org from China mainland years ago,
> so we deploy website to weex-project.io for fast access in China, as many
> of our users are from China and there is CDN for weex-project.io .  If
> there is a solution for this issue, please let me know.
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> 吴晟 Sheng Wu  于2019年2月18日周一 下午3:52写道：
>
> > Hi YorkShen
> >
> >
> > From my understanding, weex project, including branding and logo, should
> > be donated to ASF(at least before Graduation).
> > The basic policy is, weex.apache.org should be the only official website
> > for the project.
> > And project's website should be hosted in Apache Infra.
> >
> >
> > If you have others, let's say weex.io and weex-project.io, and run by
> > your committers team, I suggest
> > 1. Set redirect for `weex.io` to `weex.apache.org`, for the end user
> > convenience.
> > 2. For the Chinese documents, if your committers/contributors maintain
> > this, put it in `http://weex.apache.org/cn/`makes
> <http://weex.apache.org/cn/makes>
> > <http://weex.apache.org/cn/makes> sense.
> > 3. I don't think ASF websites are facing GFW issue.
> >
> >
> > If you want to publish another domain/website for ecosystem, you should
> > avoid using `weex-`, `weex.`, to avoid branding issues.
> > And I suggest you don't do that, because the community will be split.
> >
> >
> > The following are just suggestions from my experiences.
> > Blog(cn/en) post are popular in many Apache project, which could be
> easily
> > supported by our CI hook in GitHub, also have post control and review.
> > If you want helps from this, ping me or `d...@skywalking.apache.org`, we
> > have done something.
> >
> >
> > For Q robots, if you are running that on GitHub issue, a Robot account
> > with project subscription should be good enough.
> > If you want to do that at Website, I think it will be more complex.
> >
> >
> > --
> > Sheng Wu
> > Apache SkyWalking, ShardingSphere, Zipkin
> > Twitter, wusheng1108
> >
> >
> >
> >
> >
> >
> >
> > -- Original --
> > From:  "申远";
> > Date:  Mon, Feb 18, 2019 03:07 PM
> > To:  "general";
> >
> > Subject:  Fwd: [DISCUSS] can we use weex.io as

Re: Fwd: [DISCUSS] can we use weex.io as the short domain name fortheapache project

[申远]

weex.apache.org is fast too from my network environment now.

We had received several complaint years ago from Chinese users that
weex.apache.org is slow, so we launched weex-project.io with the same
content of weex.apache.org. If this is against rules, I think we can make
it redirect to weex.apache.org, not sure whether we would receive complaint
again.

Best Regards,
YorkShen

申远


吴晟 Sheng Wu  于2019年2月18日周一 下午4:56写道：

> Hi
>
>
> I don't know why it is slow, I just tried, very quickly.
>
>
>
>
> --
> Sheng Wu
> Apache SkyWalking, ShardingSphere, Zipkin
> Twitter, wusheng1108
>
>
>
>
>
>
>
> -- Original --
> From:  "申远";
> Date:  Mon, Feb 18, 2019 04:33 PM
> To:  "general";
>
> Subject:  Re: Fwd: [DISCUSS] can we use weex.io as the short domain name
> fortheapache project
>
>
>
> >
> > 3. I don't think ASF websites are facing GFW issue.
>
> ASF website is quite slow when accessing from China, I am not sure whether
> this is a GFW issue or simply the server is on another continent without a
> CDN.
>
> We received complains about weex.apache.org from China mainland years ago,
> so we deploy website to weex-project.io for fast access in China, as many
> of our users are from China and there is CDN for weex-project.io .  If
> there is a solution for this issue, please let me know.
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> 吴晟 Sheng Wu  于2019年2月18日周一 下午3:52写道：
>
> > Hi YorkShen
> >
> >
> > From my understanding, weex project, including branding and logo, should
> > be donated to ASF(at least before Graduation).
> > The basic policy is, weex.apache.org should be the only official website
> > for the project.
> > And project's website should be hosted in Apache Infra.
> >
> >
> > If you have others, let's say weex.io and weex-project.io, and run by
> > your committers team, I suggest
> > 1. Set redirect for `weex.io` to `weex.apache.org`, for the end user
> > convenience.
> > 2. For the Chinese documents, if your committers/contributors maintain
> > this, put it in `http://weex.apache.org/cn/`makes
> <http://weex.apache.org/cn/makes>
> > <http://weex.apache.org/cn/makes> sense.
> > 3. I don't think ASF websites are facing GFW issue.
> >
> >
> > If you want to publish another domain/website for ecosystem, you should
> > avoid using `weex-`, `weex.`, to avoid branding issues.
> > And I suggest you don't do that, because the community will be split.
> >
> >
> > The following are just suggestions from my experiences.
> > Blog(cn/en) post are popular in many Apache project, which could be
> easily
> > supported by our CI hook in GitHub, also have post control and review.
> > If you want helps from this, ping me or `d...@skywalking.apache.org`, we
> > have done something.
> >
> >
> > For Q robots, if you are running that on GitHub issue, a Robot account
> > with project subscription should be good enough.
> > If you want to do that at Website, I think it will be more complex.
> >
> >
> > --
> > Sheng Wu
> > Apache SkyWalking, ShardingSphere, Zipkin
> > Twitter, wusheng1108
> >
> >
> >
> >
> >
> >
> >
> > -- Original --
> > From:  "申远";
> > Date:  Mon, Feb 18, 2019 03:07 PM
> > To:  "general";
> >
> > Subject:  Fwd: [DISCUSS] can we use weex.io as the short domain name for
> > theapache project
> >
> >
> >
> > Hi, there
> >
> > I am a PPMC member of incubator-weex, there is some confusion about
> > third-party domain and it seems like difficult to resolve in dev@
> mailing
> > list, maybe someone here could give a hand to solve the problem of
> domains.
> >
> > 1.I 'd like to know if there is a formal rule that projects should use
> > xxx.apache.org instead of xxx.io, which is shorter and easier to
> remember.
> > 2. we have another domain  weex-project.io for fast access of Çhinese
> > Developers as GFW have some confluence on https://weex.apache.org/cn/.
> Is
> > this against rules for apache project.
> >
> > Best Regards,
> > YorkShen
> >
> > 申远
> >
> >
> > -- Forwarded message -
> > From: Dan 
> > Date: 2019年2月15日周五 下午2:39
> > Subject: [DISCUSS] can we use weex.io as the short domain name for the
> > apache project
> > To: 
> >
> >
> > Hi, Myrle/Willem,
> >
> > Currently, we have a domain name of weex.io and want to use it to
> replace
> > the previous weex-project.io domain name for the following reasons:
> >
> > 1. The domain name is shorter and easier to remember.
> > 2. Apache's website has slower access to the developer in China, so there
> > is a mirror website weex-project.io for Chinese developer.
> > 3. We expect to support https on this website and support some of our own
> > server functions, such as Q robots, article blog posts, etc.
> >
> > I would like to ask if apache has any restrictions on this third-party
> > domain name, and look forward to hearing from you.
> >
> > Thanks,
> > Dan

Re: Fwd: [DISCUSS] can we use weex.io as the short domain name fortheapache project

[吴晟 Sheng Wu]

Hi


I don't know why it is slow, I just tried, very quickly. 




--
Sheng Wu
Apache SkyWalking, ShardingSphere, Zipkin
Twitter, wusheng1108


 




-- Original --
From:  "申远";
Date:  Mon, Feb 18, 2019 04:33 PM
To:  "general";

Subject:  Re: Fwd: [DISCUSS] can we use weex.io as the short domain name 
fortheapache project



>
> 3. I don't think ASF websites are facing GFW issue.

ASF website is quite slow when accessing from China, I am not sure whether
this is a GFW issue or simply the server is on another continent without a
CDN.

We received complains about weex.apache.org from China mainland years ago,
so we deploy website to weex-project.io for fast access in China, as many
of our users are from China and there is CDN for weex-project.io .  If
there is a solution for this issue, please let me know.

Best Regards,
YorkShen

申远


吴晟 Sheng Wu  于2019年2月18日周一 下午3:52写道：

> Hi YorkShen
>
>
> From my understanding, weex project, including branding and logo, should
> be donated to ASF(at least before Graduation).
> The basic policy is, weex.apache.org should be the only official website
> for the project.
> And project's website should be hosted in Apache Infra.
>
>
> If you have others, let's say weex.io and weex-project.io, and run by
> your committers team, I suggest
> 1. Set redirect for `weex.io` to `weex.apache.org`, for the end user
> convenience.
> 2. For the Chinese documents, if your committers/contributors maintain
> this, put it in `http://weex.apache.org/cn/`makes
> <http://weex.apache.org/cn/makes> sense.
> 3. I don't think ASF websites are facing GFW issue.
>
>
> If you want to publish another domain/website for ecosystem, you should
> avoid using `weex-`, `weex.`, to avoid branding issues.
> And I suggest you don't do that, because the community will be split.
>
>
> The following are just suggestions from my experiences.
> Blog(cn/en) post are popular in many Apache project, which could be easily
> supported by our CI hook in GitHub, also have post control and review.
> If you want helps from this, ping me or `d...@skywalking.apache.org`, we
> have done something.
>
>
> For Q robots, if you are running that on GitHub issue, a Robot account
> with project subscription should be good enough.
> If you want to do that at Website, I think it will be more complex.
>
>
> --
> Sheng Wu
> Apache SkyWalking, ShardingSphere, Zipkin
> Twitter, wusheng1108
>
>
>
>
>
>
>
> -- Original --
> From:  "申远";
> Date:  Mon, Feb 18, 2019 03:07 PM
> To:  "general";
>
> Subject:  Fwd: [DISCUSS] can we use weex.io as the short domain name for
> theapache project
>
>
>
> Hi, there
>
> I am a PPMC member of incubator-weex, there is some confusion about
> third-party domain and it seems like difficult to resolve in dev@ mailing
> list, maybe someone here could give a hand to solve the problem of domains.
>
> 1.I 'd like to know if there is a formal rule that projects should use
> xxx.apache.org instead of xxx.io, which is shorter and easier to remember.
> 2. we have another domain  weex-project.io for fast access of Çhinese
> Developers as GFW have some confluence on https://weex.apache.org/cn/. Is
> this against rules for apache project.
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> -- Forwarded message -
> From: Dan 
> Date: 2019年2月15日周五 下午2:39
> Subject: [DISCUSS] can we use weex.io as the short domain name for the
> apache project
> To: 
>
>
> Hi, Myrle/Willem,
>
> Currently, we have a domain name of weex.io and want to use it to replace
> the previous weex-project.io domain name for the following reasons:
>
> 1. The domain name is shorter and easier to remember.
> 2. Apache's website has slower access to the developer in China, so there
> is a mirror website weex-project.io for Chinese developer.
> 3. We expect to support https on this website and support some of our own
> server functions, such as Q robots, article blog posts, etc.
>
> I would like to ask if apache has any restrictions on this third-party
> domain name, and look forward to hearing from you.
>
> Thanks,
> Dan

Re: Fwd: [DISCUSS] can we use weex.io as the short domain name for theapache project

[申远]

>
> 3. I don't think ASF websites are facing GFW issue.

ASF website is quite slow when accessing from China, I am not sure whether
this is a GFW issue or simply the server is on another continent without a
CDN.

We received complains about weex.apache.org from China mainland years ago,
so we deploy website to weex-project.io for fast access in China, as many
of our users are from China and there is CDN for weex-project.io .  If
there is a solution for this issue, please let me know.

Best Regards,
YorkShen

申远


吴晟 Sheng Wu  于2019年2月18日周一 下午3:52写道：

> Hi YorkShen
>
>
> From my understanding, weex project, including branding and logo, should
> be donated to ASF(at least before Graduation).
> The basic policy is, weex.apache.org should be the only official website
> for the project.
> And project's website should be hosted in Apache Infra.
>
>
> If you have others, let's say weex.io and weex-project.io, and run by
> your committers team, I suggest
> 1. Set redirect for `weex.io` to `weex.apache.org`, for the end user
> convenience.
> 2. For the Chinese documents, if your committers/contributors maintain
> this, put it in `http://weex.apache.org/cn/`makes
> <http://weex.apache.org/cn/makes> sense.
> 3. I don't think ASF websites are facing GFW issue.
>
>
> If you want to publish another domain/website for ecosystem, you should
> avoid using `weex-`, `weex.`, to avoid branding issues.
> And I suggest you don't do that, because the community will be split.
>
>
> The following are just suggestions from my experiences.
> Blog(cn/en) post are popular in many Apache project, which could be easily
> supported by our CI hook in GitHub, also have post control and review.
> If you want helps from this, ping me or `d...@skywalking.apache.org`, we
> have done something.
>
>
> For Q robots, if you are running that on GitHub issue, a Robot account
> with project subscription should be good enough.
> If you want to do that at Website, I think it will be more complex.
>
>
> --
> Sheng Wu
> Apache SkyWalking, ShardingSphere, Zipkin
> Twitter, wusheng1108
>
>
>
>
>
>
>
> -- Original --
> From:  "申远";
> Date:  Mon, Feb 18, 2019 03:07 PM
> To:  "general";
>
> Subject:  Fwd: [DISCUSS] can we use weex.io as the short domain name for
> theapache project
>
>
>
> Hi, there
>
> I am a PPMC member of incubator-weex, there is some confusion about
> third-party domain and it seems like difficult to resolve in dev@ mailing
> list, maybe someone here could give a hand to solve the problem of domains.
>
> 1.I 'd like to know if there is a formal rule that projects should use
> xxx.apache.org instead of xxx.io, which is shorter and easier to remember.
> 2. we have another domain  weex-project.io for fast access of Çhinese
> Developers as GFW have some confluence on https://weex.apache.org/cn/. Is
> this against rules for apache project.
>
> Best Regards,
> YorkShen
>
> 申远
>
>
> -- Forwarded message -
> From: Dan 
> Date: 2019年2月15日周五 下午2:39
> Subject: [DISCUSS] can we use weex.io as the short domain name for the
> apache project
> To: 
>
>
> Hi, Myrle/Willem,
>
> Currently, we have a domain name of weex.io and want to use it to replace
> the previous weex-project.io domain name for the following reasons:
>
> 1. The domain name is shorter and easier to remember.
> 2. Apache's website has slower access to the developer in China, so there
> is a mirror website weex-project.io for Chinese developer.
> 3. We expect to support https on this website and support some of our own
> server functions, such as Q robots, article blog posts, etc.
>
> I would like to ask if apache has any restrictions on this third-party
> domain name, and look forward to hearing from you.
>
> Thanks,
> Dan

Re: Fwd: [DISCUSS] can we use weex.io as the short domain name for theapache project

[吴晟 Sheng Wu]

Hi YorkShen


From my understanding, weex project, including branding and logo, should be 
donated to ASF(at least before Graduation).
The basic policy is, weex.apache.org should be the only official website for 
the project.
And project's website should be hosted in Apache Infra.


If you have others, let's say weex.io and weex-project.io, and run by your 
committers team, I suggest
1. Set redirect for `weex.io` to `weex.apache.org`, for the end user 
convenience.
2. For the Chinese documents, if your committers/contributors maintain this, 
put it in `http://weex.apache.org/cn/`makes sense.
3. I don't think ASF websites are facing GFW issue. 


If you want to publish another domain/website for ecosystem, you should avoid 
using `weex-`, `weex.`, to avoid branding issues.
And I suggest you don't do that, because the community will be split.


The following are just suggestions from my experiences.
Blog(cn/en) post are popular in many Apache project, which could be easily 
supported by our CI hook in GitHub, also have post control and review.
If you want helps from this, ping me or `d...@skywalking.apache.org`, we have 
done something.


For Q robots, if you are running that on GitHub issue, a Robot account with 
project subscription should be good enough. 
If you want to do that at Website, I think it will be more complex. 


--
Sheng Wu
Apache SkyWalking, ShardingSphere, Zipkin
Twitter, wusheng1108


 




-- Original --
From:  "申远";
Date:  Mon, Feb 18, 2019 03:07 PM
To:  "general";

Subject:  Fwd: [DISCUSS] can we use weex.io as the short domain name for 
theapache project



Hi, there

I am a PPMC member of incubator-weex, there is some confusion about
third-party domain and it seems like difficult to resolve in dev@ mailing
list, maybe someone here could give a hand to solve the problem of domains.

1.I 'd like to know if there is a formal rule that projects should use
xxx.apache.org instead of xxx.io, which is shorter and easier to remember.
2. we have another domain  weex-project.io for fast access of Çhinese
Developers as GFW have some confluence on https://weex.apache.org/cn/. Is
this against rules for apache project.

Best Regards,
YorkShen

申远


-- Forwarded message -
From: Dan 
Date: 2019年2月15日周五 下午2:39
Subject: [DISCUSS] can we use weex.io as the short domain name for the
apache project
To: 


Hi, Myrle/Willem,

Currently, we have a domain name of weex.io and want to use it to replace
the previous weex-project.io domain name for the following reasons:

1. The domain name is shorter and easier to remember.
2. Apache's website has slower access to the developer in China, so there
is a mirror website weex-project.io for Chinese developer.
3. We expect to support https on this website and support some of our own
server functions, such as Q robots, article blog posts, etc.

I would like to ask if apache has any restrictions on this third-party
domain name, and look forward to hearing from you.

Thanks,
Dan

Fwd: [DISCUSS] can we use weex.io as the short domain name for the apache project

[申远]

Hi, there

I am a PPMC member of incubator-weex, there is some confusion about
third-party domain and it seems like difficult to resolve in dev@ mailing
list, maybe someone here could give a hand to solve the problem of domains.

1.I 'd like to know if there is a formal rule that projects should use
xxx.apache.org instead of xxx.io, which is shorter and easier to remember.
2. we have another domain  weex-project.io for fast access of Çhinese
Developers as GFW have some confluence on https://weex.apache.org/cn/. Is
this against rules for apache project.

Best Regards,
YorkShen

申远


-- Forwarded message -
From: Dan 
Date: 2019年2月15日周五 下午2:39
Subject: [DISCUSS] can we use weex.io as the short domain name for the
apache project
To: 


Hi, Myrle/Willem,

Currently, we have a domain name of weex.io and want to use it to replace
the previous weex-project.io domain name for the following reasons:

1. The domain name is shorter and easier to remember.
2. Apache's website has slower access to the developer in China, so there
is a mirror website weex-project.io for Chinese developer.
3. We expect to support https on this website and support some of our own
server functions, such as Q robots, article blog posts, etc.

I would like to ask if apache has any restrictions on this third-party
domain name, and look forward to hearing from you.

Thanks,
Dan

Fwd: Release Apache Dubbo OPS(Incubating) 0.1[RC3]

[Mark Thomas]

 Forwarded Message 
Subject: Re: Release Apache Dubbo OPS(Incubating) 0.1[RC3]
Date: Wed, 6 Feb 2019 10:10:10 +
From: Mark Thomas 
Reply-To: d...@dubbo.apache.org
To: d...@dubbo.apache.org

On 03/02/2019 03:52, Minxuan Zhuang wrote:



> Please vote accordingly:
> 
> [X] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove with the reason

Mark


Notes (no action required):
Signatures and hashes match.
The Maven wrapper is present in the repository but not the source release.
The .gitignore files have been excluded from the source release.
Various npm warnings during the build process
"mvn verify" completed successfully when run from the unpacked source
distribution

Minor issues (consider fixing for next release):
sha512 hashes are missing * that indicates that the hashed files are
binaries

There appear to be some unnecessary .gitkeep files in the repository

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

Fwd: Draft incubator report

[Justin Mclean]

Sorry I meant to send this to the list but only Dave got it.

> Begin forwarded message:
> 
> From: Justin Mclean 
> Subject: Re: Draft incubator report
> Date: 6 February 2019 at 8:48:46 am AEDT
> To: Dave Fisher 
> 
> Hi,
> 
>> Yes, that is better, but here is the next challenge. For distribution 
>> channels like Maven, NPM, etc which some projects use to stage prospective 
>> releases how do we recommend that projects stay within the available, but 
>> not advertised rule? I think somewhere some guidance is needed.
> 
> When this was dicusssed (see [1]) it was stated:
> "There are an unbounded number of such downstream channels, and there is no 
> way we are going to formulate specific policies for all of them.”
> 
> But it’s really not that hard and is covered by existing policy. [2][3]
> 
> But some examples may help:
> - With GitHub I would not expect any releases that appear on the release page 
> (https://github.com/apache//releases)  to contain unreleased 
> code or be compiled from such code. Only releases compiled from official 
> approved source releases should be listed.
> - With npm if I go "npm install ” I only expect to get the 
> latest official release based on an approved offical source release. To get a 
> RC or nightly I’d need to "npm install @sometag”
> - With docker hub, if I go "docker pull ” I’d only expect to 
> get the latest official approved version and not contain any unapproved code. 
> I’s expect RCs to be tagged in some way and nightly with their commit hash or 
> something similar.
> - For PiPy I expect "pip install ” to install the lasted 
> official approved release and no contain any unapproved code. And I not 
> expect to see any releases on the release history page 
> (https://pypi.org/project//#history) to contain unapproved 
> code.
> 
> I think with most platforms you can work out what to do so that you are not 
> advising nightlys or release candidates to the general public.
> 
> And of course your ASF project site shouldn't include any links to unapproved 
> releases as mentioned in [2] "Do not include any links on the project website 
> that might encourage non-developers to download and use nightly builds, 
> snapshots, release candidates, or any other similar package”. Note it also 
> says "If you find that the general public are downloading such test packages, 
> then remove them.” so care still needs to be taken.
> 
> Thanks,
> Justin
> 
> 1. https://issues.apache.org/jira/browse/LEGAL-270
> 2. http://www.apache.org/legal/release-policy.html#what
> 3. http://www.apache.org/legal/release-policy.html#release-types

Fwd: Requesting wiki access to update Podling status

[Subbu Subramaniam]

I mistyped the 'genera' address, so here is the request again. thanks

-Subbu

Hello,

Please provide update/write access to the podling status wiki pages for
user name SubbuSubramaniam so that we can put out the status in time
starting January 2019. I have already created a wiki account with the user
name SubbuSubramaniam and am able to login.

thanks

-Subbu

Fwd: [VOTE] Graduate Apache Griffin (incubating) as a TLP

[William Guo]

+dev

-- Forwarded message -
From: William Guo 
Date: Thu, Nov 1, 2018 at 11:21 AM
Subject: [VOTE] Graduate Apache Griffin (incubating) as a TLP
To: 


Hi all,

Given that we've got positive feedback on the DISCUSS
thread, after we had made some changes based on DISCUSS feedback.
I'd like to start an official VOTE thread now.


Please vote on the resolution pasted below to graduate
Apache Griffin from the incubator to the top level project.

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

This vote will be open for at least 72 hours.


Many thanks to our mentors and everyone else for their support,

William Guo (on behalf of the Apache Griffin PPMC).


## Resolution to create a TLP from graduating Incubator podling

X. Establish the Apache Griffin 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 data quality solution for big data, including both streaming
and batch mode.


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

RESOLVED, that the Apache Griffin Project be and hereby is
responsible for the creation and maintenance of software related to
a data quality solution for big data, including both streaming and batch
mode;
and be it further

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

* Alex Lv 
* Deyi Yao 
* Eugene Liu 
* Grant Guo 
* He Wang 
* Henry Saputra 
* Jason Liao 
* John Liu 
* Juan Li 
* Liang Shao 
* Lionel Liu 
* Luciano Resende 
* Nick Sokolov 
* Shawn Sha 
* Vincent Zhao 
* William Guo 
* Yuqin Xuan 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that William Guo be
appointed to the office of Vice President, Apache Griffin, 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 Griffin Project be and hereby is tasked
with the migration and rationalization of the Apache Incubator
Griffin podling; and be it further

RESOLVED, that all responsibilities pertaining to the Apache Incubator
Griffin podling encumbered upon the Apache Incubator PMC are
here after discharged.

Re: Fwd: graphviz as a potential apache project

[Jacques Le Roux]

Le 04/06/2018 à 16:29, Bertrand Delacretaz a écrit :

On Mon, Jun 4, 2018 at 1:31 PM, Jacques Le Roux
 wrote:

...Anyway a big +1 to invite Graphviz in the incubator. I may even help if
necessary

Note that Stephen North who started this conversation with Sharan
hasn't been CCed in all messages so might have missed part of the
conversation.

Stephen, for what it's worth the full conversation is here:

https://lists.apache.org/thread.html/ad32238950411dd5d29297286a136dd58319bf9d8023cff1ff860f88@%3Cgeneral.incubator.apache.org%3E

And subscription instructions for this list are at http://incubator.apache.org/

-Bertrand

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



Thanks Bertrand

Jacques


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

Re: Fwd: graphviz as a potential apache project

[Bertrand Delacretaz]

On Mon, Jun 4, 2018 at 1:31 PM, Jacques Le Roux
 wrote:
> ...Anyway a big +1 to invite Graphviz in the incubator. I may even help if
> necessary

Note that Stephen North who started this conversation with Sharan
hasn't been CCed in all messages so might have missed part of the
conversation.

Stephen, for what it's worth the full conversation is here:

https://lists.apache.org/thread.html/ad32238950411dd5d29297286a136dd58319bf9d8023cff1ff860f88@%3Cgeneral.incubator.apache.org%3E

And subscription instructions for this list are at http://incubator.apache.org/

-Bertrand

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

Re: Fwd: graphviz as a potential apache project

[Jacques Le Roux]

Thanks Sharan,

I don't know much about Graphviz but I remember we spoke about using Graphviz 
with Ron in the OFBiz project.

He mentioned: "If we go with AsciiDoc, *GraphViz* is built-in and will become more 
familiar to everyone."[1]

Since we use AsciiDoc for our documentation now having **Graphviz in Apache 
will certainly be helpful, and not only for OFBiz.

Anyway a big +1 to invite Graphviz in the incubator. I may even help if 
necessary.

Jacques

[1] https://markmail.org/message/mp7u7iq3ro7pfl2a


Le 03/06/2018 à 17:29, sha...@apache.org a écrit :

Hi All

I received this request from Stephen so am forwarding to the general incubator 
mailing list for discussion and any suggestions for options.

Thanks
Sharan


 Forwarded Message 
Subject: graphviz as a potential apache project
Date: Thu, 31 May 2018 17:51:04 -0400
From: Stephen North 
Reply-To: Stephen North 
To: sha...@apache.org



Hi, Sharan.   I hope you’re the right person for this.  (Your org. just sent an 
invitation
to an Apache roadshow event under your name.)

I’m one of the founders of Graphviz, 20+ years ago, and it’s useful 
infrastructure
software with new and old applications in bioinformatics, machine learning, 
software
engineering and other fields, including plugins for R, python, Haskell, 
transpiled
into javascript, who knows what else.  I think for example clang, llvm, maybe Go
use it for debug output.  See www.graphviz.org

We started this in AT Labs but AT discontinued all support for the work,
eliminated some of our jobs or encouraged us to leave, has disclaimed the 
project,
so we’re on our own.  We maintain the software and the website, that we moved 
to gitlab.

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?

Sorry if this has gone long (I could say a lot more, too, for example how we 
could put
focus effort on new features, or providing better resources to people that need
network visualization as a service). I’m hoping you’re the right person to 
start the conversation.

Thank you for your time, and for your consideration.

Stephen North

Re: Fwd: graphviz as a potential apache project

[Emilian Bold]

Apache NetBeans is a pretty big and mature project too and it's still 
undergoing incubation.

The advantage for NetBeans is that Sun Microsystems / Oracle owns all the IP 
and just donated it to Apache. It might be a bit more complicated for Graphviz.

That being said, I'm totally +1 on Graphviz, it's such a handy little project 
I've used from time to time.

--emi

‐‐‐ Original Message ‐‐‐

On 3 June 2018 6:29 PM,  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.
> 
> Thanks
> 
> Sharan
> 
>  Forwarded Message 
> 
> Subject: graphviz as a potential apache project
> 
> Date: Thu, 31 May 2018 17:51:04 -0400
> 
> From: Stephen North scno...@gmail.com
> 
> Reply-To: Stephen North scno...@gmail.com
> 
> To: sha...@apache.org
> 
> Hi, Sharan. I hope you’re the right person for this. (Your org. just sent an 
> invitation
> 
> to an Apache roadshow event under your name.)
> 
> I’m one of the founders of Graphviz, 20+ years ago, and it’s useful 
> infrastructure
> 
> software with new and old applications in bioinformatics, machine learning, 
> software
> 
> engineering and other fields, including plugins for R, python, Haskell, 
> transpiled
> 
> into javascript, who knows what else. I think for example clang, llvm, maybe 
> Go
> 
> use it for debug output. See www.graphviz.org
> 
> We started this in AT Labs but AT discontinued all support for the work,
> 
> eliminated some of our jobs or encouraged us to leave, has disclaimed the 
> project,
> 
> so we’re on our own. We maintain the software and the website, that we moved 
> to gitlab.
> 
> 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?
> 
> Sorry if this has gone long (I could say a lot more, too, for example how we 
> could put
> 
> focus effort on new features, or providing better resources to people that 
> need
> 
> network visualization as a service). I’m hoping you’re the right person to 
> start the conversation.
> 
> Thank you for your time, and for your consideration.
> 
> Stephen North



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

Fwd: graphviz as a potential apache project

[sharan]

Hi All

I received this request from Stephen so am forwarding to the general 
incubator mailing list for discussion and any suggestions for options.


Thanks
Sharan


 Forwarded Message 
Subject:graphviz as a potential apache project
Date:   Thu, 31 May 2018 17:51:04 -0400
From:   Stephen North 
Reply-To:   Stephen North 
To: sha...@apache.org



Hi, Sharan.   I hope you’re the right person for this.  (Your org. just sent an 
invitation
to an Apache roadshow event under your name.)

I’m one of the founders of Graphviz, 20+ years ago, and it’s useful 
infrastructure
software with new and old applications in bioinformatics, machine learning, 
software
engineering and other fields, including plugins for R, python, Haskell, 
transpiled
into javascript, who knows what else.  I think for example clang, llvm, maybe Go
use it for debug output.  See www.graphviz.org

We started this in AT Labs but AT discontinued all support for the work,
eliminated some of our jobs or encouraged us to leave, has disclaimed the 
project,
so we’re on our own.  We maintain the software and the website, that we moved 
to gitlab.

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?

Sorry if this has gone long (I could say a lot more, too, for example how we 
could put
focus effort on new features, or providing better resources to people that need
network visualization as a service). I’m hoping you’re the right person to 
start the conversation.

Thank you for your time, and for your consideration.

Stephen North

Fwd: [RESULT] WAS Re: [VOTE] Graduate the Apache Joshua (Incubating) Project

[lewis john mcgibbney]

FYI

-- Forwarded message --
From: lewis john mcgibbney 
Date: Tue, May 1, 2018 at 7:21 PM
Subject: [RESULT] WAS Re: [VOTE] Graduate the Apache Joshua (Incubating)
Project
To: d...@joshua.incubator.apache.org, u...@joshua.incubator.apache.org


Hi Folks,
72 hours has come and gone. I am closing off this thread. Thank you to
everyone that VOTE'd. RESULT is below

[7] +1 Graduate the Apache Joshua (Incubating) Project
Rajesh Dharmadhikari
Lewis John McGibbney*
Tommaso Teofili*
Thamme Gowda*
Tom Barber*
Chris A. Mattmann*
kellen sunderland*

[0] -1 NO NOT Graduate the Apache Joshua (Incubating) Project... please
provide reasoning

* Joshua PPMC Binding

The VOTE therefore passes :)
I'll continue with the Graduation as described in the hyperlink below.
Thanks
Lewis

On Tue, Apr 24, 2018 at 10:02 PM, lewis john mcgibbney 
wrote:

> Hi Folks,
> I would like to open a VOTE for graduating the Apache Joshua (Incubating)
> project.
> For those that are interested, the Incubator guidelines on graduation can
> be found at [0].
> Joshua has been reporting to the IPMC since 16th March 2016 and made one
> Incubating release.
>
> Joshua Basics
>
>- Podling Proposal 
>- Status: current
>- Established: 2016-02-13
>- Incubating for 802 days
>- Prior Board Reports 
>
> There are a few issues to resolve before drafting the graduation
> resolution however this community VOTE is timely. The VOTE will be open at
> least 72 hours and will pass if 3 +1's are received from the Joshua PPMC.
>
> [ ] +1 Graduate the Apache Joshua (Incubating) Project
> [ ] -1 NO NOT Graduate the Apache Joshua (Incubating) Project... please
> provide reasoning
>
> P.S. Here is my binding +1
>
> [0] https://incubator.apache.org/guides/graduation.html#the_grad
> uation_process
>
>
> --
> http://home.apache.org/~lewismc/
> http://people.apache.org/keys/committer/lewismc
>



-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc



-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Fwd: [RESULT] WAS Re: [VOTE] Graduate the Apache SensSoft (Incubating) Project

[lewis john mcgibbney]

FYI

-- Forwarded message --
From: lewis john mcgibbney 
Date: Tue, May 1, 2018 at 7:37 PM
Subject: [RESULT] WAS Re: [VOTE] Graduate the Apache SensSoft (Incubating)
Project
To: d...@senssoft.incubator.apache.org, u...@senssoft.incubator.apache.org


Hi Folks,
72 hours has come and gone. I'm going to close this VOTE with the RESULT
below...
Thank you everyone that was able to VOTE

[ ] +1 Graduate the Apache SensSoft (Incubating) Project
lewis john mcgibbney*
Joshua Poore*
Rob Foley*
Laura Mariano
Arthi Vezhavendan*

[ ] -1 NO NOT Graduate the Apache SensSoft (Incubating) Project... please
provide reasoning

* SensSoft PPMC Binding

The VOTE therefore passes... :)
I'll progress with the remainder of the Graduation as per the hyperlink
below.
Best
Lewis

On Tue, Apr 24, 2018 at 10:01 PM, lewis john mcgibbney 
wrote:

> Hi Folks,
> I would like to open a VOTE for graduating the Apache SensSoft
> (Incubating) project.
> For those that are interested, the Incubator guidelines on graduation can
> be found at [0].
> SensSoft has been reporting to the IPMC since 17th August 2016 and made
> one Incubating release.
>
> SensSoft Basics
>
>- Podling Proposal 
>- Status: current
>- Established: 2016-07-13
>- Incubating for 651 days
>- Prior Board Reports
>
>
> There are a few issues to resolve before drafting the graduation
> resolution however this community VOTE is timely. The VOTE will be open at
> least 72 hours and will pass if 3 +1's are received from the SensSoft PPMC.
>
> [ ] +1 Graduate the Apache SensSoft (Incubating) Project
> [ ] -1 NO NOT Graduate the Apache SensSoft (Incubating) Project... please
> provide reasoning
>
> P.S. Here is my binding +1
>
> [0] https://incubator.apache.org/guides/graduation.html#the_grad
> uation_process
>
> --
> http://home.apache.org/~lewismc/
> http://people.apache.org/keys/committer/lewismc
>



-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc



-- 
http://home.apache.org/~lewismc/
http://people.apache.org/keys/committer/lewismc

Fwd: 404 issues

[Hen]

Apologies for my rustiness :(

Are we still able to manage a mod_rewrite configuration per project, or did
that go away?

Thanks,

Hen

-- Forwarded message --
From: Aaron Markham 
Date: Mon, Mar 5, 2018 at 3:54 PM
Subject: 404 issues
To: d...@mxnet.incubator.apache.org


I've been notified by several parties about 404s for files that are
now longer available on the site.
https://github.com/apache/incubator-mxnet/issues/9917

This page returns 404:
https://mxnet.incubator.apache.org/api/python/module.html

It was moved here:
https://mxnet.incubator.apache.org/api/python/module/module.html

There are many other examples of moved content. Some are temporarily
"fixed" via adding a meta-refresh tag in the html source for the old
pages. For example the meta tag is being used to redirect to faq, the
new location for the how_to docs.

It would seem a better solution for us is to use htaccess files and
publish persistent redirects for the new location(s) of content.

Do we have a way of pushing a config to the Apache infra to facilitate
this? I think we'd need config access if we're to put up some custom
404 pages too (which would be nicer than what we have now.)

Also, is there a good way to access the log files to get a better idea
of the 404 situation?

Cheers,
Aaron

Fwd: Two issues with license and notice auditing

[Carlos Santana]

Forwarding to Incubator mailing list to see if they any guidance.

-- Forwarded message -
From: Ying Chun Guo 
Date: Thu, Mar 1, 2018 at 10:27 PM
Subject: Two issues with license and notice auditing
To: 


Hi, team

When we are using Apache Creadur to audit licensing and notice files, we
met with two problems. I'm looking for any people who have experiences on
that.

1. Apache Rat cannot acknowledge the "minified" ASF, i.e. the short format
of Apache license header, which we plan to use in the small test files.
2. Apache Tentacles cannot support tar.gz files in the staging repo.

We have solutions to bypass these two questions. For the first issue, we
can put those files with mini headers in the Rat exclusion list. For the
second issue, we can use bash script to check LICENSE and NOTICE or we can
use zip format instead, other than tar.gz. But I would like to check if
there are any other suggestions to these issues. Thanks.

Best regards
Ying Chun Guo (Daisy)

[DISCUSS] Vote forwarding confusion (Was: Re: Fwd: [VOTE] Graduate Apache Guacamole as TLP)

[Mike Jumper]

Sounds like a good idea to me. Clicking the forward button is simple,
but the resulting list confusion outweighs that.

Forwarding in this case also confused Pony Mail, which is magically
unifying the emails from general@ into the dev@ thread, while
providing a warning in general@ that only part of the thread is shown.
The good old mod_mbox archives get the two threads right, though.

- Mike

On Fri, Oct 27, 2017 at 11:40 AM, John D. Ament <johndam...@apache.org> wrote:
>
> Thanks for pointing it out.  This tends to happen here at the incubator.
>
> I'm contemplating removing the "FWD the vote" part from
> https://incubator.apache.org/guides/graduation.html#community_graduation_vote
> to
> avoid situations like this, and instead encourage others to send an email
> to general@ indicating they're voting on graduation with a link to the vote
> in it.
>
> Thoughts?
>
> John
>
> On Fri, Oct 27, 2017 at 2:38 PM Mike Jumper <mjum...@apache.org> wrote:
>
> > I'll gladly copy these votes onto the guacamole dev@ list when the result
> > is called, but beware that this thread is not the VOTE thread. This is the
> > thread notifying the incubator general list that the community VOTE is in
> > progress.
> >
> > - Mike
> >
> > On Fri, Oct 27, 2017 at 11:11 AM, Pierre Smits <pierre.sm...@gmail.com>
> > wrote:
> >
> > > +1
> > >
> > > Best regards
> > >
> > > Pierre
> > >
> > > On Thu, 26 Oct 2017 at 14:55 Jean-Baptiste Onofré <j...@nanthrax.net>
> > wrote:
> > >
> > > > +1 (binding)
> > > >
> > > > (forwarding my vote here)
> > > >
> > > > Regards
> > > > JB
> > > >
> > > > On 10/25/2017 06:15 AM, Mike Jumper wrote:
> > > > > FYI, the community vote for graduating Apache Guacamole as TLP has
> > now
> > > > begun.
> > > > >
> > > > > Thanks,
> > > > >
> > > > > - Mike
> > > > >
> > > > > -- Forwarded message --
> > > > > From: Mike Jumper <mjum...@apache.org>
> > > > > Date: Tue, Oct 24, 2017 at 9:10 PM
> > > > > Subject: [VOTE] Graduate Apache Guacamole as TLP
> > > > > To: d...@guacamole.incubator.apache.org
> > > > >
> > > > >
> > > > > Hello all,
> > > > >
> > > > > Given the current state of the Apache Guacamole podling, positive
> > > > > discussion on this list regarding graduation [1] [2], and positive
> > > > > feedback regarding graduation in our most recent podling report [3],
> > I
> > > > > would like to begin the community VOTE for graduation of Apache
> > > > > Guacamole to TLP.
> > > > >
> > > > > The podling status page is completed and up to date, and a maturity
> > > > > evaluation has been completed and published to the website:
> > > > >
> > > > >  Podling status page:
> > > > http://incubator.apache.org/projects/guacamole.html
> > > > >  Maturity evaluation:
> > > > > http://guacamole.incubator.apache.org/maturity-evaluation/
> > > > >
> > > > > The draft resolution for establishing the Apache Guacamole TLP can be
> > > > > found at the bottom of this email. Please review the resolution and
> > > > > VOTE:
> > > > >
> > > > > [ ] +1 Graduate Apache Guacamole as TLP
> > > > > [ ] -1 Don't graduate Apache Guacamole as TLP (please provide
> > specific
> > > > comments)
> > > > >
> > > > > This is a community vote and everyone is invited to participate. PPMC
> > > > > votes should be marked binding.
> > > > >
> > > > > This vote will be open for at least 72 hours.
> > > > >
> > > > > Here is my +1 (binding).
> > > > >
> > > > > Thanks,
> > > > >
> > > > > - Mike
> > > > >
> > > > > [1]
> > > > https://lists.apache.org/thread.html/0848dd53b6acc1a0edea2eda1f3852
> > > 94eeb041a88c3d1f6221fa1ef2@%3Cdev.guacamole.apache.org%3E
> > > > > [2]
> > > > https://lists.apache.org/thread.html/a5259173a8ef4a1d2bb7be2d99d3cb
> > > c2ccf8856130ae6e3fe54e079e@%3Cdev.guacamole.apache.org%3E
> > > > > [3] https://wiki.apache.org/incubator/August2017
> > &g

Re: Fwd: [VOTE] Graduate Apache Guacamole as TLP

[John D. Ament]

Thanks for pointing it out.  This tends to happen here at the incubator.

I'm contemplating removing the "FWD the vote" part from
https://incubator.apache.org/guides/graduation.html#community_graduation_vote
to
avoid situations like this, and instead encourage others to send an email
to general@ indicating they're voting on graduation with a link to the vote
in it.

Thoughts?

John

On Fri, Oct 27, 2017 at 2:38 PM Mike Jumper <mjum...@apache.org> wrote:

> I'll gladly copy these votes onto the guacamole dev@ list when the result
> is called, but beware that this thread is not the VOTE thread. This is the
> thread notifying the incubator general list that the community VOTE is in
> progress.
>
> - Mike
>
> On Fri, Oct 27, 2017 at 11:11 AM, Pierre Smits <pierre.sm...@gmail.com>
> wrote:
>
> > +1
> >
> > Best regards
> >
> > Pierre
> >
> > On Thu, 26 Oct 2017 at 14:55 Jean-Baptiste Onofré <j...@nanthrax.net>
> wrote:
> >
> > > +1 (binding)
> > >
> > > (forwarding my vote here)
> > >
> > > Regards
> > > JB
> > >
> > > On 10/25/2017 06:15 AM, Mike Jumper wrote:
> > > > FYI, the community vote for graduating Apache Guacamole as TLP has
> now
> > > begun.
> > > >
> > > > Thanks,
> > > >
> > > > - Mike
> > > >
> > > > -- Forwarded message --
> > > > From: Mike Jumper <mjum...@apache.org>
> > > > Date: Tue, Oct 24, 2017 at 9:10 PM
> > > > Subject: [VOTE] Graduate Apache Guacamole as TLP
> > > > To: d...@guacamole.incubator.apache.org
> > > >
> > > >
> > > > Hello all,
> > > >
> > > > Given the current state of the Apache Guacamole podling, positive
> > > > discussion on this list regarding graduation [1] [2], and positive
> > > > feedback regarding graduation in our most recent podling report [3],
> I
> > > > would like to begin the community VOTE for graduation of Apache
> > > > Guacamole to TLP.
> > > >
> > > > The podling status page is completed and up to date, and a maturity
> > > > evaluation has been completed and published to the website:
> > > >
> > > >  Podling status page:
> > > http://incubator.apache.org/projects/guacamole.html
> > > >  Maturity evaluation:
> > > > http://guacamole.incubator.apache.org/maturity-evaluation/
> > > >
> > > > The draft resolution for establishing the Apache Guacamole TLP can be
> > > > found at the bottom of this email. Please review the resolution and
> > > > VOTE:
> > > >
> > > > [ ] +1 Graduate Apache Guacamole as TLP
> > > > [ ] -1 Don't graduate Apache Guacamole as TLP (please provide
> specific
> > > comments)
> > > >
> > > > This is a community vote and everyone is invited to participate. PPMC
> > > > votes should be marked binding.
> > > >
> > > > This vote will be open for at least 72 hours.
> > > >
> > > > Here is my +1 (binding).
> > > >
> > > > Thanks,
> > > >
> > > > - Mike
> > > >
> > > > [1]
> > > https://lists.apache.org/thread.html/0848dd53b6acc1a0edea2eda1f3852
> > 94eeb041a88c3d1f6221fa1ef2@%3Cdev.guacamole.apache.org%3E
> > > > [2]
> > > https://lists.apache.org/thread.html/a5259173a8ef4a1d2bb7be2d99d3cb
> > c2ccf8856130ae6e3fe54e079e@%3Cdev.guacamole.apache.org%3E
> > > > [3] https://wiki.apache.org/incubator/August2017
> > > >
> > > > --
> > > >
> > > > Establish the Apache Guacamole Project
> > > >
> > > > WHEREAS, the Board of Directors deems it to be in the best interests
> of
> > > > the Foundation and consistent with the Foundation's purpose to
> > establish
> > > > a Project Management Committee charged with the creation and
> > maintenance
> > > > of open-source software, for distribution at no charge to the public,
> > > > related to providing performant, browser-based remote access.
> > > >
> > > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > > (PMC), to be known as the "Apache Guacamole Project", be and hereby
> is
> > > > established pursuant to Bylaws of the Foundation; and be it further
> > > >
> > > > RESOLVED, that the Apache Guacam

Re: Fwd: [VOTE] Graduate Apache Guacamole as TLP

[Mike Jumper]

I'll gladly copy these votes onto the guacamole dev@ list when the result
is called, but beware that this thread is not the VOTE thread. This is the
thread notifying the incubator general list that the community VOTE is in
progress.

- Mike

On Fri, Oct 27, 2017 at 11:11 AM, Pierre Smits 
wrote:

> +1
>
> Best regards
>
> Pierre
>
> On Thu, 26 Oct 2017 at 14:55 Jean-Baptiste Onofré  wrote:
>
> > +1 (binding)
> >
> > (forwarding my vote here)
> >
> > Regards
> > JB
> >
> > On 10/25/2017 06:15 AM, Mike Jumper wrote:
> > > FYI, the community vote for graduating Apache Guacamole as TLP has now
> > begun.
> > >
> > > Thanks,
> > >
> > > - Mike
> > >
> > > -- Forwarded message --
> > > From: Mike Jumper 
> > > Date: Tue, Oct 24, 2017 at 9:10 PM
> > > Subject: [VOTE] Graduate Apache Guacamole as TLP
> > > To: d...@guacamole.incubator.apache.org
> > >
> > >
> > > Hello all,
> > >
> > > Given the current state of the Apache Guacamole podling, positive
> > > discussion on this list regarding graduation [1] [2], and positive
> > > feedback regarding graduation in our most recent podling report [3], I
> > > would like to begin the community VOTE for graduation of Apache
> > > Guacamole to TLP.
> > >
> > > The podling status page is completed and up to date, and a maturity
> > > evaluation has been completed and published to the website:
> > >
> > >  Podling status page:
> > http://incubator.apache.org/projects/guacamole.html
> > >  Maturity evaluation:
> > > http://guacamole.incubator.apache.org/maturity-evaluation/
> > >
> > > The draft resolution for establishing the Apache Guacamole TLP can be
> > > found at the bottom of this email. Please review the resolution and
> > > VOTE:
> > >
> > > [ ] +1 Graduate Apache Guacamole as TLP
> > > [ ] -1 Don't graduate Apache Guacamole as TLP (please provide specific
> > comments)
> > >
> > > This is a community vote and everyone is invited to participate. PPMC
> > > votes should be marked binding.
> > >
> > > This vote will be open for at least 72 hours.
> > >
> > > Here is my +1 (binding).
> > >
> > > Thanks,
> > >
> > > - Mike
> > >
> > > [1]
> > https://lists.apache.org/thread.html/0848dd53b6acc1a0edea2eda1f3852
> 94eeb041a88c3d1f6221fa1ef2@%3Cdev.guacamole.apache.org%3E
> > > [2]
> > https://lists.apache.org/thread.html/a5259173a8ef4a1d2bb7be2d99d3cb
> c2ccf8856130ae6e3fe54e079e@%3Cdev.guacamole.apache.org%3E
> > > [3] https://wiki.apache.org/incubator/August2017
> > >
> > > --
> > >
> > > Establish the Apache Guacamole Project
> > >
> > > WHEREAS, the Board of Directors deems it to be in the best interests of
> > > the Foundation and consistent with the Foundation's purpose to
> establish
> > > a Project Management Committee charged with the creation and
> maintenance
> > > of open-source software, for distribution at no charge to the public,
> > > related to providing performant, browser-based remote access.
> > >
> > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > > (PMC), to be known as the "Apache Guacamole Project", be and hereby is
> > > established pursuant to Bylaws of the Foundation; and be it further
> > >
> > > RESOLVED, that the Apache Guacamole Project be and hereby is
> responsible
> > > for the creation and maintenance of software related to providing
> > > performant, browser-based remote access; and be it further
> > >
> > > RESOLVED, that the office of "Vice President, Apache Guacamole" 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
> Guacamole
> > > Project, and to have primary responsibility for management of the
> > > projects within the scope of responsibility of the Apache Guacamole
> > > 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 Guacamole
> > > Project:
> > >
> > >   * Carl Harris  
> > >   * Daniel Gruno 
> > >   * Frode Langelo
> > >   * Greg Trasuk  
> > >   * James Muehlner   
> > >   * Jean-Baptiste Onofré 
> > >   * Jim Jagielski
> > >   * Mike Jumper  
> > >   * Nick Couchman
> > >   * Olivier Lamy 
> > >
> > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mike Jumper be appointed
> to
> > > the office of Vice President, Apache Guacamole, 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 

Re: Fwd: [VOTE] Graduate Apache Guacamole as TLP

[Pierre Smits]

+1

Best regards

Pierre

On Thu, 26 Oct 2017 at 14:55 Jean-Baptiste Onofré  wrote:

> +1 (binding)
>
> (forwarding my vote here)
>
> Regards
> JB
>
> On 10/25/2017 06:15 AM, Mike Jumper wrote:
> > FYI, the community vote for graduating Apache Guacamole as TLP has now
> begun.
> >
> > Thanks,
> >
> > - Mike
> >
> > -- Forwarded message --
> > From: Mike Jumper 
> > Date: Tue, Oct 24, 2017 at 9:10 PM
> > Subject: [VOTE] Graduate Apache Guacamole as TLP
> > To: d...@guacamole.incubator.apache.org
> >
> >
> > Hello all,
> >
> > Given the current state of the Apache Guacamole podling, positive
> > discussion on this list regarding graduation [1] [2], and positive
> > feedback regarding graduation in our most recent podling report [3], I
> > would like to begin the community VOTE for graduation of Apache
> > Guacamole to TLP.
> >
> > The podling status page is completed and up to date, and a maturity
> > evaluation has been completed and published to the website:
> >
> >  Podling status page:
> http://incubator.apache.org/projects/guacamole.html
> >  Maturity evaluation:
> > http://guacamole.incubator.apache.org/maturity-evaluation/
> >
> > The draft resolution for establishing the Apache Guacamole TLP can be
> > found at the bottom of this email. Please review the resolution and
> > VOTE:
> >
> > [ ] +1 Graduate Apache Guacamole as TLP
> > [ ] -1 Don't graduate Apache Guacamole as TLP (please provide specific
> comments)
> >
> > This is a community vote and everyone is invited to participate. PPMC
> > votes should be marked binding.
> >
> > This vote will be open for at least 72 hours.
> >
> > Here is my +1 (binding).
> >
> > Thanks,
> >
> > - Mike
> >
> > [1]
> https://lists.apache.org/thread.html/0848dd53b6acc1a0edea2eda1f385294eeb041a88c3d1f6221fa1ef2@%3Cdev.guacamole.apache.org%3E
> > [2]
> https://lists.apache.org/thread.html/a5259173a8ef4a1d2bb7be2d99d3cbc2ccf8856130ae6e3fe54e079e@%3Cdev.guacamole.apache.org%3E
> > [3] https://wiki.apache.org/incubator/August2017
> >
> > --
> >
> > Establish the Apache Guacamole Project
> >
> > WHEREAS, the Board of Directors deems it to be in the best interests of
> > the Foundation and consistent with the Foundation's purpose to establish
> > a Project Management Committee charged with the creation and maintenance
> > of open-source software, for distribution at no charge to the public,
> > related to providing performant, browser-based remote access.
> >
> > NOW, THEREFORE, BE IT RESOLVED, that a Project Management Committee
> > (PMC), to be known as the "Apache Guacamole Project", be and hereby is
> > established pursuant to Bylaws of the Foundation; and be it further
> >
> > RESOLVED, that the Apache Guacamole Project be and hereby is responsible
> > for the creation and maintenance of software related to providing
> > performant, browser-based remote access; and be it further
> >
> > RESOLVED, that the office of "Vice President, Apache Guacamole" 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 Guacamole
> > Project, and to have primary responsibility for management of the
> > projects within the scope of responsibility of the Apache Guacamole
> > 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 Guacamole
> > Project:
> >
> >   * Carl Harris  
> >   * Daniel Gruno 
> >   * Frode Langelo
> >   * Greg Trasuk  
> >   * James Muehlner   
> >   * Jean-Baptiste Onofré 
> >   * Jim Jagielski
> >   * Mike Jumper  
> >   * Nick Couchman
> >   * Olivier Lamy 
> >
> > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mike Jumper be appointed to
> > the office of Vice President, Apache Guacamole, 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 Guacamole 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 Guacamole Project;
> > and be it further
> >
> > RESOLVED, that the Apache Guacamole Project be and hereby is tasked with
> > the migration and rationalization of the Apache Incubator Guacamole
> > podling; and be it further
> >
> > RESOLVED, that all responsibilities pertaining to the Apache Incubator
> > Guacamole podling encumbered upon the Apache Incubator PMC are hereafter
> > discharged.
> >
> > 

Re: Fwd: [VOTE] Graduate Apache Guacamole as TLP

[Jean-Baptiste Onofré]

+1 (binding)

(forwarding my vote here)

Regards
JB

On 10/25/2017 06:15 AM, Mike Jumper wrote:

FYI, the community vote for graduating Apache Guacamole as TLP has now begun.

Thanks,

- Mike

-- Forwarded message --
From: Mike Jumper 
Date: Tue, Oct 24, 2017 at 9:10 PM
Subject: [VOTE] Graduate Apache Guacamole as TLP
To: d...@guacamole.incubator.apache.org


Hello all,

Given the current state of the Apache Guacamole podling, positive
discussion on this list regarding graduation [1] [2], and positive
feedback regarding graduation in our most recent podling report [3], I
would like to begin the community VOTE for graduation of Apache
Guacamole to TLP.

The podling status page is completed and up to date, and a maturity
evaluation has been completed and published to the website:

 Podling status page: http://incubator.apache.org/projects/guacamole.html
 Maturity evaluation:
http://guacamole.incubator.apache.org/maturity-evaluation/

The draft resolution for establishing the Apache Guacamole TLP can be
found at the bottom of this email. Please review the resolution and
VOTE:

[ ] +1 Graduate Apache Guacamole as TLP
[ ] -1 Don't graduate Apache Guacamole as TLP (please provide specific comments)

This is a community vote and everyone is invited to participate. PPMC
votes should be marked binding.

This vote will be open for at least 72 hours.

Here is my +1 (binding).

Thanks,

- Mike

[1] 
https://lists.apache.org/thread.html/0848dd53b6acc1a0edea2eda1f385294eeb041a88c3d1f6221fa1ef2@%3Cdev.guacamole.apache.org%3E
[2] 
https://lists.apache.org/thread.html/a5259173a8ef4a1d2bb7be2d99d3cbc2ccf8856130ae6e3fe54e079e@%3Cdev.guacamole.apache.org%3E
[3] https://wiki.apache.org/incubator/August2017

--

Establish the Apache Guacamole Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to providing performant, browser-based remote access.

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

RESOLVED, that the Apache Guacamole Project be and hereby is responsible
for the creation and maintenance of software related to providing
performant, browser-based remote access; and be it further

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

  * Carl Harris  
  * Daniel Gruno 
  * Frode Langelo
  * Greg Trasuk  
  * James Muehlner   
  * Jean-Baptiste Onofré 
  * Jim Jagielski
  * Mike Jumper  
  * Nick Couchman
  * Olivier Lamy 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mike Jumper be appointed to
the office of Vice President, Apache Guacamole, 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 Guacamole 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 Guacamole Project;
and be it further

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

RESOLVED, that all responsibilities pertaining to the Apache Incubator
Guacamole 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



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

Fwd: [VOTE] Graduate Apache Guacamole as TLP

[Mike Jumper]

FYI, the community vote for graduating Apache Guacamole as TLP has now begun.

Thanks,

- Mike

-- Forwarded message --
From: Mike Jumper 
Date: Tue, Oct 24, 2017 at 9:10 PM
Subject: [VOTE] Graduate Apache Guacamole as TLP
To: d...@guacamole.incubator.apache.org


Hello all,

Given the current state of the Apache Guacamole podling, positive
discussion on this list regarding graduation [1] [2], and positive
feedback regarding graduation in our most recent podling report [3], I
would like to begin the community VOTE for graduation of Apache
Guacamole to TLP.

The podling status page is completed and up to date, and a maturity
evaluation has been completed and published to the website:

Podling status page: http://incubator.apache.org/projects/guacamole.html
Maturity evaluation:
http://guacamole.incubator.apache.org/maturity-evaluation/

The draft resolution for establishing the Apache Guacamole TLP can be
found at the bottom of this email. Please review the resolution and
VOTE:

[ ] +1 Graduate Apache Guacamole as TLP
[ ] -1 Don't graduate Apache Guacamole as TLP (please provide specific comments)

This is a community vote and everyone is invited to participate. PPMC
votes should be marked binding.

This vote will be open for at least 72 hours.

Here is my +1 (binding).

Thanks,

- Mike

[1] 
https://lists.apache.org/thread.html/0848dd53b6acc1a0edea2eda1f385294eeb041a88c3d1f6221fa1ef2@%3Cdev.guacamole.apache.org%3E
[2] 
https://lists.apache.org/thread.html/a5259173a8ef4a1d2bb7be2d99d3cbc2ccf8856130ae6e3fe54e079e@%3Cdev.guacamole.apache.org%3E
[3] https://wiki.apache.org/incubator/August2017

--

Establish the Apache Guacamole Project

WHEREAS, the Board of Directors deems it to be in the best interests of
the Foundation and consistent with the Foundation's purpose to establish
a Project Management Committee charged with the creation and maintenance
of open-source software, for distribution at no charge to the public,
related to providing performant, browser-based remote access.

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

RESOLVED, that the Apache Guacamole Project be and hereby is responsible
for the creation and maintenance of software related to providing
performant, browser-based remote access; and be it further

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

 * Carl Harris  
 * Daniel Gruno 
 * Frode Langelo
 * Greg Trasuk  
 * James Muehlner   
 * Jean-Baptiste Onofré 
 * Jim Jagielski
 * Mike Jumper  
 * Nick Couchman
 * Olivier Lamy 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Mike Jumper be appointed to
the office of Vice President, Apache Guacamole, 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 Guacamole 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 Guacamole Project;
and be it further

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

RESOLVED, that all responsibilities pertaining to the Apache Incubator
Guacamole 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

Fwd: [VOTE] Resolution to create a TLP from graduating Incubator podling (PredictionIO)

[Donald Szeto]

Hi all,

The PredictionIO podling community has started a community graduation vote.
I am forwarding the thread to general@ per graduation instructions for
visibility.

Regards,
Donald

-- Forwarded message --
From: Donald Szeto 
Date: Mon, Sep 25, 2017 at 8:50 PM
Subject: [VOTE] Resolution to create a TLP from graduating Incubator podling
To: d...@predictionio.incubator.apache.org


Hi all,

Based on previous discussions (https://lists.apache.org/thread.html/
2b4ef7c394584988cf0c99920824afaa60ee4c648d5c0069b1bf55c0@%
3Cdev.predictionio.apache.org%3E and https://lists.apache.org/thread.html/
1b06e510773ee1d315728e0ce25f220c9cf7d9e8ad601ec9dba4fe1d@%
3Cdev.predictionio.apache.org%3E), I would like to start a formal vote on
graduating PredictionIO from an Incubator podling to a top level project
with the following resolution. This thread will be forwarded to the
Incubator general mailing list.

Once again, Salesforce has already signed and executed an assignment
agreement to assign the PredictionIO mark to ASF.

The graduation process we are following is described here:
http://incubator.apache.org/guides/graduation.html

Once this vote passes, a discussion will be started on Incubator general,
followed by a vote when a consensus there would be arrived. The vote will
run for at least 72 hours before closing at 9PM PST on 9/28/2017.

Thank you all! Let's graduate.

+1 (binding) from me.

Regards,
Donald

-

X. Establish the Apache PredictionIO 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 machine learning server built on top of
   state-of-the-art open source stack, that enables developers to manage
   and deploy production-ready predictive services for various kinds of
   machine learning tasks.

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

   RESOLVED, that the Apache PredictionIO Project be and hereby is
   responsible for the creation and maintenance of software
   related to a machine learning server built on top of
   state-of-the-art open source stack, that enables developers to manage
   and deploy production-ready predictive services for various kinds of
   machine learning tasks;
   and be it further

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

 * Alex Merritt 
 * Andrew Kyle Purtell 
 * Chan Lee 
 * Donald Szeto 
 * Felipe Oliveira 
 * James Taylor 
 * Justin Yip 
 * Kenneth Chan 
 * Lars Hofhansl 
 * Lee Moon Soo 
 * Luciano Resende 
 * Marcin Ziemiński 
 * Marco Vivero 
 * Mars Hall 
 * Matthew Tovbin 
 * Naoki Takezoe 
 * Pat Ferrel 
 * Paul Li 
 * Shinsuke Sugaya 
 * Simon Chan 
 * Takahiro Hagino 
 * Takako Shimamoto 
 * Tamas Jambor 
 * Tom Chan 
 * Vitaly Gordon 
 * Xiangrui Meng 
 * Xusen Yin 
 * Yevgeny Khodorkovsky 

   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Donald Szeto
   be appointed to the office of Vice President, Apache PredictionIO, 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

   

Fwd: [DRAFT] Incubator PMC Board Report - September 2017

[P. Taylor Goetz]

Forgot to cc general@...

Begin forwarded message:

> From: "P. Taylor Goetz" 
> Date: September 12, 2017 at 8:10:55 PM EDT
> To: d...@pulsar.incubator.apache.org
> Subject: Re: [DRAFT] Incubator PMC Board Report - September 2017
> 
> I'll also sign off/comment on Heron and Pulsar shortly.
> 
>> On Sep 12, 2017, at 6:02 PM, Dave Fisher  wrote:
>> 
>> Pulsar is now signed off and also shepherd notes done.
>> 
>> Heron is a little slow moving over should we keep them monthly until the 
>> repos is moved?
> 
> In my opinion, yes. Will comment on the report.
> 
>> 
>> Regards,
>> Dave
>> 
> 
> -Taylor
> 
>>> On Sep 12, 2017, at 2:40 PM, Dave Fisher  wrote:
>>> 
>>> I'll be signing Pulsar shortly.
>>> 
>>> Sent from my iPhone
 

Fwd: [VOTE] Graduate Mnemonic to TLP

[Gang(Gary) Wang]

Hi everyone,

Our community graduation vote has been concluded, I'm so sorry for the late
notification.

Here is the vote result thread in the Dev list:
https://lists.apache.org/thread.html/bbc187108b73d57fddec0d6a6c2945
27b626c7c439a7cdab991ea84e@%3Cdev.mnemonic.apache.org%3E

and the vote thread:
https://lists.apache.org/thread.html/a49e82d507bb00839413e90b05cb8b
9448ea242aeb021622f5deb323@%3Cdev.mnemonic.apache.org%3E

Thanks!

Gary
-- Forwarded message --
From: Gang(Gary) Wang 
Date: Thu, Sep 7, 2017 at 3:00 PM
Subject: [VOTE] Graduate Mnemonic to TLP
To: d...@mnemonic.incubator.apache.org


Please vote on this community resolution to seek graduation to TLP for
Mnemonic.

This vote will be open for ~72 hours and passes if a majority of at least
three +1 Apache Mnemonic PPMC votes are cast.

[ ] +1 Proceed with graduation process
[ ] 0 I don't feel strongly about it, but don't object
[ ] -1 Do not proceed yet because…

Fwd: [VOTE] Apache DataFu graduation proposal

[Matthew Hayes]

FYI, the community vote is starting.

Thanks,
Matt

-- Forwarded message --
From: Matthew Hayes 
Date: Fri, Jul 28, 2017 at 5:49 PM
Subject: [VOTE] Apache DataFu graduation proposal
To: DataFu 


Hi all,

Given the positive discussion about Apache DataFu graduating from
Incubator, I would like to open a vote.  Referring to the checklist at
https://incubator.apache.org/guides/graduation.html#graduation_check_list,

   - Status file at http://incubator.apache.org/projects/datafu.html is up
   to date
   - Podling name search for DataFu was completed https://issues.apach
   e.org/jira/browse/PODLINGNAMESEARCH-48
   
   - Demonstrated Apache releases through releasing 1.3.0, 1.3.1, and 1.3.2
   - Community seems ready to graduate according to
   https://cwiki.apache.org/confluence/display/DATAFU/Maturity+Evaluation
   
   - I don't know of any remaining issues from mentors or IPMC

I propose that Apache DataFu graduate from incubator and become a top-level
project.  The proposed graduation resolution can be found at
https://cwiki.apache.org/confluence/display/DATAFU/Graduation+Resolution.

The vote will be open for 72 hours (ends on July 31st 6 pm PST).

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

My vote: +1

If this vote passes then the next step is an Incubator PMC vote.  I will
forward this email to the Incubator general list as an FYI that the vote is
taking place.

-Matt

Fwd: [VOTE] Publish Apache Edgent 1.1.0-incubating (RC1)

[Dale LaBossiere]

… just a ping for IPMC input on this VOTE thread [1]
Thanks in advance for your assistance!

— Dale

[1] https://www.mail-archive.com/general@incubator.apache.org/msg58842.html 


> Begin forwarded message:
> 
> From: Dale LaBossiere 
> Subject: [VOTE] Publish Apache Edgent 1.1.0-incubating (RC1)
> Date: March 5, 2017 at 7:58:48 AM EST
> To: general@incubator.apache.org
> Cc: d...@edgent.apache.org
> Reply-To: d...@edgent.apache.org
> 
> The Apache Edgent community approved a vote to release
> Apache Edgent 1.1.0-incubating from RC1.
> 
> Per [1] we are requesting IPMC approval to publish the
> release bundles on the distribution site [2].
> 
> This vote will be open for 120 hours (I’m on vacation :-)
> 
> - 1.1.0-incubating-RC1 vote results / thread [3]
> - Git hash and tag for the release
>  commit: 4744f56
>  tag: 1.1.0-incubating-RC1
>  link to RC1 source in the git repository [4]
> - links to RC1 artifacts [5]
> 
> [ ]  +1 accept
> [ ]  -1 reject (explanation required)
> 
> Thanks for your assistance in achieving this milestone!
> 
> [1] policy 
> http://incubator.apache.org/incubation/Incubation_Policy.html#Releases
> [2] distribution https://dist.apache.org/repos/dist/release/incubator/edgent/
> [3] rc1 vote https://www.mail-archive.com/dev@edgent.apache.org/msg01477.html 
> 
> [4] rc1 src repo 
> https://github.com/apache/incubator-edgent/tree/1.1.0-incubating-RC1 
> 
> [5] rc1 artifacts 
> https://dist.apache.org/repos/dist/dev/incubator/edgent/1.1.0-incubating/rc1/

Fwd: Github Mirroring currently broken

[siddharth anand]

FYI!
Several projects have already reported this (e.g. Nifi, spark website,
brooklyn-server, carbondata, zeppelin, etc...) -- but Apache github
mirroring broke yesterday (Saturday)... and it's a blocker for (every?)
incubator project on Github currently. Hoping it gets resolved soon.

-s


-- Forwarded message --
From: siddharth anand 
Date: Sun, Nov 20, 2016 at 12:10 PM
Subject: Github Mirroring currently broken
To: d...@airflow.incubator.apache.org


Committers/Maintainers,
The Apache Airflow Github mirror is not synchronizing. I've filed a ticket.
It looks like, as of now, 2 other Apache projects (nifi & brooklyn-server)
have reported the same issue.

https://issues.apache.org/jira/browse/INFRA-12949

This means that although we are successfully merging to Apache master at
https://git-wip-us.apache.org/repos/asf/incubator-airflow.git, the changes
are not being mirrored to g...@github.com:apache/incubator-airflow.git. This
affects things like rebasing of PRs.. and I've opened the tickets at a
Blocker.

-s

Fwd: Apache Big Data EU - Discussion Lounge available for after-session discussion & project meetings

[Greg Chase]

Passing this offer on to podlings that would be interested to host an
introductory discussion about their community at Apache Big Data

-- Forwarded message --
From: Gregory Chase 
Date: Sun, Nov 13, 2016 at 5:10 AM
Subject: Apache Big Data EU - Discussion Lounge available for after-session
discussion & project meetings
To: d...@community.apache.org


Dear Apache Big Data Community,

ODPi.org is sponsoring a Community Lounge that anyone is welcome to use as
a place for short discussions.  This is a great way to have an extended Q
session after your talk, or to have a short meeting of your project
community.

Sign up now for a 30 minute slot.  The current schedule is posted here:
https://www.odpi.org/blog

We have lots of time available tomorrow, Monday, and Tuesday.

-Greg

--
Greg Chase

Global Head, Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Fwd: New git mirror created: incubator.git

[Roman Shaposhnik]

What's the plan for the website migration? When do we plan to cut over?

Thanks,
Roman.

-- Forwarded message --
From:  
Date: Mon, Nov 7, 2016 at 9:25 PM
Subject: New git mirror created: incubator.git
To: infrastruct...@apache.org, priv...@incubator.apache.org


New repository incubator.git was mirrored to git.a.o (and thus
GitHub), as requested by johndament.
New mirrors are available on GitHub no more than 24 hours later.

With regards,
Apache Infrastructure.

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

Re: Fwd: [VOTE] Release SAMOA 0.4.0 (incubating) RC1

[Jean-Baptiste Onofré]

+1 (binding)

Checked:
- Build OK
- LICENSE, DISCLAIMER, NOTICE look good
- Signatures OK
- ASF headers present

Regards
JB

On 09/19/2016 03:50 PM, Nicolas Kourtellis wrote:

Hi all,

Our new release has been voted from the Apache SAMOA team and we are
opening the vote to the incubator email list for testing.

Please vote on releasing the following release candidate as Apache
SAMOA (incubating)
version 0.4.0. This release will be the second release for SAMOA in the
incubator.

-
The commit to be voted on is in the branch "releases/0.4.0-incubating"
(commit fc39238dd7d3674c069a8142312da8c1812bc907):
https://git1-us-west.apache.org/repos/asf/incubator-samoa/
repo?p=incubator-samoa.git;a=commit;h=fc39238dd7d3674c069a8142312da8
c1812bc907

Tag v0.4.0-incubating:
https://git1-us-west.apache.org/repos/asf/incubator-samoa/
repo?p=incubator-samoa.git;a=tag;h=aa5bd941ccbed1aabb46b8119049ac1bb293c3a2

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

The staging repository for this release can be found at:
https://repository.apache.org/content/repositories/staging/
org/apache/samoa/samoa/0.4.0-incubating/

The developer's version artifacts:
https://dist.apache.org/repos/dist/dev/incubator/samoa/0.4.0-incubating-rc1/

-

Please vote on releasing this package as Apache SAMOA 0.4.0 (incubating).

The vote is open for the next 72 hours and passes if a majority of at least
three +1 PPMC votes are cast.

[ ] +1 Release this package as Apache SAMOA 0.4.0 (incubating)
[ ] -1 Do not release this package because ...

I'm +1 on the release.

Cheers,

Nicolas





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

Fwd: [VOTE] Apache BatchEE 0.4-incubating

[Romain Manni-Bucau]

Hi general@!

FYI the BatchEE incubation project is votiing on batchee 0.4-incubating

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Wordpress Blog
 | Github  |
LinkedIn  | Tomitriber
 | JavaEE Factory


-- Forwarded message --
From: Romain Manni-Bucau 
Date: 2016-09-22 18:16 GMT+02:00
Subject: [VOTE] Apache BatchEE 0.4-incubating
To: "d...@batchee.incubator.apache.org" 


Hi guys,

we discussed it several time so here it is: the vote for batchee N+1

Here is the release note: https://issues.apache.org/jira/secure/ReleaseNote.
jspa?projectId=12314924=12334147

Staging repo: https://repository.apache.org/content/repositories/
orgapachebatchee-1004/ (yes numbers are funny sometimes ;))

Source zip: https://repository.apache.org/content/repositories/
orgapachebatchee-1004/org/apache/batchee/batchee/0.4-incubating/batchee-0.4-
incubating-source-release.zip

Tag: https://github.com/rmannibucau/incubator-batchee/
tree/batchee-0.4-incubating

My gpg key is in tomee KEYS file (https://dist.apache.org/
repos/dist/release/tomee/KEYS) - didn't find the batchee one ATM

Please VOTE
[+1] yep
[+0] don’t care
[-1] no cause [...]

The VOTE is open for 72h

Thanks,
Romain Manni-Bucau
@rmannibucau  |  Blog
 | Old Wordpress Blog
 | Github  |
LinkedIn  | Tomitriber
 | JavaEE Factory

Fwd: [VOTE] Release SAMOA 0.4.0 (incubating) RC1

[Nicolas Kourtellis]

Hi all,

Our new release has been voted from the Apache SAMOA team and we are
opening the vote to the incubator email list for testing.

Please vote on releasing the following release candidate as Apache
SAMOA (incubating)
version 0.4.0. This release will be the second release for SAMOA in the
incubator.

-
The commit to be voted on is in the branch "releases/0.4.0-incubating"
(commit fc39238dd7d3674c069a8142312da8c1812bc907):
https://git1-us-west.apache.org/repos/asf/incubator-samoa/
repo?p=incubator-samoa.git;a=commit;h=fc39238dd7d3674c069a8142312da8
c1812bc907

Tag v0.4.0-incubating:
https://git1-us-west.apache.org/repos/asf/incubator-samoa/
repo?p=incubator-samoa.git;a=tag;h=aa5bd941ccbed1aabb46b8119049ac1bb293c3a2

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

The staging repository for this release can be found at:
https://repository.apache.org/content/repositories/staging/
org/apache/samoa/samoa/0.4.0-incubating/

The developer's version artifacts:
https://dist.apache.org/repos/dist/dev/incubator/samoa/0.4.0-incubating-rc1/

-

Please vote on releasing this package as Apache SAMOA 0.4.0 (incubating).

The vote is open for the next 72 hours and passes if a majority of at least
three +1 PPMC votes are cast.

[ ] +1 Release this package as Apache SAMOA 0.4.0 (incubating)
[ ] -1 Do not release this package because ...

I'm +1 on the release.

Cheers,

Nicolas



-- 
Nicolas Kourtellis

Fwd: [VOTE] Retire Apache Streams to the attic

[Ate Douma]

FYI, I've started below vote to retire Apache Streams, after I first initiated a
[discuss] thread more than a week ago, which resulted in zero feedback.

Ate
(Streams mentor)

 Forwarded Message 
Subject: [VOTE] Retire Apache Streams to the attic
Date: Sun, 18 Sep 2016 23:27:11 +0200
From: Ate Douma 
To: d...@streams.incubator.apache.org 

As a final follow up on the earlier [discuss] thread, lets formally vote on
retiring Apache Streams and move it to the attic.

The process is described at http://attic.apache.org/process.html

[ ] +1 Move Streams to the Attic
[ ] ±0 Proceed according to the majority
[ ] -1 Do not move Streams to the Attic, because... [please add justification]

Ate



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

Fwd: [VOTE] Release Apache Beam, version 0.2.0-incubating

[P. Taylor Goetz]

FYI. Had the same address issue. 


Begin forwarded message:

> From: "P. Taylor Goetz" 
> Date: August 5, 2016 at 10:45:21 AM EDT
> To: gene...@apache.incubator.org
> Cc: d...@beam.incubator.apache.org
> Subject: Re: [VOTE] Release Apache Beam, version 0.2.0-incubating
> 
> +1 (binding)
> 
> - built from source
> - “incubating” in file name
> - NOTICE and LICENSE look good
> - license headers present
> - no wayward binaries
> - signatures check out
> 
> -Taylor
> 
>> On Aug 1, 2016, at 12:46 PM, Dan Halperin  
>> wrote:
>> 
>> Hey folks!
>> 
>> Here's the vote for the second release of Apache Beam: version
>> 0.2.0-incubating.
>> 
>> The complete staging area is available for your review, which includes:
>> * the official Apache source release to be deployed to dist.apache.org [1],
>> and
>> * all artifacts to be deployed to the Maven Central Repository [2].
>> 
>> This corresponds to the tag "v0.2.0-incubating-RC2" in source control, [3].
>> 
>> New for this release:
>> * Release notes are available in JIRA [4].
>> * We made sure to address all the issues that the Apache Incubator PMC
>> raised in the previous release [5].
>> 
>> The Apache Beam community has unanimously approved this release: [6], [7].
>> 
>> Please vote as follows:
>> [ ] +1, Approve the release
>> [ ] -1, Do not approve the release (please provide specific comments)
>> 
>> Thanks,
>> Dan
>> 
>> As customary, the vote will be open for at least 72 hours. It is adopted by
>> a majority approval with at least three PMC affirmative votes. If approved,
>> we will proceed with the release.
>> 
>> [1]https://dist.apache.org/repos/dist/dev/incubator/beam/0.2.0-incubating/RC2/
>> [2] https://repository.apache.org/content/repositories/orgapachebeam-1004/
>> [3] https://github.com/apache/incubator-beam/tree/v0.2.0-incubating-RC2
>> [4]https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12319527=12335766
>> [5] Thread 
>> afterhttp://mail-archives.apache.org/mod_mbox/incubator-general/201606.mbox/%3CCAMdX748VZg5-p%3D5x63se-iBZU0e32n20aRyVsDPWhWZaoq7SoA%40mail.gmail.com%3E
>> [6]http://mail-archives.apache.org/mod_mbox/incubator-beam-dev/201607.mbox/%3CCAA8k_FJeyg%2BGWUBMeSPFQhnaPN3V4MrenJtrDbiyXyKJkzH7ZA%40mail.gmail.com%3E
>> [7] 
>> http://mail-archives.apache.org/mod_mbox/incubator-beam-dev/201607.mbox/browser
> 

Fwd: Warning from d...@juneau.incubator.apache.org

[James Bognar]

Anyone know what exactly these warning messages are that I occasionally
get?  As far as I can tell, I am still receiving the messages that ezmlm
says are bouncing.

-- Forwarded message --
From: 
Date: Sat, Jul 9, 2016 at 11:38 AM
Subject: Warning from d...@juneau.incubator.apache.org
To: james.bog...@salesforce.com


Hi! This is the ezmlm program. I'm managing the
d...@juneau.incubator.apache.org mailing list.

I'm working for my owner, who can be reached
at dev-ow...@juneau.incubator.apache.org.


Messages to you from the dev mailing list seem to
have been bouncing. I've attached a copy of the first bounce
message I received.

If this message bounces too, I will send you a probe. If the probe bounces,
I will remove your address from the dev mailing list,
without further notice.


I've kept a list of which messages from the dev mailing list have
bounced from your address.

Copies of these messages may be in the archive.
To retrieve a set of messages 123-145 (a maximum of 100 per request),
send a short message to:
   

To receive a subject and author list for the last 100 or so messages,
send a short message to:
   

Here are the message numbers:

   4
   6
   9
   10
   12
   13
   15
   17
   20
   24
   25
   26
   31
   34
   35
   48
   50
   52
   54
   56
   60
   63
   65
   67
   68
   73
   76
   80

--- Enclosed is a copy of the bounce message I received.

Return-Path: <>
Received: (qmail 32561 invoked by uid 99); 27 Jun 2016 14:20:33 -
Received: from pnap-us-west-generic-nat.apache.org (HELO
spamd4-us-west.apache.org) (209.188.14.142)
by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 27 Jun 2016 14:20:33 +
Received: from localhost (localhost [127.0.0.1])
by spamd4-us-west.apache.org (ASF Mail Server at
spamd4-us-west.apache.org) with ESMTP id 283BEC0439
for ; Mon, 27 Jun 2016 14:20:33
+ (UTC)
X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org
X-Spam-Flag: NO
X-Spam-Score: -2.88
X-Spam-Level:
X-Spam-Status: No, score=-2.88 tagged_above=-999 required=6.31
tests=[DSN_NO_MIMEVERSION=2, MISSING_MID=0.14, RCVD_IN_DNSWL_HI=-5,
RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01] autolearn=disabled
Received: from mx1-lw-eu.apache.org ([10.40.0.8])
by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new,
port 10024)
with ESMTP id xL0oKNYLRUmP for ;
Mon, 27 Jun 2016 14:20:30 + (UTC)
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org)
with SMTP id EA5315FB35
for ; Mon, 27 Jun 2016
14:20:29 + (UTC)
Received: (qmail 32522 invoked for bounce); 27 Jun 2016 14:20:29 -
Date: 27 Jun 2016 14:20:29 -
From: mailer-dae...@apache.org
To: dev-return...@juneau.incubator.apache.org
Subject: failure notice




-- 
James Bognar

Fwd: Requesting permission for editing Incubator PMC report

[Nabarun Nag]

Hi Nick,
The "name"  which I use for loggin in to
https://wiki.apache.org/incubator/July2016 page is Nabarun Nag.

Please do let me know if you need any other information.

Regards
Nabarun Nag


*From:* Nick Burch 
*Date:* June 30, 2016 at 4:07:03 PM PDT
*To:* general@incubator.apache.org
*Subject:* *Re: Requesting permission for editing Incubator PMC report*
*Reply-To:* general@incubator.apache.org

On Thu, 30 Jun 2016, Nabarun Nag wrote:

Please grant me the permission to append the Apache Geode podling report to
the incubator PMC page (https://wiki.apache.org/incubator/July2016).


What is your username for the incubator wiki? (Note - the wiki doesn't use
Apache ldap credentials, so you need to register if you haven't already!)

Nick

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

Re: Fwd: [VOTE] Release Apache Taverna Command-line Tool 3.1.0-incubating RC3

[Stian Soiland-Reyes]

On 29 June 2016 at 21:06, Josh Elser  wrote:
> +1 (binding)

Thanks, Josh!


>   - command-line's NOTICE has a vague reference as the other projects to
> "Copyright 2010-2014 University of Manchester, UK", but not explicitly what
> applies. Might that be clarified (if it's simple).

It's tricky to be more specific, because for all three repositories
most of the code comes from the software grant from Manchester and was
developed between 2007-2014, but the start year varies per repository
corresponding to their earliest commit.


The exception is where there's something brand new added in the last
years, e.g. GSOC 2016 is adding two new modules to common-activities,
I guess for those we can clarify that they are not included by the
Manchester (c).


I agree that the NOTICE should try to make it clear when the
additional lines can be disregarded, as an example this came up in
Apache Commons VFS, which had borrowed code from Apache Jackrabbit,
but we had to verify that code did NOT come from the original grant
when Jackrabbit entered the incubator [4], and thus did not need to
modify VFS's NOTICE.


> Portions of this software were originally based on the following:
> - Copyright 2007-2014 University of Manchester, UK
> These have been licensed to the Apache Software Foundation under a software 
> grant.

Perhaps we should also work on the exact wording here, that was also
suggested by Justin.  Do we need to mention the software grant?  (We
thought we should include it as the pre-2014 Taverna code was licensed
as LGPL 2.1, which the git log should show)


> The API jar didn't
> contain that portion in its META-INF/NOTICE, but I'm unsure if it actually
> contains code that the Uni has copyright over.

Perhaps it really should, however University of Manchester is not
going to insist on propagating this in META-INF/NOTICE as the code
didn't have such a NOTICE when we did the software grant and code
import [1].



We added Manchester to the top-level NOTICE mainly as a courtesy and
to be true to history (the software was not started in 2014).


The META-INF/NOTICE of most JAR files are auto-generated by
maven-shared-archive-resources applied by the Apache super POM - and
therefore do not mention Manchester.

I don't know a good way to customize this without adding 100s of
src/main/resources/META-INF/NOTICE or LICENSE files, as we have done
now only where legally needed. [3]


Thanks for your review!

[1] 
https://github.com/apache/incubator-taverna-engine/tree/apache-import-20150223
[2] https://github.com/apache/incubator-taverna-language/blob/master/NOTICE
[3] 
https://github.com/apache/incubator-taverna-engine/blob/master/taverna-execution-hadoop/src/main/resources/META-INF/LICENSE#L204
[4] https://issues.apache.org/jira/browse/VFS-611

-- 
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons
http://orcid.org/-0001-9842-9718

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

Re: Fwd: [VOTE] Release Apache Taverna Command-line Tool 3.1.0-incubating RC3

[Josh Elser]

+1 (binding)

* Built from source and ran tests
* xsums/sigs good
* KEYS is up to date
* DISCLAIMER is present
* L present in source release artifacts (and also in JARs where 
applicable)
  - command-line's NOTICE has a vague reference as the other projects 
to "Copyright 2010-2014 University of Manchester, UK", but not 
explicitly what applies. Might that be clarified (if it's simple). The 
API jar didn't contain that portion in its META-INF/NOTICE, but I'm 
unsure if it actually contains code that the Uni has copyright over. 
Enging and common activities had some more clarity here, I believe.

* mvn apache-rat:check passes

- Josh

Stian Soiland-Reyes wrote:

The Taverna PPMC has successfully voted for the source release of

   Apache Taverna Engine 3.1.0-incubating
   Apache Taverna Common Activities 2.1.0-incubating
   Apache Taverna Command-line Tool 3.1.0-incubating


This is the first major release of Apache Taverna, following two
library releases which this relies on.

Note that Taverna still suffers from not having enough active mentors;
so we therefore ask kindly for the wider incubator community to help
review this release candidate.

We would also welcome any new mentors to guide us as we feel we move
further towards graduation.


Related podling threads:

[VOTE]: 
https://lists.apache.org/thread.html/03184f452898d3f8280301b93b40fce5902d45997ce03e341afaf3d1@%3Cdev.taverna.apache.org%3E

[RESULT]: 
https://lists.apache.org/thread.html/d0820b3a3166d5cab89203859baa5c35707904fa2efa7b2870ccf291@%3Cdev.taverna.apache.org%3E

[DISCUSS]: 
https://lists.apache.org/thread.html/869109d8c0e33bb537ac02e8286dbba2383454e13fc6986750749e6e@%3Cdev.taverna.apache.org%3E


Apache Taverna Engine executes Taverna workflows, defined using
Apache Taverna Language or Taverna 2's .t2flow format, and
provides OSGi services for monitoring and controlling the
detailed execution of workflow.

Apache Taverna Common Activities provide bindings for the
Taverna Engine to invoke activities such as
command line tools (local/ssh), Beanshell scripts,
REST and WSDL services, spreadsheet import and
user interactions.

Apache Taverna Command-line Tool provides a shell command
for executing Taverna workflows, with output of results to either
a folder or a Research Object bundle including detailed provenance.
In addition to the Taverna Common Activities, the Command-line
supports plugins using Taverna OSGi services.


The release candidates to be voted over are available at:

https://dist.apache.org/repos/dist/dev/incubator/taverna/source/rc3/taverna-engine-3.1.0-incubating/

https://dist.apache.org/repos/dist/dev/incubator/taverna/source/rc3/taverna-common-activities-2.1.0-incubating/

https://dist.apache.org/repos/dist/dev/incubator/taverna/source/rc3/taverna-commandline-3.1.0-incubating/


Build the release candidate *in the above order*, using:

 mvn clean install


On a multi-core Linux/OSX machine with a fast disk you may achieve a
speed-up with:

 mvn clean install -T1.5C


SHA-1 checksums:

cccbdaf2cac2a05df55c62d03d6308ac75f72a58
apache-taverna-engine-3.1.0-incubating-source-release.zip
94d15c4c1dbd1021b8726e584810a6030e90a16c
apache-taverna-common-activities-2.1.0-incubating-source-release.zip
71ba1a84cf1cb7293de3fef5bbeb81b353634698
apache-taverna-commandline-3.1.0-incubating-source-release.zip


MD5 checksums:

276c36375b28c2a7a01fbb48c8cf66ea
apache-taverna-engine-3.1.0-incubating-source-release.zip
fccf07b3d6fe7245c67466e75fcd840b
apache-taverna-common-activities-2.1.0-incubating-source-release.zip
948b7f0fae080ac4be802571d182a5cb
apache-taverna-commandline-3.1.0-incubating-source-release.zip


The release candidates correspond to the following git commits:

https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-engine.git;a=commit;h=403dbc4a5984798b2ea98dfb37314128b50b2bcf

https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-common-activities.git;a=commit;h=a192c858c65441f33043aeeaa0889e0159a5a4e8

https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-commandline.git;a=commit;h=2db7d9f823e895d33ef2107ebfe5d70ed20e1fc7


Release candidates are signed with a GPG key available at:
   https://dist.apache.org/repos/dist/release/incubator/taverna/KEYS


A staged Maven repository is available for review at:
   https://repository.apache.org/content/repositories/orgapachetaverna-1015/


The changelog for this release is available from JIRA:

   
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318322=12332249
   
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318322=12332250
   
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318322=12332251



Please vote on releasing these packages as:

   Apache Taverna Engine 3.1.0-incubating
   Apache Taverna Common Activities 2.1.0-incubating
   Apache Taverna Command-line Tool 3.1.0-incubating


The vote is open for at least 72 hours and passes if a majority of at
least three +1 Apache Incubator IPMC votes 

Fwd: [VOTE] Release Apache Taverna Command-line Tool 3.1.0-incubating RC3

[Stian Soiland-Reyes]

The Taverna PPMC has successfully voted for the source release of

  Apache Taverna Engine 3.1.0-incubating
  Apache Taverna Common Activities 2.1.0-incubating
  Apache Taverna Command-line Tool 3.1.0-incubating


This is the first major release of Apache Taverna, following two
library releases which this relies on.

Note that Taverna still suffers from not having enough active mentors;
so we therefore ask kindly for the wider incubator community to help
review this release candidate.

We would also welcome any new mentors to guide us as we feel we move
further towards graduation.


Related podling threads:

[VOTE]: 
https://lists.apache.org/thread.html/03184f452898d3f8280301b93b40fce5902d45997ce03e341afaf3d1@%3Cdev.taverna.apache.org%3E

[RESULT]: 
https://lists.apache.org/thread.html/d0820b3a3166d5cab89203859baa5c35707904fa2efa7b2870ccf291@%3Cdev.taverna.apache.org%3E

[DISCUSS]: 
https://lists.apache.org/thread.html/869109d8c0e33bb537ac02e8286dbba2383454e13fc6986750749e6e@%3Cdev.taverna.apache.org%3E


Apache Taverna Engine executes Taverna workflows, defined using
Apache Taverna Language or Taverna 2's .t2flow format, and
provides OSGi services for monitoring and controlling the
detailed execution of workflow.

Apache Taverna Common Activities provide bindings for the
Taverna Engine to invoke activities such as
command line tools (local/ssh), Beanshell scripts,
REST and WSDL services, spreadsheet import and
user interactions.

Apache Taverna Command-line Tool provides a shell command
for executing Taverna workflows, with output of results to either
a folder or a Research Object bundle including detailed provenance.
In addition to the Taverna Common Activities, the Command-line
supports plugins using Taverna OSGi services.


The release candidates to be voted over are available at:

https://dist.apache.org/repos/dist/dev/incubator/taverna/source/rc3/taverna-engine-3.1.0-incubating/

https://dist.apache.org/repos/dist/dev/incubator/taverna/source/rc3/taverna-common-activities-2.1.0-incubating/

https://dist.apache.org/repos/dist/dev/incubator/taverna/source/rc3/taverna-commandline-3.1.0-incubating/


Build the release candidate *in the above order*, using:

mvn clean install


On a multi-core Linux/OSX machine with a fast disk you may achieve a
speed-up with:

mvn clean install -T1.5C


SHA-1 checksums:

cccbdaf2cac2a05df55c62d03d6308ac75f72a58
apache-taverna-engine-3.1.0-incubating-source-release.zip
94d15c4c1dbd1021b8726e584810a6030e90a16c
apache-taverna-common-activities-2.1.0-incubating-source-release.zip
71ba1a84cf1cb7293de3fef5bbeb81b353634698
apache-taverna-commandline-3.1.0-incubating-source-release.zip


MD5 checksums:

276c36375b28c2a7a01fbb48c8cf66ea
apache-taverna-engine-3.1.0-incubating-source-release.zip
fccf07b3d6fe7245c67466e75fcd840b
apache-taverna-common-activities-2.1.0-incubating-source-release.zip
948b7f0fae080ac4be802571d182a5cb
apache-taverna-commandline-3.1.0-incubating-source-release.zip


The release candidates correspond to the following git commits:

https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-engine.git;a=commit;h=403dbc4a5984798b2ea98dfb37314128b50b2bcf

https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-common-activities.git;a=commit;h=a192c858c65441f33043aeeaa0889e0159a5a4e8

https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-commandline.git;a=commit;h=2db7d9f823e895d33ef2107ebfe5d70ed20e1fc7


Release candidates are signed with a GPG key available at:
  https://dist.apache.org/repos/dist/release/incubator/taverna/KEYS


A staged Maven repository is available for review at:
  https://repository.apache.org/content/repositories/orgapachetaverna-1015/


The changelog for this release is available from JIRA:

  
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318322=12332249
  
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318322=12332250
  
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318322=12332251



Please vote on releasing these packages as:

  Apache Taverna Engine 3.1.0-incubating
  Apache Taverna Common Activities 2.1.0-incubating
  Apache Taverna Command-line Tool 3.1.0-incubating


The vote is open for at least 72 hours and passes if a majority of at
least three +1 Apache Incubator IPMC votes are cast.


[ ] +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 IPMC members,
please feel free to try out the release candidate and provide your
votes!

How to review a release candidate? https://s.apache.org/review-release



--
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons
http://orcid.org/-0001-9842-9718

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

Re: Fwd: Podling Report Reminder - June 2016

[Gary Gregory]

On Thu, Jun 2, 2016 at 1:51 AM, Sergio Fernández  wrote:

> On Thu, Jun 2, 2016 at 10:25 AM, Nick Burch  wrote:
>
>> On Thu, 2 Jun 2016, Sergio Fernández wrote:
>>
>>> Can anybody give karma to GaryGregory for editing the incubator wiki?
>>> Thanks.
>>>
>>
>> Karma granted, happy editing!
>
>
> Thanks, Nick!
>

Thank you all.

I signed off on the CommonsRDF report.

Gary

>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co
>



-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition

JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: Fwd: Podling Report Reminder - June 2016

[Sergio Fernández]

On Thu, Jun 2, 2016 at 10:25 AM, Nick Burch  wrote:

> On Thu, 2 Jun 2016, Sergio Fernández wrote:
>
>> Can anybody give karma to GaryGregory for editing the incubator wiki?
>> Thanks.
>>
>
> Karma granted, happy editing!


Thanks, Nick!


-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Re: Fwd: Podling Report Reminder - June 2016

[Nick Burch]

On Thu, 2 Jun 2016, Sergio Fernández wrote:
Can anybody give karma to GaryGregory for editing the incubator wiki? 
Thanks.


Karma granted, happy editing!

Nick

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

Fwd: Podling Report Reminder - June 2016

[Sergio Fernández]

Can anybody give karma to GaryGregory for editing the incubator wiki?
Thanks.


-- Forwarded message --
From: Gary Gregory 
Date: Thu, Jun 2, 2016 at 9:21 AM
Subject: Re: Podling Report Reminder - June 2016
To: d...@commonsrdf.incubator.apache.org


Crud, I cannot seem to edit the Wiki. I am logged on the wiki as
"GaryGregory" Do I karma?

Gary

On Wed, Jun 1, 2016 at 4:44 PM,  wrote:

> Dear podling,
>
> This email was sent by an automated system on behalf of the Apache
> Incubator PMC. It is an initial reminder to give you plenty of time to
> prepare your quarterly board report.
>
> The board meeting is scheduled for Wed, 15 June 2016, 10:30 am PDT.
> The report for your podling will form a part of the Incubator PMC
> report. The Incubator PMC requires your report to be submitted 2 weeks
> before the board meeting, to allow sufficient time for review and
> submission (Wed, June 1st).
>
> Please submit your report with sufficient time to allow the Incubator
> PMC, and subsequently board members to review and digest. Again, the
> very latest you should submit your report is 2 weeks prior to the board
> meeting.
>
> Thanks,
>
> The Apache Incubator PMC
>
> Submitting your Report
>
> --
>
> Your report should contain the following:
>
> *   Your project name
> *   A brief description of your project, which assumes no knowledge of
> the project or necessarily of its field
> *   A list of the three most important issues to address in the move
> towards graduation.
> *   Any issues that the Incubator PMC or ASF Board might wish/need to be
> aware of
> *   How has the community developed since the last report
> *   How has the project developed since the last report.
>
> This should be appended to the Incubator Wiki page at:
>
> http://wiki.apache.org/incubator/June2016
>
> Note: This is manually populated. You may need to wait a little before
> this page is created from a template.
>
> Mentors
> ---
>
> Mentors should review reports for their project(s) and sign them off on
> the Incubator wiki page. Signing off reports shows that you are
> following the project - projects that are not signed may raise alarms
> for the Incubator PMC.
>
> Incubator PMC
>



--
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition

JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory



-- 
Sergio Fernández
Partner Technology Manager
Redlink GmbH
m: +43 6602747925
e: sergio.fernan...@redlink.co
w: http://redlink.co

Fwd: [DISCUSS] A users@ mailing list for Apache Mynewt

[James Pace]

Hello. I am participating in the Apache Mynewt project and want to pose a quick 
question that might have been brought up previously… Are there any other 
ASF-supported alternatives to the current mail archive UI? If there’s a 
solution that’s been proposed, we’re keen to here; if not, we would be keen to 
explore options.

thanks, pace

Begin forwarded message:

> From: James Pace 
> Subject: Re: [DISCUSS] A users@ mailing list for Apache Mynewt
> Date: May 20, 2016 at 8:04:36 PDT
> To: d...@mynewt.incubator.apache.org
> 
> I agree 100% on the mail archive. If we could tee this off to a better 
> interface (more intuitive threading and search) and maintain sync, that would 
> help the community a lot.
> 
> I am also a newbie to the ASF, but wondering if someone in the infrastructure 
> or incubator group might have some thoughts or heard this before. We can 
> inquire at general@incubator.apache.org, which I’ll do.
> 
> Good to see you here, David.
> 
> —pace
> 
> On May 20, 2016, at 7:55, David G. Simmons  wrote:
> 
>> As a n00b, I’ll chime in here with my experience so far … Just my $0.02, so 
>> take it as you will. I’ve been involved in a few ‘new’ 
>> product/protocol/platform development efforts over the years though.
>> 
>> As a new user and (potential) developer, the lack of a ‘user’ list was (as 
>> another has previously stated) a bit intimidating. I’m not (yet) a mynewt 
>> developer, just a hacker trying to get stuff working. I finally bit the 
>> bullet and posted to the dev list and was obviously pleasantly surprised by 
>> both the speed and friendliness of the response. There is a LOT of value in 
>> having the folks actually developing the system see all the questions from 
>> the users. I know it can be a distraction from the ‘real’ work to get silly 
>> questions from new users, but in my experience, the success of a platform is 
>> in many ways highly dependent on the experience of new users. If someone new 
>> can’t start using the platform, then you wont’ have new users, and …
>> 
>> I found the archives, and attempted to go through them as best I could in 
>> order to find answers to questions I was having initially. I figured most of 
>> them out on my own, from repeated trips through the docs, etc., but the 
>> email archives could be much more helpful. The problem is that the mail 
>> archives are … so 1998. Not searchable, only navigable by year/month, etc. 
>> Having a proper interface to the mail archives would make them much more 
>> useful to users. Even the mail-archive.com interface — which has search — 
>> would work nicely. Having a forum — along the lines of phpBB2, though those 
>> are notoriously hard to keep spammers out of — with an email-to-forum 
>> gateway would also be helpful.
>> 
>> Back to hacking …
>> 
>> dg
>> 
>> 
>> 
>> 
>>> On May 19, 2016, at 4:42 PM, James Pace  wrote:
>>> 
>>> I’d personally like to see these separated. Many of the comments that are 
>>> coming in are routine (though very informative) and do not inform the 
>>> design or development of Apache Mynewt.
>>> 
>>> And, besides, it is likely that you will have “user” and “dev”  sourced to 
>>> the same mailbox or mail filter!
>>> 
>>> On May 19, 2016, at 11:12, p...@wrada.com wrote:
>>> 
 I¹d prefer to keep them together for now.  As this is new, I think that
 developers are going to learn a lot from the users issues or questions,
 and vice versa.  I agree that this will get too much at some point, but
 I¹m really getting a lot from seeing the user and developer issues
 together.
 
 
 On 5/19/16, 11:08 AM, "aditi hilbert"  wrote:
 
> Hi,
> 
> With Mynewt attracting an increasing number of both users and developers
> of various levels, it might make practical sense to have a users@ mailing
> list separate from dev@ mailing list. That way support questions about
> product usage, asks, needs etc can be separated from
> developer/design/architecture discussions. Of course, there has to be
> communication between the two groups to build truly useful and usable
> features, but we can bring some organization to it with the separate
> mailing lists. Please comment on the suggestion.
> 
> Let¹s keep this thread open through the weekend to gauge the general
> response.
> 
> thanks,
> aditi
 
>>> 
>> 
>> --
>> David G. Simmons
>> (919) 534-5099
>> Web • Blog • Linkedin • Twitter • GitHub
>> /** Message digitally signed for security and authenticity.
>> * If you cannot read the PGP.sig attachment, please go to
>> * http://www.gnupg.com/ Secure your email!!!
>> * Public key available at keyserver.pgp.com
>> **/
>> ♺ This email uses 100% recycled electrons. Don't blow it by printing!
>> 
>> There are only 2 hard things in computer science: Cache invalidation, naming 
>> things, and off-by-one errors.
>> 
>> 
> 

Re: Fwd: [jira] [Created] (HAWQ-694) 1844-313-4857 Quickbooks payroll support usa/canada

[Gregory Chase]

Cool and thanks!

On Thu, Apr 21, 2016 at 1:44 PM, Mark Thomas  wrote:

> On 21/04/2016 21:40, Gregory Chase wrote:
> > Seems we have a JIRA user who's spamming Apache HAWQ? Is this a
> compromised
> > account, or someone who has access that shouldn't?
>
> It is a public Jira instance on which anyone can create an account.
> Sometimes spam happens. It is the cost of an open development process.
>
> The infra team is already on the case to clean up the spam and is
> looking into what further filtering can be applied to reduce future
> instances.
>
> Mark
>
>
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Greg Chase

Global Head, Big Data Communities
http://www.pivotal.io/big-data

Pivotal Software
http://www.pivotal.io/

650-215-0477
@GregChase
Blog: http://geekmarketing.biz/

Re: Fwd: [jira] [Created] (HAWQ-694) 1844-313-4857 Quickbooks payroll support usa/canada

[Mark Thomas]

On 21/04/2016 21:40, Gregory Chase wrote:
> Seems we have a JIRA user who's spamming Apache HAWQ? Is this a compromised
> account, or someone who has access that shouldn't?

It is a public Jira instance on which anyone can create an account.
Sometimes spam happens. It is the cost of an open development process.

The infra team is already on the case to clean up the spam and is
looking into what further filtering can be applied to reduce future
instances.

Mark



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

Fwd: [jira] [Created] (HAWQ-694) 1844-313-4857 Quickbooks payroll support usa/canada

[Gregory Chase]

Seems we have a JIRA user who's spamming Apache HAWQ? Is this a compromised
account, or someone who has access that shouldn't?

-Greg
-- Forwarded message --
From: Kalramin (JIRA) 
Date: Thu, Apr 21, 2016 at 1:34 PM
Subject: [jira] [Created] (HAWQ-694) 1844-313-4857 Quickbooks payroll
support usa/canada
To: iss...@hawq.incubator.apache.org


Kalramin created HAWQ-694:
-

 Summary: 1844-313-4857 Quickbooks  payroll support usa/canada
 Key: HAWQ-694
 URL: https://issues.apache.org/jira/browse/HAWQ-694
 Project: Apache HAWQ
  Issue Type: Bug
Reporter: Kalramin
Assignee: Lei Chang


1844-313-4857 Quickbooks  payroll support usa/canada1844-313-4857
Quickbooks  payroll support usa/canada cloud hostinggeneralQuickbooks
cloudcloud computing can be thought 1844-313-4857 as any instance where
you're using a computer that resides outside 1844-313-4857 your physical
locationQuickbooks cloud Most users encounter cloud computing  cloud
hostingthe form 1844-313-4857 s1844-313-4857tware as a serviceQuickbooks
cloud You might pay a fee for the serviceQuickbooks cloudsuch as QuickBooks
OnlineQuickbooks cloudSalesforceQuickbooks cloudcomQuickbooks cloudor
Micros1844-313-4857t's 1844-313-4857fice 365Quickbooks cloudor you may pay
cloud hostinga nonmonetary fashion through an advertising-supported and/or
information-gathering modelsQuickbooks cloudsuch as GmailQuickbooks
cloudMintQuickbooks cloudor FacebookQuickbooks cloud

Cloud computing gives you access to an environment that you can customize
or build out to suit your needsQuickbooks cloud With SaaSQuickbooks
cloudyou're limited to the features and capabilities written into the
s1844-313-4857twareQuickbooks cloudbut cloud computing 1844-313-4857fers
the ability to increase server capacity or storage space on
demandQuickbooks cloud
Cloud computing 1844-313-4857fers elasticityQuickbooks cloudmeaning your
resources and costs can increase or decrease with your demandsQuickbooks
cloud SaaS typically involves a set fee per userQuickbooks cloudper
monthQuickbooks cloudso costs and the functionality 1844-313-4857fered tend
to be fixedQuickbooks cloud
 cloud hostingshortQuickbooks cloudcloud computing is highly
customizableQuickbooks cloudwhereas SaaS 1844-313-4857fers more
1844-313-4857 Quickbooks cloudapproachQuickbooks cloud

For SaaSQuickbooks cloudend users are removed from maintaining both the
application and the server equipmentQuickbooks cloud Benefits 1844-313-4857
SaaS versus desktop programs include:
ApplicationsQuickbooks cloudsuch as QuickBooks OnlineQuickbooks cloudallow
you to access accounting records from anywhere  cloud hostingthe
worldQuickbooks cloudinstead 1844-313-4857 from specific computers with
cloud hostingyour 1844-313-4857ficeQuickbooks cloud
New features appear  cloud hostingthe s1844-313-4857tware
automaticallyQuickbooks cloudso there's no need to purchase a
s1844-313-4857tware upgrade to be physically installed on each
1844-313-4857 your computersQuickbooks cloud
Your data is backed up automaticallyQuickbooks cloudso a local hard drive
crash won't affect your dataQuickbooks cloud

Consider the recent situation with megauploadQuickbooks cloudcomQuickbooks
cloudwhere certa cloud hostingpurported illegal actions 1844-313-4857 a
subset 1844-313-4857 users caused everyone using the service to lose access
to dataQuickbooks cloud Think about a toddler having a certa cloud
hostingbodily function  cloud hostinga public swimming pool Quickbooks
cloud everyone has to suddenly get out 1844-313-4857 the waterQuickbooks
cloud SimilarlyQuickbooks cloudactions 1844-313-4857 one or more rogue
users can cause unexpected and dramatic disruptions for everyone else
sharing a cloud-based resourceQuickbooks cloud
Both cloud computing and SaaS involve trustQuickbooks cloud cloud
hostingthat you're trusting an organization to hold up its end
1844-313-4857 the bargainQuickbooks cloud IntuitQuickbooks cloudmaker
1844-313-4857 QuickBooksQuickbooks cloudlast year experienced a spate
1844-313-4857 outages that caused business interruptions for users
1844-313-4857 their myriad online servicesQuickbooks cloud
A service you trust and rely on could suddenly change handsQuickbooks
cloudsuch as Facebook's recent acquisition 1844-313-4857
InstagramQuickbooks cloud You may then be forced to find a new service
provider if you have philosophical differences with the new owner
1844-313-4857 a tool that you've relied on or if customer service levels
start to slip to unacceptable levelsQuickbooks cloud
If you stop paying for the serviceQuickbooks cloudaccess to your data can
be immediately terminatedQuickbooks cloud HoweverQuickbooks cloudmany
providers 1844-313-4857fer a grace periodQuickbooks cloud For
instanceQuickbooks cloudif you cancel your QuickBooks Online
accountQuickbooks cloudyour data is maintained for a yearQuickbooks
cloudshould you 

Fwd: [VOTE] Graduate Apex from the Incubator

[Thomas Weise]

Please note that a graduation community [VOTE] is in progress for Apache
Apex.

Thanks,
Thomas

-- Forwarded message --
From: Pramod Immaneni 
Date: Tue, Mar 22, 2016 at 10:36 AM
Subject: [VOTE] Graduate Apex from the Incubator
To: d...@apex.incubator.apache.org


Dear Community,

Based on the positive discussion, I'm calling for the community VOTE
to graduate Apache Apex (incubating) to top level project (TLP).

Please vote on the resolution pasted below.

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

This is a community vote and everyone is invited to participate. PPMC
votes should be marked binding.

This vote will be open for at least 72 hours.

If this VOTE succeeds, a similar VOTE will commence on the
general@incubator mailing list. If that vote also succeeds,
we will submit the resolution to be included in the agenda
of the next Apache board meeting.

Many thanks to our mentors and everyone else for the support,

Pramod, for the Apache Apex PPMC

My vote is +1 (binding)

Apache Apex top-level project resolution:
=

WHEREAS, the Board of Directors deems it to be in the best
interests of the Foundation and consistent with the
Foundation's purpose to establish a Project Management
Committee charged with the creation and maintenance of
open-source software, for distribution at no charge to
the public, related to Hadoop native, distributed,
large-scale, high throughput, low-latency, fault tolerant,
easily operable, unified stream and batch processing platform.

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

RESOLVED, that the Apache Apex Project be and hereby is
responsible for the creation and maintenance of software
related to Hadoop native, distributed, large-scale,
high throughput, low-latency, fault tolerant, easily operable,
unified stream and batch processing platform;
and be it further

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

* Ilya Ganelin 
* P. Taylor Goetz 
* Gaurav Gupta 
* Pramod Immaneni 
* Amol Kekre 
* Justin Mclean 
* Chetan Narsude 
* Chris Nauroth 
* Vlad Rozov 
* Hitesh Shah 
* Thomas Weise 
* David Yan 
* Brennon York 

NOW, THEREFORE, BE IT FURTHER RESOLVED, that Thomas Weise
be appointed to the office of Vice President, Apache Apex, 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 Apex 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 Apex Project; and be it further

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

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

Fwd: Google Summer of Code 2016 Mentor Registration

[Ulrich Stärk]

Hi Incubator,

please notice below email explaining how to sign up as a mentor for Apache 
projects for this years GSoC.

Please forward to all podlings.

Cheers,

Uli

 Forwarded Message 
Subject: Google Summer of Code 2016 Mentor Registration
Date: Tue, 8 Mar 2016 18:01:20 +0100
From: Ulrich Stärk 
Reply-To: ment...@community.apache.org, ment...@community.apache.org
To: ment...@community.apache.org

Dear PMCs,

I'm happy to announce that the ASF has made it onto the list of accepted 
organizations for
Google Summer of Code 2016! [1,2]

It is now time for the mentors to sign up, so please pass this email on to your 
community and
podlings. If you aren’t already subscribed to ment...@community.apache.org you 
should do so now else
you might miss important information.

Mentor signup requires two steps: mentor signup in Melange and PMC 
acknowledgement.

If you want to mentor a project in this year's SoC you will have to

1. Be an Apache committer.
2. Request an acknowledgement from the PMC for which you want to mentor 
projects. Use the below
template and *do not forget to copy ment...@community.apache.org*. We will use 
the email adress you
indicate to send the invite to be a mentor for Apache.

PMCs, read carefully please.

We request that each mentor is acknowledged by a PMC member. This is to ensure 
the mentor is in good
standing with the community. When you receive a request for acknowledgement, 
please ACK it and cc
ment...@community.apache.org

Lastly, it is not yet too late to record your ideas in Jira (see my previous 
emails for details).
Students will now begin to explore ideas so if you haven’t already done so, 
record your ideas
immediately!

Cheers,

Uli

mentor request email template:

to: private@.apache.org
cc: ment...@community.apache.org
subject: GSoC 2016 mentor request for 

 PMC,

please acknowledge my request to become a mentor for Google Summer of Code 2016 
projects for Apache
.

I would like to receive the mentor invite to 





[1] https://summerofcode.withgoogle.com/organizations/
[2] https://summerofcode.withgoogle.com/organizations/5694656234913792/



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

Fwd: [VOTE] Release taverna-language-0.15.1-incubating-RC5 and taverna-osgi-0.2.1-incubating-RC5

[Stian Soiland-Reyes]

I am pleased to be calling this vote for the source release of

  Apache Taverna Maven Parent 2-incubating
  Apache Taverna Language 0.15.1-incubating
  Apache Taverna OSGi plugin system 0.2.1-incubating

The Apache Taverna IPMC has voted in favour of this release with 5 IPMC votes:

http://markmail.org/message/346xxkywuexw6z52
http://mail-archives.apache.org/mod_mbox/taverna-dev/201603.mbox/

We now ask for the Incubator PMC to vote on this release candidate.


Apache Taverna Language is a set of APIs for workflow definitions
(SCUFL2) and workflow inputs/outputs/run (DataBundle), as consumed and
produced by the Apache Taverna workflow system. The API includes
support for working with Research Object Bundles, and loading/saving
Taverna workflows in different formats.

Apache Taverna OSGi is a plugin system for OSGi with support for
online updates, which can be used by Java desktop and command line
applications.


The release candidates to be voted over are available at:

  
https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-parent-2-incubating-RC5/
  
https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-language-0.15.1-incubating-RC5/
  
https://dist.apache.org/repos/dist/dev/incubator/taverna/source/taverna-osgi-0.2.1-incubating-RC5/


Checksums:

md5sum:
8e7ee332896d314877af481b348dbf51
apache-taverna-parent-2-incubating-source-release.zip

6bd8ae9e2b1bc2e675e5573b87feaa2a
apache-taverna-language-0.15.1-incubating-source-release.zip

4d595212a813f62a0c16a31d3a872af4
apache-taverna-osgi-0.2.1-incubating-source-release.zip


sha1sum:
d4b675763eb03bc5a9863db27779d725e1209af6
apache-taverna-parent-2-incubating-source-release.zip

af3a14ec6d9386e9aa97309275f7b147be6f0a38
apache-taverna-language-0.15.1-incubating-source-release.zip

2e91b5176322c0e029e1a856f0752159b1564158
apache-taverna-osgi-0.2.1-incubating-source-release.zip


sha512sum:
d5787ba7066d0d3b7c3b292434eb3de909c8ebaf43f0a3ea5e9dd25f0f19b5c1b7d508ffde97c0e6afd53265835d1aa4f22bb3187011b50b7f5aac99892bd0aa
apache-taverna-parent-2-incubating-source-release.zip

7cb4860abb4c57b91e81703a0d362d2824f10f1d2abe62c3df028fdca4f3ce33c4fe572c3349e629c8d409a7b25f3c86b79487d840c642a4b39e84432aa86c04
apache-taverna-language-0.15.1-incubating-source-release.zip

31b50a87243a01f3a5a657643d0f3b7f56d86fcc309df74392df3915ef8a787948ff8c74bc6a7684e6f9049b6430324373c50959ff658803dbc2d67d8a3dc45c
apache-taverna-osgi-0.2.1-incubating-source-release.zip



To build the release candidates you need Apache Maven 3 and Java 8.


Build the release candidate, in the above order, using:

mvn clean install


The release candidates correspond to the following git commits:

  
https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-maven-parent.git;a=commit;h=d34dd67fcfa11caead08008d37279b1ea546e3ec

  
https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-language.git;a=commit;h=66866a5454ed23262c055f65155d7a195c68a17d

  
https://git-wip-us.apache.org/repos/asf?p=incubator-taverna-osgi.git;a=commit;h=0b7da331e81febade5ce2f4cf1f068013002b7aa


Release candidates are signed with a GPG key available at:

  https://dist.apache.org/repos/dist/release/incubator/taverna/KEYS

A staged Maven repository is available for review at:

  https://repository.apache.org/content/repositories/orgapachetaverna-1011/

The changelog for this release is available from JIRA:

  
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333249=12318322
  
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12333250=12318322
  
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12332248=12318322


Please vote on releasing these packages as:

  Apache Taverna Maven Parent 2-incubating
  Apache Taverna Language 0.15.1-incubating
  Apache Taverna OSGi plugin system 0.2.1-incubating


The vote is open for at least 72 hours
(let's say Monday 2016-03-07 17:00 GMT)
and passes if a majority of at least
three +1 Incubator PMC votes are cast.

[ ] +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 Incubator PMC
members, please feel free to try out the release candidate and provide
your votes.


--
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/-0001-9842-9718

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

Fwd: [VOTE] Apache Johnzon 0.9.3-incubating release

[Romain Manni-Bucau]

FYI. Apache Johnzon is currently voting on 0.9.3-incubating.

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Github  |
LinkedIn  | Tomitriber


-- Forwarded message --
From: Romain Manni-Bucau 
Date: 2016-02-17 10:47 GMT+01:00
Subject: [VOTE] Apache Johnzon 0.9.3-incubating release
To: d...@johnzon.incubator.apache.org


Hi

As mentioned on the list here is the release vote for johnzon 0.9.3:

he release is
*https://git-wip-us.apache.org/repos/asf?p=incubator-johnzon.git;a=commit;h=4ba9bca107c8f51f2e8340d05e500db19fe87366
*

Maven staging repo:
*https://repository.apache.org/content/repositories/orgapachejohnzon-1013/
*

Distribution archives (zip/tar.gz) with their hashes can be found under:
*https://repository.apache.org/content/repositories/orgapachejohnzon-1013/org/apache/johnzon/apache-johnzon/0.9.3-incubating/
*

The files are also here (apache-johnzon-0.9.3-incubating*)
https://dist.apache.org/repos/dist/dev/incubator/johnzon/

PGP release key:
https://dist.apache.org/repos/dist/release/incubator/johnzon/KEYS

Release note:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12315523=12334032


The vote will be open for at least 72 hours or until we get 3 PMC +1 votes and
no blocker is found.

[ ] +1  yep
[ ] +0  don't care
[ ] -1  no because [fill this input with your reason]

Here is my +1

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Github  |
LinkedIn  | Tomitriber

Fwd: [VOTE] Graduate Sentry from the Incubator

[Sravya Tirukkovalur]

Hi all,

Based on recommendation in the graduation guide[1], this email is to
notify the incubator general list that voting is going on in the
Sentry dev list to graduate the project.

[1] http://incubator.apache.org/guides/graduation.html#tlp-community-vote

-- Forwarded message --
From: Sravya Tirukkovalur 
Date: Tue, Feb 16, 2016 at 10:41 AM
Subject: [VOTE] Graduate Sentry from the Incubator
To: dev 


Hi all,

With positive discussion[1] around graduating sentry, I am calling a
VOTE to graduate the project from the Incubator to a TLP. Please vote
on the resolution pasted below the ballot.

[ ] +1 Graduate Sentry from the Incubator
[ ] +0 Don't care
[ ] -1 Don't graduate Sentry from the Incubator (please specify reason)

This vote will be open for at least 72 hours.

Here is my vote:
+1 (binding)

--
Regards,
Sravya Tirukkovalur

Resolution to create a TLP from graduating Incubator podling:
==

X. Establish the Apache Sentry 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 Fine grained authorization to data and
metadata in Hadoop.

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

   RESOLVED, that the Apache Sentry Project be and hereby is
   responsible for the creation and maintenance of software
   related to Fine grained authorization to data and metadata in Hadoop;
   and be it further

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

 * Ali Rizvi 

 * Anne Yu 

 * Arun Suresh 

 * Brock Noland 

 * Chaoyu Tang 

 * Colin Ma 

 * Daisy Zhou 

 * Dapeng Sun 

 * David Nalley 

 * Erick Tryzelaar 

 * Gregory Chanan 

 * Guoquan Shen 

 * Hadi Nahari 

 * Hao Hao 

 * Jarek Jarcec Cecho 

 * Johnny Zhang 

 * Karthik Ramachandran 

 * Mark Grover 

 * Milo Polte 

 * Lenni Kuff 

 * Patrick Daly 

 * Patrick Hunt 

 * Prasad Mujumdar 

 * Raghu Mani 

 * Sean Mackrory 

 * Shreepadma Venugopalan 

 * Sravya Tirukkovalur 

 * Tuong Truong 

 * Vamsee Yarlagadda 

 * Xiaomeng Huang 

 * Xuefu Zhang 

   NOW, THEREFORE, BE IT FURTHER RESOLVED, that Sravya Tirukkovalur
   be appointed to the office of Vice President, Apache Sentry, 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 Sentry 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 Sentry Project; and be it further

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

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

[1]: 

[FYI]Fwd: [VOTE] Apache BatchEE 0.3-incubating (2nd try)

[Mark Struberg]

Hi incubator!

FYI: The BatchEE incubation project is VOTEing on batchee-0.3-incubating

LieGrue,
strub


> Anfang der weitergeleiteten Nachricht:
> 
> Von: Mark Struberg 
> Datum: 8. Dezember 2015 um 12:29:09 MEZ
> An: BatchEE Dev BatchEE Dev 
> Betreff: [VOTE] Apache BatchEE 0.3-incubating (2nd try)
> 
> Hi again!
> 
> We fixed all the blockers and rolled the release again.
> Thus I’d like to call a 2nd [VOTE] on releasing Apache BatchEE-0.3-incubating.
> 
> The following improvements and bug fixes got implemented:
> 
> Bug
> 
>   • [BATCHEE-41] - JAX-RS module should create a jar
>   • [BATCHEE-52] - Partition-level artifacts don't accept 
> #{jobProperties} substitutions (see RI Bug 5748)
>   • [BATCHEE-53] - JSefa Flr/CsvField converterType won't get picked up
>   • [BATCHEE-55] - RI Bug 5806 - JobExecution returned by 
> jobOperator.getJobExecutions(jobInstance) has null parameters
>   • [BATCHEE-56] - ChunkListener.onError() should not be called in case 
> of exceptions outside of chunks
>   • [BATCHEE-57] - StepListener.afterStep() should not be called in case 
> of exceptions inside the step
>   • [BATCHEE-58] - fix tests on windows
>   • [BATCHEE-59] - Invoking JobOperator#start() using BatchEEJAXRS2Client 
> always produces NullPointerException
>   • [BATCHEE-66] - store checkpoint variables etc in human readable format
>   • [BATCHEE-67] - Some more cases with JobContext/StepContext info not 
> propagated
>   • [BATCHEE-74] - blacklist 
> org.codehaus.groovy.runtime.,org.apache.commons.collections.functors.,org.apache.xalan
>  in our custom ObjectInputStream
>   • [BATCHEE-82] - TransactionalWriter can miss some lines if closed is 
> called without a Synchronization entry
>   • [BATCHEE-83] - default header size for JsefaCsvReader
>   • [BATCHEE-84] - Batches.waitForEnd should return BatchStatus
>   • [BATCHEE-85] - allow to configure file encoding for JSefaReader
> Improvement
> 
>   • [BATCHEE-63] - use tomcat OneLineFormatter by default in batchee cli
>   • [BATCHEE-64] - StepLauncher should allow to get JobExecution instead 
> of StepExecution
>   • [BATCHEE-65] - remove unnecessary try/catch in CDIBatchArtifactFactory
>   • [BATCHEE-70] - upgrade to jsefa 1.1.1
>   • [BATCHEE-76] - Instances command doesnt list total
>   • [BATCHEE-79] - batchee diagram mojo doesnt handle split properly
> New Feature
> 
>   • [BATCHEE-60] - add skippedHeaderLines property in BeanIOReader
>   • [BATCHEE-61] - upgrade openejb in cli assembly to support java 8
>   • [BATCHEE-62] - add matchingStrategy to model mapper processor
>   • [BATCHEE-72] - commons csv integration
>   • [BATCHEE-75] - [cli] upgrade airline and allow user command to be 
> registered
>   • [BATCHEE-77] - add a cleanUp(Date until) to persistence service
>   • [BATCHEE-78] - add documentation mojo for jbatch component
>   • [BATCHEE-80] - add jsonp components
>   • [BATCHEE-81] - migrate our cli to [cli] instead of airline
> Task
> 
>   • [BATCHEE-86] - upgrade dependencies to newer versions
> 
> 
> 
> The staging repo can be found here:
> https://repository.apache.org/content/repositories/orgapachebatchee-1003/
> 
> The source-zip can be found under:
> https://repository.apache.org/content/repositories/orgapachebatchee-1003/org/apache/batchee/batchee/0.3-incubating/
> 
> my gpg key is in the KEYS file.
> 
> The branch used for releasing is available under
> https://github.com/struberg/incubator-batchee/tree/release-candidate-batchee-0.3-incubating
> 
> The tag is
> https://github.com/struberg/incubator-batchee/tree/batchee-0.3-incubating
> 
> 
> Please VOTE
> [+1] yes, all ok, let’s ship it!
> [+0] meh, don’t care
> [-1] stop, I found a ${blocker}
> 
> The VOTE is open for 72h
> 
> Thanks to all who contributed (this includes Scott, txs again!)
> 
> txs and LieGrue,
> strub
> 


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

Fwd: [VOTE][RESULT] Retire Droids

[Marvin Humphrey]

Greetings,

The Droids community has voted to retire.

As the Droids community vote was not contested, I plan to wait 72
hours for lazy consensus of the IPMC, then to proceed with the
administrative tasks of retirement.

Marvin Humphrey

-- Forwarded message --
From: Marvin Humphrey 
Date: Thu, Oct 29, 2015 at 11:14 AM
Subject: [VOTE][RESULT] Retire Droids
To: droids-...@incubator.apache.org


The vote to retire Droids passes.

  +1 Thorsten Scherler (Mentor)
  +1 Richard Frovarp (Mentor)
  +1 Marvin Humphrey (community)

I will follow up with the IPMC and attend to the administrative
aspects of retirement.

Best wishes to all,

Marvin Humphrey

On Fri, Oct 23, 2015 at 3:04 PM, Marvin Humphrey  wrote:
> Greetings,
>
> As discussed over the last few weeks on this list[1], this is a community vote
> to retire the Droids podling.
>
> [ ] +1 to retire Droids from the incubator
> [ ] -1 to keep Droids in the incubator
>
> This vote will be held open for at least 120 hours (5 days).
>
> Here is my own +1 (non-binding).
>
> Marvin Humphrey
>
> [1] 
> http://mail-archives.apache.org/mod_mbox/incubator-droids-dev/201508.mbox/browser
> 
> http://mail-archives.apache.org/mod_mbox/incubator-droids-dev/201509.mbox/browser
> 
> http://mail-archives.apache.org/mod_mbox/incubator-droids-dev/201510.mbox/browser

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

Fwd: [RESULT][VOTE] Apache Johnzon 0.9.2-incubating release

[Romain Manni-Bucau]

Hi incubator,

Mark forwarded the vote at the beginning of dev@ vote. Therefore it sounds
to me we don't need to vote again on these binaries. Can you confirm it
please?

Romain Manni-Bucau
@rmannibucau  |  Blog
 | Github  |
LinkedIn  | Tomitriber


-- Forwarded message --
From: Romain Manni-Bucau 
Date: 2015-10-05 7:02 GMT-07:00
Subject: [RESULT][VOTE] Apache Johnzon 0.9.2-incubating release
To: d...@johnzon.incubator.apache.org


So vote passed with 4 binding +1 and 2 non-binding +1.




Romain Manni-Bucau
@rmannibucau  |  Blog
 | Github  |
LinkedIn  | Tomitriber


2015-10-02 6:44 GMT-07:00 Daniel Kulp :

> +1
>
> Looks good to me.
>
> Dan
>
>
>
> > On Sep 30, 2015, at 3:33 PM, Romain Manni-Bucau 
> wrote:
> >
> > Hi
> >
> > As mentioned on the list here is the release vote for johnzon 0.9.2:
> >
> > he release is
> > *
> https://git-wip-us.apache.org/repos/asf?p=incubator-johnzon.git;a=commit;h=d88918a3b2704cf76687a894f897b2d768fe5cd5
> > <
> https://git-wip-us.apache.org/repos/asf?p=incubator-johnzon.git;a=commit;h=d88918a3b2704cf76687a894f897b2d768fe5cd5
> >*
> >
> > Maven staging repo:
> > *
> https://repository.apache.org/content/repositories/orgapachejohnzon-1009
> > <
> https://repository.apache.org/content/repositories/orgapachejohnzon-1009>*
> >
> > Distribution archives (zip/tar.gz) with their hashes can be found under:
> > *
> https://repository.apache.org/content/repositories/orgapachejohnzon-1009/org/apache/johnzon/apache-johnzon/0.9.2-incubating/
> > <
> https://repository.apache.org/content/repositories/orgapachejohnzon-1009/org/apache/johnzon/apache-johnzon/0.9.2-incubating/
> >*
> >
> > The files are also here (apache-johnzon-0.9.2-incubating-src*)
> > https://dist.apache.org/repos/dist/dev/incubator/johnzon/
> >
> > PGP release keys:
> > https://dist.apache.org/repos/dist/release/incubator/johnzon/KEYS
> >
> >
> > The vote will be open for at least 72 hours or until we get 3 PMC +1
> votes and
> > no blocker is found.
> >
> > [ ] +1  yeah do it!
> > [ ] +0  don't care
> > [ ] -1  clearly not because [fill this input with your reason]
> >
> > Here is my +1
> >
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Github <
> https://github.com/rmannibucau> |
> > LinkedIn  | Tomitriber
> > 
>
> --
> Daniel Kulp
> dk...@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>

Re: Fwd: [RESULT][VOTE] Apache Johnzon 0.9.2-incubating release

[Romain Manni-Bucau]

@Marvin: right for source/binary, sorry for this miswording

Think we should graduate soon yes, just one of us needs to take time to do
it.

Then I consider the vote done and will finish the release

Thanks guys!

2015-10-05 7:29 GMT-07:00 John D. Ament :

> I don't believe that to be the case.
>
> You guys are mature enough, why not graduate?
> On Oct 5, 2015 10:06 AM, "Romain Manni-Bucau" 
> wrote:
>
> > Hi incubator,
> >
> > Mark forwarded the vote at the beginning of dev@ vote. Therefore it
> sounds
> > to me we don't need to vote again on these binaries. Can you confirm it
> > please?
> >
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Github <
> > https://github.com/rmannibucau> |
> > LinkedIn  | Tomitriber
> > 
> >
> > -- Forwarded message --
> > From: Romain Manni-Bucau 
> > Date: 2015-10-05 7:02 GMT-07:00
> > Subject: [RESULT][VOTE] Apache Johnzon 0.9.2-incubating release
> > To: d...@johnzon.incubator.apache.org
> >
> >
> > So vote passed with 4 binding +1 and 2 non-binding +1.
> >
> >
> >
> >
> > Romain Manni-Bucau
> > @rmannibucau  |  Blog
> >  | Github <
> > https://github.com/rmannibucau> |
> > LinkedIn  | Tomitriber
> > 
> >
> > 2015-10-02 6:44 GMT-07:00 Daniel Kulp :
> >
> > > +1
> > >
> > > Looks good to me.
> > >
> > > Dan
> > >
> > >
> > >
> > > > On Sep 30, 2015, at 3:33 PM, Romain Manni-Bucau <
> rmannibu...@gmail.com
> > >
> > > wrote:
> > > >
> > > > Hi
> > > >
> > > > As mentioned on the list here is the release vote for johnzon 0.9.2:
> > > >
> > > > he release is
> > > > *
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-johnzon.git;a=commit;h=d88918a3b2704cf76687a894f897b2d768fe5cd5
> > > > <
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-johnzon.git;a=commit;h=d88918a3b2704cf76687a894f897b2d768fe5cd5
> > > >*
> > > >
> > > > Maven staging repo:
> > > > *
> > >
> https://repository.apache.org/content/repositories/orgapachejohnzon-1009
> > > > <
> > >
> https://repository.apache.org/content/repositories/orgapachejohnzon-1009
> > >*
> > > >
> > > > Distribution archives (zip/tar.gz) with their hashes can be found
> > under:
> > > > *
> > >
> >
> https://repository.apache.org/content/repositories/orgapachejohnzon-1009/org/apache/johnzon/apache-johnzon/0.9.2-incubating/
> > > > <
> > >
> >
> https://repository.apache.org/content/repositories/orgapachejohnzon-1009/org/apache/johnzon/apache-johnzon/0.9.2-incubating/
> > > >*
> > > >
> > > > The files are also here (apache-johnzon-0.9.2-incubating-src*)
> > > > https://dist.apache.org/repos/dist/dev/incubator/johnzon/
> > > >
> > > > PGP release keys:
> > > > https://dist.apache.org/repos/dist/release/incubator/johnzon/KEYS
> > > >
> > > >
> > > > The vote will be open for at least 72 hours or until we get 3 PMC +1
> > > votes and
> > > > no blocker is found.
> > > >
> > > > [ ] +1  yeah do it!
> > > > [ ] +0  don't care
> > > > [ ] -1  clearly not because [fill this input with your reason]
> > > >
> > > > Here is my +1
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau  |  Blog
> > > >  | Github <
> > > https://github.com/rmannibucau> |
> > > > LinkedIn  | Tomitriber
> > > > 
> > >
> > > --
> > > Daniel Kulp
> > > dk...@apache.org - http://dankulp.com/blog
> > > Talend Community Coder - http://coders.talend.com
> > >
> > >
> >
>

Re: Fwd: [RESULT][VOTE] Apache Johnzon 0.9.2-incubating release

[John D. Ament]

I don't believe that to be the case.

You guys are mature enough, why not graduate?
On Oct 5, 2015 10:06 AM, "Romain Manni-Bucau"  wrote:

> Hi incubator,
>
> Mark forwarded the vote at the beginning of dev@ vote. Therefore it sounds
> to me we don't need to vote again on these binaries. Can you confirm it
> please?
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Github <
> https://github.com/rmannibucau> |
> LinkedIn  | Tomitriber
> 
>
> -- Forwarded message --
> From: Romain Manni-Bucau 
> Date: 2015-10-05 7:02 GMT-07:00
> Subject: [RESULT][VOTE] Apache Johnzon 0.9.2-incubating release
> To: d...@johnzon.incubator.apache.org
>
>
> So vote passed with 4 binding +1 and 2 non-binding +1.
>
>
>
>
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Github <
> https://github.com/rmannibucau> |
> LinkedIn  | Tomitriber
> 
>
> 2015-10-02 6:44 GMT-07:00 Daniel Kulp :
>
> > +1
> >
> > Looks good to me.
> >
> > Dan
> >
> >
> >
> > > On Sep 30, 2015, at 3:33 PM, Romain Manni-Bucau  >
> > wrote:
> > >
> > > Hi
> > >
> > > As mentioned on the list here is the release vote for johnzon 0.9.2:
> > >
> > > he release is
> > > *
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-johnzon.git;a=commit;h=d88918a3b2704cf76687a894f897b2d768fe5cd5
> > > <
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-johnzon.git;a=commit;h=d88918a3b2704cf76687a894f897b2d768fe5cd5
> > >*
> > >
> > > Maven staging repo:
> > > *
> > https://repository.apache.org/content/repositories/orgapachejohnzon-1009
> > > <
> > https://repository.apache.org/content/repositories/orgapachejohnzon-1009
> >*
> > >
> > > Distribution archives (zip/tar.gz) with their hashes can be found
> under:
> > > *
> >
> https://repository.apache.org/content/repositories/orgapachejohnzon-1009/org/apache/johnzon/apache-johnzon/0.9.2-incubating/
> > > <
> >
> https://repository.apache.org/content/repositories/orgapachejohnzon-1009/org/apache/johnzon/apache-johnzon/0.9.2-incubating/
> > >*
> > >
> > > The files are also here (apache-johnzon-0.9.2-incubating-src*)
> > > https://dist.apache.org/repos/dist/dev/incubator/johnzon/
> > >
> > > PGP release keys:
> > > https://dist.apache.org/repos/dist/release/incubator/johnzon/KEYS
> > >
> > >
> > > The vote will be open for at least 72 hours or until we get 3 PMC +1
> > votes and
> > > no blocker is found.
> > >
> > > [ ] +1  yeah do it!
> > > [ ] +0  don't care
> > > [ ] -1  clearly not because [fill this input with your reason]
> > >
> > > Here is my +1
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau  |  Blog
> > >  | Github <
> > https://github.com/rmannibucau> |
> > > LinkedIn  | Tomitriber
> > > 
> >
> > --
> > Daniel Kulp
> > dk...@apache.org - http://dankulp.com/blog
> > Talend Community Coder - http://coders.talend.com
> >
> >
>

Re: Fwd: [RESULT][VOTE] Apache Johnzon 0.9.2-incubating release

[Romain Manni-Bucau]

understood it hasnt been clear enough in Mark's mail but still matches the
incubator policy. If not we can do the same vote with the same votes, not a
big deal.


Romain Manni-Bucau
@rmannibucau  |  Blog
 | Github  |
LinkedIn  | Tomitriber


2015-10-05 8:50 GMT-07:00 John D. Ament :

> I'm not sure that matches what we are saying.
> On Oct 5, 2015 10:34, "Romain Manni-Bucau"  wrote:
>
> > @Marvin: right for source/binary, sorry for this miswording
> >
> > Think we should graduate soon yes, just one of us needs to take time to
> do
> > it.
> >
> > Then I consider the vote done and will finish the release
> >
> > Thanks guys!
> >
> > 2015-10-05 7:29 GMT-07:00 John D. Ament :
> >
> > > I don't believe that to be the case.
> > >
> > > You guys are mature enough, why not graduate?
> > > On Oct 5, 2015 10:06 AM, "Romain Manni-Bucau" 
> > > wrote:
> > >
> > > > Hi incubator,
> > > >
> > > > Mark forwarded the vote at the beginning of dev@ vote. Therefore it
> > > sounds
> > > > to me we don't need to vote again on these binaries. Can you confirm
> it
> > > > please?
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau  |  Blog
> > > >  | Github <
> > > > https://github.com/rmannibucau> |
> > > > LinkedIn  | Tomitriber
> > > > 
> > > >
> > > > -- Forwarded message --
> > > > From: Romain Manni-Bucau 
> > > > Date: 2015-10-05 7:02 GMT-07:00
> > > > Subject: [RESULT][VOTE] Apache Johnzon 0.9.2-incubating release
> > > > To: d...@johnzon.incubator.apache.org
> > > >
> > > >
> > > > So vote passed with 4 binding +1 and 2 non-binding +1.
> > > >
> > > >
> > > >
> > > >
> > > > Romain Manni-Bucau
> > > > @rmannibucau  |  Blog
> > > >  | Github <
> > > > https://github.com/rmannibucau> |
> > > > LinkedIn  | Tomitriber
> > > > 
> > > >
> > > > 2015-10-02 6:44 GMT-07:00 Daniel Kulp :
> > > >
> > > > > +1
> > > > >
> > > > > Looks good to me.
> > > > >
> > > > > Dan
> > > > >
> > > > >
> > > > >
> > > > > > On Sep 30, 2015, at 3:33 PM, Romain Manni-Bucau <
> > > rmannibu...@gmail.com
> > > > >
> > > > > wrote:
> > > > > >
> > > > > > Hi
> > > > > >
> > > > > > As mentioned on the list here is the release vote for johnzon
> > 0.9.2:
> > > > > >
> > > > > > he release is
> > > > > > *
> > > > >
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-johnzon.git;a=commit;h=d88918a3b2704cf76687a894f897b2d768fe5cd5
> > > > > > <
> > > > >
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-johnzon.git;a=commit;h=d88918a3b2704cf76687a894f897b2d768fe5cd5
> > > > > >*
> > > > > >
> > > > > > Maven staging repo:
> > > > > > *
> > > > >
> > >
> https://repository.apache.org/content/repositories/orgapachejohnzon-1009
> > > > > > <
> > > > >
> > >
> https://repository.apache.org/content/repositories/orgapachejohnzon-1009
> > > > >*
> > > > > >
> > > > > > Distribution archives (zip/tar.gz) with their hashes can be found
> > > > under:
> > > > > > *
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachejohnzon-1009/org/apache/johnzon/apache-johnzon/0.9.2-incubating/
> > > > > > <
> > > > >
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachejohnzon-1009/org/apache/johnzon/apache-johnzon/0.9.2-incubating/
> > > > > >*
> > > > > >
> > > > > > The files are also here (apache-johnzon-0.9.2-incubating-src*)
> > > > > > https://dist.apache.org/repos/dist/dev/incubator/johnzon/
> > > > > >
> > > > > > PGP release keys:
> > > > > >
> https://dist.apache.org/repos/dist/release/incubator/johnzon/KEYS
> > > > > >
> > > > > >
> > > > > > The vote will be open for at least 72 hours or until we get 3 PMC
> > +1
> > > > > votes and
> > > > > > no blocker is found.
> > > > > >
> > > > > > [ ] +1  yeah do it!
> > > > > > [ ] +0  don't care
> > > > > > [ ] -1  clearly not because [fill this input with your reason]
> > > > > >
> > > > > > Here is my +1
> > > > > >
> > > > > > Romain Manni-Bucau
> > > > > > @rmannibucau  |  Blog
> > > > > >  | Github <
> > > > > https://github.com/rmannibucau> |
> > > > > > LinkedIn  | Tomitriber
> > > > > > 
> > > > >
> > > > > --
> > > > > Daniel Kulp
> > > > > dk...@apache.org - http://dankulp.com/blog
> > > > > Talend Community Coder - http://coders.talend.com
> > > > >
> > > > >
> > > >
> > >
> >
>

Re: Fwd: [RESULT][VOTE] Apache Johnzon 0.9.2-incubating release

[Marvin Humphrey]

On Mon, Oct 5, 2015 at 8:50 AM, John D. Ament  wrote:
> I'm not sure that matches what we are saying.

It matches what I was saying -- I think the thread was (barely,
arguably) within the letter of Incubator policy and thus it's not
necessary to run another vote.  But it sure would be nice if the
original vote thread had been clearer and spared us all this extra
meta discussion.

Marvin Humphrey

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

Re: Fwd: [RESULT][VOTE] Apache Johnzon 0.9.2-incubating release

[John D. Ament]

I'm not sure that matches what we are saying.
On Oct 5, 2015 10:34, "Romain Manni-Bucau"  wrote:

> @Marvin: right for source/binary, sorry for this miswording
>
> Think we should graduate soon yes, just one of us needs to take time to do
> it.
>
> Then I consider the vote done and will finish the release
>
> Thanks guys!
>
> 2015-10-05 7:29 GMT-07:00 John D. Ament :
>
> > I don't believe that to be the case.
> >
> > You guys are mature enough, why not graduate?
> > On Oct 5, 2015 10:06 AM, "Romain Manni-Bucau" 
> > wrote:
> >
> > > Hi incubator,
> > >
> > > Mark forwarded the vote at the beginning of dev@ vote. Therefore it
> > sounds
> > > to me we don't need to vote again on these binaries. Can you confirm it
> > > please?
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau  |  Blog
> > >  | Github <
> > > https://github.com/rmannibucau> |
> > > LinkedIn  | Tomitriber
> > > 
> > >
> > > -- Forwarded message --
> > > From: Romain Manni-Bucau 
> > > Date: 2015-10-05 7:02 GMT-07:00
> > > Subject: [RESULT][VOTE] Apache Johnzon 0.9.2-incubating release
> > > To: d...@johnzon.incubator.apache.org
> > >
> > >
> > > So vote passed with 4 binding +1 and 2 non-binding +1.
> > >
> > >
> > >
> > >
> > > Romain Manni-Bucau
> > > @rmannibucau  |  Blog
> > >  | Github <
> > > https://github.com/rmannibucau> |
> > > LinkedIn  | Tomitriber
> > > 
> > >
> > > 2015-10-02 6:44 GMT-07:00 Daniel Kulp :
> > >
> > > > +1
> > > >
> > > > Looks good to me.
> > > >
> > > > Dan
> > > >
> > > >
> > > >
> > > > > On Sep 30, 2015, at 3:33 PM, Romain Manni-Bucau <
> > rmannibu...@gmail.com
> > > >
> > > > wrote:
> > > > >
> > > > > Hi
> > > > >
> > > > > As mentioned on the list here is the release vote for johnzon
> 0.9.2:
> > > > >
> > > > > he release is
> > > > > *
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-johnzon.git;a=commit;h=d88918a3b2704cf76687a894f897b2d768fe5cd5
> > > > > <
> > > >
> > >
> >
> https://git-wip-us.apache.org/repos/asf?p=incubator-johnzon.git;a=commit;h=d88918a3b2704cf76687a894f897b2d768fe5cd5
> > > > >*
> > > > >
> > > > > Maven staging repo:
> > > > > *
> > > >
> > https://repository.apache.org/content/repositories/orgapachejohnzon-1009
> > > > > <
> > > >
> > https://repository.apache.org/content/repositories/orgapachejohnzon-1009
> > > >*
> > > > >
> > > > > Distribution archives (zip/tar.gz) with their hashes can be found
> > > under:
> > > > > *
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachejohnzon-1009/org/apache/johnzon/apache-johnzon/0.9.2-incubating/
> > > > > <
> > > >
> > >
> >
> https://repository.apache.org/content/repositories/orgapachejohnzon-1009/org/apache/johnzon/apache-johnzon/0.9.2-incubating/
> > > > >*
> > > > >
> > > > > The files are also here (apache-johnzon-0.9.2-incubating-src*)
> > > > > https://dist.apache.org/repos/dist/dev/incubator/johnzon/
> > > > >
> > > > > PGP release keys:
> > > > > https://dist.apache.org/repos/dist/release/incubator/johnzon/KEYS
> > > > >
> > > > >
> > > > > The vote will be open for at least 72 hours or until we get 3 PMC
> +1
> > > > votes and
> > > > > no blocker is found.
> > > > >
> > > > > [ ] +1  yeah do it!
> > > > > [ ] +0  don't care
> > > > > [ ] -1  clearly not because [fill this input with your reason]
> > > > >
> > > > > Here is my +1
> > > > >
> > > > > Romain Manni-Bucau
> > > > > @rmannibucau  |  Blog
> > > > >  | Github <
> > > > https://github.com/rmannibucau> |
> > > > > LinkedIn  | Tomitriber
> > > > > 
> > > >
> > > > --
> > > > Daniel Kulp
> > > > dk...@apache.org - http://dankulp.com/blog
> > > > Talend Community Coder - http://coders.talend.com
> > > >
> > > >
> > >
> >
>

Re: Fwd: [RESULT][VOTE] Apache Johnzon 0.9.2-incubating release

[John D. Ament]

I'm fine either way.  Could the podling forward their result at least with
the IPMC binding votes listed?
On Oct 5, 2015 11:58, "Marvin Humphrey"  wrote:

> On Mon, Oct 5, 2015 at 8:50 AM, John D. Ament 
> wrote:
> > I'm not sure that matches what we are saying.
>
> It matches what I was saying -- I think the thread was (barely,
> arguably) within the letter of Incubator policy and thus it's not
> necessary to run another vote.  But it sure would be nice if the
> original vote thread had been clearer and spared us all this extra
> meta discussion.
>
> Marvin Humphrey
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: Fwd: [RESULT][VOTE] Apache Johnzon 0.9.2-incubating release

[Romain Manni-Bucau]

the +1 bindings listed in the result were the ipmc votes, ie:

- Mark
- Justin
- Daniel
- and me



Romain Manni-Bucau
@rmannibucau  |  Blog
 | Github  |
LinkedIn  | Tomitriber


2015-10-05 9:30 GMT-07:00 John D. Ament :

> I'm fine either way.  Could the podling forward their result at least with
> the IPMC binding votes listed?
> On Oct 5, 2015 11:58, "Marvin Humphrey"  wrote:
>
> > On Mon, Oct 5, 2015 at 8:50 AM, John D. Ament 
> > wrote:
> > > I'm not sure that matches what we are saying.
> >
> > It matches what I was saying -- I think the thread was (barely,
> > arguably) within the letter of Incubator policy and thus it's not
> > necessary to run another vote.  But it sure would be nice if the
> > original vote thread had been clearer and spared us all this extra
> > meta discussion.
> >
> > Marvin Humphrey
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>

Fwd: [VOTE] Apache Johnzon 0.9.2-incubating release

[Mark Struberg]

FYI. Apache Johnzon is currently voting on 0.9.2-incubating.

txs and LieGrue,
strub


> Anfang der weitergeleiteten Nachricht:
> 
> Von: Romain Manni-Bucau 
> Datum: 30. September 2015 um 21:33:49 MESZ
> An: d...@johnzon.incubator.apache.org
> Betreff: [VOTE] Apache Johnzon 0.9.2-incubating release
> 
> Hi
> 
> As mentioned on the list here is the release vote for johnzon 0.9.2:
> 
> he release is
> *https://git-wip-us.apache.org/repos/asf?p=incubator-johnzon.git;a=commit;h=d88918a3b2704cf76687a894f897b2d768fe5cd5
> *
> 
> Maven staging repo:
> *https://repository.apache.org/content/repositories/orgapachejohnzon-1009
> *
> 
> Distribution archives (zip/tar.gz) with their hashes can be found under:
> *https://repository.apache.org/content/repositories/orgapachejohnzon-1009/org/apache/johnzon/apache-johnzon/0.9.2-incubating/
> *
> 
> The files are also here (apache-johnzon-0.9.2-incubating-src*)
> https://dist.apache.org/repos/dist/dev/incubator/johnzon/
> 
> PGP release keys:
> https://dist.apache.org/repos/dist/release/incubator/johnzon/KEYS
> 
> 
> The vote will be open for at least 72 hours or until we get 3 PMC +1 votes and
> no blocker is found.
> 
> [ ] +1  yeah do it!
> [ ] +0  don't care
> [ ] -1  clearly not because [fill this input with your reason]
> 
> Here is my +1
> 
> Romain Manni-Bucau
> @rmannibucau  |  Blog
>  | Github  |
> LinkedIn  | Tomitriber
> 


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

Fwd: [VOTE] Release Apache Open Climate Workbench 1.0.0

[lewis john mcgibbney]

Hi general@i.a.o,

The Apache Open Climate Workbench (OCW) [0] 1.0.0 release candidate is
struggling for attention. This is a major release and it really does
deserve attention.
We require binding and authoritative VOTE(s), we already have 2, however
this is not enough to release the code.
We would like to utilize and leverage the resources of the IPMC to review
and determine the outcome of OCW 1.0.0.
Thank you IPMC for your review, please direct any issues to dev@climate
Lewis
(on behalf of OCW PMC)

[0] http://climate.apache.org/

-- Forwarded message --
From: Lewis John Mcgibbney 
Date: Thu, Sep 3, 2015 at 1:02 PM
Subject: [VOTE] Release Apache Open Climate Workbench 1.0.0
To: d...@climate.apache.org


Hi all,

The second release candidate for Apache Open Climate Workbench 1.0.0 is now
available.

The tag for this release is available at:
*http://s.apache.org/1.0.0rc1 *


Release artifacts are available for review at:
https://dist.apache.org/repos/dist/dev/climate/1.0.0_rc1/


Please vote on releasing these packages as Apache OCW 1.0.0. The vote is
open for at least the next 72 hours


Only votes from Apache OCW PMC are binding, but folks are welcome to check
the
release candidate and voice their approval or disapproval. The vote passes
if at least three binding +1 votes are cast.

[ ] +1 Release the packages as Apache OCW 1.0.0

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

P.S Kudos to whoever produced the release documentation.
P.P.S Here's my +1
Thanks


-- 
*Lewis*



-- 

` :
:   , :
 #+`. ,,`,
` ;##`  .`,.  ;;':;`
 `` ##@.;.;: ,;+;;;';;';;';'`
  ```,###:  .,;; +;;'';;+;;;';;`
```#+##'``;+ '';;;'';;';;;';;;`
 ```,##+#@:: ''';';;';+;;';;':::+:
   ```.#'';';+;;';';';;';;';;':,;:
 '#+#+#';';''';;';';;';;';'::
  ;;:';,##''';'';;';';;'';;;'::';;;':.```
`.,`;;;++';'';;';'';;';;;';;'::';;:;';;;::
:`,.,.`:';+#+;;''';'';';';;';;';;';;;'::;';:;.
   .`..;,:`';;';';;;'+#+';;''+';;';:'';;';';;;':::;,:`
` ,`:. ;;;';';;;++#+'';''';''+;;';;';::';';;:..
  ` `` ;;;';';';';;'+###+';';'';;';;';;';;';;;';;',:.
  ` `  `;:;;';';';;;'+;';';;';;';;';;';;'';;';';::;
   
`.;,:::;::;';';;'#++''';;';;;'';+';:::''::;;..:

```:,'::,;';';;;';;;''##+++'';;';;';;;''';;':,,,:.:,.`

```..::,;';:;';';';;;';';';';'''++###+'+;';;;';;;';;:;.:..:..,

,;;:;:;';''';''++##+++.:..:.,;
`

`.``,,:,';;::;;::';';;;';';;';';;';';;';;';';';'++#+###@#++:...,,.;:.

`:.';.,;;',,;;;';';;';;':;;;';';;';;';';';;';;;''.:,:.,:'#@'::,

```.:,';;.::':';';',;;;';;':;';;';;';;;';;';'';;.;.,.:..,:.::

``:::',:;';;,:;;',:';';;':';';;;';;'::';;;,..,.,.,:+`

`..:'+:';;',;';,:;:';;;,,';::,';;',,';;.:.:;,

``,.';;:':,;:;,,:;:::``..,:,``

:`;;`

``: ,:`







http://people.apache.org/~lewismc || @hectorMcSpector ||
http://www.linkedin.com/in/lmcgibbney

  Apache Gora V.P || Apache Nutch PMC || Apache Any23 V.P ||
Apache OODT PMC
   Apache Open Climate Workbench PMC || Apache Tika PMC || Apache TAC
Apache Usergrid || Apache HTrace (incubating) || Apache CommonsRDF
(incubating)

Re: Fwd: [VOTE] Release Apache Open Climate Workbench 1.0.0

[Daniel Gruno]

+1

- Sigs okay
- Digest matches archive
- license and notice in order

There are a few missing license headers, but other than that, it seems
okay. See http://compliance.rocks/result.html?d704977 for more details
about the headers.

With regards,
Daniel.

On 09/18/2015 01:13 PM, lewis john mcgibbney wrote:
> Hi general@i.a.o,
> 
> The Apache Open Climate Workbench (OCW) [0] 1.0.0 release candidate is
> struggling for attention. This is a major release and it really does
> deserve attention.
> We require binding and authoritative VOTE(s), we already have 2, however
> this is not enough to release the code.
> We would like to utilize and leverage the resources of the IPMC to review
> and determine the outcome of OCW 1.0.0.
> Thank you IPMC for your review, please direct any issues to dev@climate
> Lewis
> (on behalf of OCW PMC)
> 
> [0] http://climate.apache.org/
> 
> -- Forwarded message --
> From: Lewis John Mcgibbney 
> Date: Thu, Sep 3, 2015 at 1:02 PM
> Subject: [VOTE] Release Apache Open Climate Workbench 1.0.0
> To: d...@climate.apache.org
> 
> 
> Hi all,
> 
> The second release candidate for Apache Open Climate Workbench 1.0.0 is now
> available.
> 
> The tag for this release is available at:
> *http://s.apache.org/1.0.0rc1 *
> 
> 
> Release artifacts are available for review at:
> https://dist.apache.org/repos/dist/dev/climate/1.0.0_rc1/
> 
> 
> Please vote on releasing these packages as Apache OCW 1.0.0. The vote is
> open for at least the next 72 hours
> 
> 
> Only votes from Apache OCW PMC are binding, but folks are welcome to check
> the
> release candidate and voice their approval or disapproval. The vote passes
> if at least three binding +1 votes are cast.
> 
> [ ] +1 Release the packages as Apache OCW 1.0.0
> 
> [ ] -1 Do not release the packages because...
> 
> P.S Kudos to whoever produced the release documentation.
> P.P.S Here's my +1
> Thanks
> 
> 


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

Re: Fwd: [VOTE] Release Apache Open Climate Workbench 1.0.0

[Atri Sharma]

Anyway I can help?

I am not an IPMC member but willing to support this release.
On 18 Sep 2015 16:43, "lewis john mcgibbney"  wrote:

> Hi general@i.a.o,
>
> The Apache Open Climate Workbench (OCW) [0] 1.0.0 release candidate is
> struggling for attention. This is a major release and it really does
> deserve attention.
> We require binding and authoritative VOTE(s), we already have 2, however
> this is not enough to release the code.
> We would like to utilize and leverage the resources of the IPMC to review
> and determine the outcome of OCW 1.0.0.
> Thank you IPMC for your review, please direct any issues to dev@climate
> Lewis
> (on behalf of OCW PMC)
>
> [0] http://climate.apache.org/
>
> -- Forwarded message --
> From: Lewis John Mcgibbney 
> Date: Thu, Sep 3, 2015 at 1:02 PM
> Subject: [VOTE] Release Apache Open Climate Workbench 1.0.0
> To: d...@climate.apache.org
>
>
> Hi all,
>
> The second release candidate for Apache Open Climate Workbench 1.0.0 is now
> available.
>
> The tag for this release is available at:
> *http://s.apache.org/1.0.0rc1 *
>
>
> Release artifacts are available for review at:
> https://dist.apache.org/repos/dist/dev/climate/1.0.0_rc1/
>
>
> Please vote on releasing these packages as Apache OCW 1.0.0. The vote is
> open for at least the next 72 hours
>
>
> Only votes from Apache OCW PMC are binding, but folks are welcome to check
> the
> release candidate and voice their approval or disapproval. The vote passes
> if at least three binding +1 votes are cast.
>
> [ ] +1 Release the packages as Apache OCW 1.0.0
>
> [ ] -1 Do not release the packages because...
>
> P.S Kudos to whoever produced the release documentation.
> P.P.S Here's my +1
> Thanks
>
>
> --
> *Lewis*
>
>
>
> --
>
> ` :
> :   , :
>  #+`. ,,`,
> ` ;##`  .`,.  ;;':;`
>  `` ##@.;.;: ,;+;;;';;';;';'`
>   ```,###:  .,;; +;;'';;+;;;';;`
> ```#+##'``;+ '';;;'';;';;;';;;`
>  ```,##+#@:: ''';';;';+;;';;':::+:
>```.#'';';+;;';';';;';;';;':,;:
>  '#+#+#';';''';;';';;';;';'::
>   ;;:';,##''';'';;';';;'';;;'::';;;':.```
> `.,`;;;++';'';;';'';;';;;';;'::';;:;';;;::
> :`,.,.`:';+#+;;''';'';';';;';;';;';;;'::;';:;.
>.`..;,:`';;';';;;'+#+';;''+';;';:'';;';';;;':::;,:`
> ` ,`:. ;;;';';;;++#+'';''';''+;;';;';::';';;:..
>   ` ``
> ;;;';';';';;'+###+';';'';;';;';;';;';;;';;',:.
>   ` `
> `;:;;';';';;;'+;';';;';;';;';;';;'';;';';::;
>
>  `.;,:::;::;';';;'#++''';;';;;'';+';:::''::;;..:
>
> ```:,'::,;';';;;';;;''##+++'';;';;';;;''';;':,,,:.:,.`
>
> ```..::,;';:;';';';;;';';';';'''++###+'+;';;;';;;';;:;.:..:..,
>
> ,;;:;:;';''';''++##+++.:..:.,;
> `
>
> `.``,,:,';;::;;::';';;;';';;';';;';';;';;';';';'++#+###@#++:...,,.;:.
>
> `:.';.,;;',,;;;';';;';;':;;;';';;';;';';';;';;;''.:,:.,:'#@'::,
>
> ```.:,';;.::':';';',;;;';;':;';;';;';;;';;';'';;.;.,.:..,:.::
>
> ``:::',:;';;,:;;',:';';;':';';;;';;'::';;;,..,.,.,:+`
>
> `..:'+:';;',;';,:;:';;;,,';::,';;',,';;.:.:;,
>
> ``,.';;:':,;:;,,:;:::``..,:,``
>
> :`;;`
>
> ``: ,:`
>
>
>
>
>
>
>
> http://people.apache.org/~lewismc || @hectorMcSpector ||
> http://www.linkedin.com/in/lmcgibbney
>
>   Apache Gora V.P || Apache Nutch PMC || Apache Any23 V.P ||
> Apache OODT PMC
>Apache Open Climate Workbench PMC || Apache Tika PMC || Apache
> TAC
> Apache Usergrid || Apache HTrace (incubating) || Apache CommonsRDF
> (incubating)
>