dido:public:ra:1.4_req:2_nonfunc:28_manageability:08_software
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:1.4_req:2_nonfunc:28_manageability:08_software [2021/08/09 14:50] murphy |
dido:public:ra:1.4_req:2_nonfunc:28_manageability:08_software [2022/08/31 15:38] (current) nick [About] |
||
|---|---|---|---|
| Line 3: | Line 3: | ||
| ===== About ===== | ===== About ===== | ||
| - | Over the last few decades, many advances have been made in terms of [[dido:public:ra:xapend:xapend.a_glossary:o:oss]] which has to change the way software was developed, released and used. During this time period, the traditional [[dido:public:ra:xapend:xapend.a_glossary:w:waterfall]] of System and software development has also been largely supplanted with the [[dido:public:ra:xapend:xapend.a_glossary:a:agile]]. Many of these changes also have to do with the evolution of systems (or projects) from being [[dido:public:ra:xapend:xapend.a_glossary:g:greenfield]] to [[dido:public:ra:xapend:xapend.a_glossary:b:brownfield]] development and from a "build the world" attitude towards "integrate and glue the world" mindset. | + | Over the last few decades, many advances have been made in terms of [[dido:public:ra:xapend:xapend.a_glossary:o:oss]] which has to change the way software was developed, released and used. During the [[dido:public:ra:xapend:xapend.a_glossary:s:software_development_model | Software Development Process]] (i.e., the traditional [[dido:public:ra:xapend:xapend.a_glossary:w:waterfall]], [[dido:public:ra:xapend:xapend.a_glossary:a:agile]], etc.), many of these changes also have to do with the evolution of systems (or projects) from being [[dido:public:ra:xapend:xapend.a_glossary:g:greenfield]] to [[dido:public:ra:xapend:xapend.a_glossary:b:brownfield]] development and from a "build the world" attitude towards "integrate and glue the world" mindset. |
| - | Successful OSS development and adoption not only has to produce products which are solid, strong and robust but also must meet the needs of a [[dido:public:ra:xapend:xapend.a_glossary:c:coi]] that has coalesced around a single minded, purpose built, functionality (i.e., Apache Tomcat application server, PostgreSQL Database, Node.js an asynchronous event-driven [[dido:public:ra:xapend:xapend.a_glossary:j:javascript|JavaScript]] runtime, [[dido:public:ra:xapend:xapend.a_glossary:d:docker]] containerized apps, Kubernetes orchestration engine for containers, etc.). Many of the OSS products are part of many of the successful projects today. | + | Successful OSS development and adoption not only has to produce products which are solid, strong and robust but also must meet the needs of a [[dido:public:ra:xapend:xapend.a_glossary:c:coi]] that has coalesced around a single minded, purpose built, functionality (i.e., Apache Tomcat application [[dido:public:ra:xapend:xapend.a_glossary:s:server|server]], PostgreSQL Database, Node.js an asynchronous event-driven [[dido:public:ra:xapend:xapend.a_glossary:j:javascript|JavaScript]] runtime, [[dido:public:ra:xapend:xapend.a_glossary:d:docker]] containerized apps, Kubernetes orchestration engine for containers, etc.). Many of the OSS products are part of many of the successful projects today. |
| However, it is not good enough to just write software and make it publicly available. At the heart of these successful efforts are the well governed, focused, supporting CoIs. There is a desire from almost all systems (or projects) to join the OSS trend but unfortunately, the need for strong governance and rigorous methodology is minimized or skipped in the name of expediency. Fortunately, there is an organization which can help with this called [[https://todogroup.org/about/ | Talk Openly Develop Openly (TODO)]] (not to be confused with a ''to-do''). | However, it is not good enough to just write software and make it publicly available. At the heart of these successful efforts are the well governed, focused, supporting CoIs. There is a desire from almost all systems (or projects) to join the OSS trend but unfortunately, the need for strong governance and rigorous methodology is minimized or skipped in the name of expediency. Fortunately, there is an organization which can help with this called [[https://todogroup.org/about/ | Talk Openly Develop Openly (TODO)]] (not to be confused with a ''to-do''). | ||
dido/public/ra/1.4_req/2_nonfunc/28_manageability/08_software.1628535018.txt.gz · Last modified: 2021/08/09 14:50 by murphy
