InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns

Help pattern authors with Context + Forces

未關閉
#419 5 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

還沒有人認領這個 Issue。

:gear: Type - Meta
主要語言
HTML
星號
853
分支
206
平均合併
1 天 23 小時
30 天內合併 PR
2

描述

Pattern authors often struggle with filling in the Context + Forces sections of our pattern template.

Could we give them more guidance on how to fill in Context + Forces?

@NewMexicoKid you are dropping nuggets of wisdom about these sections in your reviews sometimes (as in the example below). Could you help us extend the pattern template with further instructions, especially around these two sections?

Example of "nuggets of wisdom"

Whenever possible, forces should be stated in a way that indicates the trade-offs (which can hint at the levers by which one can react to a given force).

So if Product Owners are reluctant to be more collaborative and transparent, what is motivating them to do so? (Is it a cultural tendency to secrecy to protect proprietary information to gain a strategic advantage? If so, then is it a matter of noting which information needs to be protected vs. which info, when shared, can result in compensating advantages?)

Originally posted by @NewMexicoKid in https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/417#discussion_r878929031

貢獻指南

開啟貢獻指南

從這裡開始

  1. 先讀完整個 Issue,再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫,在一個分支上完成修改。
  4. 送出 Pull Request,並在描述裡引用這個 Issue 編號。

研究方向

找到 issue 引用的模式範本,並檢視其中現有的 Context 和 Forces 指引。將範本與引用的審查建議進行比較,然後以更清楚的說明更新這些區段;當模式作者能在範本中取得可執行的指引時,即表示完成。

由索引模型根據 Issue 內容生成。

評估

領域
content, documentation
Issue 類型
文件
難度
2/5
預估耗時
1-3 小時
活躍度
停滯
描述清晰度
基本清楚
新手友好度
35/100

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。