Innersource is a development practice where an organization adopts open-source development methodologies within its own internal environment. The primary goal of innersource is to break down silos and encourage collaboration across different teams within the organization.

Sharing Code Between Teams:

Option B is correct because innersource involves sharing code between teams within the organization, similar to how open-source communities share code across the public domain. This practice fosters collaboration, improves code quality, and allows for reuse of code, reducing duplication of efforts.

Incorrect Options:

Option A is incorrect because adopting open-source code into the organization is related to using open-source software, not specifically to innersource practices.

Option C is incorrect because removing open-source code from the organization is contrary to the principles of both open source and innersource.

Option D is incorrect because making all repositories publicly accessible refers to open source, not innersource. Innersource typically involves keeping code internal to the organization.

GitHub Docs: What is Innersource?

Innersource Commons: The Basics

Forking a repository on GitHub is a common practice, especially when contributing to open-source projects or when you want to build on existing work. Here are the two main reasons for forking a repository:

B . To propose changes to the base repository:

One of the primary reasons for forking a repository is to make changes or improvements that you can later propose to the original repository (often called the 'upstream' repository). This is typically done through a pull request. By forking the repository, you get your own copy of the project where you can freely experiment, make changes, and then propose those changes back to the original project.

C . To create a new repository based on an existing one:

Forking is also used to create a new repository that is a copy of an existing one. This allows you to work on the project independently of the original repository, effectively creating a new direction for the project or using it as a starting point for a different purpose. This is particularly useful for customization, experimentation, or when you want to build something different while still leveraging the existing codebase.

Explanation of Other Options:

A . To create an issue or open a discussion:

This is incorrect because creating an issue or opening a discussion can be done directly on the original repository without needing to fork it. Forking is unnecessary for these actions.

D . To create a new branch to develop a new feature:

While creating a new branch is related to development, it does not require a fork. Branches are typically created within the same repository to work on new features. Forking is used when you need an entirely separate copy of the repository.

Given this information, the correct answers are B and C.

GitHub Documentation: Fork a repo

GitHub Documentation: About forks

To contribute to a GitHub repository, a user typically needs to be able to create branches, push changes, and open pull requests. These actions require Write access, which is the minimum level of access needed to contribute code directly to a repository.

Write Access:

Option D is correct because 'Write' access allows users to contribute to the repository by pushing changes, creating branches, and opening pull requests. This is the minimum required access level for contributing code.

Incorrect Options:

Option A (Read) is incorrect because 'Read' access only allows viewing the repository, not making changes.

Option B (Triage) is incorrect because while Triage access allows managing issues and pull requests, it does not allow pushing code.

Option C (Maintain) is incorrect because 'Maintain' access includes additional permissions beyond those needed for basic contributions, such as managing repository settings.

GitHub Docs: Repository Roles for an Organization

In GitHub Discussions, several default categories are provided to help organize conversations within a project. One of the default categories is Show and tell. This category is designed for users to showcase their work, share progress, or discuss achievements with the community. The other options listed (Bug report, Daily check-in, Security concern) are not default categories but could be custom categories created by the repository maintainers.

A user's GitHub profile typically includes public information such as a personal biography, profile picture, and a list of public repositories. More sensitive information, like email addresses and passwords, is not publicly displayed.

Personal Biography and Profile Picture:

Option A is correct because these are standard elements displayed on a user's public GitHub profile. This information is meant to provide a brief introduction to the user and their interests or skills.

Incorrect Options:

Option B is incorrect because public SSH keys may be associated with a user's account but are not displayed by default on the profile page.

Option C is incorrect because private repositories are not listed on a public profile.

Option D is incorrect because a user's email address and password are private information and not displayed on their public profile.

GitHub Docs: Managing Your Profile