Darren Reed writes: > I'd like to see a project plan that covers more than just a single > document. This looks like an ongoing project but the current > scope doesn't reflect that and nor does it extend its vision > beyond just a single task.
This is the first document. It's an itch that needs to be scratched. Other likely documents include the long-sought Fireengine detailed design, and perhaps one about sockfs. Heck, there even could be an iphooks user document here. > I find it very hard to believe that > there is only demand for a single document about Solaris > Networking Architecture/design/code - and even then only > a single interface. I doubt there is demand for just one document; it's likely many more. That's why this is chartered as a project with a repository: it gives us a stable place to put these documents. For what it's worth, it's modeled after the existing SMF documentation project: for exactly the same reasons. > Solaris Networking *needs* more commitment to this than just > a single document and if that isn't forthcoming, I'm prepared to > give this a -1 until someone comes up with a schedule that shows > some more thought has gone into what is needed here than just > a reaction to some internal emails about GLDv3. It sounds like you're saying that we aren't allowed to get started on our long-awaited detailed documentation simply because we're not proposing to document the world from the get-go. I'd rather see us start _somewhere_ useful than sit on our hands waiting for a high level description of the possible things we might do in the future. -- 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]
