From 28a8c4a4d025da497a2c9915d21583cc63ff3024 Mon Sep 17 00:00:00 2001
From: sumantro93 <sumantro@redhat.com>
Date: Feb 05 2024 23:03:29 +0000
Subject: gsoc for 2024


---

diff --git a/antora.yml b/antora.yml
index 5c6df5e..5da975c 100644
--- a/antora.yml
+++ b/antora.yml
@@ -1,6 +1,6 @@
 name: mentored-projects
 title: Mentored Projects
 version: ~
-start_page: ROOT:gsoc/2021/index.adoc
+start_page: ROOT:gsoc/2024/index.adoc
 nav:
 - modules/ROOT/nav.adoc
diff --git a/gsoc-notes/2024/fedora_logo.png b/gsoc-notes/2024/fedora_logo.png
new file mode 100644
index 0000000..e203040
Binary files /dev/null and b/gsoc-notes/2024/fedora_logo.png differ
diff --git a/gsoc-notes/2024/gsoc-application.txt b/gsoc-notes/2024/gsoc-application.txt
new file mode 100644
index 0000000..3b8342b
--- /dev/null
+++ b/gsoc-notes/2024/gsoc-application.txt
@@ -0,0 +1,233 @@
+## Project Application
+
+### Why does your organization want to participate in Google Summer of Code? *
+
+
+One of our four foundations is Friends. We highly value community and want to participate in Google Summer of Code to grow our pool of friends, both as users and contributors. We believe that the Fedora Linux (Our operating system) represents a platform for student education and experimentation. GSoC gives us the opportunity to formalize this in a way that leads to both better education for interns and real world experience with projects and contributions to projects and their upstreams. We are a diverse community and understanding this will help Interns see how their learnings and goals relate to the larger world. The Fedora Project is both an upstream and a downstream member of the Open Source community. Participation in our project allows interns to see both sides of this equation. Additionally, using Fedora Linux has positive return-on-investment for Interns because we are the upstream for Red Hat Enterprise Linux, the largest enterprise Linux and the likely platform of their future employers.
+
+
+### What would your organization consider to be a successful GSoC program? *
+
+Getting new contributors and helping them to get started with Open Source, writing cleaner and more efficient code, bringing new perspective to projects and retaining them through the year with the Fedora Project and by extension the Open Source ecosystem.
+
+### How will you keep mentors engaged with their GSoC contributors? *
+
+Fedora Project has a representative person focused on Mentored Project participation (GSoC + Outreachy), and a Community Action and Impact Coordinator (FCAIC) who will be able to help in this regard. The org Admin and the FCAIC will maintain regular contact with mentors to ensure they are present and not overwhelmed. A mentor call with a light agenda will be scheduled periodically from the application period until the end of participation to provide an outlet for regular mentor to mentor contact. The topics presented will help our mentors grow as much as our interns and provide a forum for solving problems. Additionally, The Fedora Project is sponsored by Red Hat, a company with additional mentoring and educational resources we can draw on to help all of our participants succeed.
+
+### How will you keep your GSoC contributors on schedule to complete their projects? *
+
+
+During the application process, mentors and interns will work together to set realistic milestones and smaller goals for the project proposal. This timeline creates a structure that helps interns produce regular deliverable and get early feedback. This method surfaces challenges or difficulties before they become stoppers. Additionally, interns are asked to write weekly blog posts to share their progress on their projects. These will be read by their mentors and the Fedora Project community. The blog posts help interns think critically about their own progress. When appropriate, writing prompts will be provided to guide thinking. These posts will also illuminate the progress being made toward the milestones defined at the start of the project. We will have periodic calls with interns about their progress and provide them with a chance to share their own ideas and suggestions about their project and the overall program.
+
+### How will you get your GSoC contributors involved in your community during GSoC? *
+
+Interns are actively engaged with not only the mentor but the group their project is related to. This integrates them into the team surrounding their project and gives them visibility into other work happening in this team's area. Interns are encouraged to attend the annual Fedora Project contributor conference, Nest with Fedora, to give them an opportunity to meet and interact with their mentors and other community members. We will also work to connect them with local Fedora Project communities in their region. Interns will also be featured in the Fedora Magazine articles about their project work. This effort not only promotes the work the Intern is doing, but also motivates them to continue participating in the community after their project has ended because they see the public recognition of their work.
+
+### Anything else we should know? (Optional)
+
+xxxx
+Has your org been accepted as a mentor org in Google Summer of Code before?
+
+    Yes
+
+    Years of Participation
+
+    2005
+
+    2006
+
+    2007
+
+    2008
+
+    2009
+
+    2010 - did not participate
+
+    2011
+
+    2012
+
+    2013
+
+    2014
+
+    2015
+
+    2016
+
+    2017
+
+    2018
+
+    2019
+
+    For each year provide the counts of successful and total students (e.g. 2016: 3/4) //It seems to be really hard to find out. Below are the only numbers i found out, and I do not think that these are all "successful..." . i don't think it matters that much as fedora is a well established project
+
+    2005: 8 (6?) https://developers.google.com/open-source/gsoc/2005/
+
+    2006: 5 https://developers.google.com/open-source/gsoc/2006/
+
+    2007: 5 https://developers.google.com/open-source/gsoc/2007/
+
+    2008: 10 (https://developers.google.com/open-source/gsoc/2008/)
+
+    2009: 9 (8?) https://www.google-melange.com/archive/gsoc/2009/orgs/redhat
+
+    2010: 0 - did not participate
+
+    2011: 5 (https://www.google-melange.com/archive/gsoc/2011/orgs/fedora)
+
+    2012: 9 (https://www.google-melange.com/archive/gsoc/2012/orgs/fedora)
+
+    2013: 9 (https://www.google-melange.com/archive/gsoc/2013/orgs/fedora)
+
+    2014: 8 (https://www.google-melange.com/archive/gsoc/2014/orgs/fedora)
+
+    2015: 5 (https://www.google-melange.com/archive/gsoc/2015/orgs/fedora)
+
+    2016: 6 (https://summerofcode.withgoogle.com/archive/2016/organizations/5911585470021632/) (per Kushal there were 10 and 6 passed)
+
+    2017: 6 (5 successful)
+
+    Submitted text: 2005: 8; 2006: 5; 2007: 5; 2008:10; 2009: 9; 2011: 5; 2012: 9; 2013: 9; 2014: 8; 2015: 5: 2016: 10/6; 2017 6/5; 2018 5/5  2019 5/5- data is approximated where not available.
+
+If your org has applied for GSoC before but not been accepted, select the years
+
+    none - assuming that no application was made in 2010
+
+What year was your project started?
+
+    2003
+
+Where does your source code live?
+
+    Various repositories and git hosts on the internet, however it is focused at pagure.io
+
+Anything else we should know (500 chars)
+
+    n/a
+
+
+## Project Profile
+
+Display Name
+
+    Fedora Project
+
+Website URL
+
+    https://getfedora.org/
+
+Tagline - A very short description of your project
+
+    Examples: https://developers.google.com/open-source/gsoc/help/org-profile#descriptions
+
+    Fedora Linux is built on the foundations of Freedom, Friends, Features, & First
+
+Logo
+
+    https://pagure.io/mentored-projects/blob/master/f/gsoc-notes/2018/fedora_gsoc_logo.png
+
+Primary Open Source License
+
+    MIT
+
+Organization Category - Select which category fits your organization best. Some organizations may fit into multiple categories, you must choose one. Used to help students filter the organization list.
+
+    Operating System
+
+ Technology Tags - Enter keywords for the primary specific technologies your organization uses. Examples: Python, Javascript, MySQL, Hadoop, OpenGL, Arduino (max 5)
+    // regarding tags, i'm not sure if ansible and postgresql really describe what fedora is about or what projects to expect however these are the technologies we use..  What would you like to replace them with? LDAP? JS?
+
+    python
+
+    html/css/js
+
+    rest
+
+    angular
+
+    golang
+
+Topic Tags - Enter keywords for general topics that describe your organization. Examples: Vision, Robotics, Cloud, Graphics, Web, Real time (max 5)
+
+    containers
+
+    linux
+
+    distribution
+
+    mobile
+
+    web development
+
+Ideas List - Enter the URL of your Ideas List page. This will be linked from your organization page.
+
+    https://docs.fedoraproject.org/en-US/mentored-projects/gsoc/2019/ideas/
+
+Short Description -- displayed on the organization list page (180 Chars)
+
+    Examples: https://developers.google.com/open-source/gsoc/help/org-profile#descriptions
+
+    Advance Free/Open Source Software/Content. Fedora is more than just one technology or concept it is a larger collaborative community.
+
+Long Description - on your organization's page (2000 chars) - limited markdown: https://developers.google.com/open-source/gsoc/help/markdown
+
+    Examples: https://developers.google.com/open-source/gsoc/help/org-profile#descriptions
+
+The Fedora Project's core values, or Foundations, are Freedom, Friends, Features, & First. Read more about them here: https://fedoraproject.org/wiki/Foundations
+
+A key component of this is our **Community**. This community, which you will join as an participant in Google Summer of Code, is creating a platform that supports the work of a diverse audience. Your contributions can affect people you've never met in situations you've never dreamed of. The Fedora community includes software engineers, artists, system administrators, web designers, writers, speakers, and translators -- all of whom will be happy to help you get started.
+
+Full project description available here: https://fedoraproject.org/wiki/Overview
+
+We believe that all contributors should expect and be part of a safe and friendly environment for constructive contribution. We can more effectively and successfully compare and challenge different ideas to find the best solutions for advancement, while building the size, diversity, and strength of our community.
+
+Application Instructions - Guidance for students on how to apply to your organization. Should include any prerequisites or requirements. You may wish to include a template or tips for their proposals. May include limited Markdown. (1500 chars)
+
+Our application process is described completely here: https://docs.fedoraproject.org/en-US/mentored-projects/gsoc/2019/application/
+
+In general, we are looking for students to describe both their understanding of the project they are choosing (or their complete project if they are proposing one) and to help us understand why they are the best candidate for the project. This also includes helping us understand their availability and level of commitment. While prior experience with Fedora is ideal, it is not a selection requirement.
+
+Proposal Tags - Enter tags that students can select (one) from and apply to their own proposals to help organize them. Examples: New Feature, Optimization. You can also use these to designate "sub-organizations" if you are an umbrella organization. (max 10)
+
+    CentOS
+
+    Continuous Integration/Deployment (CI/CD)
+
+    Development:Python
+
+    Development:Web / App development
+
+    Containers
+
+    Mobile
+
+    Propose Your Own Idea
+
+You must complete at least one of the following three contact options.
+
+Chat
+
+     Freenode IRC Channel #fedora-summer-coding - https://webchat.freenode.net/?channels=#fedora-summer-coding
+
+Mailing List
+
+     summer-coding@lists.fedoraproject.org - https://lists.fedoraproject.org/admin/lists/summer-coding@lists.fedoraproject.org
+
+General Email
+
+     summer-coding@lists.fedoraproject.org
+
+Links (all optional)
+
+Twitter
+
+     https://twitter.com/fedora
+
+Blog URL
+
+     https://communityblog.fedoraproject.org
+
+
diff --git a/modules/ROOT/nav.adoc b/modules/ROOT/nav.adoc
index 76e2c06..21e5bed 100644
--- a/modules/ROOT/nav.adoc
+++ b/modules/ROOT/nav.adoc
@@ -1,6 +1,10 @@
 * Mentored Project
 ** xref:mentored_project/Info.adoc[About]
 * Google Summer of Code
+** 2024
+*** xref:gsoc/2024/index.adoc[Indformation]
+*** xref:gsoc/2024/ideas.adoc[Ideas]
+*** xref:gsoc/2024/application.adoc[Application Process]
 ** 2022
 *** xref:gsoc/2022/index.adoc[Information]
 *** xref:gsoc/2022/application.adoc[Application Process]
diff --git a/modules/ROOT/pages/gsoc/2024/application.adoc b/modules/ROOT/pages/gsoc/2024/application.adoc
new file mode 100644
index 0000000..15a7a12
--- /dev/null
+++ b/modules/ROOT/pages/gsoc/2024/application.adoc
@@ -0,0 +1,140 @@
+= Google Summer of Code Application Process
+
+NOTE: Fedora is applying to become a mentoring project.
+
+Interested in applying for Google Summer of Code with Fedora?  Here is
+how you do that!
+
+The following are specific guidelines for students to use to submit an
+application for the GSoC program through the Fedora Project. Please go
+through these carefully and follow them. Applications must be complete
+by the deadline. Late applications cannot be accepted.
+
+== Important
+
+* Timelines are set by Google for the entire program. link:https://summerofcode.withgoogle.com/how-it-works/[Follow the timeline].
+* Applications are due in Google's system by Feb 6 18:00 UTC.
+* Applications Must be filed in the Google system.  No other
+  material can be read or accepted.
+* The final application is required to be submitted as a PDF.
+
+== Student Application Process
+
+=== Learn
+
+Before you do anything, learn about the program and Fedora. These links
+may be helpful:
+
+* https://summerofcode.withgoogle.com/[GSoC official site]
+* link:index.html[Information about Fedora's Participation in GSoC]
+
+=== Communicate
+
+Begin link:https://fedoraproject.org/wiki/Communicating_and_getting_help[communicating] with the
+community. Our community members can help you understand the existing
+project proposals. If you're going to try and propose your own project,
+this is a great way to understand the needs of the project and find a
+mentor.
+
+* https://lists.fedoraproject.org/admin/lists/summer-coding.lists.fedoraproject.org[the
+  summer-coding list]
+* https://lists.fedoraproject.org/admin/lists/devel.lists.fedoraproject.org[the
+  development list].
+
+Don't forget to contact mentors on projects that interest you to learn
+more. If you're going to propose a project you must have a mentor at the
+time of proposal.
+
+=== Apply
+
+NOTE: Fedora is applying to be mentoring Organization.  Student applications open on March 9, 2021.
+
+The application process consists of 5 steps:
+
+. Create a FAS account https://admin.fedoraproject.org/accounts[FAS Account Signup / Login Page]
+. Join the fedora-summer-coding mailing list https://lists.fedoraproject.org/admin/lists/summer-coding.lists.fedoraproject.org[Fedora Summer Coding Mailing List] - This list is fairly low volume.
+. Join the devel mailing list https://lists.fedoraproject.org/admin/lists/devel.lists.fedoraproject.org[Devel Mailing List] - this list can be higher volume you may wish to use mail filters appropriately.
+. Sign the FPCA by following the directions https://fedoraproject.org/wiki/Account_System/CompleteFPCA[here]
+. Submit the application/proposal including all requirements in the next section at the https://summerofcode.withgoogle.com/get-started/[Google Summer of Code Site].  We strongly encourage you to not submit your final PDF until you get feedback about the proposal from your mentor(s).
+
+Help is available!  Share your application in progress and get feedback.  The mentors can help verify your understanding of the project and provide guidance on whether your plan is good.
+
+If you are submitting an original proposal you must find a mentor.
+Proposals without mentors will be rejected.  Sharing your proposal is
+key to doing this.  If you don't want to share your proposal publicly
+consider using something like a Google Doc and sharing a link with the
+mentor/reviewers.  You can also share the link via a private ticket in
+our link:https://pagure.io/mentored-projects/issues[Pagure Repository].
+While we would normally not suggest a close-sourced tool such as Google
+Docs, in this case it is potentially easier for you because you a)
+must have a Google account to be able to apply to the program; and b)
+must generate a PDF for your application.
+
+==== Google Summer of Code Application and Supplemental Material Requirements
+
+In addition to the information Google requests, the Fedora Project
+requires you to submit the following information:
+
+* What project are you applying to? Seriously consider choosing a
+  project for proposal from xref:gsoc/2024/ideas.adoc[ideas list].  While it is
+  possible to propose your own project, it is often more successful for
+  you to select one that is already proposed by a mentor.
+
+* Contact Information
+** List your Name, Email Address, Blog URL, and any additional contact
+   information you think we need. We tend to email so be sure you're
+   reading your email.
+
+* About You - Consider these questions
+** Do you have any past involvement with the Fedora Project or another
+   open-source project as a contributor? What kind of contributions have
+   you made (code and non-code)? Please share any public contributions you
+   have made (urls, etc.)
+** What are you studying? Why?
+** What motivates you to do your best? How do you stay focused? Briefly
+   describe how you organize your work.
+
+* Why Us? - Consider these questions
+** Why do you want to work with the Fedora Project?
+** Do you plan to continue contributing to the Fedora Project after
+   GSoC? If yes, what sub-project(s) are you interested with?
+
+* Why This Project? - Consider these questions
+** Which specific project interests you? If you are proposing your own
+   project, do it here. If you are proposing the project, explain why it
+   benefits the community.
+** Have you contacted the mentor(s) listed for the project?
+** What relevant experience do you have for this project?
+** What do you want to gain from this project?
+** Describe this project in your own words. What does it mean to you?
+   What do you think the final deliverable is?
+
+* Why should we choose you over other applicants?
+
+* Propose a rough schedule for this project. Ideally you will have
+  regular deliverables throughout the entire period.
+
+* What are you specific plans from May to September (eg: Exams in
+  university, internships, vacations..etc). We need to know if there are
+  periods of time where you are likely to be unavailable. We are better at
+  accommodating these periods if we know of them in advance.
+
+[NOTE]
+--
+You must submit a PDF version of all of the information you
+prepare with your application using the Google site. The PDF should
+consist of the information from the supplemental application
+requirements section below. It should also contain any custom project
+you are proposing, if any.
+
+We are not allowed to consider students who do not submit this PDF.
+Students will not be judged on the visual layout of their PDF, however
+all information must be readable.
+--
+
+=== Keep communicating
+
+We cannot overstress the importance of communication. Keep talking, and
+listening, to the discussion group, to the sub-projects relevant to your
+proposal and to potential mentors. Be patient, as mentors and other
+contributors are often very busy people.
diff --git a/modules/ROOT/pages/gsoc/2024/ideas.adoc b/modules/ROOT/pages/gsoc/2024/ideas.adoc
new file mode 100644
index 0000000..776ef3e
--- /dev/null
+++ b/modules/ROOT/pages/gsoc/2024/ideas.adoc
@@ -0,0 +1,123 @@
+
+
+NOTE: Fedora is applying to be a GSoC mentoring organization.
+////
+NOTE: Fedora is proud to have been accepted as a GSoC mentoring organization.  Student applications open on March 25, 2019.  Please make sure you carefully read through the xref:gsoc/2024/index.adoc[general information] and xref:gsoc/2024/application.adoc[application process] pages before applying.
+////
+If you are a student looking forward to participating in
+xref:gsoc/2024/index.adoc[Google Summer of Code with Fedora], please feel free to
+browse this idea list.  There may be additional ideas added during the
+application period.
+
+**Now please go read the xref:gsoc/2024/index.adoc#what-can-i-do-today[What
+Can I do Today] section of the main page. This has the answers to your
+questions and tells you how to apply**
+
+Do not hesitate to contact the mentors or contributors listed on this
+page for any questions or clarification. You can find helpful people on
+the IRC channel, or use the mailing list. can be used for getting help
+with programming problems.
+
+== Supporting Mentors
+
+The following contributors are available to provide general help and
+support for the GSoC program If a specific project mentor is busy, you
+can contact one of the people below for short-term help on your project
+or task.
+add yourselves and your wiki page).
+
+
+* link:https://fedoraproject.org/wiki/User:Sumantrom[Sumantro Mukherjee] (General development, general Linux,Fedora community, GSoC alumnus, questions about program, misc. advice)
+* link:https://fedoraproject.org/wiki/User:Jflory7[Justin Flory] (Fedora CI,GCI,GSoC,general linux,Fedora community, misc.)
+
+== Idea list
+
+NOTE: Ideas are subject to change as additional mentors are onboarded.
+
+
+* <<Use natural language to create network configuration>>
+* <<Make AI understand NetworkManager logs>>
+
+=== Genric Intro 
+
+NetworkManager is the standard Linux network configuration tool suite. It supports a large range of networking setups, from desktop to servers and mobile and integrates well with popular desktop environments and server configuration management tools.
+
+Nmstate is a library with an accompanying command line tool that manages host networking settings in a declarative manner. The networking state is described by a pre-defined schema. Reporting of current state and changes to it (desired state) both conform to the schema.
+
+Linux System Roles is a project related to Ansible, a tool for automating configuration management, application deployment and software provisioning. The goal of linux system roles is to provide a consistent user interface, abstracting from any particular implementation of the linux subsystems, but trying to get the most out of the particular libraries on each one of them. The Network Linux System Role currently provides a unique configuration interface for network-scripts and NetworkManager.
+
+The topic for this internship is enhancing this ecosystem with AI capabilities to improve the user experience for these projects. Possible areas are:
+
+
+
+==== Use natural language to create network configuration
+
+- Difficulty : Easy
+- Type : 1person full time 350hrs (12 weeks)
+- Technology : ML, AI, git, python, shell, linux, networking, md(for docs)
+- Mentor :   Fernando F. Mancera (Current NetworkManager Developer and Maintainer), Wen Liang , Iñigo Huguet 
+- Email : ffmancera@riseup.net,  wenliang@redhat.com,  ihuguet@redhat.com(as backup)
+
+
+===== Description
+
+While it is rather easy for users to describe in natural language what they would like to configure, it can be hard to find the right options or using the right syntax in configuration files. AI provides a way to use natural language. As part of the internship, the projects should be enhanced to provide user support TUI based on prompts such as “Configure network devices eth0 and eth1 in a linux bridge”.
+
+===== Read Me 
+
+https://networkmanager.dev/docs 
+https://nmstate.io/ 
+https://github.com/linux-system-roles/network 
+https://fedoramagazine.org/writing-useful-terminal-tui-on-linux-with-dialog-and-jq/
+
+
+===== Deliverables
+    
+As a GSoC intern, you will be responsible for the following :
+
+- Get in touch with the Upstream (Fedora and NM)
+- Basic ML/AL and LLM knowledge is preffered. Learn more 
+- Building a custom LLM which will be trained with dataset of NM and NMstate
+- Build TUI for prompt and output 
+- Write documentation
+- Python tests and CI automation
+
+'''
+
+==== Make AI understand NetworkManager logs
+
+- Difficulty : Easy
+- Type : 1 person full time 350hrs (12 weeks)
+- Technology : ML, AI, git, python, shell, linux, networking, md(for docs)
+- Mentor :   Fernando F. Mancera (Current NetworkManager Developer and Maintainer), Wen Liang , Iñigo Huguet 
+- Email : ffmancera@riseup.net,  wenliang@redhat.com,  ihuguet@redhat.com(as backup)
+
+
+===== Description
+
+AI summarizer or abstract generation is widely deployed and utilized in various applications,   
+which saves people’s time from reading lengthy or even garbled text.
+
+Analyzing the NetworkManager log is hard for new developers or users, sometimes it is time-consuming to summarize the networking behavior from the NetworkManager log. With the assistance of an AI summarizer, we should expect the model to parse and understand the NM log, and give a summary of the networking behavior with a confidence score and the verbose level of the summary can also be easily controlled. With the assistance of this TUI tool, the developers and users can analyze the NetworkManager log more easily.
+
+===== Read Me : 
+  
+- https://networkmanager.dev/docs 
+- https://nmstate.io/ 
+- https://github.com/linux-system-roles/network 
+- https://fedoramagazine.org/writing-useful-terminal-tui-on-linux-with-dialog-and-jq/
+
+
+
+==== Deliverables
+
+- Get in touch with the Upstream (Fedora and NM)
+- Basic ML/AL and LLM knowledge is preffered. Learn more
+- Building a custom LLM which will be trained with dataset of NM and NMstate
+- Build TUI for score system and output
+- Write documentation
+- Python tests and CI automation
+
+
+
+'''
diff --git a/modules/ROOT/pages/gsoc/2024/index.adoc b/modules/ROOT/pages/gsoc/2024/index.adoc
new file mode 100644
index 0000000..39e0290
--- /dev/null
+++ b/modules/ROOT/pages/gsoc/2024/index.adoc
@@ -0,0 +1,236 @@
+[[google-summer-of-code-2024]]
+= Google Summer of Code 2024
+
+
+NOTE: The Fedora Project was not selected as a mentoring organization in GSoC 2024.
+
+image::gsoc_logo.png[float="right"]
+
+This page contains information about Fedora's participation in Google
+Summer of Code (GSoC).  Please feel free to contact us via the mailing list below
+for clarifications and more information. You can also use the IRC channel.
+
+[[what-can-i-do-today]]
+== What can I do today?
+
+
+Fedora is still in the process of applying to be a mentoring organization.
+Today there is nothing we can do except wait until Google makes a
+decision.
+
+////
+Fedora is proud to have been accepted as a GSoC mentoring organization.
+Student applications open on XYZ.
+////
+
+Today you should read through the xref:gsoc/2024/ideas.adoc[ideas] and think about
+our xref:gsoc/2024/application.adoc[application process.]
+
+[[student-information]]
+== Student Information
+
+Do you want to contribute to one of the world's leading innovative Linux
+distributions? GSoC could be your chance. Please refer to the information
+below.
+
+* If you're interested in working on a mentor-submitted idea, read
+  the xref:gsoc/2024/ideas.adoc[ideas page] and about the project and the related
+  technology. There is no need to contact the mentor unless you have a
+  specific question about the project. Don't send an "I'm interested" email.
+
+* If you're interested in proposing your own project start looking
+  around the Fedora Project for a mentor and send your idea to the mailing
+  list or post it on the wiki. A list of potential mentors is also on the
+  xref:gsoc/2024/ideas.adoc[ideas page].
+
+* You may also wish to start working on the Fedora specific parts of
+  the application, see below for more information. Carefully review the
+  student responsibilities section.
+
+[[why-spend-your-summer-working-on-foss]]
+=== Why spend your summer working on FOSS?
+
+When you work in the open on free software, you create a body of work
+that follows you for the rest of your life. Rather than a coding
+assignment done by thousands of other students and relegated to the
+bottom of the drawer at semester's end, working in FOSS is a chance to
+contribute to a living project.
+
+Working in FOSS gives you a chance to:
+
+* Work with real-world, large codebases.
+* Collaborate with real engineers and other professionals.
+* Contribute to something meaningful while learning and earning.
+* Learn tools and processes that are just like what you are going to use
+  if you work in technology after graduation.
+* Make friends and contacts around the globe.
+* Attract attention that can lead to an internship or job after
+  graduation.
+* Create lifetime connections and associations.
+
+[[why-work-with-fedora]]
+=== Why work with Fedora?
+
+Our project is large and diverse. We are very experienced at working
+with new contributors and helping them be successful.
+
+Many of our contributors are long-time contributors. They remain because
+they want to keep growing the project and to lend their expertise,
+advice and mentoring to you! People who stay around the community and do
+good work are noticed. They get hired for jobs from it, including being
+hired by Red Hat. Past Google Summer of Code students were hired by Red
+Hat, as well as interns in various positions. This is just an example,
+as experience and reputation in the Fedora Project communities is
+influential in your career in many ways.
+
+As a long-standing community with many facets, it is possible for you to
+find many rewarding sub-projects to work on.
+
+You should know that contributing to FOSS doesn't require you to have
+super programming skills, or super-anything else. You just need be
+interested, curious, and willing to become comfortable being
+productively lost. This is the state of learning. You learn by finding
+your way around and figuring things out with the support of your mentor
+and the community.
+
+If you are new to the Fedora Project, the following material will help
+you to get started.
+
+* link:https://docs.fedoraproject.org/fedora-project/project/fedora-overview.html[Fedora Project Overview]
+* link:https://docs.fedoraproject.org[Fedora Technical and Community Documentation]
+* link:https://fedoraproject.org/wiki/How_to_use_IRC[How to use IRC]
+* link:https://fedoraproject.org/wiki/Development[Information about Development in Fedora]
+
+[[student-responsibilities]]
+=== Student Responsibilities
+
+You are the key ingredient for your project's success. This project is
+important to you, your mentor, and the entire Fedora Community.
+
+Your responsibilities include:
+
+* Communicating early and often with your mentor.
+* Blogging every week about what you're learning, how you're doing,
+  challenges and successes. This is key way to keep the entire Fedora
+  Community informed.
+* Working with your mentor on realistic achievable milestones that
+  provide for regular deliverables and feedback.
+* Attending the brief student calls, as announced
+* Being accountable for your success and your actions
+
+[[student-application]]
+=== Student Application
+
+Please read and follow the
+xref:gsoc/2021/application.adoc[student application process].
+
+[[mentor-information]]
+== Mentor Information
+
+Want to help the next generation of contributors grow? Want to bring new
+contributors to Fedora? Want to advance your projects along their
+roadmap? GSoC can be a chance to do all of this.
+
+NOTE: If you are contacted directly by a student, we encourage you
+to reply and include the mailing list and/or IRC channel to keep the
+process transparent and to ensure the inquiry is able to be answered by
+more people than just you.
+
+=== How to Propose a Project
+
+If you want to mentor a specific project, think carefully about several things:
+
+1. 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.
+
+2. 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."
+
+3. 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.
+
+4. 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
+https://pagure.io/mentored-projects/issues[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 https://pagure.io/mentored-projects/issues[Mentored
+  Projects Issue Tracker] offering your help.  Please tag the issue with
+  the *GSoC* tag.
+
+[[how-to-work-with-students]]
+=== How to work with students
+
+* Read about good mentoring in the
+  link:http://write.flossmanuals.net/gsoc-mentoring/what-makes-a-good-mentor[Manual
+  on Mentoring]
+
+[[mentor-responsibilities]]
+Mentor responsibilities
+^^^^^^^^^^^^^^^^^^^^^^^
+
+You are an essential part of the student's success, the project's
+success, and the success for the Fedora Project.
+
+Your responsibilities include:
+
+* Being an interface for an identified sub-project or SIG in Fedora.
+* Helping students communicate with the overall project and any
+  upstream.
+* Helping the student plan realistic achievable milestones that provide
+  for regular deliverables and feedback.
+* Regular communication with your student. This means you must be
+  regularly available for the entire project. If you take a holiday you
+  need to know early and help your student be ready for your brief
+  absence.
+* Attending a brief mentors call, as scheduled.
+* Be the final, accountable person for deciding if the student is
+  successful or not. This is responsibility akin to being a professor or
+  boss.
+
+[[communication]]
+== Communication
+
+* *Mailing List (GSoC-related):* link:https://lists.fedoraproject.org/admin/lists/summer-coding@lists.fedoraproject.org/[summer-coding@lists.fedoraproject.org]
+* *Mailing List (Technical):* link:https://lists.fedoraproject.org/admin/lists/devel@lists.fedoraproject.org/[devel@lists.fedoraproject.org]
+* *IRC:* link:https://webchat.freenode.net/?channels=#fedora-summer-coding[#fedora-summer-coding] or link:https://webchat.freenode.net/?channels=#fedora-devel[#fedora-devel] on Freenode
+
+[[timeline]]
+== Timeline
+
+Always refer to the
+link:https://summerofcode.withgoogle.com/how-it-works/#timeline[Official
+Google Summer of Code Timeline] for details.
+
+[[administration]]
+Administration
+~~~~~~~~~~~~~~
+
+In order to get questions answered or obtain more information related to
+this year's GSoC with Fedora, please contact the administrators directly
+(please consider CCing the summer-coding list where ever possible).
+
+1. link:https://fedoraproject.org/wiki/User:Sumantrom[Sumantro Mukherjee] (Primary)
+2. link:https://fedoraproject.org/wiki/User:jflory7[Justin Flory] (Secondary)
diff --git a/site.yml b/site.yml
index 009a704..02902ea 100644
--- a/site.yml
+++ b/site.yml
@@ -1,6 +1,6 @@
 site:
   title: Mentored Projects
-  start_page: mentored-projects::outreachy/2021/index.adoc
+  start_page: mentored-projects::gsoc/2024/index.adoc
 content:
   sources:
    - url: .

