Skip to content

Commit

Permalink
gsoc: Add summary of GSoC Kick-off meeting, May 27, 2024
Browse files Browse the repository at this point in the history
Signed-off-by: Razvan Deaconescu <[email protected]>
  • Loading branch information
razvand committed May 27, 2024
1 parent 13b4b5d commit 63f90b6
Showing 1 changed file with 87 additions and 0 deletions.
87 changes: 87 additions & 0 deletions discussions/gsoc/2024-05-27.md
Original file line number Diff line number Diff line change
@@ -0,0 +1,87 @@
---
datetime: 2024-05-27T17:00:00+02:00
location: Online, Discord (https://bit.ly/UnikraftDiscord), the `#monkey-business` voice channel
teams:
- gsoc
participants:
- Răzvan
- Sergiu
- CristiV
- RăzvanV
- RaduN
- ȘtefanJ
- Cezar
- Luca
- MariaP
- Spriprad
- Ujjwal
- Yang
- Mihnea
---

### Agenda

- GSoC'24 schedule
- Mentor and mentee intro
- Unikraft development process
- Mentor / mentee expectations
- General project development & resources: meetings, channels, communication, (draft) PRs
- Q&A
- (Technical) Project breakout rooms

### Discussions

Timeline:

* https://developers.google.com/open-source/gsoc/timeline
* https://summerofcode.withgoogle.com/programs/2024

Public:

* https://github.com/unikraft/gsoc/blob/staging/gsoc-2024/ideas.md

Resources:

* periodic online live meetings
* `meeting-notes` repository: https://github.com/unikraft/meeting-notes/tree/staging/discussions/gsoc
* keep a meeting summary
* Discord channel
* GitHub
* GitHub projects
* repository (source code)
* draft PRs (source code, discussions)

Contributions:

* submission / review process: https://unikraft.org/docs/contributing/
* PRs: run `checkpatch.pl`, properly test, provide extensive details on issues
* coding conventions: https://unikraft.org/docs/contributing/coding-conventions

Expectations:

* ask as often and as quick as possible questions on Discord, do not wait for meetings
* be responsive to mentor requests for progress, technical questions, any other clarifications
* announce a week before if a level of unavailability (vacation or anything else)
* keep a good look on the project timeline and on GSoC'24 timeline (midterm evaluation, final evaluation)
* provide feedback, suggestions to mentors if any sort of personal / technical issues
* carefully read and follow the contributing and coding guidelines
* create work early on (draft PRs, issues, documentation) and provide access to mentors
* take part in:
1. GSoC project specific meetings
1. periodic technical meetings relevant to your project
1. community meeting - to be announced
* be active in community: look at questions, provide support if able to
* create a blog post once every 3 weeks (4 blog posts in total): https://github.com/unikraft/docs

### TODOs and Decisions

* Mentors: be part of periodic meetings with mentees
* Mentors: keep active connections with mentees, ask them about 2-3 days how is it going, whether there are blocking points
* Mentees: start working on projects
* Mentees: have weekly time allocated for GSoC'24 starting with Monday, May 27, 2024 (the official start date)
* Mentees: take part in relevant meetings; be active on Discord; create early / draft PRs
* Mentees: create a blog post once every 3 weeks (4 blog posts in total): https://github.com/unikraft/docs
* Mentors / Mentees: be pro-active in communicating with the other party
* Mentees: (recommendation, not mandatory) keep logs of activities
* RD: Schedule booting and synchronization-smp meeeting.
* RD: Schedule community all hands on deck meeting.

0 comments on commit 63f90b6

Please sign in to comment.