choosing a license

[mfrasca]

good day Brett. @RoDuth made me notice you have chosen a different license (ISC) for this alternative version of Bauble. this prevents you from using those parts from bauble.classic (GPL) where I've been working at, like for example the search tool, which I have almost completely rewritten and which in fact you have not included.
ISC in particular, but permissive licenses in general, are not licenses I would choose for a new product.
just wondering about your motivations for this choice.

[brettatoms]

I don't put much thought towards licensing. I don't care if anyone takes my code and does whatever they want with it so for me the more permissive the better. If you want to suggest some other form of licensing I'm all ears.

I haven't included anything from Bauble.classic in the this web version of Bauble other than the original parts I copied from about 1.0.11 or so of bauble.classic. I still consider this project experimental and I don't have any grand plans for it. So far I've been more concerned with getting the project structure right than individual features. It's getting close and a lot of stuff works already. I would think it would be great to incorporate all the changes you've made to bauble.classic. Also, the API parts of this project are pretty separate from the front end code so it could be easily ripped out and incorporated into bauble.classic if you wanted to go that direction.

[mfrasca]

I like the GPL, less permissive or less tolerant of abuse. My motive is the experience I've had with MacOSX and iOS: closed source based on free software with a “permissive” license. I understand you don't have grand plans, but you never know where you will end with the small plans you have.

anyhow, if you want to include anything I've written in the last couple of years (like the new query parser, which I suggest you do include), you need adopt the GPL license.