<html>
<head>
<meta content="text/html; charset=utf-8" http-equiv="Content-Type">
</head>
<body bgcolor="#FFFFFF" text="#000000">
<div class="moz-cite-prefix">On 07/31/2015 03:15 PM, Jamie Bullock
wrote:<br>
</div>
<blockquote cite="mid:etPan.55bbc96a.7bc2af83.9ae9@aluminium.local"
type="cite">
<style>body{font-family:Helvetica,Arial;font-size:13px}</style>
<div id="bloop_customfont"
style="font-family:Helvetica,Arial;font-size:13px; color:
rgba(0,0,0,1.0); margin: 0px; line-height: auto;"><br>
</div>
<p class="airmail_on" style="color:#000;">On 31 July 2015 at
19:40:32, IOhannes m zmölnig (<a moz-do-not-send="true"
href="mailto:zmoelnig@iem.at">zmoelnig@iem.at</a>) wrote:</p>
<div>
<blockquote type="cite" class="clean_bq" style="color: rgb(0, 0,
0); font-family: Helvetica, Arial; font-size: 13px;
font-style: normal; font-variant: normal; font-weight: normal;
letter-spacing: normal; line-height: normal; orphans: auto;
text-align: start; text-indent: 0px; text-transform: none;
white-space: normal; widows: auto; word-spacing: 0px;
-webkit-text-stroke-width: 0px;"><span>
<div>
<div>On 07/31/2015 04:36 AM, Chris McCormick wrote:<span
class="Apple-converted-space"> </span><br>
> On 30/07/15 17:05, IOhannes m zmoelnig wrote:<span
class="Apple-converted-space"> </span><br>
>> in any case, i thought that it might be better
to really allow the devs<span
class="Apple-converted-space"> </span><br>
>> themselves to pick *any* hoster they prefer, be
it your own gitlab<span class="Apple-converted-space"> </span><br>
>> instance, OSUOSL, github, or even sf.<span
class="Apple-converted-space"> </span><br>
><span class="Apple-converted-space"> </span><br>
> The good thing about this is we don't even need to
"allow" anybody to do<span class="Apple-converted-space"> </span><br>
> anything. As Roman showed, anybody can take the
initiative and start<span class="Apple-converted-space"> </span><br>
> maintaining the externals they like at this very
moment.<span class="Apple-converted-space"> </span><br>
<br>
well, everybody was always free to do that.<span
class="Apple-converted-space"> </span><br>
so i probably shouldn't have used "allow".<span
class="Apple-converted-space"> </span><br>
<br>
what i'm really interested in (and which is why i put
work into it), is<span class="Apple-converted-space"> </span><br>
a coordinated transition that would allow [sic!] anybody
who is<span class="Apple-converted-space"> </span><br>
interested in taking part in the development process (or
just interested<span class="Apple-converted-space"> </span><br>
in getting the latest and greatest sources of a given
external) to find<span class="Apple-converted-space"> </span><br>
what they are looking for.<span
class="Apple-converted-space"> </span><br>
<br>
traditionally this was rather easy: Pd had a single
repository where<span class="Apple-converted-space"> </span><br>
virtually all (FLOSS) libraries were aggragated. most
were actively<span class="Apple-converted-space"> </span><br>
developed in that SVN (a few were regularily imported
from whatever<span class="Apple-converted-space"> </span><br>
their upstream used).<span class="Apple-converted-space"> </span><br>
so if you were interested in "what's going on in Pd
land", then you<span class="Apple-converted-space"> </span><br>
would just need to check out that repository.<span
class="Apple-converted-space"> </span><br>
<br>
when switching away from sf/svn we might lose this
feature.<span class="Apple-converted-space"> </span><br>
did you know that i forked iemnet onto github a while
ago?<span class="Apple-converted-space"> </span><br>
having s-abstractions hosted on gitlab.mccormick.com is
nice, but how<span class="Apple-converted-space"> </span><br>
will anybody ever stumble (serendipitously) upon that?<span
class="Apple-converted-space"> </span></div>
</div>
</span></blockquote>
</div>
<p>How about: authors / maintainers can host their externals
wherever they like, but we maintain a “meta” repository on
GitHub that includes all the various external [sic] repositories
as git submodules…?</p>
</blockquote>
<br>
And why do you prefer Github to Sourceforge? What's different
enough in their business model that there is no inherent conflict
between serving the free software<br>
community on the one hand and monetizing their users/userdata on the
other?<br>
<br>
-Jonathan<br>
</body>
</html>