dido:public:ra:xapend:xapend.b_stds:defact:todo:buildleadership
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:defact:todo:buildleadership [2020/05/22 17:48] char |
dido:public:ra:xapend:xapend.b_stds:defact:todo:buildleadership [2021/11/09 15:42] (current) char ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| ===== TODO: Building leadership in an open source community ===== | ===== TODO: Building leadership in an open source community ===== | ||
| - | [[dido:public:ra:xapend.stds:defact:todo| return to the TODO defacto Standards ]] | + | [[dido:public:ra:xapend:xapend.b_stds:defact:todo:start| return to the TODO defacto Standards ]] |
| - | ==== Overview ==== | + | ==== Overview ==== |
| There are no formal standards on Open Source projects. There are only guides. | There are no formal standards on Open Source projects. There are only guides. | ||
| - | **Source: [[https://todogroup.org/guides/building-leadership/ | The following is from TODO on "Building leadership in an open source community" ]]** | + | **Source:** [[https://todogroup.org/guides/building-leadership/ | The following is from TODO on "Building leadership in an open source community" ]] |
| //Integrating into open source communities takes time and effort and requires a new approach to product development. Where traditional, proprietary development requires secrecy and a management hierarchy, open source development requires openness and values consensus. Code contributions, not title or position, are what determine influence and technical direction in an open source project.// | //Integrating into open source communities takes time and effort and requires a new approach to product development. Where traditional, proprietary development requires secrecy and a management hierarchy, open source development requires openness and values consensus. Code contributions, not title or position, are what determine influence and technical direction in an open source project.// | ||
| Line 13: | Line 13: | ||
| //This guide explains how organizations can build leadership and influence within the open source projects they’re involved in and on which they are commercially dependent. Learn about leadership culture and roles within a project, how decisions are made, how an organization can build leadership, and tips for being a good leader in open source communities.// | //This guide explains how organizations can build leadership and influence within the open source projects they’re involved in and on which they are commercially dependent. Learn about leadership culture and roles within a project, how decisions are made, how an organization can build leadership, and tips for being a good leader in open source communities.// | ||
| - | ===== Contents ===== | + | ==== Contents ===== |
| - | 1. //Why build leadership in an open source project// | + | //1. Why build leadership in an open source project// |
| * //Leadership culture in open source// | * //Leadership culture in open source// | ||
| * //Corporate vs open source leadership// | * //Corporate vs open source leadership// | ||
| * //Governance overview// | * //Governance overview// | ||
| * //Culture overview// | * //Culture overview// | ||
| - | 2. //Leadership roles in a collaborative project// | + | //2. Leadership roles in a collaborative project// |
| * //Leadership roles matrix// | * //Leadership roles matrix// | ||
| * //How to become a leader// | * //How to become a leader// | ||
dido/public/ra/xapend/xapend.b_stds/defact/todo/buildleadership.1590184126.txt.gz · Last modified: 2020/05/22 17:48 by char
