What to contribute

We are always looking for contributions to the Open Build Service.

In particular, this community seeks the following types of contributions:

• code: contribute your expertise in an area by helping us expand the Open Build Service
• ideas: participate in an issues thread or start your own to have your voice heard.
• copy editing: fix typos, clarify language, and generally improve the quality of the content of the Open Build Service

Read this guide to understand what you can contribute to do that.

What code to contribute?

Once you are clear on how to contribute code here's a list of things the Open Build Service especially will benefit from.

Good first Ruby on Rails contributions

We maintain a list of bugs and features that we think are easy to start with for the Ruby on Rails application that serves the user and the API interface of the OBS.

If you are new to OBS and/or new to Ruby on Rails this is a good starting point to become a regular contributor to this part of the OBS.

Address Ruby on Rails Technical Debt / Anti-Patterns

We maintain a list of technical debt we took on and have have the obligation repay some time...

https://trello.com/b/yLs6IuoT

If you are a Ruby on Rails expert this is a good starting point to find things worth working on. Many of them include introducing new software design patterns to the code base, major architectural changes and fixing complicated issues. Very good opportunities to get exposure for your Rails kung-fu!

Which ideas to contribute?

Which writing to contribute?