caml-list - the Caml user's mailing list
 help / color / mirror / Atom feed
From: "Jon Harrop" <jon@ffconsultancy.com>
To: "'Ocaml Mailing List'" <caml-list@inria.fr>
Subject: RE: [Caml-list] GSoC preparedness
Date: Tue, 10 Feb 2015 12:36:51 -0000	[thread overview]
Message-ID: <016901d0452e$3fdf8610$bf9e9230$@ffconsultancy.com> (raw)
In-Reply-To: <CAN6ygOmD-C4NTZR=s_S4agEadzgV12mGgneJajzHKs8_imnq8A@mail.gmail.com>

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

Couple of ideas:

 

·       Android support for OCaml.

·       Replace the backend of GLSurf (which currently generates C code and compiles it with GCC) with a generic library that uses LLVM for run-time compilation of generated code.

 

From: caml-list-request@inria.fr [mailto:caml-list-request@inria.fr] On Behalf Of Yotam Barnoy
Sent: 06 February 2015 15:52
To: Ashish Agarwal
Cc: Ocaml Mailing List
Subject: Re: [Caml-list] GSoC preparedness

 

I believe the way it works (though I could be wrong) is that an open-source organization that signs up is supposed to have projects that concerns its codebase or related components. That means either the toolchain or some related tool like a debugger or perhaps something like Merlin. Perhaps it could even extend to a library that can be shown to be extremely useful to the community -- something like Lwt or Batteries.

 

It would be harder to make the case for something that's purely an application on top of OCaml, though I do believe that is possible once an organization is more established with GSoC, for example Xen getting Mirage into GSoC -- Anil would probably know more about that kind of thing.

 

Again, I could be wrong about this, so if anyone has better information, please correct me.

 

On Fri, Feb 6, 2015 at 10:42 AM, Ashish Agarwal <agarwal1975@gmail.com> wrote:

What you've written implies that all projects should regard the OCaml compiler itself. Is that the intention? Or could this support projects using the OCaml language for other purposes? What other purposes? General tools of use to the OCaml community, or just anything that happens to be implemented in OCaml.

 

Thanks for providing a place to collect these ideas.

 

 

On Fri, Feb 6, 2015 at 10:35 AM, Yotam Barnoy <yotambarnoy@gmail.com> wrote:

Hey everyone

 

Another year has gone by, and Google Summer of Code is upon us again. Unfortunately, it doesn't seem like we're ready to participate this year either (sign up dates for mentoring organizations are Feb 9th to the 20th). After seeing some comments on reddit, I have taken the liberty of establishing 2 pages on the ocaml.org wiki:

 

- GSoC ideas (https://github.com/ocaml/ocaml.org/wiki/GSoC-ideas): this is a list of ideas for projects that students could do. It needs to be filled up and then maintained, so that by next year at least, we actually have something to show google.

 

- GSoC Application (https://github.com/ocaml/ocaml.org/wiki/GSoC-application): a hastily filled out application covering the questions google expects answered. This should also be maintained so that it's pretty much ready to go.

 

Please fill out these pages as much as you can -- particularly the ideas page. I haven't listed any project ideas myself, but I tried to write some guidelines for the kinds of things that could be used as projects.

 

-Yotam

 

 


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

      parent reply	other threads:[~2015-02-10 12:36 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-02-06 15:35 Yotam Barnoy
2015-02-06 15:42 ` Ashish Agarwal
2015-02-06 15:51   ` Yotam Barnoy
2015-02-06 16:17     ` Gabriel Scherer
2015-02-06 16:28       ` Yotam Barnoy
2015-02-06 16:33         ` Gabriel Scherer
2015-02-06 16:50           ` Yotam Barnoy
2015-02-08 19:34     ` Anil Madhavapeddy
2015-02-10 12:36     ` Jon Harrop [this message]

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='016901d0452e$3fdf8610$bf9e9230$@ffconsultancy.com' \
    --to=jon@ffconsultancy.com \
    --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).