Open Source Summit Latin America 2022

We love the listen about epic tails and hero's journeys, but this is not one of those stories. This is a story of how an average developer interacted and was aided by open source throughout his life. How small interactions, small changes, and small movements add up and contribute to getting you somewhere. I'll share what I've experienced firsthand as a software developer for the past 20 years, working in both small startups and huge corporations, as well as the conversations and observations from other people that share this profession with me. I'll tell you not only the stories, but also how the tools and community helped shape the professional that I am and how I retributed back to this vast movement.

Open source communities are people. Participants, contributors, and users are some of the roles that we already know and we have acknowledged some of them in the existing CHAOSS [Community Health Analytics for Open Source Software] work. CHAOSS is the leading OSS community with the mission of learning and sharing insights about OSS health. The very existence of public profiles developing software with whom you can interact, make decisions together, and discuss next steps is important up to the point that the alternative is to have close governance communities with low interaction and lack of initiative. Some OSS foundations and OSS projects are indeed stating the importance of these other artifacts as key to a good open governance policy (as for instance the Four Opens by the Open Infra Foundation) and having those discussions in a transparent, public, and open way is part of their culture. How can this be translated into action? Collaboration. And how can we measure collaboration? This talk aims at providing an initial set of existing use cases where collaboration is used as a healthy community metric, an initial list of them related to the collaboration concept, and some existing software you can use to visualize them.

In this presentation, Beatriz Oliveira and Elizabeth Souza will explain what technology communities are, and their impacts on our day-to-day lives as IT professionals. In addition to this, they will also talk about the SysAdminas Community, which is an inclusive and non-profit group that provides a support network for women who want to learn IT Infrastructure related content in a safe and welcoming environment in Brazil. Learn more about the SysAdminas Community on the initiative's official website and blog. Website: https://sysadminas.com.br/ Blog: https://medium.com/sysadminas

In today's job market, especially in software engineering, things have become more fluid than ever. Professionals switch from one company to the next chasing the bigger paycheck or looking for something that is missing. I have been through that path, and my journey led me to discover that having a job with a sense of purpose, community and mutual understanding has been key to a more fullfiled, balanced and happy life. In my talk, I would like to give insights on how we actively incorporate the open source culture to our business and how we embrace and nurture this spirit at Collabora.

The presentation will look at important topics when it comes to managing remote teams effectively, such as employee engagement, 360 feedback, continuous improvement and support for professional growth to ensure our engineers and both satisfied and challenged with their projects. In my role development of People Lead to Engineering Operations Manager, I will share valuable insights on how we look at sustainable business growth without losing the personal connection to our team.

Mentoring and training new contributors within your open-source organization is a tough job and a shared struggle between maintainers and upcoming contributors. The organizations always find it tough to involve new contributors who can actively contribute to the community and make it widely inclusive and a safe space for everyone to learn and grow. This talk focuses on how you can build the right mentorship opportunities within your open-source organization and tackle some of the toughest challenges around it. The attendees will be taking away the following from the talk: 1. Identifying the pain points in bringing new contributors 2. Finding relevant mentorship opportunities for new contributors 3. Build a mentorship working group within your community 4. Bridging the gap between mentors and new contributors 5. Best practices while organizing mentoring initiatives We will discuss how you can approach various mentoring initiatives, allocate bandwidth and mentors, and even host your own mentorship program! Finally will cover Harsh's experience being an administrator & mentor for various mentorship opportunities and how opportunities can be dynamically shaped to build the right skills & enthusiasm among contributors, while tackling some of the toughest challenges around it.

