Google Data » Ashleigh Rentz https://googledata.org Everything Google: News, Products, Services, Content, Culture Thu, 02 Apr 2015 17:58:43 +0000 en-US hourly 1 http://wordpress.org/?v=4.1.1 Google Summer of Code Wrap up: Point Cloud Library https://googledata.org/google-open-source/google-summer-of-code-wrap-up-point-cloud-library/ https://googledata.org/google-open-source/google-summer-of-code-wrap-up-point-cloud-library/#comments Fri, 14 Nov 2014 18:00:00 +0000 https://googledata.org/?guid=c3b9ef345ce919adac2ef2d2c3b959b4 Today’s Google Summer of Code wrap up comes from Federico Tombari at the Point Cloud Library project, a 2D/3D image and point cloud processing framework.
pointcloudlibrary_horz_large_pos.png

For the third year, the Point Cloud Library (PCL) organization has been a participant in Google Summer of Code. We had the opportunity to mentor 12 students who spent the summer developing projects related to 3D computer vision and robotic perception.

This year, I had the pleasure to mentor two students: Manuel Gesto and Jilliam Diaz Barros. Manuel worked on porting a recent algorithm (proposed last year at the ICRA conference by Karphaty et al.) related to object discovery. The idea is that a robot can wander around a room or a building, reconstruct the surrounding environment through Kinect Fusion techniques and then try to extract interesting parts - possibly objects - out of this 3D representation without an explicit training set. Manuel worked well in implementing on his own a segmentation method that was required for the algorithm. Jilliam worked on stereo matching techniques. She implemented two state-of-the-art algorithms, one focused on efficiency and the other on accuracy, which will enrich the stereo module already present in PCL. Also, she validated her work with a comprehensive experimental evaluation using benchmark datasets.

Alex Ichim from our organization worked with Andrei Militaru, a BSc student in Computer Science from Jacobs University in Germany. We looked into efficient representations for head models in the context of face reconstruction using RGB-D devices such as the Microsoft Kinect. In order to counteract the heavy noise and missing data from this kind of camera, we employed the concept of statistical face models (first introduced by Blanz and Vetter at Siggraph ‘99). To demonstrate this, we built an application that uses live data from the camera, registers and integrates it into a point cloud using the Kinect Fusion implementation in PCL; in parallel, another thread uses the data and fits the statistical model to it, yielding a low resolution face model that updates in realtime as more views of the actor are acquired.

Markus Schoeler was another student working with us this year. His project consisted of two sub projects, namely implementing the Locally Convex Connected Patches (LCCP) algorithm and a shape generator. The LCCP algorithm was published on this year’s CVPR conference and aims at segmenting a scene into objects and parts (by tuning parameters, you can "select" the desired level of detail). The shape generator puts special emphasis on giving users full control of how they assign labels in scenes. This makes it possible to easily create annotated data and decide how coarse the segmentation should be.

Federico Tombari, Organization Co-Administrator, Point Cloud Library]]> Today’s Google Summer of Code wrap up comes from Federico Tombari at the Point Cloud Library project, a 2D/3D image and point cloud processing framework.
pointcloudlibrary_horz_large_pos.png

For the third year, the Point Cloud Library (PCL) organization has been a participant in Google Summer of Code. We had the opportunity to mentor 12 students who spent the summer developing projects related to 3D computer vision and robotic perception.

This year, I had the pleasure to mentor two students: Manuel Gesto and Jilliam Diaz Barros. Manuel worked on porting a recent algorithm (proposed last year at the ICRA conference by Karphaty et al.) related to object discovery. The idea is that a robot can wander around a room or a building, reconstruct the surrounding environment through Kinect Fusion techniques and then try to extract interesting parts - possibly objects - out of this 3D representation without an explicit training set. Manuel worked well in implementing on his own a segmentation method that was required for the algorithm. Jilliam worked on stereo matching techniques. She implemented two state-of-the-art algorithms, one focused on efficiency and the other on accuracy, which will enrich the stereo module already present in PCL. Also, she validated her work with a comprehensive experimental evaluation using benchmark datasets.

Alex Ichim from our organization worked with Andrei Militaru, a BSc student in Computer Science from Jacobs University in Germany. We looked into efficient representations for head models in the context of face reconstruction using RGB-D devices such as the Microsoft Kinect. In order to counteract the heavy noise and missing data from this kind of camera, we employed the concept of statistical face models (first introduced by Blanz and Vetter at Siggraph ‘99). To demonstrate this, we built an application that uses live data from the camera, registers and integrates it into a point cloud using the Kinect Fusion implementation in PCL; in parallel, another thread uses the data and fits the statistical model to it, yielding a low resolution face model that updates in realtime as more views of the actor are acquired.

Markus Schoeler was another student working with us this year. His project consisted of two sub projects, namely implementing the Locally Convex Connected Patches (LCCP) algorithm and a shape generator. The LCCP algorithm was published on this year’s CVPR conference and aims at segmenting a scene into objects and parts (by tuning parameters, you can "select" the desired level of detail). The shape generator puts special emphasis on giving users full control of how they assign labels in scenes. This makes it possible to easily create annotated data and decide how coarse the segmentation should be.

Federico Tombari, Organization Co-Administrator, Point Cloud Library]]> https://googledata.org/google-open-source/google-summer-of-code-wrap-up-point-cloud-library/feed/ 0 Geometry Math Library for C++ Game Developers: MathFu https://googledata.org/google-open-source/geometry-math-library-for-c-game-developers-mathfu/ https://googledata.org/google-open-source/geometry-math-library-for-c-game-developers-mathfu/#comments Thu, 13 Nov 2014 17:30:00 +0000 https://googledata.org/?guid=5262fa3297360cf8bee862da797dc215 (Cross-posted with the Google Developers Blog)

Today we're announcing the 1.0 release of MathFu, a cross-platform geometry math library for C++ game developers.  MathFu is a C++ math library developed primarily for games focused on simplicity and efficiency.


It provides a suite of vector, matrix and quaternion classes to perform basic geometry suitable for game developers.  This functionality can be used to construct geometry for graphics libraries like OpenGL or perform calculations for animation or physics systems.


The library is written in portable C++ with SIMD compiler intrinsics and has been tested on Android, Linux, OS X and Windows.


You can download the latest open source release from our GitHub page.  We invite you to contribute to the project and join our discussion list!


By Stewart Miles, Fun Propulsion Labs at Google*


