GSoC Introduction

[Matthew Joyce]

Sir,

I think that makes sense. I'll put some time into it and will follow
up in our first meeting next week. Now I'm about to jump on a
transatlantic flight with my four-year-old (Please wish me
luck)...Thank you again and have a great weekend!

Sincerely,

Matt

On Thu, May 20, 2021 at 10:50 AM Joel Sherrill <joel at rtems.org> wrote:
>
>
>
> On Thu, May 20, 2021 at 8:21 AM Matthew Joyce <mfjoyce2004 at gmail.com> wrote:
>>
>> Dr. Joel,
>>
>> Thanks! I'd definitely like to get one or two easier ones under my
>> belt first. Based on my initial look for what can be ported, I'd plan
>> to start with dladdr. Sig2str and str2sig have to be re-implemented,
>> but I think they should be fairly straightforward. Once I have those
>> done, I'll start to tackle the others. Does that sound reasonable, or
>> would you have a different recommendation?
>
>
> That sounds reasonable enough. As a work pattern for adding POSIX
> APIs, it has worked best to assume you will have patches outstanding
> for multiple APIs at the same time. While one is being reviewed, you
> should work on the next.Sometimes the newer ones end up getting
> wrapped up before the first ones posted.
>
> Also all the new APIs require adding prototypes to newlib POSIX
> headers. This means tool bumps which means it would be a good idea
> to put together a patch to update the POSIX headers which are in
> newlib to add the new APIs in a batch. This will mean a single bump
> of the newlib version in the RSB which has a reasonable chance of working
> for all the additions.
>
> Adding methods as needed to the headers would be a fairly easy
> step and is a prerequisite for a number of your planned methods.
>
>>
>>
>> Also, where can I find the master API tracking CSV file?  Thanks again!
>
>
> It is in rtems-docs
>
> https://git.rtems.org/rtems-docs/tree/posix-compliance/RTEMS-Standards-Compliance.csv
>
> I don't recall adding the new methods yet and someone internal
> spotted a couple of minor mistakes so it looks like I will be updating
> it soon.
>>
>>
>> Sincerely,
>>
>> Matt
>>
>> On Wed, May 19, 2021 at 7:11 PM Joel Sherrill <joel at rtems.org> wrote:
>> >
>> >
>> >
>> > On Wed, May 19, 2021 at 9:09 AM Matthew Joyce <mfjoyce2004 at gmail.com> wrote:
>> >>
>> >> Hello RTEMS Community,
>> >>
>> >> My name is Matt Joyce and it is a great honor for me to join you as a
>> >> 2021 GSoC student developer! I'm a former active-duty US Army infantry
>> >> officer now serving part-time in the reserves. Since 2019 I've been
>> >> back in school pursuing a BS in Computer Science remotely at Oregon
>> >> State while based with my family in Berlin, Germany.
>> >>
>> >> I see that there is a large group of RTEMS developers/users in
>> >> Germany, so one day I hope to be able to meet some of you in person,
>> >> too!
>> >
>> >
>> > Hopefully this will be a fun summer for you.
>> >>
>> >>
>> >> My project focuses on POSIX compliance. I plan to add multiple new
>> >> methods not currently supported by RTEMS with the intent to improve
>> >> application portability.
>> >> (https://summerofcode.withgoogle.com/projects/?sp-search=Matthew%20Joyce#6686502693634048)
>> >> With your guidance, I am excited to dive in and put what I've been
>> >> learning to work and make my first real-world contributions to the
>> >> greater good.
>> >
>> >
>> > Any idea which method(s) you want to tackle first?
>> >
>> > --joel
>> >>
>> >>
>> >> Thank you very much for this opportunity!  I look forward to working with you.
>> >>
>> >> Sincerely,
>> >>
>> >> Matt
>> >> _______________________________________________
>> >> users mailing list
>> >> users at rtems.org
>> >> http://lists.rtems.org/mailman/listinfo/users