On Sat, Apr 25, 2009 at 11:40:32AM +0800, HuiHuang wrote:
>
> Hi, Stefan Sperling ;
Hey HuiHuang :)
> I am Huihuang from China. I am accepted as GSoCer by Subversion
> project on 'Allow Commit from multiple working copies' and you are my
> mentor. It is exciting to work with you excellent guys and I hope I
> can do the job well under your supervision.
Yes, we are glad to have you here.
Note that I am not your only mentor. In addition to myself, the
following people are mentoring your project, too:
Stephen Butler
Hyrum Wright
We have multiple mentors because I myself am still a student, too.
I am in my last year, and I have exams next month. I won't be able
to spend much time on mentoring until June. I will try to help you
as much as I can but we will need Hyrum's and Stephen's help because
I cannot always spend time on Subversion right now. I hope you
understand.
> These days I have checked out the Subvision code and read some
> introduction on the project website:
>
> Introduction to Subversion Development.
> Hacker's Guide to Subversion.
>
> Subversion Design.
>
> Of course not all of them are read detailedly. Now would you like to
> give me some advice before I start my work on 23 May?
You should definitely read the Hacker's Guide to Subversion.
I read it, too, when I started. HACKING (we call the guide HACKING)
suggests to read some header files:
http://subversion.tigris.org/hacking.html#code-to-read
Reading the header files helped me a lot when I started looking at
Subversion's code.
The header files may not be easy to read at first, but if you don't
understand something, just ignore it and try to read on, and go back
to what you didn't understand later. The more little details you pick
up from every header file, the easier it will be to read all of them.
Of course, if you really don't understand something, just ask.
It's very important that you understand these header files.
Beside from learning about the code, you will also learn how we write
documentation for our code. You will need to document your code like
this, too. So this is another good reason for reading the header files.
> I have tried to use 'irc.freenode.net (channel #svn)' but could not
> connent to the server and I do not why. The client I use is mIRC.
The channel for developers is #svn-dev, not #svn.
But it is strange that you cannot connect to freenode.
Note that there is not just one IP address behind "irc.freenode.net".
There are many:
$ host irc.freenode.net
irc.freenode.net is an alias for chat.freenode.net.
chat.freenode.net has address 213.232.93.3
chat.freenode.net has address 213.219.249.66
chat.freenode.net has address 140.211.166.4
chat.freenode.net has address 89.16.176.16
chat.freenode.net has address 140.211.166.3
chat.freenode.net has address 154.35.200.44
chat.freenode.net has address 207.158.1.150
chat.freenode.net has address 216.155.130.130
chat.freenode.net has address 213.161.196.11
chat.freenode.net has address 92.61.33.10
chat.freenode.net has address 207.182.240.74
chat.freenode.net has address 212.117.163.190
chat.freenode.net has address 216.165.191.52
chat.freenode.net has address 86.65.39.15
chat.freenode.net has address 91.199.167.22
If your client cannot connect, just try to connect again. Maybe one
of the servers was down and you were trying to connect to that one.
Or, if you cannot connect even if you try multiple times, try using
a few of the IP addresses listed above instead of "irc.freenode.net"
If you still can't connect, let me know and I will set up a proxy for
you that you can use to connect to freenode.
> I do
> not know how to connect with you, so I send this email to
> 'dev_at_subversion.tigris.org ' and [1]'soc_at_subversion.tigris.org'. Hope
> for you reply!
You can look up my email address in the COMMITTERS file in the
Subversion source tree. You can also look up Hyrum's and Stephen's
addresses in that file. And once you can connect to freenode, just
try to find one of us in #svn-dev.
But note that for email, dev_at_subversion.tigris.org is usually the right
address to use. Unless you think the email you send must be kept private,
you should send your email to dev@.
Because when we talk on dev@, everyone else here can follow what we are
discussing, and give their opinions about it. This is very important.
That's why I put dev@ into Cc of this mail, too.
See you,
Stefan
Received on 2009-04-25 13:38:22 CEST