Announcing Nightingale 1.12.1

Nightingale 1.12.1 is finally released! Existing installations of the last release version of Nightingale (1.12) on Windows or Mac OS X will give you the opportunity to automatically update to the new version. For Linux users the packages are updated; if you installed from a tarball on Linux you’ll have to update by grabbing a new one from the download page.

What’s new?

We cleaned up quite a bit: More legacy code from Songbird was removed or disabled, thus we expect the release to be more stable. There are also some bugs fixed, such as the Unity integration causing a crash in Ubuntu 13.04, battery drain in OS X Lion or newer and playback not properly updating the play counts.

As mentioned in a previous blog post, freaktechnik implemented some beautiful firstrun pages, which will present you changes after updates or overall information on the very first start. Through our newly introduced statistics page, this will also help us to track installations and upgrades to find update-related issues. Note that if you dislike the firstrun page, you can visit about:config and set the preference ‘nightingale.update.url’ to ”.

Additionally, GeekShadow implemented a new localization infrastructure and will contact past Songbird translators. He got rid of the last Songbird references, and thanks to our translators and reviewers many locales were improved quite a lot. However, there are still some locales without maintainers; and even if your locale already has one it would be great if you volunteer for proofreading and translating Nightingale’s strings! When updating, you may need to re-download the language packs for this change to take effect.

We also did some backend work switching to a new update infrastructure, as Google Code shuts down its downloads section. Updates are now handled through GitHub, where we also keep our main source code repository. An issue preventing Linux updates got fixed as well, so you should be able to auto-update from tarballs in the future.

As this is our first release after the shutdown of Songbird we replaced everything provided through Songbird infrastructure with our own services. To see everything we changed in 1.12.1, check out the official release notes.

The IDs of some add-ons changed, namely mashTape, SHOUTcast and Last.fm. This means Nightingale will find new add-ons and ask you, if you want to install them. Since the ID changed, they will not override the existing extensions. The previous versions of those add-ons will show up in the extensions manager as incompatible with Nightingale 1.12.1 and can be uninstalled.

Unity and libnotify integration have been split up into two optional components. Thanks to this the nightingale-nounity package now also includes libnotify integration. For those who don’t want, or can’t use our PPA, we still offer GNOME/Unity integration builds.

 

Enjoy the latest version of Nightingale, update or install it and listen to your favorite songs. We’d love to hear your feedback in the forums or on the IRC channel, #nightingale on irc.mozilla.org. As always, we’re looking for testers, developers, theme makers, and users to idle in our forums and IRC, not to mention help out with the project. Feel free to join!

Spread the word – and enjoy the tune of life!

- The Nightingale Community

Help testing 1.12.1

Yesterday I landed a new feature in the trunk for 1.12.1. What it does is simply welcoming new users with a firstrun page with helpful information and users who updated with the changelog. This seems like a feature that doesn’t need testing. But it does, because it also serves as a way to measure the amount of installs and upgrades. Currently the stats are running on a test server and you can see them here. All data captured until release will be deleted.

Another reason why it needs testing, is because I had to mess with the session restore component of Nightingale. The same file, could cause a blank page on startup sometimes, but that should be fixed (or not?) . To be sure, that I messed nothing up I need other people than me to use Nightingale with this change, as I have my particular habits, and issues might only occur when you use Nightingale in a different way than I do.

Of course you can also disable the upgrade page, which shows you the changes after an upgrade. To do so just set the preference “nightingale.update.url” to “”. This is one possible reason, why our statistics for upgrades won’t be exact, while we can count on the install statistics (unless for modified builds of Nightingale, of course). Another reason are anti-tracking add-ons or disabled JavaScript.

All other changes Nightingale 1.12.1 currently contains are listed under the release notes. You will see the full release of it before January the 14th, as after this date our integrated updating system will be broken.

