#91 Application for becoming an Outreachy Coordinator
Closed 3 years ago by siddharthvipul1. Opened 3 years ago by nasirhm.

Hey everyone, I'm nasirhm and I would like to apply for becoming a Fedora Outreachy Coordinator.

FAS: @nasirhm

My Fedora Activities Include:

  • Core Member at Fedora i3 SiG (Developing a Fedora i3 Based respin)
  • Active Member of the Fedora Diversity and Inclusion Team, Fedora Join SIG and QA Team
  • Working on Fedora Badges Backend, Møte development and some bits and bytes at Fedora Core OS and Containers SIG
  • Google Code In 2019 Participant

I would like to provide some help on the Outreachy side of things.


Hi @nasirhm
Administration (coordination) is the highest level of access for the outreachy program from an org point of view. You can accept and reject projects and same with mentors and participants.
One needs to be aware of how Fedora Summer Coding works at-least a couple of times before taking this responsibility (IMO).
Since you have not participated in Outreachy or GSoC at all, it's difficult to justify your understanding of the mentored-projects. I would recommend you to participate in outreachy or GSoC as mentor/supporting mentor first and after a couple of times we can initiate the process of making you a coordinator.
also, add these to the point that there are 3 outreachy coordinators right now (@sayanchowdhury, @riecatnor and I) and we are not looking for any new coordinator. Projects ideas? very much so! So if you have a project idea you want to mentor along with someone else, please open a new ticket with relevant ticket type.
you can also help us by sharing words about our participation in the program so that we get great applicants.
For now, I will have to give a -1 to this ticket.
If you have any questions, please don't hesitate to ping me on IRC :)

I will leave this ticket open for a couple of days in case someone wants to add something

Hi @nasirhm I am thrilled that you want to get more involved in our intern projects! I tend to agree with Vipul on the various points. Beyond that there is only so much to be done, and a lot that I do is administrative through Red Hat.

Project ideas & mentoring is a great place to start! We could work on some marketing materials or ways to promote our participation(blogging, social media, etc). We could work on documentation (if needed, @siddharthvipul1 will know :)).

@nasirhm your enthusiasm is appreciated and a treasure in the Fedora community. Keep it up! Make sure not to take too much on tho :)

One needs to be aware of how Fedora Summer Coding works at-least a couple of times before taking this responsibility (IMO).
Since you have not participated in Outreachy or GSoC at all, it's difficult to justify your understanding of the mentored-projects. I would recommend you to participate in outreachy or GSoC as mentor/supporting mentor first and after a couple of times we can initiate the process of making you a coordinator.

Makes sense, mentoring / sub-mentoring an Intern would surely be a good place to start with.

also, add these to the point that there are 3 outreachy coordinators right now (@sayanchowdhury, @riecatnor and I) and we are not looking for any new coordinator. Projects ideas? very much so! So if you have a project idea you want to mentor along with someone else, please open a new ticket with relevant ticket type.

Hmm, for sure.

@riecatnor says:

Project ideas & mentoring is a great place to start! We could work on some marketing materials or ways to promote our participation(blogging, social media, etc). We could work on documentation (if needed, @siddharthvipul1 will know :)).

Sure. :)

@nasirhm your enthusiasm is appreciated and a treasure in the Fedora community. Keep it up! Make sure not to take too much on tho :)

Thanks you @riecatnor for the kind words, Trying to contribute back to Fedora at places where I can and learn from some awesome people. :)

Thanks @siddharthvipul1 and @riecatnor for the information.

Metadata Update from @siddharthvipul1:
- Issue status updated to: Closed (was: Open)

3 years ago

Login to comment on this ticket.

Metadata