Date: Fri, 4 Jan 2002 17:50:46 -0500 (EST) From: "Andrew R. Reiter" <arr@FreeBSD.org> To: freebsd-smp@FreeBSD.org Subject: SMPng biweekly updates Message-ID: <Pine.NEB.3.96L.1020104172404.68524A-100000@fledge.watson.org>
next in thread | raw e-mail | index | archive | help
Some people on IRC today were mentioning that SMPng was taking a really long time to complete... and, in general, a bunch of people agreed, including myself. We all understand the difficulties of changing the standard design of a unix-like system to what the end goal is, so obviously it will take a long time and also since this is a volunteer project, no one is forced down to continue hacking on the same thing. I believe jhb@ mentioned that one problem is lack of person-power to do the code hacking (locking down shared data, discussing design issues without going off on a whole other tangent, etc)... and I'd agree (of course I am guilty of not particpating enough). I think one of the reasons for the lack of person-power is that there is not enough organized communication. We have a web page that gets randomly updated, mailing list archives which have some discussion (even tho much happens on IRC, and tons of these emails get lost in a haze of random tangents), and, if you're into it, IRC logs floating on the web. If those who would like to get involved with SMPng coding yet have not fully followed everything that's going on (since they can't -- p4 commits & irc discussion), they don't have anywhere to really go and read a fairly informative doc or snippet on what's happening now and what needs to happen. To cut myself short: I propose a biweekly mini-email that goes out to -smp that is essentially an outline of what's being done, what's being discussed, what needs to be done, and any design changes/thoughts. I'd like to think of it as a cvs log dump for the SMPng project for a two week period. Essentially someone would track the changes to the repo (p4 and cvs) and conversations that happen randomly (irc, private email, mailing lists) and generate this outline. I believe then that this would be an easy transition into generating a monthly status report that are accurate and are helpful to those who are not following -smp. Also, if we had had these, it would be an easy way for someone who worked on the project but went on vacation to come back and easily understand what has occured (or atleast allow for making it extremely easy to find out what's changed). I am volunteering to do this job... But, what Im interested in is seeing if those out there listening are interested in having this done... Cheers, Andrew -- Andrew R. Reiter arr@watson.org arr@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-smp" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?Pine.NEB.3.96L.1020104172404.68524A-100000>