<html><body><div style="font-family: arial, helvetica, sans-serif; font-size: 10pt; color: #000000"><div>Hei,<br></div><div><br data-mce-bogus="1"></div><div>Some comments to the process outlined below. I think this is indeed how it works in practice.<br data-mce-bogus="1"></div><div><br data-mce-bogus="1"></div><hr id="zwchr" data-marker="__DIVIDER__"><div data-marker="__HEADERS__"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><b>From: </b>"Joakim Nivre" <joakim.nivre@lingfil.uu.se><br><b>To: </b>"Stephan Oepen" <oe@ifi.uio.no><br><b>Cc: </b>"infrastructure" <infrastructure@nlpl.eu>, "board" <board@nlpl.eu><br><b>Sent: </b>Tuesday, 17 October, 2017 22:58:45<br><b>Subject: </b>Re: [NLPL Task Force (A)] [NLPL Team] news on our technical infrastructure<br></blockquote></div><div data-marker="__QUOTED_TEXT__"><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;">
Thanks, Stephan. Here is an attempt to follow your proposed procedure for adding Aaron Smith as a team member.
<div class=""><br class=""><div><blockquote class=""><div class=""><div class="">(0) the ‘team’ mailing list and personnel summary at<br class=""><br class=""><a href="https://wiki.neic.no/wiki/Nordic_language_processing_laboratory#Project_Personnel" class="" target="_blank">https://wiki.neic.no/wiki/Nordic_language_processing_laboratory#Project_Personnel</a><br class=""><br class="">
bjørn is the maintainer of both of these, so maybe start by announcing<br class="">
a new team member to him and the ‘infrastructure’ task force: we will<br class="">
probably need the full name, email address, and maybe the anticipated<br class="">
duration of involvement.<br class=""></div></div></blockquote><div><br class=""></div>
Full name: Aaron Smith</div><div>Email: <a href="mailto:aaron.smith@lingfil.uu.se" class="" target="_blank">aaron.smith@lingfil.uu.se</a><br data-mce-bogus="1"></div><div>Duration: until the end of the project</div><div><br class=""><blockquote class=""><div class=""><div class="">(1) accounts on Abel and Taito and membership in the various project<br class="">
groups that control usage of cpu hours and, optionally, write access<br class="">
to the NLPL project directories. either way, the first step to<br class="">
obtaining access should be along these lines:<br class=""><br class=""><a href="http://wiki.nlpl.eu/index.php/Infrastructure/resources" class="" target="_blank">http://wiki.nlpl.eu/index.php/Infrastructure/resources</a><br class=""><br class="">
not sure who controls the uppsala Taito project group—is that martin<br class="">
or you?</div></div></blockquote></div></div></blockquote><div>On Taito each PI controls his own project, since /proj/nlpl is linked to Stephan's project he in fact controls write access via group membership there, as he mentions below.<br></div><div><br data-mce-bogus="1"></div><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div class=""><div><blockquote class=""><div class=""><div class=""> probably the above instructions should ask that new users<br class="">
coordinate with their NLPL site manager about gaining access to Taito,<br class="">
i.e. you in the UU case.</div></div></blockquote></div></div></blockquote>Yes, access to Taito can be gained via existing PIs, my understanding is that in Abel this is defacto only Stephan.<br><div><br></div><blockquote style="border-left:2px solid #1010FF;margin-left:5px;padding-left:5px;color:#000;font-weight:normal;font-style:normal;text-decoration:none;font-family:Helvetica,Arial,sans-serif;font-size:12pt;"><div class=""><div><blockquote class=""><div class=""><div class=""><br class="">
for the latter two groups (write access to the project directories on<br class="">
Abel and Taito), i am the one to add new users to these groups, both<br class="">
on Abel and Taito. i suggest the emails from step (0) above include<br class="">
an optional statement about expected involvement in software<br class="">
installations and, if so, for which of the two HPC systems.<br class=""></div></div></blockquote><div><br class=""></div>
Aaron already has accounts on Abel and Taito, but he needs to be given write access at least on Abel, because he is going to work on installing things for Activity C. </div><div><br class=""><blockquote class=""><div class=""><div class="">(2) write access to the NLPL wiki (which we are taking into active use<br class="">
these days; instructions to come to ‘team’ shortly). bjørn and i have<br class="">
administrator rights on the wiki, so i would suggest that bjørn<br class="">
remembers to generate new wiki accounts at the same time as he adds<br class="">
new members to the ‘team’ list.<br class=""><br class="">
bjørn (and martin and joerg), does the above sound feasible? maybe i<br class="">
am overlooking some additional records that need to be maintained?<br class="">
either way, we should sooner or later spell out the procedures for new<br class="">
users on the wiki :-).</div></div></blockquote></div></div></blockquote>I think this sounds fine for now. As for the future I find the concentration on one PI for write access to NLPL a bit restricting, NLPL is bending the "Project" concept on both Abel and Taito. But at least this works with current workflows.</div><div data-marker="__QUOTED_TEXT__"><br data-mce-bogus="1"></div><div data-marker="__QUOTED_TEXT__">Cheers,</div><div data-marker="__QUOTED_TEXT__">Martin<br><div><br></div><br class=""></div></div></body></html>