License question about EventBroker

15 views
Skip to first unread message

svroonland

unread,
May 2, 2012, 10:03:11 AM5/2/12
to bbvcommon
Hi,

I am looking into using the - from what I can tell so far excellent -
EventBroker library for a commercial application. The source code
mentions that it "contains software [..] from Microsoft". I noticed
that you have included the Microsoft license in your source
distribution.

Can you tell me what the consequences of using the EventBroker library
would be, concerning the Microsoft license?

Do I need to distribute the MS license along with my own license for
example?

What about the other libraries such as the State Machine?

Thanks in advance for your reply,

Steven

Urs Enzler

unread,
May 2, 2012, 2:23:43 PM5/2/12
to bbvc...@googlegroups.com
Hi Steven

Can you tell me what the consequences of using the EventBroker library
would be, concerning the Microsoft license?

Simple answer (no lawyers involved): as long as you do not change the code or pass the source code on, you do not need to include the license. When you change the code and share the code, you have to include the license as we did it in the library.

Complex answer: ask a lawyer
 
What about the other libraries such as the State Machine?

All other components are simply licensed under Apache 2.0. Details here: http://www.apache.org/licenses/LICENSE-2.0.html
For short: as long as you deploy the components unchanged, we really don't care. When you redistribute the source code, you have to add a notice where the source code come from and your changes should be marked as such (different header for example).
 
A last note: we are currently renaming the project to Appccelerate (www.appccelerate.com). It is not yet officially released, but there is a stable pre-version available through Nuget.
One thing that will change is, that because the event broker code changed dramatically since when it was inspired by the work done by Microsoft. We no longer contain code of the CAB and therefore can remove this license part completely.
There are also some minor improvements in the state machine and other components, and better documentation.
We are in the clean up phase and hope to be ready for the official release by June. Therefore, I suggest you start directly with Appccelerate instead of bbv.Common.

I hope that cleared things up. Otherwise feel free to ask.

Cheers
Urs
Reply all
Reply to author
Forward
0 new messages