lundi 23 février 2015

Where is the line drawn when sharing knowledge of open source projects while working within a company?


I'm currently working within a large corporation that has a department specifically for open source development. The idea being, someone comes to us with a project, and we develop solutions based on what's out there in the open source community.


I recently had my knuckles rapped by my line manager for doing a series of tutorials. Two of the projects in question where Liferay and Teiid in this case. I created some simple github tutorials to share with people and started to do some youtube videos on Teiid. My line manager took me into the office and told me to delete the github code and to remove the videos otherwise I'd be subject to disciplinary action. Now none of the code had anything to do with what we were doing in work, nor did it expose anything related to the company.


I did this with the best intentions. We are supposed to be open source developers, yet the company has yet to contribute a single thing back in terms of code or support to the community. I thought it would be nice to do some tutorials for my own personal development and give something back to the community. So, is there a genuine problem with doing the above?


If your company started looking at using Spring 4 or whatever framework is on the radar, would be wrong if you chose to do some videos or upload some code tutorials on github based on your own research?


This is something I really want to get legal advice on, but I thought id post it here to see if anyone has experienced this problem. I don't really want to work for a company that tries to impose these restrictions. In my mind, it goes against the nature of open source, all we are doing is capitalising on what is out there and not giving a single thing back.





Aucun commentaire:

Enregistrer un commentaire