Author Archives: Open Source Programs Office

Google Summer of Code 2019 (Statistics Part 1)

Since 2005, Google Summer of Code (GSoC) has been bringing new developers into the open source community every year. This year, we accepted 1,276 students from 63 countries into the 2019 GSoC program to work with 201 open source organizations over the summer.

Students are currently wrapping up the Community Bonding phase where they become familiar with the open source projects they will be working with by spending time learning the codebase, the community’s best practices, and integrating into the community. Students will start their 12-week coding projects on May 29th.

Each year we like to share program statistics about the GSoC program and the accepted students and mentors involved in the program.

Accepted Students

  • 89.2% are participating in their first GSoC
  • 75% are first time applicants

Degrees

  • 77.5% are undergraduates, 16.6% are masters students, and 5.9% are in PhD programs
  • 72.8% are Computer Science majors, 3.5% are Mathematics majors, 16.8% are other Engineering majors (Electrical, Mechanical, Aerospace, etc.)
  • Students are in a variety of majors including Atmospheric Science, Neuroscience, Economics, Linguistics, Geology, and Pharmacy.

Proposals

There were a record number of students submitting proposals for the program this year: 5,606 students from 103 countries submitted 7,555 proposals.

In our next GSoC statistics post we will delve deeper into the schools, gender breakdown, mentors, and registration numbers for the 2019 program.

By Stephanie Taylor, Google Open Source

Google and Binomial Partner to Open-Source Basis Universal Texture Format

Today, Google and Binomial are excited to announce that we have partnered to open source the Basis Universal texture codec to improve the performance of transmitting images on the web and within desktop and mobile applications, while maintaining GPU efficiency. This release fills an important gap in the graphics compression ecosystem and complements earlier work in Draco geometry compression.

The Basis Universal texture format is 6-8 times smaller than JPEG on the GPU, yet is a similar storage size as JPEG – making it a great alternative to current GPU compression methods that are inefficient and don’t operate cross platform – and provides a more performant alternative to JPEG/PNG. It creates compressed textures that work well in a variety of use cases - games, virtual & augmented reality, maps, photos, small-videos, and more!

Without a universal texture format, developers are left with 2 options:

  • Use GPU formats and take the storage size hit.
  • Use other formats that have reduced storage size but couldn't compete with the GPU performance.

Maintaining so many different GPU formats is a burden on the whole ecosystem, from GPU manufacturers to software developers to the end user who can’t get a great cross platform experience. We’re streamlining this with one solution that has built-in flexibility (like optional higher quality modes) but is much easier on everyone to improve and maintain.

How does it all work? Compress your image using the encoder, choosing the quality settings that make sense for your project (you can also submit multiple images for small videos or optimization purposes, just know they’ll share the same color palette). Insert the transcoder code before rendering, which will turn the intermediary format into the GPU format your computer can read. The image stays compressed throughout this process, even on your GPU!  Instead of needing to decode and read the whole image, the GPU will read only the parts it needs. Enjoy the performance benefits!
Basis Universal can efficiently target the most common GPU formats
Google and Binomial will be working together to continue to support, maintain and add features, so check back frequently for the latest. This initial release of Basis Universal transcodes into the following GPU formats: PVRTC1 opaque, ETC1, ETC2 basic alpha, BC1-5, and BC7 opaque. Over the coming months more functionality will be added including BC7 transparent, ASTC opaque and alpha, PVRTC1 transparent, and higher quality BC7/ASTC.
Basis Universal reduces transmission size for texture while maintaining similar image quality.
See full benchmarking results
Basis Universal improves GPU memory usage over .jpeg and .png
With this partnership, we hope to see adoption of the transcoder in all major browsers to make performant cross-platform compressed textures accessible to everyone via the WebGL API, and the forthcoming WebGPU API. In addition to opening up the possibility of seamless integration into pipelines, everyone now has access to the state of the art compressor, which will also be open sourced.

