From af8802f91b97463eb2e64f60c7e1ed8d316c7171 Mon Sep 17 00:00:00 2001
From: Frederic Plourde <frederic.plourde@collabora.com>
Date: Tue, 7 Feb 2023 11:37:37 -0500
Subject: [PATCH] gsoc: Add 2023 page
---
gsoc-2023.md | 28 ++++++++++++++++++++++++++++
gsoc-proposal-guide.md | 2 +-
2 files changed, 29 insertions(+), 1 deletion(-)
create mode 100644 gsoc-2023.md
diff --git a/gsoc-2023.md b/gsoc-2023.md
new file mode 100644
index 0000000..d9a14e0
--- /dev/null
+++ b/gsoc-2023.md
@@ -0,0 +1,28 @@
+---
+title: "GSoC ideas 2023"
+layout: main
+---
+
+# Monado - GSoC Ideas 2023
+{:.no_toc}
+
+* TOC
+{:toc}
+
+# Frame Timing Tools
+
+In VR, stutters, judders and jitters in rendering are a much bigger deal than on desktop monitors. Instead of being just annoying, they can cause disorientation, and even motion sickness.
+Most importantly the VR runtime must push frames to the VR hardware at the native hardware refresh rate.
+To that end it must keep track of the frames submitted by client applications, reproject old frames if the client application missed an interval, and push the frames to the VR hardware while sharing GPU hardware resources with the client application. Such a system benefits greatly from good visual frame timing tools.
+A good frame timing tool would gather timing information from both the frames submitted by the client application and the frames submitted by the compositor to the hardware and relate them in a visual way. The visualization could be either done with an existing visualization tool like Perfetto, but it could also be a custom built UI for Monado.
+
+Deliverables
+* A system gathering frame timing information from client applications and the runtime compositor and relating them to each other
+
+Requirements:
+* Basic C
+* Experience with graphics programming (Vulkan) would be helpful
+
+Difficulty: medium
+
+Project Size : Large (~350 hours)
diff --git a/gsoc-proposal-guide.md b/gsoc-proposal-guide.md
index c80ac74..fb52827 100644
--- a/gsoc-proposal-guide.md
+++ b/gsoc-proposal-guide.md
@@ -13,7 +13,7 @@ layout: main
This page has some details on how you should prepare your proposal. It is only a guide so please do not feel constrained to follow it to the letter!
# Things to think about before applying
-Before you consider applying to work on Monado for Google Summer of Code 2022, please consider the following points:
+Before you consider applying to work on Monado for Google Summer of Code this year, please consider the following points:
Students who are accepted into the Google Summer of Code program are expected to work full-time hours for the 12 weeks of the program -- that's 40 hours a week. It is not a good idea to try to do GSoC and also work another job; there simply isn't enough time. It's okay if your schedule doesn't allow 40 hours weeks every week (for instance, if you are going on vacation) but you'll have to let us know so that we can work around it.
--
GitLab