|intro and question
||[Mar. 15th, 2003|11:40 am]
|||||Ella Fitzgerald - It's Wonderful||]|
Hi, all. As I haven't posted here before, a quick word of intro, but then we move quickly on to the meat of my post. I'm a B.Eng. (Electrical) currently working as a Research Assistant at McGill University. One of my main hats is coder, another main one is Lab Admin (make sure all the people in the lab have what they need to get the work done and that communication is flowing properly), and lesser hats (for now) are: idea-woman, documenter, and designer. I've years of experience coding in C/C/C++ (and my brain is suitably warped in response), and plunged into the deep end of Perl and Perl/Tk in January.
As far as contributing to LJ goes, I don't see being able to do much actual coding for now, as I'm pretty involved in work, and have other open source projects I'd like to accomplish before putting significant chunks of time into LJ. In the meantime, if there's a short enough fix that lies in areas I feel competent to handle, I'll definitely send in patches.
Now, on to the real purpose behind my posting here. I have skimmed the server documentation available through links, and haven't come across the answer to my questions.
- Are developers expected to set up their own LJ server, apply their changes there, and then send their patches in?
- Are developers expected to test their changes by playing around with their browser or with clients? Are there no test scripts which will simulate various user activities, preferably placed in a test harness?
( Read more...Collapse )