People keep complaining about how hard and expensive it is to attract top talent. This kind of measure is exactly how you do it. Provide an environment where employees feel trusted and empowered, pay market rate, screen properly instead of having applicants jump through hoops, and you won't have much trouble hiring. Kudos to github for this, I'm impressed!
For real. I am an indie game dev who recently released his first big game on Steam. Just a week or two ago I had a prospective company tell me that, in order to hire me, I would need to sell them the entirety of my personally-developed IP and dissolve my interest in my own company. Needless to say, I decided against that job.
GitHub lets staff own IP developed for personal projects using company resources
51–60 of 484 posts
Re: GitHub lets staff own IP developed for personal projects using company resources
#52Even the fact that game developers are allowed to create other games outside of work, potentially with other non-studio teams is a super nice perk of working here.
Re: GitHub lets staff own IP developed for personal projects using company resources
#53Very good and very honest.
Re: GitHub lets staff own IP developed for personal projects using company resources
#54The cost of not using company hardware or time is that of a laptop and working outside your "9-5"; simple insurance against the potential costs.
Re: GitHub lets staff own IP developed for personal projects using company resources
#55People keep complaining about how hard and expensive it is to attract top talent. This kind of measure is exactly how you do it. Provide an environment where employees feel trusted and empowered, pay market rate, screen properly instead of having applicants jump through hoops, and you won't have much trouble hiring. Kudos to github for this, I'm impressed!
Sad that having even minimal employee rights is some how seen as exceptional.
Re: GitHub lets staff own IP developed for personal projects using company resources
#56Re: GitHub lets staff own IP developed for personal projects using company resources
#57This is just putting into a contract what ought to be considered normal and reasonable defaults. I don't think they deserve special praise for it, rather companies that don't do this deserve criticism. Whenever I've encountered overly grasping IP clauses in contracts I've always had them re-written so they only cover work which is done during working hours or related to . No employer has ever objected to this, they u…
I've not had this luck, personally. They are always willing to forgo the job offer just to ensure that everyone has the same contracts. I'm guessing that it's going to be a size of business issue.
And the IP assignment clauses are, for the most part, getting worse and worse; my current one extends the assignment to a year after termination, voluntary or not.
Re: GitHub lets staff own IP developed for personal projects using company resources
#58People keep complaining about how hard and expensive it is to attract top talent. This kind of measure is exactly how you do it. Provide an environment where employees feel trusted and empowered, pay market rate, screen properly instead of having applicants jump through hoops, and you won't have much trouble hiring. Kudos to github for this, I'm impressed!
Sad that having even minimal employee rights is some how seen as exceptional.
I have been working on mplyees.com, a site where employees can share what needs to change publicly and anonymously. Hopefully we can bridge this divide since employee happiness is key to a successful business.
Re: GitHub lets staff own IP developed for personal projects using company resources
#59Earlier quoted context omitted.
For real. I am an indie game dev who recently released his first big game on Steam. Just a week or two ago I had a prospective company tell me that, in order to hire me, I would need to sell them the entirety of my personally-developed IP and dissolve my interest in my own company. Needless to say, I decided against that job.
That's an absolutely absurd request. I can understand if they said that you wouldn't be able to work on your game during business hours, or on your company machine, but to request that you dissolve your company and sell them your IP? That's insane
Re: GitHub lets staff own IP developed for personal projects using company resources
#60Pet projects are not necessarily good for a company: 1) Code is not necessarily an asset, it is also a liability: needs to be maintained, tested, documented, etc. This has a non-trivial cost. 2) Engineer salaries are usually more expensive than a license. 3) Experience working using internal frameworks/libraries/etc can be harder to trade in the marketplace, especially if you are not the author. 4) It is hard to keep…
You might want to move the last sentence to the beginning. Your opening comment could easily be interpreted as "companies should forbid pet projects".