InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns

Ports nuggets of wisdom into existing patterns

オープン
#531 コメント 3 件 リアクション 0 件 担当者 0 名 GitHub で見る

まだ誰も着手していません。

:book: Type - Content Work
主要言語
HTML
スター
853
フォーク
206
平均マージ
1日 23時間
マージ済み PR(30日)
2

説明

We opted against creating a new pattern for this topic, and hence closed #501 without merging it.
However the PR contain some nuggets of wisdom like the one below that we should port into other already existing patterns.

Negative consequences of metrics is a great thing to tackle. Thanks for writing this up. Gamification of metrics definitely leads to some strange (and sometimes unwanted) behaviors in organizations sometimes, i.e. "promotion driven development" as described in https://twitter.com/gergelyorosz/status/1442162670753431559?lang=en

Another lens to view this through, is that incentives, intentional or otherwise, almost always have second order effects that may be desirable or undesirable besides the intended consequences. I think Kent Beck's blog has some good writing about this, but I can't find a good reference online to share other than https://geekincentives.substack.com/p/the-geek-incentives-manifesto which is very brief.

I think it's important to note is that these unintended consequences can lead to negative outcomes in an organization even when the incentives had good intentions and the ones affected by them did as well.

Using the "weapon" phrasing may imply that bad outcomes are intended by bad actors, whereas I think in reality, bad actions are often the unintended consequences of well meaning people, or at least people with an average amount of healthy-self interest in advancing their career or project, but in an organization there are always competing projects and other peers seeking similar outcomes that need the same resources (money, time, attention, budget, etc.)

That's not to say that there are never bad actors, just that things actually can go wrong without requiring it as a precondition.

Originally posted by @ranton256 in https://github.com/InnerSourceCommons/InnerSourcePatterns/pull/501#discussion_r1049990252

コントリビューションガイド

コントリビューションガイドを開く

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

調査の方向性

まずクローズされた #501 の議論と引用されたコメントを確認し、次にリポジトリに既に存在するパターンを調べて、そのガイダンスをどこに置くべきかを判断します。メトリクス、インセンティブ、意図しない結果に関する関連する考えが新しいパターンを作成せずに既存のパターンへ組み込まれた状態を完了とします。

索引モデルが issue の本文から書いたものです。

評価

領域
documentation
issue の種類
ドキュメント
難易度
4/5
見積もり時間
3〜5日
活発さ
停滞
明瞭さ
説明が足りない
初心者へのやさしさ
20/100

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。