community-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Ross Gardler <>
Subject RE: Guiding volunteers
Date Fri, 05 Feb 2016 07:24:34 GMT
Sorry I didn’t paste the markdown as promised, here it is:

<a name="guidetobeingamentor-Submittingideastothementoringprogramme"></a>
# Submitting ideas to the mentoring programme

All ASF projects are invited to submit their ideas for consideration in the
ASF mentoring programme. Any Apache member and experienced committers can
submit ideas via JIRA (if your project does not use JIRA you can [use the Comdev Issue Tracker
For GSoC Tasks](use-the-comdev-issue-tracker-for-gsoc-tasks.html). We are looking for as many
interesting projects as we can come up with. 

<a name="guidetobeingamentor-Summary"></a>
## Summary

* Add an issue to JIRA (if your project doesn't use JIRA contact
  * use sub-tasks if necessary
* Label the main issue with "mentor" (these will show up at the [ASF wide list of issues](
* Label the main issue with "gsoc2011" if appropriate (these will show up at <>)

<a name="guidetobeingamentor-Detail"></a>
## Detail

To ensure you JIRA issues are included in our list of mentored projects
please add the label "mentor" to the issue. If you want it to be included
in the Google Summer of Code lists also add the "gsoc" label. If you want
to include a number of issues in a single mentored project please create a
parent issue, label that one appropriately and add the other issues as
sub-tasks, do not label each individual sub task as they will appear as
separate tasks.

If a mentor has been identified then please assign the issue to that

ASF Members and committers can volunteer to mentor or co-mentor proposals.
When in doubt about all this, contact

For more information about what it means to be a mentor and on how to write
a proposal see:

  - [GSoC Mentoring Guide](
  - [GSoC Advice For Mentors](
  - [Gnome HowTo on mentoring](
  - [How to be a lazy but successful Google SoC mentor](

Note that interest, even by a qualified student, does not mean that any of
those project will automatically go ahead. Depending on the number of
projects; the number of people able to mentor and the timing we will
probably have to make a smaller selection.

<a name="guidetobeingamentor-Publicisingyourmentoredissues"></a>
### Publicising your mentored issues

You can link to the [ASF wide list of issues](
 or you can create your own lists and feeds within your own website.

Since your mentored issues are recorded alongside your normal issues you
can create and use filters to help people find them. You can provide RSS
feeds, JSON exports and many more goodies for helping to get the message

If you have any cool ideas for using this data please let us know so we can
share them with other projects (mail

<a name="guidetobeingamentor-Examples"></a>
## Examples

  - [Wookie GSoC Issues](
  - [Wookie RSS GSoC feed](
  - [Wookie XML GSoC feed](

<a name="guidetobeingamentor-Stayingintouch"></a>
# Staying in touch

All mentors *must* subscribe to, our list for
coordinating mentor activities. 

Subscriptions to code-awards will only be accepted from addresses known to
belong to ASF committers, so please use your address to
subscribe if possible, or at least an address that can be matched to your address via the ASF's private/committers/info or
private/committers/MailAlias.txt data.

If you are interested in the mentor programme administration please also
subscribe to

If you are planning on mentoring as part of the GSoC programme you also
need to register with Google, see our [GSoC](gsoc.html)
 page for more information.

<a name="guidetobeingamentor-Howmucheffortisinvolvedwithbeingamentor"></a>
## How much effort is involved with being a mentor

Most mentors spend between 3 and 5 hours per week with their students. Most
of this time is spent encouraging them.

Within the ASF we like to think that the whole project community will help
the student just as they would with any other community member. If your
project is supportive in this way then you may be able to get away with
less time. However, as mentor _you_ are responsible for evaluating the
student and helping them deliver on their commitments.

The [GSoC Mentoring Guide](
 has plenty of useful materials for mentors.

<a name="guidetobeingamentor-Anoteabouteligibility"></a>
## A note about eligibility

If your project has any restrictions on who can participate (as is the case
with Harmony for example) please be sure to clarify these with potential
students as early as possible. It causes unnecessary confusion and
dissapointment if a student is awarded a slot but is later found to be
ineligible. Don't rely on the fact that the student should have read
details on the project web site. You must discuss their eligibility before
offering to mentor them. Please also make a note in the webapp stating that
you have, as far as possible, confirmed the student is eligble to

-----Original Message-----
From: Ross Gardler [] 
Sent: Thursday, February 4, 2016 11:23 PM
Subject: RE: Guiding volunteers

This focus on tooling is the wrong focus, especially for those of us who don't know how to
get started on new tooling, or for those who recognize we already have a fine tool for the
job - we're just not communicating it well. 

Here are three concreate actions *anyone* with a little time available can take today.

1) Update the page at
to be more generic (i.e. not GSOC specific) and reflect the goals of this thread (if you don't
know how to use the ASF CMS to edit our site I've pasted the markdown below, just edit here
and someone can put it onto the site for you)

2) Pick your favourite project. Drop a mail to the dev list. Explain your motivation. Ask
them to mark issues according to the guidelines in

3) Get the message out to those who need a little guidance that they can find such issues
in JIRA (there are many ways this can be done, all of them are good ;-)


-----Original Message-----
From: Venkat Raman []
Sent: Thursday, February 4, 2016 7:55 PM
Subject: Re: Guiding volunteers

Hi -

It would be extremely helpful to have systems like savannah to newbies to dive in based on
their skill sets and area of interest.I would like to contribute as well. But, struggling
in the same way as others to get started.


On Thu, Feb 4, 2016 at 2:57 PM, Patricia Shanahan <> wrote:

> On 2/4/2016 10:35 AM, Greg Chase wrote:
>> On Thu, Feb 4, 2016 at 3:25 PM, Patricia Shanahan <> wrote:
>> An alternative approach would be a help-wanted page, organized 
>> according
>>> to skills, maintained on the same sort of system as the board agenda.
>>> Each
>>> PMC chair whose project is looking for volunteers would supply 
>>> information about their needs. The result would be a public web page 
>>> potential volunteers could search.
>>> Ideally, it would be on a whimsey-like system, but a start could be 
>>> made by just defining a format and keeping the master page in a PMC 
>>> chair accessible SVN archive.
>>> This is a wonderful idea.  I've been looking for a way to get the 
>>> various
>> incubating communities I'm helping organize recruit new contributors.
>> This
>> would help solve this problem by making it easier for (p)PMC's to 
>> articulate what they would like help with from new community members.
>> Obviously it would be an adhoc system, and up to projects to fill out 
>> and keep their want ad's up to date.  Perhaps a rule of the system 
>> would be that want ads are automatically deleted after a month if 
>> they aren't visited and renewed by project members to verify they are still current.
> I like the idea of automatic disappearance, but maybe make it three 
> months and tie it to the board report cycle - every time a PMC files a 
> board report, it should also check and update its help wanted.
>> So basically, I'm volunteering to help here :)
> I would also like to help, but don't know how to get something like 
> this started.
> Patricia

Thanks & Regards,

Venkat Raman. R
View raw message