Closed Bug 654320 Opened 13 years ago Closed 13 years ago

Finalize copy for Demo Studio developer challenges structure, rules, guidelines, voting, etc.

Categories

(developer.mozilla.org Graveyard :: Demo Studio / Dev Derby, defect)

Product:
developer.mozilla.org Graveyard
Component:
Demo Studio / Dev Derby
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: jay, Unassigned)

References

Details

Attachments

(1 file)

Contest Rules
28.43 KB, application/vnd.openxmlformats-officedocument.wordprocessingml.document
Details 
We have the terms and conditions for the demo challenges in bug 636267, but we need to simplify them into copy we can use on the new contest page we create.

I have outlined the few areas we should focus on in the wiki with a few notes of what I know, but I can use help from Stormy and the team to help build those out in more detail an finalize the copy and messaging we want to use.

Specifically:

1. What are the rules?  What do we want to tell developers in general about the challenge (in addition to mentioning the topics we plan to have each month)?
2. How will the demos be judges?  What criteria do we want to use to A. narrow down the field to 3-5 finalists, and B. pick the winner and runner-up?
3. Who will be the judges?  Do we want to name specific people or leave it vague enough to swap people in and out?  What role will Mozilla folks play?
4. What are the prizes?  Who qualifies to win those prizes (are there limitations for international submissions)?
5. When do we want to set submission deadlines?  Announce finalists, winnners?

My notes are here: https://wiki.mozilla.org/MDN/MDNv09x/v095/Demo_Studio_redesign#Notes  So please edit that section on the wiki with more info and let's discuss what is missing here in the bug.

I hope to have the page designs completed by mid-May, so we need to have copy ready for implementation the week of May 16.

Thanks!
Jay - Stormy and I talked about all that while preparing the rules, so answers to most of those questions are in the rules. If you want to change anything from the way it is described in the rules please let me know because the rules will then need to be updated before they're posted.
Liz:  Thanks... and yes, I have seen that document.  We plan to put all that language on one page and link to it from our contest page.  However, this bug is to take that legalese and break it down into simpler terms and more digestible chunks we can put front and center on the contest page itself.