We look forward to seeing what people do with Basis Universal now that it's open sourced. Check out the code and demo on GitHub, let us know what you think, and how you plan to use it! Currently, Basis Universal transcoders are available in C++ and WebAssembly.

By Stephanie Hurlburt, Binomial and Jamieson Brettle, Chrome Media

OpenTelemetry: The Merger of OpenCensus and OpenTracing

We’ve talked about OpenCensus a lot over the past few years, from the project’s initial announcement, roots at Google and partners (Microsoft, Dynatrace) joining the project, to new functionality that we’re continually adding. The project has grown beyond our expectations and now sports a mature ecosystem with Google, Microsoft, Omnition, Postmates, and Dynatrace making major investments, and a broad base of community contributors.

We recently announced that OpenCensus and OpenTracing are merging into a single project, now called OpenTelemetry, which brings together the best of both projects and has a frictionless migration experience. We’ve made a lot of progress so far: we’ve established a governance committee, a Java prototype API + implementation, workgroups for each language, and an aggressive implementation schedule.

Today we’re highlighting the combined project at the keynote of Kubecon and announcing that OpenTelemetry is now officially part of the Cloud Native Computing Foundation! Full details are available in the CNCF’s official blog post, which we’ve copied below:

A Brief History of OpenTelemetry (So Far)

After many months of planning, discussion, prototyping, more discussion, and more planning, OpenTracing and OpenCensus are merging to form OpenTelemetry, which is now a CNCF sandbox project. The seed governance committee is composed of representatives from Google, Lightstep, Microsoft, and Uber, and more organizations are getting involved every day.

And we couldn't be happier about it – here’s why.

Observability, Outputs, and High-Quality Telemetry

Observability is a fashionable word with some admirably nerdy and academic origins. In control theory, “observability” measures how well we can understand the internals of a given system using only its external outputs. If you’ve ever deployed or operated a modern, microservice-based software application, you have no doubt struggled to understand its performance and behavior, and that’s because those “outputs” are usually meager at best. We can’t understand a complex system if it’s a black box. And the only way to light up those black boxes is with high-quality telemetry: distributed traces, metrics, logs, and more.

So how can we get our hands – and our tools – on precise, low-overhead telemetry from the entirety of a modern software stack? One way would be to carefully instrument every microservice, piece by piece, and layer by layer. This would literally work, it’s also a complete non-starter – we’d spend as much time on the measurement as we would on the software itself! We need telemetry as a built-in feature of our services.

The OpenTelemetry project is designed to make this vision a reality for our industry, but before we describe it in more detail, we should first cover the history and context around OpenTracing and OpenCensus.

OpenTracing and OpenCensus

In practice, there are several flavors (or “verticals” in the diagram) of telemetry data, and then several integration points (or “layers” in the diagram) available for each. Broadly, the cloud-native telemetry landscape is dominated by distributed traces, timeseries metrics, and logs; and end-users typically integrate with a thin instrumentation API or via straightforward structured data formats that describe those traces, metrics, or logs.



For several years now, there has been a well-recognized need for industry-wide collaboration in order to amortize the shared cost of software instrumentation. OpenTracing and OpenCensus have led the way in that effort, and while each project made different architectural choices, the biggest problem with either project has been the fact that there were two of them. And, further, that the two projects weren’t working together and striving for mutual compatibility.

Having two similar-yet-not-identical projects out in the world created confusion and uncertainty for developers, and that made it harder for both efforts to realize their shared mission: built-in, high-quality telemetry for all.

Getting to One Project

If there’s a single thing to understand about OpenTelemetry, it’s that the leadership from OpenTracing and OpenCensus are co-committed to migrating their respective communities to this single and unified initiative. Although all of us have numerous ideas about how we could boil the ocean and start from scratch, we are resisting those impulses and focusing instead on preparing our communities for a successful transition; our priorities for the merger are clear:
  • Straightforward backwards compatibility with both OpenTracing and OpenCensus (via software bridges)
  • Minimizing the time where OpenTelemetry, OpenTracing, and OpenCensus are being co-developed: we plan to put OpenTracing and OpenCensus into “readonly mode” before the end of 2019.
  • And, again, to simplify and standardize the telemetry solutions available to developers.
