Welcome to MSDN Blogs Sign in | Join | Help

Should we keep the MSDN Wiki on WDK doc pages?

If you view WDK docs on MSDN, you probably know that a Wiki feature is available at the bottom of each WDK doc page. This MSDN-provided feature, under the green “Community Content” heading, is meant to encourage MSDN readership to post added value to any MSDN topic.

 

We enabled this Wiki feature in the WDK docs on MSDN about a year and a half ago. Frankly, at this point we’re questioning the value of this feature to our driver developer audience. So, we’d like your feedback.

 

Here’s the issue. In theory, MSDN community content is supposed to be a tool by which our customers can add value to our documentation. If you click on the little question mark next to the green “Community Content” heading, you’ll get a pop-up that cites “code samples, tips, undocumented scenarios, links to additional resources” as likely types of contributions.

 

In reality, what do the community content posts in the WDK docs consist of?  In January of 2009, 18 new wiki entries were created:

 ·         Two identified possible doc errors. We opened doc bugs to track these. I’ll leave these comments in place until the docs are fixed, even though wiki guidelines explicitly tell customers that the wiki is not meant for bug reports.

·         Four contained managed signatures that one person provided for structures that CDROM storage drivers use when receiving IOCTLs. Here’s an example: http://msdn.microsoft.com/en-us/library/ms808137.aspx. I left those in place, assuming someone might conceivably write a managed app that sends IOCTLs to a CDROM.

·         Six were questions from Windows users (such as “my Drive Ethernet Adapter is not korect is A SiS 9 -- is not prebaring in windows drive so i cannot working with it”) I deleted those because the WDK doc team does not have the resources or mandate to provide free user assistance to the non-driver-development Windows user community.

·         Three contained nonsense, which I deleted.

·         One contained just a long list of bugcheck codes. I deleted this.

·         Two contained entries in a foreign language that I was unable to translate. I deleted these.

 

January was a pretty typical month.  Based on this information, and your own observation of wiki posting in the WDK docs, do you think that wiki posts are adding value to driver developers?

 

Tell us what you think.  

  • Do you think the WDK doc wiki is useful to the driver writing community?
  • Are there ways in which we could make the wiki more useful?
  • Should we get rid of the wiki, or should we keep it?

You can answer these questions by adding a comment to this blog post or by sending us an email at ddksurv1@microsoft.com.

 

Please know that we definitely want to receive feedback about our documentation from the driver development community. We want to know about documentation errors and holes.  The best ways to send us feedback include:

  • The  “Send Feedback” link at the bottom of each doc topic in downloadable docs (not on MSDN).  
  • The “Rate and Give Feedback” link at the top of each MSDN page.

If your answers to the three questions above indicate that you’d like us to continue to provide the WDK doc wiki, we will do so.

 

 — Richard Brown [MSFT], Senior Programming Writer

Published Thursday, February 12, 2009 4:55 PM by wdkblog
Filed under: ,

Comment Notification

If you would like to receive an email when updates are made to this post, please register here

Subscribe to this post's comments using RSS

Comments

Thursday, February 12, 2009 4:22 PM by Don Burn

# re: Should we keep the MSDN Wiki on WDK doc pages?

None of the proffesional driver writers I know use the online version of the doc's for anything except for pointing to when answering questions on the forums.   Because of this the quality you are bound to get is, exactly like what you report.   I don't see how a wiki can be made to work without experts to help the content.

Monday, February 16, 2009 9:00 PM by ddebug

# re: Should we keep the MSDN Wiki on WDK doc pages?

This is a hard question. What is tha "community content" in the wiki? It could be links to various articles and example project on MVP sites, CodeProject, etc.  But this stuff is hard to review and moderate.

Tuesday, February 17, 2009 6:28 PM by Joe Dietz

# re: Should we keep the MSDN Wiki on WDK doc pages?

I despise wiki.  Wiki is the ultimate in disorganized chaos that is democracy.  I prefer the senatorial style of 'democracy' that arises from list-servs, if you ask a dumb question, you'll know it and everybody else will know it.  if you ask an insightful question and get an insightful answer the (branded) search engine of your choice can find it faster than any form of wiki-search.

Not to mention that the general view of the community is that any second spent by the WDK documentation team on anything that isn't actually documentation is at least a second lost to our collective productivity, which if your counting is quite expensive when its all added up.

Can it.

Wednesday, February 18, 2009 7:43 AM by ddebug

# re: Should we keep the MSDN Wiki on WDK doc pages?

to Joe Dietz: I respectfully disagree with your opinion on wikis in general. Most of non-controversal wiki pages contain either useful information, or links to useful resources, or at least, give a clue on what to google for.

Of course, the main body of WDK docum (including design guides and roadmaps) is far better and more useful than any wiki. But it still isn't perfect - take for example the indexing issue. And the community definitely has useful resources. Mostly these are sample projects, including fixed or improved versions of WDK samples, build tools - OSR, Hollistech,  ndis.com, wd-3 (abandoned?),  lvr.com to name some.

The question IMHO is, should this be integrated or linked into WDK, or developers should just use web search or well known forums/lists to find these resources. If wiki is not the optimal

way to integrate these resources, we could think of other ways.

Tuesday, March 24, 2009 11:57 AM by Martin O'Brien

# re: Should we keep the MSDN Wiki on WDK doc pages?

In my personal opinion, we need non-authoritative kernel documentation like we need to be remanded to a federal penitentiary.  While there will no doubt be content of value in some cases, a reference manual is supposed to be like a bible of sorts - one true source.

Friday, August 28, 2009 5:10 PM by Chad

# re: Should we keep the MSDN Wiki on WDK doc pages?

I have no idea how old this post is. Dating blog entries is important. So I am here because I am trying to develop an app using .NET 3.5. I am stunned how terrible the documentation on MSDN is. What's the point of just listing Namespaces and methods with no explanation of use or parameters? How anyone develops for the Microsoft platform at all is a mystery to me. MSDN just looks like a colossal waste of bandwidth and developer's time to me. Maybe the wiki was bad, but I doubt it was worse than nothing.

Leave a Comment

(required) 
required 
(required) 

  
Enter Code Here: Required
 
Page view tracker