Hi Leslie
I was wondering if it would be possible to review the application late
so long as the receiving organization is okay with it. I realize that
you might be bound on this and am not going to push you once you say
one way or the other, however, I too feel I have invested a lot into
this application. I have spent the entire application time talking
with wordpress core developers, and really feel this work could be
beneficial. In the end, I too missed the google application deadline
by very little time. However, I had sent my application to developers
for feedback, and thought we had at last worked everything out.
If you would like the email of one of the developers, I would be glad
to give it to you.
Thank you for your time. Either way, I will respect your decision.
Pat
Hello Leslie,
I'm not a student in SoC this year, so this does not affect me. Just
thought I'd give you something to think about in regard to this
situation (which, as you know, happens every year).
Suppose you're driving on a highway at 56 mph and the speed limit is
55. You get pulled over by a cop who writes you a speeding ticket for
1 mph over the limit. Now suppose that you're driving on the same
highway at 66 mph and the same thing happens. Where I live, 10 mph
over the limit is usually not a problem, and here you're given a
ticket for 11 mph over the limit. The speed limit is the same, but
would you be as upset with the officer in the second case as in the
first (the assumption is that driving at 55 and 65 mph in the two
respective cases would not have resulted in a ticket)?
The point of the analogy is that this is psychology problem. There
needs to be a time limit on when the applications are due. But I would
guarantee you that if you configured the system to accept proposals
for an extra 10 or 15 minutes after the published cutoff time, you
would have fewer students upset about not getting their proposals in
on time. I would also disagree with your assertion that this is
somehow unfair to other students. Move the end time back by one hour
if you think that the extra few minutes at the end will play a
significant part in the selection process, but allow for that margin
of error.
I'm not arguing that these students did the right thing by waiting
till the last minute. I'm not arguing against having a hard deadline.
I'm also not suggesting that you handle the proposals differently this
year. I do, however, think that for future summer of code programs you
should consider the human factors when configuring your system. A
student would be less upset about not getting their proposal in at
19:15 UTC than they are when the clock reads 19:00. You, in turn,
would not be stuck defending an arbitrary deadline, since a generous
margin of error was provided after the published time.
- Max
I don't get this. Accepted mentoring organizations were announced on
March 18. Proposals deadline, April 3. A week, 7 days. At least for
me.
Cheers,
Serabe
Because then other people will want us to accept applications that are
2 minutes late, and then 3 minutes late, and then 1 hour late, then 1
day late. By recurrence, your proposed change eliminates the concept
of deadline and requires Google to accept applications indefinitely.
Your proposed program never halts.
It also prevents mentoring orgs from organizing themselves to review
applications, since they never know when the brilliant but terminally
disorganized will finally get round to submitting their world-changing
idea. Again, the coding phase would never begin in this case, since
nobody would ever be in a position to say "Right, that's it, we're
done".
Overall, casting aside the termination problem, you are proposing that
the two parties who invest the most in this program, Google in
finances and mentoring organizations in man-hours, adapt themselves to
the schedule that you, the party receiving the attention, mentoring
and money, would prefer. I'm sure you now see that this is somewhat
unbalanced.
> I already know the answer, I am just ranting. Google is too big of a
> corporation to ask something as simple as 'can you accept an
> application 1 minute late'. Besides, they have 3000 other
> applications, what do they care. It is the open source applications
> that loose out from this, not Google.
You are now insulting the very real people who are running this
program. People who really drive it are less than a dozen, and I can
assure you from knowing them personally that they are neither soulless
nor unthinking machines. I'm sure that the "big corporation"
stereotype was fun to roll off the keyboard, but you are simply
misinformed and incorrect. By belittling the work of the few people
who make this program tick, you are just being an asshole. Stop it.
I'm sure that you're pissed off that you missed the deadline. However,
please realize that it is nobody's fault but your own. This whole
program can not and will not adapt to the individual schedules of
thousands of people. If you were unable to adapt your own schedule,
then too bad. Thousands of others somehow muddled through. They may
even get selected for their troubles.
> And if you are wondering why I didn't write the application at a much
> earlier date, it is because the original project I wished to code was
> for a program that didn't get accepted by Google for 2 years in a row
> now, Pure Data (in my opinion, an organization much more deserving/in
> need of grants than most well-paid programs that were accepted). So, I
> had to conceive and write a new proposal in a week (finals week).
There were 16 days to come up with an application after the accepted
orgs were announced, not a week. This still doesn't change anything to
the fact that nobody is to blame here but yourself. It's just too easy
to randomly attribute blame to other people, and I'm sure it feels
good, but it's simply misrepresenting reality.
Ranting about it after the facts in the way that you did just makes
you sound like an asshole. Your situation will not change as a result
of the bile you poured into that email, and rather than attempt to
constructively improve the imperfection you perceives, you just
decided to take a stab at everything and everyone. I do not know of a
mentoring org that would want to work with you, given that this is how
you respond to the world not meeting your private expectations.
> regards,
Please disable automatic signatures and/or reflex typing when you
don't mean it. You clearly didn't from the tone of the email.
Goodbye,
- Dave
@Rich E
If you do say that your application is as revolutionary as it is, has
the mentoring Org appealed to Google Directly? Has it served a
purpose? I am not sure if you are the only one beating your own
bandwagon or not. But I believe the community should step out of the
shadows.
@Google
I do not see what's the problem if the organization really wants the
application through? Isn't it about the mentoring organizations
benefit? Or am I missing out on the mission statement here? If I am
then I apologize. But I thought this was a platform for open source
contribution from new and hard working alike. If the Organization
needs an application through then why not give them that? If the
argument here is that it is unfair to student who applied for that
Organization before this person then it stands invalid as the Org may
not need any of the proposal. Tough break for them. The whole system
does stand unfair to so many who are not selected. In the end the
proposals that are through are selected with a lot of consideration.
I expect most replies to be: "rules are rules" or it's that "not
everyone will be satisfied by the system". As visible, I am stating
this to all parties involved. Had to get my opinion across.
----
Nandeep
This reminds me of the CMA server we have at our university which
usually goes down during assessment periods because a whole swag of
people are doing the assessments at the last minute which is more load
than the server can handle at a single given point. It is really
pointless to throw more hardware at the problem since most of the time
the system is underused. It stands to reason that if you're doing it
at 2 minutes prior there are probably a whole swag of people and
you're really not giving yourself much time for the unexpected which
has lead to old man Murphy striking again.
Perhaps we need another motto for SoC proposals:
Submit early, edit often.
(submit often implies multiple submissions which isn't what I really
want to convey)
Sam Moffatt
http://pasamio.id.au
> The NUI group did try to appeal without
> success, but hopefully we can work on the project some how in the
> future.
I'd like to put a slightly different POV across. OSPO aren't bending
the rules, no matter what orgs ask for. This is a Good Thing, it
takes pressure off orgs desperate for contributions and wanting to get
the most out of SoC from being the bad guys when we need to. It's not
appropriate to accept late proposals, it's simply not fair, but there
is a pressure on mentoring orgs if they know there are good late
proposals.
I think more people would be more uncomfortable if this wasn't a hard-
and-fast rule.
Matt
Dear all: please reread what Leslie said 2 days ago.
- Dave