[pitivi/sdk: 1/7] docs: Cleanup Roadmap and Update GSoC ideas

From: Alexandru Băluț <alexbalut src gnome org>
To: commits-list gnome org
Cc:
Subject: [pitivi/sdk: 1/7] docs: Cleanup Roadmap and Update GSoC ideas
Date: Sat, 16 Nov 2019 21:30:01 +0000 (UTC)
commit c3dc44ccb0e4eadae9d9216b236fc1d438427e67
Author: Alexandru Băluț <alexandru balut gmail com>
Date:   Mon Nov 4 03:52:20 2019 +0100

    docs: Cleanup Roadmap and Update GSoC ideas

 docs/GSoC_Ideas.md | 35 ++++++++++-------------------------
 docs/Roadmap.md    | 40 +++-------------------------------------
 2 files changed, 13 insertions(+), 62 deletions(-)
---
diff --git a/docs/GSoC_Ideas.md b/docs/GSoC_Ideas.md
index 19d37567..c18a3195 100644
--- a/docs/GSoC_Ideas.md
+++ b/docs/GSoC_Ideas.md
@@ -8,13 +8,18 @@ These ideas can be used as a base for writing a detailed project proposal if you
 
 To create a detailed proposal, use [GNOME's GSoC application 
template](https://wiki.gnome.org/Outreach/SummerOfCode/Students#Fill_out_the_Application).
 
+## Render experience
+ * Brief explanation: The render dialog should be simplified to avoid overwhelming the users, while still 
allowing full control. The dialog with the advanced settings of the encoders should similarly be improved for 
the officially supported encoders. In preparation, the render dialog should be [refactored into a 
perspective](https://gitlab.gnome.org/GNOME/pitivi/issues/2382).
+ * Requirements: Python, eye for detail. Minimal experience contributing to Pitivi.
+ * Mentor: Alexandru "aleb" Băluț
+
 ## Focus on the music
  * Brief explanation: 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 everybody can do it.
  * Requirements: Python, C. Minimal experience contributing to Pitivi.
  * Mentor: Mathieu Duponchelle
 
 ## Face blurring
- * Brief explanation: We should make it easy to blur faces. We can use an existing 3rd party plugin to 
analyze the video and report the location of the faces. The resulting data can be used to blur a specific 
face. The challenge is making this process as friendly as possible.
+ * Brief explanation: We should make it easy to blur faces. We can use an existing 3rd party plugin to 
analyze the video and report the location of the faces. The resulting data can be used to blur a specific 
face. The challenge is [making this process as friendly as 
possible](https://gitlab.gnome.org/GNOME/pitivi/issues/1942).
  * Requirements: Python. Minimal experience contributing to Pitivi.
  * Mentor: Mathieu Duponchelle
 
@@ -28,32 +33,12 @@ To create a detailed proposal, use [GNOME's GSoC application template](https://w
  * Requirements: Python, eye for detail. Minimal experience contributing to Pitivi.
  * Mentor: Alexandru "aleb" Băluț
 
-## Effects usability
- * Brief explanation: The main task would be to improve the Effects discovery experience, and find a way to 
make a set of [whitelisted effects easily accessible](https://gitlab.gnome.org/GNOME/pitivi/issues/2146). We 
should take into account also the effects used most often by the user. Depending on what ideas we explore and 
how much this takes, a potential second task is related to the consistency of the UI for configuring effects. 
For example, quite a few effects for which the configuration UI is generated automatically allow specifying a 
color, but the UI is very rough—We should create a polished widget to be reused in all these cases for 
selecting or specifying a color.
- * Requirements: Python, eye for detail. Minimal experience contributing to Pitivi. Experience with 
GStreamer would be a big plus.
- * Mentor: Alexandru "aleb" Băluț
-
-## Timeline interval
- * Brief explanation: The initial task would be to allow the user to specify an [interval on the 
timeline](https://gitlab.gnome.org/GNOME/pitivi/issues/1842). The next tasks follow up on this: playing the 
interval in a loop, or [rendering only the interval](https://gitlab.gnome.org/GNOME/pitivi/issues/1006) 
instead of the entire timeline of the project, or zoom-fitting the timeline on the selected interval.
- * Requirements: Python. Minimal experience contributing to Pitivi. Experience with GStreamer would be a big 
plus.
- * Mentor: Alexandru "aleb" Băluț
-
-## Render experience
- * Brief explanation: The Render dialog has options the users should not normally need to care about. This 
will be an exploratory task involving usability studies with people. You'll have the opportunity to learn 
about usability studies. We'll be in close contact with the GNOME Designers team. The experience when using 
the Encoder Settings dialog could similarly be improved for one or more important encoders.
- * Requirements: Python, eye for detail. Minimal experience contributing to Pitivi. Experience with 
GStreamer would be a big plus.
- * Mentor: Alexandru "aleb" Băluț
-
-## Render queue
- * Brief explanation: Currently when starting a render, the edit functionality is blocked until the render 
is done. The main task would be to render in the background. The second task would be to have a render queue 
with a simple management UI.
- * Requirements: Python. Minimal experience contributing to Pitivi. Experience with GStreamer would be a big 
plus.
- * Mentor: Mathieu Duponchelle
-
-## Nested timelines/projects
- * Brief explanation: The user should be able to use a project as if it was a clip in the timeline, allowing 
to [separate the scene in different sub projects](https://gitlab.gnome.org/GNOME/pitivi/issues/500) to better 
organize complex projects. The focus will be on the User Interface to expose the feature that needs to be 
finalized in [GStreamer Editing Services](GES.md). A usability study can be performed, which you have the 
opportunity to learn about.
- * Requirements: Python. Minimal experience contributing to Pitivi. Experience with the GStreamer Editing 
Services would be a big plus.
+## Cut perspective
+ * Brief explanation: The most tedious process of video editing is the initial cutting and structuring of 
the global timeline. A new perspective similar to the 
[EditorPerspective](https://gitlab.gnome.org/GNOME/pitivi/blob/master/pitivi/editorperspective.py) will offer 
a [second timeline representation](https://gitlab.gnome.org/GNOME/pitivi/issues/2381) above the timeline, 
that is always zoom-fitted. This could build on the [markers 
functionality](https://gitlab.gnome.org/GNOME/pitivi/blob/master/pitivi/timeline/markers.py) to allow for 
pre-insertion trimming.
+ * Requirements: Python. Minimal experience contributing to Pitivi.
  * Mentor: Thibault "thiblahute" Saunier
 
 ## Fix GPU support in Pitivi
- * Brief explanation: GStreamer has pretty good GPU support through the OpenGL set of plugins, but 
Pitivi/GES is not able to take full advantage of that infrastructure yet, mainly because of lack of testing 
and bug fixing on our side. This project is about enabling GL plugins for compositing and rendering and fix 
any issue that shows up. The second part would be about making sure hardware accelerated decoders can be used 
in the pipelines.
+ * Brief explanation: GStreamer has pretty good GPU support through the OpenGL set of plugins, but 
Pitivi/GES is not able to take full advantage of that infrastructure yet, mainly because of lack of testing 
and bug fixing on our side. This project is about 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 contributing to Pitivi. 
Experience with OpenGL is a plus.
  * Mentor: Thibault "thiblahute" Saunier
diff --git a/docs/Roadmap.md b/docs/Roadmap.md
index f7bf9303..9c1c9462 100644
--- a/docs/Roadmap.md
+++ b/docs/Roadmap.md
@@ -22,19 +22,14 @@ Any time estimates here are mostly wild guesses. Do not treat them as
 hard deadlines. This aims mostly at giving an idea of how milestones
 follow each other.
 
--   2019 Q1: release [1.0](releases/1.0.md) with ponies and rainbows
+-   2019 Q4: release [1.0](releases/1.0.md) with ponies and rainbows
 
 See [Current events](Current_events.md) for past items.
 
 # Major features
 
-## Porting to Windows and Mac
-
-Status: started
-
-We have a [Homebrew recipe](https://gist.github.com/aleb/8bfe374e4fe68419567a9d473217da95)
-for building Pitivi, but we still have to integrate Matplotlib and
-make a standalone DMG out of that.
+Besides the items below we care about, see also the list of
+[GSoC project ideas](GSoC_Ideas.md).
 
 ## Motion ramping, time stretching
 
@@ -51,27 +46,6 @@ make a standalone DMG out of that.
     compositing](https://gitlab.gnome.org/GNOME/pitivi/issues/966),
     [audio equalizer](https://gitlab.gnome.org/GNOME/pitivi/issues/1551)
 
-## Advanced layer management
-
--   See [issue 930](https://gitlab.gnome.org/GNOME/pitivi/issues/930#note_68393)
-
-## A better title editor
-
--   The current title editor UI is very simple. Please join us to make
-    it work up to your expectations! See the existing [title editor
-    issues](https://gitlab.gnome.org/GNOME/pitivi/issues?label_name%5B%5D=titles+editor).
-
-## MAM/DAM
-
--   [Digital asset
-    management](http://en.wikipedia.org/wiki/Digital_asset_management)
-    is the ability to manage huge amounts of media (video clips, sounds,
-    images, etc.). This feature is very much needed for professional
-    editing; it allows handling multiple simultaneous camera angles,
-    multiple takes of the same scene, multiple sound sources, etc.
--   Potentially being addressed by the Novacut team with
-    [dmedia](https://launchpad.net/dmedia)
-
 ## Hardware-accelerated decoding and encoding
 
 -   Since GStreamer 1.2, the basic infrastructure allowing us to cleanly
@@ -79,11 +53,3 @@ make a standalone DMG out of that.
     cards is there. We need to ensure that our planned usecases are
     properly supported with the most common graphic drivers (through
     VA-API) and to make the integration work in Pitivi.
-
-## Proxy editing
-
--   Status: [done](https://gitlab.gnome.org/GNOME/pitivi/issues/743) but
-    the proxy experience can be better
--   See [proxy editing
-    requirements](design/Proxy_editing_requirements.md) for the “spec”
-    of how this feature should behave
[Date Prev][Date Next] [Thread Prev][Thread Next] [Thread Index] [Date Index] [Author Index]