adding project idea for KubeStellar's UI #1321
Conversation
Signed-off-by: Andy Anderson <andy@clubanderson.com>
There was a problem hiding this comment.
Thanks for this really detailed proposal @clubanderson!
Usually we request that there be at least two mentors for a project -- is there another community member that you think would be interested in participating as well?
Signed-off-by: Andy Anderson <andy@clubanderson.com>
|
@nate-double-u - added Braulio. Thank you |
|
Thanks @clubanderson! @dumb0002, could you approve or 👍 this PR to confirm participation? |
|
@nate-double-u can you approve and merge? Thank you |
|
Hi @clubanderson, Sorry i missed this earlier (so much detail in this proposal), could you make a follow up PR update with an upstream issue for this work in the kubestellar/ui? |
|
@nate-double-u the entire KubeStellar/ui repo is the focus of the project |
Even so, it's good practice to have a place where folks can discuss the project during the application phase, and where you can discuss design and development during the program. WasmEdge has some good examples: WasmEdge LFX Mentorship issues |
|
Project: Binding Policy Frontend - kubestellar/ui#54 |
|
I wonder if we want to change the scope of this then. Remembering that this is a 12 week program, and that the folks who will be applying will mostly be 3-4 year university students and junior level developers. Reading this more closely, this project may be better presented as 3-4 projects. |
|
It is a single project that is comprised of frontend and backend development for 3 different KubeStellar components. Since each component is represented by a controller and CRD, the API methods needed for CRUD are similar (if not the same) for each. This provides an opportunity for interns to study Kubernetes API and bounce ideas off each other. The goal is to have the interns create the first version of the KubeStellar UI organically. We have no aspirations that this UI will be production grade in 12 weeks. We are hopeful to make progress as a team of interns and then take another turn of the crank in the follow-on internship opportunities. Each session will pickup where the last session left off. I think splitting this into separate projects would be more overhead than is necessary. I created separate issues based on your request. You can see that they are similar to each other. If you would like me to merge the 6 issues into 1, then we are back at the original "project idea". I am happy to adjust whichever way you see fit. Would like our project idea and issue(s) to be promoted to the lfx-mentorship page when possible. |
No description provided.