From: James Westby <jw+debian@jameswestby.net>
To: Josh Triplett <josh@kernel.org>
Cc: Alexey Zaytsev <alexey.zaytsev@gmail.com>, linux-sparse@vger.kernel.org
Subject: Re: Sparse and the Google Summer of Code 2008
Date: Tue, 11 Mar 2008 19:08:53 +0000 [thread overview]
Message-ID: <1205262533.6161.4.camel@flash> (raw)
In-Reply-To: <47D6CD7F.6010800@kernel.org>
On Tue, 2008-03-11 at 11:20 -0700, Josh Triplett wrote:
> If anyone else on the Sparse list has an interest in mentoring, please
> let me know as soon as possible.
>
> For anyone thinking about project ideas, I'd like to make two general
> recommendations:
>
> * Have specific goals, rather than just "improve support for $FOO".
>
> * Release early, release often. Please get comfortable with the idea
> of releasing your work to the Sparse mailing list, regardless of the
> current state of that work.
>
> Regarding specific project ideas, I would have a particularly strong
> interest in projects related to improved context checking (including
> via abstract interpretation or similar), projects to make it easier to
> add new checks to Sparse or maintain the existing checks, or projects
> attempting to port C test suites (such as GCC's) to Sparse.
Hi,
I have some interest in abstract interpretation and the like, and I
think it would be cool for someone to work on it, so I would be willing
to (co-)mentor someone on this project.
I realise I am not known on this list, so you may not want to trust me
with the role, and I would understand that.
Thanks,
James
next prev parent reply other threads:[~2008-03-11 19:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-11 17:38 Sparse and the Google Summer of Code 2008 Alexey Zaytsev
2008-03-11 18:20 ` Josh Triplett
2008-03-11 19:08 ` James Westby [this message]
2008-03-11 22:10 ` Christopher Li
2008-03-12 1:41 ` Derek M Jones
2008-03-12 2:20 ` Alexey Zaytsev
2008-03-12 4:28 ` Josh Triplett
2008-03-12 15:19 ` Neil Booth
2008-03-12 20:01 ` Josh Triplett
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=1205262533.6161.4.camel@flash \
--to=jw+debian@jameswestby.net \
--cc=alexey.zaytsev@gmail.com \
--cc=josh@kernel.org \
--cc=linux-sparse@vger.kernel.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.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.