Damans227 commented on issue #4825: URL: https://github.com/apache/cloudstack/issues/4825#issuecomment-1030916428
Hi @harikrishna-patnala and @rohityadavcloud I find this issue fascinating and would like to submit a proposal to pursue it as a GSOC mentee for 2022. I am an open source enthusiast, and have been actively contributing to various cloud related projects such as Kubernetes, AWS, Trino, and Cloud Stack itself. I started [contributing to cloud stack last year](https://github.com/apache/cloudstack/pulls?q=+is%3Apr+author%3ADamans227+), and have been doing frequent mechanical changes in the `VueJS` based frontend since then. I have had the honour of meeting a few contributors of the CloudStack project at last years **CloudStack Collaboration Conference**, and I plan on showcasing my work in the CloudStack Community at the same conference this year. I am passionate about the cloudstack project and have been ramping up my knowledge gradually since I got involved. Following is some progress I have made so far: - Read through chapter 1 and chapter 2 of the[ hackerbook. ](https://github.com/shapeblue/hackerbook) and I undersatnd the importance of [asking questions the smart way](http://www.catb.org/esr/faqs/smart-questions.html). - Deployed an experimental cloudstack server on digital ocean ubuntu server.(@rohityadavcloud [raspberry blog](https://rohityadav.cloud/blog/cloudstack-rpi4-kvm/) was very helpful in doing so) - Watched a lecture on CloudStack architecture lecture from [Chiradeep on YouTube ](https://www.youtube.com/watch?v=D1K_8rvDhic&ab_channel=cloudstack) - Planning on setting up a home lab for cloudstack on an intel NUC. - Learning fundamentals of KVM, QEMU, and LIBVIRT. - I am already on the `dev` and `user` mailing list of CloudStack Contributors. So, I am currently going through requirements for this issue and would post questions I may have shortly. In the interim, if you may have questions or feedback for me, please feel free to lemme know. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
