| At line 12 added 27 lines |
| After some experience with the Phabricator and other tools, here are our two cents: |
|
| Phabricator is a great tool for big organisations with a huge number of projects and developers, working together on a common target. If you would like to get an impression how big communities work together using Phabricator, please visit for example the Wikimedia (MediaWiki) Phabricator at [https://phabricator.wikimedia.org/]. |
|
| As we did not find good capabilities to measure successess or do estimations (complexity and efforts), most of us think, that is not the primary focus of the suite. |
| In our eyes it is not to drive small projects with limited budgets and a small number of developers. |
|
| Still it is a very comfortable tool to organize for example Scrum processes. |
|
| The interoperability of the several tools available in the suite is brilliant. This also is the case in terms of extensibility. |
|
| You will find for example the following applications: |
| ; Manifest: tasks and incident management, a nice mixture of Taskboards and Bugtracking software |
| ; Phriction: a Wiki application |
| ; Ponder: a kind of FAQ and Forum application |
| ; Conpherence: a browser based instant chat tool |
| ; Phame: a Blog application |
| ; Legalpad: place your NDAs, terms and conditions into written text and let users accept them in order to let them access Phabricator ressources |
| ; Diffusion: integrates seamlessly with GIT and Subversion repositories |
| ; Audit & Differential: for audits and code reviews |
| ...and lots of other usefull stuff. |
|
| A user may organize its own account into Dashboards, presenting its individual preferred contents. |
| Contents of the several applications are cross-connected. A user may flag contents for later evaluation, add the same tasks into several projects, move tasks from one project to another and may freely an so on. |
|
| There are some basic introductions into Phabricator on [YouTube|https://www.youtube.com/results?search_query=phabricator]. |
|
| At line 18 changed one line |
| ; How to get access? : If your team leader or your IT department forwards you to us, we are looking forward to help you. Please give us a short message using the [support form|http://www.okit.de/de/support/anfrage.svn-repository.html]. We will send you the account data.\\Some of our customers manage the accounts on their own. In that cases your team leader or the IT department of your company is the right one to ask. |
| ; How to get access? : If your team leader or your IT department forwards you to us, we are looking forward to help you. Please give us a short message using the [support form|http://www.okit.de/de/support/anfrage.svn-repository.html]. We will send you the account data according to the security terms of your company.\\Some of our customers manage the accounts on their own. In that cases your team leader or the IT department of your company is the right one to ask. |
| At line 22 changed one line |
| ; Is it possible to restrict access to my repository? : Yes, that is the default. Normally only the accounts you want to have access to your repository. We also support IP limitations and operating the Subversion server inside a VPN based infrastructure. Almost anything is possible... |
| ; Is it possible to restrict access to my repository? : Yes, that is the default. Normally only the accounts you want to have access to your repository. We also support IP limitations and operating the Subversion server inside a VPN based infrastructure. Almost anything is possible for our customers' convenience... |
