My fix will be in a file which has a GPL copyright notice, so I think there won't be a problem with it.
Still, it might be a good idea to include the license in the root directory of the repository. It's recommended e.g. by GNU GPL how-to. 2017-11-09 16:33 GMT+01:00 Michał Wróbel <michal.a.wro...@gmail.com>: > Hi Manuel, > > Is it possible to include "LICENSE.md" file in the repository? It seems > that GitHub even has a tool for that: > > https://help.github.com/articles/adding-a-license-to-a-repository/ > > Thanks, > Michał > > 2017-11-09 15:36 GMT+01:00 Manuel Uhm <manuel....@ettus.com>: > >> Hi Michal. >> >> UHD and RFNoC and both covered under GPLv3. We look forward to seeing >> your fix! >> >> Cheers, >> >> Manuel >> >> >> >> From: Michał Wróbel via USRP-users >> Sent: Thursday, November 9, 2:29 AM >> Subject: [USRP-users] FPGA source code license >> To: USRP-users >> >> >> I want to contribute a fix to https://github.com/EttusResearch/fpga >> repository. >> However, given my agreement with the company I work for, the process of >> submitting the patch might be different depending on the license of the >> project I want to contribute to. My assumption would be that the license is >> the same as GNU Radio project (GPL-3.0), however the mentioned FPGA source >> code repository doesn't state that explicitly. Can you clarify which >> license does the FPGA code for USRP devices use? >> >> >> >
_______________________________________________ USRP-users mailing list USRP-users@lists.ettus.com http://lists.ettus.com/mailman/listinfo/usrp-users_lists.ettus.com
