3 ms·
"We want our candidates to have a portfolio of open source software, but won't allow them to work on open source software while in our employ." That's also som
by Akronymus 5y ago
"We want our candidates to have a portfolio of open source software, but won't allow them to work on open source software while in our employ."
That's also something I keep hearing in anecdotes.
- Aeolun 5y agoWhat do they think will happen if you do work on open source software while in their employ?
- Akronymus 5y agoMost likely nothing, but most companies seem to have the expectation that OSS has to take a backseat
- edoceo 5y agoYea. Give me free code, don't make free code is a common problem.
- colejohnson66 5y agoYour employment contract could stipulate that any programming done outside official work is owned by the company. A “work for hire” of sorts. Whether these “copyright assignment” clauses are legal depends on your jurisdiction.
- mcny 5y agoPersonally, I don't work on open source software. My personal projects are public, free and open source but they are useless to anyone other than for me. The main reason I publish them publicly is ... I don't know why actually. However, one benefit to public github repositories is I can try out various services that are free for open source projects. This way I have exposure to these services which is nice. Also it is easier to get help from others or ask questions when I get stuck. In my experience, I've found programmers very helpful as long as I am willing to put in some effort.
- Akronymus 5y agoFor me it looks very similar to training. they want you to have x, but don't provide the ability to acquire x to their employees.