Any community has more than one throat to choke.

One of the biggest benefits with the OpenDS Wiki has been the high volume and high value of community contributions. Wiki technology makes it simple, almost tempting, for folks who know their subject matter to add good content. Perhaps because of the public nature of all edits, the signal to noise ratio stays high, too.

Download OpenDS

Even so, we want to put the quality bar for official documentation as high as for the code itself. That is why we apply a two-phase documentation review process, similar to a code review and testing process.

Will that ever be good enough? Maybe not.

When your operations depend on the reliability and availability of your directory service, you want one throat to choke, right? Any community has more than one throat to choke.

Our aim today is to continue with wikis as the community source of the latest and greatest documentation. We then expect to bring refined and validated content from that format into official product documentation. Finally, we plan to package that up in such a way that you know exactly whose throat you get to choke when you buy support.

If only the middle step were easier to automate. It would be nice to have an open source WikiText-to-OpenDocument-format conversion tool.

Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

Mark Craig writes about Directory Services products and technologies. The views expressed on this blog are my own and do not necessarily reflect the views of Oracle.

Search

Categories
Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today