Confirmed users
22
edits
Ffledgling (talk | contribs) (Additional info to prevent new contributors from wasting time setting up Tupperware when the project they want to work on is (a) not supported or (b) does not need it) |
|||
| Line 21: | Line 21: | ||
=== Getting Started === | === Getting Started === | ||
Lots of projects have now begun to use Tupperware, but there are many others that are yet to make this move. | |||
If you're interested in contributing to Release Engineering, find a project or bug you like and that'll help decide whether you need to setup and run Tupperware. | |||
If your project does not use Tupperware, feel free to leave a comment in the bug asking how to get started. | |||
We'll reply soon. We promise :) | |||
==== Tupperware ==== | ==== Tupperware ==== | ||
| Line 28: | Line 34: | ||
Great for keeping an unpolluted development environment, testing patches and enabling new contributors to join the effort by lowering the barriers to entry (being one of the biggest deterrents to potential new contributors). | Great for keeping an unpolluted development environment, testing patches and enabling new contributors to join the effort by lowering the barriers to entry (being one of the biggest deterrents to potential new contributors). | ||
Vagrant is used as a quick and easy way to provision the docker apps and make the setup truly plug n' play. The current setup only has a single Vagrantfile which launches BuildAPI and BuildBot, with their dependency apps RabbitMQ and MySQL. | Vagrant is used as a quick and easy way to provision the docker apps and make the setup truly plug n' play. The current setup only has a single Vagrantfile which launches BuildAPI and BuildBot, with their dependency apps RabbitMQ and MySQL. | ||
=== First Projects === | === First Projects === | ||