File indexing completed on 2024-12-22 05:07:43
0001 <?xml version="1.0" encoding="UTF8"?> 0002 <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01 Transitional//EN" "http://www.w3.org/TR/html4/loose.dtd"> 0003 <html> 0004 <body> 0005 <div style="position: relative; word-wrap: break-word"> 0006 <a name="att"/> 0007 <div id="attachmentDiv"> 0008 <a name="att1"/> 0009 <div id="attachmentDiv1"> 0010 <table cellspacing="1" cellpadding="1" class="signWarn"> 0011 <tr class="signWarnH"> 0012 <td dir="ltr"> 0013 <table cellspacing="0" cellpadding="0" width="100%"> 0014 <tr> 0015 <td>Not enough information to check signature validity.</td> 0016 <td align="right"> 0017 <a href="kmail:showSignatureDetails">Show Details</a> 0018 </td> 0019 </tr> 0020 </table> 0021 </td> 0022 </tr> 0023 <tr class="signWarnB"> 0024 <td> 0025 <a name="att1.1"/> 0026 <div id="attachmentDiv1.1"> 0027 <div class="noquote"> 0028 <div dir="ltr">Hi,</div> 0029 <br/> 0030 <div dir="ltr">I've talked to Ben, the current Phabricator test setup would actually be </div> 0031 <div dir="ltr">usable for "production" use for task/project management for us, without </div> 0032 <div dir="ltr">causing the sysadmins unreasonable trouble when migrating to the full </div> 0033 <div dir="ltr">production deployment of Phabricator eventually.</div> 0034 <br/> 0035 <div dir="ltr">Phabricator project layout it orthogonal to repo layout, so we can structure </div> 0036 <div dir="ltr">this however we want. Among other teams I see at least the following layouts:</div> 0037 <div dir="ltr">- single project for everything</div> 0038 <div dir="ltr">- a project per release</div> 0039 <div dir="ltr">- a project per component/module (ie. close to the repo layout)</div> 0040 <br/> 0041 <div dir="ltr">How do we want to structure this?</div> 0042 <br/> 0043 <div dir="ltr">I would start with a single project to not fragment this too much, as we have </div> 0044 <div dir="ltr">a relatively small team actually looking into this, so everyone is looking at </div> 0045 <div dir="ltr">most sub-projects anyway. And should we eventually hit scaling limits, we can </div> 0046 <div dir="ltr">always expand this I think.</div> 0047 <br/> 0048 <div dir="ltr">We of course should also talk about what we actually want to put in there. My </div> 0049 <div dir="ltr">current motivation is having a place to collect the tasks for getting more of </div> 0050 <div dir="ltr">the former pimlibs into KF5, and anything else I run into on the way there </div> 0051 <div dir="ltr">that we eventually should clean up/improve.</div> 0052 <br/> 0053 <div dir="ltr">regards,</div> 0054 <div dir="ltr">Volker</div> 0055 </div> 0056 </div> 0057 </td> 0058 </tr> 0059 <tr class="signWarnH"> 0060 <td dir="ltr">End of signed message</td> 0061 </tr> 0062 </table> 0063 </div> 0064 <a name="att2"/> 0065 <div id="attachmentDiv2"> 0066 <div class="noquote"> 0067 <div dir="ltr">_______________________________________________</div> 0068 <div dir="ltr">KDE PIM mailing list <a href="mailto:kde-pim@kde.org">kde-pim@kde.org</a></div> 0069 <div dir="ltr"> 0070 <a href="https://mail.kde.org/mailman/listinfo/kde-pim">https://mail.kde.org/mailman/listinfo/kde-pim</a> 0071 </div> 0072 <div dir="ltr">KDE PIM home page at <a href="http://pim.kde.org/">http://pim.kde.org/</a></div> 0073 </div> 0074 </div> 0075 </div> 0076 </div> 0077 </body> 0078 </html>