From: Amirouche Boubekki <amirouche.boubekki@gmail.com>
To: Guile User <guile-user@gnu.org>
Subject: Scheme Coding Competition
Date: Thu, 18 Jul 2019 15:48:31 +0200 [thread overview]
Message-ID: <CAL7_Mo_eZTg0CZC3FpmzFa-T=sQomwx8N5u-HNXq_4hRjdfHrw@mail.gmail.com> (raw)
I am organizing a Scheme coding competition where you have
to build a static blog generator with a mystery feature (that will
be revealed little by little in the next few months).
We already have sourcehut.org as a sponsor and I am actively looking
for other sponsors to reward the participants (goodies, cloud credits,
books...).
More information after the jump:
https://git.sr.ht/~schemers/competition-2019-static-blog-generator#schemers-competition-2019
Ultimately the goal is to contribute a scheme presence at
https://www.staticgen.com/
Follow @schemers@mastodon.technology <https://mastodon.technology/@schemers>
for more regular updates.
Good read and good luck!
next reply other threads:[~2019-07-18 13:48 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-18 13:48 Amirouche Boubekki [this message]
2019-08-07 9:24 ` Scheme Coding Competition Amirouche Boubekki
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://www.gnu.org/software/guile/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAL7_Mo_eZTg0CZC3FpmzFa-T=sQomwx8N5u-HNXq_4hRjdfHrw@mail.gmail.com' \
--to=amirouche.boubekki@gmail.com \
--cc=guile-user@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.
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).