As the CTO and Co-Founder of an open source SaaS commercial start-up that has received seed funding from some of the world's top VCs, Juan Pan's light speed, and empowering entrepreneurial journey started just half a year ago – when open source enthusiast, Apache member, distributed database developer, and DBA were the hats she was wearing. Having gone from being a woman developer in the open source world to CTO, didn’t simply mean a change in her title. This journey included growing an open source community from just a handful of contributors, to one of the leading communities in China and fastest growing Apache projects in the world. The secret? True openness and inclusiveness, the willingness to both mentor students by collaborating with initiatives such as Google Summer of Code or Anita B. Org’s Grace Hopper Celebration, while fostering a technically sound community whose solution has been adopted by over 170 corporations listed on the stock exchange. In this talk she will share her empowering journey and valuable experience of being the CTO at an open source commercial start-up, how women in tech can take the challenges they face and turn them into opportunities, and best practices for open source project leadership.

What is the most valuable outcome? This is the most important question to answer before starting an engineering metrics program. In this talk I discuss which dev team metrics matter most, the outcome they produce, and pitfalls to avoid when starting a metrics initiative. The truth is, no one really likes being measured, especially devs. But business leaders like looking at numbers, so they grab what’s easily available - # of code changes, agile velocity, individual dev metrics. These types of metrics are unbalanced, exclude context, and hurt engineering culture as a whole. What you measure is what your team will produce. If you start measuring the number of code changes as a key performance metric, you are going to see coding time, PR size, and Cycle Time all increase. Don’t fall into this trap. In this session I discuss which team level metrics are most significant, the outcomes they produce, and strategies that will help you avoid the mistakes I’ve already made.

Each community is different and therefore requires different metrics for data-driven decisions about building and supporting it. The CHAOSS Project was established to help empower open source communities through metrics. We have had many conversations with contributors and realized that everyone pays attention to different aspects of their communities. This talk will share what we have learned in the CHAOSS Project about having metrics for open source communities. Once the right metrics have been decided on, both technical and organizational challenges need to be overcome, which we discuss how to do. Finally, this talk will describe real-world examples of how metrics have been used to help build and support open source communities.

In this talk, Sergio Méndez, professor at USAC University, presents how he continuously updates his course content, to develop his students skills to work into the global tech market in the context of DevOps and cloud native technologies. Also he will present different strategies that he is using to update his content to introduce several CNCF open source projects such as Kubernetes as part of his course content, sharing the challenges of doing these changes. At the middle of the presentation, Sergio will share his experience hosting a Kubernetes Community Days in Guatemala with the participation of his students. Telling the audience in detail, how he organized this event, how he organized his students, speakers, the schedule, etc. At the end, Sergio presents the benefits that his students got when they participated in these events, and how now his students are participating in giving talks on local cloud native communities and events like KubeCon, applying for internships and getting jobs outside Guatemala.

Community. An almost poetic term that evokes openness, unity and, in short, altruism. It has been widely adopted in the technological environment whenever there's a need to give the image of a higher goal that is so significant that you must be part of it. However, in open source software, building healthy communities around a project is often a goal that seems to result more spontaneously and from the goodwill of a few hard-working and selfless contributors than a task that can be intentionally planned. In this session, you'll learn five strategies that have been unsuccessful in building communities across the continent and, surprisingly, are still being used in open source projects. You will leave this session with a clearer idea of common ideas to avoid in order to achieve the goal of a healthy community.

It all started with OpenStack, but it’s a much larger world now. The 4 Opens Methodology guides more open source projects every year. Hundreds, or even thousands, of people coming together from different technical backgrounds, different countries, different companies, different time zones to work on a single project together is an amazing feat packed with challenges. It’s hard to get everyone on a level playing field, but the Four Opens model for collaboration makes this partnership easier: Open Design, Open Community, Open Development, and Open Source. This talk will give the audience and overview of what the 4 Opens look like in practice and how they can make your open source project more successful.

Beyond just "don’t run everything as root" In this talk Chris will trace back the origins of how policies are often incepted, how it can get out of hand, be slow if not impossible to update and measure compliance, and often lead us to question of **is the policy helping or hindering**. From this talk you'll learn how to use a software development pattern and product ways of thinking towards how your organization can manage policy; achieve continual updates to policy allowing the risk mitigations to move as fast as the risk does, not get in the way and be easy to measure compliance.