diff --git a/Core Contributor Onboarding/course/html/4e3b6457e57049c98fff64608387a4a7.html b/Core Contributor Onboarding/course/html/4e3b6457e57049c98fff64608387a4a7.html index 83ddf47..7b90bde 100644 --- a/Core Contributor Onboarding/course/html/4e3b6457e57049c98fff64608387a4a7.html +++ b/Core Contributor Onboarding/course/html/4e3b6457e57049c98fff64608387a4a7.html @@ -1,7 +1,7 @@

To start, let's define what we mean by "sprint". Sprint, in the tech community at least, denotes a one week to one month period of work where everyone sets goals at the beginning of the sprint and then evaluates their progress, as well as any issues that have come up, at the end of the sprint.

Within the CC program, we practice two week sprints, from one Monday through the following Friday, in an extremely lightweight format. Ultimately, we only ask that you roughly report the number of hours you've spent on Open edX projects during the sprint. That form will also have some optional boxes for you to report on things that went well, challenges you have had, and other ways you could use help.

-

We use a tool called Listaflow to do this report.

-

You will receive access to Listaflow about a week after your Program Agreement is signed by both you and Axim. If you don't have access at that point, please comment on your onboarding ticket that you created on GitHub.

+

We use a tool called Listaflow to do this report.

+

You will receive access to Listaflow by messaging Fox Danger Piacenti on the Open edX slack to request access. Please send him the link to your Core Contributor nomination thread from the forums.

We really do urge you to complete the hours reporting by EOD Thurs, every other week. We use the hours reporting in the following way:

We also publicize the results of the Listaflow survey in the Core Contributors section of the discussion forums. Each sprint there is a new thread; take a look at the most recent sprint report to get a feel for what it looks like.

-

Finally, we have a biweekly Contributor’s meetup that occurs the Tuesday after the sprint concluded. The format of the meeting is ever evolving, but the goal of the meeting is to bring active contributors together to discuss their contribution work on a regular basis. As part of this discussion, the Listaflow survey results are reviewed and discussion is held around concerns people have and areas of collaboration they are seeking.

We encourage you to attend at least one Contributor's meetup! You can find the next one by looking at the shared Google calendar for all the working groups.

