unofficial mirror of guix-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Pjotr Prins <pjotr.public12@thebird.nl>
To: Guix Devel <guix-devel@gnu.org>
Subject: Projects for the Google Summer of Code
Date: Sun, 26 Feb 2023 08:38:36 +0100	[thread overview]
Message-ID: <20230226073836.daeias6fqowdsq45@thebird.nl> (raw)
In-Reply-To: <CAAqdTgNRbrNx-Ly-X3QsocHb4mo_Nw5BddFetDe0XekQZBtXEA@mail.gmail.com>

To follow up on Gábor: we excited to announce that the GNU project is
selected as an organisation for the Google Summer of Code (GSoc). GSoC
attracts talent and we have some people in our group who came in
through that route! I have done 10 years of GSoC and it has paid off
in my projects. You can still add ideas to:

https://libreplanet.org/wiki/Group:Guix/GSoC-2023

Currently only pukkamustard's project is listed, feel free to add
more. You can register/login yourself. Make sure to add below
information - title, email, hours etc. Tasks can be challenging - you
get more interesting applicants that way. Also add simple tasks, that
helps attract learners in Lisp, for example.

The overall GNU project proposals, including GNU Mes, are listed at:

https://www.gnu.org/software/soc-projects/ideas-2023.html

People are already inquiring, so today is a good day to add your idea.

When it comes to mentoring, in my experience it takes a few hours a
week that have a decent ROI. Before GSoC starts we'll have a get
together to share experiences and ideas.

Pj.

On Fri, Feb 24, 2023 at 07:21:51PM +0100, Gábor Boskovits wrote:
>    Hello Guix,
>    Here follows a short summary on where we are regarding the internship
>    programs.
>    GSoC:
>    This year the GNU Project was applying again for GSoC, and
>    we got the word yesterday that the GNU Project was accepted.
>    Thanks to Jose E. Marches for taking care of this.
>    This basically means that we should have a look at our ideas page,
>    and run a quick health check on the proposals, enriching them with
>    the following information where needed:
>    (quoted from the mail on the summer of code list)
>      + Title, and description.
>      + Skills required.
>      + A mentor with an email address.
>      + Whether it is a 175 hour or a 350 hour project.
>      + Difficulty: easy, medium or hard.
>      + CLEAR contact method for interested students.
>    From now to March 19, be ready to be contacted by contributors, in
>    whatever contact means you specified in your ideas page.  Starting in
>    March 20, contributors will start submitting their proposals through
>    the
>    program website.
>    (end quote)
>    Next week I am on holiday, so I asked Pjotr Prins to take over the
>    initial
>    coordination tasks until I am back on 6th of March, 2023.
>    Outreachy:
>    Coming up with a working solution for funding here is far from trivial.
>    Thanks to Andreas Enge and Simon Touriner now all stakeholders are
>    involved and
>    we are working on a solution. I don't want to bore the list with the
>    details
>    here, and I will send an update once we have an agreement on how to
>    handle it.
>    Thanks to everyone who is helping this effort.
>    Best regards,
>    g_bor


  parent reply	other threads:[~2023-02-26  7:39 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-02-24 18:21 Internship coordination status report Gábor Boskovits
2023-02-25 12:53 ` Simon Tournier
2023-02-26  7:38 ` Pjotr Prins [this message]
2023-02-26 16:52   ` Projects for the Google Summer of Code Kyle
2023-02-27 10:46     ` Simon Tournier
2023-03-02 23:55       ` Kyle Andrews
2023-03-03  9:28         ` Simon Tournier

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://guix.gnu.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20230226073836.daeias6fqowdsq45@thebird.nl \
    --to=pjotr.public12@thebird.nl \
    --cc=guix-devel@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/guix.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).