MyBB Internal: One or more warnings occurred. Please contact your administrator for assistance.
MyBB Internal: One or more warnings occurred. Please contact your administrator for assistance.
MyBB Internal: One or more warnings occurred. Please contact your administrator for assistance.
MyBB Internal: One or more warnings occurred. Please contact your administrator for assistance.
Nightingale Forums - Is Anyone Still Developing This?

Nightingale Forums

Full Version: Is Anyone Still Developing This?
You're currently viewing a stripped down version of our content. View the full version with proper formatting.
If so, I'd suggest a rebase against the current songbird source (I'd import the svn to git using git-svn) and re-fork from there...

Otherwise, let's revive this project. Songbird's devs are jerks for dropping official linux support and we can do better anyway.
(09-13-2011, 08:35 PM)ilikenwf Wrote: [ -> ]If so, I'd suggest a rebase against the current songbird source (I'd import the svn to git using git-svn) and re-fork from there...

Otherwise, let's revive this project. Songbird's devs are jerks for dropping official linux support and we can do better anyway.

I think the easiest thing to do would be to modify each new version of Songbird in patches e.g., swap Songbird gstreamer with native gstreamer or patch stock Songbird so that it has CD-burning capacity in Linux (like how Linux Mint is a modified version of Ubuntu that is compatible with Ubuntu). I think maintaining a real fork (like how Ubuntu has heavily modified Debian and is no longer compatible with Debian) would require more developers than this project has. I guess the major question is does Nightingale have enough man power to at least patch Songbird. I highly doubt we could create and maintain a real fork of Songbird, without a large number of developers. Which is sad because I've had to use alternatives like Banshee and do not like them.
Okies... as we speak, I'm pulling down all the songbird revisions from SVN using git svn. From here, I'll try and get the current version of Songbird workable for both x86_64 and i686.

From here on out, we'll focus on functionality first, renaming stuff with nightengale and making it look unique LAST. Once we have something that works as songbird used to on Linux, we can make it pretty then.

If I get there, I'll push the source to sourceforge's git (or somewhere) and we can work on it all from that point.

IMHO CD-burning isn't really necessary because you can use Brasero, Xfburn, or K3b amongst others...

I am not developing on Ubuntu, and I don't plan to because honestly ubuntu isn't a hacker/geek's distro as compared to gentoo or Archlinux. Other people can worry about making debian buildscripts or whatever for it once we get it working.

As for nightingale, do we want to have a fork or a patchset? Once you actually establish a fork that uses local libraries, you'd be surprised at how easy it is to manage most of the time - you just have to make sure that git or svn appropriately merges your changes, and then you make edits to make everything work as it did in your last working revision.

If it comes to it, we could take donations through a kickstarter project and hire some full time developers for a month or two to do the actual porting...just a thought. I bet the original Nightingale developers would be open to setting that up.
I think the most important thing is to make sure that x86 and x64 Linux binaries are kept up to date with important upstream changes in Songbird. Regardless of whether we use 1.8 or 1.9 we need to make sure that we at least have rebranded and retheamed Songbird, but I don't know what the status of the feather is.
From there bigger changes can be made. Although I think Kickstarter would be a good idea, I think it would help if we at least had an alpha of Nightingale before asking for donations. I think an alpha should contain the current Nightingale code base with all the necessary changes required by POTI's license. Then we could release x86 and x64 builds and have links to them on the Kickstarter. Kickstarter could help us get developers to work on creating a 1.9 build and other important things. As for having .deb or .rpm files I think that is a low priority, because you can always just put Nightingale in /opt.
Licensing is all GPL, so no worries there...we just have to change the app names and logos, and feathers. We could just grab a GPL license feather off of the songbird addons site for now though, if we get to the point of distributing this.

http://wiki.songbirdnest.com/Docs/Licensing_FAQ
I found some old Ubuntu patches on launchpad that will probably be helpful in making SB/nightingale use as many system libs as possible, amongst other things...

We really need an irc channel...or mailing list or something.
(09-15-2011, 06:58 PM)ilikenwf Wrote: [ -> ]I found some old Ubuntu patches on launchpad that will probably be helpful in making SB/nightingale use as many system libs as possible, amongst other things...

We really need an irc channel...or mailing list or something.

There is an irc channel - #nightingale on irc.mozilla.org

I found it in Geekshadows post form mid August.
I'll have to hop in there next time I'm working on it. Thanks for letting me know about that.
You can pop in IRC channel, I'm working on the feather, just tell me from which version of Songbird you are building off.