RE: Guiding volunteers

[Dennis E. Hamilton]

In the case of GSoC mentoring, one needed change is to add the search case 
http://s.apache.org/gsoc2016tasks or maybe a generic 
http://s.apache.org/gsoctasks.

Then the Guide to being a mentor can be updated to match that and not continue 
to mention "gsoc2011".  

This requires adding a public filter to the ASF JIRA and I am not certain who 
has the karma and skills to do that (being on a bugzilla-based project myself 
and my JIRA skills are past their use-by date).

QUESTION #1: If we want to broaden this mentoring of volunteers under other 
conditions, I assume that can be done by additional labelling cases along with 
or separate from any gsoc label.  Yes?

QUESTION #2: For non-GSoC mentoring of volunteers on a bugzilla-reliant 
project, I assume using the special JIRA arrangement and mailing list that has 
been dedicated to GSoC needs an alternative or modification.  We still need a 
generic place for volunteer to be able to look when looking for mentoring, but 
that might guide them to a variety of places.  Are there thoughts on how to 
flex that GSoC-focused arrangement in some manner, or to cross-connect with a 
generic arrangement?

 - Dennis


> -Original Message-
> From: Rich Bowen [mailto:rbo...@rcbowen.com]
> Sent: Friday, February 5, 2016 23:37
> To: dev@community.apache.org
> Subject: Re: Guiding volunteers
> 
> 
> 
> On 02/05/2016 08:23 AM, Ross Gardler wrote:
> > This focus on tooling is the wrong focus,
> 
> Yeah .. I was going to say ... we could spend weeks down the rat-hole of
> which tool, which tracker, which technology, and we'll lose track of the
> goal.
> 
> Invariably when I travel to events, I get excited about what we could do
> at Apache to get the word out, if only ... and then I get back home and
> real life pushes out those good intentions. Tomorrow is the last day of
> my travels. Perhaps I can get something done today ...
> 
> 
> 
> 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 http://community.apache.org/guide-to-being-a-
> mentor.html 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
> http://community.apache.org/guide-to-being-a-mentor.html
> >
> > 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 ;-)
> >
> >
> >
> > Ross
> >
> > -Original Message-
> > From: Venkat Raman [mailto:ramanindy...@gmail.com]
> > Sent: Thursday, February 4, 2016 7:55 PM
> > To: dev@community.apache.org
> > 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.
> >
> > Regards,
> > Venkat
> >
> > 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 

RE: Guiding volunteers

[Ross Gardler]

Q1 - already accounted for ("mentor" label)
Q2- already accounted for (and documented, use ComDev JIRA, sub the issue to 
dev mailing list)

The mentoring docs are already intended to be generic, I.e. Support non GSoC 
mentoring. Though I have no doubt they can be improved.

Sent from my Windows Phone

From: Dennis E. Hamilton
Sent: ‎2/‎6/‎2016 10:20 AM
To: dev@community.apache.org
Subject: RE: Guiding volunteers

In the case of GSoC mentoring, one needed change is to add the search case 
https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fs.apache.org%2fgsoc2016tasks=01%7c01%7cRoss.Gardler%40microsoft.com%7c4cd6f899105745ba25e108d32f223b14%7c72f988bf86f141af91ab2d7cd011db47%7c1=6lNYbRG9lkS2SzgNScAS2V0eqo7zXNlTD0wbkirxFFY%3d
 or maybe a generic 
https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fs.apache.org%2fgsoctasks.=01%7c01%7cRoss.Gardler%40microsoft.com%7c4cd6f899105745ba25e108d32f223b14%7c72f988bf86f141af91ab2d7cd011db47%7c1=hJfc%2bsPUbss9MoEuyDw%2bycYaXAGCzHHzez135tETK4A%3d

Then the Guide to being a mentor can be updated to match that and not continue 
to mention "gsoc2011".

This requires adding a public filter to the ASF JIRA and I am not certain who 
has the karma and skills to do that (being on a bugzilla-based project myself 
and my JIRA skills are past their use-by date).

QUESTION #1: If we want to broaden this mentoring of volunteers under other 
conditions, I assume that can be done by additional labelling cases along with 
or separate from any gsoc label.  Yes?

