Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 8 Next »

This page is meant to help those who are joining the CC program with write access to one or more code repos.

 For employees of tCRIL joining the program

Employees of tCRIL we do not need to sign individual CLA or Core Contributor’s Agreement; they are covered by the Confidentiality & Invention Assignment Agreement that everyone signs at hire. If they leave tCRIL - they must sign an individual CLA to continue to commit code, and a Program Agreement if they intend to continue working as a Core Contributor. You may skip to Step 4.

For Those Joining the Core Contributor Program as a Committer

  1. Confirm that your employer has signed an Entity Contributor Agreement and identified you as an authorized submitter under that agreement. As an employee, the code you generate is likely owned by your employer or a client of your employer, so it is important to confirm that (1) your employer supports your participation in this program and (2) the code you wish to contribute can be appropriately provided to the Open edX project.

  2. Please email cc-program-admins@tcril.org with a Hello, your personal email address, and a link to your nomination thread. We need this to generate documents related to your program participation, even if you are currently covered under an entity agreement.

  3. Once we receive your personal email address, we will send the following agreements via DocuSign:

    1. An individual contributor license agreement (using personal email address, not work email address). (For clarity, as described above, we expect the employer entity agreement to cover most contributions for so long as that relationship exists.) 

    2. A Core Contributor Program Agreement

      1. Note this agreement covers all contributions made in the capacity of any role (coder, project manager, translator, etc) so you are free to pick up other types of responsibilities as you see fit.

  4. [AFTER step 3 is completed - and you’ve received the countersigned documents]
    File a GitHub request ticket at https://github.com/openedx/tcril-engineering/issues for adding access for yourself for whichever repo(s) you should get access to. Include a link to your nomination thread and tag the CC who nominated you.

  5. Take the training courses for privacy/security and accessibility - Note: these courses are currently unavailable (as of Nov 2021). We expect them to be available sometime soon and will ask all new CCs to take them at that point.

  6. Be sure you’ve read merge guidelines - and bookmark them to refer to as you do your work.

    1. Merge Timing Guidelines for openedx Repositories

  7. Make sure you’re in the #core-contributors Slack room and the Slack room(s) corresponding to the repos you have merge access to (if your repo isn’t listed, reach out to cc-program-admins@tcril.org ). These slack rooms are meant to ensure core contributors and 2U OCM are able to collaborate, especially around questions of merge timing. More detail can be found here.

  8. Core Contributors fill in a bi-weekly check-in (which is a list of 6 simple questions) to give you a chance to report your hours contributed, ask for help on issues, report any blockers, et cetera. These bi-weekly check-ins are performed on Listaflow.com and you will be invited to create your account soon after becoming a CC.

  • No labels