Re: [VOTE] Accept Joshua as an Apache Incubator Podling

[Tommaso Teofili]

2016-02-01 16:20 GMT+01:00 Mattmann, Chris A (3980) <
chris.a.mattm...@jpl.nasa.gov>:

> Hey Jim,
>
> This is a valid concern, one that I hope is mediated by taking
> however long it takes in Incubation to attract some new committers
> to work on the project. Hopefully too you saw how long I took to
> allow the discussion to occur and so forth.
>
> Lewis has actively contributed to Joshua already - you can see -
> via the HomeBrew package he created, see:
>
> https://github.com/Homebrew/homebrew/pull/45746
>
>
> You can see too it wasn’t something just recent or something
> super quick it’s something he had to work at.
>
> As for me, my involvement is going to be limited, but I am
> actively pursuing Tika’s integration with Joshua as part of
> TIKA-1343: http://issues.apache.org/jira/browse/TIKA-1343.
>
> Finally my suspicion is that Tom, Henry and Tommaso will
> contribute a lot as well.
>

FWIW although I'm new to Joshua I am very interested and plan to contribute
(maybe we integrations here and there, hint hint) as much as I can.

Regards,
Tommaso


>
> Thanks for listening.
>
> Cheers,
> Chris
>
> ++
> Chris Mattmann, Ph.D.
> Chief Architect
> Instrument Software and Science Data Systems Section (398)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 168-519, Mailstop: 168-527
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
>
>
>
>
>
> -Original Message-
> From: Jim Jagielski 
> Reply-To: "general@incubator.apache.org" 
> Date: Monday, February 1, 2016 at 4:20 AM
> To: "general@incubator.apache.org" 
> Cc: "p...@cs.jhu.edu" 
> Subject: Re: [VOTE] Accept Joshua as an Apache Incubator Podling
>
> >I know this is specifically called-out in the proposal, but it
> >does seem worthy of further discussion.
> >
> >This has a pretty small list of initial committers, esp when one considers
> >how over-booked 2 of them appear to be.
> >
> >So, realistically, how active do both Chris and Lewis expect
> >to be?
> >
> >> On Jan 30, 2016, at 3:00 PM, Mattmann, Chris A (3980)
> >> wrote:
> >>
> >> Hi Everyone,
> >>
> >> OK the discussion is now completed. Please VOTE to accept Joshua
> >> into the Apache Incubator. I’ll leave the VOTE open for at least
> >> the next 72 hours, with hopes to close it next Friday the 5th of
> >> February, 2016.
> >>
> >> [ ] +1 Accept Joshua as an Apache Incubator podling.
> >> [ ] +0 Abstain.
> >> [ ] -1 Don’t accept Joshua as an Apache Incubator podling because..
> >>
> >> Of course, I am +1 on this. Please note VOTEs from Incubator PMC
> >> members are binding but all are welcome to VOTE!
> >>
> >> Cheers,
> >> Chris
> >>
> >> ++
> >> Chris Mattmann, Ph.D.
> >> Chief Architect
> >> Instrument Software and Science Data Systems Section (398)
> >> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> >> Office: 168-519, Mailstop: 168-527
> >> Email: chris.a.mattm...@nasa.gov
> >> WWW:  http://sunset.usc.edu/~mattmann/
> >> ++
> >> Adjunct Associate Professor, Computer Science Department
> >> University of Southern California, Los Angeles, CA 90089 USA
> >> ++
> >>
> >>
> >>
> >>
> >>
> >> -Original Message-
> >> From: jpluser 
> >> Date: Tuesday, January 12, 2016 at 10:56 PM
> >> To: "general@incubator.apache.org" 
> >> Cc: "p...@cs.jhu.edu" 
> >> Subject: [DISCUSS] Apache Joshua Incubator Proposal - Machine
> >>Translation
> >> Toolkit
> >>
> >>> Hi Everyone,
> >>>
> >>> Please find attached for your viewing pleasure a proposed new project,
> >>> Apache Joshua, a statistical machine translation toolkit. The proposal
> >>> is in wiki draft form at:
> >>>https://wiki.apache.org/incubator/JoshuaProposal
> >>>
> >>> Proposal text is copied below. I’ll leave the discussion open for a
> >>>week
> >>> and we are interested in folks who would like to be initial committers
> >>> and mentors. Please discuss here on the thread.
> >>>
> >>> Thanks!
> >>>
> >>> Cheers,
> >>> Chris (Champion)
> >>>
> >>> ———
> >>>
> >>> = Joshua Proposal =
> >>>
> >>> == Abstract ==
> >>> [[joshua-decoder.org|Joshua]] is an open-source statistical machine
> >>> translation toolkit. It includes a Java-based decoder for translating
> >>>with
> >>> phrase-based, hierarchical, and syntax-based translation models, a
> >>> Hadoop-based grammar extractor 

Re: [VOTE] Accept Guacamole into the Apache incubator

[Jim Jagielski]

+1 (binding)
> On Feb 2, 2016, at 10:05 AM, Jean-Baptiste Onofré  wrote:
> 
> Hi,
> 
> The Guacamole proposal was discussed couple of weeks ago.
> 
> The complete discussion thread is available here:
> 
> http://mail-archives.apache.org/mod_mbox/incubator-general/201601.mbox/%3c56a5c8c3.7070...@guac-dev.org%3E
> 
> As reminder the GuacamoleProposal is here:
> 
> https://wiki.apache.org/incubator/GuacamoleProposal
> 
> As we received only positive feedbacks in the discussion thread, we think 
> it's time to call for a vote to accept Guacamole into the Incubator.
> 
> Please cast your vote to:
> [] +1 - accept Apache Guacamole as a new incubating project
> []  0 - not sure
> [] -1 - do not accept the Apache Guacamole project (because: ...)
> 
> Thanks,
> Regards
> JB
> 
> 
> = GuacamoleProposal =
> 
> == Abstract ==
> 
> Guacamole is an enterprise-grade, protocol-agnostic, remote desktop gateway. 
> Combined with cloud hosting, Guacamole provides an excellent alternative to 
> traditional desktops. Guacamole aims to make cloud-hosted desktop access 
> preferable to traditional, local access.
> 
> == Background ==
> 
> Guacamole began in 2010 as a personal project - a means for Mike Jumper to 
> access to his own computer from work. Mike’s job at that time had a firewall 
> which blocked outbound access to everything except HTTP and HTTPS, and 
> directly circumventing the firewall (by changing the SSH server port, for 
> example) was a fireable offense. Mike needed a solution which provided remote 
> access and yet was a true web application. He found several projects 
> providing text-based terminal access, but decided that he wanted to make 
> something new and different.
> 
> The project began as a simple VNC client but grew rapidly in capability and 
> performance until it became an enterprise-grade, protocol-agnostic, remote 
> desktop gateway supporting both VNC and RDP. Support for SSH was added later, 
> followed by audio, file transfer, etc. By this point, Guacamole was fast and 
> stable enough to be used daily and in place of a traditional desktop.
> 
> Having used and developed Guacamole to its current state, and having observed 
> the general shift of the industry toward cloud computing and related 
> technologies, we now see Guacamole as the primary and only viable open source 
> solution for a future of cloud-hosted desktops.
> 
> Guacamole's purpose is twofold:
> 
> * To provide seamless and performant access to desktops over the web.
> * To provide an API which allows others, including commercial entities, to 
> integrate Guacamole's core into their own applications.
> 
> We believe that the lifestyle enabled by Guacamole should be preferable to 
> traditional, physically-anchored desktops, that the software enabling this 
> should be 100% free in every sense of the word, and that users should not be 
> limited by their current location, by the software installed on whatever 
> computer they are using at the moment, nor by how powerful/weak the hardware 
> of that computer happens to be.
> 
> Guacamole is stable and production-ready. It is in active production use by 
> several companies, including ESI, Glyptodon, HP, Nanocloud Software, as well 
> as individuals.
> 
> == Rationale ==
> 
> Due to the utility and popularity of cloud platforms, a logical extension to 
> traditional application hosting is to host complete desktops. The Guacamole 
> project is aimed at achieving this, and we believe that the best way to 
> fulfill the true potential of this project is to bring its development within 
> Apache and, by so doing, foster a larger community and higher visibility. The 
> resulting continuous improvements to its design and implementation will make 
> Guacamole the best tool for the job for a wide variety of use cases.
> 
> == Initial Goals ==
> 
> Our initial goals are to bring Guacamole into the ASF, transition internal 
> engineering processes into the open, and foster a collaborative development 
> model according to the "Apache Way."
> 
> == Current Status ==
> 
> Guacamole is production-ready and already provides a large set of features. 
> It is currently licensed under the MIT license, but will be relicensed under 
> the Apache license if accepted for incubation.
> 
> The source repositories are:
> 
> * https://github.com/glyptodon/guacamole-server
> * https://github.com/glyptodon/guacamole-client
> 
> == Meritocracy ==
> 
> We intend to radically expand the initial developer and user community by 
> running the project in accordance with the "Apache Way". Users and new 
> contributors will be treated with respect and welcomed. By participating in 
> the community and providing quality patches/support that move the project 
> forward, they will earn merit. The community will also be encouraged to 
> provide non-code contributions (documentation, events, community management, 
> etc.) and will gain merit for doing so. Those with a proven support and 
> 

Re: [VOTE] Accept Guacamole into the Apache incubator

[Jim Jagielski]

