Pattern idea: Service Level Agreement (SLA)

Open

#231 opened on Oct 23, 2020 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty: 5/5
Estimated time: Over a week
Newbie friendliness: 25/100

Issue type: Documentation
Clarity: Mostly clear
Activity status: Stale
Domain: content, documentation

Research direction

No file, test, or entry point is named; start by reviewing issue 231, the related patterns, and the linked InnerSource reference. Done means documenting a Service Level Agreement pattern covering contribution review, merge or rejection, bug reports, feature requests, and any no-warranty clauses.

Written by the indexing model from the issue text.

Description

:book: Type - Content Work

Problem

Teams with resource constraints may be reluctant to adopt InnerSource (accept contributions), due to fear of missing resources to review and integrate them in reasonable time
Contributors get frustrated to to lack of response or excessive delay on review and merge of contributions

Solution

The maintainers of the receiving component will document their Service Level Agreement (SLA) with respect to reviewing and merging / rejecting contributions and answering to bug reports, feature requests.

The SLA may also state no-warranty clauses (i.e. projects maintained in spare time).

Contributors will know up front what to expect before contributing, and can better decided whether to invest their time contributing, avoiding waste of resources and frustration.

Related patterns

30 day warranty
Start as an experiment

References

Martin Woodward (GitHub) at ISC.S11 - The 5 Myths of InnerSource - 8:48 - the slide states SLA for PR and issue triage

Dominant language: HTML
Stars: 853
Forks: 206
Avg merge: 1d 23h
Merged PRs (30d): 2

Contributor guide

Open the contributing guide

First steps

Read the whole issue, then the project's contributing guide.
Comment on the issue to say you are picking it up — it saves two people doing the same work.
Fork the repository and make your change on a branch.
Open a pull request that references the issue number.

Similar issues

Add: Sport 1 (Israel) SD Open

check:passed streams:add

Difficulty 1/5 Under an hour Newbie friendliness 95/100

iptv-org/iptv#52697 · 1 comment · Opened Sep 24, 2026
performance guide: ToC anchor links not working Open

bug

Difficulty 1/5 Under an hour Newbie friendliness 90/100

strawberry-graphql/strawberry.rocks#530 · Opened Sep 24, 2026
Duplicate wp-image class when source and destination attachment IDs match Open

Bug

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

Automattic/safe-publish#593 · Opened Sep 24, 2026
Add: Arena Sport Premium M2 Open

channels:add check:passed

Difficulty 1/5 Under an hour Newbie friendliness 95/100

iptv-org/database#36063 · Opened Sep 24, 2026
[workshop-sim] Improve: Add active-recall check for the two-file structure concept in Step 5 Open

feedback simulation workshop

Difficulty 2/5 1-3 hours Newbie friendliness 75/100

githubnext/gh-aw-workshop#3774 · Opened Sep 24, 2026