Re: Explore ideas on workflows improvements with Google Summer of Code mentoring program?

[Michael Turquette <mturquette@baylibre.com>]

On Tue, Jan 21, 2020 at 10:19 PM Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
>
> On Tue, Jan 21, 2020 at 11:15 PM Michael Turquette
> <mturquette@baylibre.com> wrote:
> >
> > On Fri, Jan 17, 2020 at 11:18 PM Lukas Bulwahn <lukas.bulwahn@gmail.com> wrote:
> > >
> > > On Fri, Jan 17, 2020 at 9:38 PM Michael Turquette
> > > <mturquette@baylibre.com> wrote:
> > > >
> > > > I would be interested in learning more about the duties and
> > > > expectations of mentorship. Do you have a link? If it's not too much
> > > > work to add to my load then consider me interested.
> > > >
> > >
> > > The mentor GSoC guide tells you all you need to know:
> > >
> > > https://google.github.io/gsocguides/mentor/
> >
> > Count me in. The project that I described would be a new solution or
> > utility, and commits may not go into an existing open source project.
> > Is that OK for GSoC? If not then I have a related project idea that
> > would include code contributions to an existing FOSS project on
> > github, but prefer the current submission as-is.
> >
>
> Great!
>
> I have not check the Terms in full depth here:
> https://summerofcode.withgoogle.com/terms/org
> and IANAL.
>
> As I see it:
>
> - Mentor organizations must run an active open source or free software project.
> - Have produced and released software under an OSI approved license.
>
> (https://summerofcode.withgoogle.com/get-started/) is all covered.
>
> Important aspects for GSoC are:
>
> - there is a larger community for the student to announce his work,
> reach out to and impact: in this case, Linux kernel community, kernel
> workflows group, patchwork project team; we are well covered here.
> - it is published under an open-source license, that is clear how to cover here.
> - it becomes at some point a part of the larger software project. I
> would suggest that the work is in the end documented with pointers to
> sources etc. in the kernel maintainer handbook, i.e.,
> https://www.kernel.org/doc/html/latest/maintainer/index.html, with a
> suitable section on the topic. That gives a maintainer (that has time
> to read the kernel documentation) a fair chance of finding out about
> this tool.

Agreed on all points.

Best,
Mike

>
>
> Best regards,
>
> Lukas
>
>
> Lukas



-- 
Michael Turquette
CEO - Los Angeles, CA
BayLibre - At the Heart of Embedded Linux
http://baylibre.com/
Schedule a meeting: https://calendly.com/mturquette