GSoC Mentors / Projects of Interest

Tanu Hari Dixit tokencolour at gmail.com
Tue Jan 31 17:21:28 UTC 2017


Hello,
I created (https://devel.rtems.org/ticket/2891#ticket) on the lines of
Gedare's advice for this open project
(https://devel.rtems.org/wiki/Developer/Projects/Open/ImproveBeagleBSP).
The link to buy USB-TTL FTDI Cable 3.3V on the open project page is
probably broken. What should I replace it with? Please tell if some
edit is needed and whether I should follow this pattern. Furthermore,
please indicate whether this project is of interest. Also which other
open projects should be converted to tickets?

Probably the community is interested in the idea to create simple
examples or sanity tests for all RTEMS directives so that they can be
included in the documentation (something that is user friendly). Also,
there was a thread titled 'Desirable Application Stacks (Add-On
Library Collections)' . Which ideas can be derived from there?

Regards,
Tanu Hari Dixit.

On Tue, Jan 31, 2017 at 4:52 AM, Joel Sherrill <joel at rtems.org> wrote:
>
>
> On Mon, Jan 30, 2017 at 5:13 PM, Gedare Bloom <gedare at rtems.org> wrote:
>>
>> On Mon, Jan 30, 2017 at 12:25 PM, Tanu Hari Dixit <tokencolour at gmail.com>
>> wrote:
>> > I'll be glad to do it. Please guide me as to how to proceed.
>> >
>> We will need to import each existing Open Project description into a
>> new ticket. It would be best to start with one to "try it out". The
>> project title should be the Summary of the ticket, the text of the
>> project page should be converted into the Description of the ticket,
>> type should be Enhancement, Milestone "Indefinite", and put GSoC into
>> the keywords, and we might want to use some other keywords e.g. to
>> define the project type (e.g. one of: testing, ecosystem, kernel,
>> statistics, BSP, API, libbsd, languages, libraries). The owner should
>> be assigned to one of the mentors if indicated, with others in CC if
>> any, or else set blank.
>>
>
> I agree it would be nice to get all the Open Project ideas as tickets and
> off the Wiki. Some of the ideas are likely no longer interesting/valid at
> this point and could just be deleted.
>
> FWIW I also want to move some of the Wiki content into Sphinx documents.
> I think being able to release them with RTEMS branches and use git
> for revision control.
>
> --joel
>
>>
>> > On Mon, Jan 30, 2017 at 9:38 PM, Gedare Bloom <gedare at rtems.org> wrote:
>> >>
>> >> Yes that would be much nicer. Maybe we can get potential GSoC Students
>> >> to do the work ;)
>> >>
>> >> On Mon, Jan 30, 2017 at 1:40 AM, Sebastian Huber
>> >> <sebastian.huber at embedded-brains.de> wrote:
>> >> > Maybe we should move all this open projects wiki stuff into tickets
>> >> > with
>> >> > some sort of "GSoC" tag.
>> >> >
>> >> > --
>> >> > Sebastian Huber, embedded brains GmbH
>> >> >
>> >> > Address : Dornierstr. 4, D-82178 Puchheim, Germany
>> >> > Phone   : +49 89 189 47 41-16
>> >> > Fax     : +49 89 189 47 41-09
>> >> > E-Mail  : sebastian.huber at embedded-brains.de
>> >> > PGP     : Public key available on request.
>> >> >
>> >> > Diese Nachricht ist keine geschäftliche Mitteilung im Sinne des EHUG.
>> >> >
>> >> _______________________________________________
>> >> devel mailing list
>> >> devel at rtems.org
>> >> http://lists.rtems.org/mailman/listinfo/devel
>> >
>> >
>> _______________________________________________
>> devel mailing list
>> devel at rtems.org
>> http://lists.rtems.org/mailman/listinfo/devel
>
>


More information about the devel mailing list