[Kde-pim] Phabricator Project Setup
Christian Mollekopf
chrigi_1 at fastmail.fm
Wed Aug 26 10:29:00 BST 2015
On Wednesday 26 August 2015 09.51:09 Volker Krause wrote:
> 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 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.
> >
> > 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.
>
> Looks like this is already nicely picking up. And it already helped, as we
> now know the libkleo port is already taken care of, perfect :)
>
> Two more questions that came up:
>
> - How do we handle the "done" tasks? Laurent apparently already found a way
> to make them disappear, which definitely will come in handy. I was thinking
> of having a "Done" column for every currently maintained versions (ie.
> 15.08 and 15.12 or whatever the next one will be), so we can use those to
> generate changelogs for releases, and then remove those columns after the
> release?
>
You can only do that using Projects I think. Projects in phabricator are a lot
like tags, so that would be the way to go IMO.
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/
More information about the kde-pim
mailing list