GSoC OnBoarding

Day GSoC Is Announced

• set up the year’s mailing list

• send e-mail (below is a draft) to GSoC contributors

• send e-mail to swan-announce@

• also get mentors to contact developers individually

Here’s some boiler plate text

…

Welcome to Libreswan’s GSoC for %MS_DATE%>U.

This year we’ve the privilege of mentoring your projects:

%INCLUDE% HOPEFULLY_NON_EMPTY_LIST

To get things started, we’d like to set up a google-meet. Since we’ve Contributors and Mentors spread across the globe it’s going to be a little tricky.

We’re thinking sometime around %TIME-IN-UTC% UTC. Here’s a link:

%INCLUDE% HTTP_LINK_TO_FAVORITE_SCHEDULING_TOOL

(remember this document is not secure, so be vague with what you add).

Keeping in Contact:

We’ve set up a (private) group mailing list:

%SUBJECT_TO_CHANGE%@lists.libreswan.org

Think of it as your general discussion list (just know we’re also subscribed). If you’ve a question, send it here. If you discover something that might be useful, this is a good place to share it. We’ve also been a little presumptive - you should already all be subscribed.

If you have a more technical question, the public:

swan-dev@lists.libreswan.org

can be a better choice. But if it ends up being sent to the above, that’s OK. JUST DON’T FORWARD OR CROSS POST. Remember, as with any mailing list, please use group-reply (the double back arrow) to keep discussion on the list.

Libreswan also has the occasional add-hoc call where we get to discuss technical stuff. You’re all more then welcome to join. We might need to adjust the time as it’s tended to to be around %PAINFUL_TIME% UTC.

Where and how to do work:

Video Calls?

We’d like each of you and your Mentor to schedule a one 1-1 Google Meetup (or your poison of choice) each week. And we encourage other add-hoc sessions - a face to face discussion has much higher bandwith.

IRC?

If not already, can you find a way to be on IRC.

Where?

Our first preference is on GitHub with a public repository and pull requests pull-request.

If this is a problem we can also set up private repository. As a side note, Google (I’m told) likes to see the final deliverable presented as a branch (while, IMNSHO, that is not the best way to work with old code, It’s Google that is running things).

Testing?

To help with testing, we can set up dedicated (remote) hardware so tests can be run overnight if needed. We don’t want you to leaving a noisy hot computer running overnight cooking your workspace.

How?

We’ve the:

https://github.com/libreswan/libreswan/wiki/Hacking:-Programming-Conventions

page. I’ve tried to update it (oops I see the Kernel Style link is broken).

And remember:

Don’t use AI to write code: You won’t learn anything, …

and based on recent pull-requests, GitHub’s AI Bot seems especially incompetent).

Finall the most important Admin stuff:

• be sure to keep track of official GSoC correspondence

• especially the one on how Google will pay out the stipend (Google told us to mention that explicitly)

$SOME_NAMELESS_SOLE, for the Libreswan Project