Re: [DISCUSS] Apache Guacamole Incubator Proposal

[Mike Jumper]

On Mon, Jan 25, 2016 at 8:20 AM, Noel J. Bergman  wrote:
> I've been aware of Guacamole for several years.  Definitely keen to see it 
> join the ASF.
>

Thanks, Noel!

I've been keeping the rest of the guac team apprised of the overall
response here, and we're all pretty enthused to be bumping into fellow
guac users like yourself and Greg Trasuk just by bringing forth the
proposal. Very exciting times.

- Mike

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

Re: Podlings in phonebook

[Mike Jumper]

I went ahead and tried looking up the phonebook entries for each of
the current podlings[1], and something definitely seems amiss. Roughly
half are missing:

airflow
atlas
beam
cmda
fineract
freemarker
gearpump
geode
gossip
guacamole
horn
iota
madlib
milagro
mnemonic
mynewt
odftoolkit
omid
openaz
quickstep
sirona
tephra
toree
trafodion
unomi
zeppelin

- Mike

[1] http://incubator.apache.org/


On Tue, May 10, 2016 at 11:04 AM, Julian Hyde  wrote:
> The quickstep podling does not appear in the phonebook[1]. Are there any 
> steps we missed in setting up the podling? (I know this is an infrastructure 
> question, but I have a feeling that we need to update some of our process 
> documents.)
>
> Julian
>
> [1] https://people.apache.org/phonebook.html?podling=quickstep 
> 

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

Re: Throwing my hat in the ring

[Mike Jumper]

On Sat, May 14, 2016 at 6:18 PM,   wrote:
>
> ...
>
> AIUI, I'm able to be an informal mentor for any podlings of interest (hey,
> there Guacamole!) so I'll just kinda poke around with that for a while, but
> I'll also keep an eye out here for other stuff that comes up.
>

"Hey, Daniel!" - Guacamole

This all sounds informally-great to me. You're definitely welcome; the
more the merrier.

- Mike

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

GitHub vs. the mailing lists

[Mike Jumper]

Hello all,

Does anyone here have any experience with using GitHub pull requests in a
code review workflow which leverages a podling's mailing lists?

Since things have only happened if on the mailing lists, it'd be nice if PR
activity could truly "happen" as well.

I'm specifically interested in configuring the ASF GitHub mirrors to
automatically send pull request notifications (comments, status changes,
etc.) to the commits list, but alternative methods are definitely welcome
if this is not actually possible.

Thanks,

- Mike

Re: GitHub vs. the mailing lists

[Mike Jumper]

On May 18, 2016 9:54 AM, "Jean-Baptiste Onofré"  wrote:
>
> Hi Mike,
>
> it's what we are doing at Beam.
>
> A PR submission result:
> - to a mail on the mailing list
> - to a comment in Jira (if the PR contains commit with issue ID).
>

How have you achieved this?

For Guacamole, we're seeing emails for the merge of a PR only (due no doubt
to hooks in the ASF git repos). Comments on a PR, etc. will not find their
way to the list.

RE: GitHub vs. the mailing lists

[Mike Jumper]

On May 18, 2016 10:06 AM, "Steve Varnau"  wrote:
>
> Infra can configure the github to mailing list & github to JIRA for you.
>
> In trafodion, we have all github PR and comments going to a codereview
mail
> list
> http://mail-archives.apache.org/mod_mbox/incubator-trafodion-codereview/
> So there is a catch-all, even if the PR title is not in the correct format
> to mirror into Jira. (And for those that prefer email notice versus
> following on GH or Jira.)
>

Beautiful. Thanks, Steve.

Re: Toree's One Release Constraint

[Mike Jumper]