Stormy:  Is this something you can help with?  Most of the details in the legal document answer my questions, but we need to figure out how we want to present some of the more important pieces on the contest page so everyone sees it.  I don't expect everyone to go read the full legal doc, so we were hoping to have the basic info integrated into the contest page.
I think it's great to provide the key points up front in friendly language, just make sure nothing you write contradicts or distorts anything in the rules, and do encourage people to read the rules because they'll be bound by them. I'd like to review the copy for that page before it goes live.
(In reply to comment #3)
> I think it's great to provide the key points up front in friendly language,
> just make sure nothing you write contradicts or distorts anything in the rules,
> and do encourage people to read the rules because they'll be bound by them. I'd
> like to review the copy for that page before it goes live.

Sure thing.  I think the main points we want to summarize are:

1. Basic rules around the themes and who can participate (legal copy is very clear on this, so we might just point people directly to that or use it verbatim)
2. Criteria on which the demos will be judges (legal copy is vague on this)
3. We should provide some info on who will be judging (legal copy again just says it's at mozilla's discretion)
4. If we know which prize specifically being given out, we wanted to show that off on the page (legal copy just says android device)
5. We just want to highlight the important dates in a user-friendly way (details are in the legal copy, so we can point there for more details)

I think we have all the major pieces already in the doc Liz created.  Once we have a design mockups, we will need to put in the new copy in the appropriate places.  But we will make sure to encourage everyone to read the complete rules and will link to the legal copy from various places to facilitate that.

Liz: We'll be sure to get your review and approval once we have the pages staged.  Thanks!
bump. please include a link to the final copy ASAP.
Blocks: 653808
Luke:  Janet is going to help us get contest descriptions together for CSS Animations, HTML5 <video> and Touch on mobile.  I will get the other stuff together by this week.  I'm working on it with John, so hopefully we have something by Wed or Thu this week.
Assignee: stormy → jay
Jay: Where do I find the legalese?
Attached file Contest Rules — 
Janet - Here are the rules
Janet:  Not sure how far you've gotten on this, but I have started to outline the missing copy here: http://etherpad.mozilla.com:9000/demochallenges  And will continue to add bits and pieces as I digest the legalese for the rules and judging.  If you can help get the challenge descriptions for the upcoming 3 derbies, that'll be great!

Christian:  Can you try to nail down 1-3 judges for June that are awesome CSS guys?  It'll be great to have commitment from at least 1 person by the end of this week.

Thanks!
I am putting the final copy into this doc: 
https://docs.google.com/document/d/1lQscMSCYkKz9wmfPnPq4aWnUO5hT_qRBX1YIUwgq-6Y/edit?hl=en_US&authkey=COeO_98E

Janet and I will have everything filled in and ready for Craig by tomorrow EOB.  We can then get it staged and reviewed by Liz and tested by QA.
Hey everyone. I noticed some (mostly minor) issues in the copy. My notes can be read here:

https://docs.google.com/document/d/1m9xQVvoEgy6UnciDaMDosuinfOANPjIe_KSck8dJ-aM/edit?hl=en_US&authkey=CJC2oc0G#
(In reply to comment #11)

I updated the copy based on your notes for Criteria Duplication, OWT, and Prize List. 

On the Firefox Version, I think we need to get that change made in the legal text; referencing Firefox 4 will not be valid for very long. The Use of Votes should also be clarified in the legal text. I think the intent is that judges give entries a score, and they can take "likes" into account in giving that score.
(In reply to comment #12)
> (In reply to comment #11)
> 
> I updated the copy based on your notes for Criteria Duplication, OWT, and
> Prize List. 
> 
> On the Firefox Version, I think we need to get that change made in the legal
> text; referencing Firefox 4 will not be valid for very long. The Use of
> Votes should also be clarified in the legal text. I think the intent is that
> judges give entries a score, and they can take "likes" into account in
> giving that score.

Thanks John and Janet.

I was the one that updated a section of the legal text to read "Firefox, Firefox Beta or Firefox Aurora" for the Firefox version, since some challenges will be based on technology only working in Firefox Beta or Aurora.   We will have to make sure we update other references to Firefox 4 with the full list (as long as legal is ok with that).

Liz:  Are you ok with listing the 3 main Firefox channels instead of just Firefox 4?   We technically need to do that or just say "Firefox" with some explanation about the various versions and how new tech may not work with the current official version of Firefox.   Listing the 3 covers all the bases, so that is my recommendation.
Yes, but it needs to get changed in the rules. I have some other comments.

1) I think there's too much detail in the summary of the rules. From a legal perspective that's bad because it makes it look like it's pretty complete so someone could argue they didn't realize there were additional rules and if there's any discrepancy between the 2 versions that also makes it harder to enforce them. From a participant perspective, too, it may be overkill. 

I'd rather you pull out the summary of the rules and just include some key points like "Almost anyone can enter (see the rules for exceptions). There'll be a new contest every month. Your entry must meet certain criteria, see the rules for the overall criteria and xx for any special criteria for a specific contest. Please only submit materials you created or have the right to use and distribute. Remember that your entry will be posted for all to see. Entries will be judged by a panel of qualified reviewers, who may or may not take into account how many "likes" your entry receives. Winners will be notified by the 20th of the month following the contest they entered. You can't win more than once in the same calendar year. Please read the Official Rules before submitting your entry." That's just a quick example of what I'd prefer.

2) There's a typo in the rules under Timing for Entry. It says "...by the 20th of followng month". It should say "...by the 20th of THE followIng month.

3) Under "Work Criteria," "Entry must be compatible with and function properly in the then-current final product version of Firefox 4 without plug-ins" can be changed to "Entry must be compatible with and function properly in a current version of Firefox, Firefox Beta or Firefox Aurora, without requiring plug-ins"

4) Also under "Work Criteria," "Your Entry may not depend on browser plug-ins" can be removed if that's duplicative of the first item, which it seems to be.

5) Prizes. When we wrote the rules, there was only one prize. If you're going to have 2nd and 3rd place prizes, the rules will have to be revised. I can do that next week.

6) We purposefully said judges "may" consider likes so that they aren't a significant factor in the selection of the winner. I'd like to leave that language as is.
Liz:  Thanks for the feedback and corrections.  I agree that the rules summary is probably overkill.  I like your suggestion to simplify with a few major points about the rules, so I will make the recommended changes and shorten up the rules section next week after the holiday.  I'll let you know when we have something ready for another quick review.  I appreciate the input.
Liz:  I have updated the rules and judging section with simpler copy.   And made your edits to the legalese.   Please have another look and let me know if everything is ok.  The only part left for you is updating the Prizes section of the legal doc to include the 2nd and 3rd place prizes.   Let me know when you have that ready as well.  Thanks so much for the help with this.
Assigning to Liz for the final bit of copy.

Liz: We're implementing the pages today, so if you could help wrap this up today or tomorrow, that'll be great!  Thanks.
Assignee: jay → liz
Jay - Do you have a few minutes to talk about the rules? I just want to clarify a couple of things.
I've updated Jay's doc at: 
https://docs.google.com/document/d/1lQscMSCYkKz9wmfPnPq4aWnUO5hT_qRBX1YIUwgq-6Y/edit?hl=en_US&authkey=COeO_98E and added comments to identify the changes I made. Let me know if you have any questions or think I missed anything.
Jay - I'm assigning this back to you.
Assignee: liz → jay
Thanks Liz for the edits.