In many ways, it’s most accurate to think of OpenTelemetry as the next major version of both OpenTracing and OpenCensus. Like any version upgrade, we will try to make it easy for both new and existing end-users, but we recognize that the main benefit to the ecosystem is the consolidation itself – not some specific and shiny new feature – and we are prioritizing our own efforts accordingly.

How you can help

OpenTelemetry’s timeline is an aggressive one. While we have many open-source and vendor-licensed observability solutions providing guidance, we will always want as many end-users involved as possible. The single most valuable thing any end-user can do is also one of the easiest: check out the actual work we’re doing and provide feedback. Via GitHub, Gitter, email, or whatever feels easiest.

Of course we also welcome code contributions to OpenTelemetry itself, code contributions that add OpenTelemetry support to existing software projects, documentation, blog posts, and the rest of it. If you’re interested, you can sign up to join the integration effort by filling in this form.

By Ben Sigelman, co-creator of OpenTracing and member of the OpenTelemetry governing committee, and Morgan McLean, Product Manager for OpenCensus at Google since the project’s inception

Summer is here! Welcome to our 2019 GSoC Students!


After reviewing 7,555 student proposals, our 206 mentoring organizations have chosen the 1,276 students they will be working with during the 15th Google Summer of Code (GSoC). Congratulations to our 2019 GSoC students and a big thank you to everyone who applied. This year’s students come from 64 countries!

The next step for participating students is the Community Bonding period which runs from May 6 through May 27. During this time, students will get up to speed on the culture and code base of their new community. They’ll also get acquainted with their mentor(s) and learn more about the languages or tools that they will need to complete their projects. Coding begins May 27 and will continue throughout the summer until August 26.

If you were not selected for this year’s Summer of Code - don’t be discouraged! Many students apply more than once to GSoC before being accepted. You can improve your odds for next time by contributing to the open source project of your choice directly now; organizations are always eager for new contributors! Look around for a project that interests you and get started.

Happy coding, everyone!

By Stephanie Taylor, GSoC Program Lead

Season of Docs announces participating organizations

Season of Docs has announced the 50 participating open source organizations! You can view the list of participating organizations on the website.

Technical writer applications open on May 29, 2019 at 18:00 UTC. 

During the technical writer exploration phase, which runs from now until May 28, 2019, technical writers can explore the list of participating organizations and their project ideas. They should reach out to the organizations to gain a better understanding of the organizations and discuss project ideas before applying to Season of Docs.

For more information about the technical writer exploration phase, visit the technical writer guide on the website.

What is Season of Docs?

Documentation is essential to the adoption of open source projects as well as to the success of their communities. Season of Docs brings together technical writers and open source projects to foster collaboration and improve documentation in the open source space. You can find out more about the program on the introduction page of the website.

During the program, technical writers spend a few months working closely with an open source community. They bring their technical writing expertise to the project's documentation and, at the same time, learn about the open source project and new technologies.

The open source projects work with the technical writers to improve the project's documentation and processes. Together, they may choose to build a new documentation set, redesign the existing docs, or improve and document the project's contribution procedures and onboarding experience.

How do I take part in Season of Docs as a technical writer?

First, take a look at the technical writer guide on the website. The guide includes information on eligibility and the application process.

The technical writer exploration phase runs from April 30 - May 28, 2019. During this period, you can explore the list of participating organizations and their project ideas. When you find one or more projects that interest you, you should approach the relevant open source organization directly to discuss project ideas.

Then, read create a technical writing application and prepare your application materials. On May 29, 2019 at 18:00 UTC, Season of Docs will begin accepting technical writer applications and publish a link to the application form on the website. The deadline for technical writer applications is June 28, 2019 at 18:00 UTC.