+1 (binding)
> On Feb 2, 2016, at 10:03 AM, Jean-Baptiste Onofré  wrote:
> 
> Erf, sorry about that:
> 
> Please cast your vote to:
> [] +1 - accept Apache Guacamole as a new incubating project
> []  0 - not sure
> [] -1 - do not accept the Apache Guacamole project (because: ...)
> 
> 
> 
> On 02/02/2016 03:51 PM, Daniel Gruno wrote:
>> s/Beam/Guacamole/g in the stuff below, please, before we start the vote ;)
>> 
>> With regards,
>> Daniel.
>> 
>> On 02/02/2016 02:29 PM, Jean-Baptiste Onofré wrote:
>>> Hi,
>>> 
>>> The Guacamole proposal was discussed couple of weeks ago.
>>> 
>>> The complete discussion thread is available here:
>>> 
>>> http://mail-archives.apache.org/mod_mbox/incubator-general/201601.mbox/%3c56a5c8c3.7070...@guac-dev.org%3E
>>> 
>>> 
>>> As reminder the GuacamoleProposal is here:
>>> 
>>> https://wiki.apache.org/incubator/GuacamoleProposal
>>> 
>>> As we received only positive feedbacks in the discussion thread, we
>>> think it's time to call for a vote to accept Guacamole into the Incubator.
>>> 
>>> Please cast your vote to:
>>> [] +1 - accept Apache Beam as a new incubating project
>>> []  0 - not sure
>>> [] -1 - do not accept the Apache Beam project (because: ...)
>>> 
>>> Thanks,
>>> Regards
>>> JB
>>> 
>>> 
>>> = GuacamoleProposal =
>>> 
>>> == Abstract ==
>>> 
>>> Guacamole is an enterprise-grade, protocol-agnostic, remote desktop
>>> gateway. Combined with cloud hosting, Guacamole provides an excellent
>>> alternative to traditional desktops. Guacamole aims to make cloud-hosted
>>> desktop access preferable to traditional, local access.
>>> 
>>> == Background ==
>>> 
>>> Guacamole began in 2010 as a personal project - a means for Mike Jumper
>>> to access to his own computer from work. Mike’s job at that time had a
>>> firewall which blocked outbound access to everything except HTTP and
>>> HTTPS, and directly circumventing the firewall (by changing the SSH
>>> server port, for example) was a fireable offense. Mike needed a solution
>>> which provided remote access and yet was a true web application. He
>>> found several projects providing text-based terminal access, but decided
>>> that he wanted to make something new and different.
>>> 
>>> The project began as a simple VNC client but grew rapidly in capability
>>> and performance until it became an enterprise-grade, protocol-agnostic,
>>> remote desktop gateway supporting both VNC and RDP. Support for SSH was
>>> added later, followed by audio, file transfer, etc. By this point,
>>> Guacamole was fast and stable enough to be used daily and in place of a
>>> traditional desktop.
>>> 
>>> Having used and developed Guacamole to its current state, and having
>>> observed the general shift of the industry toward cloud computing and
>>> related technologies, we now see Guacamole as the primary and only
>>> viable open source solution for a future of cloud-hosted desktops.
>>> 
>>> Guacamole's purpose is twofold:
>>> 
>>>  * To provide seamless and performant access to desktops over the web.
>>>  * To provide an API which allows others, including commercial entities,
>>> to integrate Guacamole's core into their own applications.
>>> 
>>> We believe that the lifestyle enabled by Guacamole should be preferable
>>> to traditional, physically-anchored desktops, that the software enabling
>>> this should be 100% free in every sense of the word, and that users
>>> should not be limited by their current location, by the software
>>> installed on whatever computer they are using at the moment, nor by how
>>> powerful/weak the hardware of that computer happens to be.
>>> 
>>> Guacamole is stable and production-ready. It is in active production use
>>> by several companies, including ESI, Glyptodon, HP, Nanocloud Software,
>>> as well as individuals.
>>> 
>>> == Rationale ==
>>> 
>>> Due to the utility and popularity of cloud platforms, a logical
>>> extension to traditional application hosting is to host complete
>>> desktops. The Guacamole project is aimed at achieving this, and we
>>> believe that the best way to fulfill the true potential of this project
>>> is to bring its development within Apache and, by so doing, foster a
>>> larger community and higher visibility. The resulting continuous
>>> improvements to its design and implementation will make Guacamole the
>>> best tool for the job for a wide variety of use cases.
>>> 
>>> == Initial Goals ==
>>> 
>>> Our initial goals are to bring Guacamole into the ASF, transition
>>> internal engineering processes into the open, and foster a collaborative
>>> development model according to the "Apache Way."
>>> 
>>> == Current Status ==
>>> 
>>> Guacamole is production-ready and already provides a large set of
>>> features. It is currently licensed under the MIT license, but will be
>>> relicensed under the Apache license if accepted for incubation.
>>> 
>>> The source repositories are:
>>> 
>>>  * https://github.com/glyptodon/guacamole-server
>>>  * 

Re: [VOTE] Accept Joshua as an Apache Incubator Podling

[Jim Jagielski]

+1 (binding)

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

Re: [VOTE] Release Apache Geode (incubating) 1.0.0-incubating.M1

[Justin Mclean]

Hi,

> NOTICE contains copyright, commons-io [2]

It’s my understanding that for an ASF produced product with the name, copyright 
and “this software produced at the ASF” that nothing needs to be added to 
notice.

> NOTICE contains copyright and a few other declarations, log4j2 [3]

Drop the Apache one and add the rest. I don’t know the history but it looks 
like these are from copyright statements that have been relocated from the 
original source headers. Note [1] has standard ASF header and these 
instructions [2].

> NOTICE contains LOTS of stuff, lucene [4]

Which looks wrong to me as it contains un-required Apache, MIT and BSD 
software. It looks like most (if not all) of that should be in LICENSE not 
NOTICE. Given lucene has been about for a long time there are probably 
historical reasons for this. The policy of what goes in notice / license has 
changed over time.

Thanks,
Justin

1. 
https://github.com/apache/logging-log4j2/blob/master/log4j-core/src/main/java/org/apache/logging/log4j/core/config/plugins/util/ResolverUtil.java
2. http://www.apache.org/dev/licensing-howto.html#mod-notice
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Geode (incubating) 1.0.0-incubating.M1

[Justin Mclean]

Hi,

Changing my vote to +1 binding.

> As I mentioned in my other response, thanks for the great feedback and quick 
> turnaround!  I filed JIRA’s based on the issues you noted below.

No problem, thanks for raising the JIRA’s quickly.

>> This file [12] incorrectly has an Apache header and is licensed under an 
>> MX4J license [13]. While is permissive, it’s not "Apache like" as claimed. 
>> The is not list as a category A license [14] so you probably need to raise a 
>> legal JIRA to get it added. It looks to me like it requires attribution and 
>> would need to be listed in LICENSE.
> 
> [GEODE-902] Agreed, we will investigate this.

While not in the category A list, it looks to be permissive so I see no need 
for it to block an incubating release.

Thanks,
Justin

Re: Confusion over NOTICE vs LICENSE files

[Justin Mclean]

Hi,

> Speaking from the NiFi side I can assure you an enormous amount of
> time, energy, and communication go into LICENSE and NOTICE handling
> for this project.

Sorry if you thought my message applied otherwise, there’s certainly no harm 
intended. 

I was just pointing out (with some examples) that a little confusion seems to 
occurs at TLP as well.

It was just a casual glance at your NOTICE, certainly not a formal or thorough 
review, but I would guess that these lines:

This product includes the following work from the Apache Hadoop project:
BoundedByteArrayOutputStream.java adapted to 
SoftLimitBoundedByteArrayOutputStream.java

Doesn’t need to be include in your NOTICE file as per [1]. It would be nice to 
mention this somewhere but I’m guessing NOTICE isn’t the correct place?

Of course something as minor as this may not even matter as it imposes little 
on any down stream projects.

Thanks,
Justin

1. http://www.apache.org/dev/licensing-howto.html#bundle-asf-product




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

Re: [VOTE] Release Apache Geode (incubating) 1.0.0-incubating.M1

[Niall Pemberton]

I already reviewed the release and voted +1 on dev@geode, but just wanted
to ensure that my vote was also counted here.

+1 (binding)

Niall

On Wed, Feb 3, 2016 at 1:32 AM, Anthony Baker  wrote:

> Hello,
>
> This is a call for a vote on the Apache Geode (incubating) release
> 1.0.0-incubating.M1.
>
> This release candidate, 1.0.0-incubating.M1.RC2, has successfully passed a
> vote for a release on the geode developer mailing list.
>
> Vote thread:
>
> http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201601.mbox/%3cby2pr10mb0615e804a4f4c0c9d4606339b6...@by2pr10mb0615.namprd10.prod.outlook.com%3e
>
> Results:
>
> http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201602.mbox/%3c09e32fc5-6691-4f88-a75b-5ef8efdfe...@pivotal.io%3e
>
> It fixes the following issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318420=12334248
>
> Compared to first release candidate (RC1), it fixes the following issues:
> [GEODE-610] - Review Geode's LICENSE & NOTICE File(s)
> [GEODE-769] - improve README.md file
> [GEODE-815] - RC Feedback: Fix LICENSE and NOTICE files
>
> Release candidate tag:
> rel/1.0.0-incubating.M1.RC2
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;a=tag;h=refs/tags/rel/v1.0.0-incubating.M1.RC2
>
> Commit ID: c26334542fa9e90daff5f58467d6e174b3e0f3e2
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;a=commit;h=c26334542fa9e90daff5f58467d6e174b3e0f3e2
>
> Source and binary files:
>
> https://dist.apache.org/repos/dist/dev/incubator/geode/1.0.0-incubating.M1.RC2/
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachegeode-1001/
>
> Geode's KEYS file containing PGP keys we use to sign the release:
>
> https://github.com/apache/incubator-geode/blob/release/1.0.0-incubating.M1/KEYS
>
> Release Key: pub  4096R/C72CFB64 2015-10-01
> Fingerprint: 948E 8234 14BE 693A 7F74  ABBE 19DB CAEE C72C FB64
>
> Please vote on releasing this package as Apache Geode 1.0.0-incubating.M1:
>
>  This vote will be open for 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Anthony on behalf of the Apache Geode (incubating) team
>
>

Re: [VOTE] Apache SystemML 0.9.0-incubating (RC3)

[Luciano Resende]

Thanks for the thorough review, we will definitely look into all these
issues for the next release.

Anyone else willing to review ? We still need at least one more vote.

On Tue, Feb 2, 2016 at 3:06 PM, Justin Mclean 
wrote:

