Sure, we'll connect off-list. Welcome to the project! On Tue, Oct 19, 2021 at 11:54 AM Sandro Bonazzola <sbona...@redhat.com> wrote:
> Welcome Maithreyi! > I have a first task for you :-) > Please go to https://ovirt.org/develop/ and let me know when you don't > know what to do next. > About contributing code, there are several python based sub-project within > oVirt, but first I would recommend to see it running and identifying the > area you would like to contribute to. > +Sanja Bonic <sbo...@redhat.com> would you like to peer for the > onboarding? > > > Il giorno mar 19 ott 2021 alle ore 11:40 Nir Soffer <nsof...@redhat.com> > ha scritto: > >> On Tue, Oct 19, 2021 at 10:44 AM Maithreyi Gopal >> <maithreyi.go...@gmail.com> wrote: >> >> Welcome Maithreyi! >> >> > On Tue, Oct 19, 2021 at 9:14 AM Yedidyah Bar David <d...@redhat.com> >> wrote: >> ... >> >>> I am Maithreyi Gopal, from Nuremberg, Germany. I am looking to start >> contributing to open source projects and would like to introduce myself to >> you. >> >>> >> >>> I have a lot of Software Development Experience to offer. I have a >> few years of experience working with infrastructure teams on the Cisco >> ASR9k routers. I have a Masters in Networking and Design >> >>> I currently work on developing drivers and communication protocols >> for image transfer at Siemens Healthcare. >> >> If you are interested in image transfer, maybe you would like to check the >> ovirt-imageio project? >> https://github.com/ovirt/ovirt-imageio >> >> It can be a good opportunity to learn about python, HTTP, NBD, testing, >> incremental backup, and storage. >> >> It is not very useful without oVirt (yet), so if you look for something >> you >> can use yourself now, this may not be the best option for you. >> >> The project provides a server and client for transferring disk images >> to/from oVirt. This project enables oVirt incremental backup API, >> importing VMs to >> oVirt (e.g. via virt-v2v) and exporting VMs to other systems (e.g >> openshift virtualization). >> >> This is a relatively small code base (14694 lines of python, 193 lines >> of C) with very >> good test coverage (~90%), and relatively clean code. >> >> The most important task we have at the moment is creating a command line >> tool replacing lot of example scripts from the oVirt python SDK: >> https://bugzilla.redhat.com/1626262 >> >> Another small task that may fit new contributors is supporting standard >> NBD URL >> syntax: >> https://bugzilla.redhat.com/1849091 >> >> Future ideas that we are thinking about: >> - Multithreaded checksums ( >> https://gerrit.ovirt.org/c/ovirt-imageio/+/113379) >> - Go client library >> - Using libnbd library instead of our own NBD python library >> - Packaging the project for more distros (Fedora, Debian, ...) >> - Migrating the project to github or gitlab >> - Making it useful outside of oVirt >> >> Like most other projects, we always need help with improving documentation >> and automated testing. >> >> You can start here: >> http://ovirt.github.io/ovirt-imageio/development.html >> >> >>> I want to be able to use my background to start contributing to open >> source and learn new technologies. I come with no prior open source >> contributions. If somebody is willing to point me in the right direction >> and probably help me with an easy first contribution, I would really >> appreciate it. I am most proficient in C and python. >> >> >> >> >> >> Do you use Open Source in your daily work? At home? Elsewhere? Do you >> use oVirt? >> >> >> >> Personally, I think it's best to start contributing to software you >> actually use. >> >> This works great for me, in a way; I never contributed to Chrom or vim, >> which >> are the projects I used most of the time, but I did contribute to >> projects used >> by oVirt, like python, sanlock and qemu. >> >> >> If you are interested in oVirt, you should probably start by looking >> around https://www.ovirt.org/develop/ . >> >> >> >> If in "easy first contribution" you refer to a code change/patch, then >> I might warn you that it's not really that "easy", if you have no >> experience with oVirt and related technologies as a user, first. I think it >> took me around a month, back then... >> >> Contributing to ovirt is certainly not easy, but with some help and by >> focusing >> on specific area it can be. >> >> Nir >> _______________________________________________ >> Devel mailing list -- devel@ovirt.org >> To unsubscribe send an email to devel-le...@ovirt.org >> Privacy Statement: https://www.ovirt.org/privacy-policy.html >> oVirt Code of Conduct: >> https://www.ovirt.org/community/about/community-guidelines/ >> List Archives: >> https://lists.ovirt.org/archives/list/devel@ovirt.org/message/4SC5CVSY6KXF3ANDII2ONA3D7YKRIG2Z/ >> > > > -- > > Sandro Bonazzola > > MANAGER, SOFTWARE ENGINEERING, EMEA R&D RHV > > Red Hat EMEA <https://www.redhat.com/> > > sbona...@redhat.com > <https://www.redhat.com/> > > *Red Hat respects your work life balance. Therefore there is no need to > answer this email out of your office hours.* > > >
_______________________________________________ Devel mailing list -- devel@ovirt.org To unsubscribe send an email to devel-le...@ovirt.org Privacy Statement: https://www.ovirt.org/privacy-policy.html oVirt Code of Conduct: https://www.ovirt.org/community/about/community-guidelines/ List Archives: https://lists.ovirt.org/archives/list/devel@ovirt.org/message/ICWM2UWFAEGXDFL4S7EPO5DHGEVFMZTT/