[PATCH] gsoc_task: Proof that I can contribute to RTEMS in GSoC

[Gedare Bloom]

Hi Rajiv,

On Fri, Mar 19, 2021 at 11:35 PM Rajiv Vaidyanathan <
rajiv.vaidyanathan4 at gmail.com> wrote:

> Hi Gedare,
>
> Thank you for providing feedback on the patch. I'll make sure I follow the
> character limit guidelines from now on. I have added my info template to
> the Students' Proposals table.
>
> I looked into the open projects and found the following projects
> interesting:
> 1. https://devel.rtems.org/ticket/3855
> 2. https://devel.rtems.org/ticket/3892
> It would be great if you can provide some guidance regarding these tickets.
>
> You may like to start threads about each of those possible projects with
clear email subject lines, so that you may get the attention of the
potential mentors. Not all mentors will be reading every email
continuously, and also we don't all know the ticket numbers or click on
links in emails.

That said, I know the EPICS BSP Buildset project had some work done last
summer, and I think it is almost finished now with some recent effort that
has been done in the past month, so I don't think there is enough in that
specific direction for a GSoC scope anymore.


> I just realised that I never introduced myself 😅 I am Rajiv Vaidyanathan
> studying Masters in Computer Science at IIT Bombay, India. In my coursework
> and projects/ labs, I have gained some experience in systems programming
> and real time operating systems. I am extremely excited to contribute to
> RTEMS.
>
> Great. If you have systems programming experience, I would encourage you
to not be afraid to take on some projects that push you into the C
programming. I saw the two you picked are more Python oriented, but maybe
you will have more fun hacking in the kernel? Just a thought.


> Thanks and regards,
> Rajiv
>
> On Fri, 19 Mar 2021 at 20:21, Gedare Bloom <gedare at rtems.org> wrote:
>
>> Hi Rajiv,
>>
>> On Fri, Mar 19, 2021 at 4:21 AM Rajiv Vaidyanathan
>> <rajiv.vaidyanathan4 at gmail.com> wrote:
>> >
>> > Link to the task:
>> https://docs.rtems.org/branches/master/user/start/gsoc.html
>> > ---
>> >  testsuites/samples/hello/init.c | 2 +-
>> >  1 file changed, 1 insertion(+), 1 deletion(-)
>> >
>> > diff --git a/testsuites/samples/hello/init.c
>> b/testsuites/samples/hello/init.c
>> > index 34ded37c55..a4e556de19 100644
>> > --- a/testsuites/samples/hello/init.c
>> > +++ b/testsuites/samples/hello/init.c
>> > @@ -22,7 +22,7 @@ static rtems_task Init(
>> >  {
>> >    rtems_print_printer_fprintf_putc(&rtems_test_printer);
>> >    TEST_BEGIN();
>> > -  printf( "Hello World\n" );
>> > +  printf( "Hello from The Dark Side! I'm Rajiv Vaidyanathan and am
>> excited to contribute to RTEMS at GSoC2021!\n" );
>>
>> This is fine for the proof. Note that we limit code line lengths to 80
>> characters in practice:
>>
>> https://docs.rtems.org/branches/master/eng/coding-formatting.html#eighty-character-line-limit
>>
>> Please add your info to
>> https://devel.rtems.org/wiki/GSoC/2021#StudentsProposals
>> and start to investigate which open projects you might like to
>> consider. You will need to engage on the devel mailing list with the
>> potential mentors about those projects, as some of the projects may be
>> no longer available or suitable, and in general the projects need to
>> be scoped appropriately. This engagement is best done in a separate
>> email thread dedicated to the proposed area(s) you want to investigate.
>>
>> >    TEST_END();
>> >    rtems_test_exit( 0 );
>> >  }
>> > --
>> > 2.25.1
>> >
>> > _______________________________________________
>> > devel mailing list
>> > devel at rtems.org
>> > http://lists.rtems.org/mailman/listinfo/devel
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.rtems.org/pipermail/devel/attachments/20210320/f9692591/attachment.html>