Peter Memishian writes: > > > > Well, the Clearview IPMP component is long-since delivered, but I have > > > still been regularly updating the OpenSolaris project page with links to > > > TOIs and other materials that I have authored much more recently. Having > > > all of this stuff together in one place for a project rather than smeared > > > through a variety of internal and external repositories strikes me as > > > quite useful. I think as long as things are properly dated and context > is > > > provided, having project pages remain after delivery has value. > > > > Clearview wasn't on the lists I mentioned. > > I know it wasn't, but in the not-too-distant future I'd assume it would > be, and I'd see that as a shame because it centralizes lot of valuable > project information (even from a historical perspective). Further, my > comment is more general: one reasonable use of a project page is as a > central repository for project-related information. This information > remains useful well after integration.
I think a better long-term story is to have a documentation repository where we can place -- and update -- system design information for future people who have to maintain this stuff. Scattering it on obliquely named project pages (how far can I see on a "Clearview"? and are avian carriers involved in "Volo"?) doesn't help organize or explain anything. Projects make sense to me while they're going enterprises and still doing useful work. I'm much less convinced that they're of lasting value historically. But even where they do have useful information, we still need to avoid having it just pile up in the middle of the road where it's at least slowing traffic, if not yet causing accidents. -- James Carlson, Solaris Networking <[email protected]> Sun Microsystems / 35 Network Drive 71.232W Vox +1 781 442 2084 MS UBUR02-212 / Burlington MA 01803-2757 42.496N Fax +1 781 442 1677 _______________________________________________ networking-discuss mailing list [email protected]
