14 APR 2021 - InnerSource SIG Meeting Minutes

[claredillon]

Date

Wednesday, 14 April 2021 - 10am EST / 3pm UK

Untracked attendees

• All attendees commented on issue below.

Meeting notices

• FINOS SIG Leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

• All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

• FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact legal@finos.org with any questions.

• FINOS SIG meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

• Convene & roll call (5mins)
• Display FINOS Antitrust Policy summary slide
• Review Meeting Notices (see above)
• Approve past meeting minutes
• Agenda items TBD based on votes to this comment,
• AOB, Q&A & Adjourn (5mins)

Options for the Agenda Topics

Please put comment on this issue with your favourite topic among those below, and we will use that as a guide for the agenda on the day.

• Common policies / guidelines / principles around InnerSource
  • How to measure InnerSource success and value?
    • Metrics
    • Value propositions
  • Identify patterns
    • Cultural / behavioural patterns
    • Project patterns
    • Operational / organisational patterns
• Getting started - best projects
• Specific tips/guidelines e.g. how when is a PR too big?
• How can we best advocate for InnerSource?
• Tooling
  • What tools and settings are commonly used?
  • What supporting code/tools do we have that could be open sourced?
  • Feedback for tools vendors

Noting that the agenda focus on the day was decided to be around the topic of maturity matrix.

Notes from Meeting

Purpose of this work:

• Working together to compare existing Maturity and Capability Models to come up with a canonical set we’d like to endorse for InnerSource SIG at FINOS and at InnerSourceCommons.org
• This should allow people to:
  • Self-assess readiness
  • Build development plans / goals

Extant list of existing Maturity Models for InnerSource

https://github.com/InnerSourceCommons/InnerSourcePatterns/blob/a9e136eb57fd927c12ee27827e35cd7215226e53/patterns/2-structured/maturity-model.md

Understanding the Open Source Checklist : https://innersourcecommons.org/learn/books/understanding-the-innersource-checklist/#:~:text=Do%20you%20want%20your%20day,allow%20more%20collaboration%20and%20reuse%3F

Some orgs also have multiple models in use internally - and we may get learnings from them.

Other Resources that might be useful

Rob referencing open source program health check from FINOS - the dimensions can be helpful to consider. https://finosfoundation.atlassian.net/wiki/spaces/FINOS/pages/93225748/Board+Reporting+and+Program+Health+Checks

InnerSource Commons Learning Path - Introduction (with Benefits of InnerSource): https://innersourcecommons.org/learn/learning-path/introduction/

InnerSource Commons Community Call on Metrics, Value and ROI: https://www.youtube.com/watch?v=VvP4Ubet7qM

Summary of suggestions for consideration in this work

• Make need different areas to consider
  • e.g. org and project maturity may be different
  • We may want to consider other contexts e.g. technology and culture E.g. mainframe code - code owners don’t have SMEs who understand the complexity of changing API or % of legacy code and % orphan code.
  • Tools and enablers in place may be useful to include.
  • We may also need to consider context for the implementation e.g. opportunity provided by central CI/CD implementation or code review?
• Think of levels as stop, start, performing?
• Don’t put the starting requirements too high, recognise people may already be showing good behaviour.
• Checklists are handy

Signals of maturity

• Org Level
  • Code open by default?
  • Are there projects upon which you collaborate across discreet teams?
  • Where is the code stored?
  • Where is the documentation?
  • Can outside [of the team/business unit] contributors raise a PR and get it to Production without prior discussion? I.e., are the rules of the road clearly documented?
  • Is testing framework available for local testing?
  • Capacity planning to allow InnerSource activities (both contributing and maintaining, but also refactoring/modernization of the legacy codebases)
  • Dedicated staff to enable/accelerate InnerSource adoption?
• Project level
  • Are basic documents in place per codebase?
  • Do they have strong READMEs?
  • Do they accept contributions?
  • Published roadmap?
  • Nightly builds?
  • SLAs for code reviews
  • Do you have multiple people contributing and using the like-minded projects ?
• Tools and Enablers:
  • Search/discovery of the code, APIs, shared libraries
  • Automated linting, tests of all levels
  • Automated CI/CD pipeline, including deployment gates, to provide additional quality assurance
• Culture:
  • Self-driven by individual enthusiasts
  • Included in your annual goals
  • Projects proceeding into InnerSource without push from leadership
  • Do you trust your employees, is that evident?

Discussion about how metrics