Is there a stipend for participating technical writers?

Yes. There is an optional stipend that technical writers can request as part of their application. The stipend amount is calculated based on the technical writer's home location. See the technical writer stipends page for more information.

If you have any questions about the program, please email us at [email protected].

General timeline

  • April 30 - May 28: Technical writers explore the list of participating organizations and project ideas.
  • May 29 - June 28: Technical writers submit their proposals to Season of Docs. 
  • July 30: Google announces the accepted technical writer projects
  • August 1 - September 1: Community bonding: Technical writers get to know mentors and the open source community, and refine their projects in collaboration with their mentors.
  • September 2 - November 29: Technical writers work with open source mentors on the accepted projects, and submit their work at the end of the period.
  • December 10: Google publishes the list of successfully-completed projects.
See the full timeline for details, including the provision for projects that run longer than three months.

Care to join us?

Explore the Season of Docs website at g.co/seasonofdocs to learn more about participating in the program. Use our logo and other promotional resources to spread the word. Examine the timeline, check out the FAQ, and apply now!

By Andrew Chen, Google Open Source and Sarah Maddox, Google Technical Writer

Google Open Source Peer Bonus winners are here!

At Google we’ve always used open source to innovate, build amazing products, and bring better technology to the world. We also enjoy being part of the community and are always looking for ways to give back.

In 2011 we launched the Google Open Source Peer Bonus program with the goal of supporting the ecosystem and sustainability of open source by rewarding external developers for their contributions to open source projects. Over the years the program has grown and expanded. Now we reward not just software developers but all types of contributors, including technical writers, user experience and graphic designers, community managers and marketers, mentors and educators, ops and security experts.

We are very pleased to announce the latest Google Open Source Peer Bonus Winners and their projects. We have a record number of 90 recipients this cycle representing 20 countries all over the world: Australia, Belgium, Canada, China, France, Germany, India, Italy, Japan, the Netherlands, Poland, Russia, Singapore, Slovakia, South Africa, Spain, Sweden, United Kingdom, Ukraine and USA.

Below is the list of projects and awardees who gave us permission to thank them publicly:
Name Project Name Project
Cyril TovenaAgonesVincent DemeesterKnative Build Pipeline
Rebecca CloseAMPHTMLNader Ziadaknative/build
Leon TanAMPHTMLJim AngelKubernetes
Wassim CheghamAngularZach ArnoldKubernetes
Paul GschwendtnerAngular MaterialSerguei BezverkhiKubernetes
Maxim KoretskyiAngular-in-depth blogDamini Satya KammakomatiKubernetes
Kaxil NaikApache AirflowJennifer RondeauKubernetes
Kohei SutouApache ArrowMichael FrombergerKythe
Matthias BaetensApache BeamMark BrownLinux kernel
Lukazs GajowyApache BeamLuis ChamberlainLinux Kernel
Suneel MarthiApache BeamTetsuo HandaLinux kernel
Maximilian MichelsApache BeamTakashi IwaiLinux kernel
Alex Van BoxelApache BeamHeiko StuebnerLinux Kernel
Thomas WeiseApache BeamCong WangLinux kernel
Julian HydeApache CalciteRichard HughesLinux Vendor Firmware Service
Lan SunApache GroovyAaron PuchertLLVM/ Clang
Campion FellinApps Script CLI – ClaspOrne BrocaarLoRa Server
Nicolò RibaudoBabelGraeme RocherMicronaut
Rong Jie LooBazelAnders F Björklundminikube
Dave MielkeBRLTTYIskren ChernevMoment JS
Raphael Kubo da CostaChromiumTim DeschryverNgRx
Mike BanoncorebootBrandon RobertsNgRx
Elyes HaouascorebootEelco DolstraNixOS
Angel PonscorebootGuy BedfordNode.js
Ansgar BurchardtDebianYaw AnokwaOpen Data Kit
Chris LambDebian's Reproducible BuildsAndreas BartelsOpen Location Code
Zach LeathermaneleventyWes McKinneypandas
Vladimir GlavnyyFlatBuffersPradyun Gedampip
Alexandre ArdhuinFlutterMarvin Hagemeisterpreact
Kyle WongFlutterAndre Wigginspreact
Duncan LyallForseti SecurityChris Rocheprotoc-gen-validate (PGV)
Ross ScroggsGAM (Google Apps Manager)Ernest DurbinPython Package Index (PyPI)
Gert van DijkGerritRamon Santamariaraylib
Luca MilanesioGerrit Code ReviewAleksa SarairunC
David OstrovskyGerrit Code ReviewCornelius Weigskaffold
David PursehouseGerrit Code ReviewAnton Lindqvistsyzkaller
Matthias SohnGerrit Code ReviewZdenko PodobnýTesseract
Derrick StoleeGitKeqiu HuTonY
Roman LebedevGoogle BenchmarkBasarat Ali SyedTypeScript Deep Dive (book)
Florent Revestgooglecartographer/cartographer_rosPeter WongV8
Kirill KatsnelsongRPCKevin MurrayVerilog to Routing
Eddie KohlerhotcrpDarrell CommanderVirtualGL
Daniel-Constantin MierlaKamailioLin ClarkWasi + Wasmtime
Philipp CrocollKeepass2Android Password SafeSébastien HelleuWeechat
Shashwathi ReddyKnative buildWesley ShieldsYara
Congratulations to our recipients! We look forward to your continued support and contributions to open source!

