Seadragon Ajax License?

This is not the official legal word (we're working on that), but the general idea is that you can use it for your own purposes, commercial or non, but nothing illegal (i.e. nothing that would get Microsoft in trouble, such as porn, hate speech etc.). We do prefer that you use our hosted version rather than copying it yourself.

Can you tell us why you would prefer to use your own copy of the library file? For that matter, do you have other specific licensing concerns?

Ideally it would be available under an OSI approved license ( http://www.opensource.org/licenses/al... ), as opposed to the proffered morality clause example. Microsoft currently has two osi approved licenses extant, either of which would be an excellent choice (imo). That would clarify usage restrictions and ability to modify the code as needed for deployment.

As regards using a hosted version, one of the things I need to ensure for any sites deploying it would be accessibility, which is not currently present, hence modifications would be needed (although this should be possible without source modification). But as with any software, the possibility remains that either functional changes or bug fixes might be needed for a particular deployment.

Additionally I'll be hosting static files for this application/site using akamai's cdn (global site audience), and to me that's preferable for an end user experience than the unknown resources that might be available at seadragon.com.

Another example ( albeit one i don't have in my current usage scenario) might be using it within an ssl site, pulling in non ssl resources from a third party site, could lead to confusion among end users if the site is really secure.

I would of course like to be using the latest version, and it appears that the hosted version ( which is only available in minimized form) has already had several versions incremented over the composer released version (0.8 vs 0.5.x), but its hard to assess given the minimized form what has functionally changed. Making the development version of the current hosted version available would be preferred, both to enable modification if nesc. and to assess changes.

Moreover its a simple control issue, in delivering a production system, deploying dependencies on external managed resources without certainty regarding both their availability and immutability, would be poor due diligence on the part of a developer, as changes to either could result in breakage.

Additionally if its available under an OSI license, I'd be interested and willing to contribute back any enhancements made ( accessibility, cross platform tile cutting, etc).

Thanks for all the good points! We need to get this all sorted out, and we'll let you know when we have an official license. In the meantime, I hope you can continue your development.

Hello there! Nice piece of software! But we need to know if we can rely on continued use for our projects, or if some day the license will turn out to be not so friendly. Right now I see 'all rights reserved' on the source code, besides the Microsoft Copyright banner.

Free as in beer? Free as in freedom? Not free at all?

I think that such an statement is a big milestone in Seadragon Ajax project. I feel that, without such an statement, the code is nothing but an ad. A very cool one though.

Kind regards!

I look forward to the license question. I do hope it gets resolve in an expedient manner!

Has there been any progress on the license topic?

The primary concern for us is running on a closed intranet. Many of our customers simply do not have access to public web sites.

Second to that, and mentioned by someone else, is SSL/general security. Pulling pieces in from public web sites simply isn't an option for many of our customers.

OSI would be nice but isn't a requirement for us.

Thanks,
-Mont

we really need to know if seeddragon Ajax is going to be a commercial Product or an open source like product.
I mean this is a very simple question. We don ́t need to know the specific licencing model.
It can ́t be to hard to decide if you intent to make money with it or not. This is a very nice piece of code an it would be absolutely understandable if charge some money for it.
But if this is the case we need an idea of how much.
Thanks,
philipp

any official word on this yet? Any word on when there will be an official word?