[ native-client-discuss moved to bcc, since there's some general
advice here, but i think future replies will not be of general
interest; feel free to cc n-c-d if you feel otherwise. ]
hi,
sounds good.
>
> > google NaCl team members have been professors in our past lives, but a
> > professor at your institution is needed, and generally it helps to
> > work with her/him to finalize the research focus.
>
> It is great to know that you have academic experience:) If it is
> needed, I will give my tutor a contact to you.
>
> > that said, we can try to come up with security-related projects that
> > would be appropriate for an MS thesis project. since you hadn't
> > mentioned crypto except as part of the seminar title, is it safe to
> > assume that you're more interested in the OS/Web security side of
> > things?
>
> Yes, it is. I am more interested in that area. The title of the
> seminary is general, so that we can focus on many various (theoretical
> or practical) topics.
one issue that i'd advise you on is that NaCl's main code base is
pretty fast moving -- and unless you're willing to have to deal with
frequent synchronization w/ the subversion repository and the
consequent merge conflicts, i'd recommend that you look at designing
and implementing applications of NaCl rather than features that would
require changes to the underlying core system. personally i find that
i lose significant time to dealing with merges, and if you're not
working on NaCl stuff full time i think you'll find it very annoying.
the alternative is to work from one particular revision number /
snapshot, but it makes it just makes it harder to integrate later --
if you want to at all -- research projects don't necessarily have to
contribute to the main repo, but if your project is to be on an open
source project, it seems silly if there's little hope of checking your
code in. furthermore, we are sticklers (or try to be) when it comes
to code review -- both for style and for security -- and w/o being
able to get your code reviewed for check in periodically, you'd end up
with a huge change list and nobody will want to review a large CL.
anyway, does that sound reasonable as a first step towards narrowing
down to an MS-sized project?
-bsy
>
> Regards,
> Daniel
>
> > should we take this off list?
> >
> > -bsy
> >
> >
> >
> > > Regards,
> > > Daniel
> >
> > > --
> >
> > > You received this message because you are subscribed to the Google Groups "Native Client Discuss" group.
> > > To post to this group, send email to
native-cli...@googlegroups.com.
> > > For more options, visit this group athttp://
groups.google.com/group/native-client-discuss?hl=.
> >
> > --
> > bennet s yee
> > i usually don't capitalize due to mild tendonitis
>
> --
>
> You received this message because you are subscribed to the Google Groups "Native Client Discuss" group.
> To post to this group, send email to
native-cli...@googlegroups.com.
> For more options, visit this group at
http://groups.google.com/group/native-client-discuss?hl=.