BootCamp 2014

Hi All & Welcome

First things first, lets get started with these so the rest would be easy.

1. Subscribe to our Apache Airavata mailing lists.
   1. https://airavata.apache.org/community/mailing-lists.html
   2. Be active on the mailing list so we can share, assist and evolve as community.
   3. Do you have a question to ask? Ask by mailing to dev@airavata.apache.org
      
      
2. Share your technical-know-how or your solution ideas through dev@airavata.apache.org
   
   
3. Want to join with architectural brainstorming want to share your thoughts? architecture@airavata.apache.org
   
   
4. Create an account in JIRA
   
   1. Follow the link and you will be done https://issues.apache.org/jira/secure/Signup!default.jspa
      Having an account in Apache Airavata JIRA takes us one step closer to the project. you can report bugs, post your code update information and also get an idea on what going on
   
   
5. How to use JIRA
   1. Link to Airavata JIRA https://issues.apache.org/jira/browse/AIRAVATA-1421?jql=project%20%3D%20AIRAVATA
   2. Guidelines for using JIRA
      
      
6. Do you need more on Gateways; what is better than reading yourself?
   1. Airavata Wiki: https://cwiki.apache.org/confluence/display/AIRAVATA/Home
   2. Read our Research Papers
      
      
7. How to produce quality code?
   1. Follow our guidelines: https://google-styleguide.googlecode.com/svn/trunk/javaguide.html
      
      
8. You can join the Airavata Instant Messaging Room to interact with the community.
   1. http://s.apache.org/chat

Guidelines for Using Airavata JIRA

1. Airavata JIRA is mainly for Issue reporting, tracking and for posting code patches.
   
   
2. Apart from issue reporting; JIRA can also be used to report improvements, post questions (for this best is the Airavata mailing list).
   
   
3. When it comes to recording tasks, Issues (commonly known as JIRAs) we need;
   1. User account in Airavata JIRA
   2. Knowledge in recording the JIRA
      
      
4. Life cycle of a JIRA
   1. OPEN - When a JIRA is created it will have the status ‘OPEN’. An open JIRA can be assigned to a responsible person to solve
   2. IN PROGRESS -  Once the JIRA is assigned the assignee can change the status to IN PROGRESS so others will know that the issue is been taken care of
   3. RESOLVED - Once issue is resolved the status can be changed to RESOLVED and if required the resolved code patch can be attached to the issue.
   4. CLOSED - Resolved issues are available to be tested. Any member can test an issue and tag it as CLOSED with a Resolution type.
   5. REOPENED - If an earlier issue resurfaces one can search for the issue and reopen it.
      
      
5. There are several types we could create; select
   1. Epic - A big User story which would consist of smaller set of stories and will take more than a single sprint to complete
   2. Story - A smaller user story; a subset of the epic and will have a combination of  tasks, bugs, features or could even consists of just one type
   3. Task - A single Task which could belong to a single sprint or can consists of multiple subtasks which would stretch to several sprint.
   4. Bug - This is an Airavata issue and could be reported by a user, developer, tester, etc… of the system. When reporting a bug the severity of the bug has to be reported as well as per the individual's understanding.
   5. New Feature - Airavata users can report a new feature via JIRA. These would be looked at by a system architect and then proceed to have internal discussions. If it is to be added as a new feature, this would be linked to a story and included in the appropriate sprint.
   6. Improvement - Airavata users can report an improvement to an existing feature or a service via JIRA. These would be looked at by a system architect and if selected to proceed will be included in the appropriate sprint.
      
      
6. How to create a JIRA
   1. Log in to JIRA and click on ‘Create Issue’ button on top of the page.
   2. Mandatory fields are indicated by a red star *
   3. In Create Issue page;
      1. Project ‘Airavata’ is already selected
      2. Issue type ‘Bug’ is auto selected but user can change it to needed type
      3. User can select the Component, Affected Version and Environment which will be more helpful to narrow down the location
      4. Description is not indicated as mandatory but within Airavata this is mandatory s more info is never a bad thing!
         
         
7. When JIRA is created it will be automatically assigned to the created user. An Airavata member with commit privileges will only be able to assign the issue to another member.
   
   
8. Each JIRA will have a unique issue number and also any updates on the issue will be communicated to the creator via emails.
   
   
9. Prior to creating a new JIRA always check whether it is been reported earlier. If so add a comment to the existing issue.
   
   
10. If there are more than one issue reported for the same issue, extra issues can be tagged as Duplicates and link with the remaining same issue.