|
|
|
|
|
by MarkinK
752 days ago
|
|
> I would consider what kind of licensing you want to do, I would also consider goals in doing this. One huge benefit of an open source SaaS offering is the freedom to take control of what you're getting out of it in-house, or going straight to the vendor. We plan to put both back and front under Apache-2.0. It seems like a good enough way to show that the user won't depend on us. > Will you be offering migration to and from your SaaS service? Yes, we plan to continue offering the cloud for those who don't want to deploy their own solution. > As for building a community, definitely make a Discord and a forum where people can come together and get help publicly, figure out how to get a stackoverflow space for it as well. We're thinking about Discord right now, even started one. That is an interesting idea about Stackoverflow, thank you we'll think about it! |
|
Also remember that open sourcing something isn't a marketing panacea; you can still struggle to get people interested in it afterwards. It's a useful step if it calms your customers since they don't have to worry as much if you go away, and your value isn't the actual software but support around it or something along those lines.