*Fun Propulsion Labs is a team within Google that's dedicated to advancing gaming on Android and other platforms.

]]> https://googledata.org/google-open-source/geometry-math-library-for-c-game-developers-mathfu/feed/ 0 Get the scoop on the Mentoring Organizations for Google Code-in 2014 https://googledata.org/google-open-source/get-the-scoop-on-the-mentoring-organizations-for-google-code-in-2014/ https://googledata.org/google-open-source/get-the-scoop-on-the-mentoring-organizations-for-google-code-in-2014/#comments Wed, 12 Nov 2014 17:44:00 +0000 https://googledata.org/?guid=c0f9999ad4c22e9a43751edc8b1fd8b1 We are excited to announce the 12 open source projects that will be acting as mentoring organizations for the Google Code-in 2014 contest that starts December 1st. The contest is designed to introduce 13-17 year old pre-university students to open source software development, giving them the opportunity to take the skills they have been learning in the classroom (or on their own) and apply them to a real software project. These open source projects have experienced mentors available —  all have participated in Google Summer of Code in the past with many also participating in previous years of Google Code-in.

GCI-2014-with border.jpg

Before the contest begins, students should read up on the different mentoring organizations participating this year by clicking on the links below.
Apertium - a platform for making rule-based machine translation systems
BRL-CAD - a computer aided solid modeling system
Copyleft Games Group - promotes players’ rights to create, play, modify, and share games
Drupal - a content management platform
FOSSASIA - a non-profit organization supporting developers and makers of the Free and Open Source community in Asia
Haiku - an operating system, fast and simple, inspired by BeOS
KDE -  a powerful graphical desktop environment for Unix-like workstations
Mifos - a non-profit org that brings technology-enabled financial services to the poor
OpenMRS - a medical records system platform for developing countries
Sahana Software Foundation - humanitarian open source disaster management software
Sugar Labs - a learning platform that reinvents how computers are used for primary education
Wikimedia Foundation - MediaWiki and extensions, powering Wikipedia and thousands of collaborative websites

Organizations will provide a list of tasks for students to work on during the contest in the following categories: coding, documentation, user interface, quality assurance, outreach, research, and training. Each task has at least one mentor assigned to it to help students should they have questions.  

The mentoring organizations are all busy working on identifying hundreds of tasks for students to chose from when the contest starts on December 1st. This year there are also beginner tasks available for students which are a great way for students to start working with the organizations and get a more complete understanding of the projects right away.

Starting on Monday, December 1st at 17:00 UTC, students that meet the eligibility requirements can register on the Google Code-in contest site and start claiming tasks and earning prizes.

For important contest information please check out the contest site for Contest Rules, Frequently Asked Questions and Important Dates.  We have a screencast about the contest available to view on our program site where you can also find flyers and other helpful information including the new Getting Started Guide. You can also join our announcement and discussion lists to talk with other students, mentors and organization administrators about the contest.

Students, join in the fun – Google Code-in starts Monday, December 1st!

By Stephanie Taylor, Open Source Programs
]]> We are excited to announce the 12 open source projects that will be acting as mentoring organizations for the Google Code-in 2014 contest that starts December 1st. The contest is designed to introduce 13-17 year old pre-university students to open source software development, giving them the opportunity to take the skills they have been learning in the classroom (or on their own) and apply them to a real software project. These open source projects have experienced mentors available —  all have participated in Google Summer of Code in the past with many also participating in previous years of Google Code-in.

GCI-2014-with border.jpg

Before the contest begins, students should read up on the different mentoring organizations participating this year by clicking on the links below.
Apertium - a platform for making rule-based machine translation systems
BRL-CAD - a computer aided solid modeling system
Copyleft Games Group - promotes players’ rights to create, play, modify, and share games
Drupal - a content management platform
FOSSASIA - a non-profit organization supporting developers and makers of the Free and Open Source community in Asia
Haiku - an operating system, fast and simple, inspired by BeOS
KDE -  a powerful graphical desktop environment for Unix-like workstations
Mifos - a non-profit org that brings technology-enabled financial services to the poor
OpenMRS - a medical records system platform for developing countries
Sahana Software Foundation - humanitarian open source disaster management software
Sugar Labs - a learning platform that reinvents how computers are used for primary education
Wikimedia Foundation - MediaWiki and extensions, powering Wikipedia and thousands of collaborative websites

Organizations will provide a list of tasks for students to work on during the contest in the following categories: coding, documentation, user interface, quality assurance, outreach, research, and training. Each task has at least one mentor assigned to it to help students should they have questions.  

The mentoring organizations are all busy working on identifying hundreds of tasks for students to chose from when the contest starts on December 1st. This year there are also beginner tasks available for students which are a great way for students to start working with the organizations and get a more complete understanding of the projects right away.

Starting on Monday, December 1st at 17:00 UTC, students that meet the eligibility requirements can register on the Google Code-in contest site and start claiming tasks and earning prizes.

For important contest information please check out the contest site for Contest Rules, Frequently Asked Questions and Important Dates.  We have a screencast about the contest available to view on our program site where you can also find flyers and other helpful information including the new Getting Started Guide. You can also join our announcement and discussion lists to talk with other students, mentors and organization administrators about the contest.

Students, join in the fun – Google Code-in starts Monday, December 1st!

By Stephanie Taylor, Open Source Programs
]]> https://googledata.org/google-open-source/get-the-scoop-on-the-mentoring-organizations-for-google-code-in-2014/feed/ 0 GSoC Reunion Recap with Cyrille Artho https://googledata.org/google-open-source/gsoc-reunion-recap-with-cyrille-artho/ https://googledata.org/google-open-source/gsoc-reunion-recap-with-cyrille-artho/#comments Tue, 11 Nov 2014 18:00:00 +0000 https://googledata.org/?guid=db3c45e3d5aeb6840b6720b8d07f13b8 To celebrate the tenth year of Google Summer of Code (GSoC), we recently welcomed over 500 people who’ve participated over the years to a special Reunion event. We’d like to share a few recaps of the event from the perspectives of students and mentors who joined us from 50 different countries. Today’s summary comes from Cyrille Artho, a five-year GSoC mentor from the Java PathFinder and LyX projects.
920x156xbanner-gsoc2014.png.pagespeed.ic.gdr4t3Igca.png

Having been a mentor for Google Summer of Code for five years, I had always wondered what the annual mentor summit was about. However, because October is usually a very busy time of the year, my schedule had never made it possible for me to join... until this year’s special reunion where both students and mentors from all years of the program were invited.

