InnerSource: First Contribution Explored

[michael_basil]

In the evolving landscape of software development at SAP, the adoption of InnerSource principles has unfolded as a journey of collaboration, learning, and community building. A pivotal moment in this journey, often overlooked yet critically important, is the "First Contribution." This initial step into InnerSource can feel akin to an awkward first dance—where it appears the collaboration might end once a contribution is merged. However, this is merely the beginning of a deeper and more meaningful engagement.

The Awakening After the First Contribution

In a recent project, as we navigated the path towards embracing InnerSource, we encountered what I like to refer to as points of inflection—moments that define the direction of our collaborative efforts. One such moment is the First Contribution. It’s a critical juncture that, while seemingly conclusive, actually marks the start of true collaboration.

During the introduction of a new component, it became evident that practical knowledge transfer had been inadvertently overlooked. As challenges emerged—akin to canaries in a coalmine signaling danger—we rallied together, smoothing out the rough edges through a collective effort. It was during this resolution phase that the relevance of InnerSource patterns, particularly the "30-Day Warranty," became abundantly clear.

The 30-Day Warranty: A Foundation for Collaboration

The "30-Day Warranty" [1] pattern emphasizes the principle that the journey of collaboration is just beginning with the acceptance of a contribution. It underscores the necessity for the contributing team to provide support for a specified period post-integration, ensuring a smooth transition and fostering a sense of shared responsibility. This pattern played a pivotal role recently in one of our projects, not only during the resolution of initial challenges but also as a key topic of discussion in our release retrospective.

Everest Project's Recent First Contribution

In the Everest project, which is transforming traditional click-ops engineers into Kubernauts through GitOps—a pivotal step in our operational transformation, we recently leveraged the "30-Day Warranty" principle to nurture a conducive environment for the receiving team to accept contributions confidently. This approach increased transparency and fairness, mitigating potential escalations that could become cumbersome. By focusing on the spirit of collaboration, rather than the specific timeframe, we fostered a culture where teams felt supported in adapting and enhancing initial contributions. This flexibility ensured that the essence of collaboration was prioritized, embodying the true spirit of the "30-Day Warranty."

Learning and Growing with the Dojo Community

The Dojo [5] community maintainers are becoming more aware of the importance of the "30-Day Warranty" pattern, especially in the context of sustaining future contributions. We learned that post-merge support is essential, as the absence of necessary expertise to maintain and iterate on contributions could lead to challenges. This awareness has become a cornerstone in preparing for and supporting future contributions, ensuring the continuous feed and care of projects.

Cultivating Collaboration with Praise Participants

Parallel to addressing technical and process-related challenges, recognizing and appreciating the efforts of all participants is crucial. The "Praise Participants" [2] pattern, infused with SAP's Appreciate program, has been instrumental in nurturing a culture of acknowledgment and appreciation.

SAP Appreciate Program and How We Run Values

The SAP Appreciate [3] program is at the heart of our efforts to cultivate a culture of appreciation aligned with our How We Run [4] values. We utilize platforms like Teams and Slack, in conjunction with the Appreciate program, to send personalized thank-you notes that may include the recipient's manager. This multi-faceted approach ensures that appreciation is both seen and felt across levels, reinforcing the value of every contribution.

Enriching the Dojo Community Experience

Within the SAP community, multiple Dojos (such as InnerSource, Agile, and Mindset) exemplify the "Praise Participants" pattern through their activities. Notably, the Mindset Dojo [6] incorporates an exercise that encourages participants to send appreciation notes to peers who have supported their learning journey. For many, this exercise is a first exposure to expressing gratitude in a structured manner, reinforcing the principles of mutual respect and recognition. 

The Dojo from SAP [5] communities also send notes of appreciation and congratulations as members reach new belt levels.  This is done via Teams and or Slack depending on which community-specific channels the broadest audiences tend to communicate.

Everest Appreciation

The Everest project also leverages sending notes of congratulations and appreciation via Slack and Teams.  It is inherent in the culture itself.  We also see SAP Appreciate leveraged throughout the culture.  In many of the groups I/we intersect with the same behavior is readily apparent.  This really makes it encouraging for the next collaboration opportunity!

Looking Ahead: The Next First Contribution Opportunities

The journey of integrating InnerSource at SAP, highlighted by the pivotal "First Contribution," has revealed the transformative potential of embracing each initial contribution with a mindset geared towards collaboration and recognition. Through the experiences of the Everest and Dojo projects, the importance of the "30-Day Warranty" and "Praise Participants" patterns emerges, emphasizing that the journey of collaboration begins, not ends, with the First Contribution. This moment is not just a procedural step but a gateway to fostering a culture of support, appreciation, and community.

Acknowledging and supporting the First Contribution sets a foundation for a collaborative environment where every participant feels valued and inspired. It's a call to action for us to cultivate a workspace where these initial contributions are recognized as opportunities for growth and engagement. As we move forward, let us be mindful of the profound impact these beginnings have on our collective journey in InnerSource, encouraging a culture where every First Contribution is seen as a stepping stone to innovation, collaboration, and community building.

Shout Outs

Special thanks to Michael Picht and Guilherme Dellagustin from the Open Source (InnerSource) Program Office at SAP for providing centering guidance along the way.

Further Exploration

1. InnerSource Pattern - 30 Day Warranty 
2. InnerSource Pattern - Praise Participants 
3. SAP Appreciate Program 
4. How We Run - SAP Operating Behaviors
5. How to manage DevOps culture? From traditional IT practices, to DevOps and beyond (Sumo Logic Illuminate, October 2022)
6. From Challenges to Transformation: The Data Services Organization Dojo Tale 
7. Cultivating InnerSource at SAP