Re: Re: [PHP-DEV] GSoC, Mutation Testing, Ineligible

From: Date: Sat, 31 Mar 2007 07:45:35 +0000
Subject: Re: Re: [PHP-DEV] GSoC, Mutation Testing, Ineligible
References: 1 2  Groups: php.internals 
Request: Send a blank email to internals+get-28636@lists.php.net to get a copy of this message
Sebastian Bergmann wrote: > Thomas Koch wrote: >> Today, just some minutes before deadline, the application status has >> been set to "Ineligible" without any comment or even a name of the one >> who set this status. > > I set the application status to "Ineligible" which, in the terms of > Google's web interface for GSoC, means that no mentor should vote on it > anymore. At least as far as I understood it. To avoid such wrong interpretations for the next GSoCs, I'll cite Google's explaination: | The Ineligible Link | Before any application has been scored, there will be a link on the | application page to mark the application "Ineligible." Clicking the | "Ineligible" link gives the application a score of -10 and drops it | to the bottom of the application list. Use the "Ineligible" link only | for applications that are spam. To be clear, a badly written | application is not ineligible, it should simply receive bad scores, | e.g. -2. Proposals that are copied directly from an organization's | Ideas list are not ineligible, they are just poorly written and | should be scored accordingly. An example of an Ineligible application | would be one in which the student simply states "I like to program, | can I work with you guys?" but does not provide a project proposal | for a project. The most important sentence of this paragraph is: | Use the "Ineligible" link only for applications that are spam. Source: http://groups.google.com/group/google-summer-of-code-announce/web/guide-to-the-gsoc-web-app-for-mentors-and-organization-administrators Regards, Mark -- http://www.markwiesemann.eu

« previous php.internals (#28636) next »