* just do it, and ask forgiveness or deal with the consequences.
* ask a lawyer to look at your contract and state law and see if the company has the right to what you do off hours on your own equipment
* try to sell the side project as beneficial to the company (cross training, extra publicity)
* do a side project, but expect to throw it away
* pick different ways to do a side project--there are many way. Contribute to open source via QA, documentation, user support. Do user group talks. Reach out to authors in the space that you are in and offer to review technical books. Join an email list and answer questions of other users.
* walk--find a different boss in the same company who will let you do this
* walk--find a different company
Alternatively, argue that letting you work on solo projects will be beneficial to the employer; Risk-free testing of new frameworks and languages that leads to an experienced developer.
For some very big companies (I've worked at one myself) they seem to have a zero tolerance policy of outside work and you might be SOL in that case - I guess you have to ask yourself whether it's worth it then.
You might consider asking in the context of a more general compensation discussion than just "Hey boss, can I work on OSS?" That way, if they say "No side projects", you'll say "OK, in lieu of the side projects, I'll need more money." It's easier to be sticklers for the stock agreements when there's absolutely no cost to the company to insist on the usual boilerplate, but minor concessions on the boilerplate are often easier than concessions on things which actually appear on the company's books.
Otherwise big companies could claim they own the the capitol improvements to your property which you do on your own time.
Generally don't be a dick and work on your stuff while at work and you will be fine.
(Whether this would stand up in court is dubious, but do you also want to go up against a billion-dollar company's crack legal team in court?)
Also, I've heard the main issue isn't actually getting sued, it's that VCs or investors won't even touch you if there's the slightest hint that you might not own your code. If your side-project takes off it's nice to be able to enlist other peoples' help instead of miring yourself in legalities.
Agree with the VC thing, but assuming you are doing it outside of work it shouldn't be a huge problem, but check with a lawyer.
Why not? These large corporations would pay you $1/hour if the market conditions let them.
The people in companies make the decisions and if you are good to them generally they will be good to you. Don't make bad blood by doing the wrong thing.
> Just ask. The worst they can say is "No."
And that's where I have to ask: what do you do when they say no? I followed this advice a year back or so and it essentially put the brakes on any serious side-projects. I work for a big company that you've absolutely heard of.