By Maria Tabak, Google Open Source

Bringing the best of open source to Google Cloud customers


Google’s belief in an open cloud stems from our deep commitment to open source. We believe open source is an essential part of the public cloud: It’s the foundation of IT infrastructure worldwide and has been a part of Google’s foundation since day one. This is reflected in our contributions to projects like Kubernetes, TensorFlow, Go, and many more.

Today, we’re taking our commitment to open source to the next level by announcing strategic partnerships with leading open source-centric companies in the areas of data management and analytics, including:
  • Confluent
  • DataStax
  • Elastic
  • InfluxData
  • MongoDB
  • Neo4j
  • Redis Labs
We’ve always seen our friends in the open-source community as equal collaborators, and not simply a resource to be mined. With that in mind, we’ll be offering managed services operated by these partners that are tightly integrated into Google Cloud Platform (GCP), providing a seamless user experience across management, billing and support. This makes it easier for our enterprise customers to build on open source technologies, and it delivers on our commitment to continually support and grow these open source communities.

Making open source even more accessible with a cloud-native experience

The open-source database market is big, and growing fast. According to SearchDataManagement.com, “more than 70% of new applications developed by corporate users will run on an open source database management system, and half of the existing relational database installations built on commercial DBMS technologies will be converted to open source platforms or [are] in the process of being converted."

This mirrors what we hear from our customers—that you want to be able to use open-source technology easily and in a cloud-native way. The partnerships we are announcing today make this possible by offering an elevated experience similar to Google’s native services. It also means that you aren’t locked in or out when you are using these technologies—we think that’s important for our customers and our partners.

Here are some of the benefits these partnerships will offer:
  • Fully managed services running in the cloud, with best efforts made to optimize performance and latency between the service and application.
  • A single user interface to manage apps, which includes the ability to provision and manage the service from the Google Cloud Console.
  • Unified billing, so you get one invoice from Google Cloud that includes the partner’s service.
  • Google Cloud support for the majority of these partners, so you can manage and log support tickets in a single window and not have to deal with different providers.
To further our mission of making GCP the best destination for open source-based services, we will work with our partners to build integrations with native GCP services like Stackdriver for monitoring and IAM, validate these services for security, and optimize performance for users.

Partnering with leaders in open source

