On Dec 6, 2007 12:16 PM, Andy <[EMAIL PROTECTED]> wrote: > On 05/12/2007, Matthew Wood <[EMAIL PROTECTED]> wrote: > > The delay is just a > > small-team-working-on-/programmes-and-trying-to-fit-it-all-in thing. > > Any chance of explaining what the BBC actually have to do when someone > says "let's open source Y"? > It's normally a relatively simple for a small individual project > (simply adding the appropriate license file and copyright text to each > file). However I assume it is somewhat more tricky for a large > organisation. Does this have to work it's way up to high management or > are individual teams given freedom to make these decisions themselves? > > Will you be accepting bug reports and patches from people outside the > BBC or is this a "release and forget" kind of thing? (Unfortunately I > am not a Perl coder so there isn't much I can do). >
I was asked, and readily agreed to it being made open-source. (Dunno if I count as high management - http://james.cridland.net/biography ). I trust my team to make the right decision. Chatting today, we think we'll release it quickly as a .tar.gz at /opensource, and then, depending on the reaction we get, put it on a Sourceforge-or-similar site, to allow bug reports, patches, etc etc. Please do give us time to release it; I'd rather this work didn't get in the way of delivering great tools and products. As a note, this will be the second time that a member of my team has released code to /opensource; the first was a bit of Java: http://www.bbc.co.uk/opensource/projects/tv_anytime_api/ Hope that helps. //j
