Back to all discussions

  •   over 1 year ago

Private usage credentials

Hi!
Thank you for this great hackathon!

Our team is developing a mobile app (with a cloud part) that can be used with a login and a password.
The git codebase will be public and open, but can we only send a username-password combination to judges for testing/judging or the app should have open access for testing (could run out of credits/free tokens)?

If it's possible to send only for judging, how should we do it? Should we send the data to specific emails or put in a part of Devpost submission?

Thanks!

  • 6 comments

  •   •   over 1 year ago

    Hi.
    Since the submission deadline is approaching , it would be really helpful to know to treat this aspect.
    Thanks

  • Manager   •   over 1 year ago

    Hi there, we will only be allowing public code repos, per the rules.

  •   •   over 1 year ago

    I understand that the repository should be public, and the GIT repository will indeed be public, under an MIT license. This means anyone will be able to compile the app and create the necessary services on Google Cloud.

    However, the question was about the running application that judges will use for testing. Specifically, we already have a compiled mobile app, a live Google Cloud server, and the connection between these two components set up. We will include the compiled app in the submission, but since it relies on certain Google Cloud services, we would prefer to send a username/password pair (already created on the server) to a specific email for the judges. This would allow them to test and interact with the app directly.

    The reason for this is that if the credentials were posted publicly, the service credits or the request quota for those Google Cloud services could be exhausted before the judging process even begins.

    So, is it acceptable for us to send these credentials only to the judging committee?

    Thank you!

  • Manager   •   over 1 year ago

    No, unfortunately, we will not allow this, as we have chosen to keep the judge's personal information private. We will not be sharing the judge's emails so the repo and credentials must all be public.

  •   •   over 1 year ago

    Thank you for your response!

    According to the Rules, “Access must be provided to an entrant’s working application for judging and testing by providing a link to a website, functioning demo, or a test build. If an entrant's code repository is private, the entrant must include login credentials in the testing instructions. The application must be public.”

    Where should we provide these testing instructions so that the login details remain private and aren’t publicly accessible?

    I completely understand about the judges' emails; my question was only about where to send or include these credentials to ensure that only the judges have access to them.

    Thank you!

  •   •   over 1 year ago

    Found the answer:
    "Unless noted, additional info is for judges and hackathon organizers and will not appear on your public project page."

    So I will add the credentials in the Testing instructions since it will not appear on the public project page.

    Thanks!

Comments are closed.