You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@diversity.apache.org by Griselda Cuevas <gr...@apache.org> on 2019/07/18 19:59:59 UTC
[Update] ASF's Outreachy program kick-off plan
Hi folks,
Context:
On June 24th Naomi proposed a framework for our Outreachy program [1], from
her proposal:
"...Outreachy presents a fantastic opportunity to work with and learn from
people as they go through that process
from the D&I committee's perspective, the purpose of each internship
should be to gather as much information as possible about the intern's
journey. and that information should focus on areas that relate to our
primary objective
mentors are responsible for gathering this information, and reporting
back to the D&I committee regularly. in particular, we should look at
creating something like what Google calls friction logs...."
Because of this framework, we need to set up the Outreachy program with two
components:
1) Outreachy program management (as any other Outreachy's community)
2) Connection to D&I efforts within the ASF
This email outlines the plans for the first side only.
What happened:
Today, the Outreachy coordinators for Mozilla met with Matt & Katia
(Outreachy coordinators for the ASF) and Gris. Awasum (our third
coordinator) was also invited but couldn't make it.
The purpose of the call was to understand the coordinator's duties and
role. The call was very helpful as it provided useful information for our
coordinators, and it helped them put together an action plan to set up the
program for the ASF.
What's coming next:
- Katia, Awasum and Matt will have full autonomy to work as the ASF
outreachy coordinators. I've asked them to share updates with the committee
weekly from now until we launch
- I will work with Naomi on a plan to organize the second component of this
program (The connection between the Outreachy internships and the D&I
efforts to do Experience research)
Let me know if there are questions, suggestions, etc.
G
P.S. Katia is BRAND NEW to the ASF, she found us through the diversity@
list, and when she saw an oppty to help, she decided to join us :)
[1]
https://lists.apache.org/thread.html/dbba6f4fd358737fddcb3da4b78df4f87fe384d59a35469a0d131545@%3Cdev.diversity.apache.org%3E
<https://lists.apache.org/thread.html/dbba6f4fd358737fddcb3da4b78df4f87fe384d59a35469a0d131545@%3Cdev.diversity.apache.org%3E>
Re: [Update] ASF's Outreachy program kick-off plan
Posted by Myrle Krantz <my...@apache.org>.
On Thu, Jul 18, 2019 at 10:00 PM Griselda Cuevas <gr...@apache.org> wrote:
> P.S. Katia is BRAND NEW to the ASF, she found us through the diversity@
> list, and when she saw an oppty to help, she decided to join us :)
>
Welcome Katja!!! Thank you so much for volunteering to help us with this!
: o),
Myrle
Re: [Update] ASF's Outreachy program kick-off plan
Posted by Katia Rojas <ka...@gmail.com>.
Thanks, Joan. As a brand new member here, all the guidance is appreciated!
On Thu, Jul 18, 2019 at 10:41 PM Matt Sicker <bo...@gmail.com> wrote:
> Thanks for the resources, Joan! I was curious how we handled GSoC, and
> this should help a lot.
>
> On Thu, 18 Jul 2019 at 15:32, Joan Touzet <wo...@apache.org> wrote:
> >
> > Hi Gris,
> >
> > Thanks for taking this initiative.
> >
> > Can you make sure that Awasum, Matt & Katia get pointers to the ASF
> > Google Summer of Code framework that's been put in place, as an exemplar
> > of something the ASF has implemented successfully? My hope is that
> > between this and Outreachy's own guidelines, we can come up with the
> > structure we'll need to guide PMCs in making their submissions to
> Outreachy.
> >
> > If they're all on the list, some links to start with might be:
> >
> > http://community.apache.org/gsoc.html
> >
> >
> https://www.slideshare.net/smarru/google-summer-of-code-at-apache-software-foundation
> > (especially slides 12, 14, 15, 18)
> >
> >
> https://summerofcode.withgoogle.com/archive/2018/organizations/5175246747336704/
> >
> > https://cwiki.apache.org/confluence/display/SAMZA/Google+Summer+of+Code
> >
> > Thanks,
> > Joan
> >
> > On 2019-07-18 15:59, Griselda Cuevas wrote:
> > > Hi folks,
> > >
> > > Context:
> > > On June 24th Naomi proposed a framework for our Outreachy program [1],
> from
> > > her proposal:
> > > "...Outreachy presents a fantastic opportunity to work with and learn
> from
> > > people as they go through that process
> > >
> > > from the D&I committee's perspective, the purpose of each internship
> > > should be to gather as much information as possible about the
> intern's
> > > journey. and that information should focus on areas that relate to
> our
> > > primary objective
> > >
> > > mentors are responsible for gathering this information, and
> reporting
> > > back to the D&I committee regularly. in particular, we should look
> at
> > > creating something like what Google calls friction logs...."
> > >
> > > Because of this framework, we need to set up the Outreachy program
> with two
> > > components:
> > > 1) Outreachy program management (as any other Outreachy's community)
> > > 2) Connection to D&I efforts within the ASF
> > > This email outlines the plans for the first side only.
> > >
> > > What happened:
> > > Today, the Outreachy coordinators for Mozilla met with Matt & Katia
> > > (Outreachy coordinators for the ASF) and Gris. Awasum (our third
> > > coordinator) was also invited but couldn't make it.
> > >
> > > The purpose of the call was to understand the coordinator's duties and
> > > role. The call was very helpful as it provided useful information for
> our
> > > coordinators, and it helped them put together an action plan to set up
> the
> > > program for the ASF.
> > >
> > > What's coming next:
> > > - Katia, Awasum and Matt will have full autonomy to work as the ASF
> > > outreachy coordinators. I've asked them to share updates with the
> committee
> > > weekly from now until we launch
> > > - I will work with Naomi on a plan to organize the second component of
> this
> > > program (The connection between the Outreachy internships and the D&I
> > > efforts to do Experience research)
> > >
> > > Let me know if there are questions, suggestions, etc.
> > > G
> > >
> > > P.S. Katia is BRAND NEW to the ASF, she found us through the diversity@
> > > list, and when she saw an oppty to help, she decided to join us :)
> > >
> > > [1]
> > >
> https://lists.apache.org/thread.html/dbba6f4fd358737fddcb3da4b78df4f87fe384d59a35469a0d131545@%3Cdev.diversity.apache.org%3E
> > >
> > >
> > > <
> https://lists.apache.org/thread.html/dbba6f4fd358737fddcb3da4b78df4f87fe384d59a35469a0d131545@%3Cdev.diversity.apache.org%3E
> >
> > >
> >
>
>
> --
> Matt Sicker <bo...@gmail.com>
>
Re: [Update] ASF's Outreachy program kick-off plan
Posted by Matt Sicker <bo...@gmail.com>.
Thanks for the resources, Joan! I was curious how we handled GSoC, and
this should help a lot.
On Thu, 18 Jul 2019 at 15:32, Joan Touzet <wo...@apache.org> wrote:
>
> Hi Gris,
>
> Thanks for taking this initiative.
>
> Can you make sure that Awasum, Matt & Katia get pointers to the ASF
> Google Summer of Code framework that's been put in place, as an exemplar
> of something the ASF has implemented successfully? My hope is that
> between this and Outreachy's own guidelines, we can come up with the
> structure we'll need to guide PMCs in making their submissions to Outreachy.
>
> If they're all on the list, some links to start with might be:
>
> http://community.apache.org/gsoc.html
>
> https://www.slideshare.net/smarru/google-summer-of-code-at-apache-software-foundation
> (especially slides 12, 14, 15, 18)
>
> https://summerofcode.withgoogle.com/archive/2018/organizations/5175246747336704/
>
> https://cwiki.apache.org/confluence/display/SAMZA/Google+Summer+of+Code
>
> Thanks,
> Joan
>
> On 2019-07-18 15:59, Griselda Cuevas wrote:
> > Hi folks,
> >
> > Context:
> > On June 24th Naomi proposed a framework for our Outreachy program [1], from
> > her proposal:
> > "...Outreachy presents a fantastic opportunity to work with and learn from
> > people as they go through that process
> >
> > from the D&I committee's perspective, the purpose of each internship
> > should be to gather as much information as possible about the intern's
> > journey. and that information should focus on areas that relate to our
> > primary objective
> >
> > mentors are responsible for gathering this information, and reporting
> > back to the D&I committee regularly. in particular, we should look at
> > creating something like what Google calls friction logs...."
> >
> > Because of this framework, we need to set up the Outreachy program with two
> > components:
> > 1) Outreachy program management (as any other Outreachy's community)
> > 2) Connection to D&I efforts within the ASF
> > This email outlines the plans for the first side only.
> >
> > What happened:
> > Today, the Outreachy coordinators for Mozilla met with Matt & Katia
> > (Outreachy coordinators for the ASF) and Gris. Awasum (our third
> > coordinator) was also invited but couldn't make it.
> >
> > The purpose of the call was to understand the coordinator's duties and
> > role. The call was very helpful as it provided useful information for our
> > coordinators, and it helped them put together an action plan to set up the
> > program for the ASF.
> >
> > What's coming next:
> > - Katia, Awasum and Matt will have full autonomy to work as the ASF
> > outreachy coordinators. I've asked them to share updates with the committee
> > weekly from now until we launch
> > - I will work with Naomi on a plan to organize the second component of this
> > program (The connection between the Outreachy internships and the D&I
> > efforts to do Experience research)
> >
> > Let me know if there are questions, suggestions, etc.
> > G
> >
> > P.S. Katia is BRAND NEW to the ASF, she found us through the diversity@
> > list, and when she saw an oppty to help, she decided to join us :)
> >
> > [1]
> > https://lists.apache.org/thread.html/dbba6f4fd358737fddcb3da4b78df4f87fe384d59a35469a0d131545@%3Cdev.diversity.apache.org%3E
> >
> >
> > <https://lists.apache.org/thread.html/dbba6f4fd358737fddcb3da4b78df4f87fe384d59a35469a0d131545@%3Cdev.diversity.apache.org%3E>
> >
>
--
Matt Sicker <bo...@gmail.com>
Re: [Update] ASF's Outreachy program kick-off plan
Posted by Awasum Yannick <aw...@apache.org>.
On Thu, Jul 18, 2019 at 9:32 PM Joan Touzet <wo...@apache.org> wrote:
> Hi Gris,
>
> Thanks for taking this initiative.
>
> Can you make sure that Awasum, Matt & Katia get pointers to the ASF
> Google Summer of Code framework that's been put in place, as an exemplar
> of something the ASF has implemented successfully? My hope is that
> between this and Outreachy's own guidelines, we can come up with the
> structure we'll need to guide PMCs in making their submissions to
> Outreachy.
>
>
Thank you Joan, We are in contact with GSoC Org admins for Apache and might
even schedule a call to get advice and learn from their experiences.
This will help us together with what we learn from Mozilla to have a good
way to run our Outreachy program.
If they're all on the list, some links to start with might be:
>
> http://community.apache.org/gsoc.html
>
>
> https://www.slideshare.net/smarru/google-summer-of-code-at-apache-software-foundation
> (especially slides 12, 14, 15, 18)
>
>
> https://summerofcode.withgoogle.com/archive/2018/organizations/5175246747336704/
>
> https://cwiki.apache.org/confluence/display/SAMZA/Google+Summer+of+Code
>
> Thanks,
> Joan
>
> On 2019-07-18 15:59, Griselda Cuevas wrote:
> > Hi folks,
> >
> > Context:
> > On June 24th Naomi proposed a framework for our Outreachy program [1],
> from
> > her proposal:
> > "...Outreachy presents a fantastic opportunity to work with and learn
> from
> > people as they go through that process
> >
> > from the D&I committee's perspective, the purpose of each internship
> > should be to gather as much information as possible about the intern's
> > journey. and that information should focus on areas that relate to our
> > primary objective
> >
> > mentors are responsible for gathering this information, and reporting
> > back to the D&I committee regularly. in particular, we should look at
> > creating something like what Google calls friction logs...."
> >
> > Because of this framework, we need to set up the Outreachy program with
> two
> > components:
> > 1) Outreachy program management (as any other Outreachy's community)
> > 2) Connection to D&I efforts within the ASF
> > This email outlines the plans for the first side only.
> >
> > What happened:
> > Today, the Outreachy coordinators for Mozilla met with Matt & Katia
> > (Outreachy coordinators for the ASF) and Gris. Awasum (our third
> > coordinator) was also invited but couldn't make it.
> >
> > The purpose of the call was to understand the coordinator's duties and
> > role. The call was very helpful as it provided useful information for our
> > coordinators, and it helped them put together an action plan to set up
> the
> > program for the ASF.
> >
> > What's coming next:
> > - Katia, Awasum and Matt will have full autonomy to work as the ASF
> > outreachy coordinators. I've asked them to share updates with the
> committee
> > weekly from now until we launch
> > - I will work with Naomi on a plan to organize the second component of
> this
> > program (The connection between the Outreachy internships and the D&I
> > efforts to do Experience research)
> >
> > Let me know if there are questions, suggestions, etc.
> > G
> >
> > P.S. Katia is BRAND NEW to the ASF, she found us through the diversity@
> > list, and when she saw an oppty to help, she decided to join us :)
> >
> > [1]
> >
> https://lists.apache.org/thread.html/dbba6f4fd358737fddcb3da4b78df4f87fe384d59a35469a0d131545@%3Cdev.diversity.apache.org%3E
> >
> >
> > <
> https://lists.apache.org/thread.html/dbba6f4fd358737fddcb3da4b78df4f87fe384d59a35469a0d131545@%3Cdev.diversity.apache.org%3E
> >
> >
>
>
Re: [Update] ASF's Outreachy program kick-off plan
Posted by Joan Touzet <wo...@apache.org>.
Hi Gris,
Thanks for taking this initiative.
Can you make sure that Awasum, Matt & Katia get pointers to the ASF
Google Summer of Code framework that's been put in place, as an exemplar
of something the ASF has implemented successfully? My hope is that
between this and Outreachy's own guidelines, we can come up with the
structure we'll need to guide PMCs in making their submissions to Outreachy.
If they're all on the list, some links to start with might be:
http://community.apache.org/gsoc.html
https://www.slideshare.net/smarru/google-summer-of-code-at-apache-software-foundation
(especially slides 12, 14, 15, 18)
https://summerofcode.withgoogle.com/archive/2018/organizations/5175246747336704/
https://cwiki.apache.org/confluence/display/SAMZA/Google+Summer+of+Code
Thanks,
Joan
On 2019-07-18 15:59, Griselda Cuevas wrote:
> Hi folks,
>
> Context:
> On June 24th Naomi proposed a framework for our Outreachy program [1], from
> her proposal:
> "...Outreachy presents a fantastic opportunity to work with and learn from
> people as they go through that process
>
> from the D&I committee's perspective, the purpose of each internship
> should be to gather as much information as possible about the intern's
> journey. and that information should focus on areas that relate to our
> primary objective
>
> mentors are responsible for gathering this information, and reporting
> back to the D&I committee regularly. in particular, we should look at
> creating something like what Google calls friction logs...."
>
> Because of this framework, we need to set up the Outreachy program with two
> components:
> 1) Outreachy program management (as any other Outreachy's community)
> 2) Connection to D&I efforts within the ASF
> This email outlines the plans for the first side only.
>
> What happened:
> Today, the Outreachy coordinators for Mozilla met with Matt & Katia
> (Outreachy coordinators for the ASF) and Gris. Awasum (our third
> coordinator) was also invited but couldn't make it.
>
> The purpose of the call was to understand the coordinator's duties and
> role. The call was very helpful as it provided useful information for our
> coordinators, and it helped them put together an action plan to set up the
> program for the ASF.
>
> What's coming next:
> - Katia, Awasum and Matt will have full autonomy to work as the ASF
> outreachy coordinators. I've asked them to share updates with the committee
> weekly from now until we launch
> - I will work with Naomi on a plan to organize the second component of this
> program (The connection between the Outreachy internships and the D&I
> efforts to do Experience research)
>
> Let me know if there are questions, suggestions, etc.
> G
>
> P.S. Katia is BRAND NEW to the ASF, she found us through the diversity@
> list, and when she saw an oppty to help, she decided to join us :)
>
> [1]
> https://lists.apache.org/thread.html/dbba6f4fd358737fddcb3da4b78df4f87fe384d59a35469a0d131545@%3Cdev.diversity.apache.org%3E
>
>
> <https://lists.apache.org/thread.html/dbba6f4fd358737fddcb3da4b78df4f87fe384d59a35469a0d131545@%3Cdev.diversity.apache.org%3E>
>
Re: [Update] ASF's Outreachy program kick-off plan
Posted by Katia Rojas <ka...@gmail.com>.
Hello,
Regarding this question: are mentors signing as individuals or on behalf of
the ASF?
I already asked how Mozilla handle this to Kelsey. I will share information
when I get it.
Katia
On Fri, Jul 19, 2019 at 5:58 AM Matt Sicker <bo...@gmail.com> wrote:
> I thought it was individuals signing the mentor agreements at least, though
> it’s been a while since I filled that out.
>
> On Thu, Jul 18, 2019 at 20:55, Sam Ruby <ru...@intertwingly.net> wrote:
>
> > On Thu, Jul 18, 2019 at 9:07 PM Niclas Hedhman <ni...@hedhman.org>
> wrote:
> > >
> > > On Fri, Jul 19, 2019 at 4:00 AM Griselda Cuevas <gr...@apache.org>
> wrote:
> > >
> > > >
> > > > What's coming next:
> > > > - Katia, Awasum and Matt will have full autonomy to work as the ASF
> > > > outreachy coordinators. I've asked them to share updates with the
> > committee
> > > > weekly from now until we launch
> > > >
> > >
> > > One small nitpick, and it could be me misinterpreting the language;
> > >
> > > "full autonomy" can't be delegated to a non-officer of ASF. Any
> > commitment
> > > on behalf of the ASF requires an officer, and that it is within the
> > > officer's mandate.
> > >
> > > I hope/assume that you mean, that they will do a lot of the work, keep
> > you
> > > in the loop and any official agreement/commitment on behalf of ASF is
> in
> > > your hands, preferably consulted with President (ultimately responsible
> > for
> > > a bad decision) and possibly helpful (ex-)Directors.
> >
> > The closest parallel I see is that VP Conferences (Rich) has
> > designated a number of (non-officer) Event Coordinators, each of which
> > is the key decision maker for that event. If coodinators are
> > producing weekly reports I'm confident that the oversight requirements
> > will be amply met, particularly given the number of current and
> > previous Directors on this committee.
> >
> > Signing authority could conceivably be a concern, but Outreachy only
> > requires interns and mentors to sign agreements. This does bring up
> > an interesting question: are mentors signing as individuals or on
> > behalf of the ASF. Perhaps someone could reach to Mozilla to see how
> > they handle this?
> >
> > - Sam Ruby
> >
> --
> Matt Sicker <bo...@gmail.com>
>
Re: [Update] ASF's Outreachy program kick-off plan
Posted by Katia Rojas <ka...@gmail.com>.
Hi folks,
I guess you've seen a lot of activity in the mailing list today. To keep
you updated:
Yesterday Gris, Matt, Awasum and I met to coordinate next steps for the
Outreachy program. So far we successfully submitted Apache Organisation to
Outreachy and filled out sponsors details for initial round.
We are currently working in different tasks posted in Jira. You are welcome
to help us, give some comments or join us in our calls.
Cheers,
Katia
On Fri, Jul 26, 2019 at 12:45 AM Sage Sharp <sh...@otter.technology> wrote:
> Mentors sign the mentorship agreement as an individual. A generic version
> of the agreement can be found here:
> https://github.com/outreachy/website/blob/master/docs/mentor-agreement.md
>
> Sage Sharp
> Outreachy Organizer
>
> On Thu, Jul 18, 2019 at 8:58 PM Matt Sicker <bo...@gmail.com> wrote:
>
> > I thought it was individuals signing the mentor agreements at least,
> though
> > it’s been a while since I filled that out.
> >
> > On Thu, Jul 18, 2019 at 20:55, Sam Ruby <ru...@intertwingly.net> wrote:
> >
> > > On Thu, Jul 18, 2019 at 9:07 PM Niclas Hedhman <ni...@hedhman.org>
> > wrote:
> > > >
> > > > On Fri, Jul 19, 2019 at 4:00 AM Griselda Cuevas <gr...@apache.org>
> > wrote:
> > > >
> > > > >
> > > > > What's coming next:
> > > > > - Katia, Awasum and Matt will have full autonomy to work as the ASF
> > > > > outreachy coordinators. I've asked them to share updates with the
> > > committee
> > > > > weekly from now until we launch
> > > > >
> > > >
> > > > One small nitpick, and it could be me misinterpreting the language;
> > > >
> > > > "full autonomy" can't be delegated to a non-officer of ASF. Any
> > > commitment
> > > > on behalf of the ASF requires an officer, and that it is within the
> > > > officer's mandate.
> > > >
> > > > I hope/assume that you mean, that they will do a lot of the work,
> keep
> > > you
> > > > in the loop and any official agreement/commitment on behalf of ASF is
> > in
> > > > your hands, preferably consulted with President (ultimately
> responsible
> > > for
> > > > a bad decision) and possibly helpful (ex-)Directors.
> > >
> > > The closest parallel I see is that VP Conferences (Rich) has
> > > designated a number of (non-officer) Event Coordinators, each of which
> > > is the key decision maker for that event. If coodinators are
> > > producing weekly reports I'm confident that the oversight requirements
> > > will be amply met, particularly given the number of current and
> > > previous Directors on this committee.
> > >
> > > Signing authority could conceivably be a concern, but Outreachy only
> > > requires interns and mentors to sign agreements. This does bring up
> > > an interesting question: are mentors signing as individuals or on
> > > behalf of the ASF. Perhaps someone could reach to Mozilla to see how
> > > they handle this?
> > >
> > > - Sam Ruby
> > >
> > --
> > Matt Sicker <bo...@gmail.com>
> >
>
Re: [Update] ASF's Outreachy program kick-off plan
Posted by Sage Sharp <sh...@otter.technology>.
Mentors sign the mentorship agreement as an individual. A generic version
of the agreement can be found here:
https://github.com/outreachy/website/blob/master/docs/mentor-agreement.md
Sage Sharp
Outreachy Organizer
On Thu, Jul 18, 2019 at 8:58 PM Matt Sicker <bo...@gmail.com> wrote:
> I thought it was individuals signing the mentor agreements at least, though
> it’s been a while since I filled that out.
>
> On Thu, Jul 18, 2019 at 20:55, Sam Ruby <ru...@intertwingly.net> wrote:
>
> > On Thu, Jul 18, 2019 at 9:07 PM Niclas Hedhman <ni...@hedhman.org>
> wrote:
> > >
> > > On Fri, Jul 19, 2019 at 4:00 AM Griselda Cuevas <gr...@apache.org>
> wrote:
> > >
> > > >
> > > > What's coming next:
> > > > - Katia, Awasum and Matt will have full autonomy to work as the ASF
> > > > outreachy coordinators. I've asked them to share updates with the
> > committee
> > > > weekly from now until we launch
> > > >
> > >
> > > One small nitpick, and it could be me misinterpreting the language;
> > >
> > > "full autonomy" can't be delegated to a non-officer of ASF. Any
> > commitment
> > > on behalf of the ASF requires an officer, and that it is within the
> > > officer's mandate.
> > >
> > > I hope/assume that you mean, that they will do a lot of the work, keep
> > you
> > > in the loop and any official agreement/commitment on behalf of ASF is
> in
> > > your hands, preferably consulted with President (ultimately responsible
> > for
> > > a bad decision) and possibly helpful (ex-)Directors.
> >
> > The closest parallel I see is that VP Conferences (Rich) has
> > designated a number of (non-officer) Event Coordinators, each of which
> > is the key decision maker for that event. If coodinators are
> > producing weekly reports I'm confident that the oversight requirements
> > will be amply met, particularly given the number of current and
> > previous Directors on this committee.
> >
> > Signing authority could conceivably be a concern, but Outreachy only
> > requires interns and mentors to sign agreements. This does bring up
> > an interesting question: are mentors signing as individuals or on
> > behalf of the ASF. Perhaps someone could reach to Mozilla to see how
> > they handle this?
> >
> > - Sam Ruby
> >
> --
> Matt Sicker <bo...@gmail.com>
>
Re: [Update] ASF's Outreachy program kick-off plan
Posted by Matt Sicker <bo...@gmail.com>.
I thought it was individuals signing the mentor agreements at least, though
it’s been a while since I filled that out.
On Thu, Jul 18, 2019 at 20:55, Sam Ruby <ru...@intertwingly.net> wrote:
> On Thu, Jul 18, 2019 at 9:07 PM Niclas Hedhman <ni...@hedhman.org> wrote:
> >
> > On Fri, Jul 19, 2019 at 4:00 AM Griselda Cuevas <gr...@apache.org> wrote:
> >
> > >
> > > What's coming next:
> > > - Katia, Awasum and Matt will have full autonomy to work as the ASF
> > > outreachy coordinators. I've asked them to share updates with the
> committee
> > > weekly from now until we launch
> > >
> >
> > One small nitpick, and it could be me misinterpreting the language;
> >
> > "full autonomy" can't be delegated to a non-officer of ASF. Any
> commitment
> > on behalf of the ASF requires an officer, and that it is within the
> > officer's mandate.
> >
> > I hope/assume that you mean, that they will do a lot of the work, keep
> you
> > in the loop and any official agreement/commitment on behalf of ASF is in
> > your hands, preferably consulted with President (ultimately responsible
> for
> > a bad decision) and possibly helpful (ex-)Directors.
>
> The closest parallel I see is that VP Conferences (Rich) has
> designated a number of (non-officer) Event Coordinators, each of which
> is the key decision maker for that event. If coodinators are
> producing weekly reports I'm confident that the oversight requirements
> will be amply met, particularly given the number of current and
> previous Directors on this committee.
>
> Signing authority could conceivably be a concern, but Outreachy only
> requires interns and mentors to sign agreements. This does bring up
> an interesting question: are mentors signing as individuals or on
> behalf of the ASF. Perhaps someone could reach to Mozilla to see how
> they handle this?
>
> - Sam Ruby
>
--
Matt Sicker <bo...@gmail.com>
Re: [Update] ASF's Outreachy program kick-off plan
Posted by Sam Ruby <ru...@intertwingly.net>.
On Thu, Jul 18, 2019 at 9:07 PM Niclas Hedhman <ni...@hedhman.org> wrote:
>
> On Fri, Jul 19, 2019 at 4:00 AM Griselda Cuevas <gr...@apache.org> wrote:
>
> >
> > What's coming next:
> > - Katia, Awasum and Matt will have full autonomy to work as the ASF
> > outreachy coordinators. I've asked them to share updates with the committee
> > weekly from now until we launch
> >
>
> One small nitpick, and it could be me misinterpreting the language;
>
> "full autonomy" can't be delegated to a non-officer of ASF. Any commitment
> on behalf of the ASF requires an officer, and that it is within the
> officer's mandate.
>
> I hope/assume that you mean, that they will do a lot of the work, keep you
> in the loop and any official agreement/commitment on behalf of ASF is in
> your hands, preferably consulted with President (ultimately responsible for
> a bad decision) and possibly helpful (ex-)Directors.
The closest parallel I see is that VP Conferences (Rich) has
designated a number of (non-officer) Event Coordinators, each of which
is the key decision maker for that event. If coodinators are
producing weekly reports I'm confident that the oversight requirements
will be amply met, particularly given the number of current and
previous Directors on this committee.
Signing authority could conceivably be a concern, but Outreachy only
requires interns and mentors to sign agreements. This does bring up
an interesting question: are mentors signing as individuals or on
behalf of the ASF. Perhaps someone could reach to Mozilla to see how
they handle this?
- Sam Ruby
Re: [Update] ASF's Outreachy program kick-off plan
Posted by Niclas Hedhman <ni...@hedhman.org>.
On Fri, Jul 19, 2019 at 4:00 AM Griselda Cuevas <gr...@apache.org> wrote:
>
> What's coming next:
> - Katia, Awasum and Matt will have full autonomy to work as the ASF
> outreachy coordinators. I've asked them to share updates with the committee
> weekly from now until we launch
>
One small nitpick, and it could be me misinterpreting the language;
"full autonomy" can't be delegated to a non-officer of ASF. Any commitment
on behalf of the ASF requires an officer, and that it is within the
officer's mandate.
I hope/assume that you mean, that they will do a lot of the work, keep you
in the loop and any official agreement/commitment on behalf of ASF is in
your hands, preferably consulted with President (ultimately responsible for
a bad decision) and possibly helpful (ex-)Directors.
// Niclas