Absolutely! I will send along updated docs.



-- Sent from my Palm Pre
On Mar 25, 2013 11:41 AM, Phil Haack &lt;notifications@github.com&gt; wrote: 

&gt; @@ -3,12 +3,20 @@

&gt;  ## Introduction

&gt;  

&gt;  Apart from building library/content packages and publishing them to [NuGet.org](http://nuget.org),

&gt; -NuGet also supports creating symbol/source packages and publishing them to [SymbolSource.org](http://symbolsource.org).

&gt; +NuGet also supports creating symbol/source packages and publishing them to either [SymbolSource.org](http://symbolsource.org) 

&gt; +or to an [internal internal symbol/source server][http://inedo.com/support/documentation/proget/feeds/symbol-and-source-server]. 



Thanks for the doc contributions! I'm a little concerned about listing Inedo and TFS symbol servers here in _this_ doc. If we start listing all the possible symbol servers here, this doc will grow unwieldy and I'd like to not set that precedent.



What might be more useful is to state something like: "publishing them to the default public NuGet symbol server, SymbolSource.org, or to one of the private ones listed on our symbol server list."



And "symbol server list" would be a separate document that lists alternative symbol servers with brief instructions for each one and a link to more extensive documentation. I think that'd be really cool. Would you be interested in helping us make that change?



We really do appreciate the help!



---

Reply to this email directly or view it on GitHub:

https://github.com/NuGet/NuGetDocs/pull/72/files#r3514240