The partners we are announcing today include several of the top-ranked databases in their respective categories. We’re working alongside these creators and supporting the growth of these companies’ technologies to inspire strong customer experiences and adoption. These new partners include:

Confluent: Founded by the team that built Apache Kafka, Confluent builds an event streaming platform that lets companies easily access data as real-time streams. Learn more.

DataStax: DataStax powers enterprises with its always-on, distributed cloud database built on Apache Cassandra and designed for hybrid cloud. Learn more.

Elastic: As the creators of the Elastic Stack, Elastic builds self-managed and SaaS offerings that make data usable in real time and at scale for search use cases, like logging, security, and analytics. Learn more.

InfluxData: InfluxData’s time series platform can instrument, observe, learn and automate any system, application and business process across a variety of use cases. InfluxDB (developed by InfluxData) is an open-source time series database optimized for fast, high-availability storage and retrieval of time series data in fields such as operations monitoring, application metrics, IoT sensor data, and real-time analytics. Learn more.

MongoDB: MongoDB is a modern, general-purpose database platform that brings software and data to developers and the applications they build, with a flexible model and control over data location. Learn more.

Neo4j: Neo4j is a native graph database platform specifically optimized to map, store, and traverse networks of highly connected data to reveal invisible contexts and hidden relationships. By analyzing data points and the connections between them, Neo4j powers real-time applications. Learn more.

Redis Labs: Redis Labs is the home of Redis, the world’s most popular in-memory database, and commercial provider of Redis Enterprise. It offers performance, reliability, and flexibility for personalization, machine learning, IoT, search, e-commerce, social, and metering solutions worldwide. Learn more.

We’re pleased to bring these partner technologies to you. Partnering with the companies that invest in developing open-source technologies means you get benefits like expertise in operating these services at scale, additional enterprise features, and shorter cycles in bringing the latest innovation to the cloud. 

We look forward to seeing what you build with these open source technologies. Learn more here about open source on GCP.

By Chris DiBona, Director, Open Source and Kevin Ichhpurani, Corporate VP, Global Ecosystem and Business Development

Cross-posted from the Google Cloud Blog

Season of Docs now accepting organization applications

The newly launched Season of Docs program is excited to announce that organization applications are now open!

Deadline for organization applications:
April 23, 2019 at 20:00 UTC. 

Documentation is essential to the adoption of open source projects as well as to the success of their communities. Consequently, Season of Docs was created to bring together technical writers and open source projects to foster collaboration and improve documentation in the open source space. You can find out more about the program on the introduction page of the website.

How does my organization apply to take part in Season of Docs?

Open source organizations can now submit applications to participate in Season of Docs. First, read the organization administrator guide and guidelines for creating an organization application on the Season of Docs website.

Organizations can submit their applications here: https://forms.gle/axk8AvV561K2cT6S6.

Your organization application should include one or more projects that you would like a technical writer to work on. Take a look at the examples of project ideas, then describe one or more specific projects based on your open source project’s actual documentation needs. Your goal is to attract technical writers to your organization, making them feel comfortable about approaching the organization and excited about what they can achieve in collaboration with your mentors.

Reach out to your community members to see who would like to be a mentor for Season of Docs. They may also have great suggestions for project ideas. Mentors don’t need technical writing skills. Instead, they are members of the open source organization who know the value of good documentation and who are experienced in your organization’s processes and tools. See the guidelines on working with a technical writer.

Once you have selected mentors for your organization, have them register with Season of Docs using this form: https://forms.gle/a1x26WQGzURLerv66.

Organization applications close on April 23 at 20:00 UTC.

If you have any questions about the program, please email us at [email protected].

