Tango vs Phobos

[Walter Bright]

Sean Kelly wrote:
> Unfortunately, for this to be resolved it requires cooperation from both
> sides.  It takes two to Tango, as they say (sorry, bad joke).

For my part, I have explicitly allowed the Tango team to look at, use 
and incorporate any part of Phobos into Tango without prejudice and 
release it under the Tango license (excluding stuff that I didn't write 
that has its own copyright license terms). A lot of the new stuff, such 
as the array op code are even in the public domain to make it super easy.

In order for Phobos to move towards compatibility, I need a reciprocal 
statement from the Tango team. The Tango license does not allow this, 
and I try to be very careful in making sure Phobos is clean from a legal 
standpoint.

Sean and Don have been most generous in offering such, but the rest of 
the Tango team have not been willing to, and they have every right to 
not do so, but it does stand in the way of cooperation.

P.S. The reason for the relicense when code is transferred is to avoid 
the untenable situation of one module in the library having different 
licenses for different sections of code.