You can download a build of Nightingale including the changes from SourceForge or, if your system uses apt, install it from ppa:nightingaleteam/nightingale-nightly. Please report any issues you encounter on GitHub, but please make sure the issue hasn’t been reported yet. Also bear in mind that this is not a release version and might destroy your profile, so only use your existing profile if you don’t care about it, or create a new one by launching Nightingale with the -p argument.

There are 14 comments in our discussion thread.

Social Media

fb-stats

As you’ve probably noticed, I’ve been hyperactive on Nightingale’s Twitter and Facebook. I’ve tried to post as much news and interesting stuff to you as possible. Basically, everything that’s not worth to blog about but still is of value for you. The goal is to keep you informed on what’s going on. It also helps in showing you that Nightingale is alive and evolving. That’s also why I’m posting these insights here.

I want to share a few of my insights I got from the last month with you. Bare in mind, that this doesn’t apply to our Google+ presence, I didn’t have the rights to post there just until recently.

What’s the most important thing in Social Media? Interaction. So, which network does give us the most interaction? Both. You get a lot more direct feedback on twitter, while on Facebook you know how many have seen it, and some will like or even share it. It’s interesting that there is some sort of an active core fan base, who interact a lot more with our posts than the others. Some of you just fav every tweet we put out, while others (or are they the same people?) like each and every post of ours.

Pictures interestingly do generally better on Facebook. They get reposted a lot more and liked far quicker. I asked myself, why would you immediately interact with a picture while you hesitate to interact with text or a link? And it’s pretty simple: pictures stand out of your feed. And if you look at other pages, they are constantly posting pictures, because you get that quick and big feedback.

fb-stats

To analyze your guys feedback and our Social Media performance, I use a self-hosted ThinkUp instance and the Facebook analytics, which are pretty nice.

What do I have planned? I want more interaction. Not because it’s cool, but I want the normal user to be able to influence the development. Because what the developers decide might be stupid for others. Big changes are usually discussed on github in the issues system. Would you notice that? Probably not. We only sparingly know what you guys really want. We do have a wished features list, but we don’t know what you want the most. At the moment we are being pretty selfish and are bringing Nigthingale “à jour”, so we keep up with technology. Also bare in mind, we are a very distributed development team; I am not the only one to post in our Social Media channels and I also develop parts for Nightingale.

If you ever write about Nightingale, don’t forget to let us know! Mention us on Twitter, post it on our Facebook Timeline or share it with us on Google+. Even tough we try to catch all coverage about Nightingale, we might miss some, don’t let that happen! If you don’t follow us yet on any of these networks, go ahead and do so and stay up to date with the project.

What do you think of our social media presence? What could we improve?

Bug Bounties

Bountysource

Exciting news for those of you who want to help Nightingale development with a little bit of money: we are officially using Bountysource for bounties on bugs now. Bountysource is an open source project, which allows users to put money on a bug or feature request – wether it’s already in the issues tracker or not. And it makes it easy for developers to find bugs to work on to get a little bit of money. and it’s perfect for us: we don’t have to handle money in the whole process. To give a bounty on an existing issue, just go to https://www.bountysource.com/trackers/230233-nightingale-media-player-nightingale-hacking and select the issue you want to speed up from the list.

BountysourceBy putting a bounty on a bug, you make it more likely to get another developer, who is not currently wokring on Nightingale to fix a bug. We from the team will fix bugs with and without bounties equally, just dependent on our plans and personal preferences. So no worries if you don’t have the money to boost an issue.

We will add the “bounty” tag to all issues with bounties. If you start working on an issue with the tag, be sure to got to Bountysource and click the “Start Work” button.

For more information on how Bountysource works, visit their FAQ. Please hang on if you want to donate directly to the project. We are still looking into how to handle money the best.

 

Video of our Talk at RMLL 2013

Faster than expected: here is the video of our talk at RMLL 2013. As mentioned in the last post, GeekShadow and I talked a little shorter. We registered for 40 minutes but ended up with about 20 minutes. Enjoy!