> Hi,
>
> +1 (binding) but only if LICENSE is fixed for next release
>
> I checked:
> - file contains incubating
> - signatures and hashed good
> - DISCLAIMER exists
> - LICENSE is missing bundled software [11][12]
> - NOTICE is OK
> - Several source files are missing Apache headers [7]. While they are
> generated files it would be nice for them to have Apache headers.
> - No unexpected binary files
> - Can compile from source
>
> LICENSE is missing:
> - Bootstrap [1] (MIT licensed)
> - Modernizr [2] (MIT/BSD licensed)
> - Polyfill [2] (MIT/BSD licensed)
> - Respond [2] (MIT/GPL licensed)
> - Normalize [3] (MIT licensed)
> - AnchorJS [5] (MIT licensed)
> - JQuery [6] (MIT licensed)
>
> I notice some of the code comes from/is based on "Introduction to
> Algorithms, Third Edition, MIT Press”. (e.g. [8]) Do you require permission
> to use this? How is this material licensed? Could any of the other material
> mentioned in [4] be an issue copyright wise or need to be placed in LICENSE
> if it is permissively licensed?
>
> Do the LICENSE and NOTICE files in ./src/assembly/standalone/ need to be
> included in the source release?
>
> Also for the next release could you place the RC in the correct place. [9]
>
> Can [10] (an compress archive containing a text file) not be placed in the
> source release but be created at build time?
>
> Thanks,
> Justin
>
> 1. ./docs/js/vendor/bootstrap.min.js
> 2. ./docs/js/vendor/modernizr-2.6.1-respond-1.1.0.min.js
> 3. ./docs/css/bootstrap.min.css
> 4. ./docs/Algorithms\ Reference/SystemML_Algorithms_Reference.bib
> 5. ./docs/js/vendor/anchor.min.js
> 6. ./docs/js/vendor/jquery-1.12.0.min.js
> 7. ./src/main/java/org/apache/sysml/parser/*.java
> 8.
> ./src/main/java/org/apache/sysml/hops/rewrite/RewriteMatrixMultChainOptimization.java
> 9.
> http://incubator.apache.org/guides/releasemanagement.html#glossary-incubator-dist
> 10
> ./docs/files/mlcontext-programming-guide/zeppelin-notebook-linear-regression/2AZ2AQ12B.tar.gz
> 11. http://www.apache.org/dev/licensing-howto.html#guiding-principle
> 12. http://www.apache.org/dev/licensing-howto.html#permissive-deps
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Luciano Resende
http://people.apache.org/~lresende
http://twitter.com/lresende1975
http://lresende.blogspot.com/

Re: Confusion over NOTICE vs LICENSE files

[Joe Witt]

Justin,

Speaking from the NiFi side I can assure you an enormous amount of
time, energy, and communication go into LICENSE and NOTICE handling
for this project.  We've had discussions with PMC and committers of
other projects to learn their approach as well as to encourage them to
follow these policies as well.

We attempt to adhere to both spirit and letter of policy regarding
licensing and notice information.  The NOTICE [1] you reference for us
is only the source release NOTICE and I believe it to be correct for
the source release.  Can you share what you see is missing?

We also maintain a notice that specifically applies to any convenance
binaries we produce [2].  In fact, we also do that level of artifact
specific NOTICE resolution for any bundling of dependencies we do (for
example [3]).

We produced and frequently reference this guide to help our community
stay consistent with the policy as we understood/understand it [4].

And here you can see that we are pretty strict in following the
understanding of the policy even when it deviates from otherwise
accepted practice [5].

I very much welcome efforts to improve this guidance.  I think some of
the work Todd Lipcon has initiated recently is a great start.

Now I write this realizing you are an excellent contributor to the
licensing/notice discussions and you provided some of the best RC
reviews in this area as well for us in incubation.  So I write this
fully respecting you just want things to be done right.  if we're
actually doing something wrong let us know and we'll sort it out.

[1] https://github.com/apache/nifi/blob/master/NOTICE
[2] https://github.com/apache/nifi/blob/master/nifi-assembly/NOTICE
[3] 
https://github.com/apache/nifi/blob/master/nifi-nar-bundles/nifi-hadoop-libraries-bundle/nifi-hadoop-libraries-nar/src/main/resources/META-INF/NOTICE
[4] https://nifi.apache.org/licensing-guide.html
[5] https://issues.apache.org/jira/browse/LEGAL-230

On Wed, Feb 3, 2016 at 7:01 PM, Justin Mclean  wrote:
> Hi
>
> It seems that some of the confusion comes from what top level projects have 
> done and not keep up with policy? From a 5 minute search (and not to pick on 
> / point out any particular project) here’s some examples were I think 
> improvement could be made to NOTICE files. [1][2][3][4][5][6][7]
>
> Perhaps it's time to ask TLP to review their LICENCE / NOTICE to be a little 
> more consistent with current policy? Any suggestion on how we would go about 
> this? Does the policy need to be made clearer first?
>
> Thanks,
> Justin
>
> 1. https://github.com/apache/spark/blob/master/NOTICE 
> 
> 2. https://github.com/apache/flink/blob/master/NOTICE 
> 
> 3. https://github.com/apache/nifi/blob/master/NOTICE 
> 
> 4. https://github.com/apache/accumulo/blob/master/NOTICE 
> 
> 5. https://github.com/apache/camel/blob/master/NOTICE.txt 
> 
> 6. https://github.com/apache/phoenix/blob/master/NOTICE 
> 
> 7. https://github.com/apache/lucene-solr/blob/master/lucene/NOTICE.txt 
> 
>
>
>
>

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

Re: Confusion over NOTICE vs LICENSE files

[Justin Mclean]

Hi

It seems that some of the confusion comes from what top level projects have 
done and not keep up with policy? From a 5 minute search (and not to pick on / 
point out any particular project) here’s some examples were I think improvement 
could be made to NOTICE files. [1][2][3][4][5][6][7]

Perhaps it's time to ask TLP to review their LICENCE / NOTICE to be a little 
more consistent with current policy? Any suggestion on how we would go about 
this? Does the policy need to be made clearer first?

Thanks,
Justin

1. https://github.com/apache/spark/blob/master/NOTICE 

2. https://github.com/apache/flink/blob/master/NOTICE 

3. https://github.com/apache/nifi/blob/master/NOTICE 

4. https://github.com/apache/accumulo/blob/master/NOTICE 

5. https://github.com/apache/camel/blob/master/NOTICE.txt 

6. https://github.com/apache/phoenix/blob/master/NOTICE 

7. https://github.com/apache/lucene-solr/blob/master/lucene/NOTICE.txt 

Re: Confusion over NOTICE vs LICENSE files

[Justin Mclean]

HI,

> [4] https://nifi.apache.org/licensing-guide.html 
> 
BTW nicely put together, it's well worth a read and clearly explains quite 
tricky LICENSE and NOTICE issues.

Thanks,
Justin

Re: Confusion over NOTICE vs LICENSE files

[Roman Shaposhnik]

On Wed, Feb 3, 2016 at 4:01 PM, Justin Mclean  wrote:
> Hi
>
> It seems that some of the confusion comes from what top level projects have 
> done and not keep up with policy?
> From a 5 minute search (and not to pick on / point out any particular 
> project) here’s some examples were
> I think improvement could be made to NOTICE files. [1][2][3][4][5][6][7]
>
> Perhaps it's time to ask TLP to review their LICENCE / NOTICE to be a little 
> more consistent with current policy?
> Any suggestion on how we would go about this? Does the policy need to be made 
> clearer first?

FWIW I must echo Justin's sentiment: there's quite a few TLPs out
there that prove
to be far from ideal role models for the podlings. In fact, even in my
own case, I was
looking at a few examples that proved to be an unfortunate choice of
'prior art'.

Thanks,
Roman.

P.S. Justin, I don't think we thank you enough for your diligence
around these areas. So. THANK YOU

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

Re: Confusion over NOTICE vs LICENSE files

[Julian Hyde]

I can see how a TLP would not be receptive to someone nit-picking their 
LICENSE/NOTICE files. Asking for patches, as Marvin suggests, is one approach 
that might work. Another approach is for someone with expertise in licensing to 
approach a TLP and offer to take them through a licensing review. Of course the 
TLP is at liberty to refuse, but if they accepted, some knowledge would 
undoubtedly rub off. I can speak only for the Calcite project, but I think we’d 
be happy to go through such a process every couple of years.

Julian


> On Feb 3, 2016, at 6:32 PM, Marvin Humphrey  wrote:
> 
> On Wed, Feb 3, 2016 at 4:01 PM, Justin Mclean  wrote:
>> Perhaps it's time to ask TLP to review their LICENCE / NOTICE to be a little
>> more consistent with current policy?
> 
> I approached a bunch of Lucene PMC members about this at ApacheCon a couple
> years back and they were receptive to the idea.
> 
> However, I don't think we should approach any other TLPs, to be honest.  A lot
> of the issues we'd like to fix in TLP LICENSE and NOTICE files would improve
> compliance with Apache *policy*, not law.  TLPs are the Board's purview -- the
> Incubator's writ only extends to podlings.
> 
> We can let the Board know that poor TLP compliance with Apache licensing
> policy is complicating our work in the Incubator, and perhaps the Board will
> solicit our help as volunteers to work on that problem.  But I think that if
> an initiative to tackle TLP licensing documentation originates on
> general@incubator, that's asking for trouble.  The last thing we need is
> conflict with the Board over ostensible IPMC overreach.
> 
>> Any suggestion on how we would go about this?
> 
> For any TLP we approach, I think we need to ensure that any proposed revisions
> are real, valuable contributions to the community.
> 
> *   Provide patches, rather than point out flaws.
> *   Explain persuasively and coherently to the PMC why these patches should be
>applied, while minimizing what we ask of them in terms of review and
>research.
> *   If possible, provide project-specific improvements which will help the PMC
>handle licensing better and with less effort in the future.
> 
> We need to bear in mind that we are outsiders while a project's PMC members
> are charged with legal oversight of their project, and that there is generally
> limited energy and patience for dealing with legal stuff.
> 
>> Does the policy need to be made clearer first?
> 
> Yes, I think that's important -- it will help us to persuade PMCs that our
> proposed changes are both correct and worthwhile.
> 
> Marvin Humphrey
> 
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 


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

Re: Confusion over NOTICE vs LICENSE files

[Marvin Humphrey]

On Wed, Feb 3, 2016 at 4:01 PM, Justin Mclean  wrote:
> Perhaps it's time to ask TLP to review their LICENCE / NOTICE to be a little
> more consistent with current policy?

I approached a bunch of Lucene PMC members about this at ApacheCon a couple
years back and they were receptive to the idea.

However, I don't think we should approach any other TLPs, to be honest.  A lot
of the issues we'd like to fix in TLP LICENSE and NOTICE files would improve
compliance with Apache *policy*, not law.  TLPs are the Board's purview -- the
Incubator's writ only extends to podlings.

We can let the Board know that poor TLP compliance with Apache licensing
policy is complicating our work in the Incubator, and perhaps the Board will
solicit our help as volunteers to work on that problem.  But I think that if
an initiative to tackle TLP licensing documentation originates on
general@incubator, that's asking for trouble.  The last thing we need is
conflict with the Board over ostensible IPMC overreach.

> Any suggestion on how we would go about this?

For any TLP we approach, I think we need to ensure that any proposed revisions
are real, valuable contributions to the community.

*   Provide patches, rather than point out flaws.
*   Explain persuasively and coherently to the PMC why these patches should be
applied, while minimizing what we ask of them in terms of review and
research.
*   If possible, provide project-specific improvements which will help the PMC
handle licensing better and with less effort in the future.

We need to bear in mind that we are outsiders while a project's PMC members
are charged with legal oversight of their project, and that there is generally
limited energy and patience for dealing with legal stuff.

> Does the policy need to be made clearer first?

Yes, I think that's important -- it will help us to persuade PMCs that our
proposed changes are both correct and worthwhile.

Marvin Humphrey

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

Re: [VOTE] HAWQ 2.0.0-beta-incubating RC4

[Roman Shaposhnik]

Justin,

once again -- thank you so much for your diligent reviews! Wrt.
NOTICE/LICENSE files
can you please take a look at this and see if that's acceptable:
   https://github.com/rvs/incubator-hawq/blob/master/LICENSE
   https://github.com/rvs/incubator-hawq/blob/master/NOTICE

Wrt. crypto code -- you ended up being absolutely right and apologize
for the confusion.
The only thing I can say in my defense is that I got double tripped up by:
 http://www.apache.org/dev/crypto.html#faq-previouslyexported
 
http://www.postgresql.org/message-id/can1ef+z1b1ecxq1gyudfo8wbp5+6mfkcqqgu_xvtnzuak9h...@mail.gmail.com

At any rate, we're removing the crypto code:
 https://issues.apache.org/jira/browse/HAWQ-394

Hopefully this will take care of your concerns.

Thanks,
Roman.

On Wed, Jan 27, 2016 at 5:12 AM, Justin Mclean  wrote:
> Hi,
>
>> I think this section of NOTICE is simply not worded well enough.
>
> No problem, if it is not bundled it should be removed, if the wording is 
> wrong it should be fixed.
>
>> Not it doesn’t.
>
> You might want to double check the files in here:
> ./contrib/pgcrypto
> ./src/interfaces/libpq
>
> Just do a quick search for SSL for instance. Or take a look a 
> contrib/pgcrypto/crypt-blowfish.c it says "This code comes from John the 
> Ripper password cracker, with reentrant and crypt(3) interfaces added,” and 
> that looks to be GPL software or I think public domain?  I’d expect that to 
> be in the LICENSE file. [1] I haven’t looked at everything in detail but 
> there enough for concern and IMO it needs to be double checked.
>
> Exactly what is covered by "cryptographic functions” I’m not entirely sure. 
> Do we have somewhere where that is spelt out? For instance is MD5 included in 
> that? (see ./contrib/pgcrypto/crypt-md5.c, ./contrib/pgcrypto/md5.c, 
> ./src/backend/libpq/md5.c) or DES (./contrib/pgcrypto/crypt-des.c) or SHA2 
> (./contrib/pgcrypto/sha2.c) or blowfish mentioned above? (and those are not 
> the only files)
>
>> Apache License  -- no sure what you mean here -- I think we're simply
>> bubbling up the dependencies NOTICEs. Why is that wrong?
>
> Bubbling up NOTICEs is correct but AFAICS you’re not doing that.
>
>> Not sure what do you want us to do to handle that case.
>
> Fix the paths or remove it if it's no longer the case would be best I think.
>
> Thanks,
> Justin
>
> 1. http://www.openwall.com/john/doc/LICENSE.shtml
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>

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

Re: [VOTE] HAWQ 2.0.0-beta-incubating RC4

[Roman Shaposhnik]

On Wed, Feb 3, 2016 at 7:00 PM, John D. Ament  wrote:
> So should we cancel this vote and wait for a new RC?

Yup.

Thanks,
Roman.

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

Re: [VOTE] Release Apache Geode (incubating) 1.0.0-incubating.M1

[John D. Ament]

+0 for now but if someone wants to give some tips I'd be happy to change to
a +1

Everything checks out, but when building the source package, it fails here

:gemfire-core:test


com.gemstone.gemfire.distributed.LocatorLauncherJUnitTest >
testSetBindAddressToUnknownHost FAILED

java.lang.AssertionError: Expected exception:
java.lang.IllegalArgumentException


com.gemstone.gemfire.distributed.ServerLauncherJUnitTest >
testSetServerBindAddressToUnknownHost FAILED

java.lang.AssertionError: Expected exception:
java.lang.IllegalArgumentException

*> Building 60% > :gemfire-core:test > 1382 tests completed, 2 failed, 31
skipped*


Not sure if there's something to do about these 2 tests.


John

On Tue, Feb 2, 2016 at 8:32 PM Anthony Baker  wrote:

> Hello,
>
> This is a call for a vote on the Apache Geode (incubating) release
> 1.0.0-incubating.M1.
>
> This release candidate, 1.0.0-incubating.M1.RC2, has successfully passed a
> vote for a release on the geode developer mailing list.
>
> Vote thread:
>
> http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201601.mbox/%3cby2pr10mb0615e804a4f4c0c9d4606339b6...@by2pr10mb0615.namprd10.prod.outlook.com%3e
>
> Results:
>
> http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201602.mbox/%3c09e32fc5-6691-4f88-a75b-5ef8efdfe...@pivotal.io%3e
>
> It fixes the following issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318420=12334248
>
> Compared to first release candidate (RC1), it fixes the following issues:
> [GEODE-610] - Review Geode's LICENSE & NOTICE File(s)
> [GEODE-769] - improve README.md file
> [GEODE-815] - RC Feedback: Fix LICENSE and NOTICE files
>
> Release candidate tag:
> rel/1.0.0-incubating.M1.RC2
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;a=tag;h=refs/tags/rel/v1.0.0-incubating.M1.RC2
>
> Commit ID: c26334542fa9e90daff5f58467d6e174b3e0f3e2
>
> https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;a=commit;h=c26334542fa9e90daff5f58467d6e174b3e0f3e2
>
> Source and binary files:
>
> https://dist.apache.org/repos/dist/dev/incubator/geode/1.0.0-incubating.M1.RC2/
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachegeode-1001/
>
> Geode's KEYS file containing PGP keys we use to sign the release:
>
> https://github.com/apache/incubator-geode/blob/release/1.0.0-incubating.M1/KEYS
>
> Release Key: pub  4096R/C72CFB64 2015-10-01
> Fingerprint: 948E 8234 14BE 693A 7F74  ABBE 19DB CAEE C72C FB64
>
> Please vote on releasing this package as Apache Geode 1.0.0-incubating.M1:
>
>  This vote will be open for 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)
>
> Anthony on behalf of the Apache Geode (incubating) team
>
>

Re: [VOTE] HAWQ 2.0.0-beta-incubating RC4

[John D. Ament]

So should we cancel this vote and wait for a new RC?

On Wed, Feb 3, 2016 at 9:56 PM Roman Shaposhnik 
wrote:

> Justin,
>
> once again -- thank you so much for your diligent reviews! Wrt.
> NOTICE/LICENSE files
> can you please take a look at this and see if that's acceptable:
>https://github.com/rvs/incubator-hawq/blob/master/LICENSE
>https://github.com/rvs/incubator-hawq/blob/master/NOTICE
>
> Wrt. crypto code -- you ended up being absolutely right and apologize
> for the confusion.
> The only thing I can say in my defense is that I got double tripped up by:
>  http://www.apache.org/dev/crypto.html#faq-previouslyexported
>
> http://www.postgresql.org/message-id/can1ef+z1b1ecxq1gyudfo8wbp5+6mfkcqqgu_xvtnzuak9h...@mail.gmail.com
>
> At any rate, we're removing the crypto code:
>  https://issues.apache.org/jira/browse/HAWQ-394
>
> Hopefully this will take care of your concerns.
>
> Thanks,
> Roman.
>
> On Wed, Jan 27, 2016 at 5:12 AM, Justin Mclean 
> wrote:
> > Hi,
> >
> >> I think this section of NOTICE is simply not worded well enough.
> >
> > No problem, if it is not bundled it should be removed, if the wording is
> wrong it should be fixed.
> >
> >> Not it doesn’t.
> >
> > You might want to double check the files in here:
> > ./contrib/pgcrypto
> > ./src/interfaces/libpq
> >
> > Just do a quick search for SSL for instance. Or take a look a
> contrib/pgcrypto/crypt-blowfish.c it says "This code comes from John the
> Ripper password cracker, with reentrant and crypt(3) interfaces added,” and
> that looks to be GPL software or I think public domain?  I’d expect that to
> be in the LICENSE file. [1] I haven’t looked at everything in detail but
> there enough for concern and IMO it needs to be double checked.
> >
> > Exactly what is covered by "cryptographic functions” I’m not entirely
> sure. Do we have somewhere where that is spelt out? For instance is MD5
> included in that? (see ./contrib/pgcrypto/crypt-md5.c,
> ./contrib/pgcrypto/md5.c, ./src/backend/libpq/md5.c) or DES
> (./contrib/pgcrypto/crypt-des.c) or SHA2 (./contrib/pgcrypto/sha2.c) or
> blowfish mentioned above? (and those are not the only files)
> >
> >> Apache License  -- no sure what you mean here -- I think we're simply
> >> bubbling up the dependencies NOTICEs. Why is that wrong?
> >
> > Bubbling up NOTICEs is correct but AFAICS you’re not doing that.
> >
> >> Not sure what do you want us to do to handle that case.
> >
> > Fix the paths or remove it if it's no longer the case would be best I
> think.
> >
> > Thanks,
> > Justin
> >
> > 1. http://www.openwall.com/john/doc/LICENSE.shtml
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>

Re: [VOTE] HAWQ 2.0.0-beta-incubating RC4

[Justin Mclean]

Hi,

> can you please take a look at this and see if that's acceptable:
>   https://github.com/rvs/incubator-hawq/blob/master/LICENSE
>   https://github.com/rvs/incubator-hawq/blob/master/NOTICE 
> 

Quick look looks much better but I’ve not gone through and double checked.

You may want to check the copyrights in NOTICE however. Have all these 
copyrights been relocated from a header file? There no need to list all 
copyrights (esp for MIT or BSD software) but only those that have be relocated 
or those included in non ASF bundled Apache licensed software.

Thanks,
Justin

Re: Confusion over NOTICE vs LICENSE files

[Justin Mclean]

Hi,

> We can let the Board know that poor TLP compliance with Apache licensing
> policy is complicating our work in the Incubator

+1 to that it makes reviewing releases a lot harder. Recently a few release 
candidates have waited too long for a vote here and that may be a factor.

Some incubating projects understandably tend to look at what TLP have done and 
copy that rather than find and wade through all of the policy documentation.

>  The last thing we need is conflict with the Board over ostensible IPMC 
> overreach.

Certainly not.

>> Does the policy need to be made clearer first?
> 
> Yes, I think that's important -- it will help us to persuade PMCs that our
> proposed changes are both correct and worthwhile.

OK lets work on that.

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

Re: [VOTE] Release Apache Geode (incubating) 1.0.0-incubating.M1

[Roman Shaposhnik]

On Tue, Feb 2, 2016 at 5:32 PM, Anthony Baker  wrote:
> Hello,
>
> This is a call for a vote on the Apache Geode (incubating) release 
> 1.0.0-incubating.M1.
>
> This release candidate, 1.0.0-incubating.M1.RC2, has successfully passed a 
> vote for a release on the geode developer mailing list.
>
> Vote thread:
> http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201601.mbox/%3cby2pr10mb0615e804a4f4c0c9d4606339b6...@by2pr10mb0615.namprd10.prod.outlook.com%3e
>
> Results:
> http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201602.mbox/%3c09e32fc5-6691-4f88-a75b-5ef8efdfe...@pivotal.io%3e
>
> It fixes the following issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318420=12334248
>
> Compared to first release candidate (RC1), it fixes the following issues:
> [GEODE-610] - Review Geode's LICENSE & NOTICE File(s)
> [GEODE-769] - improve README.md file
> [GEODE-815] - RC Feedback: Fix LICENSE and NOTICE files
>
> Release candidate tag:
> rel/1.0.0-incubating.M1.RC2
> https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;a=tag;h=refs/tags/rel/v1.0.0-incubating.M1.RC2
>
> Commit ID: c26334542fa9e90daff5f58467d6e174b3e0f3e2
> https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;a=commit;h=c26334542fa9e90daff5f58467d6e174b3e0f3e2
>
> Source and binary files:
> https://dist.apache.org/repos/dist/dev/incubator/geode/1.0.0-incubating.M1.RC2/
>
> Maven staging repo:
> https://repository.apache.org/content/repositories/orgapachegeode-1001/
>
> Geode's KEYS file containing PGP keys we use to sign the release:
> https://github.com/apache/incubator-geode/blob/release/1.0.0-incubating.M1/KEYS
>
> Release Key: pub  4096R/C72CFB64 2015-10-01
> Fingerprint: 948E 8234 14BE 693A 7F74  ABBE 19DB CAEE C72C FB64
>
> Please vote on releasing this package as Apache Geode 1.0.0-incubating.M1:
>
>  This vote will be open for 72 hours.
>
> [ ] +1 approve
> [ ] +0 no opinion
> [ ] -1 disapprove (and reason why)

+1 (binding)

Thanks,
Roman.

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

Re: [VOTE] Accept Joshua as an Apache Incubator Podling

[Danese Cooper]

+1 (binding) Accept Joshua as an Apache Incubator podling.

D

> On Jan 30, 2016, at 12:00 PM, Mattmann, Chris A (3980) 
>  wrote:
> 
> Hi Everyone,
> 
> OK the discussion is now completed. Please VOTE to accept Joshua
> into the Apache Incubator. I’ll leave the VOTE open for at least
> the next 72 hours, with hopes to close it next Friday the 5th of
> February, 2016.
> 
> [ ] +1 Accept Joshua as an Apache Incubator podling.
> [ ] +0 Abstain.
> [ ] -1 Don’t accept Joshua as an Apache Incubator podling because..
> 
> Of course, I am +1 on this. Please note VOTEs from Incubator PMC
> members are binding but all are welcome to VOTE!
> 
> Cheers,
> Chris
> 
> ++
> Chris Mattmann, Ph.D.
> Chief Architect
> Instrument Software and Science Data Systems Section (398)
> NASA Jet Propulsion Laboratory Pasadena, CA 91109 USA
> Office: 168-519, Mailstop: 168-527
> Email: chris.a.mattm...@nasa.gov
> WWW:  http://sunset.usc.edu/~mattmann/
> ++
> Adjunct Associate Professor, Computer Science Department
> University of Southern California, Los Angeles, CA 90089 USA
> ++
> 
> 
> 
> 
> 
> -Original Message-
> From: jpluser 
> Date: Tuesday, January 12, 2016 at 10:56 PM
> To: "general@incubator.apache.org" 
> Cc: "p...@cs.jhu.edu" 
> Subject: [DISCUSS] Apache Joshua Incubator Proposal - Machine Translation
> Toolkit
> 
>> Hi Everyone,
>> 
>> Please find attached for your viewing pleasure a proposed new project,
>> Apache Joshua, a statistical machine translation toolkit. The proposal
>> is in wiki draft form at: https://wiki.apache.org/incubator/JoshuaProposal
>> 
>> Proposal text is copied below. I’ll leave the discussion open for a week
>> and we are interested in folks who would like to be initial committers
>> and mentors. Please discuss here on the thread.
>> 
>> Thanks!
>> 
>> Cheers,
>> Chris (Champion)
>> 
>> ———
>> 
>> = Joshua Proposal =
>> 
>> == Abstract ==
>> [[joshua-decoder.org|Joshua]] is an open-source statistical machine
>> translation toolkit. It includes a Java-based decoder for translating with
>> phrase-based, hierarchical, and syntax-based translation models, a
>> Hadoop-based grammar extractor (Thrax), and an extensive set of tools and
>> scripts for training and evaluating new models from parallel text.
>> 
>> == Proposal ==
>> Joshua is a state of the art statistical machine translation system that
>> provides a number of features:
>> 
>> * Support for the two main paradigms in statistical machine translation:
>> phrase-based and hierarchical / syntactic.
>> * A sparse feature API that makes it easy to add new feature templates
>> supporting millions of features
>> * Native implementations of many tuners (MERT, MIRA, PRO, and AdaGrad)
>> * Support for lattice decoding, allowing upstream NLP tools to expose
>> their hypothesis space to the MT system
>> * An efficient representation for models, allowing for quick loading of
>> multi-gigabyte model files
>> * Fast decoding speed (on par with Moses and mtplz)
>> * Language packs — precompiled models that allow the decoder to be run as
>> a black box
>> * Thrax, a Hadoop-based tool for learning translation models from
>> parallel text
>> * A suite of tools for constructing new models for any language pair for
>> which sufficient training data exists
>> 
>> == Background and Rationale ==
>> A number of factors make this a good time for an Apache project focused on
>> machine translation (MT): the quality of MT output (for many language
>> pairs); the average computing resources available on computers, relative
>> to the needs of MT systems; and the availability of a number of
>> high-quality toolkits, together with a large base of researchers working
>> on them.
>> 
>> Over the past decade, machine translation (MT; the automatic translation
>> of one human language to another) has become a reality. The research into
>> statistical approaches to translation that began in the early nineties,
>> together with the availability of large amounts of training data, and
>> better computing infrastructure, have all come together to produce
>> translations results that are “good enough” for a large set of language
>> pairs and use cases. Free services like
>> [[https://www.bing.com/translator|Bing Translator]] and
>> [[https://translate.google.com|Google Translate]] have made these services
>> available to the average person through direct interfaces and through
>> tools like browser plugins, and sites across the world with higher
>> translation needs use them to translate their pages through automatically.
>> 
>> MT does not require the infrastructure of large corporations in order to
>> produce feasible output. Machine translation can be 

Re: New ASF visual identity

[Sergio Fernández]

+1

On Wed, Feb 3, 2016 at 8:40 PM, Sravya Tirukkovalur 
wrote:

> +1
>
> On Wed, Feb 3, 2016 at 10:51 AM,  wrote:
>
> >
> >
> > +1
> >
> >
> > Best,
> >
> >
> > Markus
> >
> >
> > .:: YAGNI likes a DRY KISS ::.
> >
> >
> >
> >
> >
> >
> > On Wed, Feb 3, 2016 at 10:07 AM -0800, "Marvin Humphrey" <
> > mar...@rectangular.com> wrote:
> >
> >
> >
> >
> >
> > Greets,
> >
> > The ASF has a new look:
> >
> >
> >
> https://blogs.apache.org/foundation/entry/the_apache_software_foundation_announces86
> > https://www.apache.org/foundation/press/kit/
> >
> > The main Incubator website needs to be updated with the new visual
> > identity, as do podling websites.
> >
> > I volunteer to create a drop-in replacement for the egg logo:
> >
> > http://incubator.apache.org/images/egg-logo.png
> >
> > I expect to take the same approach as the last time the graphic was
> > updated a few years back[1]: keep the black border and keep the same
> > pixel dimensions, so that existing podling web pages can simply switch
> > in the new file without needing to adapt their designs.
> >
> > Please note: the intent of this undertaking is to keep the Incubator up
> > to date and in sync with the efforts of our marketing team. It is not
> > to rework the Incubator's visual identity, so I hope that we can avoid a
> > lengthy bikeshed painting debate.
> >
> > Marvin Humphrey
> >
> > [1] https://issues.apache.org/jira/browse/INCUBATOR-112
> >
> > -
> > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > For additional commands, e-mail: general-h...@incubator.apache.org
> >
> >
>
>
> --
> Sravya Tirukkovalur
>



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

Re: Confusion over NOTICE vs LICENSE files

[Justin Mclean]

Hi,

I took a look at all the LICENSE, NOTCE and DISCLAIMER files in the non 
documentation / non web site github repos of all incubating projects. 

I was assisted by scripts and make a few assumptions for expediency so may of 
missed a couple/included a graduated or retired project.

Some data points:
- 10 repos are missing a LICENSE file
- There's some (very) minor variations of text in the LICENSE appendix
- 39 repos use a boiler plate LICENSE file
- 1 LICENSE file is missing Apache boilerplate test
- 1 repo is missing the LICENSE appendix part
- 2 repos have a non standard LICENSE appendix (filled in copyright line)
- 10 LICENSE files have the long form of MIT/BSD licenses where the short form 
is preferred
- 1 LICENSE file oddly / verbosely lists out the MIT/BSD license of all 
individual files
- at least 1 LICENSE file lists Apache licensed ASF software
- at least 8 LICENSE files list non ASF Apache licensed software
- 14 repos are missing a NOTICE file
- in the NOTICE file 14 repos use the name "Apache  (incubating)”, 55 use 
"Apache ”, and 3 use just “XXX”  (missing Apache)
- 29 repos have a NOTICE file copyright year before 2016
- 2 use the older “developed by” instead of “developed at” in the NOTICE file
- 2 have incorrect text in the NOTICE files
- at least 8 including licensing information in NOTICE that should be in 
LICENSE (IMO from a quick look)
- at least 1 has excessive copyright lines which may be incorrect
- 21 repos are missing DISCLAIMER files
- There's some (minor) variation on the DISCLAIMER wording

Projects are works in progress or may not have made a release or updated the 
files for the next release or the expected files may not be in the 1/2 dozen 
places my scripts looked at. Just take these numbers as a rough indication. I 
really didn’t want to spend too long on this.

A few NOTICE / LICENSE files have TODO’s which is nice to see. I would pass an 
IPMC vote on a release if I saw this.

It looks like a few projects are getting confused with what goes in LICENSE and 
NOTICE. The two issues seem to be adding MIT, BSD or Apache licenses to NOTICE 
when it is not required and adding extra copyright notices to NOTICE. An update 
on policy documentation to make it clearer what goes in both files would help 
here I think - which is already under way.

There also seems be some confusion around what to do with bundled Apache 
licensed software. This existing documentation is not entirely clear on how to 
handle non ASF Apache software and this has come up on the list a few times 
with some differing opionions.

A few questions on incubator policy that may need to be clarified:
- A release must include a NOTICE file, but should a repo include one?
- Likewise should a DISCLAIMER file be present in the repo?
- I thought incubating projects should be named "Apache  (incubating)” but 
the majority are named "Apache ” missing the “(incubating)" in the NOTICE 
file.
- What is the correct way to handle non ASF Apache license software? Currently 
policy (AFAIK) is not to add to LICENSE but not an error if you do so. What 
advice should we give to podlings here?

I think some of these issues are likely to occur from copy and paste from other 
projects files. Would it make sense when creating new source repos to add 
boiler plate LICENSE, NOTICE and DISCLAIMER files?

Anyone have any other views / opionions / insights based on the above data?

Now I don’t want to look at a LICENSE or NOTICE file for a week or so and need 
a stiff drink.

Thanks,
Justin

PS If anyone is interested in the simple scripts/process to get those numbers 
just ask offline. I used grep, wc and sort a fair bit to narrow down which 
files to look at.
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
For additional commands, e-mail: general-h...@incubator.apache.org

Re: [VOTE] Release Apache Geode (incubating) 1.0.0-incubating.M1

[Anthony Baker]

Hi John,

Thanks for testing it out and reporting the test failure.  The error is not 
expected based on previous testing but it’s great to get results from different 
environments.  You don’t happen to have an entry for 
‘badhostname.badcompany.bad’ in /etc/hosts by chance?  The test is expecting a 
hostname lookup to fail…and it succeeded.  We'll investigate this further.

If you want to skip test execution entirely, run the build as:
`gradle build -Dskip.tests=true`

Thanks,
Anthony


> On Feb 3, 2016, at 7:18 PM, John D. Ament  wrote:
> 
> +0 for now but if someone wants to give some tips I'd be happy to change to
> a +1
> 
> Everything checks out, but when building the source package, it fails here
> 
> :gemfire-core:test
> 
> 
> com.gemstone.gemfire.distributed.LocatorLauncherJUnitTest >
> testSetBindAddressToUnknownHost FAILED
> 
>java.lang.AssertionError: Expected exception:
> java.lang.IllegalArgumentException
> 
> 
> com.gemstone.gemfire.distributed.ServerLauncherJUnitTest >
> testSetServerBindAddressToUnknownHost FAILED
> 
>java.lang.AssertionError: Expected exception:
> java.lang.IllegalArgumentException
> 
> *> Building 60% > :gemfire-core:test > 1382 tests completed, 2 failed, 31
> skipped*
> 
> 
> Not sure if there's something to do about these 2 tests.
> 
> 
> John
> 
> On Tue, Feb 2, 2016 at 8:32 PM Anthony Baker  wrote:
> 
>> Hello,
>> 
>> This is a call for a vote on the Apache Geode (incubating) release
>> 1.0.0-incubating.M1.
>> 
>> This release candidate, 1.0.0-incubating.M1.RC2, has successfully passed a
>> vote for a release on the geode developer mailing list.
>> 
>> Vote thread:
>> 
>> http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201601.mbox/%3cby2pr10mb0615e804a4f4c0c9d4606339b6...@by2pr10mb0615.namprd10.prod.outlook.com%3e
>> 
>> Results:
>> 
>> http://mail-archives.apache.org/mod_mbox/incubator-geode-dev/201602.mbox/%3c09e32fc5-6691-4f88-a75b-5ef8efdfe...@pivotal.io%3e
>> 
>> It fixes the following issues:
>> 
>> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12318420=12334248
>> 
>> Compared to first release candidate (RC1), it fixes the following issues:
>> [GEODE-610] - Review Geode's LICENSE & NOTICE File(s)
>> [GEODE-769] - improve README.md file
>> [GEODE-815] - RC Feedback: Fix LICENSE and NOTICE files
>> 
>> Release candidate tag:
>> rel/1.0.0-incubating.M1.RC2
>> 
>> https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;a=tag;h=refs/tags/rel/v1.0.0-incubating.M1.RC2
>> 
>> Commit ID: c26334542fa9e90daff5f58467d6e174b3e0f3e2
>> 
>> https://git-wip-us.apache.org/repos/asf?p=incubator-geode.git;a=commit;h=c26334542fa9e90daff5f58467d6e174b3e0f3e2
>> 
>> Source and binary files:
>> 
>> https://dist.apache.org/repos/dist/dev/incubator/geode/1.0.0-incubating.M1.RC2/
>> 
>> Maven staging repo:
>> https://repository.apache.org/content/repositories/orgapachegeode-1001/
>> 
>> Geode's KEYS file containing PGP keys we use to sign the release:
>> 
>> https://github.com/apache/incubator-geode/blob/release/1.0.0-incubating.M1/KEYS
>> 
>> Release Key: pub  4096R/C72CFB64 2015-10-01
>> Fingerprint: 948E 8234 14BE 693A 7F74  ABBE 19DB CAEE C72C FB64
>> 
>> Please vote on releasing this package as Apache Geode 1.0.0-incubating.M1:
>> 
>> This vote will be open for 72 hours.
>> 
>> [ ] +1 approve
>> [ ] +0 no opinion
>> [ ] -1 disapprove (and reason why)
>> 
>> Anthony on behalf of the Apache Geode (incubating) team
>> 
>> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: New ASF visual identity

[Gregory Chase]

Saw it in action at FOSDEM - looks great.  However, the old style is now a
collector's item :)

-Greg

On Wed, Feb 3, 2016 at 11:27 PM, Sergio Fernández  wrote:

> +1
>
> On Wed, Feb 3, 2016 at 8:40 PM, Sravya Tirukkovalur 
> wrote:
>
> > +1
> >
> > On Wed, Feb 3, 2016 at 10:51 AM,  wrote:
> >
> > >
> > >
> > > +1
> > >
> > >
> > > Best,
> > >
> > >
> > > Markus
> > >
> > >
> > > .:: YAGNI likes a DRY KISS ::.
> > >
> > >
> > >
> > >
> > >
> > >
> > > On Wed, Feb 3, 2016 at 10:07 AM -0800, "Marvin Humphrey" <
> > > mar...@rectangular.com> wrote:
> > >
> > >
> > >
> > >
> > >
> > > Greets,
> > >
> > > The ASF has a new look:
> > >
> > >
> > >
> >
> https://blogs.apache.org/foundation/entry/the_apache_software_foundation_announces86
> > > https://www.apache.org/foundation/press/kit/
> > >
> > > The main Incubator website needs to be updated with the new visual
> > > identity, as do podling websites.
> > >
> > > I volunteer to create a drop-in replacement for the egg logo:
> > >
> > > http://incubator.apache.org/images/egg-logo.png
> > >
> > > I expect to take the same approach as the last time the graphic was
> > > updated a few years back[1]: keep the black border and keep the same
> > > pixel dimensions, so that existing podling web pages can simply switch
> > > in the new file without needing to adapt their designs.
> > >
> > > Please note: the intent of this undertaking is to keep the Incubator up
> > > to date and in sync with the efforts of our marketing team. It is not
> > > to rework the Incubator's visual identity, so I hope that we can avoid
> a
> > > lengthy bikeshed painting debate.
> > >
> > > Marvin Humphrey
> > >
> > > [1] https://issues.apache.org/jira/browse/INCUBATOR-112
> > >
> > > -
> > > To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> > > For additional commands, e-mail: general-h...@incubator.apache.org
> > >
> > >
> >
> >
> > --
> > Sravya Tirukkovalur
> >
>
>
>
> --
> Sergio Fernández
> Partner Technology Manager
> Redlink GmbH
> m: +43 6602747925
> e: sergio.fernan...@redlink.co
> w: http://redlink.co
>



-- 
Greg Chase

Director of Big Data Communities
http://www.pivotal.io/big-data

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

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

New ASF visual identity

[Marvin Humphrey]

Greets,

The ASF has a new look:

https://blogs.apache.org/foundation/entry/the_apache_software_foundation_announces86
https://www.apache.org/foundation/press/kit/

The main Incubator website needs to be updated with the new visual
identity, as do podling websites.

I volunteer to create a drop-in replacement for the egg logo:

http://incubator.apache.org/images/egg-logo.png

I expect to take the same approach as the last time the graphic was
updated a few years back[1]: keep the black border and keep the same
pixel dimensions, so that existing podling web pages can simply switch
in the new file without needing to adapt their designs.

Please note: the intent of this undertaking is to keep the Incubator up
to date and in sync with the efforts of our marketing team. It is not
to rework the Incubator's visual identity, so I hope that we can avoid a
lengthy bikeshed painting debate.

Marvin Humphrey

[1] https://issues.apache.org/jira/browse/INCUBATOR-112

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

Re: [VOTE] Release Apache Geode (incubating) 1.0.0-incubating.M1

[Anthony Baker]

Justin,

Thanks for the great feedback!

Regarding the NOTICE in the binary distribution:  the contents came directly 
from NOTICE files contained in bundled dependencies included in the 
distribution.  I’m sure I don’t completely understand the requirements yet [1] 
so thanks for any clarification you can provide.  I’ve included links below to 
a few representative cases.

NOTICE contains copyright, commons-io [2]
NOTICE contains copyright and a few other declarations, log4j2 [3]
NOTICE contains LOTS of stuff, lucene [4]

Would it help to clearly delineate boundaries within the NOTICE file?  For 
example:

// --
// NOTICE file corresponding to the section 4d of The Apache License,
// Version 2.0, in this case for Lucene
// --

Anthony

[1] 
http://mail-archives.apache.org/mod_mbox/incubator-general/201601.mbox/%3cCADY20s5nLc9zLKoNYf_8W8vf+Q6ri=-utanuaxzgorbysxw...@mail.gmail.com%3e
[2] https://svn.apache.org/repos/asf/commons/proper/io/trunk/NOTICE.txt
[3] 
https://git-wip-us.apache.org/repos/asf?p=logging-log4j2.git;a=blob;f=NOTICE.txt;h=0f7d00604ec9722a7f1e394c49b94caead89a0d1;hb=HEAD
[4] 
https://git-wip-us.apache.org/repos/asf?p=lucene-solr.git;a=blob;f=lucene/NOTICE.txt;h=ecf08201a5ee634b9d149f18c6d2d2a9ed3334b0;hb=HEAD


> On Feb 2, 2016, at 10:15 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> From a very quick look at the binary release the LICENSE / NOTICE needs some 
> work.
> 
> The NOTICE contains a lot of what should go in LICENSE. Normally there is no 
> need to list  MIT, BSD [1] or Apache [2] license software in NOTICE.
> 
> Thanks,
> Justin
> 
> 1. http://www.apache.org/dev/licensing-howto.html#permissive-deps
> 2. http://www.apache.org/dev/licensing-howto.html#alv2-dep
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
> 



signature.asc
Description: Message signed with OpenPGP using GPGMail

Re: [VOTE] Accept Guacamole into the Apache incubator

[Daniel Gruno]

And my axe!..I mean, +1 (binding)!

With regards,
Daniel.

On 02/03/2016 06:38 PM, Jean-Baptiste Onofré wrote:
> Of course my +1 (binding) ;)
> 
> Regards
> JB
> 
> On 02/02/2016 04:05 PM, Jean-Baptiste Onofré wrote:
>> Hi,
>>
>> The Guacamole proposal was discussed couple of weeks ago.
>>
>> The complete discussion thread is available here:
>>
>> http://mail-archives.apache.org/mod_mbox/incubator-general/201601.mbox/%3c56a5c8c3.7070...@guac-dev.org%3E
>>
>>
>>
>> As reminder the GuacamoleProposal is here:
>>
>> https://wiki.apache.org/incubator/GuacamoleProposal
>>
>> As we received only positive feedbacks in the discussion thread, we
>> think it's time to call for a vote to accept Guacamole into the
>> Incubator.
>>
>> Please cast your vote to:
>> [] +1 - accept Apache Guacamole as a new incubating project
>> []  0 - not sure
>> [] -1 - do not accept the Apache Guacamole project (because: ...)
>>
>> Thanks,
>> Regards
>> JB
>>
>> 
>> = GuacamoleProposal =
>>
>> == Abstract ==
>>
>> Guacamole is an enterprise-grade, protocol-agnostic, remote desktop
>> gateway. Combined with cloud hosting, Guacamole provides an excellent
>> alternative to traditional desktops. Guacamole aims to make cloud-hosted
>> desktop access preferable to traditional, local access.
>>
>> == Background ==
>>
>> Guacamole began in 2010 as a personal project - a means for Mike Jumper
>> to access to his own computer from work. Mike’s job at that time had a
>> firewall which blocked outbound access to everything except HTTP and
>> HTTPS, and directly circumventing the firewall (by changing the SSH
>> server port, for example) was a fireable offense. Mike needed a solution
>> which provided remote access and yet was a true web application. He
>> found several projects providing text-based terminal access, but decided
>> that he wanted to make something new and different.
>>
>> The project began as a simple VNC client but grew rapidly in capability
>> and performance until it became an enterprise-grade, protocol-agnostic,
>> remote desktop gateway supporting both VNC and RDP. Support for SSH was
>> added later, followed by audio, file transfer, etc. By this point,
>> Guacamole was fast and stable enough to be used daily and in place of a
>> traditional desktop.
>>
>> Having used and developed Guacamole to its current state, and having
>> observed the general shift of the industry toward cloud computing and
>> related technologies, we now see Guacamole as the primary and only
>> viable open source solution for a future of cloud-hosted desktops.
>>
>> Guacamole's purpose is twofold:
>>
>>   * To provide seamless and performant access to desktops over the web.
>>   * To provide an API which allows others, including commercial
>> entities, to integrate Guacamole's core into their own applications.
>>
>> We believe that the lifestyle enabled by Guacamole should be preferable
>> to traditional, physically-anchored desktops, that the software enabling
>> this should be 100% free in every sense of the word, and that users
>> should not be limited by their current location, by the software
>> installed on whatever computer they are using at the moment, nor by how
>> powerful/weak the hardware of that computer happens to be.
>>
>> Guacamole is stable and production-ready. It is in active production use
>> by several companies, including ESI, Glyptodon, HP, Nanocloud Software,
>> as well as individuals.
>>
>> == Rationale ==
>>
>> Due to the utility and popularity of cloud platforms, a logical
>> extension to traditional application hosting is to host complete
>> desktops. The Guacamole project is aimed at achieving this, and we
>> believe that the best way to fulfill the true potential of this project
>> is to bring its development within Apache and, by so doing, foster a
>> larger community and higher visibility. The resulting continuous
>> improvements to its design and implementation will make Guacamole the
>> best tool for the job for a wide variety of use cases.
>>
>> == Initial Goals ==
>>
>> Our initial goals are to bring Guacamole into the ASF, transition
>> internal engineering processes into the open, and foster a collaborative
>> development model according to the "Apache Way."
>>
>> == Current Status ==
>>
>> Guacamole is production-ready and already provides a large set of
>> features. It is currently licensed under the MIT license, but will be
>> relicensed under the Apache license if accepted for incubation.
>>
>> The source repositories are:
>>
>>   * https://github.com/glyptodon/guacamole-server
>>   * https://github.com/glyptodon/guacamole-client
>>
>> == Meritocracy ==
>>
>> We intend to radically expand the initial developer and user community
>> by running the project in accordance with the "Apache Way". Users and
>> new contributors will be treated with respect and welcomed. By
>> participating in the community and providing quality patches/support
>> that move the project forward, they will earn merit. The community will

Re: [VOTE] Release Apache Geode (incubating) 1.0.0-incubating.M1

[Anthony Baker]

Hi Justin,

As I mentioned in my other response, thanks for the great feedback and quick 
turnaround!  I filed JIRA’s based on the issues you noted below.

Anthony

> On Feb 2, 2016, at 10:06 PM, Justin Mclean  wrote:
> 
> Hi,
> 
> +0.5 for the license issues and unable to compile. Willing to change to +1 if 
> these are sorted in the next release/explained.
> 
> I checked:
> - file name contain incubating
> - signatures and hashes good
> - DISCLAIMER exists
> - NOTICE looks OK
> - LICENSE is missing a few items (see below). Everything listed in bundled.
> - All source files have Apache headers (that need it)
> - No unexpected binary in the source release
> - I think COMPILING.txt needs some updating and current gradle fails with an 
> error (see below)
> 
> License is missing:
> - ANSIBuffer (BSD) [1]
> - font awesome (front are SIL and css is MIT) [2]
> - normalise.css (MIT) [3]
> - bootstrap (MIT) [3]
> - boot flat (MIT) [4]
> - headjs (MIT) [5]
> - iCheck (MIT) [6]
> - html5shiv (MIT) [7]
> - respond (MIT) [8]
> - polyfill (MIT/BSD) [8]
> - InternalDataSerializer.java [9] contains code from BSD license protobuf 
> that should be in license
> 

[GEODE-904] Yes, these dependencies need to be called out.

> Compile fails with:
> Could not GET 
> 'https://plugins.gradle.org/m2/com/github/zafarkhaja/java-semver/0.9.0/java-semver-0.9.0.pom'.
>  Received status code 502 from server: Bad Gateway
> 

That’s odd.  When gradle resolves the plugin for me it’s downloading from 
https://plugins.gradle.org/m2/com/github/zafarkhaja/java-semver/0.9.0/java-semver-0.9.0.jar
 (this is a transitive dependency of the grgit plugin).  We’ll look into this 
to understand why it’s not resolving propertly.

> It is unclear how [10] was original licensed has an apache header been put on 
> this file by mistake? It contains:
> //  Created by Eric Zoerner on 2/13/08.
> //  Copyright 2008 __MyCompanyName__. All rights reserved.
> 

[GEODE-901] This file should have an Apache header.  The original copyright 
information looks like an auto generated template that should have been removed 
when Pivotal donated the code to ASF.

> Do you have permission to use this file [11] which contains ("All Rights 
> Reserved" generally implies no).
> Copyright (C) GemStone Systems, Inc. 2000-2004. All Rights Reserved.
> 

[GEODE-901] Same as above, this comment should be removed.  The source code 
history is GemStone -> VMWare -> Pivotal -> ASF :-)

> This file [12] incorrectly has an Apache header and is licensed under an MX4J 
> license [13]. While is permissive, it’s not "Apache like" as claimed. The is 
> not list as a category A license [14] so you probably need to raise a legal 
> JIRA to get it added. It looks to me like it requires attribution and would 
> need to be listed in LICENSE.
> 

[GEODE-902] Agreed, we will investigate this.

> Many java files under [15] contain double headers is this correct?
> 

[GEODE-905] Agreed, we need to preserve the original header and determine if we 
have to add anything to the source LICENSE or NOTICE.

> Also this file [16] has a double header but this file [17] only has one 
> header with the same (non Apache) copyright owner and an non standard Apache 
> header. This may need to be mentioned in NOTICE? [18]
> 

[GEODE-906] We will cleanup this up.

> BTW the footer [19] conatins the wrong copyright year.
> 

[GEODE-903] Yep.

> Several items in LICENSE refer to the generic BSD/MIT license, wouldn’t it be 
> more useful to point to the actual software license in question?
> 
> I didn't look at the binary release and there may be a couple of things I’ve 
> missed from a quick review.
> 
> Thanks,
> Justin
> 
> 1. 
> ./gemfire-core/src/main/java/com/gemstone/gemfire/management/internal/cli/shell/jline/ANSIBuffer.java
> 2. ./gemfire-site/website/content/font/*
> 3. ./gemfire-site/website/content/bootstrap/bootstrap.min.css
> 4. ./gemfire-site/website/content/css/bootflat*
> 5. ./gemfire-site/website/content/js/head.js
> 6. ./gemfire-site/website/content/js/jquery.icheck.js
> 7. ./gemfire-site/website/content/js/html5shiv.js
> 8. ./gemfire-site/website/content/js/respond.min.js
> 9 
> ./gemfire-core/src/main/java/com/gemstone/gemfire/internal/InternalDataSerializer.java
> 10. 
> ./gemfire-core/src/test/java/com/gemstone/gemfire/cache/query/internal/ResultsBagJUnitTest.java
> 11. 
> ./gemfire-core/src/test/java/com/gemstone/gemfire/cache/query/internal/QueryFromClauseCanonicalizationJUnitTest.java
> 12. 
> ./gemfire-core/src/main/java/com/gemstone/gemfire/admin/jmx/internal/MX4JModelMBean.java
> 13. http://mx4j.sourceforge.net/docs/ch01s06.html
> 14. http://www.apache.org/legal/resolved.html#category-a
> 15. 
> ./gemfire-core/src/main/java/com/gemstone/gemfire/internal/redis/executor/hll/*.java
> 16. 
> ./gemfire-core/src/main/java/com/gemstone/gemfire/cache/query/internal/index/HashIndexSet.java
> 17. 
> 

Re: New ASF visual identity

[Sravya Tirukkovalur]

+1

On Wed, Feb 3, 2016 at 10:51 AM,  wrote:

>
>
> +1
>
>
> Best,
>
>
> Markus
>
>
> .:: YAGNI likes a DRY KISS ::.
>
>
>
>
>
>
> On Wed, Feb 3, 2016 at 10:07 AM -0800, "Marvin Humphrey" <
> mar...@rectangular.com> wrote:
>
>
>
>
>
> Greets,
>
> The ASF has a new look:
>
>
> https://blogs.apache.org/foundation/entry/the_apache_software_foundation_announces86
> https://www.apache.org/foundation/press/kit/
>
> The main Incubator website needs to be updated with the new visual
> identity, as do podling websites.
>
> I volunteer to create a drop-in replacement for the egg logo:
>
> http://incubator.apache.org/images/egg-logo.png
>
> I expect to take the same approach as the last time the graphic was
> updated a few years back[1]: keep the black border and keep the same
> pixel dimensions, so that existing podling web pages can simply switch
> in the new file without needing to adapt their designs.
>
> Please note: the intent of this undertaking is to keep the Incubator up
> to date and in sync with the efforts of our marketing team. It is not
> to rework the Incubator's visual identity, so I hope that we can avoid a
> lengthy bikeshed painting debate.
>
> Marvin Humphrey
>
> [1] https://issues.apache.org/jira/browse/INCUBATOR-112
>
> -
> To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
> For additional commands, e-mail: general-h...@incubator.apache.org
>
>


-- 
Sravya Tirukkovalur

Ideas regarding System and network programming projects

[Gaurav Shukla]

Hi all,

I am a student of an engineering college in India.This year in my college
we have the option to work on any open source project for credits. Each
group of students(3-4) would have 4 months to work on it and the project
should be using network programming or networking.

With GSOC around the corner and one of my group mate and me willing to
apply for it, I would like to know if there are any project ideas or
podlings working on projects that fulfil above criteria.

I have some experience contributing to open source software and all of us
have above average programming knowledge. Some of the ideas given by our
faculty are listed below, please refer to them and suggest accordingly.

1. Network or pseudo-device device drivers. [C/C++ allowed]
2. Security issues targeting cloud computing and grid computing.
3. Any new module for kernel enhancement. [C/C++ allowed]
4. Designing and development of testing and debugging toolkit for device
drivers. [C/C++ allowed]
5. Performance analysis of inter process communication methods using user
application.
6. Mobile applications in Python.
7. Power dissipation in mobiles.
8. Security issues in Virtualized data center.
9. Multiplayer Game.


-- 
Regards !
Gaurav Shukla

Re: [VOTE] Accept Guacamole into the Apache incubator

[Jean-Baptiste Onofré]

Of course my +1 (binding) ;)

Regards
JB

On 02/02/2016 04:05 PM, Jean-Baptiste Onofré wrote:

Hi,

The Guacamole proposal was discussed couple of weeks ago.

The complete discussion thread is available here:

http://mail-archives.apache.org/mod_mbox/incubator-general/201601.mbox/%3c56a5c8c3.7070...@guac-dev.org%3E


As reminder the GuacamoleProposal is here:

https://wiki.apache.org/incubator/GuacamoleProposal

As we received only positive feedbacks in the discussion thread, we
think it's time to call for a vote to accept Guacamole into the Incubator.

Please cast your vote to:
[] +1 - accept Apache Guacamole as a new incubating project
[]  0 - not sure
[] -1 - do not accept the Apache Guacamole project (because: ...)

Thanks,
Regards
JB


= GuacamoleProposal =

== Abstract ==

Guacamole is an enterprise-grade, protocol-agnostic, remote desktop
gateway. Combined with cloud hosting, Guacamole provides an excellent
alternative to traditional desktops. Guacamole aims to make cloud-hosted
desktop access preferable to traditional, local access.

== Background ==

Guacamole began in 2010 as a personal project - a means for Mike Jumper
to access to his own computer from work. Mike’s job at that time had a
firewall which blocked outbound access to everything except HTTP and
HTTPS, and directly circumventing the firewall (by changing the SSH
server port, for example) was a fireable offense. Mike needed a solution
which provided remote access and yet was a true web application. He
found several projects providing text-based terminal access, but decided
that he wanted to make something new and different.

The project began as a simple VNC client but grew rapidly in capability
and performance until it became an enterprise-grade, protocol-agnostic,
remote desktop gateway supporting both VNC and RDP. Support for SSH was
added later, followed by audio, file transfer, etc. By this point,
Guacamole was fast and stable enough to be used daily and in place of a
traditional desktop.

Having used and developed Guacamole to its current state, and having
observed the general shift of the industry toward cloud computing and
related technologies, we now see Guacamole as the primary and only
viable open source solution for a future of cloud-hosted desktops.

Guacamole's purpose is twofold:

  * To provide seamless and performant access to desktops over the web.
  * To provide an API which allows others, including commercial
entities, to integrate Guacamole's core into their own applications.

We believe that the lifestyle enabled by Guacamole should be preferable
to traditional, physically-anchored desktops, that the software enabling
this should be 100% free in every sense of the word, and that users
should not be limited by their current location, by the software
installed on whatever computer they are using at the moment, nor by how
powerful/weak the hardware of that computer happens to be.

Guacamole is stable and production-ready. It is in active production use
by several companies, including ESI, Glyptodon, HP, Nanocloud Software,
as well as individuals.

== Rationale ==

Due to the utility and popularity of cloud platforms, a logical
extension to traditional application hosting is to host complete
desktops. The Guacamole project is aimed at achieving this, and we
believe that the best way to fulfill the true potential of this project
is to bring its development within Apache and, by so doing, foster a
larger community and higher visibility. The resulting continuous
improvements to its design and implementation will make Guacamole the
best tool for the job for a wide variety of use cases.

== Initial Goals ==

Our initial goals are to bring Guacamole into the ASF, transition
internal engineering processes into the open, and foster a collaborative
development model according to the "Apache Way."

== Current Status ==

Guacamole is production-ready and already provides a large set of
features. It is currently licensed under the MIT license, but will be
relicensed under the Apache license if accepted for incubation.

The source repositories are:

  * https://github.com/glyptodon/guacamole-server
  * https://github.com/glyptodon/guacamole-client

== Meritocracy ==

We intend to radically expand the initial developer and user community
by running the project in accordance with the "Apache Way". Users and
new contributors will be treated with respect and welcomed. By
participating in the community and providing quality patches/support
that move the project forward, they will earn merit. The community will
also be encouraged to provide non-code contributions (documentation,
events, community management, etc.) and will gain merit for doing so.
Those with a proven support and quality track record will be encouraged
to become committers.

== Community ==

If Guacamole is accepted for incubation, its primary initial goal will
be to build a large community of users and developers. We trust that
Guacamole will become a key project 

Re: New ASF visual identity

[markus.geiss]

+1


Best,


Markus


.:: YAGNI likes a DRY KISS ::.






On Wed, Feb 3, 2016 at 10:07 AM -0800, "Marvin Humphrey" 
 wrote:





Greets,

The ASF has a new look:

https://blogs.apache.org/foundation/entry/the_apache_software_foundation_announces86
https://www.apache.org/foundation/press/kit/

The main Incubator website needs to be updated with the new visual
identity, as do podling websites.

I volunteer to create a drop-in replacement for the egg logo:

http://incubator.apache.org/images/egg-logo.png

I expect to take the same approach as the last time the graphic was
updated a few years back[1]: keep the black border and keep the same
pixel dimensions, so that existing podling web pages can simply switch
in the new file without needing to adapt their designs.

Please note: the intent of this undertaking is to keep the Incubator up
to date and in sync with the efforts of our marketing team. It is not
to rework the Incubator's visual identity, so I hope that we can avoid a
lengthy bikeshed painting debate.

Marvin Humphrey

[1] https://issues.apache.org/jira/browse/INCUBATOR-112

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