<!DOCTYPE html>
<html>
<head>
<meta http-equiv="Content-Type" content="text/html; charset=UTF-8">
</head>
<body>
<p>FYI I see this thread referencing the GDAL github team
organization. As far as I know, nobody has "designed" it with deep
thoughts. It has the current structure most likely as an accident
of history... If I were to design it, I would keep it simple and
stupid. With git workflows, the concept of "committer" as in SVN
era is kinda irrelevant. You just need a sufficient number of
people with appropriate push rights to merge the flow of incoming
PRs, but if you have more than 10 people with push rights in a
single repo, that is already quite big. My 2 cents, and running
away as I've no idea how the GRASS team works ;-)<br>
</p>
<div class="moz-cite-prefix">Le 13/03/2024 à 01:35, Vaclav Petras
via grass-dev a écrit :<br>
</div>
<blockquote type="cite"
cite="mid:CABo5uVsRRUYqt=WEAcY=+M54LjKx638bDrcMnjaD+4Rm+3-aLg@mail.gmail.com">
<div dir="ltr">
<div dir="ltr"><br>
</div>
<br>
<div class="gmail_quote">
<div dir="ltr" class="gmail_attr">On Fri, 8 Mar 2024 at 09:10,
Ondřej Pešek <<a href="mailto:pesej.ondrek@gmail.com"
moz-do-not-send="true" class="moz-txt-link-freetext">pesej.ondrek@gmail.com</a>>
wrote:<br>
</div>
<blockquote class="gmail_quote"><br>
@Vaclav: Do you have some more points against the
master-children<br>
schema? It seems that the general agreement is *for* the
restructuring<br>
into parent and children teams. So far the only point
against was "I<br>
didn't find team nesting particularly useful and we already
had a<br>
couple of top-level teams."</blockquote>
<div><br>
</div>
<div>...and I didn't see it working for GDAL with people both
in the parent team and child teams and repos being assigned
to both levels.</div>
<div><br>
</div>
<div>How do you suggest we do it? Empty parent team without
repos? Would that look good?<br>
</div>
<div> </div>
<blockquote class="gmail_quote"> Although I appreciate all the
work you<br>
dedicate to the GitHub management, I don't think that this
is a valid<br>
point against when compared to the positive ones (although
it's<br>
understandable that nobody wants to drop something that they
have just<br>
created).<br>
</blockquote>
<div><br>
</div>
<div>Thanks. It is more that before it was a high priority for
me to get access rights in order (access rights to
individuals both directly and through teams, inactive people
from 2000s and early 2010s grandfathered into GitHub write
access, ...). These parent-child teams are low priority
compared to that.</div>
</div>
</div>
<br>
<fieldset class="moz-mime-attachment-header"></fieldset>
<pre class="moz-quote-pre" wrap="">_______________________________________________
grass-dev mailing list
<a class="moz-txt-link-abbreviated" href="mailto:grass-dev@lists.osgeo.org">grass-dev@lists.osgeo.org</a>
<a class="moz-txt-link-freetext" href="https://lists.osgeo.org/mailman/listinfo/grass-dev">https://lists.osgeo.org/mailman/listinfo/grass-dev</a>
</pre>
</blockquote>
<pre class="moz-signature" cols="72">--
<a class="moz-txt-link-freetext" href="http://www.spatialys.com">http://www.spatialys.com</a>
My software is free, but my time generally not.</pre>
</body>
</html>