dido:public:ra:xapend:xapend.b_stds:defact:todo:create
Differences
This shows you the differences between two versions of the page.
| Next revision | Previous revision | ||
|
dido:public:ra:xapend:xapend.b_stds:defact:todo:create [2019/05/24 19:05] nick created |
dido:public:ra:xapend:xapend.b_stds:defact:todo:create [2021/11/09 15:42] (current) char ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======= How to create an open source program ======= | + | ===== TODO: How to create an open source program ===== |
| - | [[dido:public: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/create-program/ | The following is from TODO on "How to create an open source program" ]]** | + | **Source:** [[https://todogroup.org/guides/create-program/ |The following is from TODO on "How to create an open source program" ]] |
| + | //A central open source program office is a designated place where open source is supported, nurtured, shared, explained, and grown inside a company. With such an office in place, businesses can establish and execute on their open source strategies in clear terms, giving their leaders, developers, marketers, and other staff the tools they need to make open source a success within their operations.// | ||
| - | : //A central open source program office is a designated place where open source is supported, nurtured, shared, explained, and grown inside a company. With such an office in place, businesses can establish and execute on their open source strategies in clear terms, giving their leaders, developers, marketers, and other staff the tools they need to make open source a success within their operations.// | + | //This guide aims to help you figure out why and how to establish a program to manage the open source use and creation inside your company, as well as to show how your developers can make their own contributions to open source projects outside your operations. It will cover topics for open source offices including: roles and responsibilities, corporate structures, elements of an open source management program, how to choose and hire an open source program manager, and more.// |
| - | + | ||
| - | : //This guide aims to help you figure out why and how to establish a program to manage the open source use and creation inside your company, as well as to show how your developers can make their own contributions to open source projects outside your operations. It will cover topics for open source offices including: roles and responsibilities, corporate structures, elements of an open source management program, how to choose and hire an open source program manager, and more.// | + | |
| - | + | ||
| - | ://Contents// | + | |
| + | //Contents// | ||
| * //Why create an open source program office// | * //Why create an open source program office// | ||
| * //The role of the open source program office// | * //The role of the open source program office// | ||
dido/public/ra/xapend/xapend.b_stds/defact/todo/create.1558739102.txt.gz · Last modified: 2019/05/24 19:05 by nick
