Contribute to OpenSource

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.

Ways to Contribute

We are looking for people to:

  1. provide feedback
  2. write or update documentation
  3. help new users
  4. recommend the project to others
  5. test the code and report bugs
  6. fix bugs and submit patches
  7. give us feedback on required features
  8. write and update the software
  9. create artwork
  10. translate to different languages
  11. anything you can see that needs doing

Mailing Lists

Your first engagement with the project should be to subscribe to our mailing lists.

Decision Making

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.

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.

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.

Lazy Consensus

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.

Consensus Building

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.

Once there is a consensus people can proceed with the work under the lazy consensus model.


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.

How to contribute

Apache Airavata Contribution Guide

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.

Engage with the community

Identify an issue or documentation that you want to fix or improve. Search JIRA and the mailing list to see if it’s already been discussed.

Create an issue in JIRA

If it’s a bug or a feature request, open a JIRA issue. Create a sample that you can use for prototyping the feature or demonstrating the bug. If creating a sample is time consuming, write steps to reproduce the issue. Attach this sample to the JIRA issue if it’s representing a bug report.

Create a pull request in GitHub

Checkout the source code. Create a pull request (PR) in GitHub for the change you're interested in making. The comment section of the PR must contain a link to the JIRA issue. Please also reference the issue in the commit message, and make sure it properly describes the changes that have been made and their purpose.

Some good references for working with GitHub are below. We ask that you keep your change rebased to master as much as possible, and we will ask you to rebase again if master has moved before accepting your patch.

Comment the issue in JIRA

Finally, add a comment in the JIRA issue with a link to the pull request so we know the code is ready to be reviewed.

The review process

The airavata community will need to review your pull request before it is merged. If we are slow to respond, feel free to also email the dev mailing list:

During the review process you may be asked to make some changes to your submission. While working through feedback, it can be beneficial to create new commits so the incremental change is obvious. This can also lead to a complex set of commits, and having an atomic change per commit is preferred in the end. Use your best judgement and work with your reviewer as to when you should revise a commit or create a new one.

A pull request is considered ready to be merged once it gets at lease one +1 from a reviewer. Once all the changes have been completed and the pull request is accepted, it must be rebased to the latest upstream version. It is also a good idea to squash all the commits into a single one, since this will allow us to generate a clean patch and merge it properly.

Accepting Contributions

Developers with Airavata Commit access should read Accepting Contribtions on steps to accept the contributed code

伊人久久大香线蕉av一区 欧美激情做真爱牲交视频 av无码一区二区三区四区 精品国产不卡一区二区三区 久久精品国产一区二区三区不卡 乱人伦人妻中文字幕 国产精品久久久久久不卡 国产无套中出白浆电影 亚洲VR国产美女精品久久久久 国产三级精品三级在线专区 国产精品v欧美精品v日韩精品 日韩精品国产另类专区 欧美日韩综合精品视频一区二区 无码孕妇孕交视频在线观看 一级欧美一级日韩片中文字幕 亚洲欧洲自拍拍偷午夜色无码 午夜色午夜视频之日本 中文国产成人精品久久不卡 亚洲精品午夜国产va久久成人 亚洲国产成年私人影院 亚洲成av人片天堂网无码 美女健身大战日籍男优直到高潮 国产乱子伦一区二区三区 无码国内精品久久人妻 久久精品国产精品青草app 精品国精品国产自在久国产不卡 热久久国产欧美一区二区精品 伊人久久大香线蕉在观看 熟妇的奶头又大又粗视频 人妻 清高 无码 中文字幕 男人狂桶女人出白浆免费视频 日本亚洲色大成网站www 日韩欧美一区二区三区 白俄罗斯毛茸茸bbwbbw 欧美精品久久天天躁 亚洲国产另类久久久精品 日韩av无码精品色午夜 日日碰日日摸夜夜爽无码 欧洲熟妇色XXXX欧美老妇 亚洲综合色丁香婷婷六月图片 日韩av片无码一区二区不卡 国产精品18久久久久久 好爽…又一高潮了毛片视频一区 亚洲熟女乱色一区二区三区 亚洲欧美日韩综合俺去了 公与熄完整版hd高清播放av网 久久天天躁狠狠躁夜夜av 1区2区3区4区产品乱码木鱼天 天天爱天天做天天爽 毛茸茸的又肥又大的岳 一边摸一边桶一边脱免费视频 少妇被爽到高潮动态图 亚洲中文无码永久在线电影 永久免费看a片无码网站vr 国内精品伊人久久大香线焦 曰批全过程免费视频播放 亚洲国产成人无码av在线影院 日本熟妇乱人伦A片免费高清 高潮亚洲AV制服丝袜日韩高清 日本一区二区毛多水多 嘿咻嘿咻免费区在线看吃奶头 国自产拍av在线天天更新 一区精品免费观看|亚洲日本中文字幕天天更新 肉丝肉足丝袜人妻在线无码 无码福利一区二区三区 欧美综合自拍亚洲综合图片区 亚洲国产日韩欧美一区二区三区 制服丝袜AV无码专区丝袜AV 又大又粗欧美黑人a片 无码国产激情在线观看 国产av天堂亚洲国产av天堂