Re: Groovy Champions proposal feedback

[Sergio Del Amo]

t;>> Have a gr8 day
>>> 
>>> 
>>> Best regards / Med venlig hilsen,
>>> Søren Berg Glasius
>>> 
>>> Hedevej 1, Gl. Rye, 8680 Ry, Denmark
>>> Mobile: +45 40 44 91 88, Skype: sbglasius
>>> --- Press ESC once to quit - twice to save the changes.
>>> 
>>> 
>>>> On Wed, 8 May 2019 at 23:44, Paul King  wrote:
>>>> Yes, I think that is the way to go. The Apache Groovy project recognizes 
>>>> contributors to the project through making them committers and/or PMC 
>>>> members. The Groovy Star awards were always proposed to be about the   
>>>>   whole community. That sits better with Friends-of-Groovy in my mind 
>>>> which also has a whole community brief.
>>>> 
>>>> Cheers, Paul.
>>>> 
>>>>> On Thu, May 9, 2019 at 12:55 AM Milles, Eric (TR Tech, Content & Ops) 
>>>>>  wrote:
>>>>> Can the open collective team recognize significant achievements in the 
>>>>> community and make awards?  You could announce one award per major 
>>>>> conference (Gr8conf, Greach, Whatever2gm).
>>>>> 
>>>>> From: Søren Berg Glasius 
>>>>> Sent: Wednesday, May 8, 2019 9:50 AM
>>>>> To: dev@groovy.apache.org
>>>>> Cc: Jochen Theodorou
>>>>> Subject: Re: Groovy Champions proposal feedback
>>>>>  
>>>>> How can we revive this discussion? I still think it's relevant.
>>>>> 
>>>>> :)
>>>>> 
>>>>> Best regards / Med venlig hilsen,
>>>>> Søren Berg Glasius
>>>>> 
>>>>> Hedevej 1, Gl. Rye, 8680 Ry, Denmark
>>>>> Mobile: +45 40 44 91 88, Skype: sbglasius
>>>>> --- Press ESC once to quit - twice to save the changes.
>>>>> 
>>>>> 
>>>>> On Fri, 2 Mar 2018 at 17:40, MG  wrote:
>>>>> ...and, of course, the
>>>>> 
>>>>> Apache Groovy Community Lifetime Achievement Award
>>>>> 
>>>>> ;-)
>>>>> 
>>>>> Like the name, +1 (again) on tying the award to a specific year, don't 
>>>>> think that mixing commit access with the award makes sense (as in 
>>>>> programming: Keep things single purpose - nobdy wants to be fat, be it 
>>>>> class or human ;-) )
>>>>> 
>>>>> 
>>>>> On 02.03.2018 10:11, Jochen Theodorou wrote:
>>>>> > hi all,
>>>>> >
>>>>> > I was thinking a while about all this and all the problems involved 
>>>>> > here and I want to show an alternative.
>>>>> >
>>>>> > Apache Groovy Community Award
>>>>> >
>>>>> > Name surely to be changed. The idea is to give a nominal award for 
>>>>> > what they did in the past. Somebody getting this award will get this 
>>>>> > for a reason, which is to be stated.
>>>>> >
>>>>> > Since it is no title like "champion" and since we can give a 
>>>>> > description of the reasons the award will be always specific, it is 
>>>>> > not a title you carry around your lifetime and all of that. Maybe a 
>>>>> > person could be awarded multiple times, but that is then to decide. 
>>>>> > That means there will be no discussions about revoking the 
>>>>> > championship, or for how long this is granted. Also I think the award 
>>>>> > leaves better space for a good naming. Also we can give commit access 
>>>>> > along with it, which may or may not be taken, but then includes the 
>>>>> > official ASF way of recognizing people.
>>>>> >
>>>>> > what do you guys think?
>>>>> >
>>>>> > bye Jochen
>>>>> >
>>>>> 
>> 

Re: Groovy Champions proposal feedback

[Andres Almiray]

