ankursinha.in/bloghttps://ankursinha.in/2023-12-02T18:11:47+00:00neuroscience/fedora/musingsVit aliases to view tasks over different periods2023-12-02T18:11:47+00:002023-12-02T18:11:47+00:00ankurtag:ankursinha.in,2023-12-02:/2023/12/02/vit-aliases-to-view-tasks-over-different-periods.html<p class="first last">A few Vit aliases I use to get an overview of my tasks over different periods of time</p>
<p>I use <a class="reference external" href="https://github.com/vit-project/vit">Vit</a> as a terminal interface to view my <a class="reference external" href="https://taskwarrior.org/">Taskwarrior</a> tasks.
In a terminal, that's just running the <code>vit</code> command.
Sometimes, one doesn't want to look at the full list, though.
I usually have a few "views" of my tasks which give me a better idea of my work load.
I add them to my <code>~/.bashrc</code> so they're available as commands.
Here they are.
They're very simple, and should be modified to suit one's workflow:</p>
<pre class="code bash literal-block">
<span class="c1"># filters common to all functions
</span><span class="nv">TASK_FILTERS</span><span class="o">=</span><span class="s2">""</span><span class="w">
</span><span class="c1"># all tasks
</span>vit-tl<span class="w"> </span><span class="o">()</span><span class="w">
</span><span class="o">{</span><span class="w">
</span>vit<span class="w"> </span><span class="si">${</span><span class="nv">TASK_FILTERS</span><span class="si">}</span><span class="w">
</span><span class="o">}</span><span class="w">
</span><span class="c1"># tasks due before the end of the day
</span>vit-tl-today<span class="w"> </span><span class="o">()</span><span class="w"> </span><span class="o">{</span><span class="w">
</span>vit<span class="w"> </span><span class="si">${</span><span class="nv">TASK_FILTERS</span><span class="si">}</span><span class="w"> </span><span class="s1">'due.by:eod'</span><span class="w">
</span><span class="o">}</span><span class="w">
</span><span class="c1"># tasks due before the end of the week
</span>vit-tl-this-week<span class="w"> </span><span class="o">()</span><span class="w"> </span><span class="o">{</span><span class="w">
</span>vit<span class="w"> </span><span class="si">${</span><span class="nv">TASK_FILTERS</span><span class="si">}</span><span class="w"> </span><span class="s1">'due.by:eow'</span><span class="w">
</span><span class="o">}</span><span class="w">
</span><span class="c1"># tasks due before the end of the month
</span>vit-tl-this-month<span class="w"> </span><span class="o">()</span><span class="w"> </span><span class="o">{</span><span class="w">
</span>vit<span class="w"> </span><span class="si">${</span><span class="nv">TASK_FILTERS</span><span class="si">}</span><span class="w"> </span><span class="s1">'due.by:eom'</span><span class="w">
</span><span class="o">}</span><span class="w">
</span><span class="c1"># tasks due in a week
</span>vit-tl-in-a-week<span class="w"> </span><span class="o">()</span><span class="w"> </span><span class="o">{</span><span class="w">
</span>vit<span class="w"> </span><span class="si">${</span><span class="nv">TASK_FILTERS</span><span class="si">}</span><span class="w"> </span><span class="s1">'due.by:1w'</span><span class="w">
</span><span class="o">}</span><span class="w">
</span><span class="c1"># tasks due in a month
</span>vit-tl-in-a-month<span class="w"> </span><span class="o">()</span><span class="w"> </span><span class="o">{</span><span class="w">
</span>vit<span class="w"> </span><span class="si">${</span><span class="nv">TASK_FILTERS</span><span class="si">}</span><span class="w"> </span><span class="s1">'due.by:1m'</span><span class="w">
</span><span class="o">}</span><span class="w">
</span><span class="c1"># tasks due in six months
</span>vit-tl-in-six-months<span class="w"> </span><span class="o">()</span><span class="w"> </span><span class="o">{</span><span class="w">
</span>vit<span class="w"> </span><span class="si">${</span><span class="nv">TASK_FILTERS</span><span class="si">}</span><span class="w"> </span><span class="s1">'due.by:6m'</span><span class="w">
</span><span class="o">}</span><span class="w">
</span><span class="c1"># tasks due in a year
</span>vit-tl-in-a-year<span class="w"> </span><span class="o">()</span><span class="w"> </span><span class="o">{</span><span class="w">
</span>vit<span class="w"> </span><span class="si">${</span><span class="nv">TASK_FILTERS</span><span class="si">}</span><span class="w"> </span><span class="s1">'due.by:1y'</span><span class="w">
</span><span class="o">}</span><span class="w">
</span><span class="c1"># next N tasks (2 by default)
</span>vit-next<span class="w"> </span><span class="o">()</span><span class="w"> </span><span class="o">{</span><span class="w">
</span><span class="nb">echo</span><span class="w"> </span><span class="s2">"Active tasks:"</span><span class="w">
</span><span class="nb">echo</span><span class="w">
</span>task<span class="w"> </span>active<span class="w">
</span><span class="nb">echo</span><span class="w">
</span><span class="nb">echo</span><span class="w">
</span><span class="nb">echo</span><span class="w"> </span><span class="s2">"Next </span><span class="si">${</span><span class="nv">1</span><span class="k">:-</span><span class="nv">2</span><span class="si">}</span><span class="s2"> tasks:"</span><span class="w">
</span><span class="nb">echo</span><span class="w">
</span>task<span class="w"> </span><span class="si">${</span><span class="nv">TASK_FILTERS</span><span class="si">}</span><span class="w"> </span>limit:<span class="s2">"</span><span class="si">${</span><span class="nv">1</span><span class="k">:-</span><span class="nv">2</span><span class="si">}</span><span class="s2">"</span><span class="w">
</span><span class="nb">echo</span><span class="w">
</span><span class="nb">echo</span><span class="w">
</span><span class="o">}</span>
</pre>
Isolating Tmux windows to prevent systemd-oomd from killing the server2022-10-29T13:30:32+01:002022-10-31T17:22:54+00:00ankurtag:ankursinha.in,2022-10-29:/2022/10/29/isolating-tmux-windows-to-prevent-systemd-oomd-from-killing-the-server.html<p class="first last">This post documents how one can isolate different <a class="reference external" href="https://github.com/tmux/tmux/wiki">Tmux</a> windows to prevent one of them getting killed by <a class="reference external" href="https://www.freedesktop.org/software/systemd/man/systemd-oomd.html">systemd-oomd</a> from causing the whole Tmux server (and all sessions!) to also be killed.</p>
<p>I run a number of <a class="reference external" href="https://github.com/tmux/tmux/wiki">Tmux</a> sessions, one for each project or context, (via <a class="reference external" href="https://www.byobu.org/">Byobu</a>) to do my work on a daily basis.
<a class="reference external" href="https://github.com/tmux/tmux/wiki">Tmux</a> uses a client-server architecture, so there's a <a class="reference external" href="https://github.com/tmux/tmux/wiki">Tmux</a> server running that all of these sessions connect to.
Some time ago, I began noticing that all my <a class="reference external" href="https://github.com/tmux/tmux/wiki">Tmux</a> sessions were being killed while I worked.
I knew this wasn't a random occurrence.
A look at the logs told me that <a class="reference external" href="https://www.freedesktop.org/software/systemd/man/systemd-oomd.html">systemd-oomd</a> was killing my <a class="reference external" href="https://github.com/tmux/tmux/wiki">Tmux</a> server, and all my sessions and their windows with it---all my vim sessions, all of it.</p>
<p>This, of course, is far from ideal.
What's happening here is that one of the processes occupying a <a class="reference external" href="https://github.com/tmux/tmux/wiki">Tmux</a> window consumes lots of CPU/memory and <a class="reference external" href="https://www.freedesktop.org/software/systemd/man/systemd-oomd.html">systemd-oomd</a> needs to kill it.
However, <a class="reference external" href="https://www.freedesktop.org/software/systemd/man/systemd-oomd.html">systemd-oomd</a> does not work on a per-process level.
It works on a cgroup level.
So, it kills the whole cgroup, taking the <a class="reference external" href="https://github.com/tmux/tmux/wiki">Tmux</a> server down.</p>
<p>I've been looking at ways of preventing this from happening.
One option is to <a class="reference external" href="https://fedoraproject.org/wiki/User:Tuju/Disable_systemd-oomd">disable systemd-oomd</a> completely.
I think I've been fine before these OOM tools came along, but I do see the advantages of having them.
So I'd rather keep them around and configure them if possible.</p>
<p>The other, perhaps simpler, option is to somehow isolate each of my <a class="reference external" href="https://github.com/tmux/tmux/wiki">Tmux</a> windows so that they're all killed independently without affecting each other.
I looked into this latter option first.
After some <a class="reference external" href="https://ask.fedoraproject.org/t/how-would-one-create-new-tmux-servers-each-isolated-in-a-separate-slice-so-that-if-systemd-oomd-kills-one-the-other-tmux-servers-keep-living/27891/2">discussion on Ask Fedora</a>, I came up with a solution: run every <a class="reference external" href="https://github.com/tmux/tmux/wiki">Tmux</a> window in isolation using <cite>systemd-run</cite>.</p>
<p>So, when we start a new <a class="reference external" href="https://github.com/tmux/tmux/wiki">Tmux</a> session, we want to start our first window using <cite>systemd-run</cite>.
Easiest to do this using a bash function that one can put in their <cite>~/.bashrc</cite> file:</p>
<pre class="code bash literal-block">
<span class="c1"># create new session, and ensure first window runs in a separate systemd
# scope
</span>byobu-new-session<span class="w"> </span><span class="o">()</span><span class="w">
</span><span class="o">{</span><span class="w">
</span>byobu<span class="w"> </span>new<span class="w"> </span>-s<span class="w"> </span><span class="nv">$1</span><span class="w"> </span>systemd-run<span class="w"> </span>--user<span class="w"> </span>--scope<span class="w"> </span>bash<span class="w">
</span><span class="o">}</span>
</pre>
<p>Next, to open a new window in an existing session using <cite>systemd-run</cite>, we can use the <cite>new window</cite> <a class="reference external" href="https://github.com/tmux/tmux/wiki">Tmux</a> command:</p>
<pre class="code bash literal-block">
new-window<span class="w"> </span>systemd-run<span class="w"> </span>--user<span class="w"> </span>--scope<span class="w"> </span>bash
</pre>
<p>This can be bound to a keyboard shortcut:</p>
<pre class="code bash literal-block">
bind-key<span class="w"> </span>c<span class="w"> </span>new-window<span class="w"> </span>systemd-run<span class="w"> </span>--user<span class="w"> </span>--scope<span class="w"> </span>bash
</pre>
<p>That's it.
Using <cite>systemd-cgls</cite> one can see that each new <a class="reference external" href="https://github.com/tmux/tmux/wiki">Tmux</a> window starts in a new systemd scope.
To test that this now isolates each window, one can run something like <cite>tail /dev/zero</cite> to cause it to get killed by <a class="reference external" href="https://www.freedesktop.org/software/systemd/man/systemd-oomd.html">systemd-oomd</a> while leaving other windows, sessions, and the server untouched.</p>
<p>This seems to be working very well for me.
If you have a better solution, do let me know, though.</p>
<div class="section" id="edit-a-simpler-way">
<h2>Edit: a simpler way</h2>
<p>As it happens, there's a much easier way to do this.
Instead of modifying <cite>~/.bashrc</cite> and then re-binding the <cite>new-window</cite> key, all one needs to do is redefine the <cite>default-command</cite> parameter that <a class="reference external" href="https://github.com/tmux/tmux/wiki">Tmux</a> uses so that it runs the <cite>systemd-run</cite> command:</p>
<pre class="code bash literal-block">
<span class="c1"># in tmux.conf
</span>set-option<span class="w"> </span>-g<span class="w"> </span>default-command<span class="w"> </span><span class="s1">'systemd-run --user --scope bash'</span>
</pre>
</div>
Restarting regular Fedora India meetings2021-01-12T20:27:27+00:002021-01-12T20:27:27+00:00ankurtag:ankursinha.in,2021-01-12:/2021/01/12/restarting-regular-fedora-india-meetings.html<p class="first last">We're restarting regular meetings for the Fedora India community. Come join us!</p>
<center><div class="figure">
<a class="reference external image-reference" href="#"><img alt="Photo by Nikunj Gupta on Unsplash." class="img-responsive" src="https://ankursinha.in/images/20210112.jpg" style="width: 80%;" /></a>
<p class="caption">Photo by <a class="reference external" href="https://unsplash.com/@mecyborg?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Nikunj Gupta</a> on <a class="reference external" href="https://unsplash.com/s/photos/india?utm_source=unsplash&utm_medium=referral&utm_content=creditCopyText">Unsplash</a>.</p>
</div>
</center><p>The <a class="reference external" href="https://fedoraproject.org/wiki/India">Fedora India community</a> has always been quite an active group of people working in various Fedora teams and Special Interest Groups (SIGs).
At some point in recent years, people got busy with projects as we tend to do, and we stopped having regular community meetings.
This is unfortunate, since these meetings keep the community ticking, and provide a platform for new members to join in.</p>
<p>Recently, there's been interest in revitalising the Fedora India community.
We've started to clean up the mailing list, and we'd like to restart regular meetings.
We had a short first one at the end of 2020 to kick things off.
You can read the logs <a class="reference external" href="https://meetbot.fedoraproject.org/teams/fedora-india/fedora-india.2020-12-11-10.01.html">here</a>.</p>
<p>The next meeting, the first of 2021, will happen soon.
In the meantime, this is a short notice to make the community aware of these on-goings.
Please subscribe to the <a class="reference external" href="https://lists.fedoraproject.org/admin/lists/india.lists.fedoraproject.org/">mailing list</a> to keep up with the community's activities.
If it has been a while since you were active there, please feel free to send in a short introduction so newcomers can get to know you.</p>
<p>The usual chat channels are also active.
You can join #fedora-india on the Freenode IRC network <a class="reference external" href="https://webchat.freenode.net/?channels=#fedora-neuro">here</a>.
It is also bridged to the <a class="reference external" href="https://t.me/fedoraindia">@fedoraindia Telegram super group</a>.</p>
<p>We hope to see you in the channels!</p>
20200404: What I did this week2020-04-04T10:49:50+01:002020-04-04T10:49:50+01:00ankurtag:ankursinha.in,2020-04-04:/2020/04/04/20200404-what-i-did-this-week.html<p class="first last">This is what I was up to this week!</p>
<center><div class="figure align-center">
<img alt="Picture of "Report" written on a blackboard in chalk kept on a desk with a calculator, a pen, clips" class="text-center img-responsive pagination-centered" src="https://ankursinha.in/images/20200404-banner.jpg" style="width: 70%;" />
<p class="caption">"Report" by <a class="reference external" href="http://gotcredit.com">GotCredit</a> <a class="reference external" href="https://flic.kr/p/QGKX1P">on Flickr</a> (CC-BY 2.0 license)</p>
</div>
</center><p>I seem to be getting busier every day, and the only way I can seem to be able
to do all the work I want to is by staying extremely organised. An important
part of organisation is being able to look back at the work that was done, and
whether it could be done better---perhaps prioritised better---to make it all a
little more efficient. So, given that I haven't been blogging frequently over
the last year, I am trying to track the time I spend working more religiously
and write a short weekly work report. It gives me the chance to review the past
week.</p>
<p>So, in the weeks leading up to today, 4th April, this is what I have been up
to.</p>
<div class="section" id="dissertation-writing">
<h2>Dissertation writing</h2>
<p>I'm working on writing up my dissertation, at the end of my PhD now. I've made
good progress. I have another chapter or so to go before I should be able to
submit. My supervision team has been reviewing and editing individual chapters
as I finish them. We are already working on a paper, and the <a class="reference external" href="https://www.biorxiv.org/content/early/2019/10/21/810846">pre-print</a> for this had gone
through multiple rounds of review. So the chapters that came from the paper
didn't need too much work. Another chapter is based on the reports I wrote for
my assessments (back in 2015!), but having it all written down also made it
easier to edit and add to the dissertation. I am extremely glad that my
supervision team got me to maintain a <a class="reference external" href="https://github.com/sanjayankur31/calliope/issues">daily lab journal</a>. It makes writing the
dissertation so much easier.</p>
</div>
<div class="section" id="research-fellow-at-the-silver-lab-at-university-college-london">
<h2>Research fellow at the Silver Lab at University College London</h2>
<p>I was fortunate enough to secure a research fellow job at the <a class="reference external" href="http://silverlab.org/">Silver Lab</a>
while working on my dissertation. Generally, we PhD candidates submit our
dissertations and then spend a few months hunting for positions. From all
accounts, it's not meant to be an easy transition to a post-doc position. The
number of PhDs entering the job market easily outnumbers the number of
available research positions. So, I was also preparing for a few months of
unemployment---saving money primarily---while I hunted for positions after I
had submitted. In my case as an international migrant/expat/job stealer, my
employers would also have to sponsor my visa, and not all employers do that. If
I hadn't managed to find a position before my current student visa expired, I'd
have to return to India and continue applying from there. That makes it even
harder, and all the time one is not working on research, one is already falling
behind. So, transitioning on to a position while still writing up was a very
very lucky break for me.</p>
<p>The research group does a lot of experimental work, but it is also where the
<a class="reference external" href="opensourcebrain.org">Open Source Brain</a> project is based. Given my computing background, and
experience with FOSS in <a class="reference external" href="https://fedoraproject.org/wiki/User:Ankursinha">Fedora</a>, a large component of my
role is to work on the development of the <a class="reference external" href="opensourcebrain.org">Open Source Brain</a> platform, and liaise
with <a class="reference external" href="https://metacell.us/">MetaCell</a> who do most of the core development. Along with that, I get to
work on modelling and other research projects. I was looking to work in a group
that included experimentalists. I think that it is important for me to develop
as an independent researcher in neuroscience.</p>
<p>It's early days yet. I am only two weeks in, so I am still settling down. Since
I am on a <a class="reference external" href="https://www.gov.uk/tier-4-general-visa">Tier 4 student visa</a> at the moment, I can only work twenty hours a
week. That's about two days a week, and is really not enough to get a lot done,
especially given that it is meant to include the various meetings that I am to
attend. HR are working on getting me my Certificate of Sponsorship (CoS) so
that I can apply to transition on to a <a class="reference external" href="https://www.gov.uk/tier-2-general">Tier 2 work visa</a>. It is similar to the
Certificate of Acceptance of Studies (CAS) that international students must get
from their universities before they can apply for their <a class="reference external" href="https://www.gov.uk/tier-4-general-visa">Tier 4 student visa</a>.
Sponsoring organisations can sponsor a limited number of internationals each
year, so we're waiting for the new cycle to start this month in April when UCL
will be able to sponsor more of us.</p>
<p>In the two weeks that I've been in, I've been learning the development process
that <a class="reference external" href="opensourcebrain.org">Open Source Brain</a> follows: attending sprint meetings, and the sort.
I'll write a post dedicated to this in a near future. It is on my to-do list.
This week, we <a class="reference external" href="https://github.com/SilverLabUCL/docker-osq/pull/6">diagnosed and fixed</a> an issue with the
current deployment. <a class="reference external" href="https://en.wikipedia.org/wiki/Sendmail">Sendmail</a> was
blocking the server because the <a class="reference external" href="https://docker.io">Docker</a> container hadn't
a <a class="reference external" href="https://en.wikipedia.org/wiki/FQDN">FQDN</a> as its hostname. The things we
learn. If you do find any issues with the <a class="reference external" href="opensourcebrain.org">Open Source Brain</a> platform, please
file an issue (or e-mail me if you prefer).</p>
<p>There's more work to be done: the deployment is being moved off <a class="reference external" href="https://aws.amazon.com/">AWS</a> on to the <a class="reference external" href="https://cloud.google.com/">Google Cloud Platform</a>. It's simple enough, but of course, the
deployment needs to be tested and validated before it can be declared live and
the AWS instance torn down.</p>
<p>I've also been learning how the research group works: getting to know the
people, what their interests are; attending the group discussions and journal
clubs; keeping an eye on various journals to share new science that may be
interesting to us. I've already learned quite a bit from the discussion. Given
the COVID situation, we're all working from home, so everything is happening
over Slack and video calls. I had managed to go to UCL for my induction in my
first week. I was the only one there for that particular session. Again, I was
lucky, since I expect that was the last induction session before UCL decided to
limit access.</p>
</div>
<div class="section" id="fedora">
<h2>Fedora</h2>
<p>We're nearing the Fedora 32 release, so I worked on the bits remaining for the
new <a class="reference external" href="https://fedoraproject.org/wiki/Changes/Comp_Neuro_Lab">CompNeuroFedora</a> lab image. Based on the discussion at the <a class="reference external" href="http://neuro.fedoraproject.org">NeuroFedora</a>
meeting, I <a class="reference external" href="https://pagure.io/fedora-websites/issue/1010">passed all the information</a> needed to set up a page for
the lab to the Websites team.</p>
<p>The general package updates continue. I just updated <a class="reference external" href="https://briansimulator.org/">Brian2</a> to the new version
this morning and <a class="reference external" href="https://bodhi.fedoraproject.org/updates/?packages=python-brian2">pushed an update with a test case</a>. The test
case takes one through the tutorial, so if one is looking to learn how to use
<a class="reference external" href="https://briansimulator.org/">Brian2</a>, this is a good way of doing it while contributing to <a class="reference external" href="http://neuro.fedoraproject.org">NeuroFedora</a>.
Another few bugs were fixed and <a class="reference external" href="https://bodhi.fedoraproject.org/users/ankursinha">updates pushed</a> too. I've got to work on
packaging a few new tools that are on the <a class="reference external" href="https://pagure.io/neuro-sig/NeuroFedora/issues?status=Open&assignee=ankursinha">list</a>.</p>
<p>On the <a class="reference external" href="https://pagure.io/fedora-join/Welcome-to-Fedora">Fedora-Join</a> front,
we've had a few more folks join the community to help out. It was lovely
chatting with new folks and discussing where and how they'd like to work with
the community. Needless to say, lots of cookie giving has occurred in the <a class="reference external" href="https://webchat.freenode.net/?channels=#fedora-join">IRC
channel</a>.</p>
<p>I've also been thinking about the lack of a process for Community Changes in
Fedora. Why isn't there something similar to the <a class="reference external" href="https://docs.fedoraproject.org/en-US/program_management/changes_policy/">Change process that we use
for dev changes</a>? I
finally <a class="reference external" href="https://pagure.io/Fedora-Council/tickets/issue/291">filed a ticket with the Council</a>. It's being discussed
on the <a class="reference external" href="https://lists.fedoraproject.org/archives/list/council-discuss@lists.fedoraproject.org/thread/NT3JI4QIA7D2UJWCOV662FZHOV6BUBLJ/">council-discuss mailing list</a>.
I've also asked <a class="reference external" href="https://pagure.io/mindshare/issue/197">Mindshare</a> and
<a class="reference external" href="https://pagure.io/fedora-commops/issue/205">CommOps</a> to weigh in this
morning. Please feel free to jump in and discuss how we should go about this. A
change process that
focusses on community is important, in my book.</p>
<p>The Git forge discussion continues on the <a class="reference external" href="https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/">-devel mailing list</a>,
so I've been keeping up with that. I would prefer Pagure myself, and I do
understand the CPE team's view even if I don't necessarily agree with it.</p>
</div>
<div class="section" id="organisation-for-computational-neuroscience-ocns">
<h2>Organisation for Computational Neuroscience: OCNS</h2>
<p>Things are quite quiet in <a class="reference external" href="https://www.cnsorg.org/">OCNS</a>. The <a class="reference external" href="https://www.cnsorg.org/board-of-directors">Board</a> has been discussing how best to
handle the <a class="reference external" href="https://www.cnsorg.org/cns-2020">CNS*2020</a> conference. An
announcement will be made once a decision has been reached.</p>
</div>
<div class="section" id="review-comments">
<h2>Review comments</h2>
<p>This turned out a lot longer than I'd expected. As I settle down to a weekly
post, it should get shorter. However, I do see that I've got lots going on, and
perhaps I do need to be more disciplined when accepting/volunteering for tasks,
and prioritising them once I've taken them up. I'm not <a class="reference external" href="https://www.winglemeyer.org/ramblings/2019/01/07/cookie-cleanup.html">cookie-licking</a> at
the moment, so that's quite good. Still, lots to do.</p>
</div>
A Vim script function to select signatures in Neomutt2020-03-15T09:39:20+00:002020-03-15T09:39:20+00:00ankurtag:ankursinha.in,2020-03-15:/2020/03/15/a-vimscript-function-to-select-signatures-in-neomutt.html<p class="first last">I was dabbling in <a class="reference external" href="https://en.wikipedia.org/wiki/Vim_(text_editor)#Vim_script">Vim script</a> and wrote myself a simple function to
select signatures when composing e-mails in <a class="reference external" href="https://neomutt.org/">Neomutt</a>.</p>
<p>I've been using <a class="reference external" href="https://neomutt.org/">Neomutt</a> for a <a class="reference external" href="https://ankursinha.in/2017/12/16/transitioning-to-neomutt-and-friends-for-e-mail.html">while now</a>.
It allows me to stick to the <a class="reference external" href="https://www.byobu.org/">Byobu</a> based terminal workflow that I'm used to.
Most importantly, it lets me use <a class="reference external" href="https://www.vim.org/">Vim</a> to write my e-mails, so I don't need to
really learn another tool now.</p>
<p><a class="reference external" href="https://neomutt.org/">Neomutt</a> can be configured to add a signature at the end of the e-mail, and one
can select a signature depending on various parameters, such as the senders
address using <a class="reference external" href="https://neomutt.org/man/neomuttrc">hooks</a>. However,
sometimes, one does need to select other signatures.</p>
<p>The simple <a class="reference external" href="https://www.vim.org/">Vim</a> way, of course, is to simply delete the last few lines, and
then read in the new signature using <code>:r <filename></code>. This takes a few
more key strokes than one would like (well, than I like) so I thought I'd
dabble in <a class="reference external" href="https://en.wikipedia.org/wiki/Vim_(text_editor)#Vim_script">Vim script</a> a bit and automate it. Here's what I've come up with:</p>
<pre class="code vim literal-block">
<span class="c">" A function to load the right signature when I'm using neomutt</span><span class="w">
</span><span class="k">function</span><span class="p">!</span> LoadSignature<span class="p">(</span>signature<span class="p">)</span><span class="w">
</span><span class="c"> " Only work for mail files</span><span class="w">
</span> <span class="k">let</span> this_file_type <span class="p">=</span> &<span class="k">filetype</span><span class="w">
</span> <span class="k">if</span> this_file_type <span class="p">!=</span> <span class="s2">"mail"</span><span class="w">
</span> echo <span class="s2">"This is not a mail file! Not running!"</span><span class="w">
</span> <span class="k">return</span> <span class="m">1</span><span class="w">
</span> <span class="k">endif</span><span class="w">
</span><span class="c">
" Get the current signature's line</span><span class="w">
</span><span class="c"> " Go to last line</span><span class="w">
</span> <span class="k">let</span> saved_cursor_position <span class="p">=</span> getpos<span class="p">(</span><span class="s1">'.'</span><span class="p">)</span><span class="w">
</span><span class="c"> " Set cursor to file end and search backwards</span><span class="w">
</span> <span class="k">call</span> cursor<span class="p">(</span><span class="m">99999999999999999999</span><span class="p">,</span> <span class="m">0</span><span class="p">)</span><span class="w">
</span> <span class="k">let</span> <span class="k">l</span>:sigstart <span class="p">=</span> search<span class="p">(</span><span class="s1">'-- '</span><span class="p">,</span> <span class="s1">'b'</span><span class="p">)</span><span class="w">
</span><span class="c"> " Confirm that the line was found</span><span class="w">
</span> <span class="k">if</span> sigstart <span class="p">==</span> <span class="m">0</span><span class="w">
</span> echo <span class="s2">"No signatures detected."</span><span class="w">
</span> <span class="k">return</span> <span class="m">1</span><span class="w">
</span> <span class="k">endif</span><span class="w">
</span><span class="c">
" Check if signature file exists</span><span class="w">
</span> <span class="k">let</span> <span class="k">l</span>:sigdir <span class="p">=</span> escape<span class="p">(</span>expand<span class="p">(</span><span class="s1">'$HOME'</span><span class="p">),</span> <span class="s1">'\'</span><span class="p">)</span> . <span class="s2">"/Sync/99_private/neomuttdir/"</span><span class="w">
</span> <span class="k">let</span> <span class="k">l</span>:sigfile <span class="p">=</span> sigdir . <span class="k">a</span>:signature . <span class="s2">".sig"</span><span class="w">
</span> <span class="k">if</span> filereadable<span class="p">(</span>sigfile<span class="p">)</span><span class="w">
</span><span class="c"> " delete the current lines after the "-- " line</span><span class="w">
</span> <span class="k">let</span> <span class="k">l</span>:delstart <span class="p">=</span> sigstart <span class="p">+</span> <span class="m">1</span><span class="w">
</span> execute delstart . <span class="s2">",$d"</span><span class="w">
</span><span class="c"> " Read the new signature</span><span class="w">
</span> execute sigstart . <span class="s2">"read "</span> . sigfile<span class="w">
</span><span class="c"> " Return cursor to wherever it was</span><span class="w">
</span> <span class="k">call</span> setpos<span class="p">(</span><span class="s1">'.'</span><span class="p">,</span> saved_cursor_position<span class="p">)</span><span class="w">
</span> <span class="k">else</span><span class="w">
</span> echo <span class="s2">"File "</span> . sigfile . <span class="s2">" not found!"</span><span class="w">
</span> echo <span class="s2">"Available signature files:\n"</span> . globpath<span class="p">(</span>sigdir<span class="p">,</span> <span class="s1">'*.sig'</span><span class="p">)</span><span class="w">
</span> <span class="k">endif</span><span class="w">
</span><span class="k">endfunction</span>
</pre>
<p>So, adding this to <code>~/.vimrc</code> would let one run <code>:call
LoadSignature('signature')</code> in <a class="reference external" href="https://www.vim.org/">Vim</a> to select a signature. Each signature is a
different file with a <code>.sig</code> file extension in the location given by
<code>sigdir</code>, and the name of the file is the argument that needs to be given
to the function. If the signature file cannot be found, it'll list available ones.</p>
<p>It's quite simple really, and I'm sure it can be made better, but it works.</p>
Useful DuckDuckGo bangs2019-01-27T15:11:35+00:002019-01-27T15:11:35+00:00ankurtag:ankursinha.in,2019-01-27:/2019/01/27/useful-duckduckgo-bangs.html<p class="first last">I switched to <a class="reference external" href="https://duckduckgo.com">DuckDuckGo</a> some time ago, and I've not had to look
back. In this post, I document some of the <a class="reference external" href="https://duckduckgo.com/bang">"bangs"</a> I find useful.</p>
<p>If you haven't moved to <a class="reference external" href="https://duckduckgo.com">DuckDuckGo</a> yet, <a class="reference external" href="https://www.quora.com/Why-should-I-use-DuckDuckGo-instead-of-Google/answer/Gabriel-Weinberg?share=9560e87d&srid=pJKz">here's</a>
why you should consider it. I moved to it a while back, and I've not looked
back since. In this post, I document some of the <a class="reference external" href="https://duckduckgo.com/bang">"bangs"</a> that I use which make <a class="reference external" href="https://duckduckgo.com">DuckDuckGo</a> even nicer
to use!</p>
<p>A <a class="reference external" href="https://duckduckgo.com/bang">"bang"</a> is a search shortcut, like ones you
can set up in Firefox and Chrome. Instead of navigating to the website to use
their search box, bangs allow you to search via <a class="reference external" href="https://duckduckgo.com">DuckDuckGo</a>, and it redirects
you to the search results on the website. So, apart from the obvious privacy
advantage: <a class="reference external" href="https://duckduckgo.com">DuckDuckGo</a> uses the website search, not you, it also means you can
search a plethora of websites right from <a class="reference external" href="https://duckduckgo.com">DuckDuckGo</a>. If you are used to using
the Firefox search bar, for example, this becomes really handy.</p>
<div class="section" id="general-bangs">
<h2>General bangs</h2>
<img alt="GIF showing the use of DuckDuckGo bangs to search Wikipedia." class="img-responsive" src="https://ankursinha.in/images/20190127-duckduckgo-wikipedia.gif" style="width: 60%;" />
<p>I use a number of general bangs:</p>
<ul class="simple">
<li><code>!bang</code> to search for bangs.</li>
<li><code>!w</code> to search Wikipedia</li>
<li><code>!g</code> to use Google when I must.</li>
<li><code>!gmaps</code> to search Google Maps.</li>
<li><code>!openstreetmap</code> to search Open Street Maps.</li>
<li><code>!youtube</code> to search Youtube.</li>
<li><code>!bbcw</code> to search BBC weather.</li>
<li><code>!goodreads</code> to search Goodreads.</li>
<li><code>!ox</code> to search the Oxford dictionary.</li>
<li><code>!sauk</code> to search Amazon UK (smile.amazon.uk).</li>
<li><code>!github</code> to search Github.</li>
<li><code>!ctan</code> to search CTAN.</li>
<li><code>!pypi</code> to search PyPi.</li>
<li><code>!man</code> to search man pages.</li>
</ul>
<p>A few academic ones I use often are:</p>
<ul class="simple">
<li><code>!gsc</code> to search Google Scholar.</li>
<li><code>!arxiv</code> to search ArXiv.</li>
<li><code>!pubmed</code> to search PubMed</li>
</ul>
</div>
<div class="section" id="fedora-related-bangs">
<h2>Fedora related bangs</h2>
<p>Now, here's where bangs get even more useful! Fedora related bangs! You can
use <code>!bang Fedora</code> to see them all, but I list the ones that are
available now here for you (and me):</p>
<ul class="simple">
<li><code>!fedora</code> or <code>!fedorawiki</code> to search the wiki.</li>
<li><code>!kojipkg</code> to search Koji for a package.</li>
<li><code>!fedpack</code> to search the Fedora packages app.</li>
<li><code>!fedoramagazine</code> to search the Fedora Magazine.</li>
<li><code>!askfedora</code> to search Ask Fedora.</li>
<li><code>!copr</code> to search COPR.</li>
<li><code>!rhbugs</code> or <code>!rhbz</code> to search Redhat Bugzilla.</li>
</ul>
<img alt="GIF showing the use of DuckDuckGo bangs to search the Fedora packages application." class="img-responsive" src="https://ankursinha.in/images/20190127-duckduckgo-fedora.gif" style="width: 60%;" />
<p>If you do use the quick search boxes that most browsers now provide, this makes
things so much easier. You needn't even use the drop down to select a search.
You just keep using <a class="reference external" href="https://duckduckgo.com">DuckDuckGo</a>. I use <a class="reference external" href="https://www.qutebrowser.org/">Qutebrowser</a> for example, where I use the command window
to do all my navigating. This is how quick it is (Capital O to open a new-tab,
and then <code>!fedpack nest</code> to search the Fedora packages application for
NEST, since <a class="reference external" href="https://duckduckgo.com">DuckDuckGo</a> is set as my default search service):</p>
<img alt="GIF showing the use of DuckDuckGo bangs from Qutebrowser." class="img-responsive" src="https://ankursinha.in/images/20190127-duckduckgo-qutebrowser.gif" style="width: 60%;" />
<p>So, there are lots of bangs. Use <a class="reference external" href="https://duckduckgo.com">DuckDuckGo</a>, use bangs, profit!
Happy ducking!</p>
</div>
<div class="section" id="addendum">
<h2>Addendum</h2>
<p>There is, of course, a lmddgtfy service. Try: <code>!lmddgtfy lmddgtfy</code>.
<a class="reference external" href="https://duckduckgo.com">DuckDuckGo</a> also provides an <a class="reference external" href="https://play.google.com/store/apps/details?id=com.duckduckgo.mobile.android">App for Android</a>,
and a widget that helps you search without having to open the browser first.</p>
<p>Bangs can be <a class="reference external" href="https://duckduckgo.com/newbang">suggested</a>, so please do
suggest new bangs for other services that you use frequently.</p>
</div>
New maintainers needed for these packages2019-01-24T11:20:00+00:002019-01-24T11:20:00+00:00ankurtag:ankursinha.in,2019-01-24:/2019/01/24/new-maintainers-needed-for-these-packages.html<p class="first last">I am looking to pass on Fedora packages that I no longer use to new maintainers.</p>
<p>I've recently realised that I am now busy enough to need to prioritise what
tasks I undertake. Apart from my research work (PhD and related activities),
I'd like to focus my time on <a class="reference external" href="https://neuro.fedoraproject.org">NeuroFedora</a>.
Therefore, I'm giving up a lot of the packages that I've accrued over the years
but no longer use. If any of these interest you, please take them from me.
Otherwise, I will orphan them at the end of the month.</p>
<p>I am quite happy to mentor contributors who are not yet packagers to help them
learn the necessary skills. You can become a package maintainer by helping to
co-maintain packages, as documented <a class="reference external" href="https://fedoraproject.org/wiki/How_to_get_sponsored_into_the_packager_group#Become_a_co-maintainer">here</a>.</p>
<p>I have already <a class="reference external" href="https://lists.fedoraproject.org/archives/list/devel@lists.fedoraproject.org/thread/VDK46C23DKBCOHYO3EOCSLRJF2UUPDFK/">e-mailed the devel mailing list</a>,
but also post here to ensure sufficient visibility of the note.</p>
<div class="section" id="orphaned-inactive-upstreams-or-retired-due-to-broken-deps">
<h2>Orphaned (inactive upstreams or retired due to broken deps)</h2>
<ul class="simple">
<li>albumart: was retired, now orphaned</li>
<li>gtg: inactive upstream</li>
<li>labyrinth: inactive upstream</li>
<li>memaker: inactive upstream</li>
<li>pyode: dead package, py3ode is available but needs packaging</li>
<li>python-inlinestyler: retired, now orphaned</li>
<li>scout: inactive upstream</li>
<li>toothchart: inactive upstream</li>
<li>xword: inactive upstream</li>
</ul>
</div>
<div class="section" id="looking-for-new-co-maintainers">
<h2>Looking for new (co)-maintainers:</h2>
<ul class="simple">
<li>axel: Light command line download accelerator</li>
<li>bibus: The bibus rpms</li>
<li>blobby: The blobby rpms</li>
<li>dcm4che-test: The dcm4che-test rpms</li>
<li>gitg: The gitg rpms</li>
<li>gnote: A note taking application for Gnome</li>
<li>gnumed: The GNUmed electronic medical record client</li>
<li>gtg: Getting Things GNOME!</li>
<li>hamster-time-tracker: A GTK3 time tracker</li>
<li>jigdo: The jigdo rpms</li>
<li>kapow: The kapow rpms</li>
<li>libgexiv2 A GObject wrapper around the Exiv2 photo metadata library</li>
<li>lifeograph: The lifeograph rpms</li>
<li>lingot: LINGOT Is Not a Guitar-Only Tuner</li>
<li>mrpt: The mrpt rpms</li>
<li>nautilus-pastebin: The nautilus-pastebin rpms</li>
<li>nut-nutrition: The nut-nutrition rpms</li>
<li>openarena: The openarena rpms</li>
<li>openmolar: The openmolar rpms</li>
<li>OSGi-bundle-ant-task: The OSGi-bundle-ant-task rpms</li>
<li>Panini: Visual tool for creating perspective views from panoramic and wide angle photographs</li>
<li>prepaid-manager-applet: The prepaid-manager-applet rpms</li>
<li>pystache: The pystache rpms</li>
<li>python-baker: The python-baker rpms</li>
<li>python-django-post_office: The python-django-post_office rpms</li>
<li>python-django-stopforumspam</li>
<li>python-uri-templates: The python-uri-templates rpms</li>
<li>rssdler: RSS Broadcatcher for podcasts, videocasts, and torrent feeds</li>
<li>tagtool: The tagtool rpms</li>
<li>trash-cli: Command line interface to the freedesktop.org trashcan</li>
<li>xmedcon: The xmedcon rpms</li>
</ul>
</div>
NeuroFedora updated: 2019 week 22019-01-13T20:55:44+00:002019-01-13T20:55:44+00:00ankurtag:ankursinha.in,2019-01-13:/2019/01/13/neurofedora-update-2019-week-2.html<p class="first last">An update on <a class="reference external" href="https://neuro.fedoraproject.org">NeuroFedora</a> at the end of week 2 in 2019.</p>
<div class="figure">
<a class="reference external image-reference" href="https://docs.fedoraproject.org/en-US/neurofedora/overview/"><img alt="NeuroFedora logo" class="img-responsive" src="https://ankursinha.in/images/20181005-NeuroFedoraLogo01.png" style="width: 30%;" /></a>
<p class="caption"><a class="reference external" href="https://pagure.io/design/issue/602">NeuroFedora logo by Terezahl from the Fedora Design Team</a></p>
</div>
<p>We had our first meeting of the year. The <a class="reference external" href="https://meetbot.fedoraproject.org/teams/neurofedora/neurofedora.2019-01-11-14.00.log.html">full logs</a>
from our meeting are available here on the <a class="reference external" href="https://meetbot.fedoraproject.org/">Fedora mote application</a>. I have pasted the minutes of the
meeting at the end for your convenience.</p>
<p>The meeting was broadly for the team to come together and discuss a few things.
We checked on the status of current tasks, and discussed our future steps.
We've got to work on our documentation, for example. There's a lot to do, and
a lot of cool new things to learn---in science, computing, and community
development. If you'd like to get involved, please get in touch.</p>
<p>We're continuing our work on including software in NeuroFedora, since that's
the major chunk of our work load.</p>
<hr class="docutils" />
<div class="section" id="meeting-summary">
<h2>Meeting summary</h2>
<p>Meeting started by FranciscoD at 14:00:15 UTC.</p>
<ul class="simple">
<li><dl class="first docutils">
<dt>Roll call (FranciscoD, 14:00:43)</dt>
<dd><ul class="first last">
<li>IRC meeting commands: <a class="reference external" href="https://fedoraproject.org/wiki/Meeting:Guide">https://fedoraproject.org/wiki/Meeting:Guide</a> (FranciscoD, 14:01:56)</li>
</ul>
</dd>
</dl>
</li>
<li><dl class="first docutils">
<dt>Joining the team (FranciscoD, 14:04:37)</dt>
<dd><ul class="first last">
<li>We need package maintainers, testers, doc writers, users---> there are so
many ways of getting involved (FranciscoD, 14:05:30)</li>
<li>To help with packaging, please join the neuro-sig FAS group, and then log
out and back in to src.fp.o once your membership is approved (FranciscoD,
14:05:49)</li>
<li>To join the group on pagure (where we maintain issues), please drop any of
us a ping and we'll add you (FranciscoD, 14:06:10)</li>
<li>Our channels: #fedora-neuro on IRC, <a class="reference external" href="https://t.me/NeuroFedora">https://t.me/NeuroFedora</a> on Telegram,
<a class="reference external" href="mailto:neuro-sig@lists.fp.o">neuro-sig@lists.fp.o</a> is our ML (FranciscoD, 14:07:07)</li>
<li><a class="reference external" href="https://pagure.io/neuro-sig/NeuroFedora">https://pagure.io/neuro-sig/NeuroFedora</a> -> housekeeping repo (FranciscoD, 14:07:57)</li>
<li><a class="reference external" href="https://pagure.io/neuro-sig/documentation">https://pagure.io/neuro-sig/documentation</a> -> documentation repo (FranciscoD, 14:08:05)</li>
<li>Tickets:
<a class="reference external" href="https://pagure.io/neuro-sig/NeuroFedora/issues?tags=S%3A+Next+meeting">https://pagure.io/neuro-sig/NeuroFedora/issues?tags=S%3A+Next+meeting</a>
(FranciscoD, 14:11:56)</li>
<li>Additional agenda item: prioritise packages so we have some order in which
to go about them (FranciscoD, 14:12:36)</li>
<li>Poster at CNS: <a class="reference external" href="https://pagure.io/neuro-sig/NeuroFedora/issue/189">https://pagure.io/neuro-sig/NeuroFedora/issue/189</a>
(FranciscoD, 14:13:49)</li>
<li>Annual organisation for computational neuroscience conference is at
Barcelona in July this year: <a class="reference external" href="https://www.cnsorg.org/cns-2019">https://www.cnsorg.org/cns-2019</a> (FranciscoD,
14:14:18)</li>
<li>Everyone that contributes in any way will be a mentioned in the author
list (FranciscoD, 14:14:53)</li>
<li><a class="reference external" href="https://pagure.io/neuro-sig/NeuroFedora/issue/188">https://pagure.io/neuro-sig/NeuroFedora/issue/188</a> -> Own neurofedora.org?
(FranciscoD, 14:16:20)</li>
<li>AGREED: Use neuro.fp.o (+5, -0) (FranciscoD, 14:18:28)</li>
<li><a class="reference external" href="https://pagure.io/neuro-sig/NeuroFedora/issue/152">https://pagure.io/neuro-sig/NeuroFedora/issue/152</a> -> Organisational blog
on neurofedora.github.io? (FranciscoD, 14:19:08)</li>
<li>We do have a github organisation: <a class="reference external" href="https://github.com/neurofedora">https://github.com/neurofedora</a>
(FranciscoD, 14:19:26)</li>
<li>AGREED: FranciscoD publish updates on his blog for the time being.
Organisational blog to be revisited in the future (+6, -0) (FranciscoD,
14:26:45)</li>
<li><a class="reference external" href="https://pagure.io/neuro-sig/NeuroFedora/issue/8">https://pagure.io/neuro-sig/NeuroFedora/issue/8</a> -> A web location for
user-end troubleshooting? (FranciscoD, 14:27:01)</li>
<li><a class="reference external" href="https://neurostars.org/">https://neurostars.org/</a> -> NeuroStars generic troubleshooting form
(FranciscoD, 14:29:51)</li>
<li>A list of neuroscience resources is here:
<a class="reference external" href="https://docs.fedoraproject.org/en-US/neurofedora/related-links/">https://docs.fedoraproject.org/en-US/neurofedora/related-links/</a>
(FranciscoD, 14:30:14)</li>
<li>A new FAS (better interface etc) is being planned, but there's no ETA of
when it'll be ready for deployment (FranciscoD, 14:33:55)</li>
<li>ACTION: FranciscoD update docs to request users to file bugs on pagure
(FranciscoD, 14:35:34)</li>
<li><a class="reference external" href="https://pagure.io/neuro-sig/NeuroFedora/issue/121">https://pagure.io/neuro-sig/NeuroFedora/issue/121</a> -> Add comps groups
(FranciscoD, 14:35:46)</li>
<li>Neuron (without MPI/Python) is currently in review:
<a class="reference external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1662526">https://bugzilla.redhat.com/show_bug.cgi?id=1662526</a> (FranciscoD,
14:37:30)</li>
<li>Link to our suggestion form is here:
<a class="reference external" href="https://docs.fedoraproject.org/en-US/neurofedora/overview/#_suggest_software_for_inclusion">https://docs.fedoraproject.org/en-US/neurofedora/overview/#_suggest_software_for_inclusion</a>
(FranciscoD, 14:39:06)</li>
<li><a class="reference external" href="https://pagure.io/neuro-sig/NeuroFedora/issue/180">https://pagure.io/neuro-sig/NeuroFedora/issue/180</a> -> Docker images for
NEST (FranciscoD, 14:41:26)</li>
<li>ACTION: FranciscoD create new page for third party software resources in
docs (FranciscoD, 14:49:18)</li>
<li>ACTION: FranciscoD add <a class="reference external" href="https://flathub.org/apps/details/org.gnode.NixView">https://flathub.org/apps/details/org.gnode.NixView</a>
to "third party sources list" on docs (FranciscoD, 14:50:38)</li>
<li>LINK: <a class="reference external" href="https://github.com/G-Node/nix/">https://github.com/G-Node/nix/</a> (gicmo, 14:53:20)</li>
<li><a class="reference external" href="https://pagure.io/neuro-sig/NeuroFedora/issue/155">https://pagure.io/neuro-sig/NeuroFedora/issue/155</a> -> Including packages
that need Matlab at runtime (FranciscoD, 14:55:27)</li>
<li>Prioritise python over Matlab/Octave (FranciscoD, 14:57:56)</li>
</ul>
</dd>
</dl>
</li>
<li><dl class="first docutils">
<dt>Open floor (FranciscoD, 14:58:50)</dt>
<dd><ul class="first last">
<li>ACTION: FranciscoD add a page "neuroscience resources for beginners"
(FranciscoD, 15:03:56)</li>
<li>LINK: <a class="reference external" href="https://labs.fedoraproject.org/">https://labs.fedoraproject.org/</a> -> I mean these (FranciscoD,
15:05:12)</li>
<li>ACTION: FranciscoD send out logs (FranciscoD, 15:06:28)</li>
<li>ACTION: FranciscoD summarise meeting discussion in next blog post
(FranciscoD, 15:06:38)</li>
<li>LoKoMurdoK and zbyszek are package maintainer sponsors (FranciscoD,
15:08:33)</li>
<li>Thanks gicmo pac23 zbyszek LoKoMurdoK blackfile mhough for coming, and
helping out (FranciscoD, 15:09:35)</li>
</ul>
</dd>
</dl>
</li>
</ul>
<p>Meeting ended at 15:10:43 UTC.</p>
<hr class="docutils" />
<p><a class="reference external" href="https://docs.fedoraproject.org/en-US/neurofedora/overview/">NeuroFedora documentation</a> is available on
<a class="reference external" href="https://docs.fedoraproject.org/en-US/docs/">the Fedora documentation website</a>. Feedback is always welcome.
You can get in touch with us <a class="reference external" href="https://docs.fedoraproject.org/en-US/neurofedora/overview/#_communicating_and_getting_help">here</a>.</p>
</div>
NeuroFedora update: 2019 week 12019-01-06T21:04:14+00:002019-01-06T21:04:14+00:00ankurtag:ankursinha.in,2019-01-06:/2019/01/06/neurofedora-update-2019-week-1.html<p class="first last">An update on <a class="reference external" href="https://neuro.fedoraproject.org">NeuroFedora</a> at the end of week 1 in 2019. Happy new
year!</p>
<div class="figure">
<a class="reference external image-reference" href="https://docs.fedoraproject.org/en-US/neurofedora/overview/"><img alt="NeuroFedora logo" class="img-responsive" src="https://ankursinha.in/images/20181005-NeuroFedoraLogo01.png" style="width: 30%;" /></a>
<p class="caption"><a class="reference external" href="https://pagure.io/design/issue/602">NeuroFedora logo by Terezahl from the Fedora Design Team</a></p>
</div>
<p>Happy new year, everyone! In week 1 of the year 2019:</p>
<ul class="simple">
<li><a class="reference external" href="https://docs.fedoraproject.org/en-US/neurofedora/overview/">NeuroFedora documentation</a> went up on
<a class="reference external" href="https://docs.fedoraproject.org/en-US/docs/">the Fedora documentation website</a>. You can find all the
information you need on NeuroFedora there. If something is missing, please
get in touch (or contribute!).</li>
<li>We announced NeuroFedora to the computational neuroscience research community
by sending an e-mail to the <a class="reference external" href="http://www.tnb.ua.ac.be/pipermail/comp-neuro/2019-January/007706.html">comp-neuro mailing list</a>
mailing list.</li>
<li>We've begun working on packaging <a class="reference external" href="https://www.thevirtualbrain.org/tvb/zwei/brainsimulator-software">TVB</a>.</li>
<li>We submitted <a class="reference external" href="https://www.neuron.yale.edu/neuron/">Neuron</a> for
<a class="reference external" href="https://bugzilla.redhat.com/show_bug.cgi?id=1662526">review</a></li>
</ul>
<hr class="docutils" />
<p><a class="reference external" href="https://docs.fedoraproject.org/en-US/neurofedora/overview/">NeuroFedora documentation</a> is available on
<a class="reference external" href="https://docs.fedoraproject.org/en-US/docs/">the Fedora documentation website</a>. Feedback is always welcome.
You can get in touch with us <a class="reference external" href="https://docs.fedoraproject.org/en-US/neurofedora/overview/#_communicating_and_getting_help">here</a>.</p>
On vacation2018-12-21T23:09:24+00:002018-12-21T23:09:24+00:00ankurtag:ankursinha.in,2018-12-21:/2018/12/21/on-vacation.html<p class="first last">I will be on vacation for about 2 weeks with limited internet connectivity.</p>
<p>I will be on vacation till the start of the new year with limited internet
connectivity. I may not reply to e-mails until I return.</p>
<p>Happy holidays!</p>