Re: Requesting for a project idea

[Justin Sherrill <justin@xxxxxxxxxxxxxxxxxx>]

--bcaec54fb9c629f28a04d25a2f1d
Content-Type: text/plain; charset=ISO-8859-1

Samuel's links are exactly what I would have posted.  In addition to that:

- There's a #dragonflybsd channel on EFNet, where you can talk to
developers.  There's no guarantee that someone will be there to talk about
your projects at the time you're there, but it may work out.

- Based on my experiences with the last few years of Google Summer of Code,
if you want to take a DragonFly project, make a detailed schedule.  The
first sign of trouble for a project is when it falls behind schedule, and
you want to be able to tell when that's happening as soon as possible, so
that you can correct for it.

- As part of your schedule, plan for some way of publicly updating people
on the status of your project.  Explain what it does, what decisions you
are making, what challenges you face, and so on.  Specifically for
DragonFly, it means I can link to news about work on the Digest (
http://shiningsilence.com/dbsdlog/) and it keeps a conversation going for
when you need help, or just the simple encouragement of having other people
interested in your work.

- Those last two can apply to any project for any organization, not just
something with DragonFly.  Plan out what you're going to do, and talk about
it while you do it.  It makes a huge difference for project success.

--bcaec54fb9c629f28a04d25a2f1d
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable

Samuel's links are exactly what I would have posted. =A0In addition to =
that:<div><br></div><div>- There&#39;s a #dragonflybsd channel on EFNet, wh=
ere you can talk to developers. =A0There&#39;s no guarantee that someone wi=
ll be there to talk about your projects at the time you&#39;re there, but i=
t may work out.</div>
<div><br></div><div>- Based on my experiences with the last few years of Go=
ogle Summer of Code, if you want to take a DragonFly project, make a detail=
ed schedule. =A0The first sign of trouble for a project is when it falls be=
hind schedule, and you want to be able to tell when that&#39;s happening as=
 soon as possible, so that you can correct for it.</div>
<div><br></div><div>- As part of your schedule, plan for some way of public=
ly updating people on the status of your project. =A0Explain what it does, =
what decisions you are making, what challenges you face, and so on. =A0Spec=
ifically for DragonFly, it means I can link to news about work on the Diges=
t (<a href=3D"http://shiningsilence.com/dbsdlog/";>http://shiningsilence.com=
/dbsdlog/</a>) and it keeps a conversation going for when you need help, or=
 just the simple encouragement of having other people interested in your wo=
rk.</div>
<div><br></div><div>- Those last two can apply to any project for any organ=
ization, not just something with DragonFly. =A0Plan out what you&#39;re goi=
ng to do, and talk about it while you do it. =A0It makes a huge difference =
for project success.</div>

--bcaec54fb9c629f28a04d25a2f1d--