Groovy Star awards were always proposed to be about the whole 
>>> community. That sits better with Friends-of-Groovy in my mind which also 
>>> has a whole community brief.
>>> 
>>> Cheers, Paul.
>>> 
>>>> On Thu, May 9, 2019 at 12:55 AM Milles, Eric (TR Tech, Content & Ops) 
>>>>  wrote:
>>>> Can the open collective team recognize significant achievements in the 
>>>> community and make awards?  You could announce one award per major 
>>>> conference (Gr8conf, Greach, Whatever2gm).
>>>> 
>>>>  
>>>> From: Søren Berg Glasius 
>>>> Sent: Wednesday, May 8, 2019 9:50 AM
>>>> To: dev@groovy.apache.org
>>>> Cc: Jochen Theodorou
>>>> Subject: Re: Groovy Champions proposal feedback
>>>>  
>>>> How can we revive this discussion? I still think it's relevant.
>>>> 
>>>> :)
>>>> 
>>>> Best regards / Med venlig hilsen,
>>>> Søren Berg Glasius
>>>> 
>>>> Hedevej 1, Gl. Rye, 8680 Ry, Denmark
>>>> Mobile: +45 40 44 91 88, Skype: sbglasius
>>>> --- Press ESC once to quit - twice to save the changes.
>>>> 
>>>> 
>>>> On Fri, 2 Mar 2018 at 17:40, MG  wrote:
>>>> ...and, of course, the
>>>> 
>>>> Apache Groovy Community Lifetime Achievement Award
>>>> 
>>>> ;-)
>>>> 
>>>> Like the name, +1 (again) on tying the award to a specific year, don't 
>>>> think that mixing commit access with the award makes sense (as in 
>>>> programming: Keep things single purpose - nobdy wants to be fat, be it 
>>>> class or human ;-) )
>>>> 
>>>> 
>>>> On 02.03.2018 10:11, Jochen Theodorou wrote:
>>>> > hi all,
>>>> >
>>>> > I was thinking a while about all this and all the problems involved 
>>>> > here and I want to show an alternative.
>>>> >
>>>> > Apache Groovy Community Award
>>>> >
>>>> > Name surely to be changed. The idea is to give a nominal award for 
>>>> > what they did in the past. Somebody getting this award will get this 
>>>> > for a reason, which is to be stated.
>>>> >
>>>> > Since it is no title like "champion" and since we can give a 
>>>> > description of the reasons the award will be always specific, it is 
>>>> > not a title you carry around your lifetime and all of that. Maybe a 
>>>> > person could be awarded multiple times, but that is then to decide. 
>>>> > That means there will be no discussions about revoking the 
>>>> > championship, or for how long this is granted. Also I think the award 
>>>> > leaves better space for a good naming. Also we can give commit access 
>>>> > along with it, which may or may not be taken, but then includes the 
>>>> > official ASF way of recognizing people.
>>>> >
>>>> > what do you guys think?
>>>> >
>>>> > bye Jochen
>>>> >
>>>> 
> 

Re: Groovy Champions proposal feedback

[Søren Berg Glasius]

Let me see, if I can summarize the story (from over 50 mails)

There is a general +1 (14ish) right now on making a Groovy Award, and a
majority of people who are in favor of the "Groovy Star" award name, both
because it has a nice ring to it, because it can be associated with the
Groovy logo, and because it sounds a bit like Java Rockstars.

There also seems to be a general consensus that it can be given to core
comitters, but also to people who contribute to frameworks/libraries in the
ecosystem, and to people who in other ways (community work, conference
organizers etc) makes an impact for the community.

There is a discussion, wether it should be awarded as an award for a given
year vs a lifetime archivement award. This is still something that needs to
be agreed uppon.

Besides being an honor to receive an award, it has also been suggested that
there could be a monitary reward, to be regcognized by becoming a
"comitter" or PMC member. If it is monitary the money could come from
Friends of Groovy, if that can be agreed uppon.

Awards could be announced at Groovy related conferences (GR8Conf, Greach,
devnexus2gm or others)

There need to be a discussion on how the nominees are appointed, and who
decides on who will get the award.

>From e personal point of view (and from the view of being a conference
organizer) I would love to be able to hand out an award like this. But it
seems that we're too late for GR8Conf at the end of this month.

I hope I have captured most of the discussion bullets, other wise feel free
to correct me.

Have a gr8 day


Best regards / Med venlig hilsen,
Søren Berg Glasius

Hedevej 1, Gl. Rye, 8680 Ry, Denmark
Mobile: +45 40 44 91 88, Skype: sbglasius
--- Press ESC once to quit - twice to save the changes.


On Wed, 8 May 2019 at 23:44, Paul King  wrote:

