This is an important thread. Most folks I know who contribute to OSS do it as a part of their day job or their work projects get open sourced. It’s actually a fantastic time to be an OSS SWE since there are many companies hiring exclusively for that. It wasn’t the case always.https://twitter.com/thenikhita/status/1022025212802555904 …
-
Show this thread
-
That also has its fair share of downsides (vendor politics especially in the infrastructure/cloud native space). Folks who contribute to OSS on a purely voluntary basis in their spare time shouldn’t even bother to “keep up” with folks doing it as their full time job.
4 replies 0 retweets 15 likesShow this thread -
Replying to @copyconstruct
This makes it also difficult for devs to push their project in a direction their employer does not endorse - that was not the case when OSS development was nearly completely independent from vendor politics.
1 reply 0 retweets 0 likes -
Replying to @neuroserve @copyconstruct
Not necessarily. Before signing your employment agreement, add language to the agreement stating that you continue to own your projects, you own all old and IP contributed to it regardless of whether you're on the clock or using company resources, you make design decisions, etc.
1 reply 0 retweets 0 likes
In some cases the employer will agree to all of that and more. In other cases you'll at least start a necessary conversation about how all of this is going to work before there's any potential for awkward disagreements later.
Loading seems to be taking a while.
Twitter may be over capacity or experiencing a momentary hiccup. Try again or visit Twitter Status for more information.
