$1000 Bounty For Podcasting on the Neuros
PDA_Monkey writes "Neuros Audio, makers of the Neuros Digital Audio Computer and the Neuros MPEG-4 Recorder, have announced on their open development blog that they will pay $1,000 USD to the first developer to enable sending and receiving podcasts from/to the Neuros."
So what they are basically doing is offering $1000 to a contract worker to develope their project, but making it out as a competition and the pay is a prize. Genius.
A pod cast combines RSS, blogging, and mp3/aac: basically, an RSS feed reader picks up the URI for the mp3 file, downloads it automatically, then hands it off automatically to the music synching program which itself automatically synchs it to the player. The point is that once you subscribe to a podcast, it magically appears on your player the next time you synch the player after a new edition. The reason folks call it a "podcast" rather than just an "mp3cast" is because it is very easy for software on the client computer to stick something into iTunes for synchronization. So that's basically what Neuros wants: a program that will automatically download and synch mp3 files on a schedule.
It's not actually downloadable, as such. Podcasts are supposed to be fed into iPod (or the like) automatically. I presume, you have to hook it up to your PC first.
You can think of Podcasting as digital radio, that allows you to play the broadcasts over and over again, (kinda like tivo, only for audio).
Maybe if they could allow linkbacks to add commentary to the original? Sort of like MST3K for podcasting...
One line blog. I hear that they're called Twitters now.
People are complaining about this off the bat.
...
/. "Developers", so it gets about 1% the traffic of a normal post, its not exactly a marketing coup.
... a developer doing this on their own (which likely would have happened eventually assuming Neuros users care about podcasting) for nothing or have the company say "hey, while you're doing all this free stuff, try this and if it works we'll pay ya for it"?
... well .. I'm procastinating because I'm still pissed). I have never worked for DI nor have I developed anything for it (I'm thinking of getting back into it, but my SqueezeBox is also a tempting hack target). Point is ... I know the product and the company. Those who don't shouldn't make comments about things they don't know about.
1) Yeah, you have to own a Neuros first to even develop this.
2) Yeah, you could look at this like Neuros is changing contract pay to a prize.
But
A) No one said you personally must participate -and- the neuros community has alot of developers. This was targetted as a bonus for existing Neuros owners who develop, not to try and snooker a bunch of non-Neuros-owning people. Face it, it got put on
B) Which is better
NOTE: Yes, I own a Neuros (had 2 until one was stolen) and yes I know the owners of Digital Innovations which created the Neuros and when I had the time I was even helping them start to open source parts of the Neuros. However, I don't use my Neuros right now (when the other got stolen they got my upgraded drive and both sync cables and
It is more productive to voice thoughtful opinions (reply) than to judge (moderate) others.
Well, this really is something of an experiment. We'll see how it goes. We're certainly not averse to paying contractors or developing stuff in house, but we figured we'd throw this out there and see what happens. This way we don't have to choose a developer based on a resume and anyone can take a shot at it.
Honestly, it might wind up a horrible failure, and we'll learn something from that too.
What works and doesn't work in encouraging open source development is a tricky issue and honestly the best way to figure it out is through experimentation and trying a lot of different things.
If you're going through hell, keep going -Winston Churchill
I have the same basic question (Say, do any of these not suck?!), but I've found a few of interest to me by sampling from the many programs listed at ipodder.org.
... follow Sturgeon's Law. However, if you don't run into any you like of the home-grown, awkward-talkin' variety, there are a lot of radio shows that are using the same system, which turns your portable player (with some large limitations, don't get me wrong) into a pretty flexible delayed-access radio :)
The vast majority, as you have found
Now, since you can only get *new* shows while you're tethered, it lacks some of the portability / immediacy of actual broadcasts; them's the breaks.
timothy
jrnl: http://tinyurl.com/c2l8yr / foes: http://tinyurl.com/ckjno5
As decribed in your blog post, the bounty seems to encourage a single hacker to work at producing a solution. This has the potential for pitting hackers against each other and potentially putting sharing of information at risk. (eg. a team collaborating and developing in the open has their their work submitted at the last minute by a third party.) By encouraging solitary work you appear to be discouraging free software's main competitive advantage: collaboration.
Wouldn't it be better to figure out a way to encourage a team of hackers to collaborate, in an open forum, to come up with a solution?
One method might be to remove personal gain from the equation, by offering a sizeable donation to a suitable free sofware project as a 'reward'.
I'm sure others can come up with much better suggestions.
In a related vein, are you going to attempt to quantify any substantial contribution made by a prexisting third party project?
By your argument then Linux and Open Office are a total waste as well.
The whole idea behind open source is to add features to your hardware. Frankly if I had a Neuro I would be interested in trying to win it. Podcasting is not all that hard. You can find RSS libs for most languages. This would make a great project for some high school or college kid. This is not supposed to be a job after all it is a prize. What I do not get is the venom and negative attitude. Are you Steve Jobs? I mean I have used a friends iPod and it is okay but I do not find it the end all and be all.
See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
Well, I think one ideal situation is that we help sponsor the establishment of a non-profit (that is not controlled or run in any way by us) and then we can make donations back to that, and they can disperse equipment and even compensation from there. Like anything, that organization will need a strong leader, and ideally should be someone independent from us. Nothing runs itself and leadership by comittee is no less a disaster in open source than anywhere else.
Regarding quantification of substantial contributions, yes we're certainly going to do that, and actually we need to be more aggressive in and systematic in doing that. Right now, we vaguely pay attention to who's contributing and make sure we give them free stuff if it comes up, but to your point, Its not very systematic and frankly, I'm sure we're missing some dedicated folks that haven't raised the issue.
If you're going through hell, keep going -Winston Churchill