•   about 2 years ago

Can we provide a private repo of the code?

And if so, which judge's email address should we provide access?

  • 5 comments

  •   •   about 2 years ago

    If you look at the other threads, you will see another thread with the same title. In that thread, the DevPost rep said yes but that you would have to provide login credentials. I responded by saying that given the way GitHub allows you to give access requires the invitee's E-mail address, we would need one of the judge's E-mail addresses to do that and that login credentials therefore wouldn't work.

    We never got a clarification on that important point, so hopefully your new thread on this subject will help get a clear answer on private repo's.

  •   •   about 2 years ago

    Thank you Robert. Given how clear you were in the original thread, perhaps it is best proceed under the assumption that we are expected to generate new credentials, extend an invitation for this new account to access the private repo, and then detail these credentials as instructions in the video.

    I'm making a lot of assumptions here, but it's the only path that aligns with the given information. Hopefully guidance from the host is provided

  • Manager   •   about 2 years ago

    Hi there,

    to Robert's point, the code repo must be public, as judges will need to have access. The code repo should be public as you will not be able to add the judge's credentials ahead of time.

  •   •   about 2 years ago

    Thank you for the clarification

  •   •   about 2 years ago

    Konrad, I know this may seem like a small mitigation strategy, but just because you make it public doesn't mean you have to make it open source. Just don't specify a license when you publish the repo. I know it doesn't stop someone from seeing your code, and remember, by entering the contest you grant Google a nearly unlimited license to do what the like with the code as stated in the rules (see other thread in this forum), it's at least something.

Comments are closed.