On May 19, 2016 10:30 AM, "Gino Bustelo"  wrote:
>
> I write this to start a discussion about the "One release constraint"
> placed on Toree and what I feel is an unreasonable constraint on a project
> that is undergoing incubation. A brief background first...
>
> In Toree we have an LGPL dependency that is not a simple rip an replace.
> The library is JeroMQ and it is a JVM binding to 0MQ. This is THE protocol
> layer used in Jupyter between clients and kernels (Toree serves as a
> Jupyter kernel). Over the past months, we've worked with the JeroMQ
> community to help move along a license change to MPL v2 (
> https://github.com/zeromq/jeromq/issues/327). The progress showed huge
> promised at the start and we are down to 3 committers out of 31 who have
> not responded. The JeroMQ community is moving towards code remediation.
>
> In my opinion, this effort shows great inter-OS community cooperation and
> something that should be valued by Apache. Why rewrite and maintain code
> that already exist? Why not allow the process to take place? Isn't that
> what the incubation period is for? Allow projects to resolve concerns
> before they graduate?
>
> So my question is, why one release? This has been our biggest impediment
in
> putting an official incubation release out. We are ready. We have all the
> disclaimer in place alerting the user that Toree contains LGPL code. The
> biggest concern is releasing and discovering a defect that we would not be
> able to fix due to the "One release constraint".
>
> Again... I just wish to start the discussion and find a resolution that
> will allow Toree to properly grow and move forward with its incubation.
>
> Thanks,
> Gino

Hi Gino,

What "one release constraint" are you referring to?

Thanks,

- Mike

Re: Notes on branding

[Mike Jumper]

On Fri, Jul 1, 2016 at 12:05 PM, Marvin Humphrey 
wrote:

> On Fri, Jul 1, 2016 at 9:35 AM, Greg Chase  wrote:
>
> > The branding guidelines do not address feedback such as "logo in footer"
> or
> > "disclaimer is buried deep or below the fold".
>
> Incubation disclaimers are intended to be substantive.  They are not CYA
> legal
> boilerplate that can be are buried in fine print. The intent is to
> communicate
> (effectively!) to consumers that a project is incubating. That way, people
> will know that certain caveats apply:
>
> Apache Foo is an effort undergoing incubation at The Apache Software
> Foundation (ASF), sponsored by the Apache Incubator.  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.
>
> What would be best is if podlings just understood that intent, and as and
> took
> it upon themselves to ensure that their incubating status was communicated
> effectively -- in websites, in release announcements, etc.
>
>
Can you cite, as an example, an incubating project's website where you
would consider the incubating status effectively communicated, and the
disclaimer not buried?

Re: Notes on branding

[Mike Jumper]

On Fri, Jul 1, 2016 at 12:47 PM, John D. Ament 
wrote:

> On Fri, Jul 1, 2016 at 3:19 PM Greg Chase  wrote:
>
> ...
> >
> > Spirits can be hard to grasp.  As I suggested before.  If being
> > prescriptive is too difficult, then force new podlings into a
> standardized
> > web template that meets requirements, and spirt.  This would actually
> > really simplify the getting started process for new podlings.  Then they
> > can either do something new with their website once they become a TLP, or
> > perhaps at some mid-level of maturity.
> >
> >
> This is where I begin to disagree.  We don't want podlings to just use
> cookie cutter websites, at least I don't believe we do.  I know I just want
> to see podlings use our guidelines as a bare minimum set of requirements
> for all of their branding.  This includes websites, docs, and releases.
> The point of the disclaimer is that there may be licensing issues within
> the release contents and as a result may not be 100% Apache License
> compliant.
>
>
There must be some middle ground between the extremes.

Cookie-cutter websites would be horrible, but there must be something
non-spiritual that podlings can reliably adhere to. If the documentation
states that podlings must do X, but they are actively frowned upon unless
they do X+1, we're heading into "pieces of flair" territory [1].

[1] https://vimeo.com/102830089

Re: Notes on branding

[Mike Jumper]

On Fri, Jul 1, 2016 at 3:44 PM, Gunnar Tapper 
wrote:

> Let me offer up a concrete example since I struggle with the issue of
> branding: http://trafodion.apache.org/documentation.html
>
> I chose the following approach based on input from out mentor Stack:
>
> - Added (incubator) to the menu bar
> - Added the incubator logo on the top of the page
> - Placed the disclaimer on the bottom of the page
>
> I did you placeholders in the documentation for things like mailing list,
> project names, and cross-documentation links to make renaming a matter of
> updating pom.xml files and rebuilding.
>
> However, I did NOT put incubator disclaimers or even an incubator status in
> the documentation simply because it felt like over communication of
> incubator status. As you'll see, the Apache license language is included in
> PDF and web-book formats but not the incubator disclaimer. I don't know
> whether I made the right choice. If I didn't, then I'd think that the
> guidance should state that web pages and documentation should include BOTH
> the ASL text and the incubator-disclaimer text.
>
> I hope this helps with the discussion.
>
> Thanks,
>
> Gunnar
>
> On Fri, Jul 1, 2016 at 1:31 PM, Mike Jumper 
> wrote:
>
> > On Fri, Jul 1, 2016 at 12:05 PM, Marvin Humphrey  >
> > wrote:
> >
> > > On Fri, Jul 1, 2016 at 9:35 AM, Greg Chase  wrote:
> > >
> > > > The branding guidelines do not address feedback such as "logo in
> > footer"
> > > or
> > > > "disclaimer is buried deep or below the fold".
> > >
> > > Incubation disclaimers are intended to be substantive.  They are not
> CYA
> > > legal
> > > boilerplate that can be are buried in fine print. The intent is to
> > > communicate
> > > (effectively!) to consumers that a project is incubating. That way,
> > people
> > > will know that certain caveats apply:
> > >
> > > Apache Foo is an effort undergoing incubation at The Apache
> Software
> > > Foundation (ASF), sponsored by the Apache Incubator.  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.
> > >
> > > What would be best is if podlings just understood that intent, and as
> and
> > > took
> > > it upon themselves to ensure that their incubating status was
> > communicated
> > > effectively -- in websites, in release announcements, etc.
> > >
> > >
> > Can you cite, as an example, an incubating project's website where you
> > would consider the incubating status effectively communicated, and the
> > disclaimer not buried?
> >
>
>
>
> --
> Thanks,
>
> Gunnar
> *If you think you can you can, if you think you can't you're right.*
>

John and/or Roman, can you comment specifically on how the results of the
branding audit [1] should be interpreted by the podlings concerned, and
(please) provide some concrete examples of what podlings should and
shouldn't do with respect to the audit?

Where is the threshold between "Present, in footer, smaller font" and the
much more colorful "Buried in footer"? Are not footers generally expected
to be in a smaller font?

Given that it sounds like the footer is generally-accepted sensible place
for the disclaimer [2], and that the branding guidelines do not currently
strictly require the Incubator logo [3], I'm not sure what the audit is
trying to say at this point.

If the consensus is that the guidelines need to change, why is an audit
occurring before the actual establishment of said guidelines? If the
guidelines are not changing, why is an audit occurring which applies
undocumented criteria?

Thanks,

- Mike

[1] https://wiki.apache.org/incubator/BrandingAuditJune2016
[2]
https://lists.apache.org/thread.html/acf796a286ed8202185b2a3b3509389630f5c833982e7b857ce3ab12@%3Cgeneral.incubator.apache.org%3E
[3] http://incubator.apache.org/guides/branding.html#logos

Write access for Incubator wiki

[Mike Jumper]

Hello,

I'm looking to add the current podling report for Guacamole, but lack write
privileges. Can write access be granted for the user "MichaelJumper"?

Thanks,

- Mike

Re: Is it ok to put ASF header onto ALv2 compatibly licensed code?

[Mike Jumper]

On Tue, Aug 9, 2016 at 2:23 PM, Roman Shaposhnik  wrote:
>
> ...
>
> ===
> Licensed to the Apache Software Foundation (ASF) under one
> or more contributor license agreements.  See the NOTICE file
> distributed with this work for additional information
> regarding copyright ownership.
> ===
>
> There are two way I can see how to read this "Licensed to..." statement.
> The first one is, indeed, along the lines of an original author re-licensing
> code under a different license.

I don't think this can be read that way. The quoted portion refers
only to the software being licensed to the ASF, not the ASF
re-licensing the software under a different license. The relevant text
for that normally immediately follows the quoted portion:

"... The ASF licenses this file to you under the Apache License,
Version 2.0 (the 'License'); ..."

> Clearly, only original author(s) can make that statement.

Not necessarily. The original license may allow for third-parties to
sublicense the code, given restrictions.

> However, a different way to read it (tell me if I'm stretching here) is to
> interpret it as an overall project that is being "Licensed to..." with the
> file itself remaining under the original license.

I think that interpretation fails due to the explicit wording "under one
or more contributor license agreements."

The original license is not a CLA.

That said, whether the original license allows a third-party (the ASF)
to sublicense the covered code under yet another license (the Apache
License) depends completely on the original license itself.

- Mike

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

Re: [VOTE] Apache HAWQ (incubating) 2.0.0.0-incubating Release

[Mike Jumper]

On Tue, Aug 9, 2016 at 4:32 PM, Justin Mclean  wrote:
> Hi,
>
>> Why? It would be perfectly fine for PG project to include, lets say an MIT
>> source code.
>
> That would be compatible with our license. But what if they included GPL or 
> CDDL licensed software?
>
>> That's why I don't feel comfortable putting the overall PG  licensed header 
>> there on my own.
>
> Nor should you if the files are not licensed that way.
>
>> I think we're talking slightly past each other -- I told you I do KNOW that 
>> they
>> are licensed under the different ALv2 compatible license.
>
> The package as a whole is licensed that way. But you stated you didn’t not 
> know how that file is licensed it may be ALv2 or it may be something else. 
> Just as it has different copyright owner it also likely is under a different 
> license, whose terms are very likely to be APv2 compatible, but may not be.
>

I'd also like to point out, from the PostgreSQL license (emphasis added):

"... Permission to use, copy, modify, and distribute this software and
its documentation for any purpose, without fee, and without a written
agreement is hereby granted, **provided that the above copyright
notice and this paragraph and the following two paragraphs appear in
all copies**. ..."

Regardless of how uncomfortable it may be to modify that file and add
legal boilerplate, the project in question would be violating the
PostgreSQL license if it does not somehow include the copyright notice
and paragraphs along with the copied portions.

If it is absolutely known that the file is indeed under the PostgreSQL
license, I'd think the best thing would be to add it and thus comply.
If, on the other hand, the license of that file truly *isn't* known,
then its inclusion in any project is dangerous.

Perhaps the upstream project could be persuaded to add the appropriate
boilerplate themselves, and thus resolve this once and for all?

- Mike

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

Re: Is it ok to put ASF header onto ALv2 compatibly licensed code?

[Mike Jumper]

On Tue, Aug 9, 2016 at 4:46 PM, Roman Shaposhnik  wrote:
> On Tue, Aug 9, 2016 at 2:48 PM, Mike Jumper  wrote:
>> On Tue, Aug 9, 2016 at 2:23 PM, Roman Shaposhnik  wrote:
>>>
>>> ...
>>>
>>> ===
>>> Licensed to the Apache Software Foundation (ASF) under one
>>> or more contributor license agreements.  See the NOTICE file
>>> distributed with this work for additional information
>>> regarding copyright ownership.
>>> ===
>>>
>>> There are two way I can see how to read this "Licensed to..." statement.
>>> The first one is, indeed, along the lines of an original author re-licensing
>>> code under a different license.
>>
>> I don't think this can be read that way. The quoted portion refers
>> only to the software being licensed to the ASF, not the ASF
>> re-licensing the software under a different license. The relevant text
>> for that normally immediately follows the quoted portion:
>>
>> "... The ASF licenses this file to you under the Apache License,
>> Version 2.0 (the 'License'); ..."
>>
>>> Clearly, only original author(s) can make that statement.
>>
>> Not necessarily. The original license may allow for third-parties to
>> sublicense the code, given restrictions.
>
> To me, the most thorny question in this is around what I would call
> 'default rights'. IOW, is the only way to allow for third parties to
> sublicense is to clearly state it in the license text or does the reverse
> apply (third party can always sublicense unless explicitly prohibited
> by the license text)?
>

I believe the only default is the protection under copyright itself.
That is, rights may be granted by the copyright holder to others via a
copyright license (like the Apache License), but otherwise only the
copyright holder has any such rights.

> On top of which, the difference between re-licensing vs. sublicensing
> seems to be of interest here as well.
>

Re-licensing is re-releasing the work under a new, different license,
independent of whatever license it was available under before. "I am
giving you access to this work under these terms."

Sublicensing is releasing the work under another license, but within
the terms of the license that originally applied. "You are already
given access to this work under these terms. In addition, I am giving
you access to this work under THESE terms."

> Do you think that ALv2 header the way it is written implies re-licensing
> or sublicensing?
>

Sublicensing.

"2. Grant of Copyright License. Subject to the terms and conditions of
this License, each Contributor hereby grants to You a perpetual,
worldwide, non-exclusive, no-charge, royalty-free, irrevocable
copyright license to reproduce, prepare Derivative Works of, publicly
display, publicly perform, sublicense, and distribute the Work and
such Derivative Works in Source or Object form."

> To illustrate the difference lets take the most liberal license of all (MIT).
> There's nothing preventing sublicensing OR re-licensing in the text of the
> license itself, but at the same time the FAQ makes it pretty clear that one
> is allowed and the other one is not:
> http://www.tawesoft.co.uk/kb/article/mit-license-faq
>

Like the Apache License, the MIT license explicitly grants permission
to sublicense:

"... including without limitation the rights to use, copy, modify,
merge, publish, distribute, sublicense, and/or sell copies of the
Software ..."

I don't believe they need to explicitly specify that they do not grant
permission to re-license the software. If the right to re-license was
a default, any restrictions imposed by a copyright license would be
easily circumvented by re-licensing under a license without those
restrictions.

>
> Suppose I have a source file under MIT license and all I want to do is
> to add a bit of
> verbiage that, when distributed as part of the ASF project, the code
> is redistributed (NOT
> re-licensed) under the ALv2 (on top of originally being available
> under the MIT license).
>
> It seems like there's no ASF-sanctioned way for me to make that statement, 
> since
> ALv2 header will imply re-licensing.
>

The issue I had with the proposed wording was not that it implies
re-licensing (I believe it implies sublicensing), but rather that it
implies things that are false (unless the work was indeed licensed to
the ASF by the original authors under a CLA).

If it's not licensed under a CLA to the ASF, I'd think the file would
need to be licensed under the Apache license just like any other
non-ASF code:

http://www.apache.org/licenses/LICENSE-2.0#apply

In the case of MIT-licensed code, you would need to also maintain
their original notice and copyright, as required by the MIT license.

- Mike

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

Namespacing of subproject Docker images vs. Incubator policy

[Mike Jumper]

Hello all,

We, Apache Guacamole (incubating), would like to migrate our project's
Docker images to something beneath the ASF, but I am unsure how to
proceed, nor the form that this migration would best take.

We currently have two repositories which provide Docker images:
incubator-guacamole-client [1] and incubator-guacamole-server [2].
Prior to acceptance into the Apache Incubator, these repositories were
used to produce the "glyptodon/guacamole" [3] and "glyptodon/guacd"
[4] images respectively.

As there is already an "apache/*" organization defined at Docker Hub
(albeit a virtual desert) [5] and there was positive discussion
regarding including the images of incubating projects under that
organization [6], it seems that would be the logical and
straightforward choice ... but because one of those images ("guacd")
would not be namespaced by the project's own name, I'm unsure if this
is actually possible/allowed.

Ideally we would end up with a mapping like:

incubator-guacamole-client -> apache/guacamole
incubator-guacamole-server -> apache/guacd

Or, since we're incubating, perhaps:

incubator-guacamole-client -> apache/incubator-guacamole
incubator-guacamole-server -> apache/incubator-guacd

But again, I'm not sure if "apache/incubator-guacd" would be a
violation of policy.

Alternatively, a cleaner approach could be to define a Docker Hub
organization specific to the project, as that would provide a nice
analogy to the project/subproject relationship that exists between
Apache Guacamole the "guacamole" and "guacd" applications:

incubator-guacamole-client -> guacamole/guacamole
incubator-guacamole-server -> guacamole/guacd

But I'm not sure if THAT would be a violation of policy. Further,
after creating exactly such an organization for the sake of testing,
I've found that I can't set up the necessary linkage for enabling
automatic builds (the organization would need to be owned by a user
with sufficient access rights to the Apache GitHub mirrors).

Any suggestions?

Thanks,

- Mike

[1] https://github.com/apache/incubator-guacamole-client
[2] https://github.com/apache/incubator-guacamole-server
[3] https://hub.docker.com/r/glyptodon/guacamole/
[4] https://hub.docker.com/r/glyptodon/guacd/
[5] https://hub.docker.com/r/apache/
[6] 
http://mail-archives.apache.org/mod_mbox/incubator-general/201604.mbox/%3CCANyrgvfAWifLkkvAccAV22Q9uyo8g3so=BJ0JFZ8oV16Bt=k...@mail.gmail.com%3E

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

Re: Namespacing of subproject Docker images vs. Incubator policy

[Mike Jumper]

On Aug 28, 2016 5:58 PM, "Roman Shaposhnik"  wrote:
>
> First of all, the way apache org is setup on GitHub make me 99% sure
> that the only artifacts allowed there would be release ones.
>
> If we agree on that, I see no problem with
>apache/incubator-foo
> naming of your *released* Docker images.
>

I definitely have no problem with adopting a "incubator-" prefix in
principle.

That said, released Maven artifacts for incubating projects are normally
named without the "incubator-" prefix, instead requiring "-incubating" as a
suffix for the version of the artifact.

Would that convention make sense here as well, with the incubating status
being given via the Docker image tag?

ie:

apache/foo:0.1.0-incubating

rather than:

apache/incubator-foo:0.1.0

?

> Note that there was a separate discussion focused on where is the right
> place for nightly/snapshot Docker builds to be deposited to.
>
> Sadly, that discussion bore no fruit :-(
>

That is unfortunate. Perhaps this one will?

The Incubator's release management guide has recommendations for version
numbering of non-release artifacts:

http://incubator.apache.org/guides/releasemanagement.html#notes-numbering-between-releases

Given that, wouldn't some explicit snapshot naming for the image tag be
sufficient for non-release automated builds from git?

I'd even argue that Docker Hub's automated build system is a third party
hosted CI, and that images produced through that system are no more
inherently release-specific than the artifacts of a Jenkins build. Release
vs. non-release should be declared through image tags, not its presence on
Docker Hub alone.

- Mike

Re: Namespacing of subproject Docker images vs. Incubator policy

[Mike Jumper]

On Sun, Aug 28, 2016 at 6:49 PM, Mike Jumper  wrote:
> On Aug 28, 2016 5:58 PM, "Roman Shaposhnik"  wrote:
>>
>> First of all, the way apache org is setup on GitHub make me 99% sure
>> that the only artifacts allowed there would be release ones.
>>
>> If we agree on that, I see no problem with
>>apache/incubator-foo
>> naming of your *released* Docker images.
>>
>
> I definitely have no problem with adopting a "incubator-" prefix in
> principle.
>
> That said, released Maven artifacts for incubating projects are normally
> named without the "incubator-" prefix, instead requiring "-incubating" as a
> suffix for the version of the artifact.
>
> Would that convention make sense here as well, with the incubating status
> being given via the Docker image tag?
>
> ie:
>
> apache/foo:0.1.0-incubating
>
> rather than:
>
> apache/incubator-foo:0.1.0
>
> ?
>
>> Note that there was a separate discussion focused on where is the right
>> place for nightly/snapshot Docker builds to be deposited to.
>>
>> Sadly, that discussion bore no fruit :-(
>>
>
> That is unfortunate. Perhaps this one will?
>
> The Incubator's release management guide has recommendations for version
> numbering of non-release artifacts:
>
> http://incubator.apache.org/guides/releasemanagement.html#notes-numbering-between-releases
>
> Given that, wouldn't some explicit snapshot naming for the image tag be
> sufficient for non-release automated builds from git?
>
> I'd even argue that Docker Hub's automated build system is a third party
> hosted CI, and that images produced through that system are no more
> inherently release-specific than the artifacts of a Jenkins build. Release
> vs. non-release should be declared through image tags, not its presence on
> Docker Hub alone.
>
> - Mike

Scrounging around for precedent, and assuming that not all ASF
projects are under "apache/*" due to the relative lack of activity, I
have found at least:

https://hub.docker.com/r/cloudstack/cloudstack-cloudmonkey/

Which is a project-specific Docker Hub organization ("cloudstack") for
Apache Cloudstack which builds against the Apache GitHub mirror
(https://github.com/apache/cloudstack-cloudmonkey). The image has only
the "latest" tag, and after looking through the Dockerfile, it is
written to simply build itself against the latest git.

Setting up the linkage between the "cloudstack" organization and the
Apache GitHub mirror must have involved intervention from Infra.
Searching through JIRA, I've found that, too:

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

That isn't an incubating project, of course, and examples of practice
can't be assumed to be examples of *good* practice or of policy, but
it does seem that project-specific Docker Hub organizations for
projects under the ASF are at least possible and arguably beneficial.

What about doing similar with an incubating project?

Specifically:

1) Using a project-specific organization of which Infra is a member.
2) Not using the "incubator-" prefix for the organization or image
names, for compatibility's sake.
3) Using the "-incubating" suffix in the tags of images of releases
while the project is incubating.

Thanks,

- Mike

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

Re: Namespacing of subproject Docker images vs. Incubator policy

[Mike Jumper]

On Aug 29, 2016 8:30 AM, "Roman Shaposhnik"  wrote:
>
> ...
> >> Note that there was a separate discussion focused on where is the right
> >> place for nightly/snapshot Docker builds to be deposited to.
> >>
> >> Sadly, that discussion bore no fruit :-(
> >>
> >
> > Was there?  I would love to get discussing about that.  Not for an
> > incubating project but for a TLP.   I share concerns about "latest" but
> > also see benefit to developers being able to use a "LATEST" tagged
> > pre-release.
>
> There was:
https://mail-search.apache.org/members/private-arch/infrastructure/201608.mbox/%3CCA+DCeTG4=yrG8aoj=rvu8o71vjmeutndd5cyjkxialktxwt...@mail.gmail.com%3E
>
> FWIW, I say that we should just adopt a repository.apache.org approach
> and declare that nightly/snapshot Docker images can only be distributed
> from our own Docker repo. That way there's absolutely 0 chance anybody
> can get them by accident.
>

If the "latest" tag points only to releases, then that would take care of
this as well.

If only a specific "snapshot" tag ever points to snapshot images, then
getting them would require:

$ sudo docker pull foo:snapshot

Zero chance of a user typing that by accident as well.

- Mike

Re: Namespacing of subproject Docker images vs. Incubator policy

[Mike Jumper]

On Sun, Aug 28, 2016 at 9:28 PM, Mike Jumper  wrote:
>
> On Sun, Aug 28, 2016 at 6:49 PM, Mike Jumper  wrote:
> > On Aug 28, 2016 5:58 PM, "Roman Shaposhnik"  wrote:
> >>
> >> First of all, the way apache org is setup on GitHub make me 99% sure
> >> that the only artifacts allowed there would be release ones.
> >>
> >> If we agree on that, I see no problem with
> >>apache/incubator-foo
> >> naming of your *released* Docker images.
> >>
> >
> > I definitely have no problem with adopting a "incubator-" prefix in
> > principle.
> >
> > That said, released Maven artifacts for incubating projects are normally
> > named without the "incubator-" prefix, instead requiring "-incubating" as a
> > suffix for the version of the artifact.
> >
> > Would that convention make sense here as well, with the incubating status
> > being given via the Docker image tag?
> >
> > ie:
> >
> > apache/foo:0.1.0-incubating
> >
> > rather than:
> >
> > apache/incubator-foo:0.1.0
> >
> > ?
> >
> >> Note that there was a separate discussion focused on where is the right
> >> place for nightly/snapshot Docker builds to be deposited to.
> >>
> >> Sadly, that discussion bore no fruit :-(
> >>
> >
> > That is unfortunate. Perhaps this one will?
> >
> > The Incubator's release management guide has recommendations for version
> > numbering of non-release artifacts:
> >
> > http://incubator.apache.org/guides/releasemanagement.html#notes-numbering-between-releases
> >
> > Given that, wouldn't some explicit snapshot naming for the image tag be
> > sufficient for non-release automated builds from git?
> >
> > I'd even argue that Docker Hub's automated build system is a third party
> > hosted CI, and that images produced through that system are no more
> > inherently release-specific than the artifacts of a Jenkins build. Release
> > vs. non-release should be declared through image tags, not its presence on
> > Docker Hub alone.
> >
> > - Mike
>
> Scrounging around for precedent, and assuming that not all ASF
> projects are under "apache/*" due to the relative lack of activity, I
> have found at least:
>
> https://hub.docker.com/r/cloudstack/cloudstack-cloudmonkey/
>
> Which is a project-specific Docker Hub organization ("cloudstack") for
> Apache Cloudstack which builds against the Apache GitHub mirror
> (https://github.com/apache/cloudstack-cloudmonkey). The image has only
> the "latest" tag, and after looking through the Dockerfile, it is
> written to simply build itself against the latest git.
>
> Setting up the linkage between the "cloudstack" organization and the
> Apache GitHub mirror must have involved intervention from Infra.
> Searching through JIRA, I've found that, too:
>
> https://issues.apache.org/jira/browse/INFRA-9915
>
> That isn't an incubating project, of course, and examples of practice
> can't be assumed to be examples of *good* practice or of policy, but
> it does seem that project-specific Docker Hub organizations for
> projects under the ASF are at least possible and arguably beneficial.
>
> What about doing similar with an incubating project?
>
> Specifically:
>
> 1) Using a project-specific organization of which Infra is a member.
> 2) Not using the "incubator-" prefix for the organization or image
> names, for compatibility's sake.
> 3) Using the "-incubating" suffix in the tags of images of releases
> while the project is incubating.
>
> Thanks,
>
> - Mike

All, setting aside the Docker Hub vs. Apache-hosted hub vs. bintray
discussion for the moment, are there any specific opinions regarding
the original issue: the actual namespacing of the podling images
themselves?

It seems we, Apache Guacamole (incubating), have three possible
choices for the images related to a release. Again, we have two
specific applications within the Guacamole project as a whole which
have their own images: "guacamole", the web application, and "guacd",
the backend daemon with which it communicates.

(A)

apache/incubator-guacamole:0.9.10-incubating
apache/incubator-guacd:0.9.10-incubating

- Seems redundant (incubator, incubating), graduation would break
compatibility (see Maven best practices [1])
- "Apache Guacd" is not an incubating project, thus perhaps
apache/incubator-guacd is problematic

(B)

apache/guacamole:0.9.10-incubating
apache/guacd:0.9.10-incubating

- Le

Re: Namespacing of subproject Docker images vs. Incubator policy

[Mike Jumper]

On Sep 6, 2016 5:38 PM, "Marvin Humphrey"  wrote:
>
> ...
>
> Or, matching up with our (post-graduation) Git repo naming
> convention again:
>
> apache/guacamole
> apache/guacamole-guacd
>
> apache/guacamole:0.9.10-incubating
> apache/guacamole-guacd:0.9.10-incubating
>
> I think this is best.  However, it bugs me that users are not provided
with
> adequate disclaimers for the common case that fetches `latest` as the
default
> tag:
>
> docker pull apache/guacamole
>

A necessary evil, perhaps. Even with Maven (at least older versions of
Maven), omitting the version while keeping only the groupId and artifactId
were legal coordinates.

Is the project-specific organization option not really an option at all
then? Frowned upon for a TLP, and not to be considered by a podling?

Thanks,

- Mike

Re: Namespacing of subproject Docker images vs. Incubator policy

[Mike Jumper]

On Wed, Sep 7, 2016 at 6:31 PM, Marvin Humphrey  wrote:
> On Wed, Sep 7, 2016 at 9:44 AM, Mike Jumper  wrote:
>
>> Is the project-specific organization option not really an option at all
>> then? Frowned upon for a TLP, and not to be considered by a podling?
>
> My chief concern so far has been assuring that our nascent Infra-supported
> offerings do not conflict with policy.  Now that this has been achieved (in
> planning, if not yet in implementation), it's easier to speak to your issue.
>
> The main Docker Hub at hub.docker.com is a public-facing downstream
> distribution channel -- similar to Maven Central, PyPI, Debian package
> management, etc.
>
> It is appropriate to distribute official releases through downstream channels,
> but inappropriate to distribute unreleased materials through them.  (That's
> why having `latest` on hub.docker.com point to git `master` is problematic.)
> See Apache's formal Release Policy and Release Distribution Policy documents:
>
> http://www.apache.org/legal/release-policy#policy
> http://www.apache.org/dev/release-distribution#policy
>
> 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.  Instead, we
> primarily rely on people respecting our trademarks: that "Apache Foo", when
> obtained from one of these channels, is what the consumer expects.
>
> http://www.apache.org/foundation/marks
>
> One implication is that if you're using the project name for that Docker
> Hub account, we'd expect the entire PMC to have access.
>
> Incubating podlings operate under additional constraints, in that the "Apache"
> brand needs to be tempered with "incubating" and appropriate disclaimers.
>
> http://incubator.apache.org/guides/branding.html
>
> But within those guidelines, the answer is: yes, go ahead.  If Infra's
> offering is not to your taste, that is.
>
> Marvin Humphrey
>

Excellent. Thanks, Marvin.

This addresses absolutely all my questions quite nicely.

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

Re: Incubator chat on Hipchat?

[Mike Jumper]

On Nov 3, 2016 00:02, "Jean-Baptiste Onofré"  wrote:
>
> Hi John,
>
> it sounds like a good idea. I would allow "direct" communication between
the podling guys and the mentors/shepherd (to discuss release or report
content).
>

Wouldn't release/content discussion be best conducted on the mailing lists?

Thanks,

- Mike

[VOTE] Release Apache Guacamole 0.9.10-incubating (RC2)

[Mike Jumper]

Hello Incubator PMC,

The Apache Guacamole community has voted on and approved a proposal to
release Apache Guacamole 0.9.10-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/201612.mbox/%3CCALKeL-OuVfmNX-8mDbRVtvN5C6kz-n8N_%3D9bHsn5OR3hdDKAmQ%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.10-incubating/

The git tag for all relevant repositories is "0.9.10-incubating-RC2":

https://github.com/apache/incubator-guacamole-client/tree/0.9.10-incubating-RC2
https://github.com/apache/incubator-guacamole-server/tree/0.9.10-incubating-RC2
https://github.com/apache/incubator-guacamole-manual/tree/0.9.10-incubating-RC2

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.10-incubating/gug/installing-guacamole.html

Maven artifacts for guacamole-common, guacamole-common-js, and
guacamole-ext can be found in the following staging repository:

https://repository.apache.org/content/repositories/orgapacheguacamole-1003/

Source and binary distributions (also linked within the release notes):

https://dist.apache.org/repos/dist/dev/incubator/guacamole/0.9.10-incubating-RC2/

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

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

Re: [VOTE] Release Apache Guacamole 0.9.10-incubating (RC2)

[Mike Jumper]

On Tue, Dec 13, 2016 at 12:11 AM, Justin Mclean
 wrote:
> Hi,
>
> Can you clarify which of the release artefact are source releases.
>

Hi Justin,

The source artifacts are guacamole-client-0.9.10-incubating.tar.gz and
guacamole-server-0.9.10-incubating.tar.gz. The other artifacts are
convenience binaries which are built from guacamole-client.

> It might be a good idea to add “-src” or “-bin” to the artefact names to make 
> this clearer.
>

In the context of the project website, I believe there is already a
clear distinction between source and binary artifacts:

http://guacamole.incubator.apache.org/releases/0.9.10-incubating/

Do you think the artifacts need renaming as well? Would organizing the
artifacts into separate "source/" and "binary/" directories suffice?

Thanks,

- Mike

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

Re: [VOTE] Release Apache Guacamole 0.9.10-incubating (RC2)

[Mike Jumper]

On Tue, Dec 13, 2016 at 12:40 AM, Justin Mclean
 wrote:
>
>> Would organizing the artifacts into separate "source/" and "binary/" 
>> directories suffice?
>
> That seems like an excellent solution.
>

Excellent. Will do.

Am I correct in assuming that this is not a difficulty which blocks
further review of the release?

Thanks,

- Mike

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

Re: [VOTE] Release Apache Guacamole 0.9.10-incubating (RC2)

[Mike Jumper]

On Tue, Dec 13, 2016 at 5:07 PM, John D. Ament  wrote:
> On Tue, Dec 13, 2016 at 6:05 PM Mike Jumper 
> wrote:
>
>> On Tue, Dec 13, 2016 at 12:40 AM, Justin Mclean
>>  wrote:
>> >
>> >> Would organizing the artifacts into separate "source/" and "binary/"
>> directories suffice?
>> >
>> > That seems like an excellent solution.
>> >
>>
>> Excellent. Will do.
>>
>> Am I correct in assuming that this is not a difficulty which blocks
>> further review of the release?
>>
>
> Another way to look at it - given peoples availability, is there something
> that can be done to make the review of the release easier?
>

I definitely have no problem with making things easier, but updating
the directory hierarchy of the release artifacts will temporarily
break the links in the draft release notes until they, too, are
updated.

If that won't derail the review effort already underway, I'll gladly
take care of this.

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

Re: [VOTE] Release Apache Guacamole 0.9.10-incubating (RC2)

[Mike Jumper]

On Tue, Dec 13, 2016 at 3:24 PM, Mike Jumper  wrote:
> On Tue, Dec 13, 2016 at 5:07 PM, John D. Ament  wrote:
>> On Tue, Dec 13, 2016 at 6:05 PM Mike Jumper 
>> wrote:
>>
>>> On Tue, Dec 13, 2016 at 12:40 AM, Justin Mclean
>>>  wrote:
>>> >
>>> >> Would organizing the artifacts into separate "source/" and "binary/"
>>> directories suffice?
>>> >
>>> > That seems like an excellent solution.
>>> >
>>>
>>> Excellent. Will do.
>>>
>>> Am I correct in assuming that this is not a difficulty which blocks
>>> further review of the release?
>>>
>>
>> Another way to look at it - given peoples availability, is there something
>> that can be done to make the review of the release easier?
>>
>
> I definitely have no problem with making things easier, but updating
> the directory hierarchy of the release artifacts will temporarily
> break the links in the draft release notes until they, too, are
> updated.
>
> If that won't derail the review effort already underway, I'll gladly
> take care of this.

OK - the directory hierarchy has been updated, and the links within
the release notes have been updated as well.

Source artifacts:

https://dist.apache.org/repos/dist/dev/incubator/guacamole/0.9.10-incubating-RC2/source/

Convenience binaries (built from guacamole-client only):

https://dist.apache.org/repos/dist/dev/incubator/guacamole/0.9.10-incubating-RC2/binary/

There are no convenience binaries for guacamole-server.

Hope this helps.

Thanks,

- Mike

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

Re: [VOTE] Release Apache Guacamole 0.9.10-incubating (RC2)

[Mike Jumper]

On Sat, Dec 17, 2016 at 8:14 PM, Justin Mclean 
wrote:

> Hi,
>
> Sorry but it’s -1 binding as the server artefact is missing a DISCLAIMER
> and NOTICE file.
>
>
Fair enough. Looks like we need to update EXTRA_DIST in the top-level
Makefile.am.

Also some files (for instance [1][2]]) contain the text of the GPL license.
> GPL is Category X and is not allowed as a dependancy (unless it’s an
> optional component or build tools like autoconf in the sever artefact). I
> think this may be is OK as the software in question is dual license but if
> that is the case you should just include the text of the license you wish
> it to be licensed under no the text of both licenses. Can you please fix
> this in the next release.
>
>
Yes ... assuming we can legally strip out the GPL option of that license
without violating said license. I'm wary of modifying/removing license
terms of third-party software.

Do you know for sure that this is OK?

For the source artefacts I checked:
> - artefacts name includes incubating
> - hashes and signatures good
> - server source is missing DISCLAIMER
> - client and server LICENSE file good
> - server artefact is missing NOTICE file
> - No unexpected binary files in source release
> - All source files have ASF headers
> - Can compile client application
> - Unable to compile server application
>
> The convenience binary file LICENSE, NOTICE, DISCLAIMERS look good.
>
> When configuring the server I get this error:
> configure: error: "libpng is required for writing png messages"
>
> But I do have libpng installed:
> brew install libpng
> Warning: libpng-1.6.26 already installed
>
> Is OSX a supported platform?


We don't *not* support it ... but I don't have experience building on OSX
myself. It stands to reason that it should build, assuming the headers,
etc. can be found by configure.

It would be nice if the README had a bit more information on how to compile
> and what the dependancies are.


The README could certainly use some updating. The manual does:

http://guacamole.incubator.apache.org/doc/0.9.10-incubating/gug/installing-guacamole.html#required-dependencies


> For instance I think the instruction "Before compiling, you need to have
> compiled and installed libguac, the core Guacamole library” may possibly be
> misleading?
>

Yes, that's definitely out-of-date. The libguac portion used to be a
separate project.

So ... based on the above, the following specific issues were identified:

1) DISCLAIMER and NOTICE are missing from
guacamole-server-0.9.10-incubating.tar.gz
2) The guacamole-server README needs to be updated to match the current
build
3) The CDDL+GPL license text of bundled dependencies needs to be stripped
of GPL text (assuming this is legal)

