GNOME.org
 

[pitivi] docs: Update GSoC pages

commit 1a85816c3f90dd9422dc4344f6a2945d86f625f7
Author: Alexandru Băluț <alexandru balut gmail com>
Date:   Sat Feb 6 11:50:58 2021 +0100

    docs: Update GSoC pages

 docs/GSoC_Application.md      |  29 ++++++----
 docs/GSoC_Ideas.md            |  70 +++++++++++++++++------
 docs/Google_Summer_of_Code.md | 130 +++++++++++++-----------------------------
 3 files changed, 109 insertions(+), 120 deletions(-)
---
diff --git a/docs/GSoC_Application.md b/docs/GSoC_Application.md
index 79ca0099c..de0415d35 100644
--- a/docs/GSoC_Application.md
+++ b/docs/GSoC_Application.md
@@ -4,7 +4,7 @@ short-description: How to fill out the application to GSoC
 
 # Fill out the Application
 
-Once the students applications period has opened (see
+Once the Student Application Period has opened (see
 [schedule](https://summerofcode.withgoogle.com/how-it-works/#timeline)),
 you have to submit your application on Google's Summer of Code website.
 Your application must be written in English.
@@ -44,7 +44,10 @@ date for any degree you have or are pursuing.*
 #### How do you plan to achieve completion of your project?
 
 *Please provide a sequence of tasks and subtasks and how long (days) you
-estimate it will take you to complete each of them.*
+estimate it will take you to complete each of them. Think about how to split the
+work in small easily approachable parts.*
+
+*Pay attention, this is the most time consuming part of the proposal.*
 
 #### What are your past experiences with the open source world as a user and as a contributor?
 
@@ -52,21 +55,23 @@ estimate it will take you to complete each of them.*
 
 #### What other relevant projects have you worked on previously and what knowledge you gained from working 
on them?
 
-#### What other time commitments, such as school work, exams, research, another job, planned vacation, etc., 
will you have between May 18th and August 10th?
+#### How do you plan to schedule the work on the project?
+
+*The Coding Period is between June 7th - August 16th. Please mention what other
+time commitments, such as school work, exams, research, another job, vacation,
+etc., will you have in this period. Mention the dates for these commitments and
+how many hours a week do these commitments take.*
 
-*Please mention the dates for these commitments and how many hours a
-week do these commitments take.*
+*The Coding Period is 10 weeks long. Mention how you will schedule 175h of work
+in this period. For example, working 7 hours per day you can finish in 25 days
+(5 weeks).*
 
 ## Tips
 
 Please be factual and clear in answering these questions. Feel free to
 add anything else that is relevant for your application.
 
-It is never too early to start working on your GSoC application! By
-large, the most time consuming part of the application is writing the
-sequence of tasks for completing the project. Split the work in small
-easily approachable parts.
+It is never too early to start working on your GSoC proposal!
 
-To write a strong application, make sure what you are proposing is a
-manageable and agreed-upon project. Demonstrate clearly your knowledge,
-skills, and enthusiasm.
+To write a useful application, make sure what you are proposing is a
+manageable and agreed-upon project.
diff --git a/docs/GSoC_Ideas.md b/docs/GSoC_Ideas.md
index 5e9a3465b..a7e12403e 100644
--- a/docs/GSoC_Ideas.md
+++ b/docs/GSoC_Ideas.md
@@ -4,12 +4,36 @@ short-description: GSoC project ideas we like
 
 # GSoC Project Ideas
 
-These ideas shall be used as a base for writing a detailed project proposal if
-you want to apply for a [GSoC internship](Google_Summer_of_Code.md). You are
-welcome to come up with your own ideas.
-
-To create a detailed proposal, use our [GSoC application
-template](GSoC_Application.md).
+To apply for a [GSoC internship] you need to make a project proposal. The scope
+of your GSoC project will probably cover only Pitivi, but it could very well
+span multiple codebases:
+
+-   [Pitivi], which is the user interface. Written in Python. *For those
+    who love design and graphical user interaction.*
+-   [GES], the high-level video editing GStreamer library that powers
+    Pitivi and other applications. Written in C. *For those who wish to
+    improve an easy to use, powerful and flexible library for
+    audio/video editing.*
+-   GStreamer, for low-level work, such as improving filters/effects,
+    codecs, hardware decoding/encoding acceleration, analysis, etc.
+    Written in C. *For those seeking a challenging audio and video
+    experience where optimization is key.*
+
+We'd love to see GSoC proposals originating from an itch you need to scratch.
+You are welcome to ask around and **bring your own ideas**. If you're not sure
+where you can be most useful, have a look at our list of ideas below. These
+shall be used as a base for writing a detailed project proposal.
+
+See [Past GSoCs] for details on what the previous GSoC students did.
+
+To create a detailed proposal, use our [GSoC application template].
+Deadlines for applying are approaching fast, hurry up!
+
+  [Pitivi]: http://www.pitivi.org/manual/mainwindow.html
+  [GES]: GES.md
+  [Past GSoCs]: Past_GSoCs.md
+  [GSoC internship]: Google_Summer_of_Code.md
+  [GSoC application template]: GSoC_Application.md
 
 
 ## Cut perspective
@@ -21,8 +45,8 @@ will offer a [second timeline
 representation](https://gitlab.gnome.org/GNOME/pitivi/issues/2381) above the
 timeline, that is always zoom-fitted.
 
-Requirements: Python. Minimal experience contributing to Pitivi including unit
-tests.
+**Requirements**: Python. Minimal experience contributing to Pitivi including
+unit tests.
 
 
 ## Timeline enhancements
@@ -31,19 +55,19 @@ Fixing timeline issues and making small enhancements would improve a lot the
 timeline usability, making it a delight to use Pitivi. See
 [GitLab](https://gitlab.gnome.org/GNOME/pitivi/-/issues?label_name%5B%5D=6.+Component%3A+Timeline).
 
-Requirements: Python. Minimal experience contributing to Pitivi including unit
-tests.
+**Requirements**: Python. Minimal experience contributing to Pitivi including
+unit tests.
 
 
 ## Focus on the music
 
 Often people want to pick a nice tune and then sync their weekend clips on it.
-To make this easy, Pitivi can detect the beats using a 3rd party library, and
-allow aligning and cutting the clips to the beat. It might sound easy, but the
-entire experience should be super-polished so it works nice and everybody can do
-it.
+To make this easy, Pitivi can detect the beats using a 3rd party library such as
+[librosa](https://librosa.org/) and allow aligning and cutting the clips to the
+beat. It might sound easy, but the entire experience should be super-polished so
+it works nice and everybody can do it.
 
-Requirements: Python, C. Minimal experience contributing to Pitivi including
+**Requirements**: Python, C. Minimal experience contributing to Pitivi including
 unit tests.
 
 
@@ -61,8 +85,8 @@ clip. You'd have to extend the UI with a new
 [perspective](https://gitlab.gnome.org/GNOME/pitivi/blob/master/pitivi/perspective.py)
 for managing the closing credits HTML, and the corresponding video files.
 
-Requirements: Python. Minimal experience contributing to Pitivi including unit
-tests.
+**Requirements**: Python. Minimal experience contributing to Pitivi including
+unit tests.
 
 
 ## Fix GPU support in Pitivi
@@ -74,5 +98,15 @@ enabling GL plugins for compositing and rendering, and fixing any issue that
 shows up. The second part would be about making sure hardware accelerated
 decoders can be used in the pipelines.
 
-Requirements: C. Experience with GStreamer is mandatory. Minimal experience
+**Requirements**: C. Experience with GStreamer is mandatory. Minimal experience
 contributing to Pitivi including unit tests. Experience with OpenGL is a plus.
+
+
+## GTK 4
+
+Initially the development environment should be migrated onto a GTK 4 runtime
+and then the app should be ported following the [migration guide from GTK 3 to
+GTK 4](https://developer.gnome.org/gtk4/unstable/gtk-migrating-3-to-4.html).
+
+**Requirements**: Python. Minimal experience contributing to Pitivi including
+unit tests. Experience developing GTK apps is a plus.
diff --git a/docs/Google_Summer_of_Code.md b/docs/Google_Summer_of_Code.md
index d469a8ce7..9cb907471 100644
--- a/docs/Google_Summer_of_Code.md
+++ b/docs/Google_Summer_of_Code.md
@@ -1,60 +1,49 @@
 # GSoC
 
-The [Google “Summer of Code” program] is available for students only. If
-we accept your project proposal, in June-July-August you work on your
-project while being paid by Google. Mid-term and end-term we evaluate
-your work.
+The [Google “Summer of Code” program] is available for students and recent
+graduates. Check section "7.1. Eligibility" in the [Rules] to see if you are
+eligible.
+
+Interested students write and submit a detailed project proposal. If the
+proposal is accepted, you work on your project while being paid by Google.
+Mid-term and end-term the student and the mentor both submit evaluations to
+Google.
 
 See the section at the top of the [contributing page] for details why
-Pitivi is important.
-
-While a GSoC with us is one of the most fun and rewarding experiences
-you can get, you need to consider it as *professional work*:
-
--   **GSoC projects are on a “full-time” basis, not “part-time”**. What
-    this means is that you should not apply if you have some strange
-    schedule where, for example, you have school exams for many weeks
-    between early May and late August. If you have school
-    exams/obligations during the summer, *you need to mention them* and
-    account for them in your schedule.
--   **No excuses!** We expect you to be a reliable, hard-working person.
-    If things don't go well because for example your roommates are
-    noisy, you don't have air conditioning, or your internet connection
-    is unreliable, and you can't fix it, tell us so we can terminate
-    your GSoC.
-
-Our policy is to ignore “theoretical” applications — to be eligible,
-you must show you're capable. Best is to get involved early-on and
-make one or more contributions prior to applying. Read more about our stance in
-this blog post: “[Applying for a GSoC project is all about early
-involvement and commitment]”. If you are interested, the best thing you
-can do is to come to our [IRC channel] now, to make sure we have enough
-time to get to know you.
+Pitivi is important, if you're still not convinced.
+
+While a GSoC with us is one of the most fun and rewarding experiences you can
+get, you need to consider it as *professional work*. We expect you to be a
+reliable, hard-working person. If things don't go well because for example your
+roommates are noisy, you don't have air conditioning, or your internet
+connection is unreliable, and you can't fix it, tell us so we can terminate your
+internship. **No excuses!**
+
+Our policy is to ignore “theoretical” applications — to be eligible, you must
+show you're capable. Best is to get involved early-on and make one or more
+contributions prior to applying. We will base ourselves 90% on your involvement
+and demonstrated ability to contribute code to Pitivi. The more good-quality
+patches you’ve made, the more chances you have.
 
   [Google “Summer of Code” program]: https://summerofcode.withgoogle.com/
+  [Rules]: https://summerofcode.withgoogle.com/rules/
   [contributing page]: http://www.pitivi.org/?go=contributing
-  [Applying for a GSoC project is all about early involvement and
-  commitment]: 
http://jeff.ecchi.ca/blog/2014/02/15/applying-for-a-gsoc-project-is-all-about-early-involvement-and-commitment/
-  [IRC channel]: http://www.pitivi.org/?go=contact
 
 ## Who we are looking for
 
 We are looking for smart and talented developers interested in
 multimedia and video editing.
 
-You need to be highly **communicative**. Stuck on a problem? We need to
-know. Achieved a milestone or solved a really nasty problem? The *entire
-world* needs to know. We require to see you in our IRC channel, that's
-where you can meet the team, where you follow what's going on and that's
-where we'll communicate. Email is not sufficient. If you're new to IRC,
-check out [IRCCloud] and [riot.im].
+The time is very short. To make the most out of it, you need to be highly
+**communicative**. Particularly when you are stuck on a problem or don't see any
+way out. We require to see you in our [chat room], that's where you can meet the
+team, where you follow what's going on and that's where we communicate.
 
 You must have experience with Python or C, depending on your project.
 Knowledge of [Git], GStreamer and [related technologies] is a plus.
 Familiarity with [Test-Driven Development] is a plus.
 
-  [riot.im]: https://riot.im/app
-  [IRCCloud]: https://www.irccloud.com
+  [chat room]: https://app.element.io/#/room/#pitivi:matrix.org
   [Git]: Git.md
   [related technologies]: Architecture.md
   [Test-Driven Development]: http://en.wikipedia.org/wiki/Test-driven_development
@@ -71,10 +60,10 @@ opportunity to play with these [technologies]. We'll direct you to make
 great use of the tight-knit GStreamer and GTK communities so you have
 high-quality feedback throughout your project.
 
-Flatpak additionally allows us to have a [development environment] with
-all the dependencies in a sandbox, which is very easy to set up.
-This means you won't have to mess your system to be able to build
-the latest GStreamer. Since all of us will be using the same
+The dependencies for a video editor are very complex. But thanks to Flatpak we
+have a [development environment] with all the dependencies in a sandbox, which
+is very easy to set up. This means you won't have to mess your system to be able
+to build the latest GStreamer. Since all of us will be using the same
 dependencies, there will be no friction due to the complex dependencies.
 
   [development environment]: HACKING.md
@@ -92,66 +81,27 @@ application and its source code. This also ensures that you get to know
 members of the community and have sufficient time and information to
 properly plan your project.
 
-See also [our official stance] (as of 2014) on the matter and Lionel
-Dricot's blog post on “[Being selected as a Summer of Code student]”.
-
 Therefore, you should proceed like this:
 
-1.  Come to our [IRC channel] and stick around.
+1.  Come to our [chat room] and stick around.
 2.  Setup your [development environment] and run the [Test suite].
     Explore the development version of Pitivi, what works well and what
-    doesn't, etc. See how you like it.
+    doesn't, etc.
 3.  To get a better idea of how comfortable you are with the code and
     community, make some small contributions to the code. Pick some
-    [small bug to fix] and have a go at it. Keep us in the loop. The
-    earlier you start contributing, the more likely you know what you're
-    getting into. Don't start contributing in March/April: we highly
-    encourage you to start getting involved in January/February, or even
-    earlier, to have time to try another team if we are not a good fit
-    for you.
+    [small bug to fix] and have a go at it. Keep us in the loop.
+    Ideally you start getting involved in January/February, or even
+    earlier, to have time to try another team if we are not a good fit.
 4.  Find a cool feature you need in Pitivi and tell us. Start making a
     design doc on how you plan to implement it. Feel free to pick
-    a project from the list of [GSoC project ideas] we thought about.
+    a project from the list of blessed [GSoC project ideas].
 5.  Fill out the [application template] and apply officially to the
     Google's Summer of Code [website].
 
-  [our official stance]: 
http://jeff.ecchi.ca/blog/2014/02/15/applying-for-a-gsoc-project-is-all-about-early-involvement-and-commitment/
-  [Being selected as a Summer of Code student]: http://ploum.net/be-selected-student-for-soc/
-  [IRC channel]: http://www.pitivi.org/?go=contact
+  [chat room]: https://app.element.io/#/room/#pitivi:matrix.org
   [development environment]: HACKING.md
   [Test suite]: Testing.md
   [small bug to fix]: https://gitlab.gnome.org/GNOME/pitivi/issues?label_name%5B%5D=4.+Newcomers
+  [GSoC project ideas]: GSoC_Ideas.md
   [application template]: GSoC_Application.md
   [website]: https://summerofcode.withgoogle.com/
-
-## Project ideas
-
-Pitivi is a very modular video editor, whose [architecture] heavily
-depends on technologies like [GES] and GStreamer. The scope of your GSoC
-project will probably cover only Pitivi, but it could very well span
-multiple codebases:
-
--   [Pitivi], which is the user interface. Written in Python. *For those
-    who love design and graphical user interaction.*
--   [GES], the high-level video editing GStreamer library that powers
-    Pitivi and other applications. Written in C. *For those who wish to
-    improve an easy to use, powerful and flexible library for
-    audio/video editing.*
--   GStreamer, for low-level work, such as improving filters/effects,
-    codecs, hardware decoding/encoding acceleration, analysis, etc.
-    Written in C. *For those seeking a challenging audio and video
-    experience where optimization is key.*
-
-We'd love to see GSoC proposals originating from an itch you need to
-scratch. You are welcome to ask around and **bring your own ideas**. If
-you're not sure where you can be most useful, have a look at our list
-of [GSoC project ideas]. Deadlines for applying are approaching fast,
-hurry up!
-
-See [Past GSoCs] for details on what the previous GSoC students did.
-
-  [architecture]: Architecture.md
-  [GES]: GES.md
-  [Pitivi]: http://www.pitivi.org/manual/mainwindow.html
-  [GSoC project ideas]: GSoC_Ideas.md
-  [Past GSoCs]: Past_GSoCs.md
[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]