blob: 50eddaa648909507dafa1a40978e955e25f130f6 (
plain)
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
|
<?xml version="1.0" encoding="UTF8"?>
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd">
<html>
<body>
<div style="position: relative; word-wrap: break-word">
<a name="att"/>
<div id="attachmentDiv">
<a name="att1"/>
<div id="attachmentDiv1">
<table cellspacing="1" cellpadding="1" class="signWarn">
<tr class="signWarnH">
<td dir="ltr">
<table cellspacing="0" cellpadding="0" width="100%">
<tr>
<td>Not enough information to check signature validity.</td>
<td align="right">
<a href="kmail:showSignatureDetails">Show Details</a>
</td>
</tr>
</table>
</td>
</tr>
<tr class="signWarnB">
<td>
<a name="att1.1"/>
<div id="attachmentDiv1.1">
<div class="noquote">
<div dir="ltr">Hi,</div>
<br/>
<div dir="ltr">I've talked to Ben, the current Phabricator test setup would actually be </div>
<div dir="ltr">usable for "production" use for task/project management for us, without </div>
<div dir="ltr">causing the sysadmins unreasonable trouble when migrating to the full </div>
<div dir="ltr">production deployment of Phabricator eventually.</div>
<br/>
<div dir="ltr">Phabricator project layout it orthogonal to repo layout, so we can structure </div>
<div dir="ltr">this however we want. Among other teams I see at least the following layouts:</div>
<div dir="ltr">- single project for everything</div>
<div dir="ltr">- a project per release</div>
<div dir="ltr">- a project per component/module (ie. close to the repo layout)</div>
<br/>
<div dir="ltr">How do we want to structure this?</div>
<br/>
<div dir="ltr">I would start with a single project to not fragment this too much, as we have </div>
<div dir="ltr">a relatively small team actually looking into this, so everyone is looking at </div>
<div dir="ltr">most sub-projects anyway. And should we eventually hit scaling limits, we can </div>
<div dir="ltr">always expand this I think.</div>
<br/>
<div dir="ltr">We of course should also talk about what we actually want to put in there. My </div>
<div dir="ltr">current motivation is having a place to collect the tasks for getting more of </div>
<div dir="ltr">the former pimlibs into KF5, and anything else I run into on the way there </div>
<div dir="ltr">that we eventually should clean up/improve.</div>
<br/>
<div dir="ltr">regards,</div>
<div dir="ltr">Volker</div>
</div>
</div>
</td>
</tr>
<tr class="signWarnH">
<td dir="ltr">End of signed message</td>
</tr>
</table>
</div>
<a name="att2"/>
<div id="attachmentDiv2">
<div class="noquote">
<div dir="ltr">_______________________________________________</div>
<div dir="ltr">KDE PIM mailing list <a href="mailto:kde-pim@kde.org">kde-pim@kde.org</a></div>
<div dir="ltr">
<a href="https://mail.kde.org/mailman/listinfo/kde-pim">https://mail.kde.org/mailman/listinfo/kde-pim</a>
</div>
<div dir="ltr">KDE PIM home page at <a href="http://pim.kde.org/">http://pim.kde.org/</a></div>
</div>
</div>
</div>
</div>
</body>
</html>
|
