SourceSafe Wiki

In modern usage, Wiki is used in three contexts that I know about:

  1. "Wiki Wiki Food" means Fast Food in Hawaii.
  2. A "WikiWiki Shuttle" is the Honolulu airport shuttle.
  3. A "Wiki" is a dynamically defined set of Web pages that anyone can access and edit.

The most famous online wiki is http://www.wikipedia.org, a collaborative encyclopedia.  Wikipedia and similar wikis have inspired us to start a wiki for Visual SourceSafe users and the VSS development team. Initially, I plan to populate the SourceSafe wiki with FAQs, answers to FAQs, and links to additional resources. I'm sure that it will soon outstrip its original purpose.

If it existed today, what would you use the SourceSafe Wiki for?

Este mensaje se proporciona "como está" sin garantías de ninguna clase, y no otorga ningún derecho.

Published 20 August 03 05:27 by KorbyP

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

# Jon Stonecash said on August 21, 2003 8:57 AM:
I would be looking for input on how to setup solutions for multiple team members that may not be physically co-located
# Alan Kleymeyer said on August 25, 2003 4:04 PM:
I would use it for Q & A.
# Simon Smith said on August 31, 2003 4:59 AM:
Is a Wiki really appropriate? Wiki's are generally fairly wide ranging unless edited ruthlessly (which makes them more or less equivalent to a Blog with commenting facilities :). See http://c2.com/cgi/wiki?DissertationOverDiscourse on the original Wiki site and wander through some of the linked pages for an idea of where a proper Wiki can end up. I'm not sure what I'd use a Wiki limited to VSS for; the idea just doesn't seem right somehow. Given groups.google.com, Usenet is more what I turn to when looking for something specific.( Usenet also has greater security in that posts are tamper-proof - something which a Wiki page by definition is not.) If you and others from the VSS team are active in a VSS newsgroup or blog(s) I think you'd get more value from them than from a Wiki, and with less administrative overhead. Sorry to sound negative. What would YOU want to get out of a VSS Wiki?
# Korby Parnell said on September 8, 2003 12:48 PM:
Thanks for the links and thoughts. Here's what I think: Like any large corporation, domain-specific knowledge is not always as centralized or accessible at Microsoft as it could or should be. Knowledge about VSS and source control in general is no exception. I imagine the [initially internal] VSS wiki as a central knowledge management workspace for all things VSS. The most obvious starting point is a product FAQ which would include both documented and undocumented answers to customer FAQs. You might ask, 'Wouldn't it be better to just use Microsoft SharePoint Team Services, which is basically a slick, productized version of a wiki?' And I would answer, 'Nope.' I believe that the open, unregulated, anything-goes nature of a wiki is the key to its potential as a knowledge management tool. Why? Because humans learn by organizing and reorganizing information. We take notes during lectures not because we intend to revisit our notes in the future but because reorganizing the information on the fly improves our ability to retain <i>and retrieve</i> that information. I'm anxious to see if the existence and use of a VSS wiki can improve my team's ability to answer previously asked customer questions more quickly and accurately.
# Korby Parnell said on September 11, 2003 7:10 PM:
Interesting tools for 'visualizing' collaborative documentation via a wiki at: http://researchweb.watson.ibm.com/history/explanation.htm. For the record, I'm using SharpWiki, which has been developed internally.
# DeanG said on October 24, 2003 1:08 AM:
What I would use it for... - A publicly annoted SourceSafe manual? You Bet! :-) - Finding Best Practices, warnings, and workarounds - Finding resources from many SourceSafe experts migrating there Favorites entries (and summaries) to the Wiki! - Reading development stories from authors and integrators through the ages Althogh sometimes disparate, Wiki's short page and simple topic view allow (like blogs) quickly digesting information in plain language.
# Chris S. said on March 24, 2004 5:55 AM:
Guess I'm a little late in responding to this, but I think a wiki dedicated to VSS would be great if its presence can be adequately conveyed to the larger community.

I have looked at usenet groups and the like, and what I have liked about the wiki architecture more is that there is less repetition of information. When new information comes in on a topic in a wiki, it can be added to the appropriate location and found much easier.

I, for one, prefer the consolidated approach over searching everywhere for obscure information relating to a problem I have. Plus, if I can't find information in a wiki that should be there, then if I do all the work to find it, I find it very simple to add that information in a wiki.

I have seen some entries in wiki's regarding vss, but they all seem rather small to me at the moment. I think having a wiki that is dedicated to vss, might actually be what is needed.

my $.02
# G-sus said on July 13, 2004 5:08 AM:
Implement the Wiki with VSS as back end and I would be interested in all technical details and work arounds!
# online basketball betting said on August 26, 2006 12:03 AM:
Thank you so much for this great post  about <a href="http://businessloannew.250free.com/online-basketball-betting.html"">http://businessloannew.250free.com/online-basketball-betting.html" title="online basketball betting">online basketball betting</a> and [URL=http://businessloannew.250free.com/online-basketball-betting.html]online basketball betting[/URL]

Leave a Comment

(required) 
(optional)
(required) 

Search

Go

This Blog

Syndication

Page view tracker