Music is a key part of my life. I spend a lot of time listening and analyzing music. However, music is as much a personal experience as it is a social one too. In music, an artist shares their perspective and experience with the listener. The listener, in turn, shares music with others. In my experience, some of the best music recommendations have come from friends or from other music fans. Thus, I’m happy to announce Tergiversate, a new column on my blog that celebrates great music and the role it plays in documenting culture and society.
This post is part of a series of posts where I contribute to the ListenBrainz project for my independent study at the Rochester Institute of Technology in the fall 2017 semester. For more posts, find them in this tag.
This week is the last week of the fall 2017 semester at RIT. This semester, I spent time with the MetaBrainz community working on ListenBrainz for an independent study. This post explains what I was working on in the last month and reflects back on my original objectives for the independent study.
This article was originally published on Opensource.com.
On November 7, 2017, members of the RIT community came together for the annual Election Night Hackathon held in the Simone Center for Student Innovation. This year marked the seventh anniversary of a civic tradition with the [email protected] community. As local and state election results come in across nine projectors, students and professors work together on civic-focused projects during the night. Dan Schneiderman, the [email protected] Community Liaison, compiled lists of open APIs that let participants use public sets of data made available by governments at the federal, state, and local level.
This post is part of a series of posts where I contribute to the ListenBrainz project for my independent study at the Rochester Institute of Technology in the fall 2017 semester. For more posts, find them in this tag.
My progress with ListenBrainz slowed, but I am resuming the pace of contributing and advancing on my independent study timeline. This past week, I finished out assigned tasks to discuss contributor-related documentation, like a Code of Conduct, contributor guidelines, and a pull request template. I began research on user statistics and found some already created. I wrote one of my own, but need to learn more about Google BigQuery to advance further.
It’s 2pm in the afternoon and the weather is becoming cold after so long. On this brisk November day, an old professor steps out in the corner lobby of the college. The golden rays of the sun cast a warm, radiant glow, leaving a bright, inviting air. This small moment of time is meaningless in an infinite universe of possible moments.
Over the summer, I migrated my desktop environment to i3, a tiling window manager. Switching to i3 was a challenge at first, since I had to replace many things that GNOME handled for me. One of these things was changing screen brightness. xbacklight, the standard way of changing backlight brightness on laptops, doesn’t work on my hardware.
Recently, I discovered brightlight, a tool that changes backlight brightness. I decided to try it, and it worked with root privileges. However, I found there was no RPM package in Fedora for brightlight. I decided this was the right time to try creating a package in Fedora and learn how to create an RPM.
In this article, I’ll cover and share how I…
- Created the RPM SPEC file
- Built the package in Koji and Copr
- Worked through an issue with debug package
- Submitted the package to Fedora package collection
This post is part of a series of posts where I contribute to the ListenBrainz project for my independent study at the Rochester Institute of Technology in the fall 2017 semester. For more posts, find them in this tag.
Last week moved quickly for me in ListenBrainz. I submitted multiple pull requests and participated in the weekly developer’s meeting on Monday. I was also invited to take part as a mentor for ListenBrainz for the upcoming round of Google Code-In! In addition to my changes and new role as a mentor, I’m researching libraries like D3.js to help build visualizations for music data. Suddenly, everything started moving fast!
Since I became a Fedora contributor in August 2015, I’ve spent a lot of time in the community. One of the great things about a big community like Fedora is that there are several different things to try out. I’ve always tried to do the most help in Fedora with my contributions. I prefer to make long-term, in-depth contributions than short-term, “quick fix”-style work. However, like many others, Fedora is a project I contribute to in my free time. Over the last month, I’ve come to a difficult realization.
After deep consideration, I am resigning from the Fedora Council effective at the end of the Fedora 26 release cycle.
This post is part of a series of posts where I contribute to the ListenBrainz project for my independent study at the Rochester Institute of Technology in the fall 2017 semester. For more posts, find them in this tag.
One of the first rites of passage when working on a new project is creating your development environment. It always seems simple, but sometimes there are bumps along the way. The first activity I did to begin contributing to ListenBrainz was create my development environment. I wasn’t successful with the documentation in the README, so I had to play around and work with the project before I was even running it.
The first part of this post details how to set up your own development environment. Then, the second half talks about the solution I came up with and my first contribution back to the project.
A unique opportunity of attending an open source-friendly university is when course credits and working on open source projects collide. This semester, I’m participating in an independent study at the Rochester Institute of Technology where I will contribute to the ListenBrainz project.
Many students take part in independent studies where they work on their own projects. However, in the spirit of open source collaboration, I wanted to contribute to a project that already existed. That way, my work would be helpful to a real-world project where it would have a value even after the end of the semester. Additionally, I wanted a project to help me sharpen my Python skill. And ListenBrainz was a fun, exciting candidate for this.
© 2018 Justin W. Flory's Blog
Theme by Anders Norén — Up ↑
Recent Comments