MozillaWiki

ReleaseEngineering/Contribute: Difference between revisions

Page Discussion

ReleaseEngineering/Contribute (view source)

Revision as of 07:13, 8 October 2018

1,145 bytes removed ,  8 October 2018
Remove obsolete content
(Added glossary of terms)
(Remove obsolete content)
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 to help with. Feel free to leave a comment in the bug asking how to get started.
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 ====
 
The quickest and easiest way to get up and contributing with Release Engineering is by running [[ReleaseEngineering/Tupperware|Tupperware]]
 
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.


=== First Projects ===
=== First Projects ===
Line 42: Line 29:
The Mozilla Project has the idea of a 'Good First Bugs' and 'Mentored Bugs'. A 'Good First Bug' is a bug which has been marked as a good first step into the Project and a 'Mentored Bug' is a bug which an experienced contributors has marked as one they will help a new contributor to fix.
The Mozilla Project has the idea of a 'Good First Bugs' and 'Mentored Bugs'. A 'Good First Bug' is a bug which has been marked as a good first step into the Project and a 'Mentored Bug' is a bug which an experienced contributors has marked as one they will help a new contributor to fix.


Here you can see [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=RelEng%20good%20first%20bugs&sharer_id=464696 RelEng good first bugs].
Here you can see [https://bugzilla.mozilla.org/buglist.cgi?cmdtype=dorem&remaction=run&namedcmd=RelEng%20good%20first%20bugs&sharer_id=464696 RelEng good first bugs], and [https://codetribute.mozilla.org/projects/releng mentored bugs]. Don't be discouraged if you don't understand much (or anything!) about the bug, that's completely normal. Just ask for help and you'll be a contributor in no time.
 
Mozilla Releng has both! You can see a list of them [http://www.joshmatthews.net/bugsahoy/?releng=1 here]. Don't be discouraged if you don't understand much (or anything!) about the bug, that's completely normal. Just ask for help and you'll be a contributor in no time.


==== RelengAPI ====
==== Mozilla Release Services ====


[https://github.com/mozilla/build-relengapi RelengAPI] is our new interface to Release Engineering services. It's a Flask application, with services registered on it as blueprints. We're aiming for it to be a modern, scalable architecture for the services we provide.
[https://github.com/mozilla/release-services/ Release Services] is our interface to Release Engineering services.  


We're building new services on top of it, and porting old ones to the new structure. Porting an existing application could be a great way to gain familiarity with a big chunk of the existing architecture at your own pace.
We're building new services on top of it, and porting old ones to the new structure. Porting an existing application could be a great way to gain familiarity with a big chunk of the existing architecture at your own pace.


Plenty of [https://api.pub.build.mozilla.org/docs/ documentation] exists, and there's a [https://github.com/IanConnolly/build-relengapi-template example and template application] available.  
Plenty of [https://github.com/mozilla/release-services/ documentation] exists, and there's an irc channel at #release-services on [https://developer.mozilla.org/en-US/docs/Mozilla/QA/Getting_Started_with_IRC irc.mozilla.org].


Ask the team how you can help, there's always a bunch to do!
Ask the team how you can help, there's always a bunch to do!
Line 62: Line 47:
=== IRC ===
=== IRC ===


Come find us in irc.mozilla.org channel: '''#releng''' with your questions, we want you to be able to successfully work on code and submit useful patches so don't be afraid to ask about whatever is blocking you.
Come find us in irc.mozilla.org channel: '''#ci''' with your questions, we want you to be able to successfully work on code and submit useful patches so don't be afraid to ask about whatever is blocking you.


=== Planet Releng ===
=== Planet Releng ===


To help the team keep in touch with each other and contributors, many members of Mozilla Releng write regular blog posts on what they're doing. You can find an RSS feed of those posts [http://planet.mozilla.org/releng/ here].
To help the team keep in touch with each other and contributors, many members of Mozilla Releng write regular blog posts on what they're doing. You can find an RSS feed of those posts [http://planet.mozilla.org/releng/ here].
Highly recommended is the 'This Week in Releng' series, which is a round-up of what the team have been up to in the past week.


=== Glossary of terms ===
=== Glossary of terms ===


If you ever feel lost with all the jargon around you, here's a [https://docs.google.com/document/d/1VcEjW82jBxr77aYi3TVaha9S4uJwAkwEapXnhhMwcgg/edit# handy reference (Google doc)] .
If you ever feel lost with all the jargon around you, here's a [https://docs.google.com/document/d/1VcEjW82jBxr77aYi3TVaha9S4uJwAkwEapXnhhMwcgg/edit# handy reference (Google doc)] .
NThomas
Confirmed users
4,293

edits

Retrieved from "https://wiki.mozilla.org/Special:MobileDiff/1202048"