Brian E Carpenter <brian.e.carpenter@xxxxxxxxx> writes: > On 10/09/2015 07:58, Charles Eckel (eckelcu) wrote: >> My original response inadvertently gloss over that point. My understanding >> is the same as yours, Sam. >> >> Cheers, >> Charles >> >> On 9/9/15, 10:07 AM, "Sam Hartman" <hartmans-ietf@xxxxxxx> wrote: >> >>>>>>>> "Charles" == Charles Eckel (eckelcu) <eckelcu@xxxxxxxxx> writes: >>> >>> Charles> Good question, Miao. Hackathon registration and >>> Charles> participation is independent of the IETF meeting; however, >>> Charles> we do make it clear in the registration and at the event >>> Charles> that participation in the Hackathon is subject to the IETF >>> Charles> Note Well. In addition to this, open source projects have >>> Charles> their own governance and rules for contributing to >>> Charles> them. These must be adhered to as well when code developed >>> Charles> at the Hackathon is contributed into these projects. >>> >>> My understanding of copyright and the IETF note well is inconsistent >>> with Mr. Fuyou's description though. >>> In particular, typically ownership of the IETF contribution remains with >>> the contributor, although the IETF is granted a rather broad >>> non-exclusive license to >>> the contribution. > > If somebody wants to provide their hackathon code to the IETF, they could > submit an Internet Draft whose body consists of their code, between > <CODE BEGINS> and <CODE ENDS>. Then it becomes an IETF contribution with a > Simplified BSD licence, as I understand the IETF Trust's legal provisions. Since ownership of the contribution stays with the author, it is simpler for the author to release the contribution under a suitable license directly. Further, releasing it directly allows the author to place a copyright notice on the work -- something many free software licenses requires to be preserved. If you submit it in an ID, according to the IETF policies, you aren't allowed to add your own copyright notice to it. /Simon
Attachment:
signature.asc
Description: PGP signature