This year's event was the biggest one ever with a crowd so large that finding someone was not easy. I had never met anyone from the summit in person so it was nice to see Stefano, my fellow LyX project mentor, in the hotel lobby. From there we could proceed straight to registration and the reception, and finally discuss our experiences with GSoC face to face. Up to that point, thousands of kilometers and usually 7 or 8 time zones had always separated me from fellow developers and mentors, as I am located in Japan.
photo 2.JPG

The next day, I chose to stay in the event meeting rooms instead of going to the theme park so I could get some work done while also having a chance to see what other people are working on. It is interesting that Google does not restrict GSoC to “infrastructure-critical" projects, but also includes games. However, games are not necessarily simple software; some games require complex algorithms to keep information from many clients consistent, so some of the software can be just as complex as part of an OS kernel.

The second day ended with a big reception featuring guest speakers at the San Jose Tech Museum where it was interesting to see what can make a project successful in Linus Torvalds' opinion. The code has to fulfill certain quality standards --"good taste", as he called it -- but persistence is just as important as that. Nowadays, with so many projects being available as open source, something that is just released and then updated for a few weeks after that is just a blip on the radar that will no longer be noticed by the community.

The weekend was dedicated to the heart of the event, the "unconference" sessions, which were for me the highlight of the reunion. I was actually surprised that a few free slots were available early on (as I consider the early slots to be the most valuable ones), so I jumped in and proposed a session on testing. It was interesting for me to see that everybody who attended is using some sort of automated testing at some level, but almost nobody is happy with the tools that exist today. Although people see the benefit of testing, creating and maintaining test cases is still a burden and we need higher-level tools that help us with that. Unfortunately, if we move towards test case generation, it is impossible to create a single tool that caters to everyone, so we need tools that can interoperate. Open source is good at that, but the process can still take years or even decades, as we need to solve open research problems and then come up with some standards so we can (in the hopefully not-so-far future) combine partial solutions into a big ensemble.

Other sessions were dedicated to both technical and non-technical topics (for example, how to make our GSoC projects successful), and also included tutorial-like presentations. This helped me understand what some projects (such as crash reporting tools) or groups were about in a way that I would probably not have found when looking for information in the virtual world. I also liked that people could come up with suggestions on session topics in real time, although this sometimes meant that a session that I would have liked to join was canceled just as it was about to begin, or some sessions ended up drawing only a few people while others had more attendees than seats were available in the room.

All in all it was a very intense and enjoyable weekend, and I will try to keep that late October weekend free from now on to increase my chances of attending future summits!

By Cyrille Artho
]]> To celebrate the tenth year of Google Summer of Code (GSoC), we recently welcomed over 500 people who’ve participated over the years to a special Reunion event. We’d like to share a few recaps of the event from the perspectives of students and mentors who joined us from 50 different countries. Today’s summary comes from Cyrille Artho, a five-year GSoC mentor from the Java PathFinder and LyX projects.
920x156xbanner-gsoc2014.png.pagespeed.ic.gdr4t3Igca.png

Having been a mentor for Google Summer of Code for five years, I had always wondered what the annual mentor summit was about. However, because October is usually a very busy time of the year, my schedule had never made it possible for me to join... until this year’s special reunion where both students and mentors from all years of the program were invited.

This year's event was the biggest one ever with a crowd so large that finding someone was not easy. I had never met anyone from the summit in person so it was nice to see Stefano, my fellow LyX project mentor, in the hotel lobby. From there we could proceed straight to registration and the reception, and finally discuss our experiences with GSoC face to face. Up to that point, thousands of kilometers and usually 7 or 8 time zones had always separated me from fellow developers and mentors, as I am located in Japan.
photo 2.JPG

The next day, I chose to stay in the event meeting rooms instead of going to the theme park so I could get some work done while also having a chance to see what other people are working on. It is interesting that Google does not restrict GSoC to “infrastructure-critical" projects, but also includes games. However, games are not necessarily simple software; some games require complex algorithms to keep information from many clients consistent, so some of the software can be just as complex as part of an OS kernel.

The second day ended with a big reception featuring guest speakers at the San Jose Tech Museum where it was interesting to see what can make a project successful in Linus Torvalds' opinion. The code has to fulfill certain quality standards --"good taste", as he called it -- but persistence is just as important as that. Nowadays, with so many projects being available as open source, something that is just released and then updated for a few weeks after that is just a blip on the radar that will no longer be noticed by the community.

The weekend was dedicated to the heart of the event, the "unconference" sessions, which were for me the highlight of the reunion. I was actually surprised that a few free slots were available early on (as I consider the early slots to be the most valuable ones), so I jumped in and proposed a session on testing. It was interesting for me to see that everybody who attended is using some sort of automated testing at some level, but almost nobody is happy with the tools that exist today. Although people see the benefit of testing, creating and maintaining test cases is still a burden and we need higher-level tools that help us with that. Unfortunately, if we move towards test case generation, it is impossible to create a single tool that caters to everyone, so we need tools that can interoperate. Open source is good at that, but the process can still take years or even decades, as we need to solve open research problems and then come up with some standards so we can (in the hopefully not-so-far future) combine partial solutions into a big ensemble.

Other sessions were dedicated to both technical and non-technical topics (for example, how to make our GSoC projects successful), and also included tutorial-like presentations. This helped me understand what some projects (such as crash reporting tools) or groups were about in a way that I would probably not have found when looking for information in the virtual world. I also liked that people could come up with suggestions on session topics in real time, although this sometimes meant that a session that I would have liked to join was canceled just as it was about to begin, or some sessions ended up drawing only a few people while others had more attendees than seats were available in the room.

All in all it was a very intense and enjoyable weekend, and I will try to keep that late October weekend free from now on to increase my chances of attending future summits!

By Cyrille Artho
]]> https://googledata.org/google-open-source/gsoc-reunion-recap-with-cyrille-artho/feed/ 0 Utilities for C/C++ Android Developers: fplutil 1.0 https://googledata.org/google-open-source/utilities-for-cc-android-developers-fplutil-1-0/ https://googledata.org/google-open-source/utilities-for-cc-android-developers-fplutil-1-0/#comments Mon, 10 Nov 2014 17:30:00 +0000 https://googledata.org/?guid=e291ac3a60cd823e93774260f0fc9ff3
(cross-posted with the Android Developers Blog)

