<div dir="ltr"><div>Ondrej,</div><div><br></div><div>I agree with you that there are too many teams for GRASS [1] and they should be consolidated (or not, but at least moved) as child teams.<br></div><div><br></div><div>Do we still need these subversion teams?<br></div><div><div>* <a id="gmail-team-grass-subversion-committers" class="gmail-lh-condensed gmail-f4" href="https://github.com/orgs/OSGeo/teams/grass-subversion-committers"><span class="gmail-css-truncate-target gmail-nested-team-name">grass-subversion-committers</span></a>

          <span class="gmail-d-block">GRASS GIS Subversion committers</span></div><div></div></div><div>* <a id="gmail-team-grass-addons-subversion-committers" class="gmail-lh-condensed gmail-f4" href="https://github.com/orgs/OSGeo/teams/grass-addons-subversion-committers"><span class="gmail-css-truncate-target gmail-nested-team-name">grass-addons-subversion-committers</span></a>

          <span class="gmail-d-block">GRASS GIS Addons Subversion committers</span>
      </div><div><span class="gmail-css-truncate-target gmail-nested-team-name"><br></span></div><div><span class="gmail-css-truncate-target gmail-nested-team-name">How is this team different from the above grass-addons-subversion-committers?<br></span></div><div><span class="gmail-css-truncate-target gmail-nested-team-name">* </span><a id="gmail-team-grass-addons-write" class="gmail-lh-condensed gmail-f4" href="https://github.com/orgs/OSGeo/teams/grass-addons-write"><span class="gmail-css-truncate-target gmail-nested-team-name">grass-addons-write</span></a>

          <span class="gmail-d-block">Maintainers of tools in GRASS GIS Addons with write access to the repository</span></div><div><span class="gmail-d-block"><br></span></div><div><span class="gmail-d-block">How are these three teams different?<br></span></div><div>*<span class="gmail-css-truncate-target gmail-nested-team-name"> </span><a id="gmail-team-grass-admin" class="gmail-lh-condensed gmail-f4" href="https://github.com/orgs/OSGeo/teams/grass-admin"><span class="gmail-css-truncate-target gmail-nested-team-name">grass-admin</span></a>

          <span class="gmail-d-block">GRASS GIS repo administration team</span></div><div>* <a id="gmail-team-grass-maintain" class="gmail-lh-condensed gmail-f4" href="https://github.com/orgs/OSGeo/teams/grass-maintain"><span class="gmail-css-truncate-target gmail-nested-team-name">grass-maintain</span></a>

          <span class="gmail-d-block">GRASS GIS repo settings maintenance team</span></div><div></div><div>* <a id="gmail-team-grass-write" class="gmail-lh-condensed gmail-f4" href="https://github.com/orgs/OSGeo/teams/grass-write"><span class="gmail-css-truncate-target gmail-nested-team-name">grass-write</span></a>

          <span class="gmail-d-block">Maintainers of GRASS GIS with write access to the main repository</span> <br></div><div><br></div><div>I think we need this team.<br></div>* <a id="gmail-team-grass-docker-homebrew-users" class="gmail-lh-condensed gmail-f4" href="https://github.com/orgs/OSGeo/teams/grass-docker-homebrew-users"><span class="gmail-css-truncate-target gmail-nested-team-name">grass-docker-homebrew-users</span></a>

          <span class="gmail-d-block">Users for automated dockerhub and homebrew builds</span><div><br></div><div>I believe we can consolidate these two teams.<br></div><div>* <a id="gmail-team-grass-promo-write" class="gmail-lh-condensed gmail-f4" href="https://github.com/orgs/OSGeo/teams/grass-promo-write"><span class="gmail-css-truncate-target gmail-nested-team-name">grass-promo-write</span></a>

          <span class="gmail-d-block">Contributors to GRASS GIS promo repo with write access</span></div><div><div>* <a id="gmail-team-grass-website-write" class="gmail-lh-condensed gmail-f4" href="https://github.com/orgs/OSGeo/teams/grass-website-write"><span class="gmail-css-truncate-target gmail-nested-team-name">grass-website-write</span></a>

          <span class="gmail-d-block">Maintainers of GRASS GIS website</span></div><div><br></div><div>What about these two?<br></div><div><div>* <a id="gmail-team-grass-discussion-moderators" class="gmail-lh-condensed gmail-f4" href="https://github.com/orgs/OSGeo/teams/grass-discussion-moderators"><span class="gmail-css-truncate-target gmail-nested-team-name">grass-discussion-moderators</span></a>

          <span class="gmail-d-block">Discussion moderators with general Triage access</span></div><div></div></div>* <a id="gmail-team-grass-triage" class="gmail-lh-condensed gmail-f4" href="https://github.com/orgs/OSGeo/teams/grass-triage"><span class="gmail-css-truncate-target gmail-nested-team-name">grass-triage</span></a>

          <span class="gmail-d-block">Contributors with PR and issue triage power</span></div><div><br></div><div>Best,</div><div>Huidae</div><div><br></div><div>[1] <a href="https://github.com/orgs/OSGeo/teams">https://github.com/orgs/OSGeo/teams</a></div><div></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Feb 22, 2024 at 1:35 AM OndÅ™ej PeÅ¡ek via grass-dev <<a href="mailto:grass-dev@lists.osgeo.org">grass-dev@lists.osgeo.org</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">Sweet devs,<br>
<br>
Looking at the GitHub teams within the OSGeo organisation [1], it is<br>
impossible not to notice the fact that the GRASS people are very good<br>
in making themselves visible through visual weed infestation. On one<br>
side, it is nice to see GRASS all over the dance floor; on the other<br>
one, I don't find it particularly polite to storm the org and see that<br>
GRASS owns 11 OSGEO's teams out of 24 in the overview (11 out of 26 in<br>
total).<br>
<br>
Wouldn't it be better to follow the example of GDAL instead? Creating<br>
only one master team (grass) and then 11 child teams (grass-write,<br>
grass-addons-write, ...)? It would make the org team overview much<br>
cleaner. Also, you could see all grass child teams' members in one<br>
place.<br>
<br>
In the name of New GitHub Order,<br>
Ondrej<br>
<br>
PS: I also believe that we should reduce the number of GRASS teams and<br>
consolidate some (grass-addons-subversion-committers -><br>
grass-addons-write) but I guess this is for another and much more<br>
contentious discussion.<br>
_______________________________________________<br>
grass-dev mailing list<br>
<a href="mailto:grass-dev@lists.osgeo.org" target="_blank">grass-dev@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/grass-dev" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/grass-dev</a><br>
</blockquote></div><br clear="all"><br><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><span><div><div dir="ltr">Huidae Cho, Ph.D., GISP, /<a href="http://ipa-reader.xyz/?text=hid%C9%9B" target="_blank">hidÉ›</a> tÍ¡É•o/, ì¡°í¬ëŒ€, æ›ºå–œå¤§</div><div dir="ltr">GRASS GIS Developer</div><div><a href="https://idea.isnew.info/" target="_blank">https://idea.isnew.info/</a><br></div></div></span></div></div></div></div></div></div></div></div></div></div>