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.
After years of using the excellent Firefox, I've decided to tweak my workflow a little more by giving Qutebrowser a go. Qutebrowser is a brilliant keyboard-focused browser. In this post, I document my first day with Qutebrowser, and I also include some tips and tricks that others may find helpful.
A summary of the Fedora Join SIG meeting we had on 22nd May, 2017. We discussed the ongoing resurrection of the IRC classroom programme, and then went on to discuss various video platforms that can be used for the Classroom v2 initiative. Both classroom programmes are aimed at seasoned contributors passing their knowledge on to newer ones. The IRC classrooms are text only (because they're held over the IRC) and this limits the breadth of topics that can be covered here. The new v2 initiative on the other hand, is aimed at using newer, more powerful platforms to host better sessions with more variety. There's much work to be done, and you can help!
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.