Re: [hackathon] What is the IPR policy for Hackathon? RE: [94all] IETF 9

The question of rights is important for the Hackathon. I have a personal
perspective on this, largely from a pragmatic viewpoint.

My primary goal is to make it possible for people to hack the things they want
to hack. This means that they should be able to work on Linux kernel and
whatever else, without causing issues in their ability to commit code to the
relevant open source projects. And change existing code. And work together
with others inside and outside the IETF Hackathon. To me this says: respect
the rules of the relevant open source project when it comes to
code.

But code is not everything in the Hackathon. You also have discussions,
presentations, and demos. I think it is a reasonable assumption that the
usual IETF copyright and IPR rules apply there. For instance, that IETF
gets rights to use the slides in proceedings, or that if you convince your
IETF colleagues to work on some cool extension, you should let the
IETF and those colleagues know about the IPR you know of…

Is this an approach that people feel comfortable with?

Note: The IAOC and IETF legal team are also working on this topic and may
be saying something as well. This e-mail isn’t a legal opinion; I just want
to express my view on what kind of a setup works for the participants.
And that I think needs to be the starting point.

Jari

signature.asc
Description: Message signed with OpenPGP using GPGMail