mirror/opencv
1
0
Fork 0
mirror of https://github.com/opencv/opencv.git synced 2024-12-04 00:39:11 +08:00
Code Issues Actions Packages Projects Releases Wiki Activity

Updated GSoC_2019 (markdown)

Gary Bradski 2019-03-01 15:44:33 -08:00
parent 6c417bbd3f
commit f0e013de52
1 changed files with 43 additions and 27 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

70
GSoC_2019.md

@ -426,7 +426,7 @@ General Information:
--------------------
[ ▶️ **Join our OpenCV GSoC 2019 Mailing List** ◀️ ](https://groups.google.com/d/forum/opencv-gsoc-2019)
- [Program Site for GSoC 2019](https://summerofcode.withgoogle.com/)
- Mailing list for OpenCV GSOC 2019: `opencv-gsoc-2019@googlegroups.com`
- [Mailing list for OpenCV GSOC 2019](https://groups.google.com/d/forum/opencv-gsoc-2019): `opencv-gsoc-2019@googlegroups.com`
- IRC Channel: `#opencv` on freenode
- **Timelines**
- [Timeline for GSoC 2019](https://summerofcode.withgoogle.com/how-it-works/#timeline)
@ -463,7 +463,7 @@ UTC to PDT (California uses PST in the winter (from Nov 1st) and PDT in the summ
### Resources:
- [ OpenCV Project Ideas List](https://github.com/opencv/opencv/wiki/GSoC_2019#OpenCV-project-ideas-list)
- [OpenCV Project Ideas List](https://github.com/opencv/opencv/wiki/GSoC_2019#OpenCV-project-ideas-list)
- [OpenCV official Site](https://opencv.org)
- [OpenCV wiki](https://github.com/opencv/opencv/wiki)
- [Questions and Answers](http://answers.opencv.org/questions/)
@ -471,8 +471,47 @@ UTC to PDT (California uses PST in the winter (from Nov 1st) and PDT in the summ
- Source Code can be found at [GitHub/opencv](https://github.com/opencv/opencv) and [GitHub/opencv_contrib](https://github.com/opencv/opencv_contrib)
- [[Developer meeting notes|Meeting_notes]]
How you will be evaluated if you are an accepted student
--------------------------------------------------------
How do Students Apply for OpenCV GSoC
-------------------------------------
1. You **must** already know how to program fluently in C++!
- Some projects may instead specifically require Python, javascript or Matlab skills
- Some projects may require knowledge of Deep Nets and perhaps one or more of the standard packages:
- PyTorch, TensorFlow, MXNet. Familiarity with OpenCV's DNN ([here for code](https://github.com/opencv/opencv/tree/master/modules/dnn) and [here for samples](https://github.com/opencv/opencv/tree/master/samples/dnn)) and [ONNX](https://onnx.ai/) deep net exchange is a big plus
1. Go to the [Google Summer of Code site](https://summerofcode.withgoogle.com/) and sign up as a student
1. Get on our [OpenCV GSoC 2019 mailing list](https://groups.google.com/d/forum/opencv-gsoc-2019)
1. Please read the [GSoC 2019 timeline](https://developers.google.com/open-source/gsoc/timeline) and note
1. The application period to OpenCV THROUGH the Google Summer of Code site is **March 18 - April 9**
1. Before that time, contributing to OpenCV is a **big plus**. Some suggestions:
1. Fixing an [bug/issue](https://github.com/opencv/opencv/issues) or
1. Very advanced people can already start delivering code for the idea they like to their mentor
1. More realistically and still **great**: REALLY learn some OpenCV function and contribute a well written tutorial on it
1. Applying:
1. Read our [OpenCV Project Ideas List](https://github.com/opencv/opencv/wiki/GSoC_2019#OpenCV-project-ideas-list) and/or the [OpenCV evolution list](https://github.com/opencv/opencv/wiki/Evolution-Proposals)
1. Post the [idea](https://github.com/opencv/opencv/wiki/GSoC_2019#OpenCV-project-ideas-list) from above or your own agreed on project on opencv-gsoc [mailing list](https://groups.google.com/d/forum/opencv-gsoc-2019)
- Include Name, google email
- Include how you think you are qualified to accomplish this project (skills, relevant courses, relevant working and project background, prior contributions to open source, prior work with GSoC)
- Include Country of origin, school you are enrolled in, Professor you work with (if any)
- Include a projected timeline and milestones for the project
1. Between March 18 and April 9, apply to OpenCV through the [GSoC site](https://summerofcode.withgoogle.com/)
1. Between **April 9 and May 6**:
1. Continue all the above
1. **When** we are told how many slots we will get **and** you've signed up for a project with us, **Then:**
- We will weigh the students and projects against the mentors we gather and the mentor's interests and choose which students/project to pursue
- Each year, we do not get enough slots or mentors to cover every good student, we just have to decide and cry for the rest. Rejection does not mean you were 'bad' and acceptance does not mean you were 'better', it is mostly a choice of internal priorities/interests and finding a mentor to cover the number of slots we get.
- You can still work on a project if you can afford to. Any student who does good work for OpenCV may at least get good letters of recommendation from us, and published projects to show future employers or schools.
1. **May 6** Accepted Student Announcement:
1. Accepted students will be posted on the GSoC site (and we will notify the accepted students ourselves afterwards).
- Students are paid over the summer by Google **IF** the mentor accepts the student's work. There are several milestone based go-nogo points as above.
6. We've had a lot of experience with this: Please only propose projects that you already know how to do.
- It is impossible for a mentor to train you in how to do the task while helping you do it. This **always** results in failure.
- Mentors exist to keep you on track, and ensure good code, but not to teach you a new area of vision or AI.
- This is also not a _research_ period. If you are a top student with publications in top conferences from a top professor in a top University known to us, we may let you code your research area. This is rare.
- Documentation, tests and tutorial are as vital as the code. We'd rather have rougher code then miss these items because if these are not in place, your code will be useless to everyone.
How you students will be evaluated once working
-----------------------------------------------
- Student projects to be paid only if:
- **Phase 1:**
@ -505,30 +544,7 @@ How you will be evaluated if you are an accepted student
- [The 2014 Movie](https://www.youtube.com/watch?v=3f76HCHJJRA)
- [The 2013 Movie](https://www.youtube.com/watch?v=_TTtN4frMEA)
For students interested in applying
-----------------------------------
1. You **must** already know how to program fluently in C++
- Some projects may instead specifically require Python, javascript or Matlab skills
2. Ask to join the opencv-gsoc mailing list above
- Discuss projects ideas below or your own ideas with OpenCV mentors on the list.
- Always title your proposal with what you want to do (example: *Implement Patch Match Stereo Algorithm* )
- **NOTE:** The above is to discuss proposals with mentors. **BUT**, when the application period starts, you must still sign up with Google Summmer of Code and submit your proposal to the OpenCV organization. If not, you will not show up on the database where we can select you as a student.
3. Sign up to be a student with OpenCV
4. Post the project from below or your own agreed on project on the GSoC to opencv-gsoc mailing list above
- Include Name, google email
- Include how you think you are qualified to accomplish this project (skills, courses, relevant background)
- Include Country of origin, school you are enrolled in, Professor you work with (if any)
- Include a projected timeline and milestones for the project
5. **When** we are told how many slots we will get **and** you've signed up for a project with us, **Then:**
- We will weigh the students and projects against the mentors we gather and the mentor's interests and choose which students/project to pursue.
- Accepted students will be posted on the GSoC site (and we will notify the accepted students ourselves afterwards).
- Students are paid over the summer by Google **IF** the mentor accepts the student's work. There are several milestone based go-nogo points as above.
6. We've had a lot of experience with this: Please only propose projects that you already know how to do.
- It is impossible for a mentor to train you in how to do the task while helping you do it. This **always** results in failure.
- Mentors exist to keep you on track, and ensure good code, but not to teach you a new area of vision or AI.
- This is also not a _research_ period. If you are a top student with publications in top conferences from a top professor in a top University known to us, we may let you code your research area. This is rare.
- Documentation, tests and tutorial are as vital as the code. We'd rather have rougher code then miss these items because if these are not in place, your code will be useless to everyone.
For computer vision professionals interested in mentoring
---------------------------------------------------------