Discussion
I'm just starting thinking it through. It basically means Outsystems develops a proprietary platform that engages users to share their own works under OS licenses with other users to further improve the usage of Outsystems by drastically extending its adaptability, scope and use-cases.
But the platform stays proprietary and any contributions stay dependent on the platform.
Meaning that users / institutions who develop applications, pipelines etc to be used by the underlying outsystems can be shared in the "Forge" with other Outsystems user through an open source licensing model (BSD if not stated otherwise).
It also goes the other way round: Users /institutions can use "Forge" to share external OS libraries they discovered to be re-used by the - still proprietary - Outsystems, with or without adaption.
I'm just starting thinking it through. It basically means Outsystems develops a proprietary platform that engages users to share their own works under OS licenses with other users to further improve the usage of Outsystems by drastically extending its adaptability, scope and use-cases.
But the platform stays proprietary and any contributions stay dependent on the platform.
While I on one hand appreciate that Outsystems encourages its community to share developments through OS licenses, on the other hand it might only serve to increase dependency on its proprietary roots.
Open source community building as a sweetener for monopolistic dependencies?
What do you think?
#outsystems #forge #opensource #dependency #publicadministration
Thanks for this writing. Totally agree, and made a post on the matter, at:
https://discuss.coding.social/t/how-proprietary-commercial-parties-sap-value-from-the-commons/779
Thanks for this writing. Totally agree, and made a post on the matter, at:
https://discuss.coding.social/t/how-proprietary-commercial-parties-sap-value-from-the-commons/779
A space for Bonfire maintainers and contributors to communicate
