Back to all discussions

  •   almost 9 years ago

Why do we have to share the bot code for testing?

In the FAQ there is a requirement to share the bot code for testing -- why? Will it not be enough if we share all the details on how to test the bot?

https://awschatbot2017.devpost.com/details/faq#test

How can I provide Devpost with access to test my app?
Include a link to your bot code on GitHub. Your Github code repository may be public or private. If your repository is private, access must be given in the testing instructions provided with your submission. Github code will be used only for application review and testing. Make sure to include all deployment files and testing instructions needed for testing your bot.

  • 4 comments

  •   •   almost 9 years ago

    I see that the code submission requirement is also part of the HOW TO ENTER section in the home page:

    https://awschatbot2017.devpost.com/

    5. Provide a way to access your bot for judging and testing, including a link to your GitHub repo hosting the bot code and all deployment files and testing instructions needed for testing your bot.

    Can someone please explain what are the judges and testers looking to do with the code? If they have all the information they need to judge and test the bot without looking at the code, then why do they need to look at the code?

    I can send them the details of the AWS instance if they want to look at the code internally, but it will be a deal breaker for me share the code via GitHub. Please let me know.

  •   •   almost 9 years ago

    Hi there, code is part of the submission because there needs to be proof that entrants actually built something, beyond a demonstration video. Often with competitions, we can ask for a link to a compiled website or application as proof that something was built. In this case, there is no similar way to submit the software, hence the code request.

    But please know this is NOT a requirement to make your code open source. You may just share your private repo with testing@devpost.com. That has been in the official competition rules; we have now made it clearer on the homepage, in case you thought code needed to be open sourced (which it does not).

  •   •   almost 9 years ago

    Although I don't mind open sourcing my submission - you might consider allowing other forms of submission as well as GitHub, eg. BitBucket (if not possible now for this hackathon, perhaps for future ones?). The current rules mean people have to decide between open sourcing or establishing a paid private GitHub plan, if they don't have one already, which might exclude those who aren't able to pay for it.

  • Manager   •   almost 9 years ago

    The competition doesn't require you to open source your code. It can be shared through a private repo with the hackathon managers. We agree with you and will gladly allow you to share privately with GitHub or BitBucket. Please make sure to share the repo with testing@devpost.com before the submission deadline.

Comments are closed.