dido:public:ra:xapend:xapend.b_stds:defact:todo:shutdown
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:shutdown [2019/05/24 19:56] nick |
dido:public:ra:xapend:xapend.b_stds:defact:todo:shutdown [2021/11/09 15:40] (current) char ↷ Links adapted because of a move operation |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ======= Shutting down an open source project ======= | + | ===== TODO: Shutting down an open source project ===== |
| - | [[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/shutting-down/ | The following is from TODO on "Shutting down an open source project" ]]** | + | **Source:** [[https://todogroup.org/guides/shutting-down/ | The following is from TODO on "Shutting down an open source project" ]] |
| + | //This Open Source Guide is designed to offer advice about how your enterprise and your development team can plan for the day when you are ready to end or move away from an unneeded open source project. By shutting down the project gracefully or by transitioning it to others who can continue the work, your enterprise can responsibly oversee the life cycle of the effort. In this way, you can also set proper expectations for users, ensure that long-term project code dependencies are supported, and preserve your company’s reputation within the open source community as a responsible participant.// | ||
| - | : //This Open Source Guide is designed to offer advice about how your enterprise and your development team can plan for the day when you are ready to end or move away from an unneeded open source project. By shutting down the project gracefully or by transitioning it to others who can continue the work, your enterprise can responsibly oversee the life cycle of the effort. In this way, you can also set proper expectations for users, ensure that long-term project code dependencies are supported, and preserve your company’s reputation within the open source community as a responsible participant.// | + | //This guide will help you decide when a project is no longer useful, understand how to disengage from a project, and determine what to do about its code, repositories, websites, wikis, and other project assets as you head in a new direction.// |
| - | : //This guide will help you decide when a project is no longer useful, understand how to disengage from a project, and determine what to do about its code, repositories, websites, wikis, and other project assets as you head in a new direction.// | + | ==== Contents ==== |
| - | + | * //Lifecycle planning for your open source project// \\ | |
| - | ===== Contents ===== | + | //1. Why life cycle planning is important// \\ |
| - | + | //2. What does a dead open source project look like?// | |
| - | * Lifecycle planning for your open source project | + | * //Why plan for the end of a project before you even launch it?// |
| - | * Why life cycle planning is important | + | * //Deciding when to end, transfer or pull out of a project// |
| - | * What does a dead open source project look like? | + | * //How to end an open source project// |
| - | * Why plan for the end of a project before you even launch it? | + | |
| - | * Deciding when to end, transfer or pull out of a project | + | |
| - | * How to end an open source project | + | |
dido/public/ra/xapend/xapend.b_stds/defact/todo/shutdown.1558742211.txt.gz · Last modified: 2019/05/24 19:56 by nick
