* merge conflict resolution: It definitely looks cool and make conflict resolution BY MERGING easier than any other way i know BUT most of the time I want my co-worker to resolve conflict BY REBASING (i.e as if they had branched just right now) , following the principle that you merge from specific to generic. So though I definitely agree most of people don't care, but for larger team/project where you often need to make archeology and dig inside the commit history , the "master merged into feature branch" makes the commits tree look weird
Outside of this, it's maybe only me, but most of the team I've worker with where using a scrum-like taskboard (like http://taiga.io ) instead of a kanban-like, is it planned to be added/provide the option or (which I perfectly understand) do you plan on focusing on kanban and letting third-party project for those who prefer scrum ?