Hey Justin, I think it would be better if we ask the gsoc participants to go through handbook and material before diving deep into the projects. This suggestion should have been provided early but its never too late. It seems most of the gsoc participants are new to BSD as compared to Linux.
On Fri, Mar 30, 2012 at 7:59 PM, Justin Sherrill <jus...@shiningsilence.com>wrote: > On Fri, Mar 30, 2012 at 4:54 PM, Supriti Singh <supritising...@gmail.com> > wrote: > > I am looking at the use case of the virtioSCSI driver and learning about > the > > SCSI specification. I want to find out whether this will be a useful > support > > for DragonflyBSD, and will be accepted as a project for GSoC. Please > help me > > here. > > > > Since I am new to the DragonflyBSD kernel, I will take some time to > clearly > > understand the driver framework. My experience on Linux is going to help > me > > here. I want to find out the level of detail in design that is expected > from > > the student as a part of the project proposal. > > The proposal is what gets your project accepted. We (as in the > mentors) have to read the proposal, and based on its level of detail > (the schedule) and your apparent ability (provided code samples), > judge whether or not it's likely that your project will finish. We > also have to have an available mentor with interest in the project, > but that's secondary. > > The virtioSCSI driver is valuable, but we can't tell if your project > will be accepted without a proposal. The GSOC framework allows the > mentors to comment on your proposal and ask for feedback, so the best > thing to do is to have that proposal in, so that you can get questions > that ask for any needed detail. >
