|
|
Open Source Product Cycle
- A need is seen.
- A solution is built.
- Usually by an individual who can program/script, or by
the IT talent of an organization.
- Alpha solution is tested.
- Using the environment where the need was first preceived.
- Debugging.
- Any problems encountered are corrected so the solution works.
- Small-scale Beta deployment.
- Solution is used in production at development point.
- Source is made available, and notices given
(e.g. www.freshmeat.net).
- Early Adapters (tend to be technical types) download
and deploy solution.
- Debugging and feature additions (based on feedback).
- As the solution is used in a wider range of environments,
additional bugs are discovered.
- As the source is available, those who discover the bugs can
look at the source code to document the problem, and even patching
the code to fix the bug.
- Bug notices and patches are returned to author for consideration
and use.
- Large-scale Production deployment.
- Solution has entered a state of stability making it
of interest to the general user. Notice of V1.0 is made.
- Debugging and feature additions (based on feedback).
- At no point did money change hands. Only code and information.
|