search

kubevirt / kubevirt.github.io

KubeVirt website repo, documentation at https://kubevirt.io/user-guide/
https://kubevirt.io
MIT License
30 stars 112 forks source link

Create a blog for kubevirt Code Code Walkthrough #732

Closed ansijain closed 2 years ago

ansijain commented 3 years ago

Create a blog for kubevirt Code Code Walkthrough

ansijain commented 3 years ago

/kind enhancement

mazzystr commented 3 years ago

@davidvossel What do you think about a special meeting on the KubeVirt zoom meeting? We can record then blog and post to YouTube.

davidvossel commented 3 years ago

@davidvossel What do you think about a special meeting on the KubeVirt zoom meeting? We can record then blog and post to YouTube.

That might make sense. One concern I have is that our code base is constantly in flux. Things get moved around all the time. For example, I could cover the location for our API being in the staging directory, then we might move that around in the future.

I might be able to talk about the structure in broader terms though.

@ansijain What kind of information would you find useful here?

ansijain commented 3 years ago

Thank you for the response.

I am new to kubevirt community. I want to get more familiar with the code base so that I can start code contribution.

It would be great if you help me with structure or any relevant information that is helpful for contribution.

davidvossel commented 3 years ago

@ansijain have you checked out our getting started [1] and contributing [2] guides? Have those been helpful with onboarding ?

  1. https://github.com/kubevirt/kubevirt/blob/master/docs/getting-started.md
  2. https://github.com/kubevirt/kubevirt/blob/master/CONTRIBUTING.md
ansijain commented 3 years ago

@davidvossel yes I have gone through these documents. It was really helpful. But with this I am expecting some overview on code side. If that is possible.

davidvossel commented 3 years ago

@davidvossel yes I have gone through these documents. It was really helpful. But with this I am expecting some overview on code side. If that is possible.

possibly ,I'm unsure about the scope of what we're talking about here though. Do you have an example of another project that provides the kind of code walk-through you're interested in?

ansijain commented 3 years ago

@davidvossel
I am expecting walk-through something like in this video [1] and blog [2]

[1] https://developer.ibm.com/conferences/oscc_become_a_kubernetes_contributor/kubernetes_scheduler_code_walkthrough/ [2] https://developer.ibm.com/components/kubernetes/articles/a-tour-of-the-kubernetes-source-code/

davidvossel commented 3 years ago

I am expecting walk-through something like in this video [1] and blog [2]

Thanks, I'll give this some thought. It might take some time before I can look at this closer.

mazzystr commented 3 years ago

May this diagram helps?

https://kubernetes.slack.com/files/U2WUVHD6Y/F0221FWU6KW/kubevirt_create_vmi_seq_diagram.jpg

On Tue, May 4, 2021 at 2:27 PM David Vossel @.***> wrote:

I am expecting walk-through something like in this video [1] and blog [2]

Thanks, I'll give this some thought. It might take some time before I can look at this closer.

— You are receiving this because you commented. Reply to this email directly, view it on GitHub https://github.com/kubevirt/kubevirt.github.io/issues/732#issuecomment-832259702, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAS5KZZVFZ6DP2X7YQFJHCDTMBRDHANCNFSM433ZTEPA .

ansijain commented 3 years ago

Yes this sequence diagram is helpful.

kubevirt-bot commented 3 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

ansijain commented 3 years ago

/remove-lifecycle stale

kubevirt-bot commented 2 years ago

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale. Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

/lifecycle stale

kubevirt-bot commented 2 years ago

Stale issues rot after 30d of inactivity. Mark the issue as fresh with /remove-lifecycle rotten. Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

/lifecycle rotten

kubevirt-bot commented 2 years ago

Rotten issues close after 30d of inactivity. Reopen the issue with /reopen. Mark the issue as fresh with /remove-lifecycle rotten.

/close

kubevirt-bot commented 2 years ago

@kubevirt-bot: Closing this issue.

In response to [this](https://github.com/kubevirt/kubevirt.github.io/issues/732#issuecomment-1029003946): >Rotten issues close after 30d of inactivity. >Reopen the issue with `/reopen`. >Mark the issue as fresh with `/remove-lifecycle rotten`. > >/close Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.