Today we're announcing the 1.0 release of fplutil, a set of small libraries and tools by Fun Propulsion Labs at Google* (the FPL in fplutil) that is useful when developing C/C++ applications for Android.

fplutil introduces the following:

  • build_all_android.py, an all-in-one build script that allows you to build (with the Android NDK), install and run native (C/C++) Android apps from the command line. This is ideal for build automation, but is also useful in a developer’s compile/run loop.
  • buildutil performs the configuration, build and archive steps of Android and Linux C/C++ applications using a suite of Python modules. This suite of modules can automate builds in a continuous integration environment. This framework uses legacy tools in the Android Development Toolkit.
  • libfplutil enables C/C++ developers to write traditional applications (like Hello World) using "main()" and "printf()" on Android.
  • android_ndk_perf.py is a desktop tool that enables native (C/C++) developers to measure the CPU utilization of their applications on Android, guiding their optimization efforts.  An example report is shown below:

android_ndk_perf.py example HTML report


You can download the latest open source release from our github page. We invite you to contribute to the project and join our discussion list!

By Stewart Miles, Fun Propulsion Labs at Google*

*Fun Propulsion Labs is a team within Google that's dedicated to advancing gaming on Android and other platforms.

]]>
(cross-posted with the Android Developers Blog)

Today we're announcing the 1.0 release of fplutil, a set of small libraries and tools by Fun Propulsion Labs at Google* (the FPL in fplutil) that is useful when developing C/C++ applications for Android.

fplutil introduces the following:

  • build_all_android.py, an all-in-one build script that allows you to build (with the Android NDK), install and run native (C/C++) Android apps from the command line. This is ideal for build automation, but is also useful in a developer’s compile/run loop.
  • buildutil performs the configuration, build and archive steps of Android and Linux C/C++ applications using a suite of Python modules. This suite of modules can automate builds in a continuous integration environment. This framework uses legacy tools in the Android Development Toolkit.
  • libfplutil enables C/C++ developers to write traditional applications (like Hello World) using "main()" and "printf()" on Android.
  • android_ndk_perf.py is a desktop tool that enables native (C/C++) developers to measure the CPU utilization of their applications on Android, guiding their optimization efforts.  An example report is shown below:

android_ndk_perf.py example HTML report


You can download the latest open source release from our github page. We invite you to contribute to the project and join our discussion list!

By Stewart Miles, Fun Propulsion Labs at Google*

*Fun Propulsion Labs is a team within Google that's dedicated to advancing gaming on Android and other platforms.

]]> https://googledata.org/google-open-source/utilities-for-cc-android-developers-fplutil-1-0/feed/ 0 Google Summer of Code wrap up: Ceph https://googledata.org/google-open-source/google-summer-of-code-wrap-up-ceph/ https://googledata.org/google-open-source/google-summer-of-code-wrap-up-ceph/#comments Fri, 07 Nov 2014 18:00:00 +0000 https://googledata.org/?guid=1a075548c9f2a88505f6b3620e72b893 We continue our Google Summer of Code 2014 wrap up series with Ceph, a distributed object store and file system. Patrick McGarry joins us for a review of two summer projects.



With our first year participating in Google Summer of Code (GSoC) in the rearview mirror, we are already looking forward to GSoC 2015. Over the summer, we learned useful lessons on how to engage with a broader audience and gained valuable code and developer insights. We had two GSoC students that were guided by three mentors, but we certainly hope to grow these numbers in the future. Read on for summaries of our developer projects.


Ceph Wireshark Dissector
Student: Kevin Cox
Mentor: Sage Weil


Wireshark, originally known as Ethereal, is a cross-platform, free and open source packet analyzer used for network troubleshooting, protocol development and general analysis. Although past efforts had been made to integrate Ceph protocols into Wireshark, these efforts were outdated and would no longer compile on a modern version of Wireshark.


This summer Kevin Cox was tasked with creating a new dissector that could be maintained easily and extended as both Ceph and Wireshark changed over time. The main points of the proposal were:
  • Create a strong framework from which the dissector can be built so that new message types can be added in the future
  • Develop code that allows the dissector to be accepted into upstream Wireshark
  • Work with the Wireshark team to get the dissector into Wireshark natively
  • Implement as many message types as possible


The code has been included in Wireshark, but it won't land until our next major release. Until then, users should follow the instructions on building and installing from the latest source. For more details, see Kevin’s student report.


Add Erasure Code to the Reliability Model
Student: Veronica Estrada Galiñanes
Mentors: Kyle Bader, Loïc Dachary


One of the compelling features behind Ceph is the built-in data reliability. The default scheme to ensure that your data will still be around in the event of hardware failures is replication.  Ceph takes data, splits it into chunks, and replicates those chunks (3x by default) across physical servers. There are many things that could affect the reliability of your data (writes, disk failures, network interruptions, etc) and Ceph's reliability model was based around the concept of this 3x replication.


“Erasure Coding” has recently been introduced as an alternative approach to data durability for Ceph. Unlike the default replication scheme, data can be stored in several chunks all on different physical servers with error correction information added. When one of those chunks becomes unavailable due to hardware failure, it can be reconstructed. The error correction information is much more efficient to store than literal copies of data; Ceph can often store data with erasure coding using only 1.4x the size of the data instead of 3x as with plain replication.


Veronica Estrada Galiñanes’ GSoC project was to model the impact that different replication schemes have on data durability in distributed systems. Veronica provided a thorough analysis starting with the existing system reliability. She then modeled several different approaches, including erasure coding and locally repairable codes. Although the analysis was focused on Ceph, it could be applied to any other object-based storage system.


This work provided a great methodology to analyze and confirm the redundancy and overall reliability of data within a Ceph system across a wide array of replication schemes. For the full student report, read Veronica's final report.


As we worked with the students, mentors, and other organization admins within the Google Summer of Code, we realized that students often have a different perspective of the world. This fresh perspective can offer insights and renewed enthusiasm that would otherwise be difficult to achieve. We found our experience with the program to be rewarding both in a tangible sense (code/developers) and, perhaps more importantly, in the intangible of new ideas and experience that will help broaden our ecosystem in the future. We hope to participate again next year!


By Patrick McGarry, Ceph Organization Administrator

]]> We continue our Google Summer of Code 2014 wrap up series with Ceph, a distributed object store and file system. Patrick McGarry joins us for a review of two summer projects.



