[OSPO Book] Proposal of additional topics: How to be a good Open Source community citizen and What to prepare when not every one plays by rules.

[victorjunlu]

Following is an example of how to be a good open source community citizen when transitioning from open source model to closed-source model:
In some cases, an open source company may decide to switch to a closed-source model, abandoning the open source community and making its software proprietary. This can be a difficult decision for a company to make, and it requires careful planning and preparation. So, how a company should prepare for an open source company turned non-open source.
Communicate Clearly with the Community
One of the most important things that an open source company should do when transitioning to a closed-source model is to communicate clearly with the open source community. The company should be transparent about its decision to switch to a closed-source model, and it should provide clear reasons for doing so. The company should also provide a timeline for the transition and should explain how the transition will affect the open source community.
Protect the Community
An open source company has a responsibility to the community that has supported its software. When transitioning to a closed-source model, the company should take steps to protect the community. This may involve releasing the software under a permissive license, allowing the community to fork the project and continue development independently, or providing access to the source code for a limited time.
Ensure Continuity of Support
When transitioning to a closed-source model, the company should ensure that existing customers and users of the software will continue to receive support. This may involve providing a transition plan, offering incentives for users to switch to a new product, or providing access to support for a limited time.
Maintain Quality
When transitioning to a closed-source model, the company should ensure that the quality of the software remains high. This may involve hiring additional developers, investing in new technology, or providing training to employees. The company should also ensure that its closed-source product is fully tested and stable before releasing it to customers.
Develop a New Business Model
Transitioning to a closed-source model may require a new business model. The company should carefully consider its revenue streams and develop a strategy for generating revenue from its closed-source software. This may involve offering support and services, licensing the software to other businesses, or developing a subscription model.

[cornelius]

I'm wondering if transitioning from an open source to a closed source model still can be considered behavior of a good open source citizen. For a good open source citizen I would expect that they contribute to the open source ecosystem and take responsibility for maintaining the common good which is used by them and others. So removing software from this common ecosystem by making it proprietary doesn't seem to contribute to this goal.

The mentioned topics are all good points to consider when doing such a transition, but I would not see them under the title how to be a good open source cititzen.

[victorjunlu]

Hi Cornelius, yes, I agree that the title needs further discussion. Actually I joined the CHAOSS Risk Metrics Working Group this past week and I believe topics like these could be part of the risk management topics.