+1 I would leave the money out. But a trophy or something physical would be nice.
I would collect votes via a web form. To keep the winner unknown. Allows for surprise announcement. Sergio > On 10 May 2019, at 18:27, Andres Almiray <aalmi...@gmail.com> wrote: > > I concur with most points except for the $ aspect. I’d simply leave it out. > > Sent from my primitive tricorder > >> On May 10, 2019, at 17:38, MG <mg...@arscreat.com> wrote: >> >> Good summary Søren. Let me add my 5 Gents to maybe advance the topic further: >> Since I think that this is the easiest: Anybody who is against taking funds >> out of FOG (Friends of Groovy) for this in principle should speak up now or >> 4ever hold his peace G-) >> As a ballpark number / discussion point I would suggest $250 to $500 for the >> award - what do you gals & guys think ? Too high ? Too low ? >> My suggestion would be to award it for work done recently (i.e. not >> life-time), in part for the practical reason that I think it would be easier >> to agree on a person here, and it would be faster to get this whole thing >> off the ground... (Disclaimer: I have argued for non-lifetime before based >> on additional reasons) >> One important open question, as you point out, is: Who should be allowed to >> vote ? PMC (maybe too restrictive) ? FOG contributors ? Everyone who has >> been on the dev or user mailing list for a year ? >> Note: Letting everyone vote would worry me, since I have personally >> witnessed votes like that being manipulated/rigged (all in the name of >> "well, democracy has spoken..."), by someone who has 50 Facebook friends... >> Shall the vote be "most votes wins", or a decision between the e.g. two >> people with the highest number of votes, or... ? >> Shall the vote be changeable (i.e. everybody sees how many votes everybody >> currently has, and the votes can be shifted, until the voting is over) ? >> Is the voting going to be informal e.g. through posting on the mailing list, >> or would we want to use a web site/service for this (which ? requires more >> effort...) ? >> Shall the award be virtual, or tied to a physical manifestation ? If >> physical, I would suggest something like a mug, since it is something you >> can put on your desk, or actually use if you so choose (I have experience >> designing things and would volunteer to design (the print on) such a mug). >> Other suggestions of course welcome G-) >> (GR8Conf could work, if people would nominate some Groovy conbtributors (in >> the broader sense) within the next week, and voting could then be open for >> one week after that...) >> >> Cheers, >> mg >> >> >>> On 09/05/2019 17:12, Søren Berg Glasius wrote: >>> 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 monetary 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 a 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, otherwise 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 <pa...@asert.com.au> 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 <soe...@glasius.dk> >>>>> 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 <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 >>>>> > >>>>> >>
