unofficial mirror of guile-user@gnu.org 
 help / color / mirror / Atom feed
From: Noah Lavine <noah.b.lavine@gmail.com>
To: Mike Gran <spk121@yahoo.com>
Cc: Guile User <guile-user@gnu.org>
Subject: Re: [ANN] the Guile 100 Programs Project
Date: Wed, 30 Jan 2013 23:33:01 -0500	[thread overview]
Message-ID: <CA+U71=NbcS0bNdcKFWdXzKAGsUbvydw=DPKU4VmxVmaOvM6wvw@mail.gmail.com> (raw)
In-Reply-To: <1359587062.94850.YahooMailNeo@web120403.mail.ne1.yahoo.com>

[-- Attachment #1: Type: text/plain, Size: 2097 bytes --]

Hello,

This is a great idea! I especially like the way you ask for information on
what Guile features need to be improved. We could learn a lot from this
project.

I'm also curious - would you consider it bad for people who are already
contributing to Guile to volunteer? I have some free time coming up and the
project sounds fun to try, but you won't be adding another contributor to
Guile if I am chosen. :-)

Thanks,
Noah Lavine



On Wed, Jan 30, 2013 at 6:04 PM, Mike Gran <spk121@yahoo.com> wrote:

> Hello.  I'm pleased to announce the upcoming Guile 100 Programs
> Project.
>
> The Guile 100 Programs Project is an opportunity to show off your
> Guile skills in exchange for a small honorarium.
>
> Each week, on Monday, I'll announce a coding project and ask for
> volunteers.  On Wednesday, a volunteer will be chosen at random from
> all entrants.  The volunteer will have two weeks to complete the task.
> If judged to have completed the task correctly, he or she will receive
> a honorarium of 100 USD.
>
> The task will either be a Scheme script, a bug fix on an existing
> project, or a C code with Guile bindings.
>
> The Guile 100 Programs project will begin March 11, 2013.  The location
> of the website is still TBD. The site is not live yet and will go live
> just before the beginning of the project.
>
> Along with the completed code, the entrant must submit two paragraphs
> on what was learned and what in the Guile experience needs to be
> improved.  If the project results in new code, the submitter must
> license it as GPL3+ or LGPL3+ as well as allowing it to appear in
> a GFLD-licenced document including invariant sections.
>
> The first two tasks to be announced will likely be
>
> Mar 11, 2013 - Implement a version of the commands `cat' and
> `echo' in Scheme.
>
> Mar 18, 2013 - Implement a reduced functionality version of the
> command `ls' in Scheme.
>
> Full terms and conditions will be announced when the site goes live.
> In the meantime, for more information or ideas you can contact me
> on list or at spk121@yahoo.com
>
> Thanks,
> Mike Gran
>
>
>

[-- Attachment #2: Type: text/html, Size: 2744 bytes --]

  reply	other threads:[~2013-01-31  4:33 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-30 23:04 [ANN] the Guile 100 Programs Project Mike Gran
2013-01-31  4:33 ` Noah Lavine [this message]
2013-01-31  4:43   ` Mike Gran
2013-01-31  6:56     ` Nala Ginrut
2013-01-31 16:55 ` Ludovic Courtès
2013-02-01  9:15 ` zx spectrumgomas
2013-02-01 16:40 ` Ian Price
2013-02-01 17:28   ` Nala Ginrut
2013-02-01 17:41     ` Mike Gran
2013-02-02  2:16     ` Hengqing Hu
2013-02-02  3:14       ` Nala Ginrut
2013-02-02  3:21         ` Hengqing Hu
2013-03-12  5:37 ` Mike Gran

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='CA+U71=NbcS0bNdcKFWdXzKAGsUbvydw=DPKU4VmxVmaOvM6wvw@mail.gmail.com' \
    --to=noah.b.lavine@gmail.com \
    --cc=guile-user@gnu.org \
    --cc=spk121@yahoo.com \
    /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).