The day started with a good gathering to understand what to be done on the Open Source Day. There was initial discussion about allowing each person to do what ever they liked. However since we didn't want each to do just whatever they wanted to do, we wanted them to come out with ideas and tell us what they wanted to do, so that others who might be interested in the activity might want to team up with each other.

We started from the Seniority Level where the Seniors would like to propose what they wish to do and the juniors would like to follow the seniors if they wish to do the same activity. Based on each senior's selection, we finally divided our small team of 8 people into 3 teams each executing a different activity.

Team 1: Developing Plugins on Rails 3

As Rails Detectives (formerly Heurion) we have had learnt to develop plugins for last 5 years. We have built plugins for Rails v1.x, v2.x. but since then we had not much time to understand how to build Rials Plugins for Rails 3.x as the concept involved in building a plugin for Rails 3.x is much different than Rails 2.x with inclusion of gemspec and other tools.

This team has 2 interested people Alok and Ganesh, where alok, wanted to build a new plugin based on his experience in a previous project and Ganesh wanted to migrate our 2.X plugins to 3.x. Hence forth the decision was taken to invest the day to understand how to build a plugin and if time persisted to build the plugins.
 

First few hours they achieved to understand how to use the plugin and finally Alok developed his basic plugin (needs more cleaning before it can be launched) and Ganesh picked up our Acts As Fannable  plugin (https://github.com/heurionconsulting/acts_as_fannable_2.0) to configure and migrate. At the end of the Day we had Acts as fannable 3.0 plugin ready and is yet to be launched to the industry as we had to write some more specs and tests to the plugin

Team 2: Learning RSpec

Kundan decided that he would like to learn RSpec and how to write test cases for the codes that they write. Most of the time kundan was involved in writing codes using TDD, but never got the opportunity to learn RSpec, This idea was supported by Senthil (Test Lead) as he would also want to involve into more coding based tests so that he could later on manage tests written for most of our projects. Ravi, our Master BDD expert decided, he would like to teach them RSpec rather than learning RSpec, His interests were that if he is able to teach the rest on how to write RSpec, it would become easy for him to understand where he would go wrong and what is he missing. Its like Teacher learning while teaching.

So this team started with the basics of RSpec and covered the following aspects

1. Installation and bundling Rspec

2. Generation of spec folder

3. What all could be done with Spec_helper file

4. Generate basic specs

5. Use of standard RSpec methods making use of RSpec Cheat sheet

At the end of the day, though Kundan was satisfied with the Rspec, Senthil required some more time to come to speed being a tester and having less knowledge on Coding.

Team 3 : Learning Rails Architecture

Learning Rails Architecture was suggest by Satish who wanted to get into t he depth of the architecture. He was followed by Prathibha and Pradeep, who were new to the technology and wanted to know the depth of the system. Satish went through the architecture and helping the rest to understand what all could be done with ActiveRecord classes and ActionPack classes (to include ActionMailer)...and identify codes to achieve different scenarios