I just read through the license agreement that applies to everybody here and nowhere I find the word "publish" in there which surprises me a bit. How am I supposed to put code on my mbed that I don't want to share? For instance it could be a industrial secret project or just not finished code that needs to be cleaned up a bit.

Usually you don't bother about what license to publish under until after you got something working but as I understands it you need to state it *before* you write a single line at mbed.org, otherwise people can take it and use it in their own secret projects not sharing and vice versa. In theory that only applies to mbed.org since normal users don't see the code until it is published.

Wouldn't it be better to use the "publish" point as the where to put in the license? Up until then it is just your private code base... What's your thoughts on this? And yeahh, I'd like to share and will put in some LGPL license in my sources but that is really NOT what I would like to do first thing in the morning if you know what I mean.

Other than that this is the sh*t, really easy to use environment, unless you are unconnected to Internet that is....

Hi Joakim,

Sure, you can just write away; your compiler workspace is private to you.

The usage license is just making it clear that it is your responsibility to notify people of any terms you wish to attach to things you upload on the site. For example, if you publish a library to the website, it is your responsibility to add any license terms (should you choose to publish in the first place, and should you choose to attach terms such as an open source license).

We have lots of users who work totally privately. There is no requirement to share anything or apply licenses to your personal work.

So, first thing in the morning, you can concentrate on your project :)

Simon