imms maintenance

[mar...@martingkelly.com]

Hi,

I've been using imms for a long time now and really like the software! Recently, I've been working with imms, in particular trying to get it to work with Audacious 3.6+. After discussing this with John Lindgren of Audacious, John graciously converted imms to Audacious 3.6+ (there were some API changes). After that, I wrote a patch so that imms would send played songs immediately to the database instead of waiting for a GIOChannel's internal buffer to fill up (this can take quite a while). All of these changes are captured here, in my fork of John Lindgren's fork of imms:

https://github.com/martingkelly/imms

I also opened these issues for tracking:
https://code.google.com/p/imms/issues/detail?id=23
https://code.google.com/p/imms/issues/detail?id=24

I discussed this with Artur R. Czechowski, who mentioned to me that both he and Michael Grigoriev have been too busy to do much work with imms lately, but that he'd be happy for me to help out with imms, both upstream and in Debian packaging.

Given all of this, I'm wondering if I could get John Lindgren and my patches into imms. If no one has time to review the patches, would it be possible for me to commit them directly? I would be sad to see imms die once Audacious 3.6+ becomes more widely used.

Thanks,
Martin

[Dave Schaefer]

Hey Martin,

Thanks for the hard work! I agree, IMMS is great software, and it
would be good to keep it alive.

Google Code is turning into a read-only site soon[1]. That will make
hosting releases there rather difficult. Perhaps this is a good time
to move the official depo to github, and host future releases there?
That might make pull requests and issue tracking easier.

I don't believe there is an official location for imms on github. If
you, Mag, or Artur want to host one under their account that could
work. If you don't feel comfortable with that or no one else wants to,
I'm happy to host it. I'd be happy to convert the existing wiki docs
into markdown either way.

Any votes?


[1] https://code.google.com/p/support/wiki/ReadOnlyTransition

[mar...@martingkelly.com]

Yeah, I was thinking along the same lines wrt github and Google Code. I think we should move to Github, and I'd be happy to host it on my account. Hopefully I can work on that some this weekend; I'll keep you posted.

Mag, Arthur: Any objections to moving this to Github? Would either of you like to host it?

Thanks,
Martin

[mar...@martingkelly.com]

Hi all,

Today, I migrated Google Code to my personal account (https://github.com/martingkelly/imms). I'm in the process of migrating Debian patches and John Lindgren's patches for Audacious 3.6+ compatibility, as well as my own recent patch. At that point, we will have all known bug fixes in the codebase.

Unless mag or others have objections, I propose that we use that location for imms in the future, so that future development can continue once Google Code goes read-only.

[mar...@martingkelly.com]

I should also note that, for now, the most recent changes are on the branch staging-master. Once I get permission from everyone involved, I will merge that into master.

[Michael Grigoriev]

Sounds good to me!

Thanks for looking after IMMS, guys :)

--
You received this message because you are subscribed to the Google Groups "imms-users" group.
To unsubscribe from this group and stop receiving emails from it, send an email to imms-users+...@googlegroups.com.
To post to this group, send email to imms-...@googlegroups.com.
Visit this group at http://groups.google.com/group/imms-users.
For more options, visit https://groups.google.com/d/optout.