NeuroFedora update: week 42
A quick update on NeuroFedora at the end of week 42.
neuroscience/fedora/musings
A quick update on NeuroFedora at the end of week 42.
A quick update on NeuroFedora at the end of week 41.
I have recently resurrected the NeuroFedora SIG. We aim to make Fedora a ready to use platform for neuroscientists, so that they can focus on the science. Read on to learn more!
The Connfa open source suite looks like a great set of tools for conference management. It consists of a web application, a central CMS integration server, and mobile applications for both Android and iOS. I was looking at how one could use the mobile applications. The mobile applications get their data from the integration server, which provides an API. So, I looked at how to set it up and document my findings in this post.
I taught a Fedora Classroom session the other day - Git 101 - where I walked through the basics of Git. This is a quick summary of the session.
I taught a Fedora classroom session today - "Command Line 101" - where I introduced the command line and demonstrated how useful the command line is. This is a quick summary of the session.
Different teams use different platforms to communicate within themselves. When teams on different communication platforms want to collaborate, though - there's a bit of an issue. In this post, I document how one can setup channels on various platforms (Slack, IRC, Gitter) and bring them all together on Riot.
I've come across a few mailing lists for neuroscientists, but I couldn't find a chat channel. While mailing lists suit certain purposes, open source communities tend to use a combination of mailing lists and chat channels - each platform serves different purposes. TLDR: here's a new chat channel on Gitter here for everything neuroscience related. It is also accessible using the IRC and Riot.
People find issues with software everyday. Some of these people will take the time to inform the developers of these issues. Some of these issues that have been reported will be looked at by developers. Some of the issues that the developers look at will contain enough information to encourage the developers to work on a fix. Ultimately, only a handful of issues will be fixed. In this post, I encourage users to report issues to developers the right way - increasing the chances of the bug being corrected. In the process, not only does one improve one's personal experience, one can help improve the experience of other users, while helping developers make their software better. The intended target here is not the developer community - they already know most all of this.
As part of the migration of the Fedora Free Media group, we're refreshing the FAS group membership!