-
Notifications
You must be signed in to change notification settings - Fork 5
docs: Update CC Onboarding course steps #71
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from all commits
Commits
Show all changes
2 commits
Select commit
Hold shift + click to select a range
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
9 changes: 4 additions & 5 deletions
9
Core Contributor Onboarding/course/html/ff2b3db490a947d0a7d027d5a716797f.html
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,9 +1,8 @@ | ||
| <p>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.</p> | ||
| <p>Start getting involved today! Here's some things we'd love for you to do:</p> | ||
| <ul style="margin-top: 0; margin-bottom: 0; padding-inline-start: 48px;"> | ||
| <li>Say Hello to everyone in the <a href="https://openedx.slack.com/archives/C015KC8CN76" target="_blank">#core-contributors Slack channel</a></li> | ||
| <li>Join the <a href="https://discuss.openedx.org/" target="_blank">Discussion Forums</a> and participate, particularly answering questions in areas you're an expert in</li> | ||
| <li>Make sure your information is accurate on the <a href="https://openedx.atlassian.net/wiki/spaces/COMM/pages/3156344833/Core+Contributors+to+the+Open+edX+Project" target="_blank">Core Contributor wiki page</a></li> | ||
| <li>Consider joining the next Contributor's Meetup to get a sense for what it is (every other Tuesday; see the <a href="https://calendar.google.com/calendar/embed?src=c_v86shrnegshsqgp4fj2k94u7bc%40group.calendar.google.com&ctz=America%2FNew_York" target="_blank">Working Groups shared calendar</a>)</li> | ||
| <li>Consider joining <a href="https://openedx.atlassian.net/wiki/spaces/COMM/pages/46793351/Open+edX+Working+Groups" target="_blank">other Working Groups</a>, depending on your areas of expertise</li> | ||
| <li>Say Hello to everyone in the <a href="https://openedx.slack.com/archives/C015KC8CN76" target="_blank" rel="noopener">#core-contributors Slack channel</a></li> | ||
| <li>Join the <a href="https://discuss.openedx.org/" target="_blank" rel="noopener">Discussion Forums</a> and participate, particularly answering questions in areas you're an expert in</li> | ||
| <li>Make sure your information is accurate on the <a href="https://openedx.atlassian.net/wiki/spaces/COMM/pages/3156344833/Core+Contributors+to+the+Open+edX+Project" target="_blank" rel="noopener">Core Contributor wiki page</a></li> | ||
| <li>Consider joining <a href="https://openedx.atlassian.net/wiki/spaces/COMM/pages/46793351/Open+edX+Working+Groups" target="_blank" rel="noopener">other Working Groups</a>, depending on your areas of expertise</li> | ||
| </ul> |
13 changes: 2 additions & 11 deletions
13
Core Contributor Onboarding/course/problem/069804872032408caa57e3f050875cbe.xml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,12 +1,3 @@ | ||
| <problem display_name="Ensure Your Write Access is Set" markdown="null"> | ||
| <multiplechoiceresponse> | ||
| <p>File a <a href="https://github.com/openedx/axim-engineering/issues/new/choose">Axim Access/Config GitHub request</a> 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.</p> | ||
| <p>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.</p> | ||
| <label>I have done this</label> | ||
| <choicegroup type="MultipleChoice"> | ||
| <choice correct="false">I'll do it later</choice> | ||
| <choice correct="true">Yes</choice> | ||
| <choice correct="false">I'll never do it</choice> | ||
| </choicegroup> | ||
| </multiplechoiceresponse> | ||
| <problem display_name="Ensure Your Write Access is Set" markdown="null" showanswer="" submission_wait_seconds="0" weight="1.0"><multiplechoiceresponse> | ||
| <p>If you have not already done so, file a <a href="https://github.com/openedx/axim-engineering/issues/new/choose">Axim Access/Config GitHub request</a> 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.</p><p>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.</p><label>I have done this, or it has already been done.</label><choicegroup><choice correct="true"><div>OK, I'll double-check my access as soon as it's granted</div></choice><choice correct="false"><div>Nah, I'll just wait until there's a problem</div></choice></choicegroup></multiplechoiceresponse> | ||
| </problem> | ||
14 changes: 2 additions & 12 deletions
14
Core Contributor Onboarding/course/problem/2bd1d52a645043ac921fd24a7c958933.xml
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -1,13 +1,3 @@ | ||
| <problem display_name="Section Checklist" markdown="null"> | ||
| <choiceresponse> | ||
| <label>Let's make sure you've completed all the CC tasks presented in this unit. </label> | ||
| <checkboxgroup> | ||
| <choice correct="true">I've signed the Core Contributor Program Agreement </choice> | ||
| <choice correct="true">I've said hi in <a href="https://openedx.slack.com/archives/C015KC8CN76">#core-contributors in Slack</a></choice> | ||
| <choice correct="true">I've made sure my information is accurate on the Core Contributor wiki page </choice> | ||
| <choice correct="true">I've made an account on the Open edX forums so I can participate in and be tagged in sprint retrospectives</choice> | ||
| <choice correct="true">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.</choice> | ||
| <choice correct="true">I have added the Working Groups calendar to my calendar, and I know when the biweekly Contributor's Discussion is.</choice> | ||
| </checkboxgroup> | ||
| </choiceresponse> | ||
| <problem display_name="Section Checklist" markdown="null" showanswer="" submission_wait_seconds="0" weight="1.0"><choiceresponse> | ||
| <label>Let's make sure you've completed all the CC tasks presented in this unit. </label><checkboxgroup><choice correct="true"><div>I've signed the Core Contributor Program Agreement</div></choice><choice correct="true"><div>I've said hi in <a href="https://openedx.slack.com/archives/C015KC8CN76">#core-contributors in Slack</a></div></choice><choice correct="true"><div>I've added myself to the Core Contributor wiki page</div></choice><choice correct="true"><div>I've made an account on the Open edX forums so I can participate in and be tagged in sprint retrospectives</div></choice><choice correct="true"><div>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.</div></choice><choice correct="true"><div>I have added the Working Groups calendar to my calendar.</div></choice></checkboxgroup></choiceresponse> | ||
| </problem> |
Binary file not shown.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
the pretty xml formatting was nice, consider preserving that? but OTOH, completely understood if you think it's not worth the effort, you're the one maintaining this--up to you.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
At some point, Studio exports quit pretty-printing. I have been just raw-exporting these from Studio. cc @ormsbee
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
(I don't do any editing in the XML)
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
👍🏻