<div class="gmail_quote">2011/2/27 David Edmundson <span dir="ltr"><<a href="mailto:david@davidedmundson.co.uk">david@davidedmundson.co.uk</a>></span><br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div>I can pull the latest code now too. </div><div><br></div><div>Do you see the code there at present as the future final contact list, or simply experimentation of prototype designs and ideas? </div></blockquote><div>
<br>
</div><div>I'd say the future final one, I guess it could stay there until it reaches some point of good usability, is it ok?</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><br></div><div>
<div>May I suggest:</div><div> - Have a wiki page listing all the tasks to be done. (we have a wiki page here, as new maintainer it's yours now - <a href="http://community.kde.org/Real-Time_Communication_and_Collaboration/Components/Buddy_List" target="_blank">http://community.kde.org/Real-Time_Communication_and_Collaboration/Components/Buddy_List</a> please edit this, and make as many other pages as you like0</div>
</div></blockquote><div><br></div><div>Ok, I'll tak care of this.</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div>
<div><br></div><div> - Decide on some committing policy for your branch (should we email patches to you to merge) or just everyone start pushing to master (which would get messy if we get more people involved)</div></div>
</blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div>
<div><br></div><div> - At some point when we're happy with what we're doing can I suggest we stop adding new features and focus on getting it merged into our main tree. </div></div></blockquote><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div><div> </div><div>I'd quite like to get this merged into our main tree sometime soon, as it's working far better than what is currently there, and we can start using reviewboard and such.</div></div></blockquote>
<div><br></div><div><meta http-equiv="content-type" content="text/html; charset=utf-8">Emailing patches could get too complicated for both sides, so let's leave it at open commit policy for now, there are only three of us working on it at the moment anyway. Should more people get involved, then I'll start enforcing some policy :P But I hope, that it will get merged to the main tree sooner than that and after that there's the reviewboard. So for now, just push your code, I'll track the web log.</div>
<div><br></div><div>Marty</div><div> </div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;"><div>
<div><br></div><div><div class="gmail_quote">2011/2/26 Martin Klapetek <span dir="ltr"><<a href="mailto:martin.klapetek@gmail.com" target="_blank">martin.klapetek@gmail.com</a>></span><div><div></div><div class="h5">
<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<p>Should be back up, go commit! :)</p>
<p>Marty</p><div><div></div><div>
<div class="gmail_quote">On Feb 26, 2011 3:08 AM, "David Edmundson" <<a href="mailto:david@davidedmundson.co.uk" target="_blank">david@davidedmundson.co.uk</a>> wrote:<br type="attribution">> In the worst case, just commit to a scratch repository. It doesn't have to<br>
> be a clone.<br>> <br>> 2011/2/25 Martin Klapetek <<a href="mailto:martin.klapetek@gmail.com" target="_blank">martin.klapetek@gmail.com</a>><br>> <br>>> Hi,<br>>><br>>> My git repo got broken and I can't create a new clone due to "major<br>
>> breakage" of kde git clone features. The sysadmins are aware of this and are<br>>> already working to get my clone back up (so they told me ;), so please just<br>>> hold your commits for a little while, I'll let you know the second it's back<br>
>> up;)<br>>><br>>> Marty<br>>><br>>> _______________________________________________<br>>> KDE-Telepathy mailing list<br>>> <a href="mailto:KDE-Telepathy@kde.org" target="_blank">KDE-Telepathy@kde.org</a><br>
>> <a href="https://mail.kde.org/mailman/listinfo/kde-telepathy" target="_blank">https://mail.kde.org/mailman/listinfo/kde-telepathy</a><br>>><br>>><br></div>
</div></div><br>_______________________________________________<br>
KDE-Telepathy mailing list<br>
<a href="mailto:KDE-Telepathy@kde.org" target="_blank">KDE-Telepathy@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-telepathy" target="_blank">https://mail.kde.org/mailman/listinfo/kde-telepathy</a><br>
<br></blockquote></div></div></div><br></div></div>
<br>_______________________________________________<br>
KDE-Telepathy mailing list<br>
<a href="mailto:KDE-Telepathy@kde.org">KDE-Telepathy@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-telepathy" target="_blank">https://mail.kde.org/mailman/listinfo/kde-telepathy</a><br>
<br></blockquote></div><br>