dido:public:ra:xapend:xapend.b_stds:defact:todo:improve
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:improve [2019/06/07 14:33] nick |
dido:public:ra:xapend:xapend.b_stds:defact:todo:improve [2021/11/09 15:40] (current) char ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======= TODO: Improve your open source development impact ======= | + | ===== TODO: Improve your open source development impact ===== |
| - | [[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/impact/| The following is from TODO on "Improve your open source development impact" ]]** | + | **Source:** [[https://todogroup.org/guides/impact/| The following is from TODO on "Improve your open source development impact" ]] |
| + | //Open source development requires a different approach to software engineering than many organizations are accustomed to. It becomes easier if you have a clear plan to follow. Fortunately, many companies and individuals have already forged a path to success by contributing to significant open source projects in strategic ways. This practical guide will help you and your company improve your internal development process and prepare you to contribute to the open source projects that matter most to your company. Contributing to the Linux kernel is one of the hardest challenges for open source developers. So we’ll use this case as an example for this guide. Fortunately, the guidance will apply to nearly any open source project you’ll face.// | ||
| - | : //Open source development requires a different approach to software engineering than many organizations are accustomed to. It becomes easier if you have a clear plan to follow. Fortunately, many companies and individuals have already forged a path to success by contributing to significant open source projects in strategic ways. This practical guide will help you and your company improve your internal development process and prepare you to contribute to the open source projects that matter most to your company. Contributing to the Linux kernel is one of the hardest challenges for open source developers. So we’ll use this case as an example for this guide. Fortunately, the guidance will apply to nearly any open source project you’ll face.// | + | ==== Contents ==== |
| - | + | * //What is impactful open source development?// | |
| - | ===== Contents ===== | + | * //The role of an open source program in improving development: // \\ |
| - | + | //1. Direct enablement// \\ | |
| - | * What is impactful open source development? | + | //2. Indirect Enablement// |
| - | * The role of an open source program in improving development | + | * //Common areas for improvement// |
| - | * Direct enablement | + | * //Top Recommended Practices// |
| - | * Indirect Enablement | + | * //Metrics for tracking progress// |
| - | * Common areas for improvement | + | |
| - | * Top Recommended Practices | + | |
| - | * Metrics for tracking progress | + | |
dido/public/ra/xapend/xapend.b_stds/defact/todo/improve.1559932424.txt.gz · Last modified: 2019/06/07 14:33 by nick