> Yes, I think that is the way to go. The Apache Groovy project recognizes
> contributors to the project through making them committers and/or PMC
> members. The Groovy Star awards were always proposed to be about the whole
> community. That sits better with Friends-of-Groovy in my mind which also
> has a whole community brief.
>
> Cheers, Paul.
>
> On Thu, May 9, 2019 at 12:55 AM Milles, Eric (TR Tech, Content & Ops) <
> eric.mil...@thomsonreuters.com> wrote:
>
>> Can the open collective team recognize significant achievements in the
>> community and make awards?  You could announce one award per major
>> conference (Gr8conf, Greach, Whatever2gm).
>>
>> --
>> *From:* Søren Berg Glasius 
>> *Sent:* Wednesday, May 8, 2019 9:50 AM
>> *To:* dev@groovy.apache.org
>> *Cc:* Jochen Theodorou
>> *Subject:* Re: Groovy Champions proposal feedback
>>
>> How can we revive this discussion? I still think it's relevant.
>>
>> :)
>>
>> Best regards / Med venlig hilsen,
>> Søren Berg Glasius
>>
>> Hedevej 1, Gl. Rye, 8680 Ry, Denmark
>> Mobile: +45 40 44 91 88, Skype: sbglasius
>> --- Press ESC once to quit - twice to save the changes.
>>
>>
>> On Fri, 2 Mar 2018 at 17:40, MG  wrote:
>>
>> ...and, of course, the
>>
>> Apache Groovy Community Lifetime Achievement Award
>>
>> ;-)
>>
>> Like the name, +1 (again) on tying the award to a specific year, don't
>> think that mixing commit access with the award makes sense (as in
>> programming: Keep things single purpose - nobdy wants to be fat, be it
>> class or human ;-) )
>>
>>
>> On 02.03.2018 10:11, Jochen Theodorou wrote:
>> > hi all,
>> >
>> > I was thinking a while about all this and all the problems involved
>> > here and I want to show an alternative.
>> >
>> > Apache Groovy Community Award
>> >
>> > Name surely to be changed. The idea is to give a nominal award for
>> > what they did in the past. Somebody getting this award will get this
>> > for a reason, which is to be stated.
>> >
>> > Since it is no title like "champion" and since we can give a
>> > description of the reasons the award will be always specific, it is
>> > not a title you carry around your lifetime and all of that. Maybe a
>> > person could be awarded multiple times, but that is then to decide.
>> > That means there will be no discussions about revoking the
>> > championship, or for how long this is granted. Also I think the award
>> > leaves better space for a good naming. Also we can give commit access
>> > along with it, which may or may not be taken, but then includes the
>> > official ASF way of recognizing people.
>> >
>> > what do you guys think?
>> >
>> > bye Jochen
>> >
>>
>>

Re: Groovy Champions proposal feedback

[Paul King]

Yes, I think that is the way to go. The Apache Groovy project recognizes
contributors to the project through making them committers and/or PMC
members. The Groovy Star awards were always proposed to be about the whole
community. That sits better with Friends-of-Groovy in my mind which also
has a whole community brief.

Cheers, Paul.

On Thu, May 9, 2019 at 12:55 AM Milles, Eric (TR Tech, Content & Ops) <
eric.mil...@thomsonreuters.com> wrote:

> Can the open collective team recognize significant achievements in the
> community and make awards?  You could announce one award per major
> conference (Gr8conf, Greach, Whatever2gm).
>
> --
> *From:* Søren Berg Glasius 
> *Sent:* Wednesday, May 8, 2019 9:50 AM
> *To:* dev@groovy.apache.org
> *Cc:* Jochen Theodorou
> *Subject:* Re: Groovy Champions proposal feedback
>
> How can we revive this discussion? I still think it's relevant.
>
> :)
>
> Best regards / Med venlig hilsen,
> Søren Berg Glasius
>
> Hedevej 1, Gl. Rye, 8680 Ry, Denmark
> Mobile: +45 40 44 91 88, Skype: sbglasius
> --- Press ESC once to quit - twice to save the changes.
>
>
> On Fri, 2 Mar 2018 at 17:40, MG  wrote:
>
> ...and, of course, the
>
> Apache Groovy Community Lifetime Achievement Award
>
> ;-)
>
> Like the name, +1 (again) on tying the award to a specific year, don't
> think that mixing commit access with the award makes sense (as in
> programming: Keep things single purpose - nobdy wants to be fat, be it
> class or human ;-) )
>
>
> On 02.03.2018 10:11, Jochen Theodorou wrote:
> > hi all,
> >
> > I was thinking a while about all this and all the problems involved
> > here and I want to show an alternative.
> >
> > Apache Groovy Community Award
> >
> > Name surely to be changed. The idea is to give a nominal award for
> > what they did in the past. Somebody getting this award will get this
> > for a reason, which is to be stated.
> >
> > Since it is no title like "champion" and since we can give a
> > description of the reasons the award will be always specific, it is
> > not a title you carry around your lifetime and all of that. Maybe a
> > person could be awarded multiple times, but that is then to decide.
> > That means there will be no discussions about revoking the
> > championship, or for how long this is granted. Also I think the award
> > leaves better space for a good naming. Also we can give commit access
> > along with it, which may or may not be taken, but then includes the
> > official ASF way of recognizing people.
> >
> > what do you guys think?
> >
> > bye Jochen
> >
>
>

