public inbox for libstdc++@gcc.gnu.org
 help / color / mirror / Atom feed
From: Jerry D <jvdelisle2@gmail.com>
To: Martin Jambor <mjambor@suse.cz>,
	GCC Mailing List <gcc@gcc.gnu.org>,
	Gfortran mailing list <fortran@gcc.gnu.org>,
	libstdc++@gcc.gnu.org
Subject: Re: GCC GSoC 2022: Call for project ideas and mentors
Date: Wed, 9 Mar 2022 18:09:28 -0800	[thread overview]
Message-ID: <7ff8f8f1-8b39-46f6-64fd-ba18920965a0@gmail.com> (raw)
In-Reply-To: <ri6tuc7nqat.fsf@suse.cz>

Perhaps someone could work on completing and merging the shared memory 
(native) fortran coarrays branch.

Regards,

Jerry

On 3/9/22 6:39 AM, Martin Jambor wrote:
> Hello,
>
> I am pleased that I can announce that GCC has been accepted as a
> mentoring organization of Google Summer of Code 2022.
>
> Contributors(*) will be applying from April 4th to April 19th but have
> already seen some announcing their intention to apply and asking for
> guidance when selecting a project and preparing their applications.
> Please continue helping them figure stuff out about GCC like you always
> do.
>
> If anyone still wants to add a project to our idea list (and sign up to
> be a potential mentor), now is the time to do it.
>
> I'm looking forward to another year of interesting projects,
>
> Martin
>
>
>
> (*) Contributors no longer have to be students - they should
> however be "new or beginner" contributors to our project with the
> exception that participants of GSoC 2020 or GSoC 2021 can apply.
>
> More on changes this year is in my original call for projects:
> https://gcc.gnu.org/pipermail/gcc/2022-January/238006.html
>


  reply	other threads:[~2022-03-10  2:09 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-01-06 16:20 Martin Jambor
2022-01-07 17:41 ` David Malcolm
2022-01-12  9:53 ` Martin Jambor
2022-01-12 10:01   ` Martin Jambor
2022-03-09 14:39 ` Martin Jambor
2022-03-10  2:09   ` Jerry D [this message]
2022-03-10 16:13     ` Damian Rouson
2022-03-10 16:22       ` Martin Jambor

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

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

  git send-email \
    --in-reply-to=7ff8f8f1-8b39-46f6-64fd-ba18920965a0@gmail.com \
    --to=jvdelisle2@gmail.com \
    --cc=fortran@gcc.gnu.org \
    --cc=gcc@gcc.gnu.org \
    --cc=libstdc++@gcc.gnu.org \
    --cc=mjambor@suse.cz \
    /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.
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).