Re:Give before you take – thoughts on the best way to implem...
by yangmeyer on Friday March 13, 2015 @05:20AM
(#9196254)
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.
(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?