yangmeyer

For Gemba, this could mean limiting the number of connected Git repositories. I decided against this because:

(1) some new users try out Gemba with a test repository, and needing to remove it to free up a slot for the "real" repo seems like unnecessary friction;

(2) some designers work full-time on a single product (e.g. in a startup) and would get loads of value (pushing hundreds of assets) for free and might never need to unlock unlimited repos.

Thoughts?

Uhm, duly noted and fixed. Thanks!

I wrote this. Feedback welcome.

Ole Begemann recently wrote about the changes in the context of selling apps through the App Store: http://oleb.net/blog/2014/07/eu-vat-changes-2015/

Apple sells all apps through its Luxemburg subsidiary, meaning Luxemburg's low 15% VAT rate applied.

On the buyer side, am I right to assume that as a VAT-registered company/freelancer I will be able to deduct VAT paid on apps purchased through the App Store?

There’s a whole movement around Micropreneurship, which celebrates the fact that not all product businesses need to become "the next Facebook" to be successful. It all depends on your definition of success.

http://changethis.com/manifesto/show/80.03.MicropreneurManif... http://www.startupsfortherestofus.com http://unicornfree.com

Bitbucket works for me, as long all you do is hosting a git repo there. For everything else, I agree that it feels clunkier and generally less polished than GitHub.

Point in case: I tried – and failed – to integrate Bitbucket services through their REST APIs in my upcoming Mac app (“git push assets” for designers - http://gemba.io).

After 2 fruitless days of trying to get an OAuth access token, I gave up. The Bitbucket way of doing OAuth felt weird to me, and the cluttered documentation (which felt a bit like Facebook’s developer documentation 3-4 years ago) didn’t really help.

Doing the same for GitHub was a breeze. OAuth was straightforward, and documentation was unambiguous, concise and clear.

The best thing about this "assign after payment in full" clause: It makes potential disputes about unpaid invoices a copyright infringement issue. And crucially, legal costs for copyright cases in the US are paid by the infringing party.

(IANA lawyer, but I learned this from one while contracting.)

From my experience freelancing in Germany, the standard approach there is to grant an exclusive, perpetual etc. license to your client for whatever you made under the contract, of which you as the author continue to own the copyright (Urheberrecht).

There is also Seedmatch (https://www.seedmatch.de) and FundedByMe (https://www.fundedbyme.com)