Lydia,<br><br>Good work on this list. Looks like we've got our work cut out for us, but we've got a plan so that's excellent.<br><br><div class="gmail_quote">On Mon, Jul 12, 2010 at 1:27 PM, Lydia Pintscher <span dir="ltr"><<a href="mailto:lydia@kde.org">lydia@kde.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">Heya :)<br>
<br>
We had a very good discussion about how to improve communication to<br>
the rest of the community about our move to git. In the last months<br>
we've honestly been rather bad with that every now and then. I've seen<br>
sentences like "You're stupid because you're using SVN" and that<br>
wasn't meant in a funny way in that conversation. That's obviously not<br>
the way to win the hearts of the rest of the community.<br>
<br>
The way forward is to make it clear in our communication that git<br>
isn't perfect but brings us a huge amount of benefits. And at the same<br>
time make it clear that SVN isn't perfect for us either atm.<br>
<br>
During the bof we came up with a list of good and bad things that we<br>
need to talk about.<br>
<br>
= bad =<br>
- allows offline commits -> community splitting<br></blockquote><div><br>Sorry I missed the BoF but how does allowing offline commits lead to community splitting?<br> </div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
- move means / will mean work<br>
- move will cause disruption to workflow/projects/deadlines for a<br>
while -> pick the right time for the move to cause the least amount of<br>
disruption<br>
- steeper learning curve<br>
- repo management is needed (this was about allowing force push iirc -<br>
my notes say we need to ask sysadmin what the status of that is atm)<br>
- non-resumable checkout -> offer shipping DVD's / usb sticks<br>
<br>
= good =<br>
- enables a social workflow (for example linux kernel style<br>
development -> problem and opportunity to rethink our development<br>
model?)<br>
- lowers the barrier - increased 3rd party contributions (about x10<br>
for Amarok I'd guess)<br>
- clearer patch flow (gitorious - need to figure it out for <a href="http://git.kde.org" target="_blank">git.kde.org</a> still)<br>
- occasional contribution gets easier<br>
- offline commits<br>
- separating stuff in branches is easier -> work on many different<br>
things simultaneously gets easier<br>
- checkout size - complete history<br>
<br>
= needs doing =<br>
- document the patch flow clearly<br>
- have and advertise a helpdesk like thing where people can go if they<br>
screw up they repo - especially in the first weeks/months<br>
- document the most simple way to work with git / how to work like in SVN<br>
- find more people to write rules files<br>
- keep pushing for continuing to "commit early, commit often" and<br>
public sharing of branches<br>
- make it clear that we will need to keep an eye on communicating what<br>
everyone is working on in their branch<br>
<br>
<br>
This is by no means an exhaustive list but one that should be a good<br>
start for the next weeks.<br>
I was thinking we should start with maybe short blog articles each<br>
about one of the points above and explaining it a bit more in detail.<br>
Anyone up for that? I'm happy to help with review and other tips but<br>
I'm not feeling comfortable to write those on my own. </blockquote><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<br>
<br>
Cheers<br>
Lydia<br></blockquote><div><br>Looks/sounds good to me, maybe we should put this list on the wiki somewhere and we can put our name and/or a link next to each when we blog about the items?<br><br>Regards,<br>Jeremy<br> <br>
</div><blockquote class="gmail_quote" style="border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">
<font color="#888888"><br>
--<br>
Lydia Pintscher<br>
Amarok community manager<br>
<a href="http://kde.org" target="_blank">kde.org</a> - <a href="http://amarok.kde.org" target="_blank">amarok.kde.org</a> - <a href="http://kubuntu.org" target="_blank">kubuntu.org</a><br>
<a href="http://claimid.com/nightrose" target="_blank">claimid.com/nightrose</a><br>
</font><div><div></div><div class="h5">_______________________________________________<br>
Kde-scm-interest mailing list<br>
<a href="mailto:Kde-scm-interest@kde.org">Kde-scm-interest@kde.org</a><br>
<a href="https://mail.kde.org/mailman/listinfo/kde-scm-interest" target="_blank">https://mail.kde.org/mailman/listinfo/kde-scm-interest</a><br>
</div></div></blockquote></div><br>