docs: added github access details to CC onboarding course

[MahnoorArbisoft]

Based on conversation in this thread: Added details of accessing Github in CC Onboarding Courses

Details of updated Text

What is GitHub Issue?
A GitHub issue, also known as a GitHub Ticket, closely resembles a Jira ticket, Trello card, or any other form of single-problem representation within an issue tracking system. We use GitHub because it’s public and free to use - browsing GitHub issues or boards doesn’t require an account. (A GitHub board mirrors a Jira or Trello board - offering a consolidated view of tickets.) For those new to GitHub, [this tutorial](https://docs.github.com/en/issues/tracking-your-work-with-issues/quickstart) could help you.

How can you get access to GitHub?
Anybody can create a GitHub issue, but only Open edX organization members can assign themselves to tickets or manage tickets on project boards. Product / Project Managers, and Working Group Members can gain access by following these steps:


Open [this link](https://github.com/openedx/axim-engineering/issues/new/choose)
Select “🔐 GitHub Request - Access/Config”
Complete the form: enter your GitHub username and specify that you need "Triage Access Level" to aid your contributions to the Product Working Group
Please be sure to promptly accept your invitation as it expires in 7 days

[openedx-webhooks]

Thanks for the pull request, @MahnoorArbisoft!

This repository is currently maintained by @sarina.

Once you've gone through the following steps feel free to tag them in a comment and let them know that your changes are ready for engineering review.

🔘 Get product approval

If you haven't already, check this list to see if your contribution needs to go through the product review process.

• If it does, you'll need to submit a product proposal for your contribution, and have it reviewed by the Product Working Group.
  • This process (including the steps you'll need to take) is documented here.
• If it doesn't, simply proceed with the next step.

🔘 Provide context

To help your reviewers and other members of the community understand the purpose and larger context of your changes, feel free to add as much of the following information to the PR description as you can:

• Dependencies

  This PR must be merged before / after / at the same time as ...

• Blockers

  This PR is waiting for OEP-1234 to be accepted.

• Timeline information

  This PR must be merged by XX date because ...

• Partner information

  This is for a course on edx.org.

• Supporting documentation
• Relevant Open edX discussion forum threads

🔘 Get a green build

If one or more checks are failing, continue working on your changes until this is no longer the case and your build turns green.

Details

---

Where can I find more information?

If you'd like to get more details on all aspects of the review process for open source pull requests (OSPRs), check out the following resources:

• Overview of Review Process for Community Contributions
• Pull Request Status Guide
• Making changes to your pull request

When can I expect my changes to be merged?

Our goal is to get community contributions seen and reviewed as efficiently as possible.

However, the amount of time that it takes to review and merge a PR can vary significantly based on factors such as:

• The size and impact of the changes that it introduces
• The need for product review
• Maintenance status of the parent repository

💡 As a result it may take up to several weeks or months to complete a review and merge your PR.

[sarina]

@MahnoorArbisoft when this is unpacked it's really messed up, I'm not sure what happened to your exported course here - you only changed one file, right? I can't actually see what you changed. Could you point to a course with the updated unit(s), or send screenshots?

[sarina]

Also your title of your PR says you changed the CC onboarding course, but the export is from the Intro to Open edX course - maybe that's the issue?

[sarina]

@cassiezamparini could you help me clarify where this updated text is supposed to be added?

[cassiezamparini]

@sarina Is there an easy way to see the course content somewhere on GitHub? Perhaps you can tell me what to do if it's easy enough. My memory of the course content is murky so I need a refresher for context. Or perhaps I should just look at the actual onboarding course, but I don't seem to have access to anymore (even tried resetting my password). Could you give me access?

@MahnoorArbisoft Do you have any ideas where this might best land (as you've done the course recently)?

[sarina]

You can download all the courses here: https://github.com/openedx/training-courses/tree/main/dist and import it into your instance.

I'm a bit confused as to what course this change is meant to go into.

[cassiezamparini]

@sarina This is for the Core Contributor Onboarding Course: https://training.openedx.io/courses/course-v1:OpenedX+NewCC+2024/about

I'll wait on @MahnoorArbisoft to comment before trying to import the courses into an instance (I'd need to learn how to do this -- it's a good thing to know). Having access to the actual learner view would be far easier and quicker for me.

[sarina]

I was confused because in this PR the Intro to Open edX course has been updated:

[sarina]

Do you have an instance you can import the course into to test it out? Otherwise I need the email address you have an account on the training sit ewith

[cassiezamparini]

@sarina I'm not sure why the intro would have been updated. @MahnoorArbisoft can you advise how you went about this / where you intended this to be added in the course?

[MahnoorArbisoft]

sorry about the confusion. Not sure what went wrong here. I cant trail back to the issue either because i used our sandbox and that flushes the data everyday.

I added this text in "Finding meaningful work" unit of the course but since this was my first PR maybe i did something wrong in the process. I can make changes and export the course again -- would that make it easier?

[sarina]

@MahnoorArbisoft could you just clarify:

• What course you intended to update
• The name of the unit you wanted to update