With our first year participating in Google Summer of Code (GSoC) in the rearview mirror, we are already looking forward to GSoC 2015. Over the summer, we learned useful lessons on how to engage with a broader audience and gained valuable code and developer insights. We had two GSoC students that were guided by three mentors, but we certainly hope to grow these numbers in the future. Read on for summaries of our developer projects.


Ceph Wireshark Dissector
Student: Kevin Cox
Mentor: Sage Weil


Wireshark, originally known as Ethereal, is a cross-platform, free and open source packet analyzer used for network troubleshooting, protocol development and general analysis. Although past efforts had been made to integrate Ceph protocols into Wireshark, these efforts were outdated and would no longer compile on a modern version of Wireshark.


This summer Kevin Cox was tasked with creating a new dissector that could be maintained easily and extended as both Ceph and Wireshark changed over time. The main points of the proposal were:
  • Create a strong framework from which the dissector can be built so that new message types can be added in the future
  • Develop code that allows the dissector to be accepted into upstream Wireshark
  • Work with the Wireshark team to get the dissector into Wireshark natively
  • Implement as many message types as possible


The code has been included in Wireshark, but it won't land until our next major release. Until then, users should follow the instructions on building and installing from the latest source. For more details, see Kevin’s student report.


Add Erasure Code to the Reliability Model
Student: Veronica Estrada Galiñanes
Mentors: Kyle Bader, Loïc Dachary


One of the compelling features behind Ceph is the built-in data reliability. The default scheme to ensure that your data will still be around in the event of hardware failures is replication.  Ceph takes data, splits it into chunks, and replicates those chunks (3x by default) across physical servers. There are many things that could affect the reliability of your data (writes, disk failures, network interruptions, etc) and Ceph's reliability model was based around the concept of this 3x replication.


“Erasure Coding” has recently been introduced as an alternative approach to data durability for Ceph. Unlike the default replication scheme, data can be stored in several chunks all on different physical servers with error correction information added. When one of those chunks becomes unavailable due to hardware failure, it can be reconstructed. The error correction information is much more efficient to store than literal copies of data; Ceph can often store data with erasure coding using only 1.4x the size of the data instead of 3x as with plain replication.


Veronica Estrada Galiñanes’ GSoC project was to model the impact that different replication schemes have on data durability in distributed systems. Veronica provided a thorough analysis starting with the existing system reliability. She then modeled several different approaches, including erasure coding and locally repairable codes. Although the analysis was focused on Ceph, it could be applied to any other object-based storage system.


This work provided a great methodology to analyze and confirm the redundancy and overall reliability of data within a Ceph system across a wide array of replication schemes. For the full student report, read Veronica's final report.


As we worked with the students, mentors, and other organization admins within the Google Summer of Code, we realized that students often have a different perspective of the world. This fresh perspective can offer insights and renewed enthusiasm that would otherwise be difficult to achieve. We found our experience with the program to be rewarding both in a tangible sense (code/developers) and, perhaps more importantly, in the intangible of new ideas and experience that will help broaden our ecosystem in the future. We hope to participate again next year!


By Patrick McGarry, Ceph Organization Administrator

]]> https://googledata.org/google-open-source/google-summer-of-code-wrap-up-ceph/feed/ 0 GSoC Reunion Recap with Abhishek Das https://googledata.org/google-open-source/gsoc-reunion-recap-with-abhishek-das/ https://googledata.org/google-open-source/gsoc-reunion-recap-with-abhishek-das/#comments Wed, 05 Nov 2014 21:00:00 +0000 https://googledata.org/?guid=9db59ce324ff0370bb9b21a636521202 To celebrate the tenth year of Google Summer of Code (GSoC), we recently welcomed over 500 people who’ve participated over the years to a special Reunion event. We’d like to share a few recaps of the event from the perspectives of students and mentors who joined us from 50 different countries. Today’s summary comes from Abhishek Das, a student participant in GSoC 2013 and 2014.



In celebration of the 10th anniversary of Google's prestigious Summer of Code program, they organized a reunion for mentors and students from the past 10 iterations of Summer of Code in San Jose, California from October 23-26. I attended the event as a student and a representative of the OWASP foundation.


I traveled from New Delhi, India and arrived in San Jose early morning on the 23rd and checked in at my hotel. I knew I'd be staying in the heart of Silicon Valley but was nonetheless pleasantly surprised to see the Adobe headquarters from my room! The evening was spent registering for the event and socializing with other developers who had flown in from all over the world. It was a delightful experience to randomly bump into developers and get to know about their organizations and open source projects.


The next day was a fun outing to the Great America theme park. Google had bought out the park for the whole day just for the summit attendees! That evening, a GSoC celebration event was held at the San Jose Tech Museum of Innovation. It was a wonderful (semi-)formal get together, full of geek speak and inspiring talks. Among the speakers were Chris DiBona, Alfred Spector, Peter Norvig, Dirk Hohndel and Linus Torvalds! Mr. DiBona talked about how he came up with the idea of Summer of Code and the immense impact it has had over the past 10 years as it continues to grow. Mr. Norvig's short inspiring talk mentioned how a bad craftsman blames his tools and how a good one wouldn't differentiate between the two. Hohndel emphasized the need and importance of valuing criticism. And Torvalds implored budding developers to develop good taste and to know what to keep and more importantly, what to throw away. Selfies with the guests followed alongside lavish drinks and buffet. 


The unconference sessions started Saturday morning. I loved the idea of having spontaneous sessions with lots of free interaction rather than the rigidity that is usually associated with conferences. Some sessions were run by Googlers but most were run by attendees. The first one I attended was by Grant Grundler (Googler) on Chrome OS. He talked about the future of Chrome OS and Android, the development cycle of a hardware-based product such as a Chromebook, the support model of Chrome OS and ended with a Q&A.

Next up was one on data visualization libraries. People talked about the libraries they were using and the applications they'd built using them. Others asked questions and lots of new ideas came up.

Among other sessions I attended were ones on Processing, bioinformatics (scope, ongoing work and future), artificial intelligence (again a brainstorming and ideation meetup), big data, robotics and Google Cardboard! There were also several lightning talks going on at the same time in the Ballroom where organization representatives introduced their projects in under 3 minutes. It’s always fun to listen to these quick talks and get familiar with their work.

Sunday morning began with the much awaited trip to the Googleplex.


Sessions continued till the afternoon after which we had to bid farewell. Carol Smith conducted the feedback session and delivered the closing address.

