Version 13

    As an open source project we are always on the lookout for community members that want to step up and help with the project.  There are lots of ways to help, and this article will help you get started!

    Help Others

    Have experience with mobile or HTML5 based technologies?  Interested in sharing your knowledge? 


    Join the forum discussions and share what your working on, or struggling with.  For more immediate gratification join the IRC channel (#aerogear).  There are are usually a good bunch of people hanging out there.  Ask your questions, share your experience, or just make jokes :-)


    If you've got ideas for the project, or want to discuss ways to improve AeroGear join the aerogear-dev mailing list, or create a forum post in the development forums and let your ideas be heard.  If you've already done that, or found an issue with our stuff check out the next section.


    Found An Issue?

    Have you run into an issue with one of our examples, sites, or have a suggestion?  The best place to start is probably talking about it in the forums or IRC.  If you've already done that, or just want to create the issue please do at


    We only ask that you review our AeroGear Jira Usage and Guidelines and use your noodle!  Help the community help you :-)

    Fix an Issue!

    Your ready to start taking action, dig into an issue, and update some code!  Excellent!!


    The first recommended step is to communicate with the project team.  This way you can get any advice, or feedback on your plans.


    The best ways to do this are through:

    Pick your poison

    If what you want to work on is already in jira, then ask to have it assigned to you (see communicate section above).  If there is no jira, go ahead and make one as described above, and in the AeroGear Jira Usage and Guidelines.

    Sign the JBoss community license agreement

    This is pretty standard stuff for open source.  Just use your JBoss user, and pick AeroGear for the project here:


    bq. []

    Follow AeroGear's coding conventions and style

    This link has the IDE settings, and conventions that should be followed for all AeroGear source code.  Be sure to use the aerogear branch as it contains the correct license and copyright information.  The aerogear branch should be the default branch.


    bq. []

    Follow AeroGear's github workflow

    Follow our document that will walk you through how to work with GitHub, and the AeroGear repositories: AeroGear GitHub Workflow & Instructions.

    Get Fame and Applause from Everyone!!

    Talk about your work, create a blog, or tweet about it using the #AeroGear hashtag!