Workflows Archive on lore.kernel.org
 help / color / Atom feed
From: Michael Turquette <mturquette@baylibre.com>
To: Lukas Bulwahn <lukas.bulwahn@gmail.com>
Cc: workflows@vger.kernel.org,
	Till Kamppeter <till.kamppeter@gmail.com>,
	Aveek Basu <basu.aveek@gmail.com>,
	Stephen Boyd <sboyd@kernel.org>
Subject: Re: Explore ideas on workflows improvements with Google Summer of Code mentoring program?
Date: Wed, 22 Jan 2020 14:22:10 -0800
Message-ID: <CAEG3pNBvpT3VZxVr1TG7kf9qpTD-rWGu3qsLBLDKM0D5zBs1eQ@mail.gmail.com> (raw)
In-Reply-To: <CAKXUXMyR0pk7WUBY3wqgFkNrwTMBX6+diUPeCaOHo=AWCfJvFA@mail.gmail.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

      reply index

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-01-14 18:07 Lukas Bulwahn
2020-01-15 22:07 ` Michael Turquette
2020-01-15 23:03   ` Bjorn Helgaas
2020-01-16 19:39     ` Michael Turquette
2020-01-17  1:34     ` Stephen Boyd
2020-01-16  0:59   ` Daniel Axtens
2020-01-16 19:35     ` Michael Turquette
2020-01-17  2:19       ` Daniel Axtens
2020-01-17 20:25   ` Lukas Bulwahn
2020-01-17 20:38     ` Michael Turquette
2020-01-18  7:18       ` Lukas Bulwahn
2020-01-21 22:14         ` Michael Turquette
2020-01-22  6:18           ` Lukas Bulwahn
2020-01-22 22:22             ` Michael Turquette [this message]

Reply instructions:

You may reply publically to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAEG3pNBvpT3VZxVr1TG7kf9qpTD-rWGu3qsLBLDKM0D5zBs1eQ@mail.gmail.com \
    --to=mturquette@baylibre.com \
    --cc=basu.aveek@gmail.com \
    --cc=lukas.bulwahn@gmail.com \
    --cc=sboyd@kernel.org \
    --cc=till.kamppeter@gmail.com \
    --cc=workflows@vger.kernel.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link

Workflows Archive on lore.kernel.org

Archives are clonable:
	git clone --mirror https://lore.kernel.org/workflows/0 workflows/git/0.git

	# If you have public-inbox 1.1+ installed, you may
	# initialize and index your mirror using the following commands:
	public-inbox-init -V2 workflows workflows/ https://lore.kernel.org/workflows \
		workflows@vger.kernel.org
	public-inbox-index workflows

Example config snippet for mirrors

Newsgroup available over NNTP:
	nntp://nntp.lore.kernel.org/org.kernel.vger.workflows


AGPL code for this site: git clone https://public-inbox.org/public-inbox.git