> well, perhaps. in this case, however, he's looking for a student project, > and one that's essentially a load of grunge work isn't a good choice.
I don't think grunge work is bad if the result is usable. Hence, what I am trying to evaluate via the discussion is whether the result is something that can actually be used by developers. > it might or might not have been a good gsoc project, but i don't think > it's the best choice for a final year project, even if you're in Engineering > not CS. > (the aims are often quite different for gsoc projects than for a final-year > project.) Incidentally, I am pursuing Computer Engineering - but syllabi can be easily mistaken for a CS course, there's no difference. > if you're looking for something plan9-related, i'd pick an application area > of interest to you that looks as though it could benefit from applying plan > 9's > techniques, mechanisms, etc., and apply them in an implementation. > if you aim to finish in about 2 months, you should be done in time in 4, with > write-up. > a modular project is always good, so if you've actually got spare time > at the end, you can add another component. (for instance, if the project > is split into 9p server and 9p clients, you can add a different type of client > for the same service.) Thanks, I'll look some more and see if I can find more ideas. (Trouble is, I already registered glendix.org ;)) -- Anant
