#47 Outreachy Summer 2018
Closed: Complete 6 years ago Opened 6 years ago by labbott.

Now that the current Outreachy round has started it's time to start thinking about the next round. I do realize this is very early but I wanted to file a ticket as a place holder for discussion before it gets lost in the shuffle.


Metadata Update from @jflory7:
- Issue priority set to: normal (3-4 weeks)
- Issue set to the milestone: Fedora 28 (to May 2018)
- Issue tagged with: budget, meeting, outreach

6 years ago

Thanks @labbott for opening this one. I will add this to our next year goals.

As a general FYI, the Outreachy flow is changing its logistics slightly https://github.com/sagesharp/outreachy-django-wagtail/blob/master/docs/onboarding-coordinator-flow.md so we should review that for how it would impact Fedora (my reading, mostly just adding more steps and means we need to be on top of approvals more)

thanks for sharing it @labbott , we will keep that in mind for next time.

Metadata Update from @jflory7:
- Issue untagged with: meeting
- Issue priority set to: by next release (was: normal (3-4 weeks))
- Issue set to the milestone: Future releases (was: Fedora 28 (to May 2018))

6 years ago

It would be good to see the diversity team decide if they want to fund an outreachy internship for May 2018 right now. If there is a desire to do this, please open a council ticket ASAP and request an allocation of $6500 for this. I'd like to get this paid in FY18 (by March 1, 2018).

Also, if Outreachy funding is a continuing goal of the Diversity team, please make a note to file a council ticket AFTER MARCH 1, 2019, and request funding for $13000 to support one position in both December 2018 and May 2019. This will allow me to queue up the finances if the team wants this and the council approves it.

I am +1 to funding Outreachy from D&I budget in May 2018, and beyond in Dec. 2018 / May 2019.

+1, for funding Outreachy intern(s) in upcoming round and beyond (assuming we have project proposals to offer interns).

However, we also need some efforts so that Outreachy interns feel that they want to contribute to Fedora even beyond the internship. I feel that a sense of being a part of the project community and not just limited to Outreachy mentors during the internship helps in this regard, along with having some help from mentors during the transition (other areas to contribute to if the project was limited to the internship). However, this is from my own Outreachy experience and feedback is welcome. In regards to the first point, I can work on a Community Blog post with the current interns to showcase their work to the Fedora community. Also, as a part of their internship, Outreachy interns write blog posts regarding their project. The first blog post is usually about the application - to do's and dont's. We can try to aggregate such blogposts from past Fedora interns so that it can help future applicants during their application process.

Let me know what you think.

+1, for funding Outreachy intern(s) in upcoming round and beyond (assuming we have project proposals to offer interns).

+1 from me too

+1 but I'd like more head time next year so we have the details (project, mentors, stuffs...)

Thanks for supporting Fedora's participation in Outreachy! It looks like there is a consensus in the team about participating. Could someone please file a ticket with the council as soon as possible for funding one intern with $6,500 from FY18 budget. We'll need the council to vote on it, bex make a requisition, and Software Freedom Conservancy invoice Red Hat by February 20.

@amsharma @jflory7 could one of you file the ticket with the council as soon as possible? thank you!

@amsharma @jflory7 could one of you file the ticket with the council as soon as possible? thank you!

@marinaz https://pagure.io/Fedora-Council/tickets/issue/184

Here is the community blog post interviewing interns for Dec-Mar 2018 round: https://communityblog.fedoraproject.org/outreachy-2017-meet-interns/

Here is a blog post which aggregates blog posts by past interns (some Fedora) about do's and dont's during application process:
https://networksfordata.wordpress.com/2018/03/07/how-to-outreachy/

@labbott Should we share it with current applicants so that it's helpful for them? maybe via the mailing list?

Also, here is a timeline we can follow for next Outreachy cycle so that we don't rush as much -

March

  • Feedback email to Dec-Mar 2018 interns, mentors about their Outreachy experience.

May

  • Engage with incoming Outreachy and RSOC interns, welcome to the community.

July

  • Publish CommBlog post with interviews with interns showcasing their work
  • Discuss participation and logistics (budget and swag planning process) for the upcoming Outreachy round.

August end - September

  • Call for projects for the upcoming Outreachy round.
  • Support Outreachy co-ordinators
  • Feedback email to interns, mentors about their Outreachy experience.

December

  • Engage with incoming Outreachy interns, welcome to the community
  • Discuss participation, and logistics (budget and swag planning) for upcoming Outreachy and RSOC round

Jan

  • Call for projects for RSOC
  • Support RSOC coordinators

Feb

  • Publish CommBlog post with interviews with interns showcasing their work
  • Call for projects for the upcoming Outreachy round.
  • Support Outreachy co-ordinators

I have included Rails Summer of Code (RSOC) as it is easier to have a unified calendar for both.

@jflory7 since these are not meetings, anyway we can add this to Fedocal? Then we can close this ticket.

Do we want to have all these work items assigned as well, so that we won't skip them.

The schedule is great, I started something similar in the mentored-projects repo. Would you like to move a copy of the schedule there so we have it in our reference materials?

@labbott Does the fork need approval? Accesing my fork gives me a Bad Link Error. Once this is set, I can submit a PR with edited timeline.txt

@amsharma It would be too soon to assign a single person. Maybe we review tasks for next month in diversity meetings the month before?

@labbott I have submitted a PR with changes :) Also, should we add a RGSoC folder to the repo too?

I propose we close this ticket and open smaller ones for individual tasks.

Metadata Update from @bee2502:
- Issue close_status updated to: Complete
- Issue status updated to: Closed (was: Open)

6 years ago

@bee2502 said…
Also, should we add a RGSoC folder to the repo too?

I'm not sure if we need to do this yet, since we are only sponsoring, not participating as an organization. We should keep this in mind if we participate as a project in 2019.

@bee2502 said…
I propose we close this ticket and open smaller ones for individual tasks.

+1. This will be easier to keep up with.

Metadata Update from @jflory7:
- Issue set to the milestone: Fedora 29 (to Oct. 2018) (was: Future releases)

5 years ago

Login to comment on this ticket.

Metadata