Is the issue with DISCLAIMER and NOTICE the only issue you've found which
blocks this release?

Thanks,

- Mike

Re: [VOTE] Release Apache Guacamole 0.9.10-incubating (RC2)

[Mike Jumper]

On Sat, Dec 17, 2016 at 11:20 PM, Justin Mclean
 wrote:
> ...
>
>> Is the issue with DISCLAIMER and NOTICE the only issue you've found which
>> blocks this release?
>
> Yep they would be the only things I consider blockers.
>

OK. Sounds good then.

Thanks for taking the time to review, Justin. I'll cancel the vote and
start working toward another RC.

- Mike

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

[CANCEL] [VOTE] Release Apache Guacamole 0.9.10-incubating (RC2)

[Mike Jumper]

On Sat, Dec 17, 2016 at 8:14 PM, Justin Mclean  wrote:
> Hi,
>
> Sorry but it’s -1 binding as the server artefact is missing a DISCLAIMER and 
> NOTICE file.
>

Due to the issue noted above, this VOTE is canceled. We'll work to
address this in the next RC.

Thanks,

- Mike

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

Re: Fwd: Undelivered Mail Returned to Sender

[Mike Jumper]

I opened an issue in JIRA with Infra for this recently:

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

My understanding so far is:

1) Some things were changed to work around emails being flagged as spam.
2) Those changes broke sending of automatic SVN emails.
3) Repairs partly fixed the issue yesterday, but resulted in such emails
having "PROJECT.apache.org" rather than "PROJECT.incubator.apache.org" in
the "To" field email address.