It was an absolutely awesome event. The feeling of getting to meet FOSS superstars in person, people who I'd been following on GitHub or Twitter for a while, was inexplicable. The idea of having a sticker exchange as well as a chocolate room was perfect. And most importantly, the organisers got all the basic things spot on: get open source developers from different backgrounds in one place and make it as comfortable as possible for them to interact and have productive discussions with each other (no shuttling between the conference venue and accommodation, free and fast WiFi, awesome food and drinks, a formal celebratory dinner, schwag, and so on). A big shout out to Carol, Chris, Stephanie, and the entire Google Open Source Programs team for an amazing event!


By Abhishek Das

]]> To celebrate the tenth year of Google Summer of Code (GSoC), we recently welcomed over 500 people who’ve participated over the years to a special Reunion event. We’d like to share a few recaps of the event from the perspectives of students and mentors who joined us from 50 different countries. Today’s summary comes from Abhishek Das, a student participant in GSoC 2013 and 2014.



In celebration of the 10th anniversary of Google's prestigious Summer of Code program, they organized a reunion for mentors and students from the past 10 iterations of Summer of Code in San Jose, California from October 23-26. I attended the event as a student and a representative of the OWASP foundation.


I traveled from New Delhi, India and arrived in San Jose early morning on the 23rd and checked in at my hotel. I knew I'd be staying in the heart of Silicon Valley but was nonetheless pleasantly surprised to see the Adobe headquarters from my room! The evening was spent registering for the event and socializing with other developers who had flown in from all over the world. It was a delightful experience to randomly bump into developers and get to know about their organizations and open source projects.


The next day was a fun outing to the Great America theme park. Google had bought out the park for the whole day just for the summit attendees! That evening, a GSoC celebration event was held at the San Jose Tech Museum of Innovation. It was a wonderful (semi-)formal get together, full of geek speak and inspiring talks. Among the speakers were Chris DiBona, Alfred Spector, Peter Norvig, Dirk Hohndel and Linus Torvalds! Mr. DiBona talked about how he came up with the idea of Summer of Code and the immense impact it has had over the past 10 years as it continues to grow. Mr. Norvig's short inspiring talk mentioned how a bad craftsman blames his tools and how a good one wouldn't differentiate between the two. Hohndel emphasized the need and importance of valuing criticism. And Torvalds implored budding developers to develop good taste and to know what to keep and more importantly, what to throw away. Selfies with the guests followed alongside lavish drinks and buffet. 


The unconference sessions started Saturday morning. I loved the idea of having spontaneous sessions with lots of free interaction rather than the rigidity that is usually associated with conferences. Some sessions were run by Googlers but most were run by attendees. The first one I attended was by Grant Grundler (Googler) on Chrome OS. He talked about the future of Chrome OS and Android, the development cycle of a hardware-based product such as a Chromebook, the support model of Chrome OS and ended with a Q&A.

Next up was one on data visualization libraries. People talked about the libraries they were using and the applications they'd built using them. Others asked questions and lots of new ideas came up.

Among other sessions I attended were ones on Processing, bioinformatics (scope, ongoing work and future), artificial intelligence (again a brainstorming and ideation meetup), big data, robotics and Google Cardboard! There were also several lightning talks going on at the same time in the Ballroom where organization representatives introduced their projects in under 3 minutes. It’s always fun to listen to these quick talks and get familiar with their work.

Sunday morning began with the much awaited trip to the Googleplex.


Sessions continued till the afternoon after which we had to bid farewell. Carol Smith conducted the feedback session and delivered the closing address.

It was an absolutely awesome event. The feeling of getting to meet FOSS superstars in person, people who I'd been following on GitHub or Twitter for a while, was inexplicable. The idea of having a sticker exchange as well as a chocolate room was perfect. And most importantly, the organisers got all the basic things spot on: get open source developers from different backgrounds in one place and make it as comfortable as possible for them to interact and have productive discussions with each other (no shuttling between the conference venue and accommodation, free and fast WiFi, awesome food and drinks, a formal celebratory dinner, schwag, and so on). A big shout out to Carol, Chris, Stephanie, and the entire Google Open Source Programs team for an amazing event!


By Abhishek Das

]]> https://googledata.org/google-open-source/gsoc-reunion-recap-with-abhishek-das/feed/ 0 Google Summer of Code wrapup: The Concord Consortium https://googledata.org/google-open-source/google-summer-of-code-wrapup-the-concord-consortium/ https://googledata.org/google-open-source/google-summer-of-code-wrapup-the-concord-consortium/#comments Fri, 31 Oct 2014 17:00:00 +0000 https://googledata.org/?guid=fe38df68f13153f59d23cd3de5fc7b59 Today’s Google Summer of Code wrap-up comes from Cynthia McIntyre at the Concord Consortium, a provider of online educational activities.


The Concord Consortium is a non profit R&D organization based in Concord, MA, dedicated to transforming education through technology. Our digital tools and learning activities capture the power of curiosity and create revolutionary new approaches to science, math and engineering education that bring out the inner scientist in everyone.


Our two Google Summer of Code students did a fabulous job this summer.


Mobile-friendly HTML5 Seismic Eruption 
mash-up
Abhinav Mukherjee worked on an HTML5 version of the popular Seismic Eruption software. (The original version ran only on Windows.) He has created a client side application that pulls data from the U.S. Geological Survey and displays it both on a 2D map using leaflet and in 3D space using three.js.


The software shows a visual display of the distribution, depth and magnitude/strength of the earthquakes and eruptions, as well as popup information about the type of volcano, date of eruption and information about plate boundaries. A user can cut a cross section into the 2D map, then choose the 3D view, or adjust the time range of the data being displayed in order to focus on certain earthquakes. We look forward to embedding this software in Earth science activities for middle and high school teachers.


Data analytics for user actions in HTML5 web apps
For our educational research, we would like to be able to capture detailed logs of student actions in browser-based activities, then analyze the data in a shared tool. Peeyush Agarwal worked on the Data Analytics Log Manager, a new server-side application that makes it easier for any project to log user events and then view them using CODAP (our Common Online Data Analysis Platform).


Logs from HTML5 applications or other client-side apps (e.g. Java) can be posted to the log manager, which stores them and provides access to registered researchers. The logs can then be filtered and transformed through a variety of methods (adding calculated metadata, adding new "synthetic events" by pattern matching) before being imported into CODAP for visual analysis.


