New contributor: Interested in helping with cloud-init #6367
-
|
Hi maintainers, I'm Ahmet, a backend and Linux-focused software engineer currently exploring Canonical's cloud infrastructure and packaging ecosystem. I'm reaching out because I’m preparing for a system-level engineering interview with Canonical and want to meaningfully contribute to open-source projects like I’ve already cloned the project, reviewed the contribution docs, and set up a local environment. Would you be able to recommend:
Also, is it necessary or recommended to use Ubuntu locally when contributing to cloud-init? I'm currently using macOS as my main development environment. I can spin up an Ubuntu VM, container, or cloud instance if that's more aligned with how contributors usually work. Just let me know what's preferred. Thanks a lot for your time 🙏 I’d love to start collaborating and learning from you all. Best regards, GitHub: https://github.com/ahmetdeger |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
These questions are pretty high level and apply to most open source projects so I'm not going to try to answer them all. This is what I would say to any beginner: Start by diving in and learning. Read the docs, try using the project. Form a mental model of how the project works and see what's confusing or doesn't work how you expect it too. Iterate.
I don't know of anybody currently developing cloud-init on macOS, but that shouldn't generally be an issue - virtual machines or cloud instances are typical ways to develop. Something that would actually be quite helpful would be to run unit tests on your local machine (make sure you have tox and a supported version of Python installed) and file a bug if you see any errors and try to fix any that you see.
Did you check for issues with the good first issue tag? |
Beta Was this translation helpful? Give feedback.
These questions are pretty high level and apply to most open source projects so I'm not going to try to answer them all. This is what I would say to any beginner: Start by diving in and learning. Read the docs, try using the project. Form a mental model of how the project works and see what's confusing or doesn't work how you expect it too. Iterate.
I don't know of anybody currently developing cloud-init on macOS, but that shouldn't generally be an issue - virtual machines or cloud instances are typical ways to develop. Something that would actually be quite helpful would be to run unit tests on your local machine (make sure …