|Subject:||Re: [Qemu-devel] KVM call agenda for April 05|
|Date:||Tue, 5 Apr 2011 10:29:48 +0200|
On 05.04.2011, at 08:01, Brad Hards wrote:
Hrm. I don't even know that page. Where is it linked? Maybe it should be linked on the http://wiki.qemu.org/Contribute/StartHere page?
That's sometimes even hard for people who have been working on Qemu for ages :). I'm not sure how to improve the situation. I as a maintainer usually ask other people to take over for me when I'm off on vacation, so contributers don't get exactly that feeling. But some parts of Qemu are just plain unmaintained, so nobody feels responsible.
Yes, please add that to the wiki :). I'd also like to see the savannah one just deactivated. Last time I checked it wasn't synced, so you simply get an old snapshot which is the worst case scenario for everyone.
You don't need a public git tree. But try to imagine you're a maintainer. Usually, those people just tend to have full-time jobs and look at patches along the way. If you send in a patch set of 20 patches, it's a lot easier for them to clone your tree to at least try out the patches than to apply them manually.
So rule of thumb is: As of 5 patches, creating a git tree helps getting your patches tested/reviewed.
I usually just push my work to repo.or.cz. They offer their services for free and are available almost every time I've needed them :).
What exactly do you mean by better-practice git setups?
Take a look at http://wiki.qemu.org/Contribute/StartHere. It links to (rudimentary) explanations for QED. We don't have a full-on architectural doc though. And I'm not sure we ever will - unless people volunteer to write documentation instead of code :).
Ah, very nice! Thank you!
You certainly welcome :). And thanks a lot for helping out on the wiki!
|[Prev in Thread]||Current Thread||[Next in Thread]|