Assigning to Les since he's implementing those pages now.  

Les:  Please use the latest copy in the Google Doc linked in comment #19.  There are a few changes Liz made that were not in Craig's template pages.

Thanks.
Assignee: jay → lorchard
https://github.com/mozilla/kuma/commit/e9366e1550e501ff42b74a4f2e213b7dea40a60f

I think this commit covers the changes, but let me know if I missed anything. 

Also, thanks to Liz for highlighting the edits - that helps a *lot* in figuring out what to change in the pages!
Status: NEW → RESOLVED
Closed: 13 years ago
Resolution: --- → FIXED
Oh, the changes should be reflected on these pages in staging, after it updates within the next 15 minutes:

https://developer-stage9.mozilla.org/en-US/demos/devderby/
https://developer-stage9.mozilla.org/en-US/demos/devderby/rules
Thanks Les.

Jay - In reviewing the pages, something else occurred to me. There may be too much detail in the Judging section. You say a scale of 1-5 will be used, the overall score will be the average of all 4 components, and describe how ties will be resolved. Unless you feel it's really necessary to provide this level of detail, it might be better not to. We don't go into that kind of detail in the rules because then you're locked into doing it that way. What if you find a scale of 1 to 5 isn't working and you want to use 1-10 instead? Or there's a tie and you want to use number of likes to break the tie instead of re-evaluating the entries? I'd feel better if the description were vaguer.

Here's one way to revise the section:

Entries will be reviewed by a panel of qualified judges, including members of the Mozilla team and outside experts. We will rate the demos across 4 dimensions:

    Technology – Does the demo showcase the power of open Web technologies?
    Originality – How innovative and unique is the demo?
    Aesthetics – How good is the visual design and interaction experience?
    Practicality – How useful is this demo in enhancing the Web today?

The judges will use all four dimensions in scoring each entry, and any additional criteria specified for a particular contest.

The judges may also take into account how many “likes” the entries have received from the community. So make sure to share your demo with others and encourage them to visit Dev Derby to “vote.”

Sorry for the late suggested changes.
(In reply to comment #24)
> Thanks Les.
> 
> Jay - In reviewing the pages, something else occurred to me. There may be
> too much detail in the Judging section. You say a scale of 1-5 will be used,
> the overall score will be the average of all 4 components, and describe how
> ties will be resolved. Unless you feel it's really necessary to provide this
> level of detail, it might be better not to. We don't go into that kind of
> detail in the rules because then you're locked into doing it that way. What
> if you find a scale of 1 to 5 isn't working and you want to use 1-10
> instead? Or there's a tie and you want to use number of likes to break the
> tie instead of re-evaluating the entries? I'd feel better if the description
> were vaguer.
> 
> Here's one way to revise the section:
> 
> Entries will be reviewed by a panel of qualified judges, including members
> of the Mozilla team and outside experts. We will rate the demos across 4
> dimensions:
> 
>     Technology – Does the demo showcase the power of open Web technologies?
>     Originality – How innovative and unique is the demo?
>     Aesthetics – How good is the visual design and interaction experience?
>     Practicality – How useful is this demo in enhancing the Web today?
> 
> The judges will use all four dimensions in scoring each entry, and any
> additional criteria specified for a particular contest.
> 
> The judges may also take into account how many “likes” the entries have
> received from the community. So make sure to share your demo with others and
> encourage them to visit Dev Derby to “vote.”
> 
> Sorry for the late suggested changes.

I'm good with your suggestions.  It give us more flexibility.  I just borrowed the voting from the Game-On contest, so I thought that was vetted already.
retornam:  can you please verify all of this copy on stage8 and mark v.fixed once you've tested the pages.  thanks!
Assignee: lorchard → mozbugs.retornam
Version: MDN → unspecified
Component: Demos → Demo Studio / Dev Derby
Assignee: mozbugs.retornam → nobody
Commits pushed to master at https://github.com/mozilla/kuma

https://github.com/mozilla/kuma/commit/d4f6f489367967168f36218ebab0af90ebefc023
bug 654320 - updated few 404 w3 urls

Need to check all other urls also.

https://github.com/mozilla/kuma/commit/71f6930d5baa4a852ddbfb91ff5979585b60b97b
Merge pull request #3644 from EmiXLabs/patch-1

bug 654320 - updated html5 video and audio 404 w3 urls
Product: developer.mozilla.org → developer.mozilla.org Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: