diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom.md index 7a12a921f5fc..cb71a2559493 100644 --- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom.md +++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/connect-a-learning-management-system-course-to-a-classroom.md @@ -32,6 +32,22 @@ To configure an LMS to connect to {% data variables.product.prodname_classroom % {% data reusables.classroom.supported-lmses %} +## Linking a Blackboard course with a classroom + +You can link your Blackboard course with a classroom in {% data variables.product.prodname_classroom %}. For more information about Blackboard, see the [Blackboard website](https://www.anthology.com/products/teaching-and-learning/learning-effectiveness/blackboard). + +An administrator needs to register your LMS instance with classroom before you can link an LMS course. For more information, see [AUTOTITLE](/education/manage-coursework-with-github-classroom/teach-with-github-classroom/register-a-learning-management-system-with-github-classroom#configuring-blackboard-for-github-classroom). + +1. Sign into your **Blackboard** instance. +1. Select the Blackboard course or organization to integrate with {% data variables.product.prodname_classroom %}. +1. In the right sidebar on the course page, click **Books & Tools**, then click **GitHub Classroom**. Note that the name may be different if your LMS administrator named it something else when registering your LMS. +1. Click **{% data variables.product.prodname_classroom %}**. +1. In {% data variables.product.prodname_classroom %}, select a classroom to link with your LMS course. + + > [!NOTE] This step might give you an error message, "Unable to launch link. The Tool Provider has been disabled by the System Administrator: {% data variables.product.prodname_classroom %}". To resolve this error, ensure that the status of the “{% data variables.product.prodname_classroom %}” tool is set to `Approved`. In the "Admin Panel," click **LTI Tool Providers**. Hover on the name next to {% data variables.product.prodname_classroom %} and click **Approve**. + +Once your course is linked, you can import your roster from your LMS course to your classroom. For more information, see [Importing a roster from your LMS](#importing-a-roster-from-your-lms). + ## Linking a Canvas course with a classroom You can link your Canvas course with a classroom in {% data variables.product.prodname_classroom %}. For more information about Canvas, see the [Canvas website](https://www.instructure.com/canvas/). diff --git a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/register-a-learning-management-system-with-github-classroom.md b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/register-a-learning-management-system-with-github-classroom.md index 6043154c9622..3776bbd78067 100644 --- a/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/register-a-learning-management-system-with-github-classroom.md +++ b/content/education/manage-coursework-with-github-classroom/teach-with-github-classroom/register-a-learning-management-system-with-github-classroom.md @@ -17,6 +17,78 @@ Before you can connect your LMS to a classroom, an administrator for your LMS in {% data reusables.classroom.supported-lmses %} +## Configuring Blackboard for {% data variables.product.prodname_classroom %} + +You can register your Blackboard installation with {% data variables.product.prodname_classroom %} to enable teachers to import roster data into their classrooms. For more information about Blackboard, see the [Blackboard website](https://www.anthology.com/products/teaching-and-learning/learning-effectiveness/blackboard). + +### Step 1. Register {% data variables.product.prodname_classroom %} Developer Keys in the Anthology Developer Portal + +1. Sign into the [Anthology Developer Portal](https://developer.anthology.com/). +1. Click on the **plus sign** in the [My Application](https://developer.anthology.com/portal/applications) page. +1. Click **Manual Registration** in the dropdown menu. +1. On the "Register a new application" configuration screen, set the fields to the following values. + + | Field in the new app configuration | Value or setting | + | :- | :- | + | **Application Name** | `GitHub Classroom`

You can use any name, it will be showed only to administrators. | + | **Description** | `Sync Blackboard course roster to GitHub Classroom` (or something similar) | + | **Domain(s)** | `classroom.github.com` | + | **Group** | Leave the default value or change it according to your institution needs. | + | **My Integration supports LTI 1.3** | Enable the flag.| + | **Login Initiation URL** | `https://classroom.github.com/lti1p3/openid-connect/auth` | + | **Tool Redirect URL(s)** | `https://classroom.github.com/lti1p3/openid-connect/redirect,https://classroom.github.com/context-link` | + | **Tool JWKS URL** | `https://classroom.github.com/.well-known/jwks.json` | + | **Signing Algorithm** dropdown | `RS256` | + | **Custom parameters** | Leave empty. | +1. Click **Register Application**. +1. The Developer Portal will show a screen that contains important information you'll need to input in the next steps of registering your instance in your Blackboard instance and in {% data variables.product.prodname_classroom %} below. Please note them in a safe place and click **Done**. +1. In the table on the "My Applications" page, in the row for the GitHub Classroom application, click on the three dots and then **Manage Placements** in the dropdown menu. +1. Click on the **plus sign**. +1. On the "Register a new placement" configuration screen, set the fields to the following values. + + | Field in the new placement configuration | Value or setting | + | :- | :- | + | **Placement Name** | `GitHub Classroom`

You can use any name, but if you set this to something else, be sure this is communicated to teachers. | + | **Description** | `Sync Blackboard course roster to GitHub Classroom` (or something similar) | + | **Type** dropdown | Course Tool | + | **Allow students access** | Don't enable the flag. | + | **Launch in new window** | Don't enable the flag, unless you want to offer that user experience. | + | **Target link URI** | `https://classroom.github.com/context-link` | + | **Icon URL** | Leave it empty or provide a static URL for the icon. If needed, later in Blackboard can be manually uploaded. | + | **Custom parameters** | Leave empty. | +1. Click **Register Placement**. + +### Step 2. Register {% data variables.product.prodname_classroom %} Developer Keys in Blackboard + +1. Sign into your **Blackboard** instance. +1. In the left sidebar on the home page, click **Admin**, then click **LTI Tool Providers**. +1. On the "LTI Tool Providers" page, click **Register LTI 1.3/Advantage Tool**. +1. Insert the **Client ID** / **Application ID** obtained from the Developer Portal and click **Submit**. +1. Blackboard will show all application data. In this page: + 1. Verify that **Tool Status** is `Approved`. + 1. Verify that **User Fields to be Sent** flags are enabled for "Role in Course", "Name", "Email Address". + 1. Verify that **Allow mark service access** radio button is set to "No". To enable this option, navigate to the LTI Tool Providers in the Admin Panel: + - Select Manage Global Properties + - Under Creation of Tool Provider Links, select radio button “Allow links to any tool provider, but require approval for each new provider” + 1. Verify that **Allow Membership Service Access** radio button is set to "Yes". +1. Click **Submit**. + +### Step 3. Register your developer keys with {% data variables.product.prodname_classroom %} + +1. Go to https://classroom.github.com/register-lms. +1. Fill in the following information: + + * Under "LMS Type", choose "Other" from the dropdown menu. + * "Issuer Identifier": `https://blackboard.com` + * "Domain": The base URL to your Blackboard instance + * "Client ID": The "Client ID" / "Application ID" obtained from the registration of the app in the Anthology Developer Portal. + * "OIDC Initiation URL": The "OIDC auth request endpoint" obtained from the registration of the app in the Anthology Developer Portal. + * "OAuth 2.0 Token Retrieval URL": The "Auth token endpoint" obtained from the registration of the app in the Anthology Developer Portal. + * "Key Set URL": The "Public keyset URL" obtained from the registration of the app in the Anthology Developer Portal. + +1. Click **Register**. +1. You should see the "Successfully registered LMS" banner at the top of the screen, which means that you've registered your LMS instance and teachers can now link their classrooms. + ## Configuring Canvas for {% data variables.product.prodname_classroom %} You can register your Canvas installation with {% data variables.product.prodname_classroom %} to enable teachers to import roster data into their classrooms. For more information about Canvas, see the [Canvas website](https://www.instructure.com/canvas/). diff --git a/content/get-started/exploring-projects-on-github/contributing-to-a-project.md b/content/get-started/exploring-projects-on-github/contributing-to-a-project.md index 57c432826304..834351f3ecfa 100644 --- a/content/get-started/exploring-projects-on-github/contributing-to-a-project.md +++ b/content/get-started/exploring-projects-on-github/contributing-to-a-project.md @@ -16,6 +16,12 @@ redirect_from: - /get-started/quickstart/contributing-to-projects --- +Contributing to a project on {% data variables.product.github %} is an essential skill for developers and collaborators working together to achieve shared goals. Whether you're fixing bugs, adding features, or improving documentation, the process of contributing ensures structured and efficient collaboration. + +By following the {% data variables.product.github %} flow of forking repositories, creating branches, and submitting pull requests, you can propose changes to a project and get feedback without disrupting other people's work. + +This guide provides instructions on contributing to a project using the GitHub UI and the command line. For more information on contributing with GitHub Desktop, see [AUTOTITLE](/desktop/adding-and-cloning-repositories/cloning-and-forking-repositories-from-github-desktop). For the same with GitHub CLI (Command Line Interface), see [AUTOTITLE](/github-cli/github-cli/quickstart). + ## About forking If you want to contribute to someone else's project but don’t have permission to make changes directly, you can create your own copy of the project, make updates, and then suggest those updates for inclusion in the main project. This process is often called a "fork and pull request" workflow. @@ -50,11 +56,9 @@ You've successfully forked the Spoon-Knife repository, but so far, it only exist You can clone your fork with the command line, {% data variables.product.prodname_cli %}, or {% data variables.product.prodname_desktop %}. -{% webui %} - 1. On {% data variables.product.github %}, navigate to **your fork** of the Spoon-Knife repository. {% data reusables.repositories.copy-clone-url %} -{% data reusables.command_line.open_the_multi_os_terminal %} +1. On Mac or Linux, open Terminal. On Windows, open Git Bash. {% data reusables.command_line.change-current-directory-clone %} 1. Type `git clone`, and then paste the URL you copied earlier. It will look like this, with your {% data variables.product.github %} username instead of `YOUR-USERNAME`: @@ -73,133 +77,44 @@ You can clone your fork with the command line, {% data variables.product.prodnam > Unpacking objects: 100% (10/10), done. ``` -{% endwebui %} - -{% cli %} - -{% data reusables.cli.cli-learn-more %} - -To create a clone of your fork, use the `--clone` flag. - -```shell -gh repo fork REPOSITORY --clone=true -``` - -{% endcli %} - -{% desktop %} - -{% data reusables.desktop.choose-clone-repository %} -{% data reusables.desktop.cloning-location-tab %} -{% data reusables.desktop.cloning-repository-list %} -{% data reusables.desktop.choose-local-path %} -{% data reusables.desktop.click-clone %} - -{% enddesktop %} - ## Creating a branch to work on Before making changes to the project, you should create a new branch and check it out. By keeping changes in their own branch, you follow {% data variables.product.github %} flow and ensure that it will be easier to contribute to the same project again in the future. See [AUTOTITLE](/get-started/using-github/github-flow#following-github-flow). -{% webui %} - ```shell git branch BRANCH-NAME git checkout BRANCH-NAME ``` -{% endwebui %} - -{% cli %} - -```shell -git branch BRANCH-NAME -git checkout BRANCH-NAME -``` - -{% endcli %} - -{% desktop %} - -For more information about how to create and manage branches in {% data variables.product.prodname_desktop %}, see [AUTOTITLE](/desktop/making-changes-in-a-branch/managing-branches-in-github-desktop). - -{% enddesktop %} - ## Making and pushing changes Go ahead and make a few changes to the project using your favorite text editor, like [{% data variables.product.prodname_vscode %}](https://code.visualstudio.com). You could, for example, change the text in `index.html` to add your {% data variables.product.github %} username. When you're ready to submit your changes, stage and commit your changes. `git add .` tells Git that you want to include all of your changes in the next commit. `git commit` takes a snapshot of those changes. -{% webui %} - -```shell -git add . -git commit -m "a short description of the change" -``` - -{% endwebui %} - -{% cli %} - ```shell git add . git commit -m "a short description of the change" ``` -{% endcli %} - -{% desktop %} - -For more information about how to stage and commit changes in {% data variables.product.prodname_desktop %}, see [AUTOTITLE](/desktop/making-changes-in-a-branch/committing-and-reviewing-changes-to-your-project-in-github-desktop#selecting-changes-to-include-in-a-commit). - -{% enddesktop %} - -When you stage and commit files, you essentially tell Git, "Okay, take a snapshot of my changes!" You can continue to make more changes, and take more commit snapshots. +When you stage and commit files, you essentially tell Git, "Take a snapshot of my changes." You can continue to make more changes and take more commit snapshots. Right now, your changes only exist locally. When you're ready to push your changes up to {% data variables.product.github %}, push your changes to the remote. -{% webui %} - ```shell git push ``` -{% endwebui %} - -{% cli %} - -```shell -git push -``` - -{% endcli %} - -{% desktop %} - -For more information about how to push changes in {% data variables.product.prodname_desktop %}, see [AUTOTITLE](/desktop/making-changes-in-a-branch/pushing-changes-to-github-from-github-desktop). - -{% enddesktop %} - ## Making a pull request -At last, you're ready to propose changes into the main project! This is the final step in producing a fork of someone else's project, and arguably the most important. If you've made a change that you feel would benefit the community as a whole, you should definitely consider contributing back. +Creating a pull request is the final step in producing a fork of someone else's project. When you've made a beneficial change and want to propose it to the original repository, you'll create a pull request for a maintainer to review. -To do so, head on over to the repository on {% data variables.product.github %} where your project lives. For this example, it would be at `https://github.com//Spoon-Knife`. You'll see a banner indicating that your branch is one commit ahead of `octocat:main`. Click **Contribute** and then **Open a pull request**. +To do so, navigate to the repository on {% data variables.product.github %} where your project lives. For this example, it would be at `https://github.com//Spoon-Knife`. You'll see a banner indicating that your branch is one commit ahead of `octocat:main`. Click **Contribute** and then **Open a pull request**. {% data variables.product.github %} will bring you to a page that shows the differences between your fork and the `octocat/Spoon-Knife` repository. Click **Create pull request**. {% data variables.product.github %} will bring you to a page where you can enter a title and a description of your changes. It's important to provide as much useful information and a rationale for why you're making this pull request in the first place. The project owner needs to be able to determine whether your change is as useful to everyone as you think it is. Finally, click **Create pull request**. -## Managing feedback - -Pull requests are an area for discussion. Don't be offended if the project owner rejects your pull request, or asks for more information on why it's been made. Even if the project owner chooses not to merge your pull request, your changes still exist in your fork. It could be that someone else will find your fork much more valuable than the original project. - -## Finding projects - -You've successfully forked and contributed back to a repository. Go forth, and -contribute some more!{% ifversion fpt %} For more information, see [AUTOTITLE](/get-started/exploring-projects-on-github/finding-ways-to-contribute-to-open-source-on-github).{% endif %} - {% ifversion copilot %} ## Familiarizing yourself with a project diff --git a/data/reusables/classroom/supported-lmses.md b/data/reusables/classroom/supported-lmses.md index b47bd761052e..1e9255eb0df2 100644 --- a/data/reusables/classroom/supported-lmses.md +++ b/data/reusables/classroom/supported-lmses.md @@ -7,6 +7,7 @@ Using LTI helps keep your information safe and secure. LTI is an industry-standa {% data variables.product.company_short %} has tested and verified registration, connection and the import of roster data from the following LMSes into {% data variables.product.prodname_classroom %}. +* Blackboard (This is a community supported option) * Canvas * Moodle * Sakai diff --git a/src/events/components/Survey.tsx b/src/events/components/Survey.tsx index 581bbedacdb6..d87ca37c37e5 100644 --- a/src/events/components/Survey.tsx +++ b/src/events/components/Survey.tsx @@ -201,7 +201,7 @@ export const Survey = () => {