How to contribute
Installation procedure (for developers)
If you want to help maintaining and improving the tqec package, you will need
to install a few more packages than the regular installation. It is also
recommended to use an editable installation.
# Clone the repository to have local files to work on
git clone https://github.com/QCHackers/tqec.git
# Install the library with developer dependencies
python -m pip install -e 'tqec[all]'
# Go in the tqec directory and enable pre-commit
cd tqec
pre-commit install
You can now start contributing, following the rules explained in the next sections.
How to contribute
1. Look at issues
Start by looking at the issues list. Issues can be filtered by tags. Below are a few of the most interesting tags:
good first issue for issues that have been judged easy to address without prior knowledge on the code base.
backend for issues related to the Python code.
Pick one issue that you want to work on. We emphasize on want: this is an open source project, so do not force yourself to work on something that does not interest you.
3. Create a specific branch for each issue
If you are part of the QCHacker community, you will be able to create a branch directly in the QCHacker/tqec repository. If you are not, you can fork the QCHacker/tqec repository on your own account (click here) and create a branch there.
4. Work in your branch and submit a pull request
You should only work on the branch you just created. Implement the fix you envisionned to the issue you were assigned to.
If, for personnal/professional reasons, lack of motivation, lack of time, or whatever the reason for which you know that you won’t be able to complete your implementation, please let us know in the issue so that we can un-assign you and let someone else work on the issue.
Once you think you have something that is ready for review or at least ready to be read
by other people, you can
submit a pull request (PR)
on the main branch of the QCHacker/tqec repository. In the PR message, try to
provide as much information as possible to help other people understanding your code.
5. Merge the PR
Once your code has been reviewed and accepted by at least one of the developers, you
will be able to merge it to the main branch.
You (the PR owner) are responsible to click on the “Merge” button. If you prefer someone
else to do it, you should send a clear comment asking for it.
2. Comment on one or more issues
Once you have found one or more issue(s) you want to work on, send a comment on these issues to:
make your interest public,
ask for updates, as the issue might not be up-to-date.
One of the lead developers will come back to you and assign you the issue if
nobody is already working on it,
the issue is still relevant.