Re: [VOTE] Release Apache Guacamole 0.9.11-incubating (RC1)

2017-02-02 Thread Sergio Fernández
+1 (binding)

On Thu, Jan 26, 2017 at 10:18 PM, Mike Jumper 
wrote:

> Hello Incubator PMC,
>
> The Apache Guacamole community has voted on and approved a proposal to
> release Apache Guacamole 0.9.11-incubating.
>
> We now kindly request that the Incubator PMC members review and vote on
> this incubator release.
>
> The VOTE RESULT is here:
>
> http://mail-archives.apache.org/mod_mbox/incubator-
> guacamole-dev/201701.mbox/%3CCALKeL-PA3VO0kgetj15aVTp%
> 3D5uD2G3s88Hf6Hi_ozp507R9OFg%40mail.gmail.com%3E
>
> The draft release notes (along with links to artifacts,
> signatures/checksums, and updated documentation) can be found here:
>
> http://guacamole.incubator.apache.org/releases/0.9.11-incubating/
>
> The git tag for all relevant repositories is "0.9.11-incubating-RC1":
>
> https://github.com/apache/incubator-guacamole-client/tree/0.
> 9.11-incubating-RC1
> https://github.com/apache/incubator-guacamole-server/tree/0.
> 9.11-incubating-RC1
> https://github.com/apache/incubator-guacamole-manual/tree/0.
> 9.11-incubating-RC1
>
> Build instructions are included in the manual, which is part of the updated
> documentation referenced above. For convenience:
>
> http://guacamole.incubator.apache.org/doc/0.9.11-incubating/
> gug/installing-guacamole.html
>
> Maven artifacts for guacamole-ext can be found in the following staging
> repository (guacamole-common and guacamole-common-js are unchanged from the
> previous release):
>
> https://repository.apache.org/content/repositories/orgapacheguacamole-1005
>
> Source and binary distributions (also linked within the release notes):
>
> https://dist.apache.org/repos/dist/dev/incubator/guacamole/0
> .9.11-incubating-RC1/
>
> Artifacts have been signed with the "mjum...@apache.org" key listed in:
>
> https://dist.apache.org/repos/dist/dev/incubator/guacamole/KEYS
>
> Please review and vote:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
>
> - Mike
>



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


Re: Request for write access to Apache Incubator Wiki

2017-02-02 Thread Connie Yang
My page is Rheos Proposal, HTTPS://wiki.apache.org/incubator/RheosProposal

On Feb 1, 2017 2:49 PM, "Connie Yang"  wrote:

> Hello,
>
> Please grant Connie Yang write access to Apache Incubator Wiki.  I'm in
> the process of submitting an Apache project proposal.  So, I will need
> update access to my wiki once it's promoted.
>
> Thanks
> Connie
>


Request for write access to Apache Incubator Wiki

2017-02-02 Thread Connie Yang
Hello,

Please grant Connie Yang write access to Apache Incubator Wiki.  I'm in the
process of submitting an Apache project proposal.  So, I will need update
access to my wiki once it's promoted.

Thanks
Connie


Re: [DISCUSS] Podling report format changes

2017-02-02 Thread Shane Curcuru
John D. Ament wrote on 1/24/17 8:15 PM:
> All,
> 
> The Incubator PMC has received feedback from the board that changes may
> need to be made to the structure of our report.  Specifically, there is
> confusion from the board members over how podlings get classified.  There
> is also a request to increase and improve mentor feedback on podling
> reports.  Based on this input, I would like to propose the following
> changes to our report format.  I would like to try to implement this for
> the March report, if not before then.
> 
> 1. Eliminate the podling summary section of the report.  It shouldn't be on
> the report manager to classify each podling.  We have begun leveraging a
> maturity model for podlings, while its not required to fulfill it serves as
> an equivalent to this section.  The list of podlings who failed to report
> shall remain.

+1, if this simplifies work it's fine.

> 
> 2. Add a "Podling Maturity Assessment" to the individual podling reports.
> This would give a clear opportunity for each podling to describe how they
> are doing, perhaps compared to the maturity model or our classic categories.

+1, with a general encouragement to start each with a simple category.
That is, when scanning the whole report, it would be very helpful to see
one of "Ready to Graduate", "Some Community Growth", "No Release" and
"Still Getting Started" or a similar set of values.  Any additional
description is great, but having fairly consistent markers really helps
get a sense of progress across the whole incubator.

Personally I like the maturity model, so using that is great, but I do
understand that we may not always have cycles to use it.

