* Ben Rockwood <benr at cuddletech.com> [2006-01-23 13:03]: > .... to ensure that that effort does not duplicate or conflict with > existing or future projects of this, the docs, community.
I think it's reasonable to comment that a particular project's aims might duplicate or conflict with a community's unidentified future projects, but those unidentified projects must be quickly identified. However, I don't believe any community can monitor "all things written", so I wonder what projects you might mean. (For instance, in such a scheme, any composition efforts the new SysAdmin community might pursue could be perceived as duplicative or in conflict.) Certainly the Documentation community can choose not to endorse the Articles project's work, but I am curious what more it should do. (In fact, I am wondering why any choice other than attempting to coopt them would seem attractive.) - Stephen -- Stephen Hahn, PhD Solaris Kernel Development, Sun Microsystems stephen.hahn at sun.com http://blogs.sun.com/sch/
