<div dir="ltr">Hi,<div><br></div><div>All members of the TC & OC have been invited to be members of the Robocup-SSL github organization. In addition, The current TC chair, and I from the Execs, are owners, and can make further membership changes.</div><div>Past TC and OC members who were in the github Robocup-SSL organization remain as members.</div><div><br></div><div>For ssl-vision, there are 20 additional members, who are not TC or OC members. </div><div><br></div><div>-Joydeep</div><div class="gmail_extra"><br clear="all"><div><div class="m_-863727809977791168gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div style="font-size:small"><u> </u></div><div style="font-size:small"><br></div><div style="font-size:small">Joydeep Biswas<br></div><div style="font-size:small">Assistant Professor</div><div style="font-size:small">College of Information and Computer Sciences</div><div style="font-size:small">University of Massachusetts Amherst</div><div style="font-size:small">Amherst, MA 01003</div><div><br></div></div></div></div>
<br><div class="gmail_quote">On Sat, Oct 15, 2016 at 12:10 PM, Christopher Head <span dir="ltr"><<a href="mailto:chead@chead.ca" target="_blank">chead@chead.ca</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><span>On Sat, 15 Oct 2016 16:16:15 +0200<br>
Andre Ryll <andre@ryll.cc> wrote:<br>
<br>
> Since the creation of these pull-requests there were no comments, no<br>
> actions have been taken by the SSL-Vision maintainers. To address<br>
> this issue, I would like to offer my support for maintaining the<br>
> SSL-Vision. It would be great if one of the current maintainers can<br>
> grant me write access to the vision repo (username asctec-andre).<br>
> Then I can check/test the pull-requests and eventually address other<br>
> open issues as well.<br>
<br>
</span>Hi Andre,<br>
I technically have the ability to add people as committers to the<br>
SSL-Vision repositories individually on a per-repository bases.<br>
However, the proper way to handle this is that all the committee members<br>
for the year should be members of the RoboCup-SSL GitHub organization,<br>
which gives them write access to all the repositories under that<br>
namespace automatically. I am not sure if all the committee members<br>
*are* currently members of that organization (the committees haven’t<br>
created the 2017 Organization page on the RoboCup wiki so I don’t have<br>
the list of people on hand). I also don’t have access to add people to<br>
the organization; only Joydeep and Stefan Zikler can do that. That power<br>
should probably lie with all the execs, but again, that’s not something<br>
I can fix.<br>
<br>
I will take a look and maybe comment on the PRs, though, as that's<br>
something anyone can (and should) do.<br>
<br>
Committees/execs, could someone check the organization ownership?<br>
<span class="m_-863727809977791168HOEnZb"><font color="#888888">--<br>
Christopher Head<br>
</font></span><br>______________________________<wbr>_________________<br>
robocup-small mailing list<br>
<a href="mailto:robocup-small@cc.gatech.edu" target="_blank">robocup-small@cc.gatech.edu</a><br>
<a href="https://mailman.cc.gatech.edu/mailman/listinfo/robocup-small" rel="noreferrer" target="_blank">https://mailman.cc.gatech.edu/<wbr>mailman/listinfo/robocup-small</a><br>
<br></blockquote></div><br></div></div>