source/get-involved.html

---
layout: default
title: Get Involved
---
<div id="page-header-gradient" class="ui vertical inverted top-header segment">
    {% include inner-nav.html %}
    <div class="ui container">
        <div class="ui relaxed stackable grid">
            <div class="sixteen wide column left aligned">
                <div class="ui hidden divider"></div>
                <h1 class="page-title">
                    Contribute to OpenSource
                </h1>
                <div class="ui hidden divider"></div>
            </div>
        </div>
    </div>
</div>
<div class="ui vertical theme segment">
    <div class="ui very relaxed stackable container grid">
        <div class="row stackable middle aligned">
            <div class="four wide column left aligned middle aligned">
                <img class="ui middle aligned massive image"
                     data-position="bottom center"
                     src="/assets/img/contribute.png">
            </div>
            <div class="twelve wide column left aligned middle aligned">
                <p>You don't need to be a software developer to contribute to Apache Airavata. To be successful this
                    project requires a huge range of different skills, levels of involvement and degrees of technical
                    expertise. So, if you want to get involved in Apache Airavata, there is almost certainly a role for
                    you.</p>
                <div class="ui hidden divider"></div>
            </div>
            <div class="sixteen wide column">
                <div class="theme-h2-header">Ways to Contribute</div>
                <h2 class="theme-h2-sub-header">We are looking for people to</h2>
                <div class="ui hidden divider"></div>
                <div class="ui ordered list">
                    <div class="item">provide feedback</div>
                    <div class="item">write or update documentation</div>
                    <div class="item">help new users</div>
                    <div class="item">recommend the project to others</div>
                    <div class="item">test the code and report bugs</div>
                    <div class="item">fix bugs and submit patches</div>
                    <div class="item">give us feedback on required features</div>
                    <div class="item">write and update the software</div>
                    <div class="item">create artwork</div>
                    <div class="item">translate to different languages</div>
                    <div class="item">anything you can see that needs doing</div>
                </div>
                <h2 class="theme-h2-sub-header">Mailing Lists</h2>
                <p>Your first engagement with the project should be to subscribe to our mailing lists.</p>
                <h2 class="theme-h2-sub-header">
                    Decision Making

                </h2>
                <p>The most important thing about engaging with any Apache project is that everyone is equal. All people
                    with an opinion are entitled to express that opinion and, where appropriate, have it considered by
                    the community.

                </p>
                <p>To some the idea of having to establish consensus in a large and distributed team sounds inefficient
                    and frustrating. Don't despair though, The Apache Way has a set of simple processes to ensure things
                    proceed at a good pace.</p>
                <p>

                    In ASF projects we don't like to vote. We reserve that for the few things that need official
                    approval for legal or process reasons (e.g. a release or a new committer). Most of the time we work
                    with the consensus building techniques documented below.</p>

                </p>
                <h2 class="theme-h2-sub-header">
                    Lazy Consensus

                </h2>
                <p>Lazy consensus is the first, and possibly the most important, consensus building tool we have.
                    Essentially lazy consensus means that you don't need to get explicit approval to proceed, but you
                    need to be prepared to listen if someone objects.

                </p>
                <h2 class="theme-h2-sub-header">Consensus Building
                </h2>
                <p>Sometimes lazy consensus is not appropriate. In such cases it is necessary to make a proposal to the
                    mailing list and discuss options. There are mechanisms for quickly showing your support or otherwise
                    for a proposal and building consensus amongst the community.

                </p>
                <p>Once there is a consensus people can proceed with the work under the lazy consensus model.

                </p>
                <h2 class="theme-h2-sub-header">Voting</h2>
                <p>Occasionally a "feel" for consensus is not enough. Sometimes we need to have a measurable consensus.
                    For example, when voting in new committers or to approve a release.</p>
                <h2 class="theme-h2-header">How to contribute</h2>
                <div class="ui hidden divider"></div>

                <div class="theme-h2-sub-header">Apache Airavata Contribution Guide</div>
                <div class="ui hidden divider"></div>

                <p>Welcome and thank you for your interest in contributing to Apache Airavata! This guide will take you
                    through the process of making contributions to the airavata code base.</p>

            </div>
        </div>
    </div>
</div>