The week was fast-paced and exciting! On Monday, we got to know each others’ projects, nailed down our target audience and desired outcomes, and brainstormed ways in which we might share this new resource after the week was over. By Tuesday mid-morning, we had a table of contents. We chose the sections we were each most excited about to write first. By the end of Tuesday we had our core chapters mostly written and spent Wednesday writing our introductory and supporting material. Thursday we spent the day editing and gearing up for our 6pm deadline to complete the book for it to go to print. The week was a lot of work and a lot of fun, we were all inspired and well fed.
And that is how our book titled “Contributing to OpenMRS: Getting Started as a Developer”came to be. Usually the hardest part of making meaningful contributions to any open source project is getting started. On behalf of the authors and broader OpenMRS community, we hope this book helps significantly lower the hurdles new OpenMRS developers encounter, whether they are new to open source projects, Health IT, OpenMRS, or all three. The book introduces OpenMRS development processes and architecture, walks the reader through setting up a development environment and building a basic module, overviews OpenMRS collaboration tools and where to go for support, and suggests a potential progression of becoming a seasoned developer community member.
By Jordan Kellerstrass, OpenMRS team
Last week, a small troop of five GNOMies from the docs team (Sindhu Sundar, David King, Kat Gerasimova, Michael Hill and Aruna Sankaranarayanan) arrived at Google ready to write a book for our community. We were joined by two enthusiastic documenters, Amanda French and Heidi Waterhouse, who volunteered to help us with our book from the perspective of complete newbies to our project, which was perfect as they are the intended audience for the book.
Our first day was spent getting to know the other teams, sharing our project with them and pinning down the table of contents. In the evening, Amanda and Heidi started setting up a working environment for using GNOME’s Yelp help viewer. It has been very useful to see how our tools are presented by the Internet at large to potential users. For the most part, the available information is accurate, although some details needed to be clarified.
On Wednesday, halfway through our second full day of writing, we almost had our first version of the book completed. For Thursday, we refined the existing content and expanded the book where necessary, completing our book by the 6pm deadline to go to print. On Friday we got to see (at least on screen), the fruit of our labour: the Introduction to Mallard book. The printed copies were ready by 8pm Friday night.
The week of book sprinting was a remarkable collaborative writing experience, and I can’t wait to recommend it to other projects I know. Thanks again to Allen Gunn for inspiring us and to Adam Hyde for getting a book out of us and to the Google Open Source Programs team for Doc Camp.
By Michael Hill, Aruna Sankaranarayanan, and Kat Gerasimova, GNOME Mallard team
BRL-CAD, a computer-aided design open source software project, is ecstatic for having participated in the 2013 Google Doc Camp. BRL-CAD's team of seven individuals came together from four different countries, three continents and one oceanic island to produce a contributor's guide totaling more than 100 pages in length in less than one week. The inspiration, ideas, and productivity experienced throughout the week-long event has invigorated an effort to expand documentation and improve outreach for our project. Google Doc Camp introduced an exciting technique for documenting and sharing information which we are using to help grow our community.
By Christopher Sean Morrison, BRL-CAD team
“All the knowledge and skillset that I have learned will certainly help me in my career ahead. Working with a nonprofit organization like Benetech, you have that awesome feeling of being part of something big that is helping people across the globe. I sincerely hope to continue the same in the future.” -- Yashasvi Gridhar
Google Summer of Code
Back in 2005, Google made a commitment to support open source software contributors. In addition to our other programs to build and support the contributor base, we thought a great way to increase awareness was to introduce the wide world of open source to college students. Google Summer of Code was born: match student developers from around the world with open source software organizations to work on a project while on break from their universities.
With over 8,300 mentors in 100 countries around the world, the 8,500 student developers have produced a stunning 50 million lines of code. The program will now be reaching its 10th instance in 2014.
We told you on the Official Google Blog just a few highlights of what we’ll be up to this year, and now we want to tell you all the details:
10 visits to countries with high participation throughout the year.
10 developer events in promotion of the program.
10 mentors who have participated in Google Summer of Code will be featured on our open source blog.
10% additional student stipend (a total of $5500 for students who successfully complete the whole program).
10% more students than we’ve ever had participate in the program before.
10 more mentoring organizations than we’ve ever had in the program will be participating in Google Summer of Code 2014
10 year student reunion event will be held on Google’s Mountain View campus next year for all the students who have participated in the program.
10 year reunion mentor summit will be held on Google’s Mountain View campus for all our Google Summer of Code organization alumni.
10 students/organizations will be chosen to highlight their work at the Google booths at open source events throughout the year.
10 student projects from the past nine years will be highlighted on the open source blog and YouTube.
We’re pleased to be running a program that touches a lot of lives around the world, and we hope this will be a celebration of all the accomplishments we’ve seen from so many of our participants. Watch this blog for announcements about our travel and our efforts over the next year. Here’s to 10 Things!
Google Code-in - Program starts for students November 18th
For the fourth consecutive year we are thrilled to announce Google Code-in, an international contest designed to introduce 13-17 year old pre-university students to the world of open source development. Open source projects are about more than just coding, and this contest highlights a variety of ways to contribute to open source projects. Every year, open source software is becoming more important around the globe; from government, healthcare, relief efforts, gaming, to large tech companies and everything in between.
When you read the term open source do you think:
What is open source?
What types of work do open source projects do?
I’ve only taken one computer science class, can I contribute to an open source project?
I’m not really into coding, what else can I do to contribute to open source?
I’ve never participated in open source or an online contest before, can someone help guide me?
Open source sounds cool, how can I get started?
If you’ve wondered about any of these questions and are a pre-university student (age 13-17) then we hope you will join in the fun and excitement of the Google Code-in contest starting Monday, November 18th.
For seven weeks from mid November to early January, the Google Code-in contest will have students working with 10 selected open source projects on a variety of tasks. These projects have all successfully served as mentoring organizations in previous Google Code-in contests or have worked with university students in our sister program, Google Summer of Code.
The different categories of tasks that students will be able to work on include:
Code: Tasks related to writing or refactoring code
Documentation/Training: Tasks related to creating/editing documents and helping others learn more
Outreach/research: Tasks related to community management, outreach/marketing, or studying problems and recommending solutions
Quality Assurance: Tasks related to testing and ensuring code is of high quality
User Interface: Tasks related to user experience research or user interface design and interaction
Over the past 3 years we have had over 1200 students from 71 countries complete tasks in the contest. In April, we flew the 20 Google Code-in 2012 Grand Prize winners and a parent to Google’s Mountain View, CA headquarters for a 5 day/4 night trip where they enjoyed talking with Google engineers, an awards ceremony, a Google campus tour, and a full day of fun in San Francisco.
Visit the Frequently Asked Questions page on the Google Code-in 2013 site for more details on how to sign up and participate. And please help us spread the word to your friends around the globe! If you are a teacher that would like to encourage your students to participate, please send an email to our team at email@example.com. We would be happy to answer any questions you may have.
Stay tuned to the contest site and subscribe to our mailing list for more updates on the contest. We will announce the 10 open source organizations that will be participating in the contest on November 1. The Google Code-in contest starts for students on November 18, 2013. We look forward to welcoming hundreds of students from around the world into the open source family again this year.
Apache Isis -- Students: Bhargav Golla and Dimuthu Upeksha
Apache Isis is a Java framework for rapidly developing domain-driven apps. This summer we had two students working on new “viewers” that interact with a REST API that Isis automatically generates, reflecting the structure and behavior of the domain objects. In the past the Isis community has worked on single-page HTML5/JS viewer and on a Windows Store App viewer. For Google Summer of Code our two students are each building their own viewers, one for Android, and one using JQueryMobile (to be packaged using Apache Cordova/PhoneGap).
Both students have become quite fluent in the REST API, and both have a viewer running that is quite usable and can be deployed to an Android mobile device. The two viewers are broadly similar in terms of features implemented, and indeed towards the end of the project hit the limits of the available features in the REST API. Both students have said they are keen to continue developing their viewers after the Google Summer of Code program ends.
By Dan Haywood, Apache Mentor
Apache OODT -- Student: Rajith Siriwardana
Some exciting work to make Apache OODT interoperate with the scalable Ganglia open source resource monitoring system has been undertaken by Rajith Siriwardana. Rajith and his mentor, Chris Mattmann, divided the project up into several manageable milestones, first developing a fast Java parsing library for Ganglia's XML based response format. This is one of the first modular Java-based Ganglia clients that exists, and to our knowledge is the first one to exist at Apache.
With the Ganglia Java client in hand, Rajith and Chris worked to develop a weighted average load balancing algorithm that plugged into Apache OODT's Resource Monitor interface, allowing it to poll Ganglia for current metrics like 5-min, 1-min avg load, and current disk capacity and space. The algorithm then takes this information into account, along with the requirement for job load, and plugs into the Capacity based scheduler part of the OODT Resource Manager, thereby allowing OODT to poll its resource monitoring information from Ganglia.
We are excited that Rajith is now a member of the Apache OODT Project Management Committee (PMC) and a committer on the project. Apache OODT is a better overall project because of his efforts this summer.
By Chris Mattmann, Apache Mentor
Apache OODT -- Student Ross Laidlaw
Just as a pencil needs to be kept sharp in order to be useful, computer software needs to be regularly improved and polished in order to stay relevant. Fortunately for the Apache OODT project, this is exactly the type of work Ross Laidlaw, under the mentorship of Rishi Verma, has performed over the past few months through the Google Summer of Code program. Ross has taken a component of the OODT framework called the Product Server, and sculpted it into a more intuitive and usable package. He's taken the Java servlet-based set of web applications constituting the Product Server framework, and ported them to easier-to-maintain JAX-RS RESTful end-points. Moreover, Ross has advanced the content dissemination package, that's a part of the framework, to help make available OODT metadata in various forms like: JSON, RSS, and RDF.
Why perform all this refactoring as well as new development work? Simple: it helps to keep the OODT Product Server framework relevant, maintainable, and sharp. Ross has done an excellent job through his Google Summer of Code project, and we're definitely looking forward to his continuing involvement with OODT.
By Rishi Verma, Apache Mentor
Apache Gora -- Apostolos Giannakidis
Data volumes have been growing at an astronomical rate in recent years with the term 'Big Data' being used ubiquitously within tech circles, mainstream media, governments and society alike. Apache Gora is an open source object-to-datastore mapping framework providing an in-memory data model and persistence for big data. Gora supports persisting to column stores, key value stores, document stores and RDBMSs, and analyzing the data with extensive Apache Hadoop™ MapReduce support.
Apostolos Giannakidis’ project involved extending datastore support for Oracle's NoSQL database as part of the Gora suite of datastore modules. Work on the design and implementation of the gora-oracle module included the provision of full CRUD operations while exploiting the ACID transactions, flexible consistency options and the simple data mode of Oracle NoSQL database. With these, Apache Gora will be able to integrate seamlessly with the Oracle stack and the Big Data Appliance. Also, this module is one step further toward rendering Apache Gora as the standard persistence framework for NoSQL databases.
By Lewis John Mcgibbney, Apache Mentor