<div dir="ltr"><br><div class="gmail_extra"><br><br><div class="gmail_quote">On 24 April 2014 09:56, Stephen Gallagher <span dir="ltr"><<a href="mailto:sgallagh@redhat.com" target="_blank">sgallagh@redhat.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">-----BEGIN PGP SIGNED MESSAGE-----<br>
Hash: SHA1<br>
<br>
</div><div class="">On 04/24/2014 11:01 AM, Stephen John Smoogen wrote:<br>
><br>
><br>
><br>
> On 24 April 2014 02:49, Christian Schaller <<a href="mailto:cschalle@redhat.com">cschalle@redhat.com</a><br>
</div><div><div class="h5">> <mailto:<a href="mailto:cschalle@redhat.com">cschalle@redhat.com</a>>> wrote:<br>
><br>
> Well my point is I spoke to Red Hat legal before I even posted the<br>
> original proposal to open up to more 3rd party repositories some<br>
> Months ago. There are a lot of repositories that it is perfectly<br>
> fine for Fedora to include from a legal perspective. But they will<br>
> need to be reviewed by legal on a case to case basis, going to<br>
> legal up front and saying 'hey can I include a hypothetical<br>
> repository' will only yield you the answer 'depends on the<br>
> repository'.<br>
><br>
><br>
> OK cool. What is the plan for when repositories change what they<br>
> are carrying and add stuff that may be legal for them but not for<br>
> others? Will there be periodic reviews to make sure that this<br>
> hasn't happened or some way that we roll back what repositories we<br>
> recommend?<br>
><br>
<br>
<br>
</div></div>At the risk of being glib: What's the plan for periodically<br>
re-reviewing every package in Fedora to make sure that its sources<br>
always remain legal?<br>
<br>
It's the same problem and it can only realistically be dealt with by<br>
"If someone notices, deal with it then."</blockquote><div><br></div><div>There are a couple of differences. If we find that dvdcss was added to a package, we can rip out that package, put an update in the repository and people who do updates get a package without dvdcss. A third party repository is one we don't have any control over. If code that the 3rd party has no legal right to ship or fill in problem here, what is our remediation to our users? Are we in contributary infringement because we gave the users a way access to pirated software that we never intended in the first place? Is there an agreement between us and the third party that they are to be offering X, that they are legally able to offer X, and that if they are not they are to take all liability of offering X?</div>
<div><br></div><div>These were things that people were wondering when this came up in the past. </div></div><div><br></div>-- <br><div dir="ltr">Stephen J Smoogen.<br><br></div>
</div></div>