Our Application for GSoC is ready and we will make the submission deadline tomorrow. Therefore we should start working on ideas.
See https://docs.stg.fedoraproject.org/mentored-projects/gsoc/2018/#mentor-in... for details. Text is also below.
How to Propose a Project
If you want to mentor a specific project, think carefully about several things:
Do you have enough time to work on this with the student during the entire project. You will be helping someone else when they get stuck. You don’t want to become a blocker because you’re busy.
It is harder to find success when you are completely certain of how an idea needs to be implemented; finding a student with the skills and interest to implement a specific solution is a lot harder than finding a student with enough skills to respond to a use case need. Also, students learn more when they help design and guide the project. In other words, provide guidance and direction but let the student do some of the "driving."
Where you can have looser ideas, you may be able to find a student who works as a sort-of intern who can implement a solution to a use case you have. In past experiences, students going after a use case are more likely to get somewhere with self-direction and support from you.
Who can help you? Try to find a second mentor for the project.
If you’re interested in working with a student on a specific project you should post your idea to the Mentored Projects Issue Tracker. Your issue should be tagged GSoC and use the Google Summer of Code template. We strongly encourage you to find a second person to help with mentoring and to solicit feedback on your proposal
Can I be a Mentor Without a Project?
Yes! You can either:
Work with a student who brings an idea to your sub-project. This requires a different level of communication throughout the project, but can be the most rewarding.
Be a general mentor. This is a person who works with all students regardless of their project. To become a general mentor please open an issue in the Mentored Projects Issue Tracker offering your help. Please tag the issue with the GSoC tag.
We are looking for interested people who are willing to write docs in person for one week. You don't have to be an existing docs team member to participate. It helps if you're familiar with AsciiDoc, but if you're not, it's easy to learn.
You'll hang out with other people interested in making Fedora documentation the best in the world. Fun will be had, but mostly it will be the sort of fun which involves sitting in a small room intensely focused on writing and editing. If that's *your* idea of a good time, this will be a good experience for you.
You can find details about the FAD, including the goals here: https://fedoraproject.org/wiki/FAD_Documentation_2018
The Fedora Council has approved funding and we will make selections based on the ability to the person asking and within our approved travel budget. https://pagure.io/Fedora-Council/tickets/issue/174
Interested? Open a Pagure ticket in the Fedora Docs tracker here: https://pagure.io/fedora-docs
- Your Name/FAS
- Why you want to come and what your background in writing (of any kind) is.
- Any specific areas of interest
- Location you will travel from
We will start picking people ASAP.
bex & Matthew
I am going to start working on the Fedora GSoC Organizational application. I will also work on the structure for suggesting projects.
# If you want to mentor
Please use this time to start thinking about potential projects for GSoC Students. There are no wiki pages to update yet - you'll hear about those soon. (I think we might try something new this year to try and get more feedback on ideas).
# If you want to help in a general or administrative way
Contact me directly off list and we can figure out what works for you