On Thu, Apr 30, 2020 at 03:14:09PM -0400, Laine Stump wrote: > Here are two things that would help enable me to make useful contributions: > > > 1) a basic "source tree for a go library" setup in a libvirt-subproject on > gitlab (since gitlab is the official location of libvirt projects now), > including basic commit and CI hooks/test cases. I'm guessing we could > borrow/steal a lot from what was done by the people who participated in > "virt-blocks" last fall. Andrea - any advice/suggestions to give here? > > (A side question - should we put it under the libvirt umbrella on gitlab > right away? Or play around in personal trees at first and then later fork it > into an official libvirt project?) I intended it to be under libvirt project right from the start, and have indeed already created the repos & CI. There is no reason to hide it away in private repos. It is fine for the official repo to have zero guarantee of stability in the early days. > 2) a more concrete idea of what the API should look like. This is always the > toughest part for me, since it is what the rest of the world sees, so it > needs to be intelligible and capable of expansion, and I have a long history > of making questionable choices that come back to haunt me (and everybody > else! :-P). Since danpb has made good decisions in this area in the past > (and since the original proposal is his), I'm thinking/hoping he can help > provide direction to minimize mis-steps (on the other hand, I know he's > really busy, so maybe he was just hoping that someone else would grab up his > proposal and run with it). Yep, this is what I'm fleshing out an API skeleton for now. Regards, Daniel -- |: https://berrange.com -o- https://www.flickr.com/photos/dberrange :| |: https://libvirt.org -o- https://fstop138.berrange.com :| |: https://entangle-photo.org -o- https://www.instagram.com/dberrange :|
