Help | Getting Started | Publishing | Policy Compliance | Copilot

Need Help?

First, please make sure you have read and followed all of the instructions below. If you still need help, please request assistance via the Trimble GitHub Charlie Page.

🔍 Already set up? You can Go straight to the Trimble GitHub Organization

Getting Started

Please be sure you read through the following bullet points and take any necessary action.

• ⭐ Add the GitHub - Trimble application from your Okta homepage.
• ⭐ Create a GitHub account if you don't already have one.
  • Update: It is recommended that you create a Trimble specific GitHub account rather than using an existing personal GitHub username. This is particularly important if you want to use GitHub Copilot as using a personal GitHub account risks combining personal data and business data.
• ⭐ Replace the default GitHub account avatar with something that uniquely identifies you.
• ⭐ Read the Contributor Guidelines. No really, we mean it, read them!
• ⭐ Join the Trimble GitHub Channel on Charlie!
• 🎯 Now you are ready to request to join!

Request to Join an Organization

Complete the request to join form to request access to the trimble-oss organization.

If you want to join a different organization, you can still complete the request to join form to receive a Trimble license for GitHub. However, you will also need to specifically request access to that organization by finding and contacting an administrator for that organization.

Publishing

Ready to publish a project to the public?

• Read and ensure all requirements are met in the Trimble OSS - Open Source Publication Policies and Procedures
• Contact trimble-oss-contrib-admins-ug@trimble.com when you are ready for a pre-publication review and we will work with you to get your project published

Open & Inner Source Policy Compliance

All repositories in the trimble-oss GitHub organization must conform to the Open and Inner Source Publication Policies and Procedures, which are maintained in the oss-overseer repository. See Open and Inner Source Publication Policies and Procedures for detailed requirements.

Automated Audits & Enforcement

A weekly automated audit checks every public and internal repository against these policies. Results are published as a Policy Audit Report discussion and committed to the oss-overseer reports directory. Repositories with unresolved MUST violations may be automatically delisted (public → internal, internal → private). Once all violations are resolved, repositories are automatically relisted.

Getting Compliant

To bring a repository into compliance, maintainers can use the oss-compliance Copilot prompt in VS Code with GitHub Copilot enabled.

For the full policy details, see the Open and Inner Source Publication Policies and Procedures.

GitHub Copilot

🔍 Looking for GitHub Copilot?

• Request a License
• Read the Getting Started Guide