Member reply requested for 2008/772 Command Assistant

[James Carlson]

Christof Pintaske writes:
> A user can add to the repository by submitting the document to the 
> opensolaris documentation community and notifying us. The number of 
> submissions in that community is so low that I don't see that any 
> further automation is justified (so far we haven't seen any document 
> from the community that would be suitable).

That plainly doesn't work for third parties.  Why would (say) Oracle
choose to publish its user documentation under Sun's^WOpenSolaris's
licensing rules?

> I don't see any architectural constraints that would prohibit a future 
> closer community involvement. I would just like to postpone this 
> discussion until the community shows interest and tells us how they 
> would like to get involved.

The architectural issue is how the client finds the server (it's
hard-coded) and how the server indexes documents (it's closed).  There
are other high-level designs that could be chosen, so, although
there's an element of business issue here, there are still clearly
architectural issues as well.

In any event, this is far off topic here.  All that the project team
wanted out of this discussion was an indication of whether folks were
ready to vote based on the new materials, because they were eager to
avoid scheduling a normal review.  Please stop the debate here.

So far, we have Garrett saying NP and Sebastien saying "not ready."
Based on the latter, I think the way forward should be obvious, but if
the project team has specific other plans, then we can plow ahead
knowing the likely outcome.

-- 
James Carlson, Solaris Networking              <james.d.carlson at sun.com>
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