-
-
Notifications
You must be signed in to change notification settings - Fork 72
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Business plans on Gitly? #235
Comments
I presume the non answering mean that it’s out of scope |
Sorry, missed this question. I think paid support is fine, but I'm not sure about the open core model. I think all features should be open source. |
Hello. I hope to contribute with this open issue here, with some interesting and current information.
The open-core model is a business model for the monetization of commercially produced open-source software. Coined by Andrew Lampitt in 2008, the open-core model primarily involves offering a "core" or feature-limited version of a software product as free and open-source software, while offering "commercial" versions or add-ons as like plugins etc. source: Examples of this monetization style include Kubernetes or a Linux kernel modified to serve cloud providers, who then charge users a fee to use that uniquely modified codebase within their cloud services. source: To make the concept more understandable for everyone, Google Docs is software with a subscription model, but it is not open core. This is because Google Docs does not provide the source code, a version, for example, community and open. And at the same time there are free or paid plugins that also don't have source code. That is, it is a product that is almost 99% closed, is that there are some plugins that people make available, but that does not reach half of the source code of plugins available through Google Docs. Subscription and open core models like Linux Kernel are different from the traditional subscription model, which is what I gave in the Google Docs example. But there is an alternative to the open core model and the subscription model, some say the bug bounty idea is interesting. That is, pay per feature or bug, but the idea of being "open" is more of the "developer" than the "community" itself. |
Alex's point is that all the software features should be open to everyone. Different levels of support could be offered, with perhaps a free "tier" being support via community forum, a paid "tier" with direct email support, and an enterprise "tier" with a phone number. |
I agree with the previous post. There should be ways to add value - and make money - beyond making proprietary features. Although Alex, as the owner of this project, has the right to make money from it like this, as long as he doesn't make currently free features paid. |
Hi everyone.
Idea
An interesting idea would be for the community to provide an open core plan, part of the open code and support is paid, this to enable more features, developers, etc.
Concept
https://about.gitly.com/pricing/
Image
reference
question/feedback
What do you all think of this idea?
The text was updated successfully, but these errors were encountered: