The Core Contributor community is friendly, welcoming, and cooperative. We aim to sync our work via two-week retrospectives and do a read out every two weeks in the Contributor's Meetup to discuss ways to improve. As part of the retrospective we ask people to report their number of hours spent doing CC work so we can monitor the success of the program; we'll discuss this more in the coming sections.
Start getting involved today! Here's some things we'd love for you to do:
\ No newline at end of file
diff --git a/Core Contributor Onboarding/course/problem/069804872032408caa57e3f050875cbe.xml b/Core Contributor Onboarding/course/problem/069804872032408caa57e3f050875cbe.xml
index c266498..7da88d5 100644
--- a/Core Contributor Onboarding/course/problem/069804872032408caa57e3f050875cbe.xml
+++ b/Core Contributor Onboarding/course/problem/069804872032408caa57e3f050875cbe.xml
@@ -1,12 +1,3 @@
-
-
-
File a Axim Access/Config GitHub request 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.
-
Once you've received confirmation that your access is set, please visit each repository you were nominated to be a Core Contributor for and ensure you have write access. This is easy to do by navigating to any open PR and checking that the "merge" button is visible underneath the automated test check reporting.
-
-
- I'll do it later
- Yes
- I'll never do it
-
-
+
+
If you have not already done so, file a Axim Access/Config GitHub request 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.
After your access has been granted, be sure to remember to double-check your access by visiting each repository you were nominated to be a Core Contributor for and ensuring you have write access. This is easy to do by navigating to any open PR and checking that the "merge" button is visible underneath the automated test check reporting.
OK, I'll double-check my access as soon as it's granted
Nah, I'll just wait until there's a problem
diff --git a/Core Contributor Onboarding/course/problem/2bd1d52a645043ac921fd24a7c958933.xml b/Core Contributor Onboarding/course/problem/2bd1d52a645043ac921fd24a7c958933.xml
index 4b28d8a..4eb63e7 100644
--- a/Core Contributor Onboarding/course/problem/2bd1d52a645043ac921fd24a7c958933.xml
+++ b/Core Contributor Onboarding/course/problem/2bd1d52a645043ac921fd24a7c958933.xml
@@ -1,13 +1,3 @@
-
-
-
-
- I've signed the Core Contributor Program Agreement
- I've said hi in #core-contributors in Slack
- I've made sure my information is accurate on the Core Contributor wiki page
- I've made an account on the Open edX forums so I can participate in and be tagged in sprint retrospectives
- I can access Listaflow (sprint retrospective tool) - Note: 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.
- I have added the Working Groups calendar to my calendar, and I know when the biweekly Contributor's Discussion is.
-
-
+
+
I've signed the Core Contributor Program Agreement
I've added myself to the Core Contributor wiki page
I've made an account on the Open edX forums so I can participate in and be tagged in sprint retrospectives
I can access Listaflow (sprint retrospective tool) - Note: you will need to message Fox Danger Piacenti on the Open edX slack to request access to Listaflow. Please send him the link to your Core Contributor nomination thread from the forums.
I have added the Working Groups calendar to my calendar.