groovy-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Laforge <>
Subject Re: Groovy Champions proposal feedback
Date Mon, 26 Feb 2018 08:06:28 GMT
The Groovy Star / Champion is an award beyond Apache Groovy itself, and
spans plenty other projects that can be quite remote from Groovy, apart
from the fact they do use Groovy.
So those stars/champions should span also the wider ecosystem, even if they
haven't contributed otherwise in any way to the Groovy project itself
(code, documentation, promotion, bug reports, help on the lists, etc.)
My sentiment is that committer and PMC membership are for those who
contribute directly to the Apache Groovy project itself (even if not in
code form).
But to please the board, since the award bears the name of Apache Groovy,
and even if its the champions themselves who elect new members, we should
give the PMC a special vote, like a veto capability, to say yes or no, the
PMC is happy to have this person get that Groovy award.

On Mon, Feb 26, 2018 at 9:00 AM, Cédric Champeau <>

> It feels like everybody agrees this is a good idea, but somethings hasn't
> been discussed so far: the Foundation already has 2 ways of recognizing
> members of the community:
> 1. by making them "committers"
> 2. by making them members of the PMC
> If Groovy Champions is going to be different, we need a good explanation
> why it doesn't fit in those 2 categories. Especially to give to the Board.
> I have my ideas why, but I'd like to hear what others say.
> 2018-02-26 8:55 GMT+01:00 Søren Berg Glasius <>:
>> @Mario
>> Very good thoughts, I really like the idea that an award is permanent, I
>> believe that goes for Java Champs as well.
>> Naming wise, Groovyssimo is fun, but not naming material for an award :-)
>> But we need to narrow down the name-space to something realistic that can
>> be voted on.
>> On Mon, 26 Feb 2018 at 08:50 Mario Garcia <> wrote:
>>> +1 to what Guillaume said :) Common guys! Lets focus on what we think is
>>> a great language and let others think what they want!
>>> Regarding the duration of the award. I've though about it, trying not to
>>> think in terms of annually or permanent, but trying to see what's out there
>>> outside the CS world, and I ended up thinking on the Nobel prize. I'd like
>>> some ideas of Nobel prize:
>>>    - Takes place every year
>>>    - A given prize could be vacant a given year.
>>>    - It's so important that it's really noticeable to be awarded
>>>    - Makes people very proud of some achievement they did a given year
>>>    - Once you're a Nobel you will always be a Nobel.
>>>    - Of  course there's been awarded people that even rejected the
>>>    prize but that never really underrated the prize overtime
>>>    - New members are chosen by previous members and some other relevant
>>>    people (members of the parliament among others). Here I'd add the
>>>    idea of letting anybody to propose a nominee, but leaving the final
>>>    decision to the prize committee (whatever we decide who is in)
>>> Despite the difference of content between the Nobel prize and the Groovy
>>> awards, after reviewing these points I think they seem to fit better in the
>>> Groovy Champions/Stars idea. There is also something I haven't heard yet. I
>>> guess this will require a kind of permanent organization, e.g. to contact
>>> members, nominees, organize the awards, a web to show the winners...etc
>>> BTW: Here you have another naming for the awards: Groovisimo Awards. Can
>>> you imaging a "Groovisimo" statue like the Oscars ? It would be a blast
>>> My two cents
>>> Mario
>>> 2018-02-25 10:53 GMT+01:00 Guillaume Laforge <>:
>>>> James Stachan's quote has really been taken out of context, and
>>>> over-exagerated bu the Scala-fanboys.
>>>> If Scala had been what it is now, James would probably not have
>>>> initiated Groovy *then*. But Scala was nascent just like Groovy *then*.
>>>> It's like if Gavin King had said that he wouldn't have invented
>>>> Hibernate if JPA had existed... but JPA came ten years later.
>>>> This quote was really harmful, but as the saying goes, lots of water's
>>>> gone through the bridges since then.
>>>> There's still the myth of slowliness, which we all know is not true
>>>> anymore, even in pure dynamic mode (without even mentioning static
>>>> compilation)
>>>> Usually, you spend way more time in network latency (access to remote
>>>> resources, access to database, etc) than waiting for the CPU spent by just
>>>> the pure language execution time.
>>>> Also back on James Strachan: he went to play with Scala, then with
>>>> Kotlin, and has come back to using Groovy.
>>>> He's using Groovy on a regular basis through his work with Jenkins, its
>>>> pipelines, etc.
>>>> So he's back at his old love!
>>>> So let's turn the page on those stories, please.
>>>> Guillaume
>>>> On Sun, Feb 25, 2018 at 10:26 AM, Daniel Sun <>
>>>> wrote:
>>>>> The creator of Groovy said "I can honestly say if someone had shown me
>>>>> the
>>>>> Programming in Scala book...". I think he compared Scala with the old
>>>>> version of Groovy he created in about 2003. As we all know, Groovy has
>>>>> evolved a lot, so I never care about others' out-dated opinions on
>>>>> Groovy :)
>>>>> Cheers,
>>>>> Daniel.Sun
>>>>> --
>>>>> Sent from: http://groovy.329449.n5.nabble
>>>>> .com/Groovy-Users-f329450.html
>>>> --
>>>> Guillaume Laforge
>>>> Apache Groovy committer & PMC Vice-President
>>>> Developer Advocate @ Google Cloud Platform
>>>> Blog:
>>>> Social: @glaforge <> / Google+
>>>> <>
>>> --
>> Best regards / Med venlig hilsen,
>> Søren Berg Glasius
>> Hedevej 1, Gl. Rye, 8680 Ry, Denmark
>> Mobile: +45 40 44 91 88 <+45%2040%2044%2091%2088>, Skype: sbglasius
>> --- Press ESC once to quit - twice to save the changes.

Guillaume Laforge
Apache Groovy committer & PMC Vice-President
Developer Advocate @ Google Cloud Platform

Social: @glaforge <> / Google+

View raw message