Code of Conduct for Participants of “USC Hack for Hope”

By participating in the USC Hack for Hope online hackathon (“Hackathon”), sponsored by the Lloyd Greif Center for Entrepreneurial Studies in the USC Marshall School of Business )”USC”), you (“Participant”) agree to the following:

  1.  The Hackathon will be implemented and coordinated through the designated Hackathon Manager (“HM”) and the HC team. The HM will oversee mentor assignments.  The Hackathon will culminate with each Participant, either individually or as a part of a team, submitting an entry for their project to be judged (“Submission”).
  2. You will be professional, open, and responsive to your mentor(s) and teammates, maintaining regular contact using the communication and collaboration tools provided by the Hackathon organizers.
  3. You will do your best to ensure that at least one team member participates in the online workshops. These will cover various topics including COVID-19, such as technology platforms for development, customer discovery, agile development, intellectual property, and the pitch. The dates for these online workshops will be listed on the DevPost site and emailed to you.
  4. You will provide to the Hackathon and judges accurate information regarding your product/solution innovations to the best of your ability. All identified proprietary information provided by Participants will be maintained in strict confidence by all mentors and other Participants.
  5. Participants will adhere to USC policies, including those regarding the use of USC resources, intellectual property and conflict of interest.
  6. You will notify the HM promptly of any problems or changes in relationships with your assigned mentor(s) and are encouraged to discuss with the HM or members of the HM team the participation of additional mentors as needs and interests change. All requests for replacement of a mentor or assignment of additional mentors must be made through the HM.
  7. Participants should understand that any mentor who desires to enter into a financial, equity, or compensated business relationship with an innovator must quit the hackathon. Participants should notify the HM as soon as they are aware of any of these relationships. In such cases, the HM will assign new mentor(s) as appropriate.
  8. Names of individual mentors may be used on business presentations only if permission is granted by the mentor in question.
  9. Participants that do not comply with the Hackathon rules, or USC rules or procedures, may be eliminated from participation in the Hackathon at any point.
  10. These policies may be revised or otherwise updated from time to time at the discretion of USC based upon the evolving needs of the Hackathon, mentors, Participants and their projects.
  11. Participants retain ownership of all intellectual property rights they may create or develop during the Hackathon and in and to any Submission. USC will not assert any ownership of any intellectual property merely by virtue of Participant’s participation in the Hackathon. If Participant is part of a team, that team is wholly responsible for determining ownership of any intellectual property rights developed during the Hackathon.
  12. We encourage Participants to open source their projects to share their hacks with the greater community and to promote innovation for hope.

 Code of Conduct for Mentors of “USC Hack for Hope”

The Greif Center for Entrepreneurial Studies is grateful for seasoned members of the corporate, investment, and entrepreneurial community to support the USC Hack for Hope online hackathon (“Hackathon”) as mentors.  Mentor candidates must demonstrate experience in coaching academic innovators and creating new high-impact ventures.

Guidelines for handling privileged information and managing conflict of interest apply for all meetings and activities related to the hackathon.  By serving as a mentor, you agree to follow this Code of Conduct.

  1.  The Hackathon will be implemented and coordinated through the designated Hackathon Manager (“HM”) and the HM team. The HM will oversee mentor assignments.  The Hackathon will culminate with each Participant, either individually or as a part of a team, submitting an entry for their project to be judged (“Submission”).
  2. The pairing or assigning of mentors to participants will be based solely on the needs of the participant and the best available mentor for the needs identified as determined by the HM.
  3. No mentor may accept, for him/herself or any related party, a primary financial interest or financial relationship with a Hackathon team and project without first formally recusing him/herself as a mentor and providing the HM written notice.
  4. You must disclose to the HM any potential known secondary conflicts of interest where the success or failure of a project which you assist or oversee would potentially have material impact on any entity in which that person or related party is significantly invested or is a principal or for which such a close relationship is contemplated. In such cases, separation from the Hackathon or from the project may be appropriate if the conflict is deemed substantive by the HM.
  5. You will act consistent with the law and will promote the best interests of the participants who have formed a relationship with the Hackathon program.
  6. The commitment period for each mentor is coincident with the dates of the Hackathon, terminating immediately after the end of the event.
  7. You will maintain regular contact with your mentees.
  8. You will keep the HM informed of the activities of the mentees and you will participate in Hackathon meetings and activities as appropriate.
  9. You are considered a USC visitor, and therefore members of the University community, and thus you will adhere and to the USC Intellectual Property Policy and the USC Conflict of Interest policies.
  10. You do not receive any ownership interest in any USC intellectual property by virtue of participating as a mentor. 
  11. You will maintain strict confidentiality over any proprietary information entrusted to you by the participants, including business model elements.
  12. Any disclosure of USC confidential or proprietary information by the mentor to a third party must be subject to a written non-disclosure agreement between USC and the third party. The HM will oversee the formation of each relationship between mentors and participants.
  13. These policies may be revised or otherwise updated from time to time at the discretion of USC based upon the evolving needs of the Hackathon, mentors, participants and their projects.
  14. Participants retain ownership of all intellectual property rights they may create or develop during the Hackathon and in and to any Submission. USC will not assert any ownership of any intellectual property merely by virtue of Participant’s participation in the Hackathon
  15. We encourage participants to open source their projects to both share their hacks with the greater community and to promote innovation for hope.