<div dir="auto"><span style="word-spacing:1px;border-color:rgb(49,49,49);color:rgb(49,49,49)">Hello </span><br style="color:rgb(49,49,49);word-spacing:1px"><br style="color:rgb(49,49,49);word-spacing:1px"><span style="word-spacing:1px;border-color:rgb(49,49,49);color:rgb(49,49,49)">I'm Atheer, a PhD student in AI from Iraq, I would like to join the team although my software knowledge is high level, how can I help?</span><br style="color:rgb(49,49,49);word-spacing:1px"><br style="color:rgb(49,49,49);word-spacing:1px"><span style="word-spacing:1px;border-color:rgb(49,49,49);color:rgb(49,49,49)">Greetings</span><br></div><div><br><div class="gmail_quote"><div dir="ltr" class="gmail_attr">On Thu, Oct 6, 2022 at 1:03 PM Ankur Sinha <<a href="mailto:sanjay.ankur@gmail.com">sanjay.ankur@gmail.com</a>> wrote:<br></div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Dear all,<br>
<br>
As discussed in the last monthly meeting, we would like to set up a<br>
task force to work on delivering the first version the software<br>
development guidelines/best practices.<br>
<br>
<a href="https://ocns.github.io/SoftwareWG/2022/09/27/wg-meeting-19-september-2022.html" rel="noreferrer" target="_blank">https://ocns.github.io/SoftwareWG/2022/09/27/wg-meeting-19-september-2022.html</a><br>
<br>
Context<br>
--------<br>
<br>
Computational neuroscience, and neuroscience in general, is extremely<br>
multi-disciplinary. We are a mix of physicists, mathematicians,<br>
biologists, chemists, engineers, computer scientists and more. Not all<br>
these sectors receive formal training on software development---a lot of<br>
us just learn what we need "on the job".<br>
<br>
Usually, this means that folks are not aware of the best/suggested<br>
software development best practices. This tends to result in "code<br>
smell"[1] which leads to all sorts of general issues that the general<br>
scientific community worries about, e.g.:<br>
<br>
- code not being openly shared: if people perceive their code to be "not<br>
well written", they are less likely to share it openly<br>
- unmaintained code: sometime after the code was shared/published, it is<br>
already outdated/unmaintained and requires lots of work to<br>
re-run/re-use<br>
- reproducibility issues: does not reproduce the same results when run<br>
on different environments/platforms<br>
<br>
So the goal here is to come up with a simple set of rules/do's and<br>
don'ts/shoulds and musts that the community can use as a reference.<br>
<br>
Please see this ticket for more information and discussion:<br>
<a href="https://github.com/OCNS/SoftwareWG/issues/113" rel="noreferrer" target="_blank">https://github.com/OCNS/SoftwareWG/issues/113</a><br>
<br>
Join the task force<br>
-------------------<br>
<br>
Task forces are temporary teams that come together for the duration of a<br>
project. Task forces work autonomously to deliver the goals/requirements<br>
of the project. They decide when they meet, and how they work, and what<br>
specific tasks/steps they take.<br>
<br>
To join a task force, one must commit to spending time (a few hours a<br>
week) on the activities of the task force:<br>
<br>
- to work on the project related tasks that you are responsible for<br>
- to regularly attend the meetings of the task force (frequency/time<br>
etc. to be decided by the task force itself)<br>
<br>
Please comment on this ticket to let us know if you would like to join<br>
this task force:<br>
<br>
<a href="https://github.com/OCNS/SoftwareWG/issues/116" rel="noreferrer" target="_blank">https://github.com/OCNS/SoftwareWG/issues/116</a><br>
<br>
Why should you join the task force?<br>
------------------------------------<br>
<br>
There are lots of benefits of joining task forces. Here's an incomplete<br>
list:<br>
<br>
- form and strengthen connections with others in the research community<br>
- gain and exchange in-depth knowledge on the project and related subjects<br>
- have an extra, smaller, project to work on and gain regular positive<br>
reinforcement from (very useful for days when our primary projects are<br>
going slow or not going anywhere at all)<br>
<br>
Projects may also lead to short papers, although that is for<br>
the task force to decide.<br>
<br>
Finally, all of this contributes to a stronger professional profile.<br>
<br>
So, we'd really encourage everyone to please strongly consider<br>
participating in the task force.<br>
<br>
[1] <a href="https://en.wikipedia.org/wiki/Code_smell" rel="noreferrer" target="_blank">https://en.wikipedia.org/wiki/Code_smell</a><br>
<br>
-- <br>
Thanks,<br>
Regards,<br>
Ankur Sinha (He / Him / His) | <a href="https://ankursinha.in" rel="noreferrer" target="_blank">https://ankursinha.in</a><br>
Research Fellow at the Silver Lab, University College London | <a href="http://silverlab.org/Free/Open" rel="noreferrer" target="_blank">http://silverlab.org/<br>
Free/Open</a> source community volunteer at the NeuroFedora project | <a href="https://neuro.fedoraproject.org" rel="noreferrer" target="_blank">https://neuro.fedoraproject.org</a><br>
Time zone: Europe/London<br>
-- <br>
Incf-ocns-software-wg mailing list<br>
<a href="mailto:Incf-ocns-software-wg@incf.org" target="_blank">Incf-ocns-software-wg@incf.org</a><br>
<a href="https://lists.incf.org/cgi-bin/mailman/listinfo/incf-ocns-software-wg" rel="noreferrer" target="_blank">https://lists.incf.org/cgi-bin/mailman/listinfo/incf-ocns-software-wg</a><br>
</blockquote></div></div>-- <br><div dir="ltr" class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div dir="ltr"><div><span style="color:rgb(11,83,148)"><b><span style="color:rgb(204,0,0)">ATHEER HADI ISSA AL-RAMMAHI</span><br></b></span></div><div><span style="color:rgb(11,83,148)"><b>University of Al-Qadisiyah</b></span></div><div><b style="color:rgb(11,83,148)">Iraq</b><br></div><div><span style="color:rgb(11,83,148)"><b><br></b></span></div><br><br></div></div></div>