• How can metrics be used to incentivise InnerSource, as relates to maturity matrix?
• Can incentivise behaviours with metrics - but may need to evolve those measures over time.
• How to encourage good owners?
  • E.g. private repos to opening repos to documentation.
  • Project can be deployed right away based on README
  • PIpeline / testing already there.
• Publishing roadmaps? Current pushback against that.
  • One option is to publish event horizon (to stop others spinning up separate efforts).

Decisions Made

• ...

Action Items

• SIG to arrange next meeting as working meeting to flesh out maturity matrix
• Danese Cooper volunteered to create a starting document by synthesizing the existing maturity matrices.

WebEx info

• Meeting link: https://finos.webex.com/finos/j.php?MTID=m9c14803fc76a2fa53fa745393c231f18
• Meeting number: 127 703 9041
• Join by phone
  • +1-415-655-0003 US Toll
  • +44-20319-88141 UK Toll
  • Access code: 127 703 9041

Mailing List

Email innersource+subscribe@finos.org to subscribe to the InnerSource SIG mailing list.

[claredillon]

I feel there was a lot of energy around the idea of sharing guidelines and policies in use in organizations already practicing InnerSource. Propose we share examples in the next SIG meeting.

[daniela-g-zheleva-db]

I feel there was a lot of energy around the idea of sharing guidelines and policies in use in organizations already practicing InnerSource. Propose we share examples in the next SIG meeting.

I think that's a great topic to start with Clare! It would be awesome if we could come up with a list of policies/guidelines that are generally applicable and useful to any regulated company looking to get involved with inner source.

[mcleo-d]

@daniela-g-zheleva-db and @claredillon - I have added the Webex and call details to the event above.

[mcleo-d]

Hi SIG Leads,

Whilst scheduling the InnerSource SIG meeting, I noticed 7th April clashes with Open Source Readiness, which includes people who might want to join the InnerSource SIG call. It's best to avoid this type of scenario.

https://www.finos.org/hosted-events/2021-04-07-open-source-readiness-panel-discussion-running-an-open-source-project-from-inside-a-bank

Can we move the SIG meeting to Wednesday 14th April, when OSR isn't running and there aren't other FINOS meeting clashes?

Kind regards,

James. 

[mcleo-d]

Hi @claredillon - I have rescheduled the InnerSource SIG meeting for 14th April at 10am ET / 3pm UK. Details have been added to the meeting agenda.

[mcleo-d]

Hi @finos/innersource-maintainers

I'd like to tip my 🎩 to issue Inner Source Maturity Model? #11 that was raised by @brooklynrob as the SIG prepares itself for the next meeting.

@Ludmila-N has also added the following comment to the issue, which is awesome 👏 Thank you ! ... #11 (comment)

James 🚀

[claredillon]

Thanks for the flag @mcleo-d - we will add this to the agenda! :)

[mcleo-d]

Hello 👋

[claredillon]

Hello!

[daniela-g-zheleva-db]

Hello 👍

[agitana]

hi

[godds]

Hi

[mcleo-d]

Please say hello in the comments 😄

[eduardosan]

Hello

[alstratigos]

Hello!

[Leguet]

Hello

[melindajoy]

hello

[Ivan-Radovanovic]

Hello there

[Ludmila-N]

ciao

[DanielleAlmeida]

Hello!

[Danese]

Howdy

…

On Wed, Apr 14, 2021 at 9:30 AM Ivan-Radovanovic ***@***.***> wrote: Hello there — You are receiving this because you are subscribed to this thread. Reply to this email directly, view it on GitHub <#10 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AANYPFECJ2VX3VCHHXJSYZLTIWRINANCNFSM4ZYXECVA> .

[Leguet]

Hi,
I will be very interested to exchange on how to measure InnerSource success and value and if possible to have access to illustration of concrete examples.
Have a nice day

[toshaellison]

Hi

[claredillon]

Hi,
I will be very interested to exchange on how to measure InnerSource success and value and if possible to have access to illustration of concrete examples.
Have a nice day

You may be interested in the output from the last InnerSource Commons Community Call, which was on the topic of Metrics, Value and ROI. The recording has just gone live here: https://youtu.be/VvP4Ubet7qM

[Leguet]

Hi Clare,
Thank you. I will look at it.

[chamindra]

Hello! 👋 Could not join the SIG meeting due my schedule. Will look forward to the next meet. I am particularly interested in how we better integrate source work with open source contribution particulaly when using open source componets in inner source projects.

[github-actions]

Couldn't find the following GitHub usernames on file: @chamindra, @Ivan-Radovanovic, @melindajoy, @DanielleAlmeida, @Ludmila-N, @Leguet . /CC @aitana16 @maoo @mcleo-d