blob: 7a311486149ee9672b65d5b01203c43bfd304a1f [file] [log] [blame] [view]
---
layout: website-normal
title: Developers
started-pdf-exclude: true
children:
- code/
- how-to-contribute.md
- /guide/dev/
- committers/
- code-standards.md
- links.md
- { link: 'http://github.com/apache/brooklyn', title: 'GitHub' }
- { link: 'https://issues.apache.org/jira/browse/BROOKLYN', title: 'Bug Tracker (JIRA)' }
---
Hello developers!
These pages are aimed at people who want to get involved with reading, changing, testing and otherwise
working with the bleeding edge Brooklyn code.
<div class="panel panel-danger">
<div class="panel-heading" markdown="1">
#### Caution
</div>
<div class="panel-body" markdown="1">
As these pages contain information about accessing the bleeding edge code and artifacts produced from it,
you should be aware that the code and binaries you will encounter may be unstable.
The Apache Software Foundation has not performed the level of validation and due diligence done
on formally released artifacts.
Proceed only if you understand the potential consequences of using unreleased code
and are comfortable doing so.
</div>
</div>
We heartily welome contributions and new members.
There's nothing official needed to get involved;
simply come say hello somewhere in the [community](../community/index.md):
- [Mailing lists](../community/mailing-lists.md)
- [IRC channel](../community/irc.md)
- [JIRA for bug tracking](https://issues.apache.org/jira/browse/BROOKLYN)
Then [get the code](code/).
When you have a blueprint or an improvement you want to share,
there are a few instructions to note on [how to contribute](how-to-contribute.md).
If you're looking to learn more about the codebase itself,
have a look at [Developer Guide](/guide/dev/).
There are also a number of [development bookmarks](links.md) for the tools we use
(git, jenkins, jira).