By Cynthia McIntyre, The Concord Consortium Organization Administrator
]]> Today’s Google Summer of Code wrap-up comes from Cynthia McIntyre at the Concord Consortium, a provider of online educational activities.


The Concord Consortium is a non profit R&D organization based in Concord, MA, dedicated to transforming education through technology. Our digital tools and learning activities capture the power of curiosity and create revolutionary new approaches to science, math and engineering education that bring out the inner scientist in everyone.


Our two Google Summer of Code students did a fabulous job this summer.


Mobile-friendly HTML5 Seismic Eruption 
mash-up
Abhinav Mukherjee worked on an HTML5 version of the popular Seismic Eruption software. (The original version ran only on Windows.) He has created a client side application that pulls data from the U.S. Geological Survey and displays it both on a 2D map using leaflet and in 3D space using three.js.


The software shows a visual display of the distribution, depth and magnitude/strength of the earthquakes and eruptions, as well as popup information about the type of volcano, date of eruption and information about plate boundaries. A user can cut a cross section into the 2D map, then choose the 3D view, or adjust the time range of the data being displayed in order to focus on certain earthquakes. We look forward to embedding this software in Earth science activities for middle and high school teachers.


Data analytics for user actions in HTML5 web apps
For our educational research, we would like to be able to capture detailed logs of student actions in browser-based activities, then analyze the data in a shared tool. Peeyush Agarwal worked on the Data Analytics Log Manager, a new server-side application that makes it easier for any project to log user events and then view them using CODAP (our Common Online Data Analysis Platform).


Logs from HTML5 applications or other client-side apps (e.g. Java) can be posted to the log manager, which stores them and provides access to registered researchers. The logs can then be filtered and transformed through a variety of methods (adding calculated metadata, adding new "synthetic events" by pattern matching) before being imported into CODAP for visual analysis.


By Cynthia McIntyre, The Concord Consortium Organization Administrator
]]> https://googledata.org/google-open-source/google-summer-of-code-wrapup-the-concord-consortium/feed/ 0 Google Summer of Code wrapup: OpenMRS https://googledata.org/google-open-source/google-summer-of-code-wrapup-openmrs/ https://googledata.org/google-open-source/google-summer-of-code-wrapup-openmrs/#comments Fri, 24 Oct 2014 17:00:00 +0000 https://googledata.org/?guid=fb1adf70a7ddb925e80bd3a43d237cac As a long-time Google Summer of Code participant, OpenMRS had twelve Google Summer of Code students in 2014. One of those students, Stephen Po-Chedley, writes more about his experience below as well as other students’ projects.


OpenMRS logo

Waking up to an uneventful landing in September 2013, I found our plane surrounded by dry grass fields. I couldn’t even tell that we were on a runway. I had slept through the approach over small clay houses and family gardens. This small, dusty country of Malawi is where I would spend the next year.

Prior to Autumn 2013, I had been a PhD student studying climate change in Seattle. As part of my research, I was constantly working through random technical and computational challenges. It seemed like every week I was hacking together some code in some unfamiliar language. While the work was challenging and interesting, I wanted to take some time away from my studies to apply some of these technological skills to issues even more acute than climate change.

Upon deplaning, I stepped away from supercomputers meant for climate research and found myself in Malawi working with barely functional laptops. As a volunteer with a health NGO in Malawi, I was slotted to help support the OpenMRS based electronic medical records system that was crucial for monitoring and evaluating the remote district’s health progress. OpenMRS is an open source medical records system used on every continent. The system was created to help provide management tools to meet global health challenges, especially in resource poor countries.

I quickly understood why OpenMRS was such an important tool. The system could generate reports to help us track down patients that had missed appointments, we could flag people who needed a change in medication or a new lab test, doctors could get an overview of their clinical practices, and clinical programs could get a snapshot of their patient cohorts.

Of course, any information that we derive is only as good as the data it comes from. With an entire district of health data being fed into the system, it is easy to miss some parts of records or mis-enter information. Any errors have the potential to affect patient care or high-level decisions made about programs. We need not only good data, but to also understand the quality of the data we have. And this is where Google Summer of Code (GSoC) became so important.

Over the last few months, I was able to work with mentors to design and begin to build a module within OpenMRS to help assess data quality. Beginning work on the project was terrifying for me because my programming experience was mostly hacking together code for scientific analysis. Most of my programming education has been through exhaustive Google searches and discussions with fellow geeks, but this was nearly impossible in Malawi working off of an unreliable satellite internet connection with pretty limited bandwidth.

But I could see that the project was important. My mentors were awesome and the OpenMRS community was incredibly supportive, offering invaluable advice to those that are new to the community. Throughout the summer, I learned a ton of new technologies and — together with my mentors — made a lot of progress on our project.


Group photo climbing a mountain
Myself (crouching lower left) with my mentor Cosmin Ioan (standing left), and other colleagues climbing Sapitwa Mountain in Malawi.

Being involved with OpenMRS and Google Summer of Code 2014 was incredibly exciting and I feel fortunate that there are opportunities to continue to stay involved with the community. One important lesson was that open source projects have all kinds of ways to help. The OpenMRS tagline for GSoC is “Write code. Save Lives.” From my experience as an implementer and developer of OpenMRS, that motto rings completely true. It has been inspiring to see code pieced together by a diverse community of contributors from all over the planet to create a system that is literally saving lives.

You need look no further than the projects worked on during GSoC 2014 to get an idea of all the important work going on at OpenMRS:


On behalf of all the students involved with OpenMRS and the Google Summer of Code 2014, thank you to OpenMRS and to Google for supporting our work and to our mentors that helped make the summer so successful. It was an incredible opportunity to learn so much from world-class mentors, be involved in important work that makes a huge difference, and to get exposure to the rich communities that support open source projects.

By Stephen Po-Chedley, OpenMRS Student, 2014

]]> As a long-time Google Summer of Code participant, OpenMRS had twelve Google Summer of Code students in 2014. One of those students, Stephen Po-Chedley, writes more about his experience below as well as other students’ projects.


OpenMRS logo

Waking up to an uneventful landing in September 2013, I found our plane surrounded by dry grass fields. I couldn’t even tell that we were on a runway. I had slept through the approach over small clay houses and family gardens. This small, dusty country of Malawi is where I would spend the next year.

