<html><head></head><body>+1<br><br>Moritz<br><br><div class="gmail_quote">Am 20. Januar 2019 00:44:35 MEZ schrieb Markus Neteler <neteler@osgeo.org>:<blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
<pre class="k9mail">Dear PSC,<br><br>please vote (in a timely manner) on granting GRASS-core write access<br>to Ondřej Pešek:<br><br>On Sat, Jan 12, 2019 at 8:53 PM Markus Neteler <neteler@osgeo.org> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">On Thu, Jan 10, 2019 at 11:37 AM Ondřej Pešek <pesej.ondrek@gmail.com> wrote:<br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"> Dear GRASS,<br><br> I already have the access to GRASS addons repository (mainly because of my master's thesis [1]), but with my Ph.D. supervisor Martin Landa we decided that it might be useful to have the access also to normal trunk. Now, I mostly work on the modeler (parameterization in the Python export [2], which should be followed by still-not-finished PyWPS export [3] - but before this one, we should wait for one GRASS-related fix in PyWPS) and I test some python3 functionalities with my ANN AddOns.<br><br> I have read and accepted the legal aspects of code contributions (RFC2).<br><br> My osgeo_id is "pesekon2".<br><br> Many thanks for considering my request,<br><br> Kind regards,<br><br> Ondrej Pesek<br><br> [1] <a href="https://trac.osgeo.org/grass/browser/grass-addons/grass7/imagery/i.ann.maskrcnn">https://trac.osgeo.org/grass/browser/grass-addons/grass7/imagery/i.ann.maskrcnn</a><br> [2] <a href="https://trac.osgeo.org/grass/ticket/3669">https://trac.osgeo.org/grass/ticket/3669</a><br> [3] <a href="https://github.com/ctu-yfsg/2017-d-grass-modeler-pywps">https://github.com/ctu-yfsg/2017-d-grass-modeler-pywps</a><br></blockquote> Thanks for your request!<br><br> According to RFC1 [1] and "HowToContribute" [2] we need to vote for a<br> new core developer [3].<br> I have added this topic to the PSC Agenda [4].<br><br> Motion timeline:<br> - proposal published: 12 Jan 2019<br> - voting to be opened on 19 Jan 2019<br></blockquote><br>I start with a<br>+1<br><br>Markus<br><br><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;">[1] <a href="https://trac.osgeo.org/grass/wiki/RFC/1_ProjectSteeringCommitteeGuidelines">https://trac.osgeo.org/grass/wiki/RFC/1_ProjectSteeringCommitteeGuidelines</a><br>[2] <a href="https://trac.osgeo.org/grass/wiki/HowToContribute#WriteaccesstotheMainGRASS-SVNrepository">https://trac.osgeo.org/grass/wiki/HowToContribute#WriteaccesstotheMainGRASS-SVNrepository</a><br>[3] <a href="https://trac.osgeo.org/grass/wiki/RFC/3_PSCVotingProcedures">https://trac.osgeo.org/grass/wiki/RFC/3_PSCVotingProcedures</a><br>[4] <a href="https://trac.osgeo.org/grass/wiki/PSC/Agenda">https://trac.osgeo.org/grass/wiki/PSC/Agenda</a><br></blockquote><hr>grass-psc mailing list<br>grass-psc@lists.osgeo.org<br><a href="https://lists.osgeo.org/mailman/listinfo/grass-psc">https://lists.osgeo.org/mailman/listinfo/grass-psc</a></pre></blockquote></div></body></html>