QUESTION #2: For non-GSoC mentoring of volunteers on a bugzilla-reliant 
project, I assume using the special JIRA arrangement and mailing list that has 
been dedicated to GSoC needs an alternative or modification.  We still need a 
generic place for volunteer to be able to look when looking for mentoring, but 
that might guide them to a variety of places.  Are there thoughts on how to 
flex that GSoC-focused arrangement in some manner, or to cross-connect with a 
generic arrangement?

 - Dennis


> -Original Message-
> From: Rich Bowen [mailto:rbo...@rcbowen.com]
> Sent: Friday, February 5, 2016 23:37
> To: dev@community.apache.org
> Subject: Re: Guiding volunteers
>
>
>
> On 02/05/2016 08:23 AM, Ross Gardler wrote:
> > This focus on tooling is the wrong focus,
>
> Yeah .. I was going to say ... we could spend weeks down the rat-hole of
> which tool, which tracker, which technology, and we'll lose track of the
> goal.
>
> Invariably when I travel to events, I get excited about what we could do
> at Apache to get the word out, if only ... and then I get back home and
> real life pushes out those good intentions. Tomorrow is the last day of
> my travels. Perhaps I can get something done today ...
>
>
>
> 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 
> > https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fcommunity.apache.org%2fguide-to-being-a-=01%7c01%7cRoss.Gardler%40microsoft.com%7c4cd6f899105745ba25e108d32f223b14%7c72f988bf86f141af91ab2d7cd011db47%7c1=3c30cYtsVivKqFCwuQry%2bjTUYvOco5smiw28P3AOI9E%3d
> mentor.html 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
> https://na01.safelinks.protection.outlook.com/?url=http%3a%2f%2fcommunity.apache.org%2fguide-to-being-a-mentor.html=01%7c01%7cRoss.Gardler%40microsoft.com%7c4cd6f899105745ba25e108d32f223b14%7c72f988bf86f141af91ab2d7cd011db47%7c1=jzKOdrzMpiM6btUeFMsL4%2b3XpRlR9Z0SLlJCjVYmUHQ%3d
> >
> > 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 ;-)
> >
> >
> >
> > Ross
> >
> > -Original Message-
> > From: Venkat Raman [mailto:ramanindy...@gmail.com]
> > Sent: Thursday, February 4, 2016 7:55 PM
> > To: dev@community.apache.org
> > 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.
> >
> > Regards,
> > Venkat
> >
> > 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 

Re: Making license adjustment tools publicly available

[Shane Curcuru]

Christopher wrote on 2/4/16 7:25 PM:
> It might be relevant that that both of those tools appear to be licensed
> under ASL 2.0, which explicitly permits redistribution (presumably outside
> the private area?). I would think it confusing to have an open source
> license on software which is expected to remain private, or otherwise
> restricted from redistribution. As such, it seems prudent to move them to a
> more appropriate area. That's my opinion, anyway.

Yes, the Apache license explicitly gives broad permissions.  But the ASF
organizationally is very conservative about actually redistributing
software.  That is, we *could* legally redistribute some random software
we found under AL or MIT or the like, but if someone makes it clear they
*didn't* intend to submit it to an Apache project, then we'll generally
respect their wishes.

In this case, it's all work done by ASF Committers for the purpose of
doing work on Apache projects, so I can't see why it would be a problem.
 It's most likely that once Apache projects finished updating to 2.0
license, no-one bothered to think of these tools again.

In any case, I would definitely recommend either testing them, or
putting in behavior so that it doesn't actually change files in the
default command line (to prevent surprises, if it doesn't work as
someone anticipated).

- Shane

> 
> On Thu, Feb 4, 2016 at 7:14 PM Roman Shaposhnik  wrote:
> 
>> Hi!
>>
>> a podling recently asked me why:
>> https://svn.apache.org/repos/private/committers/relicense/
>> https://svn.apache.org/repos/private/committers/tools/copy2license.pl
>> are only available to commiters. I see
>> no reason why, but of course I'm appreciative
>> of the warning here:
>> https://svn.apache.org/repos/private/committers/README
>>
>> Two questions:
>>1. Is there any disagreement that making this tool publically
>> available would be a 'good thing' ?
>> 2. Who should bless the svn mv if we all agree?
>>
>> Thanks,
>> Roman.
>>
>