Subject: Re: [boost] [gsoc17] GSoC next steps (was: Re: [gsoc2017]Satyam Pandey Copy GSoC 2017 Proposal writen by Ruoyun Jing)
From: Ruoyun Jing (jingry0321_at_[hidden])
Date: 2017-04-05 15:20:36
Thanks all for your help!
I will notice the following progress.
2017-04-04 21:26 GMT+08:00 Niall Douglas <gsoc-admin_at_[hidden]>:
> > Sorry for disturbing you at this time, I experienced a very bad thing
> > that Satyam Pandey, a student who sent proposal yesterday copied too
> > many sections of my proposal. I marked the sections red in the given
> > PDF.*I think the same pattern of GSoC proposal is common, and it does
> > not matter, but his proposal has too many same description as me. *
> Thank you for reporting this issue.
> It is unavoidable in Google Summer of Code that students copy one
> another and indeed sometimes pay another to write their competency test
> for them. We actually encourage students to study one another's
> applications and submit an even better application, this happened
> several times this year with the static map proposal. But we frown on
> failure to attribute sources, including failure to mention when the
> community or stackoverflow gave them help. And students who are later
> prove to be incapable of programming code at the level they advertised
> in their proposal are lifetime banned not just by us, but by Google.
> Last night I read every application and pre-eliminated half of them as I
> do every year so the Boost community doesn't waste their time with them.
> The calibre at the top this year is even higher than in past years, we
> have at least three truly superb candidates per project. It will be very
> hard to choose between them, and we will have to reject two superb
> candidates for no good reason other than only one student can do one
> You should see an announcement regarding community ranking soon. Watch
> this space.
-- Northwest University of China Software Engineering jingry0321_at_[hidden] <jingry0321_at_[hidden]>
Boost list run by bdawes at acm.org, gregod at cs.rpi.edu, cpdaniel at pacbell.net, john at johnmaddock.co.uk