unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Daniel Clemente <dcl441-bugs@yahoo.com>
To: emacs-devel@gnu.org
Subject: Re: Summer of Code 2009
Date: Thu, 15 Jan 2009 11:10:59 +0100	[thread overview]
Message-ID: <87k58wg9qk.fsf@CPU107.opentrends.net> (raw)
In-Reply-To: 18797.40998.179248.71695@kahikatea.snap.net.nz



Hi,
  I think this is a very good opportunity to tackle the big projects which have been around for a long time and which would improve Emacs considerably.


  As examples:

1. Integrate CEDET into Emacs
-----------------------------
  This will ease support for other languages and integrate features like code completion, syntax checking, project handling, ... Some other tools like JDEE (Java support) or ECB could also be included.


2. Good multithreading support for Emacs
----------------------------------------
  This is much wanted, specially for background processes like checking mail. It is necessary to profit from multicore processors, very common nowadays.
  There were already attempts to do this.


3. Version control system and bug tracker
-----------------------------------------
  This would include:
- setting the Bazaar repository, migrating from CVS to Bazaar
- web interface to the bug tracker, similar to the other projects like Bugzilla and Launchpad, where you could see reports, send a new bug, query for bugs, ...
- and at the same time, mail interface, where you can issue all commands just via mail
- integration between VC and bug tracker; similar to what Bundle Buggy (in Launchpad) does: patch tracking, asking for automatic merges from the mailing list, patch approval, ...
- some other infrastructure tasks could be added, like automatic building (continuous integration), breakage detection (get noticed when code doesn't compile), validation at commit time, ...



  There are for sure more ambitious projects; and I'm sure that many students would apply for them. Emacs needs mentors first.


  Greetings,

Daniel






  parent reply	other threads:[~2009-01-15 10:10 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-01-14  8:19 Summer of Code 2009 Nick Roberts
2009-01-14 13:52 ` Chong Yidong
2009-01-14 19:07   ` Nick Roberts
2009-01-22  6:56   ` Dan Nicolaescu
2009-01-22 14:31     ` Stefan Monnier
2009-01-15 10:10 ` Daniel Clemente [this message]
2009-01-16  0:25   ` Richard M Stallman
2009-01-16  7:10   ` Nick Roberts
2009-01-16 14:18     ` Daniel Clemente
2009-01-16 22:13       ` Lennart Borgman
2009-01-23 11:13         ` Daniel Clemente
2009-01-17  0:19     ` Will Farrington
2009-01-18  0:53       ` Nick Roberts
2009-01-18 20:12         ` Glenn Morris
2009-01-18 20:33           ` Stefan Monnier
2009-01-18 21:35             ` Alex Ott
2009-01-19  2:41         ` Will Farrington
2009-01-19  3:02           ` Chong Yidong
2009-01-19  7:30             ` Will Farrington
2009-01-20  0:59               ` Richard M Stallman
2009-01-19  7:38             ` Will Farrington
2009-01-19  6:45           ` Nick Roberts
2009-01-19  7:32             ` Will Farrington
2009-01-18 10:24   ` Alex Ott
2009-01-18 14:37     ` Chong Yidong
2009-01-19  4:30     ` Richard M Stallman

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=87k58wg9qk.fsf@CPU107.opentrends.net \
    --to=dcl441-bugs@yahoo.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).