Hey guys. I'm sorry for forgetting to mention this in the meeting today. We will have three new judges for the January Dev Derby, so we will need to update the "Judging" tab accordingly. I do not have the headshots/bios yet, but should have them within a week or so. Additionally, we should probably remove the current judges or list them under a "Previous Judges" heading. None of them will be judging January entries. The good news? We plan to hold onto judges for three months at a time, so updates like these should be relatively infrequent. Also, if it helps, I can update the tab myself and send you guys a pull request (assuming I ever get vagrant going).
+1 to doing a PR! :) When will the January winners be announced? Seems we don't need to list the new judges until their judgements are also listed. So we can probably do this in 2.4.
Whiteboard: u= c= p= → u=contributor c=demos p=
Target Milestone: --- → 2.4
Agreed. In theory, the goal is to announce them by the 20th, but considering this is our first month with the new judging process it will probably be closer to late Feb / early March.
John, can you put a link to the content here in this bug? Thanks.
Bringing up to 2.3 because we need to add the tab copy for March to push on 2/28.
Target Milestone: 2.4 → 2.3
6 years ago
Whiteboard: u=contributor c=demos p= → u=contributor c=demos p=1
The copy doesn't need to be updated until judging happens, which will hopefully be around early March. The copy for the first judge is coming momentarily. There will be two more judges after that, but I'm still waiting to wrap those judges up...
Remy Sharp: Headshot: https://twimg0-a.akamaihd.net/profile_images/1509934279/rem-2011.jpg Title: MasterChef of code and cookies Website: http://remysharp.com Twitter: @rem Bio: Short, ginger, British. Built a few things: jsbin.com, html5demos.com, remote-tilt.com, responsivepx.com, nodemon, inliner.leftlogic.com, jqueryfordesigners.com, mit-license.org, snapbird.org, jsconsole.com. Runs a conference, wrote half a book.
6 years ago
Whiteboard: u=contributor c=demos p=1 → u=contributor c=demos p=1 2.4.5
Target Milestone: 2.3 → 2.4
Summary: Update the Dev Derby "Judging" tab before late February → Update the Dev Derby "Judging" with January--March judges
Chris Heilmann (you might know him): *Headshot* http://christianheilmann.com/wp-content/uploads/2011/06/codepo8.png *Title* Principal Evangelist at Mozilla *Twitter* @codepo8 *Website* http://christianheilmann.com *Bio* Chris Heilmann is the principal evangelist for Mozilla and has been blogging on web technologies for the last 6 years. Before Mozilla he was part of the Yahoo Developer Network and before that he spent several years developing large web sites and apps. Originally Chris was a radio journalist and newscaster. Chris lives in England but travels most of the time. His blog mostly contains his presentations, code examples about upcoming technologies and tips and tricks on web development of all kinds.
And that's it for January--March judges, so this can be pushed out whenever. There is still the open question of what to do with the judges that are currently listed, since they are no longer active. Listing them under a "Past judges" expandable could be nice, but I'm happy to just remove from the tab if it saves you guys some time.
I'm out of 2.4 bugs so I'm working ahead some more.
Assignee: nobody → lcrouch
Whiteboard: u=contributor c=demos p=1 2.4.5 → u=contributor c=demos p=1
Commit pushed to mdn at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/44dab696b2a567362638f681420199c420b34f4d Fix Bug 725481 new derby judges
Status: NEW → RESOLVED
Last Resolved: 6 years ago
Resolution: --- → FIXED
Commit pushed to mdn_prod at https://github.com/mozilla/kuma https://github.com/mozilla/kuma/commit/44dab696b2a567362638f681420199c420b34f4d Fix Bug 725481 new derby judges
verified fixed https://developer.mozilla.org/en-US/demos/devderby
Status: RESOLVED → VERIFIED
Component: Website → Landing pages
Product: Mozilla Developer Network → Mozilla Developer Network
You need to log in before you can comment on or make changes to this bug.