Except that you work for a State University supported by tax payers. Thus Open Records laws apply to any and all code you develop while working for UCSD.
On Fri, Apr 14, 2017 at 5:39 PM, Ruben ON3RVH on3rvh@on3rvh.be wrote:
(Please trim inclusions from previous messages) _______________________________________________ Yeah if parts of the code are written on company time or with company resources (laptop and such) then the code is strictly owned by your employer. No doubt about it, it's in your contract (and mine and everyone else in IT) :/
On 14 Apr 2017, at 21:05, Brian Kantor Brian@UCSD.Edu wrote:
(Please trim inclusions from previous messages) _______________________________________________ I have; the problem is that it's derived from several non-open-source programs that I don't own the copyright on. Getting permission to freely distribute it would be extremely difficult. It's also unclear whether the parts I wrote aren't owned by my employer. So no, I doubt it'll ever be open-source.
- Brian
On Fri, Apr 14, 2017 at 11:00:20AM -0700, Tom Hayward wrote: Have you considered open sourcing this infrastructure software so we can get more eyes looking for bugs like this?
Tom KD7LXL
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net
44Net mailing list 44Net@hamradio.ucsd.edu http://hamradio.ucsd.edu/mailman/listinfo/44net