> 
> 3. Change the mentor sign off section to include a per-mentor comment.
> E.g. instead of the current:
> 
>   [ ](podling) mentor1
>   [ ](podling) mentor2
>   [ ](podling) mentor3
> 
> It would be:
> 
>   [ ](podling) mentor1
>   Comments:
>   [ ](podling) mentor2
>   Comments:
>   [ ](podling) mentor3
>   Comments:
> 
> And rename Shepherd/Mentor notes: to just "Shepherd notes:"

Big +1.  Having even a sentence for most mentors with their thoughts is
a huge improvement if we can get it.

> 
> Thoughts?
> 
> John

Thanks, John!

- Shane


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



Re: [VOTE] Release apache-singa-incubating-1.1.0 (RC1)

2017-02-02 Thread Anh Dinh
+1 (non-binding)

I've checked:
LICENSE file
no binaries
hash and signature correct

Would appreciate PMC members to help check and cast their votes.

Anh.


On 30 January 2017 at 09:24, Wang Wei  wrote:

> Hi all,
>
> The SINGA community has voted on and approved a proposal to release Apache
> SINGA 1.1.0 (incubating).
>
> The vote thread is at:
> http://mail-archives.apache.org/mod_mbox/singa-dev/201701.mbox/%
> 3CCAJz0iLvAaEd5AgCqaWFD1M4-D_3EBh%3DUHbeZu-MRn%3DcKuQiX-Q%40mail.gmail.com
> %3E
>
> and the result is at:
> http://mail-archives.apache.org/mod_mbox/singa-dev/201701.mbox/%
> 3ccajz0ilspborscstawuraowwetidb4cn14ak5sgdyb8umxoj...@mail.gmail.com%3e
>
> We ask the IPMC to vote on this release.
>
> The artifacts to be voted on are located here:
> https://dist.apache.org/repos/dist/dev/incubator/singa/1.1.0/
>
> The hashes of the artifacts are as follows:
> MD5:  08 CA 31 10 4E 79 02 16  A1 D7 3F 20 2D 60 21 BB
>
> Release artifacts are signed with the following key:
> https://people.apache.org/keys/committer/dinhtta.asc
>
> and the signature file is:
> https://dist.apache.org/repos/dist/dev/incubator/singa/1.1.0
> /apache-singa-incubating-1.1.0-RC1.tar.gz.asc
>
> The Github tag is at:
> https://github.com/apache/incubator-singa/releases/tag/v1.1.0-rc1
> commit ID is: 59ca44a7ce38ce4f965511c805cda074d0b8e360
>
> To check the license, you can use the Apache Rat tool as follows:
> 1. download & decompress apache rat from http://creadur.apache.org/rat/
> download_rat.cgi
> 2. run the following command under singa folder:
> java -jar /PATH/TO/RAT/apache-rat-0.11.jar -E rat-excludes -d . >
> rat_check
> 3. check the results in file named "rat_check"
>
> Please check and vote on releasing this package. The vote is open for at
> least 72 hours and passes if a majority of at least three +1 votes are
> cast.
>
> [ ] +1 Release this package as Apache SINGA 1.0.0-incubating
> [ ]  0 I don't feel strongly about it, but I'm okay with the release
> [ ] -1 Do not release this package because...
>
> Best,
> Wei
>


Incubator wiki write access

2017-02-02 Thread Liang Chen
Hi

Please grant me (username:chenliang613) write access to Apache Incubator
Wiki for podling report.

Thanks.

Regards
Liang


[RESULT] [VOTE] Release Apache Guacamole 0.9.11-incubating (RC1)

2017-02-02 Thread Mike Jumper
On Thu, Jan 26, 2017 at 1:18 PM, Mike Jumper  wrote:
> Hello Incubator PMC,
>
> The Apache Guacamole community has voted on and approved a proposal to
> release Apache Guacamole 0.9.11-incubating.
>
> We now kindly request that the Incubator PMC members review and vote on this
> incubator release.
>
> The VOTE RESULT is here:
>
> http://mail-archives.apache.org/mod_mbox/incubator-guacamole-dev/201701.mbox/%3CCALKeL-PA3VO0kgetj15aVTp%3D5uD2G3s88Hf6Hi_ozp507R9OFg%40mail.gmail.com%3E
>
> The draft release notes (along with links to artifacts,
> signatures/checksums, and updated documentation) can be found here:
>
> http://guacamole.incubator.apache.org/releases/0.9.11-incubating/
>
> The git tag for all relevant repositories is "0.9.11-incubating-RC1":
>
> https://github.com/apache/incubator-guacamole-client/tree/0.9.11-incubating-RC1
> https://github.com/apache/incubator-guacamole-server/tree/0.9.11-incubating-RC1
> https://github.com/apache/incubator-guacamole-manual/tree/0.9.11-incubating-RC1
>
> Build instructions are included in the manual, which is part of the updated
> documentation referenced above. For convenience:
>
> http://guacamole.incubator.apache.org/doc/0.9.11-incubating/gug/installing-guacamole.html
>
> Maven artifacts for guacamole-ext can be found in the following staging
> repository (guacamole-common and guacamole-common-js are unchanged from the
> previous release):
>
> https://repository.apache.org/content/repositories/orgapacheguacamole-1005
>
> Source and binary distributions (also linked within the release notes):
>
> https://dist.apache.org/repos/dist/dev/incubator/guacamole/0.9.11-incubating-RC1/
>
> Artifacts have been signed with the "mjum...@apache.org" key listed in:
>
> https://dist.apache.org/repos/dist/dev/incubator/guacamole/KEYS
>
> Please review and vote:
>
> [ ] +1 Approve the release
> [ ] -1 Don't approve the release (please provide specific comments)
>
> This vote will be open for at least 72 hours.
>
> Thanks,
>
> - Mike
>

