<div dir="ltr"><div dir="ltr"><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Hi DelazJ</div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Tue, Apr 11, 2023 at 9:49 AM DelazJ via QGIS-PSC <<a href="mailto:qgis-psc@lists.osgeo.org">qgis-psc@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"><div dir="ltr"><div>Hi all,</div><div><br></div><div>I find Sandro's request for an accurate statement for identifying people that can make nominations quite valid and had expressed the same concern to Marco just after he sent the call. Not about git repositories. About Transifex.</div><div><br></div><div>Speaking of Transifex, I find the wording "<span style="font-family:Roboto,sans-serif;color:rgb(0,0,0);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap">with <b>write access in transifex</b> are eligible" even more confusing. The "low" level of contributor in Transifex is "translator" and that person necessarily has write access to QGIS strings and the changes he/she does is directly pulled to QGIS repository (considering we do not have specific review process at project level). They are around 2400 subscribed translators (see screenshot). Does the previous statement refer to them? No opinion myself, just asking for clarification (for later calls and know to what extent I can forward the call to "my" committers).</span></div></div></blockquote><div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">From my understanding and memory of the original discussions, yes. The intent was to acknowledge everyone involved in the creation of QGIS with some sense of agency in who the voting members of the project are. (I had now idea there are so many contributing translators now! Do you have a sense that they are all genuine contributors?).</div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><span style="font-family:Roboto,sans-serif;color:rgb(0,0,0);font-variant-numeric:normal;font-variant-east-asian:normal;vertical-align:baseline;white-space:pre-wrap"><br></span></div><div>Back to git repository "issue", next to the guys with write access to the official repos, we also have teams of bug triagers (adding labels, doing first tests and providing/asking feedback). Depending (or not) on what transifex write access means, maybe should we consider them as eligible to make nominations also... (unless it is already the case?)</div><div><br></div></div></blockquote><div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">If you think the criteria should be changed, probably just raise a motion for the AGM, including these additional contributor types does not seem unreasonable to me.</div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div></div><div>PS: I don't think this wording "issue" is something new. We have always used that so I'm not expecting it to be solved for this round.</div></div></blockquote><div><br></div><div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Thanks for your inputs Sandro and Harrisou.</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Regards</div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small"><br></div><div class="gmail_default" style="font-family:arial,helvetica,sans-serif;font-size:small">Tim</div><br></div><div> </div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex"><div dir="ltr"><div><br></div><div>Kind regards,</div><div>Harrissou<br></div></div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">Le sam. 8 avr. 2023 à 21:16, Sandro Santilli via QGIS-PSC <<a href="mailto:qgis-psc@lists.osgeo.org" target="_blank">qgis-psc@lists.osgeo.org</a>> a écrit :<br></div><blockquote class="gmail_quote" style="margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);padding-left:1ex">On Sat, Apr 08, 2023 at 04:02:18PM +0100, Tim Sutton via QGIS-PSC wrote:<br>
<br>
> Right, but the wording is clear - you need to have rights to commit into an<br>
> official QGIS Git repository<br>
<br>
Nobody really "commits" into any official QGIS git repository.<br>
What people with write access to it do is "push" commits into it.<br>
<br>
> This list of who has commit rights<br>
> would be obtained by looking in the GitHub settings for each repository<br>
> that is hosted under <a href="https://github.com/qgis" rel="noreferrer" target="_blank">https://github.com/qgis</a><br>
<br>
Would it be the "QGIS Developers" team ?<br>
<br>
<a href="https://github.com/orgs/qgis/teams/qgis-developers" rel="noreferrer" target="_blank">https://github.com/orgs/qgis/teams/qgis-developers</a><br>
<br>
That team (which is non-public) currently lists 39 people<br>
(compared to the 400+ "committers" of the QGIS git repository).<br>
<br>
The privilege people in that team have is reported by GitHub<br>
as being "write" (not "commit"):<br>
<br>
<a href="https://github.com/orgs/qgis/teams/qgis-developers/repositories" rel="noreferrer" target="_blank">https://github.com/orgs/qgis/teams/qgis-developers/repositories</a><br>
<br>
Of course at this point in time we can all understand "committer" as<br>
we are all coming from SVN times, but git-native people may be really<br>
puzzled about that wording.<br>
<br>
<br>
--strk;<br>
_______________________________________________<br>
QGIS-PSC mailing list<br>
<a href="mailto:QGIS-PSC@lists.osgeo.org" target="_blank">QGIS-PSC@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-psc</a><br>
</blockquote></div>
_______________________________________________<br>
QGIS-PSC mailing list<br>
<a href="mailto:QGIS-PSC@lists.osgeo.org" target="_blank">QGIS-PSC@lists.osgeo.org</a><br>
<a href="https://lists.osgeo.org/mailman/listinfo/qgis-psc" rel="noreferrer" target="_blank">https://lists.osgeo.org/mailman/listinfo/qgis-psc</a><br>
</blockquote></div><br clear="all"><div><br></div><span class="gmail_signature_prefix">-- </span><br><div dir="ltr" class="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div style="text-align:center">------------------------------------------------------------------------------------------</div><div style="text-align:center"><div style="color:rgb(0,0,0);font-family:arial,helvetica,sans-serif;font-size:small;display:inline"><img src="https://kartoza.com/files/KartozaNewLogoThumbnail.jpg" width="96" height="75"></div><br></div><div style="text-align:center">Tim Sutton</div><div style="text-align:center">Kartoza Co-Founder</div><div style="text-align:center"><span style="text-align:start">Visit </span><a href="http://kartoza.com/" style="text-align:start" target="_blank">http://kartoza.com</a><span style="text-align:start"> to find out about open source:</span><br style="text-align:start"><span style="text-align:start"> * Desktop GIS programming services</span><br style="text-align:start"><span style="text-align:start"> * Geospatial web development</span></div><div style="text-align:center"><span style="text-align:start">* GIS Training</span></div><div style="text-align:center"><span style="text-align:start">* Consulting Services</span></div><div style="text-align:center"><div style="text-align:center"></div><div style="text-align:start"><div style="text-align:center">Tim is a member of the QGIS Project Steering Committee</div><div style="text-align:center">-------------------------------------------------------------------------------------------</div></div></div></div></div></div></div></div>