Skip to content
Switch branches/tags
Go to file
3 contributors

Users who have contributed to this file

@berezovskyi @OASIS-OP-Admin @jorydotcom


When contributing to this repository, please first discuss significant changes you wish to make via issue, email, or any other method with the owners of this repository before making a change.

Please note we have a code of conduct, please follow it in all your interactions with the project.

Communication channels


One of the best ways to communicate with the rest of the project contributors is by opening an issue!

Discussions and announcements

Longer discussions can be taken on the Discourse forum or via the mailing list.

General announcements will be posted via multiple channels including blog posts under (RSS). Please send any general questions about OASIS Open Projects to staff at Information about the Open Projects program can be found at


OSLC community has used Slack for a long while and it will become home to the Open Project discussions from now on. Use this invite to join our Slack channel.

Online Meetings

The OSLC Open Project general call takes place once a week. Everyone is welcome to join the call:

Join meeting:

The meeting minutes are edited in Previous minutes can be found under

Meeting ID: 2979764690#

One tap audio Dial In: +15124022718,,,,2979764690# (US) or +498938038719,,,,2979764690# (Germany) Looking for a different dial in number? Please see:

Import OSLC OP calendar (iCal).

Unfortunately, Jitsi functionality is limited in Safari (screen-sharing does not work) and on Firefox it uses considerable CPU resources and hangs sometimes. Please try using Chrome or Brave if you encounter significant problems.

Git Workflow

We prefer you submit PRs from your own fork of the project. Please fork the project and create a new branch for your PR.

Pull Request Process

  1. Ensure any install or build dependencies are removed before the end of the layer when doing a build.
  2. Update relevant documentation with any details of any changes, including those that affect the interface, build process, environment variables, and so on.
  3. If you have write access to the repoository, you may merge the Pull Request in once you have the sign-off of two other developers. If you do not have permission to do that, you may request the second reviewer to merge it for you.
  4. You are required to sign our CLA before your PR can be merged. This is handled via bot and only needs to be signed once.

About the CLA Bot

Once you've submitted a Pull Request, the CLA Assistant bot will automatically check to see whether you have signed the Individual CLA. If you have already done so, this check will pass. If not, the cla check does not pass and the bot will comment on the PR with a link and instruction for you to click and sign the CLA electronically via GitHub. If you use different GitHub accounts for work and personal use, please make sure you are signed in to the correct account.