Re: [9fans] GSOC: Gitfs

[yy <yiyu.jgl@gmail.com>]

2009/3/26 Devon H. O'Dell <devon.odell@gmail.com>:
> The GSoC traffic is misdirected. The GSoC emails *SHOULD* be going to
> the plan9-gsoc list, which is hosted by Google.
>

I hope the plan9-gsoc list gets more attention. I sent my project
ideas there a week ago and you were the only person who replied my
message. Maybe that's why people is directing their emails to 9fans.

Since I would really like to hear some comments before writting my
application, I will explain here what I have in mind (there's also
some alternative ideas in my original message:
http://groups.google.com/group/plan9-gsoc/browse_frm/thread/52d77f27a3f5645b):
1. Cleaning up drawterm and 9vx draw devices in unix (I don't have a
windows or macos dev environment, or any experience FWIW). I have seen
several small TODOs in the code, and in particular all the Xlib code
should be isolated. I don't know if a complete merge would be
possible, or if p9p could be included in the group.
2. As suggested in drawterm TODO, replace the console with 9term (in 9vx too).
3. Write a wctl device which speaks directly with Xlib, this way rio
wouldn't have to (but could) be used in 9vx/drawterm, and windows
could be managed with the X wm.
4. I have seen the A-term proposition in gsoc.cat-v.org and I could do
it. I'm quite familiar with acme code and in fact is something I had
in mind (to be used with the wctl described above).
I don't think any of these projects is enough for gsoc, but more than
one of the ideas could be combined. I'd like to know your opinions
about what could/should be done.

Regards,


--
- yiyus || JGL .