[Kde-pim] Phabricator Project Setup

[Christian Mollekopf]

On Saturday 22 August 2015 11.31:38 Volker Krause wrote:
> Hi,
> 
> I've talked to Ben, the current Phabricator test setup would actually be
> usable for "production" use for task/project management for us, without
> causing the sysadmins unreasonable trouble when migrating to the full
> production deployment of Phabricator eventually.
> 
> Phabricator project layout it orthogonal to repo layout, so we can structure
> this however we want. Among other teams I see at least the following
> layouts: - single project for everything
> - a project per release
> - a project per component/module (ie. close to the repo layout)
> 
> How do we want to structure this?
> 

I'd suggest to start with a KDEPIM project only, and only create more as 
required. Release/Milestone projects can be useful for milestone planning, but 
I'd rather try to do that for the moment using the Kanboard.

> I would start with a single project to not fragment this too much, as we
> have a relatively small team actually looking into this, so everyone is
> looking at most sub-projects anyway. And should we eventually hit scaling
> limits, we can always expand this I think.

Agreed.

> 
> We of course should also talk about what we actually want to put in there.
> My current motivation is having a place to collect the tasks for getting
> more of the former pimlibs into KF5, and anything else I run into on the
> way there that we eventually should clean up/improve.

It can be IMO used for any sort of developer tasks. It should remain a 
developer tool IMO, and as such it should only contain stuff that somebody 
actually wants to work on (even if in the distant future). So it can be used 
to i.e. collect porting tasks, do roadmap planning, etc.

Cheers,
Christian
_______________________________________________
KDE PIM mailing list kde-pim at kde.org
https://mail.kde.org/mailman/listinfo/kde-pim
KDE PIM home page at http://pim.kde.org/