General Challenge Updates Moving Forward

#devchallenge

Hey all, as part of our expanding challenge program we want to update and clarify some challenge requirements moving forward. First off, we want to express our gratitude for the dedication and effort you have put into your submissions. This has been one of our busiest years yet in terms of challenge participation, and it’s the enthusiasm you put into your work that makes these events a joy to run. Thank you for that!

Now, onto some housekeeping. We hope the following clarifications will not only streamline our process, but make things easier and more fair for all who participate.

Please note: These announcements only apply to challenges announced after this post, so these changes do not apply to the Bug Smash or Frontend Challenge: Comfort Food Edition that are currently ongoing.

One Submission Per Prompt

For future challenges, our default rule will be one submission per person per prompt. You may still qualify for multiple prize categories as part of one submission, but we want participants to focus their efforts into projects and posts of very high quality rather than getting distracted with multiple submissions. There will be exceptions to this rule but if there is an exception, we will let the community know in the announcement post and FAQ section. Otherwise, we default to one submission per prompt. If there is a writing prompt and a build prompt for a challenge, you may continue submitting to each of those prompts, once. Folks who repeatedly break this rule will not be eligible to win.

New Projects Please

We also wanted to take this moment and clarify that projects need to be created within the timeframe of the challenge unless specifically stated otherwise (for example, the current Bug Smash and recent Github “Finish-Up-A-Thon” would not have this rule since they explicitly allow for existing projects). We will clarify when there are exceptions to this rule.

Judging Period

We also realize that it can be frustrating to stop working on a project while waiting for the judging period, especially since we have extended our judging period window recently. That said, folks can update the readme of their projects to state what they did before and after the challenge. We will not consider anything committed after the challenge submission deadline. We will be double checking this as part of our process. If we see commits after the deadline, we will look for your notes in your readme or you’ll be disqualified.

Thank you all for making these recent challenges some of our most participated in yet. We hope these guidelines make things clearer and fairer for all involved.

With all that said, be sure to register for our upcoming challenges launching soon:

Our next Weekend Challenge is coming up! As always the prompt will be revealed at launch. Register with the sign up button to be notified when it drops. When it does, you'll have the weekend to build and submit. That's it! Because our community spans every timezone on the planet, we've set the window so that everyone around the world gets at least a full weekend to participate.

Happy coding!