Pattern idea: Service Level Agreement (SLA)

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

未指定文件、测试或入口点；请先查看 issue 231、相关模式以及链接的 InnerSource 参考资料。完成的标准是记录一个涵盖贡献审查、合并或拒绝、错误报告、功能请求以及任何无保证条款的 Service Level Agreement 模式。