[Kde-pim] Phabricator Project Setup

[Volker Krause]

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?

Kanban Kevin, I'm especially looking for your input on this :)

- So far I just have been dumping a few entries of my todo list in there, with 
limited amount of details, for my own use. If there is interest in more 
details for others to pick up tasks, I'm happy to do that as well of course, 
all my tasks in the backlog column aren't started yet and could just as well 
be picked up by somebody else.


regards,
Volker
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 173 bytes
Desc: This is a digitally signed message part.
URL: <http://mail.kde.org/pipermail/kde-pim/attachments/20150826/ee37c617/attachment.sig>
-------------- next part --------------
_______________________________________________
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/