On Sat, 31 Dec 2011, Ian Wild wrote:

Actually it says Trac either needs to switch to Apache license or cannot use any code from the fork. This is the opposite of what you say.

"Carrying changes back and forth will still allow the overall package to be delivered under a permissive license. It is simply that parts will be BSD and parts will be ALv2."

Where does that say that Trac would need to switch to an Apache license to use code licensed under ALv2?

When a file-based license situation is impossible, then you will need to stick to one license. As BSD can become ALv2, but ALv2 cannot become BSD, the Trac product must be ALv2 when code is copied.

Even when really doing file-exact licensing (and believe me, nobody really wants this), each copied patch would change one more file into ALv2 - in the end everything would be ALv2.

The is only one situation, where dual licensing works: When all code is released under both licenses.

As Felix already said, maintaining license on file level is impossible
and also would prevent structures or functions to be copied - normally patches do not consist of singular files.

Assuming the Trac project wants to take Apache Bloodhound code, why is shipping the Apache v2 license file and adding an appropriate attribution in the form of a boilerplate to any file that contains Apache licensed code 'impossible'?

Ok. It is not "impossible". It is "undoable". A programmer is no lawyer and nobody I know doing software development in his free time wants to care for this. The result would be that after probably one year of copying code the license situation would be so confused, that nobody knows which files are licensed how. Again the result would be to switch everything to ALv2.

I know the trouble I had with JOSM to find out whether the code is "GPLv2+" or "GPLv2 only", which is a major difference and this is only one license.

Ciao
--
http://www.dstoecker.eu/ (PGP key available)

--
You received this message because you are subscribed to the Google Groups "Trac 
Development" group.
To post to this group, send email to trac-dev@googlegroups.com.
To unsubscribe from this group, send email to 
trac-dev+unsubscr...@googlegroups.com.
For more options, visit this group at 
http://groups.google.com/group/trac-dev?hl=en.

Reply via email to