Correct the Project hours for GSoC projects on GSoC page

[rareddy]

Project sizes need to be scoped to 90, 175 or 350 hours (you can not have a project that is 200 hours, or some other random number of hours).

Make sure your Project Ideas list is public so GSoC Google reviewers can access it.
Make sure your Project Ideas include the ALL of the required information below:

a) a project title/description
b) more detailed description of the project (2-5 sentences)
c) expected outcomes
d) skills required/preferred
e) possible mentors
f) expected size of project (90, 175 or 350 hour – yes, 3 options starting in 2024)

[tarilabs]

thank you for the headsup, for Model Registry (project 10)

--- a/content/en/events/gsoc-2024.md
+++ b/content/en/events/gsoc-2024.md
@@ -217,7 +217,7 @@ We aim to extend the capabilities of the KF Model Registry Python client by enab
 
 **Difficulty:** medium
 
-**Length:** 250 hrs
+**Length:** 175 hrs
 
 **Mentors:** Matteo Mortari, Andrea Lamparelli
 

[rimolive]

Project 9:PostgreSQL integration in Kubeflow Pipelines will require 175 hours

[andreyvelich]

• Project 4: Implement LLM Tuning API for Katib - requires 350 hours
• Project 5: Support Distributed Jax for Training Operator - requires 350 hours
• Project 6: Push-based metrics collection for Katib - requires 175 hours
• Project 7: Automate docs generation for Kubeflow Python SDKs - requires 90 hours
• Project 8: Support various parameter distributions like log-uniform in Katib - requires 350 hours

cc @tenzen-y @johnugeorge

[tenzen-y]

Project 9:PostgreSQL integration in Kubeflow Pipelines

SGTM

[Ayush9026]

I think Expected Outcome section is not mentioned in projects. Can i add Expected Outcome section.

[rareddy]

@Ayush9026 yes, please go ahead and add them