Judging from your email, the date of which is after when things seemed
partly fixed, it looks like things have been re-broken.

- Mike


On Dec 20, 2016 06:46, "James Bognar"  wrote:

> Anybody have any idea why I'm seeing these bounced messages?  Is something
> misconfigured?
>
> It appears to be an automated message caused by an svn commit command.
>
>
> -- Forwarded message --
> From: Mail Delivery System 
> Date: Mon, Dec 19, 2016 at 7:48 PM
> Subject: Undelivered Mail Returned to Sender
> To: jamesbog...@apache.org
>
>
> This is the mail system at host svn01-us-west.apache.org.
>
> I'm sorry to have to inform you that your message could not
> be delivered to one or more recipients. It's attached below.
>
> For further assistance, please send mail to postmaster.
>
> If you do so, please include this problem report. You can
> delete your own text from the attached returned message.
>
>The mail system
>
> : host hermes.apache.org[140.211.11.
> 3]
> said: 550 relaying denied (in reply to RCPT TO command)
>
> Final-Recipient: rfc822; comm...@juneau.incubator.apache.org
> Original-Recipient: rfc822;comm...@juneau.incubator.apache.org
> Action: failed
> Status: 5.0.0
> Remote-MTA: dns; hermes.apache.org
> Diagnostic-Code: smtp; 550 relaying denied
>
>
> -- Forwarded message --
> From: jamesbog...@apache.org
> To: comm...@juneau.incubator.apache.org
> Cc:
> Date: Tue, 20 Dec 2016 00:48:39 -
> Subject: svn commit: r17492 - in /dev/incubator/juneau:
> binaries/juneau-6.0.1-incubating-RC2/ binaries/juneau-6.0.1-
> incubating-RC3/
> source/juneau-6.0.1-incubating-RC2/ source/juneau-6.0.1-incubating-RC3/
> Author: jamesbognar
> Date: Mon Dec 19 20:06:05 2016
> New Revision: 17492
>
> Log:
> juneau-6.0.1-incubating-RC3
>
> Added:
> dev/incubator/juneau/binaries/juneau-6.0.1-incubating-RC3/
> dev/incubator/juneau/binaries/juneau-6.0.1-incubating-RC3/
> apache-juneau-6.0.1-incubating-bin.zip   (with props)
> dev/incubator/juneau/binaries/juneau-6.0.1-incubating-RC3/
> apache-juneau-6.0.1-incubating-bin.zip.asc
> dev/incubator/juneau/binaries/juneau-6.0.1-incubating-RC3/
> apache-juneau-6.0.1-incubating-bin.zip.md5
> dev/incubator/juneau/binaries/juneau-6.0.1-incubating-RC3/
> apache-juneau-6.0.1-incubating-bin.zip.sha1
> dev/incubator/juneau/source/juneau-6.0.1-incubating-RC3/
> dev/incubator/juneau/source/juneau-6.0.1-incubating-RC3/
> apache-juneau-6.0.1-incubating-src.zip   (with props)
> dev/incubator/juneau/source/juneau-6.0.1-incubating-RC3/
> apache-juneau-6.0.1-incubating-src.zip.asc
> dev/incubator/juneau/source/juneau-6.0.1-incubating-RC3/
> apache-juneau-6.0.1-incubating-src.zip.md5
> dev/incubator/juneau/source/juneau-6.0.1-incubating-RC3/
> apache-juneau-6.0.1-incubating-src.zip.sha1
> Removed:
> dev/incubator/juneau/binaries/juneau-6.0.1-incubating-RC2/
> dev/incubator/juneau/source/juneau-6.0.1-incubating-RC2/
>
> 
>
>
>
>
> --
> James Bognar
>

[VOTE] Release Apache Guacamole 0.9.10-incubating (RC3)

[Mike Jumper]

Hello Incubator PMC,

The Apache Guacamole community has voted on and approved a proposal to
release Apache Guacamole 0.9.10-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/201612.mbox/%3CCALKeL-P-nSVEO92Zbo3c%3D-obhD-sk8t_b26kMVFxc8eixqbt1Q%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.10-incubating/

The git tag for all relevant repositories is "0.9.10-incubating-RC3":

https://github.com/apache/incubator-guacamole-client/tree/0.9.10-incubating-RC3
https://github.com/apache/incubator-guacamole-server/tree/0.9.10-incubating-RC3
https://github.com/apache/incubator-guacamole-manual/tree/0.9.10-incubating-RC3

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.10-incubating/gug/installing-guacamole.html

Maven artifacts for guacamole-common, guacamole-common-js, and
guacamole-ext can be found in the following staging repository:

https://repository.apache.org/content/repositories/orgapacheguacamole-1004/

Source and binary distributions (also linked within the release notes):

https://dist.apache.org/repos/dist/dev/incubator/guacamole/0.9.10-incubating-RC3/

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.

Ho ho ho,

- Mike

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

Re: [VOTE] Release Apache Guacamole 0.9.10-incubating (RC3)

[Mike Jumper]

On Wed, Dec 21, 2016 at 4:38 PM, Mike Jumper  wrote:
> Hello Incubator PMC,
>
> The Apache Guacamole community has voted on and approved a proposal to
> release Apache Guacamole 0.9.10-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/201612.mbox/%3CCALKeL-P-nSVEO92Zbo3c%3D-obhD-sk8t_b26kMVFxc8eixqbt1Q%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.10-incubating/
>
> The git tag for all relevant repositories is "0.9.10-incubating-RC3":
>
> https://github.com/apache/incubator-guacamole-client/tree/0.9.10-incubating-RC3
> https://github.com/apache/incubator-guacamole-server/tree/0.9.10-incubating-RC3
> https://github.com/apache/incubator-guacamole-manual/tree/0.9.10-incubating-RC3
>
> 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.10-incubating/gug/installing-guacamole.html
>
> Maven artifacts for guacamole-common, guacamole-common-js, and
> guacamole-ext can be found in the following staging repository:
>
> https://repository.apache.org/content/repositories/orgapacheguacamole-1004/
>
> Source and binary distributions (also linked within the release notes):
>
> https://dist.apache.org/repos/dist/dev/incubator/guacamole/0.9.10-incubating-RC3/
>
> 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.
>
> Ho ho ho,
>
> - Mike

