From: Robert Buchholz <rbu@gentoo.org>
To: gentoo-security@lists.gentoo.org
Cc: Mansour Moufid <mansourmoufid@gmail.com>
Subject: Re: [gentoo-security] the Gentoo Audit project and dev-util/splint
Date: Thu, 11 Jun 2009 16:13:20 +0200 [thread overview]
Message-ID: <200906111613.22362.rbu@gentoo.org> (raw)
In-Reply-To: <44a1f4d20906101335t108a410bjef39a1d9d97e2004@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 1551 bytes --]
Hello Mansour,
On Wednesday 10 June 2009, Mansour Moufid wrote:
> > But keep in mind there is a certain amount of work that comes with
> > this.
>
> How much time would members typically put in, say, per week? I
> imagine it's difficult to estimate an 'average' -- since most of the
> time spent is probably in actually reviewing source code -- but I'm
> looking forward to contributing a decent number of hours a week as
> part of this project. Effort is certainly no deterrent.
As with most oss projects, you put in the amount of time you are
comfortable with. There's usually more items on the TODO stack than you
can handle anyway, so you either let it rest for a few days/weeks when
you are busy, or work off large chunks when you have some time to burn.
To get you started, I would suggest you look for tasks that sound
interesting. There are several bugs that need attention. Some of them
are in the "Gentoo Security/Audit" section of Bugzilla. Mondo-rescue's
latest version needs to be looked at, for example:
https://bugs.gentoo.org/show_bug.cgi?id=106497
There is a list of packages bundling libraries. Some of these might have
security impact:
https://bugs.gentoo.org/showdependencytree.cgi?id=251464
There's also some of the "Gentoo Security/Vulnerabilities" bugs that
need attention. If you're seeking to discover new vulnerabilities
instead of working on details of existing bugs, can literally start
anywhere you like.
Contact us in IRC or via Jabber if you need assistance.
Robert
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
prev parent reply other threads:[~2009-06-11 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-04 3:44 [gentoo-security] the Gentoo Audit project and dev-util/splint Mansour Moufid
2009-06-04 10:58 ` Robert Buchholz
2009-06-10 20:35 ` Mansour Moufid
2009-06-11 14:13 ` Robert Buchholz [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=200906111613.22362.rbu@gentoo.org \
--to=rbu@gentoo.org \
--cc=gentoo-security@lists.gentoo.org \
--cc=mansourmoufid@gmail.com \
/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