3 ms·
The idea of paying someone to contribute a week of their time to an open source project is commendable, but a couple of issues spring to mind; 1. The problem w
by onion2k 12y ago
The idea of paying someone to contribute a week of their time to an open source project is commendable, but a couple of issues spring to mind;
1. The problem with any "pay someone to do some test work" solution to hiring ignores the fact that most people already have a job. They will need to either take time off to do the test, which is effectively asking someone to give up vacation time to speculatively spend time working for a new job, or for them to do the test work outside of hours and be consequentially less effective in both the test and their existing job. Neither option is reasonable. There might also be contractual obligations with their current role that prohibit them working on paid outside development.
2. Having someone contributing to an open source project for a week and then vanishing means lots of open projects would get tiny bits of unmaintained code pushed to them making the maintainers lives harder. That's fine if it's a trivial big fix, but if you wanted to test someone's ability to add a feature to a project you're essentially asking the project maintainers to take on a feature that won't be supported afterwards. Again, that's not reasonable. This could be mitigated by giving the employee time to carry on supporting the feature once they're hired, or for an existing employee to maintain code that's added if the hire is rejected.
I like the idea, but really, why not just make it known that your company prefers to hire people with an existing profile in an open source project? That would encourage people to contribute in the long term rather than just popping in for a week.
- zaroth 12y agoI think looking for a new job should take some time. It's definitely going to take time out of the work day. That's a fact of capitalism, and it's unfair for the current company to feel cheated when employees take time to find a new place to work. That might have to occur during normal business hours, and ultimately paying for that is part and parcel of being "exempt". If they are hourly, certainly they would exclude that time. It's a great point dumping a bit of un-maintained code. Better to dump a bit of un-maintained documentation perhaps, or close obvious bugs. I don't think there'll be much of it, but all significant code should have backwards compatibility and documentation. But more likely, the contributions are small things. Very good points to consider carefully if doing this. I do think the information value is reasonable. It does take a time commitment to review what was done. Changing jobs is a rare opportunity to take some time to work on something "else". Once you're in the new job it can just expand to take up every available moment.
- dalke 12y agoDid you really just combine "fact of capitalism" and "it's unfair for the current company to feel cheated" in the same sentence? Where in the facts of capitalism does it say that companies will be fair in how they treat their employees, and that time off to seek employment elsewhere is part of being fair? In fact, I thought it was the other way around. When someone changes a job, they get a revaluation of what their job is worth. Often the job change comes with a salary increase and higher status in the new company. This serves to raise the price of a worker. By discouraging workers from leaving, a company can keep its wages lower because the workers are not as coupled to the market rate.
- deleted 12y ago[deleted]
- zaroth 12y agoHmm... I guess I did! I am thinking the market for workers required the reasonably free flow of workers between companies. Obviously there are issues with our labor market, but I don't think it's so bad that employers are able to actively prevent employees from spending even significant amounts of time job searching. Of course I'm not saying employers should pay for the employee to search for a new job (although in practice that often happens to some extent). Just that they can't stop them, and shouldn't be able to retaliate against employees who spend time off the clock interviewing. To your point, I couldn't find any particular CA or Fed statues that guarantee this. If CA doesn't offer it, then I guess it must be far-fetched on my part.
- Jeremy1026 12y agoTaking the afternoon off for an interview, and taking a week off to write code that may or may not turn out into a job offer are two very different things.