Before you file a bug or new review set, it’s often helpful to chat with other
developers. The #openstack-ironic channel is a good place to start, and if
you don’t have IRC (or would prefer email), openstack-dev@lists.openstack.org
is the mailing list for all OpenStack projects. As the name implies, that
mailing list is for all OpenStack development, so it’s often harder to get
attention on your particular issue.

Bifrost requires a valid OpenStack contributor agreement to be signed before
code can be accepted. Details can be found in the development workflow link
above.

Code isn’t committed directly (so pull requests won’t work); instead, the
code is submitted for review through Gerrit via git review, and once its
been sufficiently reviewed it will be merged from there.

From that point on, the link the git review command generated is
the place to do final tweaks. When its approved, the code
will be merged in automatically.

If you propose a new feature and are unable to complete it, please
let the community know by commenting in the review set indicating
that someone else is free to carry on your change. If the core
reviewers observe reviews that are not being actively worked on,
we are likely to inquire with you. If a review is untouched and the
owner of the review is unreachable for a lengthy period of time,
such as three to six months, the core reviewers may abandon the
change as we do not utilize auto-abandon.

Playbook conditionals utilizing variables intended as booleans,
should make use of the |bool casting feature. This is due
to command line overrides are typically interpreted as strings
instead of booleans. Example: