Open source contributors are instrumental in ensuring the success and advancement of open source projects, and creating a smooth and efficient onboarding process for contributors significantly enhances the likelihood of success.
Below is a guide that outlines essential steps for both open source maintainers and contributors to expedite the onboarding process. By following these guidelines, maintainers can establish an environment that welcomes contributors and allows them to quickly integrate into the project. And contributors can efficiently get up to speed and start making valuable contributions.
Specific features usually reserved for Enterprise users may be required for certain open source projects. Our team is ready to help by enabling the Enterprise features necessary for your open source project. Contact us to find out more.
Create an account on the ActiveState Platform. If you plan on using the runtime as-is, without changing dependencies, you can skip this step and move straight to accessing the project.
Access the project, git repo, and install the State Tool by downloading the project via your command prompt. Enter the “Install via command prompt” code posted by the project’s maintainer directly into your command terminal.
To begin working on the project, it may help to integrate your IDE with your ActiveState runtime. The following IDEs are supported
After downloading and installing the project, you may need to create a copy of the main project (provided the project maintainer has enabled these features). The contribution guidelines may specify that you fork from the original project, while others may prefer you branch from the original project before merging. ActiveState supports both forking and branching.
While forking will create an independent copy of the project, branching can be kept in sync with the dependencies of the main project as they change. Depending on the project requirements branches and multiple operating systems may be needed.
After completing work on the project, you can add, remove, or change packages (or package versions) on your branch without affecting the main project branch.
In the future, enter state shell <orgname/projectname>
to activate your project and check the current branch by entering state branch
. Enter state switch <branchname>
to switch to the correct branch if needed.
If you have made any changes to the project, you can push your changes using the state push
command. These changes will be pushed to the current working branch.