Earlier quoted context omitted.
To add an anecdote: on my last job search I got offers from two different but very similar companies (both around ~200 people). I got one first, read through the contract, saw the standard clause about owning your whole life. I told them it was a deal-breaker if we couldn't get it changed. I got the standard response "oh we never act on that, lots of people here have side-projects", etc. I told them if that was the p…
I work at a startup that had a similar clause. During hiring, I asked them to add some language that it was specific only to work that is competing in nature with the core business. CEO was happy to oblige. No issues with me doing side projects so far. It has been 4+ years. Big companies probably suck harder though.
Bumble claims IP rights on employee's open-source libs
321–330 of 339 posts
Re: Bumble claims IP rights on employee's open-source libs
#322I have a slightly unrelated question and I'm in need of advice: I'm about to work on a grant, with another PI at University of Sydney for a project we've worked on for four years. This grant is to advance our mission of building software system for supporting personalized bacteriophage therapy. Essentially, we're building software to make personalized therapy possible in this space, so we're building something critic…
The default position from legal teams ( uni or corporate) will always be to own everything.
Re: Bumble claims IP rights on employee's open-source libs
#323Earlier quoted context omitted.
Thirded, I would never knowingly work for a company with a clause like that. Whenever I see it, I strike it out and return the signed contract. Usually it's easier for them to just sign and get it over with than to go into a whole thing with legal. This is startups, though. YMMV with big companies. Still, no way I'd accept them owning my considerable volume of (FOSS) side-projects.
I applied for a job as a network engineer with a (then large) UK ISP that had a "we will own all your IP", managed to negotiate that to "I keep anything done on my kit, on my time" (which is fair, I think). Then the ISP was acquired, we were promised that all extra contract negotiations would be honoured, but it seems my contract amendment was in one of a few boxes that somehow did not make it across. Cue an exciting…
Re: Bumble claims IP rights on employee's open-source libs
#324I worked for a company once that had this sort of "we own everything" IP clause. They tried to get me to sign it after I had already started. I crossed out that part, initialed the change, and sent it back unsigned. Ended up going back and forth a few times, and then it got dropped behind a desk or something and we all forgot about it. Not surprisingly, I suppose, that company turned out to be a bit of a mess for oth…
> I worked for a company once that had this sort of "we own everything" IP clause. To clarify: Bumble doesn't appear to be going after everything this developer produced while working for them. They're claiming ownership of only two specific repos, both of which even mention that they were "inspired by" Badoo/Bumble open-source projects. These two repos were developed while the developer was working for Badoo/Bumble…
Re: Bumble claims IP rights on employee's open-source libs
#325Re: Bumble claims IP rights on employee's open-source libs
#326[1] https://twitter.com/arkann1985/status/1467914399381925888
Re: Bumble claims IP rights on employee's open-source libs
#327Earlier quoted context omitted.
Keep in mind that this labour that's considered utself shortage, overpayed and somewhat 'elite'. Most devs thing standard issues of labour don't apply to them. Yet we can barely get a useless clause changed in a contract
Honestly my main hope is that junior devs of ten years ago have had to put up with this long enough that they're senior enough now to stick up for the direct reports they perhaps have now. Of course, it's far more common to develop the attitude that if it was "standard" when they were junior and they turned out alright then surely it's fine. And for 99% of them it will have turned out fine. I've repeatedly heard from…
This example is rightly absurd because if someone told me "don't worry about that code that will segfault, it's never actually called", I would naturally say "WTF this is unacceptable complacency". And yet the argument in both situations is damn near identical!
I think this no good at all, and when the humanities people bring up STEM credulousness, I am quite sympathetic.
Re: Bumble claims IP rights on employee's open-source libs
#328A note to Bumble, this makes me not want to work for you or anyone who is currently in a related leadership position at Bumble (ie: eng leadership, etc.). Given the lack of supply in engineering the bad publicity is going to cost you more than any miniscule gain. edit: And I don't even publish OSS anymore but if you're willing to go after an employee for something this petty what else would you go after them for.
> but if you're willing to go after an employee for something this petty After reading more closely, it appears both repos are derivative works of pojects that Bumble (aka Badoo) owns. It says so in the README.md. They were also written while the author was employed by Badoo/Bumble. I don't think this is as clear-cut in favor of the developer as the comments would suggest.
I wonder what the implications are, and what else there will be to know on this case later.
Re: Bumble claims IP rights on employee's open-source libs
#329Earlier quoted context omitted.
Don't have money for that. May be an IP attorney here on HN can help us out?!
> Don't have money for that. and how about money to defend a potential lawsuit? you're gambling with more than just your job, honestly.
Re: Bumble claims IP rights on employee's open-source libs
#330Earlier quoted context omitted.
I’d like to differ. The foundation of my strategy is that I shouldn’t be obligated to run every code I write with my company legal. On the contrary, the simple reason that my code is generic absolves me from having to consult my company for anything I decide to write in my own time on my own property. I'm never going to say “I 'took' it because I thought I might use it later”. That clearly implies theft. My reasoning…
> Nevertheless, I think we have our separate approaches and I think we can agree to disagree. That's not how the law works. You're either right that your solution works or you're wrong. I'm not a lawyer, but I'm warning you that you really need to talk to an attorney before assuming that this practice will keep you safe.
> That's not how the law works.
Oh, this is how the law works. Unlike programming, there's never a hard right or wrong.
> you really need to talk to an attorney
that's not what you said earlier. your idea is that I should run it through my company's legal for everything I do. Let me enlighten you what will happen next. They will simply summarily reject my request and put me on a watchlist. Consult your company legal only if you need to keep written evidence for your defense. For any advise, always consult an attorney from outside.
Anyway, after getting all feedback from other comments in this thread, I did decide to run this with a lawyer and after a good and pretty long discussion and going through all my stuff, he is pretty satisfied with my setup. In fact, some of the things I did are an overkill! Wouldn't say it would work for you too as the laws of the land from where you come from might be wildly different.