From 4a74ad9da21652c8cd851d8b5b156b095fd3814e Mon Sep 17 00:00:00 2001
From: Deepak Khatri <deepaklorkhatri7@gmail.com>
Date: Tue, 6 Feb 2024 23:46:37 +0530
Subject: [PATCH] Update student guide

---
 guides/student.rst | 22 +++++++++++++++++++---
 1 file changed, 19 insertions(+), 3 deletions(-)

diff --git a/guides/student.rst b/guides/student.rst
index 3a78e31..0e3cb8d 100644
--- a/guides/student.rst
+++ b/guides/student.rst
@@ -15,8 +15,8 @@ All projects have the following basic requirements:
 1. Students must create accounts on `OpenBeagle <https://openbeagle.org/>`_, `Discord <http://bbb.io/gsocchat>`_ and `Beagle Forum <http://bbb.io/gsocml>`_ prior to creating their application.
 2. All newly generated materials must be released under an `open source license <http://www.opensource.org/licenses>`_. Individual students shall retain copyright on their works.
 3. Students will demonstrate their ability to cross-compile and utilize version control software by creating a “Hello World” application and generating a pull request to `jadonk/gsoc-application <https://github.com/jadonk/gsoc-application/tree/master/ExampleEntryJasonKridner>`_. For assistance, please visit `Discord <http://bbb.io/gsocchat>`_ or utilize the `Beagle Forum <http://bbb.io/gsocml>`_. The “Hello World” application must print your name and the date out in an ARM Linux environment. Freely available emulators may be used to test your application or you can ask anyone on the chat or mailing list to help you test.
-4. All projects will produce reusable software components and will not be “what–I-built-over-my-summer-vacation” projects. Including a hardware component is welcome, but the project deliverable will be software that may be utilized by a wide audience of the `BeagleBoard.org <http://beagleboard.org/>`_ community.
-5. Students will demonstrate their ability to collaborate by creating a project proposal on this site using our :ref:`proposal template <proposal_template>` and utilizing `Discord <http://bbb.io/gsocchat>`_ to collect quotes regarding the usefulness of their proposal to the `BeagleBoard.org <http://beagleboard.org/>`_ community. **Use of Google Docs for proposal development is discouraged due to insufficient revision control and extensive use of computing resources having numerous documents open simultaneously**.
+4. All projects will produce reusable software components and will not be “what–I-built-over-my-summer-vacation” projects. Including a hardware component is welcome, but the project deliverable will be software that may be utilized by a wide audience of the `BeagleBoard.org <https://www.beagleboard.org/>`_ community.
+5. Students will demonstrate their ability to collaborate by creating a project proposal on this site using our :ref:`proposal template <proposal_template>` and utilizing `Discord <http://bbb.io/gsocchat>`_ to collect quotes regarding the usefulness of their proposal to the `BeagleBoard.org <https://www.beagleboard.org/>`_ community. **Use of Google Docs for proposal development is discouraged due to insufficient revision control and extensive use of computing resources having numerous documents open simultaneously**.
 6. Source code generated during the project must be released on OpenBeagle (and we’ll setup a mirror on `Github.com <http://github.com/>`_).
 7. Students will provide two recorded audio/video presentations uploaded to Youtube or Vimeo (screencasts are appropriate), one near the beginning of the project summarizing their project goals and another in the wrap-up phase to summarize their accomplishments. Examples can be found on `http://beagleboard.org/gsoc <http://beagleboard.org/gsoc>`_. There is no requirement to show your faces or use English.
 
@@ -32,4 +32,20 @@ All projects have the following basic requirements:
     4. Plans for this week
 
     For example, `Weekly Progress Report Thread: 
-    Cape Compatibility <https://forum.beagleboard.org/t/weekly-progress-report-thread-cape-compatibility/28709/9>`_
\ No newline at end of file
+    Cape Compatibility <https://forum.beagleboard.org/t/weekly-progress-report-thread-cape-compatibility/28709/9>`_
+
+Student proposals can encompass projects based on the :ref:`ideas page <gsoc-project-ideas>`  or can include personal project ideas, 
+but should be focused on generating a sustainable and reusable open source software component. Previous Google Summer of Code projects show 
+that the key to success is being passionate about your project, so propose something that is extremely interesting to you, even 
+if it is not on this list. We will be glad to help students develop ideas into projects via `Discord <http://bbb.io/gsocchat>`_ 
+and `Forum <https://forum.beagleboard.org/c/gsoc>`_. There are many potential project ideas and we will match students to projects 
+based on their interests and help scope the proposals to something that can be completed in the Summer of Code timeframe.
+
+.. tip::
+   There are more than a thousand existing projects listed at `Projects Archive <http://www.beagleboard.org/projects>`_. 
+   If you are interested in any of the projects listed on the `BeagleBoard.org <https://www.beagleboard.org/>`_ projects page, 
+   contact the project members to see if there are any aspects of their projects that can be enhanced to create a GSoC project. 
+   There are also several ideas on the `ECE497 class project idea list <https://elinux.org/ECE497_Project_Ideas>`_. 
+   Note, however, we are looking for projects that provide a service to the developer community and aren’t simply “look what cool 
+   thing I made or you can make”. The projects should provide a useful software component for other people to utilize.
+
-- 
GitLab