General timeline

  • April 2-23: Open source organizations apply to take part in Season of Docs
  • April 30: Google publishes the list of accepted mentoring organizations, along with their ideas for documentation projects
  • April 30 - June 28: Technical writers choose the project they’d like to work on and submit their proposals to Season of Docs 
  • July 30: Google announces the accepted technical writer projects
  • August 1 - September 1: Community bonding: Technical writers get to know mentors and the open source community, and refine their projects in collaboration with their mentors
  • September 2 - November 29: Technical writers work with open source mentors on the accepted projects, and submit their work at the end of the period
  • December 10: Google publishes the list of successfully-completed projects.
See the full timeline for details, including the provision for projects that run longer than three months.

Join us

Explore the Season of Docs website at g.co/seasonofdocs to learn more about participating in the program. Use our logo and other promotional resources to spread the word. Examine the timeline, check out the FAQ, and apply now!

By Andrew Chen, Google Open Source and Sarah Maddox, Google Technical Writer

Open sourcing Science Journal iOS



Google’s Science Journal app enables you to use the sensors in your mobile devices to perform science experiments. We believe anyone can be a scientist anywhere. Science doesn’t just happen in the classroom or lab—tools like Science Journal let you see how the world works with just your phone. From learning about sound and motion to discovering how atmospheric pressure works, Science Journal helps you understand and measure the world around you.

We’re extremely excited to announce that we’re open sourcing this powerful science tool. We know the heart of science is not just critical thinking, but also knowledge sharing, building on discoveries, and learning about the world. Have a student with a knack for building things? Do you want to learn how mobile applications are put together? Download our source code, make changes and discoveries, and then deploy the newly-modified app to your own iOS device.

Why open source?

Inquiring minds are always asking, “How does this work?” With our open source app, there are many science and engineering topics to explore! For example, we use the Fast Fourier transform in our iOS code, but you may ask “how did you do that?” Because you can see our source code, you can discover-- not just that we used the Fast Fourier transform-- but how the algorithm works. We also make it possible to graph many sensor values in realtime and now you can see exactly how we’ve made that possible.

If you aren’t an iOS or Android engineer, don’t fret! You can even learn how apps are put together so you can build your own. Learning from, and making modifications to, open source code has helped countless Google engineers explore complicated topics and learn new skills.



Have you ever wished you could do something with Science Journal that it doesn’t currently do? Do you have an idea for building a new sensor and displaying its data in Science Journal? Maybe you’ve wanted to experiment with changing colors or fonts in the app, or even changing the Science Journal app icon to be a labrador with a lab coat? Now you can, by forking our repo, making changes, and committing them in your fork!

If you think your changes are amazing and should be included in Google’s Science Journal App, read our contribution guide. But if you want to keep your changes to yourself and your friends, well, that’s cool too! We’d love to see what you’ve built, so you can tweet at us @GScienceJournal, or just use the #myScienceJournal hashtag on Twitter.

By Joshua Liebowitz, iOS Tech Lead

Celebrating the Apache Software Foundation’s 20th anniversary

This week we join free and open source software communities around the world in celebrating the 20th anniversary of the Apache Software Foundation (ASF). It’s a huge milestone, and as we reflect on it we know there’s a lot to be grateful for.

Google makes extensive use of Apache projects, contribute our own, and most of our open source projects are released under an Apache 2 license. Our community of Googlers decided to mark 20 years of The Apache Way by sharing their thoughts about ASF…

… and we can hardly think of a more fitting way than to do that in the style of a mailing list thread:

FWD: [Discuss] 20 years of The Apache Way

---------- Forwarded message ---------
From: Gris Cuevas <[email protected]>
Date: Tue, 26 Mar 2019 at 9:20 a.m.
Subject: Fwd: [DISCUSS] 20 years of The Apache Way
To: The World <[email protected]>

When we think about the early days of the Internet one of the first names that comes to mind is the Apache Software Foundation (ASF) and its contributions to Open Source! In fact, as I was recently told by a friend in the community, whenever she hears “Apache”, in a technology context, she automatically thinks about the Internet. I was in awe of her testament!

Here are the things I’d love to raise my glass to:

