News for hackers. Stuff that matters.
Re:Building an Open Source Service by fiatjaf on Wednesday October 26, 2016 @05:00PM (#12800494)
What if another company takes open-source Sentry and start offering hosted versions of it, competing with Sentry.io and in the end putting Sentry.io out of the market? Would that make you regret making your software open-source?

I guess this is probably not an issue for Sentry as it is now, but imagine some small company with a new software-as-a-service, super useful and loved everywhere, but without a well-established "name" in the market yet. Does the same answer still apply?

Re:Building an Open Source Service by zeeg on Wednesday October 26, 2016 @05:04PM (#12800539)
There's only two things we really consider as protection of our product and brand:

1. It's a big project, we are the experts (and the only real committers to the service). We also control commit access, so unless you want to maintain a complicated fork it's just not in your best interests.

2. We own the trademarks. This doesn't always help, for example this is literally a copy paste of our previous homepage: http://getsentry.cn/welcome

That said, there are companies out there who absolutely violate the 'spirit of open source' and use our code for other commercial entities. While we're not preventing them from doing that, I promise you we (and many of our users) absolutely look at that in a negative light. In a lot of ways, we're trusting that the fact that our advocates, who are developers, are also willing to do the right thing.

As you mentioned, this isn't really a threat to Sentry these days, but it was a fair concern two years ago. I think you really do have to put trust in the fact that most people aren't evil.

Re:Building an Open Source Service by fiatjaf on Wednesday October 26, 2016 @08:50PM (#12802073)
I see that copy-pasting and using Sentry's name is, but if a competitor credits you, but still offers the hosted service, would you consider it evil?

I have the impression that someone doing it would have a better image even with people loyal to Sentry: "well, these competitors here are not bad guys, just Sentry users like us, the only difference is that they are offering hosted Sentry for lower prices!".

(I'm not talking about the legal stuff, I'm completely ignoring it)

Re:Building an Open Source Service by zeeg on Wednesday October 26, 2016 @10:39PM (#12802544)
Unless you want to maintain a fork we could very easily make life difficult ;)

I don't have a concrete answer, but if it happens you just gotta work around it. Not much different than having a dozen competitors trying to do the same thing as you.

I think it's very easy to see you, as a commercial business, wouldn't want to put all of your livelihood on a project that has 150k lines of code and you know very little about. That's obviously not true for every project, but if your project is so simple there's no reason I couldn't just reimplement it anyways.

Re:Building an Open Source Service by jordigh on Wednesday October 26, 2016 @05:14PM (#12800626)
> I guess this is probably not an issue for Sentry as it is now

It kind of is, with Opbeat as their competitor which forked off from Sentry, but Opbeat have also kept the code that came from Sentry free.

Re:Building an Open Source Service by the_mitsuhiko on Wednesday October 26, 2016 @05:32PM (#12800833)
Opbeat forked the clients not the server. The client forks are fun because we are still credited in their licenses. Most of our competitors have their clients open source so that is not really a concern anyways.
Re:Building an Open Source Service by mperham on Wednesday October 26, 2016 @05:33PM (#12800841)
Generally you license the code so competitors have a disadvantage e.g. with GNU licenses, they may have to open source any changes they make. As the copyright holder, you can do things with the code that they cannot (since you don't have to follow license restrictions), i.e. create premium features.
Re:Building an Open Source Service by zeeg on Wednesday October 26, 2016 @05:40PM (#12800893)
Thats a common situation, but we explicitly refuse to do that. I have a strong opinion that it doesn't represent what open source should be, and thats absolutely free software. I do understand that some things are considered necessary, but we're trying to prove thats not the case.

It's also something that can limit the adoption of your product. I've worked with companies in the past have either refused to use allow GPL software, or would have a significant audit process you'd have to go through to be able to use it.

Re:Building an Open Source Service by nickpsecurity on Wednesday October 26, 2016 @10:06PM (#12802403)
What do you think about using a license that forces freeing any changes to what you shared but doesn't affect anything linking to it dynamically or statically? As in:

http://zeromq.org/area:licensing

Additionally, patent license provisions for using the shared code seem almost mandatory given the patent trolling we're seeing of both suppliers and users of whatever they manage to get through a patent clerk. All the FOSS licenses should try to include some protection there against beneficiaries suing derivatives.

Re:Building an Open Source Service by zeeg on Thursday October 27, 2016 @01:30AM (#12803118)
Definitely not a license expert here. Lots of legal folk I trust would stand by "Apache and only Apache" for releasing FOSS, and I think one of the core reasons is patent protection. We may re-license Sentry at some point to Apache just because its a more understood model and as a growing business that may one day be important. It's also nice that it provides good out of the box tools that are widely supported (e.g. the CLA).
Re:Building an Open Source Service by nickpsecurity on Thursday October 27, 2016 @10:11AM (#12805225)
You should definitely check out MPL too. I was told it's like LGPL for static linking. As in, commercial integrators can use it without releasing their source. Only have to release improvements to sentry itself in that model.
Re:Building an Open Source Service by the_mitsuhiko on Wednesday October 26, 2016 @05:38PM (#12800882)
That's one way to do it but we (Sentry) don't do that. Our server software is BSD licensed.
Re:Building an Open Source Service by dozzie on Wednesday October 26, 2016 @06:11PM (#12801143)
> with GNU licenses, [competitors] may have to open source any changes they make.

Only with AGPL, and only if the competitors expose APGL-licensed software for interaction directly.

Re:Building an Open Source Service by fiatjaf on Wednesday October 26, 2016 @08:53PM (#12802090)
How can you possibly know they've made changes to the software?

Suppose they've started offering Sentry-with-a-twist, how can you know they modified Sentry code? They may as well have written a separate software running in a different stack, but interfacing with Sentry and with the users and providing the twist.

Re:Building an Open Source Service by dozzie on Thursday October 27, 2016 @04:20AM (#12803582)
How can I know? The same way as I know the vendor based their firmware on Linux, so I am entitled to receive a copy of source code. Meaning, I can't, technically.