-
Notifications
You must be signed in to change notification settings - Fork 788
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Correct the Project hours for GSoC projects on GSoC page #3673
Comments
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
|
Project 9:PostgreSQL integration in Kubeflow Pipelines will require 175 hours |
|
SGTM |
I think Expected Outcome section is not mentioned in projects. Can i add Expected Outcome section. |
@Ayush9026 yes, please go ahead and add them |
/help |
@varodrig: Please ensure the request meets the requirements listed here. If this request no longer meets these requirements, the label can be removed In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
We are looking for help to follow up on this PR #3685 thanks |
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)
The text was updated successfully, but these errors were encountered: