It is friendly -- to end users and anyone who happily embraces the software. It may be seen as a hostile fork of SMF, though, in the sense that currently the license we chose is set to prevent SMF from re-using our implementations. Our choice of license was dictated by a few events that, while regrettable in a sense, contributed to the birth of Wedge, and its subsequent good health.
In the first two months of the project lifetime, while we were building Wedge in private, we were in touch with the SMF team and were providing bug reports and fixes that we had done in Wedge. At the time, we thought of Wedge as a "laboratory" to allow experimenting outside of the SMF codebase. Our new code was supposed to be able to be merged back into the SMF codebase.
However, after more internal conflicts with the team, we decided that the SMF team didn't do anything to deserve our help. While we can understand that many people might have thought that our apparent leaving of the active SMF community might be reason enough to blame us for whatever conflict happened between the SMF team and us, fact is, we *were* active, and actually way more active than the SMF team itself, providing many, many bug fixes and helping speed up the releases of SMF 2.0 RC4 and RC5 among other things.
In the future, when Wedge is stable enough, then we will reconsider what our final license is. But as much as we'd like to license our code as BSD, it is unlikely to happen until we feel comfortable sharing more than a few fixes with the SMF team again. I guess we can say the ball is in their camp at this point. :)
In the first two months of the project lifetime, while we were building Wedge in private, we were in touch with the SMF team and were providing bug reports and fixes that we had done in Wedge. At the time, we thought of Wedge as a "laboratory" to allow experimenting outside of the SMF codebase. Our new code was supposed to be able to be merged back into the SMF codebase.
However, after more internal conflicts with the team, we decided that the SMF team didn't do anything to deserve our help. While we can understand that many people might have thought that our apparent leaving of the active SMF community might be reason enough to blame us for whatever conflict happened between the SMF team and us, fact is, we *were* active, and actually way more active than the SMF team itself, providing many, many bug fixes and helping speed up the releases of SMF 2.0 RC4 and RC5 among other things.
In the future, when Wedge is stable enough, then we will reconsider what our final license is. But as much as we'd like to license our code as BSD, it is unlikely to happen until we feel comfortable sharing more than a few fixes with the SMF team again. I guess we can say the ball is in their camp at this point. :)