Notes from the Phabricator BoF

Luigi Toscano luigi.toscano at tiscali.it
Thu Jul 30 14:50:08 BST 2015


Hi all,
thanks to Victor Blazquez, here are the notes from the Phabricator BoF. Feel 
free to add your comments and corrections.


Feedback on Phabricator gathered outside the BoF from people who could not 
attend:
---------------------------------------------------------------------------------

krita
    used for everything (reviews, tasks, mockups, even bugs);
    overwelmingly positive feedback from community
    - annoyance: big unified list of projects; confusing

akonadinext
    used reviews, tasks; prefer tasks separate from bugs
    used internally in company too; also used sprint module
    - problem: in case of tasks coming from company phabricator and KDE
      phabricator, the line which reference the commit message will clash
      (same Txxxxx), a different prefix is needed 
      -> (ervin said it's not a problem), as you could use the full URL of the
         task instead of just the task ID in the commit message.
    - annoyance: few rendering/usability bugs in the kanboard view
                 with many tasks

tanglu
    phabricator developers responsive
    thousands of projects handled in tanglu (no repositories yet)
    - problem: fast development can be a problem for updates (no real 
      stable branch)

Positive feedback from Ivan (kactivities)
Positive feedback from Eike (konversation)


BoF
---------

Remove login form which is not LDAP
    - Change message and write something like "Authenticate through 
identity.kde.org"
Uses of maniphest vs bugzilla
    - No migration for now (not the foreseeable future)
Projects hierarchy (https://secure.phabricator.com/T3670)
Custom view and notifications for groups 
    - Dashboards
    - Share queries inside a group (check later)
Can we push a patch through the webpage? (keep an eye on upstream)
Do we want to reuse our CI system? https://wiki.jenkins-ci.org/display/JENKINS/Phabricator+Plugin
When a new review is posted, trigger the CI, it needs some changes to the CI
Lack of integration with CI is not a blocker
Suggestion: It would be nice not need to test every patch (CI), to be 
discussed

Support for arcanist is available for other plaftorms (Windows, MacOSx)

Good feedback in general from the people who assisted

Ciao
-- 
Luigi




More information about the kde-core-devel mailing list