For reference, the following changes were made since the last RC:

* DISCLAIMER and NOTICE added to guacamole-server source .tar.gz [1]
* Category X licenses removed for dual-licensed dependencies [2]
* guacamole-server README updated with respect to current build and
dependencies [3] (though the manual is still the ultimate reference
[4])

[1] https://issues.apache.org/jira/browse/GUACAMOLE-143
[2] https://issues.apache.org/jira/browse/GUACAMOLE-144
[3] https://issues.apache.org/jira/browse/GUACAMOLE-145
[4] 
http://guacamole.incubator.apache.org/doc/0.9.10-incubating/gug/installing-guacamole.html#building-guacamole-server

- Mike

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

[RESULT] [VOTE] Release Apache Guacamole 0.9.10-incubating (RC3)

[Mike Jumper]

On Wed, Dec 21, 2016 at 4:38 PM, Mike Jumper  wrote:
> Hello Incubator PMC,
>
> The Apache Guacamole community has voted on and approved a proposal to
> release Apache Guacamole 0.9.10-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/201612.mbox/%3CCALKeL-P-nSVEO92Zbo3c%3D-obhD-sk8t_b26kMVFxc8eixqbt1Q%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.10-incubating/
>
> The git tag for all relevant repositories is "0.9.10-incubating-RC3":
>
> https://github.com/apache/incubator-guacamole-client/tree/0.9.10-incubating-RC3
> https://github.com/apache/incubator-guacamole-server/tree/0.9.10-incubating-RC3
> https://github.com/apache/incubator-guacamole-manual/tree/0.9.10-incubating-RC3
>
> 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.10-incubating/gug/installing-guacamole.html
>
> Maven artifacts for guacamole-common, guacamole-common-js, and
> guacamole-ext can be found in the following staging repository:
>
> https://repository.apache.org/content/repositories/orgapacheguacamole-1004/
>
> Source and binary distributions (also linked within the release notes):
>
> https://dist.apache.org/repos/dist/dev/incubator/guacamole/0.9.10-incubating-RC3/
>
> 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.
>
> Ho ho ho,
>
> - Mike

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

+1 Jean-Baptiste Onofré
+1 Jim Jagielski
+1 Justin Mclean

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

[ANNOUNCE] Apache Guacamole 0.9.10-incubating released

[Mike Jumper]

The Apache Guacamole community is proud to announce the release of Apache
Guacamole 0.9.10-incubating.

Apache Guacamole (incubating) is a clientless remote desktop gateway which
supports standard protocols like VNC, RDP, and SSH. We call it "clientless"
because no plugins or client software are required; once Guacamole is
installed on a server, all you need to access your desktops is a web
browser.

0.9.10-incubating is our first release under the Apache Incubator. It
features support for both screen sharing and recording, improved file
transfer behavior, and support for LDAP within the Docker images. Local
clipboard integration has also been added (for those browsers which support
it), as well as audio input for RDP, theming/branding via extensions, and
several other improvements.

A full list of the changes in this release, along with links to downloads
and updated documentation, can be found in the release notes:

http://guacamole.incubator.apache.org/releases/0.9.10-incubating/

For more information on Apache Guacamole, please see:

http://guacamole.incubator.apache.org/

Thanks!

The Apache Guacamole (incubating) Community



DISCLAIMER:

Apache Guacamole is an effort undergoing Incubation at The Apache Software
Foundation (ASF), sponsored by the Incubator. 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.

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

[Mike Jumper]

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

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

[Mike Jumper]

On Jan 26, 2017 19:22, "Justin Mclean"  wrote:

...
- client LICENSE is missing license for this file [1] (mostly likely BSD
but not 100% sure). Server LICENSE is fine. Can you fix this in the next
release.


Sure thing: https://issues.apache.org/jira/browse/GUACAMOLE-186

Thanks,

- Mike

Re: Incubator PMC February 2017 Board Report Timeline

[Mike Jumper]

On Mon, Jan 30, 2017 at 7:23 PM, John D. Ament  wrote:
> February 2017 Incubator report timeline:
>
> https://wiki.apache.org/incubator/February2017
>
> Wed February 01 -- Podling reports due by end of day
> Sun February 05 -- Shepherd reviews due by end of day
> Sun February 05 -- Summary due by end of day
> Tue February 07 -- Mentor signoff due by end of day
> Wed February 08 -- Report submitted to Board
> Wed February 15 -- Board meeting

Hi John,

Did things get rescheduled recently?

The automated reminders I received give the podling report due date
and board meeting one week later than above:

"The board meeting is scheduled for Wed, 22 February 2017, 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, February 08)."

Thanks,

- Mike

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

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