\ No newline at end of file diff --git a/Core Contributor Onboarding/course/html/624df66a96d74246b33748c8d23b3f2b.html b/Core Contributor Onboarding/course/html/624df66a96d74246b33748c8d23b3f2b.html index b879ce5..074d404 100644 --- a/Core Contributor Onboarding/course/html/624df66a96d74246b33748c8d23b3f2b.html +++ b/Core Contributor Onboarding/course/html/624df66a96d74246b33748c8d23b3f2b.html @@ -3,7 +3,7 @@
  • #core-contributors in Slack
  • the Core Contributor wiki page
  • Open edX Discussion Forums
    • -
  • Listaflow (retrospective tool)
    • +
  • Listaflow (retrospective tool)
  •  Working Groups calendar

    • \ No newline at end of file diff --git a/Core Contributor Onboarding/course/html/624df66a96d74246b33748c8d23b3f2b.xml b/Core Contributor Onboarding/course/html/624df66a96d74246b33748c8d23b3f2b.xml index f1ad3fe..7c9f785 100644 --- a/Core Contributor Onboarding/course/html/624df66a96d74246b33748c8d23b3f2b.xml +++ b/Core Contributor Onboarding/course/html/624df66a96d74246b33748c8d23b3f2b.xml @@ -1 +1 @@ - + diff --git a/Core Contributor Onboarding/course/html/93b6b32694cd48cd9bcd05e49e83c577.html b/Core Contributor Onboarding/course/html/93b6b32694cd48cd9bcd05e49e83c577.html index b0c4fdf..c896bf1 100644 --- a/Core Contributor Onboarding/course/html/93b6b32694cd48cd9bcd05e49e83c577.html +++ b/Core Contributor Onboarding/course/html/93b6b32694cd48cd9bcd05e49e83c577.html @@ -1,6 +1,6 @@

    The Core Contributor program grants you rights to the Open edX project beyond what is covered by an entity contribution agreement (the contribution agreement that an organization/company signs to cover the contributions made by their employees). Particularly, because you can act in the program at any time - even on time not being paid for by your employer - you must sign a personal Core Contributor Program Agreement and Individual Contributor License Agreement that attests that you personally take on the responsibilities your rights grant, including but not limited to committing code to the project and maintaining conduct befitting an ambassador of the project. It is a personal assignment and responsibility, even when the hours are provided by your employer.

    Note: since the Core Contributor agreement is between you and Axim, you will not be automatically offboarded from being a Core Contributor when you leave your employer. You are welcome to continue your CC responsibilities; however, at any time, you can leave the CC program by following these offboarding instructions.

    -

    We will be asking all Core Contributors to sign an Individual Contributor License Agreement ("Individual CLA"). This agreement covers actions that you might take on GitHub that are not covered under the scope of agreement that your employer may have with Axim (known as an "Entity CLA"). Generally, this applies mostly to Coding CCs, however, this allows Axim to give you access to certain functionalities within GitHub (such as the ability to edit issues) that your role may require.

    +

    We will be asking all Core Contributors to sign an Individual Contributor License Agreement ("Individual CLA"), regardless of their Core Contributor role. This agreement covers actions that you might take on GitHub that are not covered under the scope of agreement that your employer may have with Axim (known as an "Entity CLA"). Generally, this applies mostly to Coding CCs, however, this allows Axim to give you access to certain functionalities within GitHub (such as the ability to edit issues) that your role may require.

    Please sign the individual CLA using this link: https://openedx.org/cla.

    The personal CC Program Agreement will be sent to you via DocuSign after you've emailed cc-program-admins@axim.org with your personal (not work!) email address - for example, my-home-account@gmail.com , not my-work-account@my-company.com

    Note that the CC Program 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, provided you go through the nomination process for the new role.

    diff --git a/Core Contributor Onboarding/course/html/9b87da64084847439a120fb33d1bee98.html b/Core Contributor Onboarding/course/html/9b87da64084847439a120fb33d1bee98.html index e67ba0e..65aa0f4 100644 --- a/Core Contributor Onboarding/course/html/9b87da64084847439a120fb33d1bee98.html +++ b/Core Contributor Onboarding/course/html/9b87da64084847439a120fb33d1bee98.html @@ -1,4 +1,4 @@ -

    You can use the following template for your email to cc-program-admins:

    +

    You can use the following template for your email to cc-program-admins (for Role, use the Role you were nominated for in your nomination thread, such as Code Contributor, Design CC, Marketing CC, etc):

    My name is [name] and I'm joining the Core Contributor program as a [role-name]. Please see my nomination thread here: [link-to-nomination-thread]. I'm sending this email from my personal address, so please send the Core Contributor Program Agreement to this address.

    (if applicable) I work for [employer name] and am covered under their entity CLA. 

    Thank you!

    diff --git a/Core Contributor Onboarding/course/html/ff2b3db490a947d0a7d027d5a716797f.html b/Core Contributor Onboarding/course/html/ff2b3db490a947d0a7d027d5a716797f.html index dd02bf7..b50a4f2 100644 --- a/Core Contributor Onboarding/course/html/ff2b3db490a947d0a7d027d5a716797f.html +++ b/Core Contributor Onboarding/course/html/ff2b3db490a947d0a7d027d5a716797f.html @@ -3,6 +3,6 @@ \ No newline at end of file diff --git a/Core Contributor Onboarding/course/problem/2f35b51cae78452b876b5dd65542c894.xml b/Core Contributor Onboarding/course/problem/2f35b51cae78452b876b5dd65542c894.xml index 2d3b17f..ffa45a5 100644 --- a/Core Contributor Onboarding/course/problem/2f35b51cae78452b876b5dd65542c894.xml +++ b/Core Contributor Onboarding/course/problem/2f35b51cae78452b876b5dd65542c894.xml @@ -1,19 +1,3 @@ - - -

    We often get questions about which types of work count as Core Contributor work. There is admittedly a blurry line at times, but often it is very clear.

    - - - Doing prep work for a Working Group meeting - Attending a Working Group meeting, or catching up on a meeting (via recording or notes) if you can't attend synchronously - Performing follow-up work from a Working Group meeting - Working on projects for my company's client - Meetings within my company's team about projects our company is working on - Answering questions on the Open edX forums - Giving a talk to my team - Recording a talk on a topic relevant to some part of the community, and posting it for the greater community to see - 1-1/synchronous collaboration time with other community members on work you're doing together - Working on a design, strategy, or other program that benefits the Open edX project but is not work that falls under my Core Contributor role (for example, working on translating the platform when you're a Product Manager) - Using the knowledge or contacts I've gained through my Core Contributor role to try to gain new clients for my company - -     + +

    We often get questions about which types of work count as Core Contributor work. There is admittedly a blurry line at times, but often it is very clear. Review "Finding Meaningful Work" as a refresher.

    Doing prep work for a Working Group meeting
    Attending a Working Group meeting, or catching up on a meeting (via recording or notes) if you can't attend synchronously
    Performing follow-up work from a Working Group meeting
    Working on projects for my company's client
    Meetings within my company's team about projects our company is working on
    Answering questions on the Open edX forums
    Giving a talk to my team
    Recording a talk on a topic relevant to some part of the community, and posting it for the greater community to see
    1-1/synchronous collaboration time with other community members on work you're doing together
    Working on a design, strategy, or other program that benefits the Open edX project but is not work that falls under my Core Contributor role (for example, working on translating the platform when you're a Product Manager)
    Using the knowledge or contacts I've gained through my Core Contributor role to try to gain new clients for my company
         diff --git a/Core Contributor Onboarding/course/video/11a533d6ca5c4772971678fd1e3dea5c.xml b/Core Contributor Onboarding/course/video/11a533d6ca5c4772971678fd1e3dea5c.xml index 54d3ad2..a8effc4 100644 --- a/Core Contributor Onboarding/course/video/11a533d6ca5c4772971678fd1e3dea5c.xml +++ b/Core Contributor Onboarding/course/video/11a533d6ca5c4772971678fd1e3dea5c.xml @@ -1,3 +1,3 @@ -