The VOTE for releasing Apache Guacamole 0.9.11-incubating is now
closed. With a total of +4 binding votes and NO -1 votes, the VOTE
passes. Overall binding vote breakdown is as follows:

+1 Justin Mclean
+1 Jim Jagielski
+1 Jean-Baptiste Onofré
+1 Sergio Fernández

Thanks to everyone for taking the time to review and vote. We will now
proceed with the release.

- Mike

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



Re: Incubator wiki write access

2017-02-02 Thread Nick Burch

On Thu, 2 Feb 2017, Liang Chen wrote:
Please grant me (username:chenliang613) write access to Apache Incubator 
Wiki for podling report.


Karma granted, enjoy!

Nick

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



Re: Request for write access to Apache Incubator Wiki

2017-02-02 Thread Nick Burch

On Wed, 1 Feb 2017, Connie Yang wrote:

Please grant Connie Yang write access to Apache Incubator Wiki.  I'm in
the process of submitting an Apache project proposal.  So, I will need
update access to my wiki once it's promoted.


I've granted write permissions to the username "Connie Yang", let us know 
if you're using something else


Nick

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



[VOTE] Release Apache Traffic Control 1.8.0-incubating (RC9)

2017-02-02 Thread Dan Kirkwood
Hello Incubator PMC,

The Apache Traffic Control community has voted on and approved a
proposal to release Apache Traffic Control 1.8.0-incubating.  We now
kindly request that the Incubator PMC members review and vote on this
incubator release.

The VOTE RESULT is here:

https://lists.apache.org/thread.html/4aa7f70b34ba9d2e4190301ae7ea118aa86b297c81e60467aedaf3dc@%3Cdev.trafficcontrol.apache.org%3E

The draft release notes (along with links to artifacts,
signatures/checksums, and updated documentation) can be found here:

http://trafficcontrol.incubator.apache.org/downloads/

The git tag for the repository is "RELEASE-1.8.0-RC9":
https://github.com/apache/incubator-trafficcontrol/releases/tag/RELEASE-1.8.0-RC9

The source distribution (also linked in the release notes) is here:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/1.8.0/RC9/

Build instructions are included in the BUILD.md file which is
included in the source artifact.

Artifacts have been signed with the "dang...@apache.org" key listed in:

https://dist.apache.org/repos/dist/dev/incubator/trafficcontrol/KEYS

Please review and vote:

[  ] +1 Approve the release
[  ] -1 Don't approve the release (please provide specific comments)

This vote will be open for at least 72 hours.

Thanks,

- Dan

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



Re: [DISCUSS] Podling report format changes

2017-02-02 Thread Marvin Humphrey
On Thu, Feb 2, 2017 at 5:52 AM, Shane Curcuru  wrote:
> John D. Ament wrote on 1/24/17 8:15 PM:

>> 2. Add a "Podling Maturity Assessment" to the individual podling reports.
>> This would give a clear opportunity for each podling to describe how they
>> are doing, perhaps compared to the maturity model or our classic categories.
>
> +1, with a general encouragement to start each with a simple category.
> That is, when scanning the whole report, it would be very helpful to see
> one of "Ready to Graduate", "Some Community Growth", "No Release" and
> "Still Getting Started" or a similar set of values.  Any additional
> description is great, but having fairly consistent markers really helps
> get a sense of progress across the whole incubator.
>
> Personally I like the maturity model, so using that is great, but I do
> understand that we may not always have cycles to use it.

How we implement this matters a great deal.  It should be possible to figure
out what to do simply from the template -- if it is not clear, I anticipate
befuddlement and backlash.  A lot of our podlings and Mentors do not
participate in these centralized discussions, and a disruptive change to
reporting will incur a large community cost.

