51–60 of 81 posts
Earlier quoted context omitted.
Would it make sense to have a license that gives any contributors a full license as long as they have ownership in the company they want to use it with or if that company makes a million in revenue?
my counter: how would you know if someone is using your AGPL software without paying you and how would you enforce it?
Hey, One good case study is Maybe Finance. It was a dead project. They open sourced it. And it went viral. And they raised $1.5m within another few weeks. The virality was on GitHub stars and Twitter. I run a channel about open source that may give you ideas of what other COSS projects are doing: https://youtube.com/elie2222 My COSS is called Inbox Zero: https://getinboxzero.com .
COSS stands for ? Controller of site safety doesn't exactly fit the bill..
It's likely "Commercial Open Source Software"
It's not clear to me why you want to open source. Is your hope that your product is so good people will install it and run it for themselves? As others have said, I doubt you'll get anyone interested in writing code. It's a niche product in a less popular language, and you'd need to get people using the product who can code. Not a lot of people who use CRM/ERP also code. What goal are you trying to achieve?
That's all true, but why not put it out there for all to see? This project is useful. People are using it. There are customers with hundreds of users and tens of millions of rows in the database. But the product is not growing fast. What's the point of hiding this code and not putting it out into the open source?
Open sourcing it will not necessarily give you signficantly more growth but it will give you more work and if it actually any useful, someone will fork it and make a better version then outgrow you
For anyone else wondering what the product is, it appears it is this: https://ozma.io/
Make sure to AGPL it so you can still relicense and sell it later to someone (or more than one someone) who thinks they can make money with it.
I'm afraid that AGPL is not an actual open-source launch test. As a developer, I wouldn't contribute to such a product.
I would definitely focus more than anything on figuring out what kind of license you want to do. For example AGPL is probably the most sensible if you want to force anyone making back-end changes to share them back, but it also puts off people like me, who avoid that license like the plague, but when something is AGPL and I only care about using it as-is, that's perfectly fine. The caveat there being you could dual-l…
isn't most YC open-core products AGPL basically not really open source unless you pay them for it?
Earlier quoted context omitted.
Going back to the original question of the thread, it’s starting to sound more like a grieving process than an answerable question. How do you open source the code? You flip it from private to public. That’s pretty much it. Well, okay, maybe an over-simplification. If the business is small and profitable but it’s not growing how you’d like then I’d probably be more interested in selling it if it was me. I am not sure…
> it's starting to sound more like a grieving process Why? No grieving. Many products in the world are not growing as fast as their creators would like – it is OK. We just try new things and see what happens. Like what if you put all the code on the net :-)
Though, I like what someone else brought up in another reply to you about pain/dream/fix. It’s very similar to what you learn in programs like Force Management training where they teach frameworks like MEDDPICC. Finding business pain, demonstrating negative consequences to build urgency, etc.
I don’t know if this is something you’ve already done or if the sales approach has been more like “if you build it they will come.”