I know it is a PITA, but duplicating across pairs of hard drives is cheap per GB, and allows you to move the data to an offsite location / *SNL Al Gore Voice* lockbox. I have ~2TB of video project data that I store using this method.

CI was going to be my question as well, since I spend my time at work managing a multi-site Jenkins CI system for ~100 jobs.

When are they going to fix their CAPTCHA so that scammers can't get unlimited gmail accounts with which to flood my forum with bogus registrations?

well that might be cause for me to blow the dust off a reference book (or just hit up google) and try some c++ again... but it has been so long since I bothered with it.... 10years actually. but I'm also not in low level device control / OS level coding.

where as they refused to admit that solar activity had anythign to do with the ramp up. Nice. way to be consistent.

Unless you have regularly tried to chop up and burn 80GB of video data onto 4.3GB single sided discs... the idea seems ok. but after you have tried it, you realize you waste all yoru time tryign to find the individual clips that equal close to the capacity of a single DVD (assuming you chopped up the video by scenes or that your capture card correctly identified scene stops and starts to create new individual clips). I wasted hours and hours trying to take each project (roughly 80GB of data per shoot / project) and chop up the clips into groupings for each disc... and then burning the disc.... Much faster solution is either getting a drobo and maxing out the storage, or using individual drives.

Two lobbyists is considered "upping in a big way" And employes from the former administration (opposite party of who is in power)? not likely to be getting tee-times with the Oval Office, but I can see where they (article writer) might think so.

We as a developer community, and more generally as citizens, need to propose a new law in each state that specifically allows the law to catch up to recent technology by explicitly allowing these apps, their streams, and the developers to listen (not broadcast) to any public service employee radio communication (police, fire, ems, utilities, FBI, etc etc). Why? Who will watch the watchers? If watching is limited to antiquated mechanisms, then it isn't really watching. I will be contacting my state rep / sen to introduce such legislation, since I also intend to develop apps for mobile use (none of mine are related to this story... but who knows what can be wrapped up under a zealous prosecution / DA). Don't be afraid of legislation-eese and legal speak. It is just a syntax. There are rules for form of the law. Laws are just specifications. Take affirmative steps to both protect developers from prosecution due to illegal use of their app, and to protect citizens so they can effectively watch their public officers.

I operated my own video production business for 5 or so years (off and on full time). Each shoot generated about ~80GB of video footage and 15GB of renders. I used to store DVD backups, but the cost of chopping up footage is measured in hours of my time. I switched to using a SATA docking station and purchasing a 1/2 dozen 1.5TB drives. Projects & renders are copied to a pair of HDDs and that is it. Drives are used to store footage until a pair is full.

In your case you churn through a lot more footage, but do you really need to save it? Change your services and offer lifetime(1) backups with various limitations (such as the lifetime of your company.... not of the customer). or backups for 1yr, 5yr, 10yr, etc. Then bill appropriately. Factor in the cost of the external HDD pairs and then you have a decent storage mechanism AND you get paid extra for it AND your customers get even greater confidence taht you care about their productions (if they pay for it).

For the customers that don't pay, just keep a 1 month backup (in case they want additional copies) and then nuke the source (you don't need the source after all... just the finished render). If a client wants changes to the production after the source is gone, then re-bill for importing from their source footage. Their fault for not choosing an archive service add-on.

Nothing more to say other than, how is this unexpected? Governments always work in their best interests, not in the interests of their citizens.

I managed to program two parts of Bach's Fugue in C minor using the "[FREQ in Hz] [ DURATION in sec] BEEP" command and could, if I borrowed another student's 48, transfer part 2 via IR and run both mostly in sync through out the entire piece. Two devices beeping in lovely counterpoint oblivious to the unintended awesomeness they accomplished.

CI systems also provide a handy central location to track all SW dev activity for all projects. You can tie all different dev platforms (Linux, Mac, Win, etc) to Jenkins and see build stats for everything in real time. Build node fail overs are automatically handled if you have a cloud of connected build servers so hardware problems are removed from causing any interruption to your SW deployment. Even if the underlying tasks are accomplished on the individual machines by Ant, MSBuild, windows .bat, there is still a central location to track & assign everything. I used to build for a dozen different SW projects manually.... logging on to the build nodes, checking out from SVN, pulling in dependencies, and then manually calling all the VisualStudio build targets. Jenkins greatly simplifies and automates those manual tasks, even if under the hood the same tasks are performed.

Oracle is, as usual, too late. I operate a large Hudson cluster for a top 5 tech company (dozens of build nodes, quartets of backup servers, big SAN storage for all the artifacts) and we immediately jumped on Jenkins and have no plans of looking back at Hudson no matter who runs it. We are sticking with where ever Kawaguchi takes this project, as are most of Hudson's users. Given that some of our engineer's revisions and new features have been or are being rolled into Jenkins, we are not going to be wooed back by anything Oracle does (or doesn't do). I have a suspicion that a vast majority of Hudson's user base feels the same.