@AliMussawi also see this excerpt from https://google.github.io/gsocguides/mentor/ to better understand the student acceptance process
Following the GSoC contributor application deadline, organizations begin reviewing the proposals they received. During the review phase, organizations maintain an open dialogue with their applicants. This may involve clarifying questions in regards to the final proposals to ensure applicants and organizations have the same understanding of the proposal. It is important to note an applicant’s proposal can’t be altered after the final submission deadline, and mentor organizations should not attempt to do so during the review period.
Organizations may also conduct further interviews to determine which applicants are most likely to be a good fit for the community and work required. Over the course of several weeks, each organization prioritizes its list of proposals, ranking them and then submitting their requests for slots to Google. Google will let each organization know how many slots it will fund, and based on ranked order those proposals will be automatically selected (if given 5 slots, those proposals ranked 1-5 will be selected).
@ADI10HERO Thanks very much for sharing the plugin health score calculating algorithm with me. I have one doubt/observation that I wanted to share with you (and everyone else)
As per the algo, if we pass unbounded discrete values via a "tanh" function, it will definitely bring our discrete value to a [-1,1] range but we might not be able to preserve some useful info. For example, I've noticed that the tanh function gives the value as "1" for both the (example) inputs "150" as well as "38825".
So, even though both the values have a huge difference between them, both of them result in a common value "1" when passed through the tanh function. I believe, ideally, we would need to treat both values differently while calculating the health score.
As per the discussion on the "Plugin Health Score" project idea's brainstorming session, we'd like to have weight re-adjusted every 12 weeks for now.
But how often would we want to re-run the health-score-calculation algorithm for each plugin? Given that, plugin repos merge new PRs every 2-3 days (or week maybe), so we'd want to display the "updated" health score quite frequently (not only every 12 weeks).
I was thinking about re-running the algorithm on every merged PR within a plugin's repo. What are your thoughts/suggestions on this?
Build periodically with parameters.. Do I need to setup any initial configuration to view this option?
From the official docs:
I am a student in the United States on an F1 visa. How do I get authorization to participate?
Please talk to your school's international student affairs office for more details. Google can not provide you with any kind of CPT or OPT authorization. It is your responsibility to determine if your visa allows you to participate in a program like GSoC, please check before applying. You should also be sure that you can accept the stipend so you are not surprised later if you can not (often due to visa concerns).
All accepted participants will receive an email confirmation of acceptance. We do not offer customized letters.