Skip site navigation (1)Skip section navigation (2)
Date:      Thu, 12 Mar 2009 09:17:41 -0500
From:      Brooks Davis <brooks@FreeBSD.org>
To:        Robert Watson <rwatson@FreeBSD.org>
Cc:        Alexander Leidinger <Alexander@Leidinger.net>, Brooks Davis <brooks@FreeBSD.org>, cvs-doc@FreeBSD.org, cvs-all@FreeBSD.org, doc-committers@FreeBSD.org
Subject:   Re: cvs commit: www/en/projects/ideas ideas.xml
Message-ID:  <20090312141741.GA58535@lor.one-eyed-alien.net>
In-Reply-To: <alpine.BSF.2.00.0903121222070.61873@fledge.watson.org>
References:  <200903120659.n2C6xas2031642@repoman.freebsd.org> <20090312113812.179151uxuziye0w0@webmail.leidinger.net> <alpine.BSF.2.00.0903121128320.61873@fledge.watson.org> <20090312131147.18623am36o8ct24g@webmail.leidinger.net> <alpine.BSF.2.00.0903121222070.61873@fledge.watson.org>

next in thread | previous in thread | raw e-mail | index | archive | help

--TB36FDmn/VVEgNH/
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

On Thu, Mar 12, 2009 at 12:23:59PM +0000, Robert Watson wrote:
>=20
> On Thu, 12 Mar 2009, Alexander Leidinger wrote:
>=20
>>> I think there could be a useful project to be done on fleshing out kern=
el=20
>>> SDT providers, but that we need to come up with a more specific=20
>>> description if we want it to be useful for GSoC.  We also need to=20
>>> identify a potential mentor for the project who can field questions=20
>>> during the proposal process, potentially mentor the project, and so on.
>>=20
>> To have it on the ideas list we don't need a GSoC mentor... basically I=
=20
>> say that I think that the DTraceToolkit stuff should stay on the ideas=
=20
>> list in some form (doesn't matter to me if it is marked up fro the GSoC =
or=20
>> not).
>=20
> On the ideas list, perhaps, but I feel increasingly strongly that no idea=
=20
> without a technical contact should be tagged as GSoC-appropriate, and tha=
t=20
> we should also have mentors in mind for every project there. =20
> Pre-submission interaction improves not just the quality of the proposal,=
=20
> but also gives us an early sense as to whether they have the right skills=
=20
> so that they can tune the proposal to what it turns out the students are=
=20
> able to do. I also feel we shouldn't invite people to submit proposals on=
=20
> an idea if we don't have someone willing to mentor them, because we've ha=
d=20
> that happen and it's unproductive :-).

I agree.  To be blunt and specific, I plan to remove all class=3D"soc"
specifications on projects that don't have a contact listed before our
project profile is posted.  That doesn't mean we won't accept gsoc
proposals on untagged projects or that we can't list them, but the bar
will be higher.  I'm also not entirely convinced we should list ideas
without technical contacts, but that's a separate discussion.

-- Brooks

--TB36FDmn/VVEgNH/
Content-Type: application/pgp-signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.9 (FreeBSD)

iD8DBQFJuRmEXY6L6fI4GtQRApsFAJ0WKovwXR1hOxvVGeDtcGuxvkqIagCguxgl
7lC2NS93lP28jiMOxQI5j44=
=O9P3
-----END PGP SIGNATURE-----

--TB36FDmn/VVEgNH/--



Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?20090312141741.GA58535>