Open nicolas-raoul opened 2 years ago
Someone reached out to me yesterday, expressing their concerns over the impact of their ideas getting "copied". They even cited this incident and asked about the selection procedure (which I believe is already there on GitHub and says merged bugfixes are the topmost priority, but still they're hesitant about discussing the implementation strategy even in the proposal since they're publicly available on Phabricator). While it is highly encouraged to use public channels to communicate when it comes to the open-source community, some potential GSoC applicants might refrain from discussing their ideas in their proposals or end up not submitting at all. Sharing this, since there's already some discussion around the proposal process.
@RitikaPahwa4444 Thanks for pointing this out! I still think that the proposal is not what will make us choose one candidate rather than the other. Unless a proposal is somehow unrealistic, the merged pull request is how we compare the top candidates, mostly.
This year we had less GSoC candidates than previous years, and several great candidates ended up not submitting a proposal.
This issue is to collect feedback and brainstorm on ideas to improve/simplify/etc the proposal phase process.
Anyone is welcome to share feedback and ideas, anonymously or not, now or in a few weeks or at any time. For instance, what are the main challenges as a potential candidate?
Thank you all! :-)