OSS Contributions
Contributions to OSS
The Developer Advocacy team believes in Open Source and wants to lead by example, contributing to GitLab and the OSS ecosystem. Our workshops, community activities and projects are documented in the projects overview.
Projects maintained by Developer Advocates
We organize our projects in the Developer Advocacy group. A few examples are:
Contribution Examples
GitLab
- GitLab CI/CD Pipeline Efficiency documentation sourcing from the CI Monitoring webcast
- CI/CD Templates: Support the default branch, shift to main
Prometheus
HashiCorp Waypoint
- Documentation
- Blog posts
- GitLab Integration
- Demo
- Community
Definition of Contributions
Contributions are “more than just code” and are often times hard to measure. Our team tries to start with a small subset and update this section over time.
- Source Code
- Documentation
- Tutorials and blog posts
- Workshops and trainings
- Issue discussion, resolving bugs and suggesting feature design/architecture
- Package and release distribution
- Help on community forums and social media
Resource and Time Dedication
Developer Advocates are encouraged to find time every week for Open Source contributions.
Measurement
We aim to measure this in the form of submitted issues, MR/PRs and commit URLs where applicable.
Contribution Areas
It can be hard to decide, or make a one-time contribution a permanent engagement in a project, leading the way to maybe help maintain it in the future. As a first iteration, we define the requirements for qualifying projects:
- Use them on a daily basis (e.g. CLI tools)
- Help you and your environment (e.g. a calendar app)
- Benefits the ecosystem and makes processes easier
We focus on languages and frameworks where we have the most experience: Golang, C/C++, JS, Ruby, .NET, etc.
e889d608)
