Quote from: coins101 on February 05, 2016, 12:46:35 AM

You should seriously think about dropping the name Armory or get permission to use it.

Armory is the name of the company, as well as the product.

I know its a pain, but its actually not covered by any open source licence, that I can see.

Quote from: gangtraet on February 05, 2016, 01:36:55 PM

Quote from: goatpig on February 04, 2016, 11:16:43 PM

Quote

I am certainly no expert on copyright law and licenses, but a sound engineering principle is KISS ("Keep It Simple, Stupid"). I can certainly understand that you prefer MIT license over GNU Affero for your own work (I agree with you here), but you should seriously consider if the extra complication of having to keep track of two different licenses is worth the trouble. In particular, once you start refactor code you will constantly have to worry about not moving code from an Affero file to an MIT file. Furthermore, the GNU licenses tends to affect the whole work, so the entire Armory will be under that license, even if people can reuse parts of the project that you alone wrote under MIT license.

Read above. I appreciate KISS but I AGPL has to go and I don't want to rewrite everything from the ground up. Phasing out the old code will be a long term effort along the course of at least 2016.

I can certainly see your point. I doubt that you will ever end with an Armory without AGPL stuff in it, but the new stuff you write will be easier to integrate into other projects with an MIT license.

Quote

I have Alan's verbal consent.

"A verbal agreement is not worth the paper it is written on." Grin

Get a GPG signed email from him. He seems to be a very trustworthy guy, but still things may change or come out of his control.

I got in touch with the share holders yesterday about the use of their trademark. I'm waiting for their decision before doing anything about that.

Quote from: RoadStress on February 05, 2016, 06:14:08 PM

Quote from: goatpig on February 04, 2016, 11:51:00 PM

No he hasn't but I expect it is off limit, and he can't do anything about it either.

What does that mean exactly? Are we able to use the latest builds found on the website or they aren't safe anymore?

It means I most likely won't have access to the bitcoinarmory.com domain, so unless ATI keeps that up to date, it will decay into obsolescence. As for the builds, it never was a matter of where you downloaded the file, rather if the hash matches the signature and the signature matches Alan's key. This has no changed for now. Once I put out my own builds, I'll make an offline signing key and reveal the public key here for all to check the builds against.

Quote from: knightdk on February 05, 2016, 02:05:11 AM

Here is a site for the project that I put together using Github Pages: https://achow101.github.io/BitcoinArmory/. It uses Jekyll (which github recommends using) and Github Pages as the hosting. The code is at https://github.com/achow101/BitcoinArmory/tree/gh-pages and if someone can get a domain, that domain can also be pointed to the site so it uses the domain. Let me know what you think about it.

I'll look into website matters once I have a release.