On Wednesday 02 July 2008 01:55:09 Daniel Fetchinson wrote: > > The CC attribution license would require the TG quickstart to have > > attribution information in the manner specified by the author (a link > > back to the YAML page). No big deal. But I'm pretty sure it would also > > require that TG users don't rip that attribution link out of their page > > template -- which would be a burdensome requirement of an otherwise > > permissively-licensed (MIT -- just leave the copyrights in the source > > files) project. > > This is indeed quite annoying and maybe will stop tg from using yaml after > all. On the positive side, not every page has to contain a backlink, > quoting from yaml.de: > > "For the free use of the YAML framework, a backlink to the YAML > homepage (http://www.yaml.de) in a suitable place (e.g.: footer of the > website or in the imprint) is required." > > Which I understand to mean that it is enough to link back to yaml.de > on a single page (e.g. imprint page) for the whole web site. > > What is not clear to me from > http://www.yaml.de/en/license/license-conditions.html is what are the > conditions of redistribution for a non-commercial situation. Say a > backlink is provided on turbogears.org can the tg team bundle yaml for > download in the tg distribution? If yes, tg users are required to add > a backlink? Are they required to know that tg contains something which > requires this?
So far we are 100% free to write opensource and commercial code. So far we are not required to recognize that we are using a specific framework (and believe me, it is easier to add a new thing to some environments when absolutely nothing changes visually from what was there before, specially to big corporations). I see this addition as a drawback to using TG and my vote is -1 to anything that makes this a concern. If we are having problems figuring it out and would have to "hire a lawyer" to check, then what would take this requirement from our users? Our word? I don't believe that we are here to support anyone's business decision, specially if one day we might be questioned about the endorsement. So, -1 from me to add this. Make it an external project, make it a module... But never a dependency or requirement for any application where the author himself / herself didn't ask for it. -- Jorge Godoy <[EMAIL PROTECTED]>
signature.asc
Description: This is a digitally signed message part.
