Licensing and Permissions

[cosden]

Because it's public, there are a few questions I think we should proactively address:

1. How should we license the content? (Does it have to be the same for each item?)
2. Should each picture have its own attribution?
3. What kind of permission do we need from image owners?
4. Should we insist that the picture owner upload content/approve, or is anything in slack fair game?
5. Do we need a way that people can request a picture be removed?

[github-actions]

Welcome to us-rse! We are excited that this is your first issue!

[vsoch]

1. Not sure, but my inclination would be to retain licensing for whomever contributed the picture OR we could have submission be under some common license (and either way note it on the site)
2. Not sure either
3. Probably permission to post here, or they contribute it
4. I don't know
5. Yes

[cmaimone]

Just generally seconding here that attribution/licensing issues are important -- perhaps make the site not live/rendered until they're addressed? (I'm saying I think it's that important) -- I understand the repo is still available, but that feels different/less official than a rendered website while these issues are worked out

Re: #4 above: Definitely don't think that things in Slack are fair game. That's a private-ish space. This isn't.

[JeffCarver]

I second @cmaimone and @cosden that we need to be careful about attribution and licensing. Those should be explicit before posting something on the web or allowing others to use pictures. I also agree that posting on slack is not explict permission to share publicly.

[sandragesing]

We probably should have a form or so to fill out for licensing to be on the safe side. I know from organizing conferences that the legal department at the university insisted that no photo from attendees/speakers can be posted online if they did not fill out the form and sign it.