And this in turn could be presented on an agreement page (if the package was in, say, Ubuntu's Universe repo)?
Or an agreement reached on behalf of end users if the plugin was distributed through Canonical's Partner repo, for instance? (Think Firefox on Ubuntu) ----- Original message ----- > On Wed, Jun 16, 2010 at 09:57, Stuart Clark <stuart.cl...@jahingo.com> > wrote: > > [I know such information doesn't help for open source projects, but it > > would be interesting to know the level of the monetary/contractual bar > > to people wanting to do things officially, and what effect doing so > > has on their products] > > > > > If they did it right then it would be a help (of sorts) to Open Source > projects and everybody would be happy. All that's needed is a website > where there's a form that includes an all import "I agree to the terms > and conditions" tick box and then everyone who uses an open source > project could individually get their own tables. > > This would be pretty much identical to how a lot of Open Source > projects that connect to Web Services that need a developer API key > work. > > Scot > - > 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/backstage@lists.bbc.co.uk/
