From: Mike Gran <spk121@yahoo.com>
To: "Aleix Conchillo Flaqué" <aconchillo@gmail.com>
Cc: guile-user <guile-user@gnu.org>, guile-devel <guile-devel@gnu.org>
Subject: Re: Guile Potluck 2021
Date: Fri, 26 Feb 2021 17:08:17 -0800 [thread overview]
Message-ID: <1144e4d9920845eb4f49e6e099a306e85735bd01.camel@yahoo.com> (raw)
In-Reply-To: <CA+XASoVUb9vkd1dY9Nt0kRmctSwUriH4qm4SySfvBB3YfAJXzw@mail.gmail.com>
On Fri, 2021-02-26 at 15:19 -0800, Aleix Conchillo Flaqué wrote:
> In case it was not clear:
>
> guile-oauth 1.0.0 with OAuth2 support:
> https://github.com/aconchillo/guile-oauth
> guile-redis 2.1.0 with Redis 6.2.0 commands:
> https://github.com/aconchillo/guile-redis
>
> Aleix
>
Awesome. Thanks! Look forward to checking it out.
> On Sun, Feb 21, 2021 at 9:59 PM Aleix Conchillo Flaqué
> <aconchillo@gmail.com> wrote:
> >
> > Thank you Mike!
> >
> > I should have waited to release guile-oauth with the OAuth2 support
> > :-). But if that counts...
> >
> > Also planning to release guile-redis with redis 6.2 support when
> > they make a release (they are in RC3), but I might do it sooner.
> >
> > Best,
> >
> > Aleix
> >
> > On Thu, Feb 18, 2021, 9:43 AM Mike Gran <spk121@yahoo.com> wrote:
> > >
> > > Hello All-
> > >
> > > In celebration of the (slightly belated) 10-year anniversary of
> > > Guile
> > > v2.0, we're having another Guile Potluck! The Guile Potluck is a
> > > randomly annual event to give people a chance to show off their
> > > Guile
> > > projects and skills. Think of it as a game jam, but, not
> > > constrained
> > > to games.
> > >
> > > To participate, on or before Mar 6, send an email to
> > > guile-user@gnu.org
> > > with instructions on how to find your entry, which could be
> > > anything
> > > you like. For example,
> > >
> > > - a script showing off some feature of Guile or your favorite
> > > Guile
> > > library
> > > - a blog post describing something interesting about Guile
> > > - an updated release of a neglected library
> > > - a mini-game
> > > - a graphical or audio demoscene-type demo
> > >
> > > There probably won't be any prizes. But there will definitely be
> > > an e-
> > > mail and blog post about the entries.
> > >
> > > If you think you might attempt to participate, please reply to
> > > this e-
> > > mail so I can gauge the feasibility of some sort of participation
> > > swag.
> > >
> > > Regards,
> > > Mike Gran, on behalf of the Guile team
> > >
> > >
> > >
next prev parent reply other threads:[~2021-02-27 1:08 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <be71b3d5db9c43723c749f108dbd1ada7785daf2.camel.ref@yahoo.com>
2021-02-18 17:24 ` Guile Potluck 2021 Mike Gran
2021-02-20 17:38 ` Alex Sassmannshausen
2021-02-21 14:20 ` Dr. Arne Babenhauserheide
2021-02-21 17:21 ` Daniel Tornabene
2021-02-22 5:59 ` Aleix Conchillo Flaqué
2021-02-26 23:19 ` Aleix Conchillo Flaqué
2021-02-27 1:08 ` Mike Gran [this message]
2021-02-27 9:39 ` Dr. Arne Babenhauserheide
2021-02-27 10:14 ` Linus Björnstam
2021-02-27 16:42 ` Dr. Arne Babenhauserheide
2021-02-27 16:43 ` Dr. Arne Babenhauserheide
2021-03-02 7:08 ` Dr. Arne Babenhauserheide
2021-03-01 11:34 ` pukkamustard
2021-03-01 21:14 ` Linus Björnstam
2021-03-01 21:37 ` Aleix Conchillo Flaqué
2021-03-02 0:43 ` Dr. Arne Babenhauserheide
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=1144e4d9920845eb4f49e6e099a306e85735bd01.camel@yahoo.com \
--to=spk121@yahoo.com \
--cc=aconchillo@gmail.com \
--cc=guile-devel@gnu.org \
--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).