[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

[ANNOUNCE] Apache Guacamole 0.9.11-incubating released

[Mike Jumper]

The Apache Guacamole community is proud to announce the release of Apache
Guacamole 0.9.11-incubating.

Apache Guacamole (incubating) is a clientless remote desktop gateway which
supports standard protocols like VNC, RDP, and SSH. We call it "clientless"
because no plugins or client software are required; once Guacamole is
installed on a server, all you need to access your desktops is a web
browser.

0.9.11-incubating features support for two-factor authentication, password
policies, improvements to LDAP support, and support for arbitrary/custom
extensions within the Docker images. A full list of the changes in this
release, along with links to downloads and updated documentation, can be
found in the release notes:

http://guacamole.incubator.apache.org/releases/0.9.11-incubating/

For more information on Apache Guacamole, please see:

http://guacamole.incubator.apache.org/

Thanks!

The Apache Guacamole (incubating) Community



DISCLAIMER:

Apache Guacamole is an effort undergoing Incubation at The Apache Software
Foundation (ASF), sponsored by the Incubator. 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.

Re: Podling Graduation Rally

[Mike Jumper]

On Feb 19, 2017 8:01 PM, "Niclas Hedhman"  wrote:

...
CatA licenses are CatA because they allow modifications on source and
re-license...


sublicense*

- Mike

Re: Podling Graduation Rally

[Mike Jumper]

AFAIK, only the copyright holder can relicense a copyrighted work, whereas
others may sublicense under compatible terms so long as the original
license grants that permission (ie: the license of the original work is not
actually changing).

Is that not correct?

- Mike


On Feb 20, 2017 10:35 AM, "John D. Ament"  wrote:

Mike,

I'll point out that sublicense is probably not the right term.  While both
are Cat A, the BSD license is much less restrictive/offers less than the
Apache license.  Re-license is more accurate.  Its still compatible with
BSD, and removes any expectation that one is more/less than the other
license.

On Sun, Feb 19, 2017 at 11:19 PM Mike Jumper 
wrote:

> On Feb 19, 2017 8:01 PM, "Niclas Hedhman"  wrote:
>
> ...
> CatA licenses are CatA because they allow modifications on source and
> re-license...
>
>
> sublicense*
>
> - Mike
>

[VOTE] Release Apache Guacamole 0.9.12-incubating (RC1)

[Mike Jumper]

Hello Incubator PMC,

The Apache Guacamole community has voted on and approved a proposal to
release Apache Guacamole 0.9.12-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/201703.mbox/%3CCALKeL-Op5PO2nD%2Bw0SEU52L_
HZTD0DU4KtfwQo294fQ3ObCp%3DA%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.12-incubating/

The git tag for all relevant repositories is "0.9.12-incubating-RC1":

https://github.com/apache/incubator-guacamole-client/tree/0.
9.12-incubating-RC1
https://github.com/apache/incubator-guacamole-server/tree/0.
9.12-incubating-RC1
https://github.com/apache/incubator-guacamole-manual/tree/0.
9.12-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.12-incubating/
gug/installing-guacamole.html

Maven artifacts for guacamole-common-js and guacamole-ext can be found in
the following staging repository (guacamole-common is unchanged from the
previous release):

https://repository.apache.org/content/repositories/orgapacheguacamole-1006

Source and binary distributions (also linked within the release notes):

https://dist.apache.org/repos/dist/dev/incubator/guacamole/0
.9.12-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

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

[Mike Jumper]

On Wed, Mar 22, 2017 at 7:11 PM, John D. Ament 
wrote:

> Hi,
>
> So I'll be up front - I have mixed feelings about the download page.  I
> love the format, it works well.  I dislike that you're linking to
> unapproved releases, but it does have a decent warning sign.
>
>
The release notes / download page is only available through direct link
(it's not linked from anywhere on the site whatsoever).

What would be the preferred alternative? Not staging the release notes, and
linking to all artifacts directly within the vote email?


> Some items I'm noticing:
>
> - The included dockerfile should reference the guacamole community instead
> a single author for the maintainer
>

Fair enough. The single author is a holdover from the pre-Apache days. I'll
open an issue to address this.


> - There's a few files such as Makefile.in that have a mix of ASF and
> non-ASF headers, which isn't really appropriate.


Makefile.in is autogenerated. Non-ASF headers are present because they're
placed there by GNU Autotools. I don't think it's possible to configure
autotools to not include their headers in its output.

I also don't see the FSF
> claim in the License file.
>
>
Does the license of autotools need to be included in LICENSE? I do see
reference to autotools being approved for usage within the ASF, but not any
example to how the license of those tools should be cited in practice,
being not a bundled dependency per se.

https://www.apache.org/legal/resolved.html#build-tools

What would you recommend here?

Thanks,

- Mike

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

[Mike Jumper]

On Wed, Mar 22, 2017 at 8:34 PM, John D. Ament 
wrote:

> On Wed, Mar 22, 2017 at 7:55 PM Justin Mclean 
> wrote:
>
> > Hi,
> >
> > > Does the license of autotools need to be included in LICENSE?
> >
> > Good question. Other projects that use it don't add to license INAL but
> > given the exclusion states you’re allowed to distribute under your own
> > terms [2] I think that’s OK.
> >
> > > I do see reference to autotools being approved for usage within the ASF
> >
> > Correct see [1]
> >
> >
> Right - the main note is that a few files have a mixed ASF and FSF header
> which isn't right either.  But that might be limited to Makefile.in.
>
>
For reference, there are quire a few auto-generated files produced by the
GNU Autotools built-in "make dist" target that builds the source .tar.gz.
Though not necessarily pertinent to the release, we have those excluded
from git, so there's a list of what is autogenerated within .gitignore:

https://github.com/apache/incubator-guacamole-server/blob/cbca2f169b708a34dabc72a91a9a2dec653126fb/.gitignore#L22-L46

If something needs to be done to LICENSE, etc. to list GNU Autotools'
terms, please let us know, but I highly doubt we can control whether GNU
Autotools includes its own headers within generated files.

I believe it's possible to force autotools to exclude the ASF headers if we
replace the "#" with "dnl" in all relevant build files [1] ... but since
the generated files will contain portions of the source of the original
build files, I'm not sure stripping the ASF headers would be correct either.

Thanks,

- Mike

[1] http://stackoverflow.com/questions/3371239/autoconf-dnl-vs

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

[Mike Jumper]

On Wed, Mar 22, 2017 at 9:11 PM, Mike Jumper 
wrote:

> On Wed, Mar 22, 2017 at 8:34 PM, John D. Ament 
> wrote:
>
>> On Wed, Mar 22, 2017 at 7:55 PM Justin Mclean 
>> wrote:
>>
>> > Hi,
>> >
>> > > Does the license of autotools need to be included in LICENSE?
>> >
>> > Good question. Other projects that use it don't add to license INAL but
>> > given the exclusion states you’re allowed to distribute under your own
>> > terms [2] I think that’s OK.
>> >
>> > > I do see reference to autotools being approved for usage within the
>> ASF
>> >
>> > Correct see [1]
>> >
>> >
>> Right - the main note is that a few files have a mixed ASF and FSF header
>> which isn't right either.  But that might be limited to Makefile.in.
>>
>>
> For reference, there are quire a few auto-generated files produced by the
> GNU Autotools built-in "make dist" target that builds the source .tar.gz.
> Though not necessarily pertinent to the release, we have those excluded
> from git, so there's a list of what is autogenerated within .gitignore:
>
> https://github.com/apache/incubator-guacamole-server/blob/
> cbca2f169b708a34dabc72a91a9a2dec653126fb/.gitignore#L22-L46
>
> If something needs to be done to LICENSE, etc. to list GNU Autotools'
> terms, please let us know, but I highly doubt we can control whether GNU
> Autotools includes its own headers within generated files.
>
> I believe it's possible to force autotools to exclude the ASF headers if
> we replace the "#" with "dnl" in all relevant build files [1] ... but since
> the generated files will contain portions of the source of the original
> build files, I'm not sure stripping the ASF headers would be correct either.
>
>
Should it be determined that this is indeed necessary, I've just now
verified that the ASF headers can indeed be excluded from all autogenerated
build output if the leading "#" is replaced with "##" in configure.ac and
all Makefile.am, though I'm still not sure if that's proper due to the
output containing occasional verbatim bits of the original
non-autogenerated build file source (especially the Makefiles ultimately
produced from the Makefile.am's).

- Mike

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

[Mike Jumper]

On Fri, Mar 24, 2017 at 9:01 PM, John D. Ament 
wrote:

> So OK, I'm going to vote +1 on the release.  There's some questionable
> stuff about the autogenerated files, and I think we can handle as a follow
> up JIRA (run it by legal first, as I'm honestly curious).  I suspect the
> ruling would be that the ASF header is OK to leave there since the tooling
> itself generates that file including header, but best to get a true ruling.
>
>
Thanks, John. We definitely won't move forward with altering the presence
of the ASF headers until we get a ruling from legal one way or the other.
I'm equally worried that simply removing them would be just as wrong, due
to the way GNU Autotools pulls in chunks of build file source verbatim.

What about your other feedback regarding the draft release notes +
downloads?

- Mike

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

[Mike Jumper]

On Sat, Mar 25, 2017 at 6:25 AM, John D. Ament  wrote:
>
> On Sat, Mar 25, 2017 at 1:03 AM Mike Jumper 
> wrote:
> > ...
> > Thanks, John. We definitely won't move forward with altering the presence
> > of the ASF headers until we get a ruling from legal one way or the other.
> > I'm equally worried that simply removing them would be just as wrong, due
> > to the way GNU Autotools pulls in chunks of build file source verbatim.
> >
> > What about your other feedback regarding the draft release notes +
> > downloads?
> >
> >
> http://www.apache.org/dev/release-distribution.html#unreleased
>
> I feel you violate this, but since its unlinked I'm OK with sayings just
> there.  For the next release, prep the page, but don't publish it.
>

Can you clarify how this is violated?

With the release artifacts themselves uploaded to staging dist prior
to being promoted to release dist, Maven artifacts uploaded to a
staging repository prior to being promoted to the release repo, etc.,
I'm not seeing why uploading the release notes to a staging section of
the website would be a violation of policy.

Part of the idea behind staging the release notes in this way was to
ensure that promoting an RC to release involves only updating
metadata, with all tangible release-related work being strictly part
of each RC. If the release notes cannot be uploaded until the release
is going out, then that'll be a part of the system that doesn't get
exercised during the RC process.

- Mike

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

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

[Mike Jumper]

On Sat, Mar 25, 2017 at 11:10 AM, John D. Ament  wrote:
> On Sat, Mar 25, 2017 at 1:14 PM Mike Jumper 
> wrote:
>
>> On Sat, Mar 25, 2017 at 6:25 AM, John D. Ament 
>> wrote:
>> >
>> > On Sat, Mar 25, 2017 at 1:03 AM Mike Jumper 
>> > wrote:
>> > > ...
>> > > Thanks, John. We definitely won't move forward with altering the
>> presence
>> > > of the ASF headers until we get a ruling from legal one way or the
>> other.
>> > > I'm equally worried that simply removing them would be just as wrong,
>> due
>> > > to the way GNU Autotools pulls in chunks of build file source verbatim.
>> > >
>> > > What about your other feedback regarding the draft release notes +
>> > > downloads?
>> > >
>> > >
>> > http://www.apache.org/dev/release-distribution.html#unreleased
>> >
>> > I feel you violate this, but since its unlinked I'm OK with sayings just
>> > there.  For the next release, prep the page, but don't publish it.
>> >
>>
>> Can you clarify how this is violated?
>>
>> With the release artifacts themselves uploaded to staging dist prior
>> to being promoted to release dist, Maven artifacts uploaded to a
>> staging repository prior to being promoted to the release repo, etc.,
>> I'm not seeing why uploading the release notes to a staging section of
>> the website would be a violation of policy.
>>
>> Part of the idea behind staging the release notes in this way was to
>> ensure that promoting an RC to release involves only updating
>> metadata, with all tangible release-related work being strictly part
>> of each RC. If the release notes cannot be uploaded until the release
>> is going out, then that'll be a part of the system that doesn't get
>> exercised during the RC process.
>>
>>
> Just to be 100% clear, I'm talking about this page:
> http://guacamole.incubator.apache.org/releases/0.9.12-incubating/
>
> Here are the items this page violates (from my POV):
>
> - You're linking to dist.apache.org

Is providing links to dist.apache.org not a requirement of the release
process whilst those artifacts are available on dist.apache.org only?

Were there no release notes on the website containing said links,
wouldn't a link to dist.apache.org need to be present in the email
regarding the RC vote, which ultimately reaches the same audience?

If/when the RC is promoted to a release, those links no longer point to dist:

http://guacamole.incubator.apache.org/release-procedures-part4/#update-website

> - There's nothing stating that these files are only for the dev community
> (there is a note saying its not released yet)

If explicitly stating that the files are meant only for the dev
community is what needs to be done, then we'll gladly do that.

If it's necessary that the URL pattern of the staged notes needs to be
different from the URL pattern of actual releases, that can be done as
well.

> - Anyone who has this link can use the prebuilt software.
>

But that also goes for anyone with access to git, or anyone who visits
dist.apache.org, or anyone following the dev@ list ... correct?

> Effectively, everything listed on
> http://www.apache.org/dev/release-distribution.html#unreleased is violated.

I'm afraid I still don't see how. Quoting from the policy linked above:

"Unreleased materials, in original or derived form...
   * MUST NOT be distributed through www.apache.org/dist."

Unreleased materials are not present on www.apache.org/dist. Only the
absolute latest release is present (with older releases only on
archive.apache.org):

http://www.apache.org/dist/incubator/guacamole/

The unreleased materials for a particular RC are exposed only through
the dev area of dist.apache.org:

https://dist.apache.org/repos/dist/dev/incubator/guacamole/

"... * MUST NOT be distributed through channels which encourage use by
anyone outside the project development community."

The only distribution channel in use is the dev section of SVN
dist.apache.org, the project's dev@ email list, and an unlinked page
on the website reachable only through an email to that dev@ list.

"... * MUST NOT be advertised to anyone outside of the project
development community."

The link is sent out only to the dev@ list.

"... * MAY be distributed to consenting members of a development community."

Which would be the dev@ list, correct?

- Mike

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

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

[Mike Jumper]

On Wed, Mar 22, 2017 at 6:56 PM, Mike Jumper 
wrote:

> Hello Incubator PMC,
>
> The Apache Guacamole community has voted on and approved a proposal to
> release Apache Guacamole 0.9.12-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/201703.mbox/%3CCALKeL-Op5PO2nD%2Bw0SEU52L_HZTD0DU4KtfwQ
> o294fQ3ObCp%3DA%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.12-incubating/
>
> The git tag for all relevant repositories is "0.9.12-incubating-RC1":
>
> https://github.com/apache/incubator-guacamole-client/tree/0.
> 9.12-incubating-RC1
> https://github.com/apache/incubator-guacamole-server/tree/0.
> 9.12-incubating-RC1
> https://github.com/apache/incubator-guacamole-manual/tree/0.
> 9.12-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.12-incubating/
> gug/installing-guacamole.html
>
> Maven artifacts for guacamole-common-js and guacamole-ext can be found in
> the following staging repository (guacamole-common is unchanged from the
> previous release):
>
> https://repository.apache.org/content/repositories/orgapacheguacamole-1006
>
> Source and binary distributions (also linked within the release notes):
>
> https://dist.apache.org/repos/dist/dev/incubator/guacamole/0
> .9.12-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
>
>
Friendly bump.

Many thanks,

- Mike

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

[Mike Jumper]

On Thu, Mar 30, 2017 at 3:30 PM, Josh Elser  wrote:

> +1 (binding)
>
> * Could build the client, but I don't have a setup to build the server
> * DISCLAIMER in every artifact
> * Sufficient LICENSE & NOTICE files. Even in the WAR! Good job :)
> * Commits exist in SCM
> * Sigs/xsums OK
>
> In the future:
>
> * Your copyright in NOTICE files needs updating (2017)
>

OK.


> * Dockerfile Maintainer line should be the Apache Guacamole community
> (instead of your email). I assume this was just missed in the transition
>

Exactly.

This is fixed now on git, so should be fine for next release and onward. It
turns out that the "MAINTAINER" Dockerfile instruction is deprecated now,
anyway, so we simply removed it:

https://issues.apache.org/jira/browse/GUACAMOLE-251


> * Please include SHA1's from Git. The tag name could be modified easily.
>

OK.


> * guacamole-auth-header includes some copies of ALv2 and mentions in your
> LICENSE file. You only need to propagate the copyright notice here, not the
> license text (since you already have that once). Looks like this might be
> the case around the binary tarballs.
>
>
Are you referring to the copies of the ALv2 LICENSE for dependencies that
happen to have that license?

I'm rather partial to the consistency of always having a copy of the
upstream license within a systematically-named directory structure,
regardless of whether the text of that license is the same as the license
of the project bundling it.

- Mike

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

[Mike Jumper]

On Fri, Mar 31, 2017 at 9:00 AM, Josh Elser  wrote:

> Mike Jumper wrote:
>
>> * guacamole-auth-header includes some copies of ALv2 and mentions in your
>>> >  LICENSE file. You only need to propagate the copyright notice here,
>>> not the
>>> >  license text (since you already have that once). Looks like this
>>> might be
>>> >  the case around the binary tarballs.
>>> >
>>> >
>>>
>> Are you referring to the copies of the ALv2 LICENSE for dependencies that
>> happen to have that license?
>>
>> I'm rather partial to the consistency of always having a copy of the
>> upstream license within a systematically-named directory structure,
>> regardless of whether the text of that license is the same as the license
>> of the project bundling it.
>>
>
> Yup. I understand your reasoning for doing that and that's fine. I just
> wanted to point out that it was unnecessary (as you had already included a
> copy of it the license text).
>
>
Ah, OK then.

Thanks for the thorough review, Josh!

- Mike

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

[Mike Jumper]

On Wed, Mar 22, 2017 at 6:56 PM, Mike Jumper 
wrote:

> Hello Incubator PMC,
>
> The Apache Guacamole community has voted on and approved a proposal to
> release Apache Guacamole 0.9.12-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/201703.mbox/%3CCALKeL-Op5PO2nD%2Bw0SEU52L_HZTD0DU4Kt
> fwQo294fQ3ObCp%3DA%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.12-incubating/
>
> The git tag for all relevant repositories is "0.9.12-incubating-RC1":
>
> https://github.com/apache/incubator-guacamole-client/tree/0.
> 9.12-incubating-RC1
> https://github.com/apache/incubator-guacamole-server/tree/0.
> 9.12-incubating-RC1
> https://github.com/apache/incubator-guacamole-manual/tree/0.
> 9.12-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.12-incubating/
> gug/installing-guacamole.html
>
> Maven artifacts for guacamole-common-js and guacamole-ext can be found in
> the following staging repository (guacamole-common is unchanged from the
> previous release):
>
> https://repository.apache.org/content/repositories/orgapacheguacamole-1006
>
> Source and binary distributions (also linked within the release notes):
>
> https://dist.apache.org/repos/dist/dev/incubator/guacamole/0
> .9.12-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.12-incubating is now closed.
With a total of +3 binding votes and NO -1 votes, the VOTE passes. Overall
binding vote breakdown is as follows:

+1 John D. Ament
+1 Josh Elser
+1 Mark Struberg

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

- Mike

[ANNOUNCE] Apache Guacamole 0.9.12-incubating released

[Mike Jumper]

The Apache Guacamole community is proud to announce the release of Apache
Guacamole 0.9.12-incubating.

Apache Guacamole (incubating) is a clientless remote desktop gateway which
supports standard protocols like VNC, RDP, and SSH. We call it "clientless"
because no plugins or client software are required; once Guacamole is
installed on a server, all you need to access your desktops is a web
browser.

The 0.9.12-incubating release features auto-updating connection thumbnails
for tab icons, performance improvements, and fixes for issues with
printing, file transfer, and terminal emulation. New support for
authenticating users based on arbitrary HTTP headers has also been added,
allowing the authentication result of external systems sitting between the
user and Guacamole to be trusted (as long as those headers can be truly
guaranteed to come only from those trusted systems).

A full list of the changes in this release, along with links to downloads
and updated documentation, can be found in the release notes:

http://guacamole.incubator.apache.org/releases/0.9.12-incubating/

For more information on Apache Guacamole, please see:

http://guacamole.incubator.apache.org/

Thanks!

The Apache Guacamole (incubating) Community



DISCLAIMER:

Apache Guacamole is an effort undergoing Incubation at The Apache Software
Foundation (ASF), sponsored by the Incubator. 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.

Re: Help with Dependency Licensing

[Mike Jumper]

On Tue, Apr 11, 2017 at 9:16 AM, Niclas Hedhman  wrote:

> Please note that Cat X licenses are deemed to be incompatible with Apache
> License, insofar that they are viral in nature, and FSF has made a claim
> that dynamically linked languages, such as Java, forces the virality to the
> dependent project...


I think it's important not to conflate "Cat X" with "GPL".

There are numerous reasons a license might be Cat X, but not all such
licenses are due to the FSF, and not all such licenses are viral to the
extent that the licensing of the source of the linking project is
compromised.

Meaning, if you have an import statement linking your
> code to such dependency, there is legal uncertainty whether the entire
> project must be under the copyleft license in question. FSF certainly
> thinks so, and VP Legal has in the past concluded that we should have the
> same stance.
>

Even in the case of the GPL, my understanding is that the virality takes
hold upon linking (at build time), not upon referencing the API via an
import, include, etc. in the source.

- Mike

Re: Help with Dependency Licensing

[Mike Jumper]

On Apr 11, 2017 17:29, "Niclas Hedhman"  wrote:

On Wed, Apr 12, 2017 at 12:31 AM, Mike Jumper 
wrote:

>
> Even in the case of the GPL, my understanding is that the virality takes
> hold upon linking (at build time), not upon referencing the API via an
> import, include, etc. in the source.
>

Your understanding is, simply put, not aligned with the FSF, and the ASF
has decided to follow FSF's conclusion. In fact, a former Director at ASF
and lawyer, Larry Rosen, was trying to fight this stance, basically making
the claim that GPL is overreaching, and that ended with Larry being kicked
out (not only for this particular question).


http://www.gnu.org/licenses/lgpl-java.html"; emphasis="mine">
It has always been the FSF's position that *dynamically linking
applications to libraries creates a single work derived* from both the
library code and the application code


Sorry, but I don't see the disagreement between the above statement and "the
virality takes hold upon linking (at build time)". Doesn't this creation of
a derivative work, even in the FSF interpretation, occur at the time of
linking, and not at the time that the source is written?

A piece of uncompiled source code is not yet linked. Linking is part of the
build and/or runtime processes.

- Mike

Inclusion/exclusion of ASF headers from GNU Autotools output (Was: [VOTE] Release Apache Guacamole 0.9.12-incubating (RC1))

[Mike Jumper]

On Fri, Mar 24, 2017 at 10:03 PM, Mike Jumper  wrote:
> On Fri, Mar 24, 2017 at 9:01 PM, John D. Ament 
> wrote:
>>
>> So OK, I'm going to vote +1 on the release.  There's some questionable
>> stuff about the autogenerated files, and I think we can handle as a follow
>> up JIRA (run it by legal first, as I'm honestly curious).  I suspect the
>> ruling would be that the ASF header is OK to leave there since the tooling
>> itself generates that file including header, but best to get a true
>> ruling.
>>
>
> Thanks, John. We definitely won't move forward with altering the presence of
> the ASF headers until we get a ruling from legal one way or the other. I'm
> equally worried that simply removing them would be just as wrong, due to the
> way GNU Autotools pulls in chunks of build file source verbatim.
>

To all those curious, I've opened the following issue in Legal Discuss
regarding the above:

https://issues.apache.org/jira/browse/LEGAL-300

- Mike

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

[VOTE] Release Apache Guacamole 0.9.13-incubating (RC1)

[Mike Jumper]

Hello Incubator PMC,

The Apache Guacamole community has voted on and approved a proposal to
release Apache Guacamole 0.9.13-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/201707.mbox/%3CCALKeL-Oc-xjbeKr_RiLqp_m4_
7sYdF5ZoK9T4q%3DN%2B0J7q-Hk9g%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.13-incubating/

The git tag for all relevant repositories is "0.9.13-incubating-RC1":

https://github.com/apache/incubator-guacamole-client/
tree/0.9.13-incubating-RC1 (commit de12b683d746129ddc8b34425ed6e40b618c91d6)
https://github.com/apache/incubator-guacamole-server/
tree/0.9.13-incubating-RC1 (commit ca3563a38e6416a6cde7f208dc9827c512227888)
https://github.com/apache/incubator-guacamole-manual/
tree/0.9.13-incubating-RC1 (commit a1a4ee64dd00217905288ac1d902713b0298c03b)

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.13-incubating/gug/installing-
guacamole.html

Maven artifacts for guacamole-common, guacamole-common-js, and
guacamole-ext can be found in the following staging repository:

https://repository.apache.org/content/repositories/orgapacheguacamole-1007

Source and binary distributions (also linked within the release notes):

https://dist.apache.org/repos/dist/dev/incubator/guacamole/
0.9.13-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

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

[Mike Jumper]

On Mon, Jul 24, 2017 at 11:50 PM, Justin Mclean
 wrote:
> Hi,
>
> +1 binding
>
> I checked:
> - incubating in name
> - signatures and hashes correct
> - DISCLAIMER exists
> - server and client's LICENSE and NOTICE good (although Autoconf had me 
> concerned for a second there)
> - no unexpected binary files
> - all source files have ASF headers
>
> I didn't compile from source as it look like it requires some setup and OSX 
> doesn’t seem to be a supported platform?
>

I can't say I've tried building on OSX myself, but it's not
unsupported. The C portions of Guacamole are coded to be as POSIX-ly
compatible as possible. I think the main issues you might run into
there would be in getting the components of your toolchain of choice
to find the libraries and headers of Guacamole's dependencies.

If you make the attempt and encounter any specific error(s), I'm sure
we could help you figure out how to give the toolchain a prod in the
right direction over on the user@ list. If all that fails and it does
turn out to not build on OSX, that would be a bug.

Thanks,

- Mike

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

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

[Mike Jumper]

On Sun, Jul 23, 2017 at 10:32 PM, Mike Jumper 
wrote:

> Hello Incubator PMC,
>
> The Apache Guacamole community has voted on and approved a proposal to
> release Apache Guacamole 0.9.13-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/201707.mbox/%3CCALKeL-Oc-xjbeKr_RiLqp_m4_7sYdF5ZoK9T4q%
> 3DN%2B0J7q-Hk9g%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.13-incubating/
>
> The git tag for all relevant repositories is "0.9.13-incubating-RC1":
>
> https://github.com/apache/incubator-guacamole-client/tree/0.
> 9.13-incubating-RC1 (commit de12b683d746129ddc8b34425ed6e40b618c91d6)
> https://github.com/apache/incubator-guacamole-server/tree/0.
> 9.13-incubating-RC1 (commit ca3563a38e6416a6cde7f208dc9827c512227888)
> https://github.com/apache/incubator-guacamole-manual/tree/0.
> 9.13-incubating-RC1 (commit a1a4ee64dd00217905288ac1d902713b0298c03b)
>
> 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.13-incubating/
> gug/installing-guacamole.html
>
> Maven artifacts for guacamole-common, guacamole-common-js, and
> guacamole-ext can be found in the following staging repository:
>
> https://repository.apache.org/content/repositories/orgapacheguacamole-1007
>
> Source and binary distributions (also linked within the release notes):
>
> https://dist.apache.org/repos/dist/dev/incubator/guacamole/0
> .9.13-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
>
>
Friendly bump.

Many thanks,

- Mike

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

[Mike Jumper]

On Sun, Jul 23, 2017 at 10:32 PM, Mike Jumper 
wrote:

> Hello Incubator PMC,
>
> The Apache Guacamole community has voted on and approved a proposal to
> release Apache Guacamole 0.9.13-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/201707.mbox/%3CCALKeL-Oc-xjbeKr_RiLqp_m4_7sYdF5ZoK9T4q%
> 3DN%2B0J7q-Hk9g%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.13-incubating/
>
> The git tag for all relevant repositories is "0.9.13-incubating-RC1":
>
> https://github.com/apache/incubator-guacamole-client/tree/0.
> 9.13-incubating-RC1 (commit de12b683d746129ddc8b34425ed6e40b618c91d6)
> https://github.com/apache/incubator-guacamole-server/tree/0.
> 9.13-incubating-RC1 (commit ca3563a38e6416a6cde7f208dc9827c512227888)
> https://github.com/apache/incubator-guacamole-manual/tree/0.
> 9.13-incubating-RC1 (commit a1a4ee64dd00217905288ac1d902713b0298c03b)
>
> 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.13-incubating/
> gug/installing-guacamole.html
>
> Maven artifacts for guacamole-common, guacamole-common-js, and
> guacamole-ext can be found in the following staging repository:
>
> https://repository.apache.org/content/repositories/orgapacheguacamole-1007
>
> Source and binary distributions (also linked within the release notes):
>
> https://dist.apache.org/repos/dist/dev/incubator/guacamole/0
> .9.13-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.13-incubating is now closed.
With a total of +3 binding votes and NO -1 votes, the VOTE passes. Overall
binding vote breakdown is as follows:

+1 Jean-Baptiste Onofré
+1 Justin Mclean
+1 Olivier Lamy

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

- Mike

[ANNOUNCE] Apache Guacamole 0.9.13-incubating released

[Mike Jumper]

The Apache Guacamole community is proud to announce the release of Apache
Guacamole 0.9.13-incubating.

Apache Guacamole (incubating) is a clientless remote desktop gateway which
supports standard protocols like VNC, RDP, and SSH. We call it "clientless"
because no plugins or client software are required; once Guacamole is
installed on a server, all you need to access your desktops is a web
browser.

The 0.9.13-incubating release features new support for CAS single sign-on,
automatic failover to connections within the same connection group, and
fixes for issues in all supported protocols. The JavaScript API has also
been extended to provide for in-browser playback of screen recordings, and
the extension API now allows custom REST services to be defined.

A full list of the changes in this release, along with links to downloads
and updated documentation, can be found in the release notes:

http://guacamole.incubator.apache.org/releases/0.9.13-incubating/

For more information on Apache Guacamole, please see:

http://guacamole.incubator.apache.org/

Thanks!

The Apache Guacamole (incubating) Community



DISCLAIMER:

Apache Guacamole is an effort undergoing Incubation at The Apache Software
Foundation (ASF), sponsored by the Incubator. 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.

Re: Digests in releases

[Mike Jumper]

On Aug 31, 2017 11:21, "Julian Hyde"  wrote:

After downloading artifacts, there are 3 things to check: (1) the download
is successful; (2) the artifacts were indeed created by the named author;
and (3) the artifacts have not been tampered with.

A security expert would know to use the .md5 for (1), the .asc for (2), and
the .sha256 or .sha512 for (3).


If there is a danger that the artifacts may be tampered with, there is an
equivalent danger that the checksum files will be tampered with, as well.
Checksums alone cannot be relied upon to verify an artifact hasn't been
altered.

Only the signature allows verification of authorship and integrity ...
assuming users have secure access to the corresponding public keys, and
that those keys are linked into the web of trust.

- Mike

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

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 Tras

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

[DISCUSS] Resolution to graduate Apache Guacamole to TLP

[Mike Jumper]

Hello all,

The Guacamole PPMC has discussed [1] [2] and voted to graduate to TLP.
Prior to calling the IPMC vote, we would greatly appreciate review and
feedback on our proposed resolution, which can be found at the bottom
of this email.

For reference, the community graduation VOTE result can be found here:

https://lists.apache.org/thread.html/0de2c49ee556b0e024d25be6092d405ce8d1cccbb9df1823ba79713e@%3Cdev.guacamole.apache.org%3E

and our completed maturity evaluation can be found here:

http://guacamole.incubator.apache.org/maturity-evaluation/

Many 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

--

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

Re: [DISCUSS] Resolution to graduate Apache Guacamole to TLP

[Mike Jumper]

On Sat, Oct 28, 2017 at 6:37 AM, John D. Ament  wrote:
> Hi,
>
> For the proposed PMC, could you share what the corporate affiliations are?
>

To the best of my knowledge/research, the corporate affiliations are
as follows (with some members associated with multiple):

Capital One:
   Jim Jagielski

Coty, Inc.:
   Nick Couchman

Glyptodon, Inc.:
   James Muehlner
   Mike Jumper

OS3 Consulting LLC:
   Nick Couchman

Quenda:
   Daniel Gruno

Skytap:
   Frode Langelo

Talend:
   Jean-Baptiste Onofré

Planet Labs, Inc.:
   James Muehlner

Virginia Polytechnic Institute and State University:
   Carl Harris

Web Age Solutions:
   Greg Trasuk

Webtide LLC:
Olivier Lamy

I've reached out to the proposed PMC members for updates regarding
corporate affiliation, in case things have changed, but hopefully this
gives at least some perspective for the time being.

Thanks,

- Mike

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

Re: [DISCUSS] Resolution to graduate Apache Guacamole to TLP

[Mike Jumper]

On Sun, Oct 29, 2017 at 11:53 AM, Mike Jumper  wrote:
>
> On Sat, Oct 28, 2017 at 6:37 AM, John D. Ament  wrote:
> > Hi,
> >
> > For the proposed PMC, could you share what the corporate affiliations are?
> >
>
> To the best of my knowledge/research, the corporate affiliations are
> as follows (with some members associated with multiple):
>
> Capital One:
>Jim Jagielski
>
> Coty, Inc.:
>Nick Couchman
>
>     Glyptodon, Inc.:
>James Muehlner
>Mike Jumper
>
> OS3 Consulting LLC:
>Nick Couchman
>
> Quenda:
>Daniel Gruno
>
> Skytap:
>Frode Langelo
>
> Talend:
>Jean-Baptiste Onofré
>
> Planet Labs, Inc.:
>James Muehlner
>
> Virginia Polytechnic Institute and State University:
>Carl Harris
>
> Web Age Solutions:
>Greg Trasuk
>
> Webtide LLC:
> Olivier Lamy
>
> I've reached out to the proposed PMC members for updates regarding
> corporate affiliation, in case things have changed, but hopefully this
> gives at least some perspective for the time being.
>

Any further feedback/discussion?

Thanks,

- Mike

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

Re: [DISCUSS] Resolution to graduate Apache Guacamole to TLP

[Mike Jumper]

On Sat, Oct 28, 2017 at 12:11 AM, Mike Jumper  wrote:

> Hello all,
>
> The Guacamole PPMC has discussed [1] [2] and voted to graduate to TLP.
> Prior to calling the IPMC vote, we would greatly appreciate review and
> feedback on our proposed resolution, which can be found at the bottom
> of this email.
>
> For reference, the community graduation VOTE result can be found here:
>
> https://lists.apache.org/thread.html/0de2c49ee556b0e024d25be6092d40
> 5ce8d1cccbb9df1823ba79713e@%3Cdev.guacamole.apache.org%3E
>
> and our completed maturity evaluation can be found here:
>
> http://guacamole.incubator.apache.org/maturity-evaluation/
>
> Many 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
>
> --
>
> 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.
>

Olivier Lamy has advised that, as he resigned as a Guacamole mentor early
this year, he doesn't think he should be part of the initial PMC. The
initial PMC will thus be as follows:

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

It's been a decent while with no further feedback, so I expect we're good
to move forward. I'm going to go ahead and start the IPMC VOTE in another
thread. Many thanks to those who took the time to review the draft
resolution.

- Mike

[VOTE] Graduate Apache Guacamole as TLP

[Mike Jumper]

Hello Incubator PMC,

The Apache Guacamole community has discussed  [1] [2], voted on, and
approved a resolution to graduate to a top-level project. The draft
resolution has since been given to the IPMC for review and discussion [3],
and with no further feedback, we would now like to call a VOTE to graduate
and establish Apache Guacamole as a top-level project.

Apache Guacamole began incubation in February of 2016. Since entering the
Incubator, the podling has gone through four releases [4], added three
committers, and grown a healthy and active community on the mailing lists.
Our completed maturity evaluation can be found here:

http://guacamole.incubator.apache.org/maturity-evaluation/

and the community graduation VOTE result can be found here:

https://lists.apache.org/thread.html/0de2c49ee556b0e024d25be6092d40
5ce8d1cccbb9df1823ba79713e@%3Cdev.guacamole.apache.org%3E

The full text of the proposed resolution can be found below.

Please review and vote:

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

This vote will be open for at least 72 hours.

Thanks,

- Mike

[1] https://lists.apache.org/thread.html/0848dd53b6acc1a0edea2ed
a1f385294eeb041a88c3d1f6221fa1ef2@%3Cdev.guacamole.apache.org%3E
[2] https://lists.apache.org/thread.html/a5259173a8ef4a1d2bb7be2
d99d3cbc2ccf8856130ae6e3fe54e079e@%3Cdev.guacamole.apache.org%3E
[3] https://lists.apache.org/thread.html/da03d479209b6f7a254a301de9bcd4
07a6eaf65f632227e76395f32d@%3Cgeneral.incubator.apache.org%3E
[4] http://guacamole.incubator.apache.org/releases/

--

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

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.

[RESULT] [VOTE] Graduate Apache Guacamole as TLP

[Mike Jumper]

On Fri, Nov 10, 2017 at 11:51 AM, Mike Jumper  wrote:

> Hello Incubator PMC,
>
> The Apache Guacamole community has discussed  [1] [2], voted on, and
> approved a resolution to graduate to a top-level project. The draft
> resolution has since been given to the IPMC for review and discussion [3],
> and with no further feedback, we would now like to call a VOTE to graduate
> and establish Apache Guacamole as a top-level project.
>
> Apache Guacamole began incubation in February of 2016. Since entering the
> Incubator, the podling has gone through four releases [4], added three
> committers, and grown a healthy and active community on the mailing lists.
> Our completed maturity evaluation can be found here:
>
> http://guacamole.incubator.apache.org/maturity-evaluation/
>
> and the community graduation VOTE result can be found here:
>
> https://lists.apache.org/thread.html/0de2c49ee556b0e024d25be
> 6092d405ce8d1cccbb9df1823ba79713e@%3Cdev.guacamole.apache.org%3E
>
> The full text of the proposed resolution can be found below.
>
> Please review and vote:
>
> [ ] +1 Graduate Apache Guacamole podling from the Incubator
> [ ] +0 Don't care
> [ ] -1 Don't graduate Apache Guacamole from the Incubator because...
>
> This vote will be open for at least 72 hours.
>
>
The vote to graduate Apache Guacamole to TLP is now closed. With a total of
+6 binding, +1 from the community, and NO -1 votes, the VOTE passes.
Overall vote breakdown is as follows:

+1 (binding) Raphael Bircher
+1 Pierre Smits
+1 (binding) John D. Ament
+1 (binding) Greg Trasuk
+1 (binding) Jim Jagielski
+1 (binding) Byung-Gon Chun
+1 (binding) Jean-Baptiste Onofré

Thanks to everyone who voted, and to the Incubator in general for helping
the project get this far. I will send an email to the Board proposing the
resolution voted on here, as documented at:

https://incubator.apache.org/guides/graduation.html#
submission_of_the_resolution_to_the_board

With less than 72 hours remaining before the November meeting (2017-11-15),
but definitely greater than 72 hours before December, I suppose we shall
simply see where this falls.

- Mike

Incubator status page for Guacamole reverted (somehow?)

[Mike Jumper]

Hello all,

I recently updated the Guacamole podling status page [1] to reflect its
graduation:

http://svn.apache.org/viewvc?view=revision&revision=1815410

The following morning, I verified that the changes deployed automatically,
and all was well. Later that day, however, the changes mysteriously
disappeared, and the website remains now as it was prior to my update.

Somehow, the publicly visible portion of things has reverted, while the
source which builds it has not been touched. Manually updating and building
the site locally, I see the expected changes present.

Any ideas what might be going on? Should I open a ticket with Infra?

Thanks,

- Mike

[1] http://incubator.apache.org/projects/guacamole.html

Re: Podling user@ lists (was: [PROPOSAL] SkyWalking - proposal for Apache Incubation)

[Mike Jumper]

On Fri, Dec 1, 2017 at 10:06 AM, sebb  wrote:
> On 1 December 2017 at 13:52, John D. Ament  wrote:
> > ...
> >
> > At the same time, if we're saying we want to limit the creation of user@
> > lists, if a podling is already established and using forums, discourse,
> > slack, google groups, etc, do we recommend to keep those open for user type
> > questions, until they feel they are ready to move to Apache fully?
> >
>
> That seems to me to be the sensible approach.
>
> There's no need to move user mailing lists until the podling actually 
> graduates.
>
> Also, if the podling fails to graduate, the user ASF list would be
> closed, whereas the original forums etc could continue as before.
>

IMHO, avoiding establishing TLP-like procedures for fear that a
podling may not graduate (or postponing establishing those procedures
until graduation) is self-defeating.

Speaking as a member of a recently-graduated podling that joined the
Incubator with an established user base, I think we would not have
done as well without a user@ list.

- Mike

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

Re: Podling user@ lists (was: [PROPOSAL] SkyWalking - proposal for Apache Incubation)

[Mike Jumper]

On Fri, Dec 1, 2017 at 11:11 AM, sebb  wrote:
> On 1 December 2017 at 18:57, Mike Jumper  wrote:
>>...
>>
>> Speaking as a member of a recently-graduated podling that joined the
>> Incubator with an established user base, I think we would not have
>> done as well without a user@ list.
>
> So how did your users communicate before the podling was established?

Users communicated on forums hosted at SourceForge. Once the project
was accepted into the Incubator, a sticky was added to the forums
advising users to migrate to the user@ list. When new threads were
created in the old forums, the user would be directed to reopen the
thread on the mailing lists. Eventually, after enough time had elapsed
that people were generally using the lists instead of the forums, the
forums were closed down permanently following a final advisory sticky.

> Surely that would have continued to work during incubation even if the
> user list was not created?
>

Work, yes, but the podling would not have been as healthy. Gaining
experience conducting non-development user support/discussion via
mailing lists was important, and seems to me to be exactly the sort of
thing that should be done prior to graduation, not after.

- Mike

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

Re: Apache Policy Quiz

[Mike Jumper]

On Wed, Jan 24, 2018 at 5:49 PM, Justin Mclean 
wrote:

> ... It’s probably harder and not as fun as the logo game ...
>
>
I'm not sure anything can as hard as the Apache Lucene question in the logo
game:

https://github.com/justinmclean/ApacheLogos/blob/84a740914a7ea55c27875dbd83900a1c3c1d97a2/resources/logos-blur/lucene.jpg

;)

- Mike

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

[Mike Jumper]

On Sun, May 20, 2018 at 10:07 PM, SHUANG SU  wrote:

> Thanks, Justin,
>
> I think I should remove the jar about rat from the artifact, and then
> there is no binary code anymore.
>
> But I am puzzled about the definition of the term "compiled code".
> Generally, the JavaScript code does not need to be compiled to binary. The
> code in "dist/**" is also JavaScript code, which is combined to some single
> files and some of them are minified. And the ".map" file is provided for
> mapping each term of the combined code to the original code in src/**.
> Without or without the ".map", the combined code can be checked. I think
> this kind of combined code is not "compiled code" ...


It's not purely about being able to check things, nor about how you define
the word "compiled". You also need to be able to make changes. From
http://www.apache.org/legal/release-policy.html#compiled-packages :

"... All releases are in the form of the source materials needed to make
changes to the software being released. ..."

In the sense that the original source has been passed through a tool that
mangled it into a form that can't be readily modified, it's not source,
even if you don't want to call it "compiled".

- Mike