On 04/12/2007, vijay chopra <[EMAIL PROTECTED]> wrote:
> I expect the BBC will use an in house licence to fit it's needs as set out
> in the charter.

I'd be surprised at an inhouse license being created, since its not happened 
before. Choosing a license to fit charter/business needs/the community 
targeted at/the team's personal preference, doesn't need a new license :-)

The closest I've come to this is when we drafted a contributor agreement for
Kamaelia (on the website if curious) - which we used for Summer of Code
contributions. Even then despite the need for a contributor agreement (to
protect contributors & the BBC), there was significant pushback for 2
reasons:

   * The lawyers thought we were asking for too many rights over the code. (we
      ask for less than the FSF ask for the GNU project though, because we
      just ask for a license that allows relicense as MPL/GPL/LGPL to ensure
      the person who goes after violations is the BBC (in a similar way the
      FSF can for GNU). When I pointed out that this is a benefit for
      contributors and that contributors would however retain full rights over
      their own code, they became happier.

   * They didn't particularly want to risk license proliferation or going
      outside industry norms (our agreement is based on the python
      community's agreement, just with necessary minimum changes)

BBC legal were really nice & helpful BTW, and really interested in not doing 
the wrong thing, and really interested (as am I) in not going too far. We 
also provided people a mechanism of contributing without a contributor 
agreement as well.

On Wednesday 05 December 2007 11:48:48 Dave Crossland wrote:
> I strongly hope that the BBC will not contribute to the problem of
> license proliferation.

http://www.bbc.co.uk/opensource/licensing.shtml

Gives an overview of licenses the BBC has used in the past.


Michael.
-
Sent via the backstage.bbc.co.uk discussion group.  To unsubscribe, please 
visit http://backstage.bbc.co.uk/archives/2005/01/mailing_list.html.  
Unofficial list archive: http://www.mail-archive.com/[email protected]/

Reply via email to