Thus, I propose this addition to the template:

How would you assess the podling's maturity?  Please feel free to add your
own commentary.

  [ ] 1. Initial setup
  [ ] 2. Working towards first release
  [ ] 3. Community building
  [ ] 4. Nearing graduation
  [ ] Other:

A bit long perhaps, but that will be solved the day we integrate podling
reporting into Whimsy. :)

>> 3. Change the mentor sign off section to include a per-mentor comment.
>> E.g. instead of the current:
>>
>>   [ ](podling) mentor1
>>   [ ](podling) mentor2
>>   [ ](podling) mentor3
>>
>> It would be:
>>
>>   [ ](podling) mentor1
>>   Comments:
>>   [ ](podling) mentor2
>>   Comments:
>>   [ ](podling) mentor3
>>   Comments:
>>
>> And rename Shepherd/Mentor notes: to just "Shepherd notes:"
>
> Big +1.  Having even a sentence for most mentors with their thoughts is
> a huge improvement if we can get it.

I agree, this is very nice.

Marvin Humphrey

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



[VOTE] Apache SystemML 0.12.0-incubating (RC2)

2017-02-02 Thread Arvind Surve
Please vote on releasing the following candidate as Apache SystemML version 
0.12.0-incubating !

The vote is open for at least 72 hours and passes if a majority of at least 3 
+1 PMC votes are cast.

[ ] +1 Release this package as Apache SystemML 0.12.0-incubating
[ ] -1 Do not release this package because ...

To learn more about Apache SystemML, please see http://systemml.apache.org/

The tag to be voted on is v0.12.0-incubating-rc2 
(d96a17f64cef7f251d9592679ecdee7ac17feb04)

https://github.com/apache/incubator-systemml/commit/d96a17f64cef7f251d9592679ecdee7ac17feb04

The release artifacts can be found at :

https://dist.apache.org/repos/dist/dev/incubator/systemml/0.12.0-incubating-rc2/

The maven release artifacts, including signatures, digests, etc. can be found 
at:

https://repository.apache.org/content/repositories/orgapachesystemml-1013/

PPMC Vote Mail 
Threadhttps://www.mail-archive.com/dev@systemml.incubator.apache.org/msg01321.html

PPMC Vote Results 
Mailhttps://www.mail-archive.com/dev@systemml.incubator.apache.org/msg01349.html



 --     Arvind Surve     Spark Technology Center     
http://www.spark.tc/

[VOTE] Retire the Climate Model Data Analyzer Podling

2017-02-02 Thread John D. Ament
All,

Due to the lack of progress made by the CMDA podling I am calling a vote to
retire them.  A discussion and vote thread [1] have occurred on the
podling's lists.  It was confirmed that development activities happen
outside the ASF.

I'm considering this a 72 hour lazy consensus vote since 3 IPMC members
voted +1 on the podling's list.  My +1 is implied due to the fact that I've
been monitoring them and am calling this vote.

John

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


Re: [VOTE] Retire the Climate Model Data Analyzer Podling

2017-02-02 Thread Ted Dunning
+1



On Thu, Feb 2, 2017 at 4:20 PM, John D. Ament  wrote:

> All,
>
> Due to the lack of progress made by the CMDA podling I am calling a vote to
> retire them.  A discussion and vote thread [1] have occurred on the
> podling's lists.  It was confirmed that development activities happen
> outside the ASF.
>
> I'm considering this a 72 hour lazy consensus vote since 3 IPMC members
> voted +1 on the podling's list.  My +1 is implied due to the fact that I've
> been monitoring them and am calling this vote.
>
> John
>
> [1]:
> https://lists.apache.org/thread.html/ac4de53d2b16afb91142449d7832f6
> 713f54eb9a1fd2d9c6c3efaffb@%3Cdev.cmda.apache.org%3E
>


Re: [VOTE] Retire the Climate Model Data Analyzer Podling

2017-02-02 Thread James Carman
+1

On Thu, Feb 2, 2017 at 7:20 PM John D. Ament  wrote:

> All,
>
> Due to the lack of progress made by the CMDA podling I am calling a vote to
> retire them.  A discussion and vote thread [1] have occurred on the
> podling's lists.  It was confirmed that development activities happen
> outside the ASF.
>
> I'm considering this a 72 hour lazy consensus vote since 3 IPMC members
> voted +1 on the podling's list.  My +1 is implied due to the fact that I've
> been monitoring them and am calling this vote.
>
> John
>
> [1]:
>
> https://lists.apache.org/thread.html/ac4de53d2b16afb91142449d7832f6713f54eb9a1fd2d9c6c3efaffb@%3Cdev.cmda.apache.org%3E
>