caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: William Le Ferrand <William.Le-Ferrand@polytechnique.edu>
To: caml-list@inria.fr
Subject: [Caml-list] Re: [ www.baoug.org ] ocaml puzzles
Date: Sat, 30 Jul 2011 13:06:15 -0700	[thread overview]
Message-ID: <CAGS5m-mX5jgYigdtzP0OWZFPr0QCWciFyXdpBVEqUor1nakU_A@mail.gmail.com> (raw)
In-Reply-To: <CAGS5m-m+cNLFHZPKNZzSN8dCqxeHbzyvooxOW9U+t9bPyOG0Pg@mail.gmail.com>

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

By the way, we have a dedicated mailing-list for the Bay Area OCaml User
Group (actually it's a google group)
http://groups.google.com/group/*baoug*<http://groups.google.com/group/baoug>
Feel
free to register to stay tuned; we'll organize a new meeting in the coming
weeks.

Many thanks to Cedric for his challenge on www.baoug.org ; who'll be the
next poster :) ?

Best

William

On Sat, Jul 30, 2011 at 1:09 AM, William Le Ferrand <
William.Le-Ferrand@polytechnique.edu> wrote:

> Dear all,
>
> Last week, we were three friends experimenting an "ocaml hackathon" : we
> met and we built a simple webservice where you can either post problems or
> try to solve them.
>
> It's now online at www.baoug.org and the code is released at
> https://github.com/baoug/ocaml-challenges . It's an 100% ocsigen 2.0
> website, leveraging the newest features of the framework (client/server
> interactions, message bus, etc ..)
>
> Although baoug.org is still lacking a lot of features (syntax
> highlighting, client side code checking, solution ranking, etc etc), we hope
> that it can already provide at least as much fun as we got when we wrote it.
> Actually, it's already waiting for your challenges :)
>
> This website is also the seminal event of baoug, the Bay Area OCaml User
> Group. We plan to organize some ocaml events here; the next one will be
> another hackathon to improve on baoug (if we get some feedback from you
> all!); we're based in California but everyone is invited, as we can get
> remote contributions. So far we're three, Marc Simon, Mike Well an I
> (William Le Ferrand), but we'll grow up, hopefully.
>
> If you want to contribute to the platform or if you have some ideas for
> fresh features, please get in touch !
>
> If you want to get more information about ocsigen and the way we leverage
> it, please don't hesitate either.
>
> What about posting a little challenge on www.baoug.org now :) ?
>
> Happy hacking,
>
> Cheers
>
> William
>
> --
> William Le Ferrand
>
> Mobile : (+1) (415) 683-1484
> Web : http://williamleferrand.github.com
>  <http://www.linkedin.com/in/williamleferrand>
>
>


-- 
William Le Ferrand

Mobile : (+1) (415) 683-1484
Web : http://williamleferrand.github.com/
<http://www.linkedin.com/in/williamleferrand>

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

  reply	other threads:[~2011-07-30 20:06 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-30  8:09 [Caml-list] " William Le Ferrand
2011-07-30 20:06 ` William Le Ferrand [this message]
2011-08-01 16:15   ` [Caml-list] " rixed
2011-08-01 18:23     ` William Le Ferrand

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=CAGS5m-mX5jgYigdtzP0OWZFPr0QCWciFyXdpBVEqUor1nakU_A@mail.gmail.com \
    --to=william.le-ferrand@polytechnique.edu \
    --cc=caml-list@inria.fr \
    /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 NNTP newsgroup(s).