search

topcoderinc / cab

9 stars 3 forks source link

Code Track Final Fixes Clarification #22

Closed hokienick closed 7 years ago

hokienick commented 7 years ago

Code Track has no Final Fixes. In case, at the end of the contest, the submission has issues, what is the procedure to get this corrected from the participant? Are they expected to fix that for free or for a fee?

https://apps.topcoder.com/forums/?module=Thread&threadID=889949&start=15&mc=21

hokienick commented 7 years ago

callmekatootie posted in the same forum what had been decided in the CAB Meeting:

Hello Members,

So here's the update on the points after our meeting today.

1 - Topcoder is open to any suggestions here. In this regard, it would be good if the community can take the initiative and come up with a proposal on how best to improve the UI Prototype track.

What I have in mind is to have a sample prototype created and shared that contains the changes that we would like to see in the prototype track. We can then share this with Topcoder and discuss it further with them.

Right now, we only have words and statements on how we can improve that track. But it would be better if we actually have a sample code that we can point to and describe how it is an improvement over the existing ones.

We'll have less luck pushing for a specific framework / library (example - make twitter bootstrap mandatory. Too restrictive.) and more luck trying to instead propose how to better organize the prototype (such as naming conventions not limited to class names, data-attribute names etc, organizing stylesheets into multiple files instead of one single large stylesheet etc to name a few of the changes that we can propose). So, if you want to take the initiative and create same prototypes and share with the community for feedback, we can organize it better and perhaps come up with some really good examples of how the prototype can take shape and take our ideas to Topcoder

2 - As mentioned, this will not be of concern anymore once the new scorecard rolls out

3 - What Ghostar mentioned would be the way forward from here on. At the end of the contest, the winner is not obligated to fix the issue reported by the reviewer for free.

Instead, the co-pilot will have the option to consolidate the issues reported by the reviewers that they would like to be fixed, reach out to the submitter and propose:

  1. What fixes to do
  2. What the payment will be
  3. When the fixes are needed by besides running follow up contests (such as F2F)

An email in this regard will be sent out shortly (to co-pilots only).