Terminology
SOFT org
A SOFT org is a cooperative organization which follows SOFT framework.
SOFT membership
Members include producers, maintainers and consumers of all the software products produced by the SOFT org combined.
Product sub
Each product produced at a SOFT org is its own autonomous sub-cooperative.
SOFT source software
The software produced at a SOFT org should publish its source code which is accessible by the membership of the product sub. The SOFT license provides access to view and modify the code, use for personal or organizational consumption purposes. The license however prohibits resale, redistribution and any other forms of commercial use without additional use grants.
Root fund
Root fund is a financial mechanism that provides ongoing operational support for the SOFT. The fund covers the SOFT org's operating costs and provides seed funding for new product ideas. This ensures that the organization can continue to operate sustainably and promote innovation through the development of new software products.
Root equity ownership
A certain percentage share of equity of a newly produced product that is owned by root fund.
Root equity ownership refers to the percentage share of equity in a newly produced product by the org. This percentage of equity ownership ensures that the Root fund has a vested interest in the success of the product and can potentially benefit from any financial gains resulting from its success. This equity ownership provides a mechanism for the Root fund to support the org's ongoing operations and enable the development of new software products.
Product life cycle
Blue paper
A blue paper is a document that provides a detailed description of a product idea and its implementation. It typically includes technical specifications, user flows, and implementation strategies. The purpose of a blue paper is to provide a comprehensive plan for the production and implementation of a product.
White paper
A white paper is a document that provides a detailed explanation of an idea or concept. It typically includes research, analysis, and data to support the idea or concept. The purpose of a white paper is to inform and educate readers about the idea, its potential benefits, and how it can be implemented.
Conception & conceiver
"Conception" refers to the process of coming up with an idea or concept. It is the initial stage of product development, where the idea is conceived. During this stage, the focus is on generating and refining ideas and determining the feasibility of implementing them. The conception stage is critical to the success of a product as it sets the foundation for the entire development process.
A "conceiver" is the person(s) responsible for coming up with the idea or concept during the conception stage. They are often the driving force behind the product development process, and their ideas and insights set the foundation for the product's success.
Development & developer(s)
"Development" refers to the process of transforming an idea or concept into a tangible product design and a blue paper.
A "developer" is a person or team responsible for carrying out the development process.
Production & producers
"Production" refers to the process of transforming the design and blue paper into a tangible product. It is the stage where the product is built, tested, and refined until it meets the desired specifications. Production involves a range of activities, including coding, testing, debugging, and integration. Effective production requires a combination of technical skills, creativity, and problem-solving abilities.
A "producer" is a person or team responsible for carrying out the production process. producers are skilled in programming languages and technologies and have a deep understanding of software development processes. They work closely with the developers to bring the idea to life by writing code, testing the product, and making improvements as needed.
Consumption, consumers, maintenance and maintainers
"Consumption" refers to the process of using a product or service. In the context of software products, consumption involves using the software for its intended purpose.
A "consumer" is a person or organization that uses a product or service. In the context of software products, consumers are the end-users who benefit from the features and functionalities of the software. Consumers play a critical role in shaping the success of a product, as their feedback and usage patterns can inform future updates and improvements.
"Maintenance" refers to the ongoing process of keeping a product or service in good working order. In the context of software products, maintenance involves fixing bugs, upgrading features, and ensuring that the software runs smoothly. Effective maintenance requires a combination of technical knowledge, problem-solving skills, and attention to detail.
A "maintainer" is a person or team responsible for carrying out maintenance activities. Maintainers are skilled in software development and have a deep understanding of the software architecture. They work closely with the consumers to identify and fix bugs, upgrade features, and improve the overall performance of the software. Maintainers are critical to the success of a product, as their work ensures that the software remains functional and useful over time.
Voting thresholds
voting threshold for bylaw amendment
voting threshold for funding
voting threshold for product retirement
Last updated
Was this helpful?