This is so disappointing. I planned to use it for my project and I really liked...
An apology to open source
11–20 of 259 posts
Re: An apology to open source
#12That's a shame. This serves as a reminder to us all to be very careful when signing employment contracts. We're fortunate enough to be in an industry with huge demand for talent at the moment, so in addition to salary / benefits, things like having the right to open source your work should be included in your negotiations. In my experience, most good companies are OK with it.
Re: An apology to open source
#13This is such a shame. Companies that shut down projects like this are completely ignorant as to the benefits of open-sourcing such a useful tool.
Re: An apology to open source
#14Mirror?
I was able to find at least 3 extant forks on Github, but the fact that the project author's employer was concerned about IP rights would make me wary about using such code. If the author "borrowed" similar code from work he previously did from the employer, it is likely that the MIT license of chart.js is invalid.
Re: An apology to open source
#15Ugh, why? Would a better move not have been to ask the employee to move it to a company affiliated site? Get your name out there and in to developers minds as good guys?
Re: An apology to open source
#16Oh Jesus... does anyone forked that?
Re: An apology to open source
#17Don't just take it down. Destroy it. Make sure that any benefit your employer was receiving from it vanishes. If they claim ownership, despite the work having been done in your free time, demand the overtime pay. Make it clear that OSHA will be involved if they decline.
Hardline dickery deservers to be repaid in kind.
Ah: Edit still available: Destroy was the wrong word. Make inaccessible to everyone, including the employer as if erased. If the employer claims exclusive ownership you have a bargaining chip. They may own it, but they should pay for it.
Re: An apology to open source
#18This shows the shitty policy that most companies have. They use open source internally and give nothing back.
Yeah, I have been working for Rails shop that did exactly this.
I wasn't able to do anything, not even in my spare time, to contribute to open-source projects or do other work. The other work I can understand, because I could help a competitor for an example.
But that they owned ownership for every line of code written by me, even on my time off, was killing my inspiration.
Re: An apology to open source
#19That's a shame. This serves as a reminder to us all to be very careful when signing employment contracts. We're fortunate enough to be in an industry with huge demand for talent at the moment, so in addition to salary / benefits, things like having the right to open source your work should be included in your negotiations. In my experience, most good companies are OK with it.
>This serves as a reminder to us all to be very careful when signing employment contracts.
If he was a full-time employee in the US, a contract wouldn't be necessary for this to be an issue. All work done by an employee on company time or using company resources is 'work for hire' (a term often misused in the software contracting industry, where it rarely applies), and that IP belongs to the company.
>In my experience, most good companies are OK with it.
Most good companies are sometimes 'OK with it'. It depends on how much it will affect their competitive advantages in their field. My employer would probably sign off on open-sourcing a charting library, but not a graph layout library, for example - displaying complex data as graphs is near the core of our business.
Certainly most companies will not grant you a blanket right to open source all of your work for them.
Re: An apology to open source
#20What's the name of the company?