The Apache Way, for Being an Impressive Model for Collaborative Development
Technology as we know it wouldn’t be possible without the outstanding contributions of volunteers from all over the world, who under the umbrella of “The Apache Way,” have developed and maintained some of the most sophisticated software over the years.

When I joined Apache Beam, just a few months after its graduation as a top-level project, I realized how much work could be accomplished by the collaborative culture and the consensus driven decision making fostered by the ASF. Sure, sometimes things might drag a little behind the release schedule. But looking at the big picture, the developments that occurred in the last 20 years have significantly changed and enhanced our lives as they became the backbone and remain at the forefront of technology innovation.

The Community > Code
The Apache model recognizes contributors that help a project thrive, not only with code but also with contributions in project advocacy, documentation and community management. When I became the second non-code committer to Apache Beam, I realized how lucky I was to be part of a project that recognizes contributions of all type. I felt empowered and even more committed to the project. I’m passionate about building communities in open source, which aim to better the world, and I am committed to fostering a positive, diverse culture in which all ideas and perspectives are welcome and all members of  the community have an equal opportunity to influence the technology.

The Apache Way model positions the community at the center of a project, caring for the individuals, their rights and responsibilities. People participate based on their merit and not based on any external affiliation, title, or education.

Ever since, my mission has been to act as an ambassador for Apache projects at Google and to increase our contributions to Apache projects.

I hope you all join us, sharing stories and taking a moment to be grateful for what 20 years of strong open source practices have brought to the world.

Gris Cuevas
Google Cloud - Open Source Strategist


---------- Forwarded message ---------
From: Aizhamal Nurmamat kyzy <[email protected]>
Date: Tue, 26 Mar 2019 at 8:26 a.m.
Subject: Fwd: [DISCUSS] 20 years of The Apache Way
To: The World <[email protected]>

What a great occasion to celebrate! 20 years is no easy feat, and as the Apache Way has taught us, something like this can only be accomplished through enabling communities to grow healthily.

I want to raise my glass to the many ways in which the Apache Way has been implemented across all of the Apache projects. As I’ve been becoming familiar with different communities, I’ve observed how each one is different. Some of them are young and full of energy. Others are older and wiser. They have all adopted the Apache Way, and implemented it in ways that suit them. This has let them build vibrant and diverse communities, attract new users and contributors, and help them mature into full citizens of their projects.

As a new contributor, seeing these different communities thrive fills me with hope that 20 years is just the beginning, and we will see many more years of exciting projects and communities coming from the ASF.

So, cheers to 20 years of great communities! And here’s to 20 more!

Aizhamal Nurmamat kyzy
Google Cloud - Open Source Program Manager


---------- Forwarded message ---------
From: Joana Carrasqueira <[email protected]>
Date: Tue, 26 Mar 2019 at 8:20 a.m.
Subject: [DISCUSS] 20 years of The Apache Way
To: The World <[email protected]>

Hello community,

I would like to invite you all to celebrate the 20th Anniversary of the Apache Software Foundation on March 26th!

To acknowledge this historic moment, I would like to start a [Discuss] thread so everyone can share Apache related milestones and memories they would like to celebrate with our vibrant community!

Apache Software is so ubiquitous that I believe it is safe to say that the ASF can be hailed as one of the most successful influencers in Open Source and I feel very grateful for being part of this vibrant community.

I would like to start by raising my glass to the organization of the Beam Summits 2019! It is an absolute pleasure being part of the team that is behind the scenes, pulling these events together to ensure we provide new and advanced contributors with the best tools and resources to continuously support the Apache Beam Project. In addition, I am very grateful for supporting the development of a diverse community, creating the mechanisms by which everybody can share knowledge and expertise.

Please join me in celebrating the 20th Anniversary of the Apache Software Foundation and the contributions of thousands of contributors, who work every day to make the Apache community a success!

Joana Carrasqueira
Google Cloud - Open Source Events Manager