InnerSourceCommons / InnerSourceCommons/InnerSourcePatterns
Ports nuggets of wisdom into existing patterns
Ninguém assumiu esta issue ainda.
- Linguagem predominante
- HTML
- Estrelas
- 853
- Forks
- 206
- Merge médio
- 1d 23h
- PRs com merge (30d)
- 2
Descrição
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
Guia de contribuição
Primeiros passos
- Leia a issue inteira e depois o guia de contribuição do projeto.
- Comente na issue dizendo que vai assumir — evita que duas pessoas façam o mesmo trabalho.
- Faça um fork do repositório e trabalhe em uma branch.
- Abra um pull request que referencie o número da issue.
Direção de pesquisa
Comece revisando a discussão encerrada de #501 e os comentários citados; em seguida, inspecione os padrões existentes no repositório para determinar onde a orientação deve ficar. A tarefa estará concluída quando as ideias relevantes sobre métricas, incentivos e consequências não intencionais forem incorporadas aos padrões existentes sem criar um novo.
Escrita pelo modelo de indexação a partir do texto da issue.
Avaliação
- Domínio
- documentation
- Tipo de issue
- Documentação
- Dificuldade
- 4/5
- Tempo estimado
- 3-5 dias
- Status de atividade
- Estagnada
- Clareza
- Precisa de esclarecimento
- Facilidade para iniciantes
- 20/100