unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: "Aurélien Aptel" <aurelien.aptel+emacs@gmail.com>
To: Emacs development discussions <emacs-devel@gnu.org>
Subject: Google Summer of Code - some ideas
Date: Sun, 21 Apr 2013 18:46:04 +0200	[thread overview]
Message-ID: <CA+5B0FOD+C=xOxOg3GD_Zczg3=MhvDhG42+mekQVgXf5sSGOJg@mail.gmail.com> (raw)

Hi,

I would like to work on Emacs itself for this year GSoC. I have
several projects in mind.

- Modules & FFI

I'm interested in adding a way to load compiled modules dynamically
and possibly add a FFI. I say possibly because the more I look into
into the more I realize it's not really helpful for complex stuff and
simple stuff are easy to do with a module. I know Joakim Verona
suggested to look into GObjectIntrospection which he implemented in
his xwidget branch but I have not looked at it yet. It's possible that
this project overlaps a bit with Daimrod's project [1] in which case
we could both work on it, I don't think it would be a problem.

I've also already posted on the mailing list about it [2] if you want
to know more.

- Internal documentation

I have started a "Hacker Guide" on the wiki few month ago [3] hoping
some people would jump in to help me (didn't happen :( ). Anyway Eli
gave me some advice and suggestions to improve it but I didn't have
the time to work on it. Ultimately this could end up in the manual. I
could also clean/fix some things as I document them.

- Support for library <FOO>

By support I mean expose the lib API to Emacs Lisp. I don't know which
lib could be added but I'm sure people here could make some
suggestions. This can be done to extend Elisp or to make it faster (or
both :).

All these are just ideas, you can always suggest something different
for any of them.

As for the credentials, I've already several contributions related to Emacs :
- raw strings patch which you can read more about on my blog [4]
- under-"waving" patch (accepted) [5]
- I've worked on org-mode in last year GSoC

Also I've already signed/sent the copyright assignment, so that's
done. Thought I should mention it.

So, If an emacs hacker is interested in mentoring any of these
projects please manifest yourself :) !


1: http://comments.gmane.org/gmane.emacs.devel/158990
2: http://comments.gmane.org/gmane.emacs.devel/151243
3: http://www.emacswiki.org/emacs/HackerGuide
4: http://definitelyaplug.b0.cx/post/raw-strings/
5: http://comments.gmane.org/gmane.emacs.devel/147958



             reply	other threads:[~2013-04-21 16:46 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-04-21 16:46 Aurélien Aptel [this message]
2013-04-21 17:16 ` Google Summer of Code - some ideas Aurélien Aptel
2013-04-21 17:25   ` Bastien
2013-04-21 17:53     ` Aurélien Aptel
2013-04-21 23:05       ` Bastien
2013-04-21 18:34 ` joakim
2013-04-22 14:34 ` Stefan Monnier
2013-04-22 16:48   ` Eli Zaretskii
2013-04-23  3:23     ` Stefan Monnier
2013-04-22 17:51   ` Aurélien Aptel
2013-04-22 18:26     ` Eli Zaretskii
2013-04-22 20:16       ` Jérémie Courrèges-Anglas
2013-04-22 20:30         ` Eli Zaretskii
2013-04-22 20:39           ` Jérémie Courrèges-Anglas
2013-04-23  2:38             ` Eli Zaretskii
2013-04-23 16:21               ` Eli Zaretskii
2013-04-22 15:52 ` Lennart Borgman

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/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='CA+5B0FOD+C=xOxOg3GD_Zczg3=MhvDhG42+mekQVgXf5sSGOJg@mail.gmail.com' \
    --to=aurelien.aptel+emacs@gmail.com \
    --cc=emacs-devel@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.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs.git

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).