digitalmars.D.announce - GSoC 2017 Application Rejected
- CRAIG DILLABAUGH (23/23) Feb 10 2017 Hello D Community
- bachmeier (5/28) Feb 10 2017 Thanks for your effort. If someone else doesn't like it, well, I
- CRAIG DILLABAUGH (9/20) Feb 10 2017 You are welcome. Even though I am unlikely to be fired it was
- Joseph Rushton Wakeling (15/15) Feb 10 2017 Hi Craig,
- CRAIG DILLABAUGH (15/30) Feb 10 2017 Joe good point. The first thing I thought after this happened is
- Jeremy DeHaan (7/30) Feb 10 2017 Not sure how viable this is, but would the D Foundation be able
- Martin Nowak (5/6) Feb 11 2017 Unfortunate, I guess the best improvement for the next GSoC is
Hello D Community Just coming here to inform everyone that our D application for GSoC 2017 was sadly rejected. Unfortunately (for me) it is completely my fault, I failed to fill out one line on one of the three forms that comprised the application. Even more frustrating I went online on the 8th to make sure that everything was in order and I noticed and filled in the offending line. However I must have either failed to hit 'save' or the save itself failed (I will assume the later since that makes me look less incompetent). To make matters worse I got an automated email from Google at 3am the morning of the deadline warning me, but since I had a particularly busy day at work on the 9th I didn't get a chance to check my email until shortly after noon on Feb 9th. At which point it was too late. So I want to apologize to the D community for this mix up on my part, and in particular to those who invested time in helping get ready for this year's GSoC and to you students who were looking forward to applying. However, for anyone who did work on the Ideas page that can at least be re-used and we now have a much fuller list. Regards Craig
Feb 10 2017
On Friday, 10 February 2017 at 19:00:54 UTC, CRAIG DILLABAUGH wrote:Hello D Community Just coming here to inform everyone that our D application for GSoC 2017 was sadly rejected. Unfortunately (for me) it is completely my fault, I failed to fill out one line on one of the three forms that comprised the application. Even more frustrating I went online on the 8th to make sure that everything was in order and I noticed and filled in the offending line. However I must have either failed to hit 'save' or the save itself failed (I will assume the later since that makes me look less incompetent). To make matters worse I got an automated email from Google at 3am the morning of the deadline warning me, but since I had a particularly busy day at work on the 9th I didn't get a chance to check my email until shortly after noon on Feb 9th. At which point it was too late. So I want to apologize to the D community for this mix up on my part, and in particular to those who invested time in helping get ready for this year's GSoC and to you students who were looking forward to applying. However, for anyone who did work on the Ideas page that can at least be re-used and we now have a much fuller list. Regards CraigThanks for your effort. If someone else doesn't like it, well, I guess I don't remember a big competition among volunteers for the position.
Feb 10 2017
On Friday, 10 February 2017 at 19:37:20 UTC, bachmeier wrote:On Friday, 10 February 2017 at 19:00:54 UTC, CRAIG DILLABAUGH wrote:clipHello D CommunityYou are welcome. Even though I am unlikely to be fired it was disappointing and I know a number of people were excited, and were looking forward to this. Last year's success set the bar pretty high. At least the mentors and such will now have some extra time to devote to other worthwhile D projects over the summer. CraigRegards CraigThanks for your effort. If someone else doesn't like it, well, I guess I don't remember a big competition among volunteers for the position.
Feb 10 2017
Hi Craig, So sorry to hear that this happened. I know very well from working with you last year how much care and attention you put into GSoC, so I can imagine how you must feel right now. In the circumstances it seems best to focus on: how could we try to stop something like this happening again? One thing that occurs to me is that it might be a good idea for the email address through which the application is submitted to forward to a couple of other people, who could step in should there be an emergency like this (with the principle being, whoever gets such an emergency alert deals with it ASAP, unless they hear that it's dealt with from the other people involved). What do you think? Best wishes, -- Joe
Feb 10 2017
On Friday, 10 February 2017 at 20:21:56 UTC, Joseph Rushton Wakeling wrote:Hi Craig, So sorry to hear that this happened. I know very well from working with you last year how much care and attention you put into GSoC, so I can imagine how you must feel right now. In the circumstances it seems best to focus on: how could we try to stop something like this happening again? One thing that occurs to me is that it might be a good idea for the email address through which the application is submitted to forward to a couple of other people, who could step in should there be an emergency like this (with the principle being, whoever gets such an emergency alert deals with it ASAP, unless they hear that it's dealt with from the other people involved). What do you think? Best wishes, -- JoeJoe good point. The first thing I thought after this happened is 'what should I do to prevent this from happening again?' We are supposed to have a backup administrator. I had added an email (for backup admin) to the admin list but while the individual confirmed his interest to me I don't know if he confirmed with Google (they send an invite when you register someone). Perhaps they would have pinged him too had the invite been accepted, but I am not sure, I will ask the Google folks. In any case, next year I will make sure we have one or two backup admins signed up well ahead of time who could act as a backup for submission even if that was all they had to do. Cheers Craig
Feb 10 2017
On Friday, 10 February 2017 at 19:00:54 UTC, CRAIG DILLABAUGH wrote:Hello D Community Just coming here to inform everyone that our D application for GSoC 2017 was sadly rejected. Unfortunately (for me) it is completely my fault, I failed to fill out one line on one of the three forms that comprised the application. Even more frustrating I went online on the 8th to make sure that everything was in order and I noticed and filled in the offending line. However I must have either failed to hit 'save' or the save itself failed (I will assume the later since that makes me look less incompetent). To make matters worse I got an automated email from Google at 3am the morning of the deadline warning me, but since I had a particularly busy day at work on the 9th I didn't get a chance to check my email until shortly after noon on Feb 9th. At which point it was too late. So I want to apologize to the D community for this mix up on my part, and in particular to those who invested time in helping get ready for this year's GSoC and to you students who were looking forward to applying. However, for anyone who did work on the Ideas page that can at least be re-used and we now have a much fuller list. Regards CraigNot sure how viable this is, but would the D Foundation be able to do its own version of the Summer of Code? The D Summer of Code? Depending on how much money it has, it could pick some students that were working on proposals and pay them what Google would have paid them based on performance like in the real GSoC.
Feb 10 2017
On Friday, 10 February 2017 at 19:00:54 UTC, CRAIG DILLABAUGH wrote:Hello D CommunityUnfortunate, I guess the best improvement for the next GSoC is getting more help (people) to cater for the application/organization.
Feb 11 2017