Re: Groovy Champions proposal feedback

[Milles, Eric (TR Tech, Content & Ops)]

Can the open collective team recognize significant achievements in the 
community and make awards?  You could announce one award per major conference 
(Gr8conf, Greach, Whatever2gm).


From: Søren Berg Glasius 
Sent: Wednesday, May 8, 2019 9:50 AM
To: dev@groovy.apache.org
Cc: Jochen Theodorou
Subject: Re: Groovy Champions proposal feedback

How can we revive this discussion? I still think it's relevant.

:)

Best regards / Med venlig hilsen,
Søren Berg Glasius

Hedevej 1, Gl. Rye, 8680 Ry, Denmark
Mobile: +45 40 44 91 88, Skype: sbglasius
--- Press ESC once to quit - twice to save the changes.


On Fri, 2 Mar 2018 at 17:40, MG mailto:mg...@arscreat.com>> 
wrote:
...and, of course, the

Apache Groovy Community Lifetime Achievement Award

;-)

Like the name, +1 (again) on tying the award to a specific year, don't
think that mixing commit access with the award makes sense (as in
programming: Keep things single purpose - nobdy wants to be fat, be it
class or human ;-) )


On 02.03.2018 10:11, Jochen Theodorou wrote:
> hi all,
>
> I was thinking a while about all this and all the problems involved
> here and I want to show an alternative.
>
> Apache Groovy Community Award
>
> Name surely to be changed. The idea is to give a nominal award for
> what they did in the past. Somebody getting this award will get this
> for a reason, which is to be stated.
>
> Since it is no title like "champion" and since we can give a
> description of the reasons the award will be always specific, it is
> not a title you carry around your lifetime and all of that. Maybe a
> person could be awarded multiple times, but that is then to decide.
> That means there will be no discussions about revoking the
> championship, or for how long this is granted. Also I think the award
> leaves better space for a good naming. Also we can give commit access
> along with it, which may or may not be taken, but then includes the
> official ASF way of recognizing people.
>
> what do you guys think?
>
> bye Jochen
>

Re: Groovy Champions proposal feedback

[Søren Berg Glasius]

How can we revive this discussion? I still think it's relevant.

:)

Best regards / Med venlig hilsen,
Søren Berg Glasius

Hedevej 1, Gl. Rye, 8680 Ry, Denmark
Mobile: +45 40 44 91 88, Skype: sbglasius
--- Press ESC once to quit - twice to save the changes.


On Fri, 2 Mar 2018 at 17:40, MG  wrote:

> ...and, of course, the
>
> Apache Groovy Community Lifetime Achievement Award
>
> ;-)
>
> Like the name, +1 (again) on tying the award to a specific year, don't
> think that mixing commit access with the award makes sense (as in
> programming: Keep things single purpose - nobdy wants to be fat, be it
> class or human ;-) )
>
>
> On 02.03.2018 10:11, Jochen Theodorou wrote:
> > hi all,
> >
> > I was thinking a while about all this and all the problems involved
> > here and I want to show an alternative.
> >
> > Apache Groovy Community Award
> >
> > Name surely to be changed. The idea is to give a nominal award for
> > what they did in the past. Somebody getting this award will get this
> > for a reason, which is to be stated.
> >
> > Since it is no title like "champion" and since we can give a
> > description of the reasons the award will be always specific, it is
> > not a title you carry around your lifetime and all of that. Maybe a
> > person could be awarded multiple times, but that is then to decide.
> > That means there will be no discussions about revoking the
> > championship, or for how long this is granted. Also I think the award
> > leaves better space for a good naming. Also we can give commit access
> > along with it, which may or may not be taken, but then includes the
> > official ASF way of recognizing people.
> >
> > what do you guys think?
> >
> > bye Jochen
> >
>
>

