----------------------------------------------------------------------
Message: 1 Date: Mon, 15 Dec 2014 14:56:59 -0600 From: Jessica Ross <jessica.r.ross@gmail.com> Subject: Re: [eudyptula] has anyone received a gift after completing the challenge ? To: Markus B?hme <markus.boehme@outlook.com> Cc: kernelnewbies <kernelnewbies@kernelnewbies.org> Message-ID: <CA+zc98Qn07iynMmHPJfAaV_tv6OQbbW=o3t6x5S23LL-=3Z09g@mail.gmail.com> Content-Type: text/plain; charset="utf-8"
I got it, I was impatient. I need to find a real machine for task 2 now. :)
oh man, I have been waiting for 5 days now since I submitted task 03. I can't believe how slow this script is if all it's doing is parsing the results. I don't mean this in a disrespectful way but I'd happily pay 20$ to run this script on a VPS for one month so I could finish the tasks promptly. I am that desperate to finish it. I am itching to contribute but at this pace, I don't think it's far fetched to say you'll finish all 20 tasks in at least a year. Could we get the eudyptula guys to participate in the discussion please? Thanks, Dean
On Mon, 15 Dec 2014 20:35:08 -0700, Dean Michael Ancajas said:
I have been waiting for 5 days now since I submitted task 03. I can't believe how slow this script is if all it's doing is parsing the results.
The problem is that although there's some scripting involved, it's not anywhere near 100% automated - there's still a lot of human intervention needed. (Basically, you can write a script that can tell definitely that somebody got it totally wrong - but you can't always get a script to tell that somebody got it right, especially for more complicated assignments. Looking for the output of 'printk("Here is the magic string expected");' is easy - checking a more complicated thing like screwing around with sysfs is a bunch harder...
Last I checked the challenge had 6000 plus people signed up. If I was the person who had to review and respond to all tasks submitted by folks who are taking the challenge that is 6000 plus emails which to me is daunting, and there is NO way I will be able to balance work+life+responding on time to tasks so my 2 cents is as keep this in mind when you get impatient :) I learnt the hard way, little 'always' but always does respond it may not be immediately as we would like but little will respond as and when time permits him/her to do so. Am on the 6th task and it took me three months to figure things out but the knowledge and skills I have gained far outweigh any time delays and response delays :) On Tue, Dec 16, 2014 at 12:21 AM, <Valdis.Kletnieks@vt.edu> wrote:
On Mon, 15 Dec 2014 20:35:08 -0700, Dean Michael Ancajas said:
I have been waiting for 5 days now since I submitted task 03. I can't believe how slow this script is if all it's doing is parsing the results.
The problem is that although there's some scripting involved, it's not anywhere near 100% automated - there's still a lot of human intervention needed.
(Basically, you can write a script that can tell definitely that somebody got it totally wrong - but you can't always get a script to tell that somebody got it right, especially for more complicated assignments. Looking for the output of 'printk("Here is the magic string expected");' is easy - checking a more complicated thing like screwing around with sysfs is a bunch harder...
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
When I was digging around I stumbled across this by *Robert P. J. Day* : http://www.linux.com/learn/linux-training/32867-the-kernel-newbie-corner-wha... The info and manner in which he explains things was very helpful and there are many more articles by the gentleman that shed light on how and why kernel modules do what they do and how we can mess with them :) This seriously opened my eyes, again by the same gentleman: http://www.linux.com/learn/linux-training/33991-the-kernel-newbie-corner-ker... On Tue, Dec 16, 2014 at 12:30 AM, Aruna Hewapathirane < aruna.hewapathirane@gmail.com> wrote:
Last I checked the challenge had 6000 plus people signed up. If I was the person who had to review and respond to all tasks submitted by folks who are taking the challenge that is 6000 plus emails which to me is daunting, and there is NO way I will be able to balance work+life+responding on time to tasks so my 2 cents is as keep this in mind when you get impatient :)
I learnt the hard way, little 'always' but always does respond it may not be immediately as we would like but little will respond as and when time permits him/her to do so.
Am on the 6th task and it took me three months to figure things out but the knowledge and skills I have gained far outweigh any time delays and response delays :)
On Tue, Dec 16, 2014 at 12:21 AM, <Valdis.Kletnieks@vt.edu> wrote:
On Mon, 15 Dec 2014 20:35:08 -0700, Dean Michael Ancajas said:
I have been waiting for 5 days now since I submitted task 03. I can't believe how slow this script is if all it's doing is parsing the results.
The problem is that although there's some scripting involved, it's not anywhere near 100% automated - there's still a lot of human intervention needed.
(Basically, you can write a script that can tell definitely that somebody got it totally wrong - but you can't always get a script to tell that somebody got it right, especially for more complicated assignments. Looking for the output of 'printk("Here is the magic string expected");' is easy - checking a more complicated thing like screwing around with sysfs is a bunch harder...
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
Well said. I think people in general should also pay it forward. Could be a good idea for volunteers to help check others' answers. For instance, people who have passed task 05 should be allowed to check task 1,2,3 etc.. from others' submissions so on and so forth. Obviously, that platform is not possible right now but some sort of "community checking" is desirable to relieve the main developers' burden. On Mon, Dec 15, 2014 at 10:30 PM, Aruna Hewapathirane <aruna.hewapathirane@gmail.com> wrote:
Last I checked the challenge had 6000 plus people signed up. If I was the person who had to review and respond to all tasks submitted by folks who are taking the challenge that is 6000 plus emails which to me is daunting, and there is NO way I will be able to balance work+life+responding on time to tasks so my 2 cents is as keep this in mind when you get impatient :)
I learnt the hard way, little 'always' but always does respond it may not be immediately as we would like but little will respond as and when time permits him/her to do so.
Am on the 6th task and it took me three months to figure things out but the knowledge and skills I have gained far outweigh any time delays and response delays :)
On Tue, Dec 16, 2014 at 12:21 AM, <Valdis.Kletnieks@vt.edu> wrote:
On Mon, 15 Dec 2014 20:35:08 -0700, Dean Michael Ancajas said:
I have been waiting for 5 days now since I submitted task 03. I can't believe how slow this script is if all it's doing is parsing the results.
The problem is that although there's some scripting involved, it's not anywhere near 100% automated - there's still a lot of human intervention needed.
(Basically, you can write a script that can tell definitely that somebody got it totally wrong - but you can't always get a script to tell that somebody got it right, especially for more complicated assignments. Looking for the output of 'printk("Here is the magic string expected");' is easy - checking a more complicated thing like screwing around with sysfs is a bunch harder...
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
On Mon, Dec 15, 2014 at 10:44:08PM -0700, Dean Michael Ancajas wrote:
Well said. I think people in general should also pay it forward. Could be a good idea for volunteers to help check others' answers. For instance, people who have passed task 05 should be allowed to check task 1,2,3 etc.. from others' submissions so on and so forth.
Agreed. I think it'd be possible to at the very least crowdsource the earlier tasks. For instance, task 1 is basically trivial to check for correctness. -- Jonathan Jin jjin.me
On Wed, Dec 17, 2014 at 12:18 AM, Jonathan Jin <jjin082693@gmail.com> wrote:
On Mon, Dec 15, 2014 at 10:44:08PM -0700, Dean Michael Ancajas wrote:
Well said. I think people in general should also pay it forward. Could be a good idea for volunteers to help check others' answers. For instance, people who have passed task 05 should be allowed to check task 1,2,3 etc.. from others' submissions so on and so forth.
Agreed. I think it'd be possible to at the very least crowdsource the earlier tasks. For instance, task 1 is basically trivial to check for correctness.
Sorry, but I don't agree. My opinion : you can review others code only after you have a good number of patch submission in lkml , and your submitted patches have been reviewed by others, and ultimately some or all of them accepted in the linux kernel. when I started, it took me 3 - 4 attempts to just send the result , and then again 2 attempts to clear that task 1. thanks sudip
-- Jonathan Jin jjin.me
_______________________________________________ Kernelnewbies mailing list Kernelnewbies@kernelnewbies.org http://lists.kernelnewbies.org/mailman/listinfo/kernelnewbies
participants (5)
-
Aruna Hewapathirane -
Dean Michael Ancajas -
Jonathan Jin -
Sudip Mukherjee -
Valdis.Kletnieks＠vt.edu