|IRC Nick||Time (GMT-7)||Message|
|taxilian||09:10||in case jim_ comes back, no FireBreath does not support ppapi because ppapi w/out NPAPI is not usable to normal developers|
|resi||13:10||Hi, Could you please tell me which license terms apply to the files autmatically generated by firebreath?|
|taxilian||13:10||… not if he leaves before I can answer, I can't|
|resi||14:10||Hi, Could you please tell me which license terms apply to the files generated automatically by FireBreath (e.g. Factory.cpp)?|
|taxilian||14:10||resi they are unlicensed and belong to you
in other words, whatever license you put on them
|resi||14:10||Thanks.This was also my assumption. How can I prove that to the guys in my company that are responsible for verifying the open source licenses?|
|taxilian||14:10||have them ask me?
I wrote those files
let me see if there is anything in the codebase
I specifically did not put a license on them because they are not licensed
|dcherman2||14:10||they wouldn't fall under the dual BSD/LGPL licensing?|
FireBreath itself does, but those are your files
you can license them however you want, as long as it is compliant with the FireBreath license you choose
and if you choose to use BSD then that can be anything
|resi||14:10||OK. Great. Would it be OK for you if I print out your answer and I show it to my colleagues?
OK. Great. Would it be OK for you if I print out your answer and I show it to my colleagues?
look under "license of generated files"
I just updated it to clarify
|resi||14:10||As I far as I know, the author of the files has the ultimate authority on the license terms.Your answer will reassure my colleagues. Thanks a lot.|
|taxilian||14:10||that should be correct =]|