Chandler is now licensed under the Apache 2.0 License
August 2nd, 2006 at 4:43 pm (1 year, 9 months ago) by Ted Leung under Chandler Desktop Development, Chandler Product News, CommunityAs of version 0.7 alpha3 of Chandler, OSAF is changing the license for the Chandler desktop product to the Apache 2.0 License (our Cosmo and Scooby codebases are already Apache Licensed). Previous versions of Chandler were licensed under the GNU GPL because we thought that we would pursue a MySQL style dual licensing scheme as part of the sustainability plans for the Foundation. We no longer plan to pursue this kind of scheme in order to acheive our sustainability goals, and we want to reduce the number of open source licenses in use at OSAF.
Those interested in the complete discussion on this topic can look at the archives of the OSAF ‘general’ mailing list: <http://lists.osafoundation.org/pipermail/general/2006-May/000248.html>
October 29th, 2007 at 4:09 pm
Hey,
My names Patrick Patience, I’m a developer over at PortableApps.com What we do their is package regular application with ‘launchers’ written in NSIS that allow the application to run from a portable device.
I think Chandler’s a great application, I was interested in making a portable version of the Windows edition for PortableApps.com. As far as I understand the Chandler logo and name are copyrighted, I was wondering if I could receive permission to use them under instruction.
I was going to start on writing the launcher shortly, and keep up with releases until the 1.0 release, when Chandler Portable Edition will be released and updated wit any future versions.
I will not release any branded version of Chandler Portable until I receive permission from the OSAF. While I am writing the ‘launcher’ for Chandler, I wanted to get some information on command line switches, etc.
Here’s my questions:
Although I’m quite sure already, where does Chandler store it’s settings, and does Chandler modify/create any other settings or files on a host PC?
Does Chandler support any -profile or -config type switches to pass the chandler settings to a different location, if not is it possible this type of switch could be implemented in a future version.
Does Chandler require any system files and specific runtimes to function?
Is there anything else specific I should know that may be a problem in making Chandler run from a portable device?
I think that’s all the questions I really have for now. I’m sure I can adjust most issues in making Chandler a portable application and I am positive I will get any other issues worked out before the 1.0 release of Chandler.
Again, I will not be modifying the Chandler source code, only making a ‘launcher’ to adjust paths, settings, etc using the Nullsoft Scriptable Install System. Also, I will not be releasing anything into beta/alpha testing until all bugs in the launcher are worked out and Chandler Portable functions properly.
Sorry for the long and someone confusing e-mail, I appreciate you here from you, and keep up the excellent work.
Yours,
Patrick Patience
October 29th, 2007 at 5:12 pm
Hi Patrick,
The best place for you to direct this is to send a note to the chandler-dev mailing list, which you can find from here: http://chandlerproject.org/mailinglists
October 30th, 2007 at 10:50 am
Hey Patrick,
Andi Vajda has already done some work on a “portable Chandler” for USB keys, so you might want to talk to him.
Reid
November 25th, 2007 at 8:55 pm
Haha, thanks guys. I must have been REALLY tired when I posted this, I have NO idea how I posted this here.
Wow, I was just googling my name, and this came up as the third result. 
I was apparently up much to late that night. 