Re: Groovy Champions proposal feedback

[Paolo Di Tommaso]

I this proposal +1

On Fri, Mar 2, 2018 at 10:57 AM, Daniel Sun  wrote:

> +1
>
> Maybe adding a specific year will be better, e.g. Apache Groovy Community
> Award 2018
>
> Revoking championship may make champions disappointed...
>
> Cheers,
> Daniel.Sun
>
>
>
>
> --
> Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html
>

Re: Groovy Champions proposal feedback

[Daniel Sun]

+1

Maybe adding a specific year will be better, e.g. Apache Groovy Community
Award 2018

Revoking championship may make champions disappointed...

Cheers,
Daniel.Sun




--
Sent from: http://groovy.329449.n5.nabble.com/Groovy-Dev-f372993.html

Re: Groovy Champions proposal feedback

[Jochen Theodorou]

hi all,

I was thinking a while about all this and all the problems involved here 
and I want to show an alternative.


Apache Groovy Community Award

Name surely to be changed. The idea is to give a nominal award for what 
they did in the past. Somebody getting this award will get this for a 
reason, which is to be stated.


Since it is no title like "champion" and since we can give a description 
of the reasons the award will be always specific, it is not a title you 
carry around your lifetime and all of that. Maybe a person could be 
awarded multiple times, but that is then to decide. That means there 
will be no discussions about revoking the championship, or for how long 
this is granted. Also I think the award leaves better space for a good 
naming. Also we can give commit access along with it, which may or may 
not be taken, but then includes the official ASF way of recognizing people.


what do you guys think?

bye Jochen

Re: Groovy Champions proposal feedback

[Keith Suderman]

I may as well chip in my $0.00 worth.

I like the concept,  that it will be retroactive, and will consider more than 
just code contributions.

I also think the chosen name should be professions looking/sounding and not be 
"cutesy".  Therefore my preference(s) would be:

1. Groovy Champion (to be as close as possible to Java Champion)
2. Groovy Star (due to the logo tie-in)
3. Groovy MVP

Anyone confusing "Most Valuable Player" with "Minimum Viable Product" needs to 
get out and watch more sports ;-)

- Keith

> On Feb 13, 2018, at 4:58 AM, Paul King  wrote:
> 
> 
> Hi everyone,
> 
> A few of us have had various discussions (in fact over many years)
> about having a recognition scheme similar to Java Champions,
> perhaps called "Groovy Champions" or "Apache Groovy Champions"
> or something else entirely if we think of a better name.
> 
> I think the idea has always been to recognize contribution within the
> whole Groovy ecosystem not just the Apache Groovy project. The many
> tens of projects within the ecosystem are often where many ideas come
> from for the project's future evolution and also where future contributors
> may arise. And in any case, Groovy has always been about making
> coding productive and fun and we should celebrate that widely!
> 
> There are various questions to ask like should such a scheme
> be formally coordinated by the project/by Apache or should it be run as a
> community-driven unsanctioned activity and if so what guidelines should
> be in place. Also, there are many details like how will the scheme operate?
> How are new members elected? Is it a lifetime recognition or is there
> an "emeritus" status? And so forth. Java Champions vote themselves
> on new champions and the recognition has a lifetime status for instance.
> if we progress this idea, we'd need to make that all clear but that isn't
> the purpose of this email - we need to first decide if we like the idea.
> 
> Even if we like the idea, there are still some hurdles to step through.
> We've already sought some informal feedback from other parts of
> Apache and other projects within the Groovy Ecosystem and we'll
> likely need further discussions. We want something that embraces
> the whole community but fits in with Apache project governance
> around trademarks/branding.
> 
> So, the first question is: are we as a project in favor of such a scheme?
> 
> Cheers, Paul.

--
Keith Suderman
Research Associate
Department of Computer Science
Vassar College, Poughkeepsie NY
suder...@cs.vassar.edu