The Kolab development team works with a variety of external, third-party software development projects, each with their own set of semantics;
* KDE PIM uses Phabricator itself for a number of applications in their suite, meaning that any copy of the GIT repository cannot be enabled "auto-close" for on all branches.
This project is different in that we employ a forked clone of the repositories in which we branch off to store our work.
* Cyrus IMAP uses Phabricator itself.
This particular involvement is different, in that we employ no forking to work on our interests.
* Phabricator itself might receive some work, or otherwise the Sprint extension we employ.
These particular projects are different in that the timeline to deployment for us is not necessarily in line with the timeline to acceptance upstream.