<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body text="#000000" bgcolor="#FFFFFF">
<div class="moz-cite-prefix">On 07/18/2017 08:35 AM, Dominik Ruf
wrote:<br>
</div>
<blockquote type="cite"
cite="mid:CAAfZa5=WaE3m=7FjQ=Zx7keqy3GPKL4nB0a6A-EFHzWWqYGCXA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<div dir="ltr">Mads Kiilerich <<a
href="mailto:mads@kiilerich.com" moz-do-not-send="true">mads@kiilerich.com</a>>
schrieb am Di., 18. Juli 2017 um 01:10 Uhr:<br>
</div>
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">
Hosting of code from open source contributors requires some
continous<br>
amount of work and resources. Both for establishing trust
and for<br>
cleaning up when rogue players abuse the system anyway. </blockquote>
<div><span style="color:rgb(33,33,33);font-size:13px">How is
that different on</span><span
style="color:rgb(33,33,33);font-size:13px"> </span><a
href="http://bitbucket.org/" target="_blank"
style="font-size:13px" moz-do-not-send="true">bitbucket.org</a><span
style="color:rgb(33,33,33);font-size:13px">?</span></div>
<div style="color:rgb(33,33,33);font-size:13px">What kind of
abuse do you suspect?</div>
</div>
</div>
</blockquote>
<br>
Bitbucket do (for the same reason) have a legal department, constant
monitoring, and people and process for dealing with DMCA takedown
notices and similar.<br>
If we open loopholes where anybody can make anything available for
download, it will be abused for hosting illegal content.<br>
<br>
<blockquote type="cite"
cite="mid:CAAfZa5=WaE3m=7FjQ=Zx7keqy3GPKL4nB0a6A-EFHzWWqYGCXA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">But it can
be<br>
done, assuming we want to do it and establish a realistic
process and<br>
tooling.<br>
<br>
Also, Kallithea is mainly used internally inside
organisations. It has<br>
not been optimized for hosting open source projects with
"random"<br>
contributors. I think some of the short-comings are quite
obvious </blockquote>
<div><span style="color:rgb(33,33,33);font-size:13px">Not to
me.</span></div>
</div>
</div>
</blockquote>
<br>
Before I would host a fully public site with self-registration and
untrusted users, I would want more isolation between users, quotas,
and for example a concept of a user home. One current
show-stopper-ish feature is the need for subscribing to be CCed on
all PRs and comments for a repo.<br>
<br>
<blockquote type="cite"
cite="mid:CAAfZa5=WaE3m=7FjQ=Zx7keqy3GPKL4nB0a6A-EFHzWWqYGCXA@mail.gmail.com">
<div dir="ltr">
<div class="gmail_quote">
<blockquote class="gmail_quote" style="margin:0 0 0
.8ex;border-left:1px #ccc solid;padding-left:1ex">- we<br>
don't need dogfooding to find these. </blockquote>
<div style="color:rgb(33,33,33);font-size:13px">It is not only
about finding issues. It also send a message to potential
users.</div>
<div><span style="color:rgb(33,33,33);font-size:13px">Would
you eat at McDonalds, if their employees eat at Burger
King?</span> <br>
</div>
</div>
</div>
</blockquote>
<br>
I would have even more dislike for McDonalds if their employees
*only* ate McDonalds food. McDonalds might be good for some
purposes, but it is not a solution to all problems and not a full
diet.<br>
<br>
Kallithea has mainly been developed and seen improvements for use
inside organizations. It is not so much built for hosting open
source projects. That would have other requirements that probably
are less relevant to the main use case. We *could* use it for
Kallithea, but I don't have a problem with admitting that this is
not a use case we have aimed for so far.<br>
<br>
It would be nice to use non-proprietary software, but I don't have a
big problem with Bitbucket as long as the repos are in a standard
format that can be used anywhere ... and are mirrored on our own
infrastructure with free software.<br>
<br>
But if Andrew configure account for you (and other trusted
contributors), then it is perfectly fine to use our own Kallithea
for PRs.<br>
<br>
/Mads<br>
</body>
</html>