All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alison Schofield <alison.schofield@intel.com>
To: "Ira Weiny" <ira.weiny@intel.com>,
	"Deepak R Varma" <drv@mailo.com>, Fabio <fmdefrancesco@gmail.com>,
	"Paul Moore" <paul@paul-moore.com>,
	"Anna Trikalinou" <atrikalinou@microsoft.com>,
	"Zahra Tarkhani" <ztarkhani@microsoft.com>,
	"Mickaël Salaün" <mic@digikod.net>,
	"James Morris" <JAMORRIS@microsoft.com>
Cc: Outreachy Linux Kernel <outreachy@lists.linux.dev>
Subject: [Outreachy Mentors] Starter Tasks
Date: Fri, 3 Mar 2023 10:52:17 -0800	[thread overview]
Message-ID: <ZAJB4b4MSKIdSyDL@aschofie-mobl2> (raw)

This message is for Project Mentors.

It's almost here! March 6th begins the contribution period for your
projects. Please check on your projects 'Starter Tasks'.

The "Starter Tasks" allow you to get to know and select a good fit
applicant. It also lets the applicants get to know your project, and
you all, as mentors. Please check your project view [1] and define a
couple of starter tasks as needed.

It may be helpful to toggle between editing your project forms, and
then view the result here. [1] This allows you to see how the community
info flows into the project info in the final view. FYI: I recently
updated the community info.

It is perfectly fine to update the starter tasks during the contribution
period. You might change tasks based on how they are working out. Note
that applicants will likely be busy with their community-wide contributions
for the first 2 weeks and not give projects much attention.

In the 'Define-a-project' page [2] it says: "You should have around 10-20
small newcomer tasks and 5-10 medium-sized tasks." You are not responsible
for defining that much, because the Linux Kernel community, has already
defined starter tasks called "Cleanup Patches" as a community-wide
contribution.

Samples of past project tasks: setup/run a project specific tool and share
output; review a topic area and write a blog post; and sometimes actually
submit a patch to the project.

Mentors are welcome to include a pointer to a personal page where
tasks are defined. Please don't make the first starter task 'email me
for starter tasks'.

Application Period == Contribution Period

[1] https://www.outreachy.org/outreachy-may-2023-internship-cohort/communities/linux-kernel/
[2] https://www.outreachy.org/mentor/mentor-faq/

Questions, please ask. Thanks for volunteering!

Alison

                 reply	other threads:[~2023-03-03 18:52 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly 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=ZAJB4b4MSKIdSyDL@aschofie-mobl2 \
    --to=alison.schofield@intel.com \
    --cc=JAMORRIS@microsoft.com \
    --cc=atrikalinou@microsoft.com \
    --cc=drv@mailo.com \
    --cc=fmdefrancesco@gmail.com \
    --cc=ira.weiny@intel.com \
    --cc=mic@digikod.net \
    --cc=outreachy@lists.linux.dev \
    --cc=paul@paul-moore.com \
    --cc=ztarkhani@microsoft.com \
    /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
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.