781–790 of 1001 posts
Earlier quoted context omitted.
What if you would just publish your code on GitHub, would they seek to punish you?
In some courses publishing coursework on GitHub can break academic integrity rules related to plagiarism. It’s hurt students as more hiring processes assume portfolios. CS departments are behind the times.
Earlier quoted context omitted.
How on earth is Microsoft "absolutely" behind OSS? Which of their main products is Open Source? Windows? Office? SQL Server? Azure? Exchange? What exactly makes Microsoft a company "absolutely behind OSS?" Their stupid boot loader still ignores any other operating system for god's sake. Kudos to people at Microsoft's Marketing and "developer relations" department who won the hearts of developers by allowing TypeScrip…
I work in the public sector in Denmark, and we’ve delt a lot with both IBM and Microsoft over the past 25 years. Microsoft has been one of our best partners, including for the open source software we run, especially since Azure became their mission. IBM has been one of the worst, so bad that I’d dread making any deals with them ever again. I wouldn’t say MS is fully behind OSS though, they contribute a lot these year…
Earlier quoted context omitted.
Yeah sure, and if you like I can also clean the bathrooms because I know how to do it... Off-time is for your own not for your company regardless off what you do with it.
The /s stands for sarcasm
When I worked for IBM (via acquisition), I wanted to fix bugs in Cygwin (owned by Red Hat). Red Hat does not accept patches unless you get permission from your current employer. I could not get anybody in IBM to sign Red Hat's permission slip. Nobody would sign because it's all risk, no reward from IBM's point of view.
I have the same problem in academia, being in a non-CS department, I'm required to notify the University's Center for Technology & Venture Commercialization about assigning my copyright over software to another entity (like the FSF), but so far I have been unsuccessful at getting them to sign the letter the FSF wants, despite the code I would be contributing being completely outside of my work at the University and s…
All large organizations have a decent amount of bureaucracy around copyright and IP, but the difference is good ones make it easy and straightforward for employees to go through that process.
Google, for example, has a well-documented and clear process for contributing to open source software (both in work hours and in personal time): https://opensource.google.com/docs/patching/
I went to IBM(India) interview sometime in 2011, after leaving GlusterFS (Red Hat). Interview went well, during final call with management. I was asked to stop working on Open Source during weekends or off-hours even though the IBM project and my Open Source work has nothing in common. I said, "I thought, IBM support Open Source right?" his response, "Yes, but that's another team" I decided to call-off the interview…
Earlier quoted context omitted.
Also Atomic/CoreOS - this will probably be cut now, perhaps even before it is complete. http://www.projectatomic.io/blog/2018/06/welcome-to-fedora-c...
I doubt it. When you read the IBM and Core OS acquisition press releases side by side you get a lot of the same "hybrid cloud" language. Update: Near as I can tell the acquisition completed in March/April.
In progress greenfield projects with no obvious monetisation are just the sort of thing that gets cut in this sort of merger, after the assurances that redhat will be run as a completely independent unit are forgotten and a new manager comes in looking to trim fat.
I use coreos and am now very concerned about its future.
When I worked for IBM (via acquisition), I wanted to fix bugs in Cygwin (owned by Red Hat). Red Hat does not accept patches unless you get permission from your current employer. I could not get anybody in IBM to sign Red Hat's permission slip. Nobody would sign because it's all risk, no reward from IBM's point of view.
I went to IBM(India) interview sometime in 2011, after leaving GlusterFS (Red Hat). Interview went well, during final call with management. I was asked to stop working on Open Source during weekends or off-hours even though the IBM project and my Open Source work has nothing in common. I said, "I thought, IBM support Open Source right?" his response, "Yes, but that's another team" I decided to call-off the interview…
What wouldn't be the 5th time I've heard such stories, but I don't think it's in any way specific to IBM. Employers like that want any OT you do to be dedicated to THEIR endeavor, not somebody else's...even your own. If you're able and willing to code in your off-time, you should be doing it for the good of the Company. /s