Prior to Autumn 2013, I had been a PhD student studying climate change in Seattle. As part of my research, I was constantly working through random technical and computational challenges. It seemed like every week I was hacking together some code in some unfamiliar language. While the work was challenging and interesting, I wanted to take some time away from my studies to apply some of these technological skills to issues even more acute than climate change.

Upon deplaning, I stepped away from supercomputers meant for climate research and found myself in Malawi working with barely functional laptops. As a volunteer with a health NGO in Malawi, I was slotted to help support the OpenMRS based electronic medical records system that was crucial for monitoring and evaluating the remote district’s health progress. OpenMRS is an open source medical records system used on every continent. The system was created to help provide management tools to meet global health challenges, especially in resource poor countries.

I quickly understood why OpenMRS was such an important tool. The system could generate reports to help us track down patients that had missed appointments, we could flag people who needed a change in medication or a new lab test, doctors could get an overview of their clinical practices, and clinical programs could get a snapshot of their patient cohorts.

Of course, any information that we derive is only as good as the data it comes from. With an entire district of health data being fed into the system, it is easy to miss some parts of records or mis-enter information. Any errors have the potential to affect patient care or high-level decisions made about programs. We need not only good data, but to also understand the quality of the data we have. And this is where Google Summer of Code (GSoC) became so important.

Over the last few months, I was able to work with mentors to design and begin to build a module within OpenMRS to help assess data quality. Beginning work on the project was terrifying for me because my programming experience was mostly hacking together code for scientific analysis. Most of my programming education has been through exhaustive Google searches and discussions with fellow geeks, but this was nearly impossible in Malawi working off of an unreliable satellite internet connection with pretty limited bandwidth.

But I could see that the project was important. My mentors were awesome and the OpenMRS community was incredibly supportive, offering invaluable advice to those that are new to the community. Throughout the summer, I learned a ton of new technologies and — together with my mentors — made a lot of progress on our project.


Group photo climbing a mountain
Myself (crouching lower left) with my mentor Cosmin Ioan (standing left), and other colleagues climbing Sapitwa Mountain in Malawi.

Being involved with OpenMRS and Google Summer of Code 2014 was incredibly exciting and I feel fortunate that there are opportunities to continue to stay involved with the community. One important lesson was that open source projects have all kinds of ways to help. The OpenMRS tagline for GSoC is “Write code. Save Lives.” From my experience as an implementer and developer of OpenMRS, that motto rings completely true. It has been inspiring to see code pieced together by a diverse community of contributors from all over the planet to create a system that is literally saving lives.

You need look no further than the projects worked on during GSoC 2014 to get an idea of all the important work going on at OpenMRS:


On behalf of all the students involved with OpenMRS and the Google Summer of Code 2014, thank you to OpenMRS and to Google for supporting our work and to our mentors that helped make the summer so successful. It was an incredible opportunity to learn so much from world-class mentors, be involved in important work that makes a huge difference, and to get exposure to the rich communities that support open source projects.

By Stephen Po-Chedley, OpenMRS Student, 2014

]]> https://googledata.org/google-open-source/google-summer-of-code-wrapup-openmrs/feed/ 0 Introducing the Google APIs Terms of Service and an update to Code Labs https://googledata.org/google-code/introducing-the-google-apis-terms-of-service-and-an-update-to-code-labs/ https://googledata.org/google-code/introducing-the-google-apis-terms-of-service-and-an-update-to-code-labs/#comments Tue, 13 Dec 2011 00:07:00 +0000 https://googledata.org/?guid=a0743164c4ce0ff94245cf248cbe030e By Adam Feldman, APIs Product Manager

The Google APIs Terms of Service

Beginning today, most of our APIs use a single Terms of Service. We have rewritten these terms from the ground up with the goals of making them concise and easier to understand.Our intent is to simplify, not to make dramatic functional changes.

For all the APIs that share this single Terms of Service, you won’t need to study a whole new document, although some have brief specific Additional Terms.  In this rewrite, we have removed over 125,000 words from the combined previous terms, resulting in less to read and faster access to your favorite APIs.  Over time, other APIs will be migrated to the new terms.  Please review each API’s documentation to see its terms.

The new Terms of Service is another step in making Google APIs more technically consistent by sharing common infrastructure such as the Discovery service, the APIs Explorer, and the APIs Console.

Removing the Code Labs Label

In order to reduce confusion we're removing the Code Labs label from APIs on code.google.com. The Google Labs program has wound down. APIs formerly in Code Labs will now use the standard header in their documentation. The APIs themselves are unchanged.

Adam Feldman is a Product Manager, focusing on all of Google's APIs and making sure Google provides the best possible platform to developers.

Posted by Ashleigh Rentz, Editor Emerita

]]> https://googledata.org/google-code/introducing-the-google-apis-terms-of-service-and-an-update-to-code-labs/feed/ 0 What Does It Mean To Be A Google Developer? Share Your Story https://googledata.org/google-code/what-does-it-mean-to-be-a-google-developer-share-your-story/ https://googledata.org/google-code/what-does-it-mean-to-be-a-google-developer-share-your-story/#comments Wed, 28 Sep 2011 19:14:00 +0000 https://googledata.org/?guid=d1a120b6f82dbe3a0268611fc88ee34f Author PictureBy Amy Walgenbach, Google Developer Marketing

Our developer program started in 2005 with a handful of APIs and developer advocates. Fast forward to today: Google offers over 100 APIs, dozens of developer tools, and a raft of developer advocates around the world. Obviously, a lot has changed and the Web has matured significantly. Google has also evolved and matured, and we felt that it was time to step back and rethink how we interact with and support our developer community. We believe we can make it easier to find what you’re looking for, and facilitate connections with others in the Google Developer community. We know we can do better and we want your input so that we can understand your needs — and what drives you — better.


Now we want to hear from you.

We want to know what inspires you as a developer and how Google can support you. What does being a Google developer mean to you? Tell us what’s important to you and how we can make your experience as a Google developer better. Like any good open source project, the Google developers project needs your contributions. Share your story so we can we better support your success — and we may just pick you to be featured.

You can add a video (it's easy, really!) directly from the page, on your mobile phone, or write to us here. However you share with us, we’re looking forward to hearing what you have to say.


Amy Walgenbach is the Product Marketing lead for the Google+ platform and leads developer marketing for games at Google.

Posted by Ashleigh Rentz, Editor Emerita
]]> https://googledata.org/google-code/what-does-it-mean-to-be-a-google-developer-share-your-story/feed/ 0