<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>Community and Developers</title><link>http://blogs.msdn.com/jerbos/archive/2003/12/26/46006.aspx</link><description>What is the ultimate community experience for developers? I am a program manager at Microsoft that works on helping developers find interesting ways to help the community and make developers more successful. This is an exciting opportunity to start a</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: Community and Developers</title><link>http://blogs.msdn.com/jerbos/archive/2003/12/26/46006.aspx#46020</link><pubDate>Fri, 26 Dec 2003 22:02:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:46020</guid><dc:creator>denny</dc:creator><description>&amp;quot; how do you find all the answers from various resources? &amp;quot; a lot of Google ...&lt;br&gt;PS:  msdn search is often no help, serching the KB is better than searching MSDN for some stuff.&lt;br&gt;&lt;br&gt;I use GDN and CodeProject a *LOT* to find stuff.&lt;br&gt;I like the MSDN TV and .Net SHow -- watch them almost as soon as they show up.&lt;br&gt;&lt;br&gt;seems like I have found that there are folks who find a .Net or a VS.NEt problem who will not go to MS PSS and report it. perhaps a &amp;quot;Report the bugs&amp;quot; site might be of use??&lt;br&gt;&lt;br&gt;there have been a few times where I had other make these comments:&lt;br&gt;&lt;br&gt;1) microsoft is not responding to my bug.&lt;br&gt;2) submiting the problem is to hard.&lt;br&gt;3) I submited the problem and got no follow up last time so I'm not going to waste my time now.&lt;br&gt;&lt;br&gt;so I would say that we have a start on GDN and here of a trend for coders like me to get one step &amp;quot;closer&amp;quot; to interacting with MS folks about problems.... If we can in some form take that a step further??&lt;br&gt;&lt;br&gt;for example:  I posted on GDN about writing a VS.NET addin to help with debuging Win32 Services from VS. An MS staffer liked what I did and asked me if I was doing a Workspace.&lt;br&gt;I did and have not heard back from anyone...&lt;br&gt;I posted some IMHO good questions related to addin development... I still don't have any answers.... &lt;br&gt;if posts like that got read and MS could post good MSDN / KB bits and link them to the place they were asked like GDN then other folks would find them faster.&lt;br&gt;&lt;br&gt;well Just an idea or two....&lt;br&gt;</description></item><item><title>re: Community and Developers</title><link>http://blogs.msdn.com/jerbos/archive/2003/12/26/46006.aspx#46024</link><pubDate>Fri, 26 Dec 2003 22:26:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:46024</guid><dc:creator>Jan Tielens</dc:creator><description>Hi Jeremy&lt;br&gt;&lt;br&gt;I'm quite active in the .NET community (MSDN Belux site (www.msdn.be), my blog, Belgian .NET UG (www.benug.be), MSDN Newsgroups, ...), it's great that you are asking the question, because in my opinion some things can be organized a little bit better.&lt;br&gt;&lt;br&gt;When you have a question, the first thing that you do is search MSDN and/or use Google. Google is great because it indexes newsgroups too, MSDN doesn't, plus Google indexes local Microsoft sites with sometimes quite intresting articles (e.g. www.microsoft.com/belux/nl/msdn/community/articles.mspx). So how can Microsoft make improvements for searching: add (MS)newsgroups searching and add local MS content indexing. Ofcourse there are other great resources like weblogs, 3rd party sites, ... but these do not belong in the MSDN search I think.&lt;br&gt;&lt;br&gt;If you haven't found an answer to your question yet, you'll probably want to post your question somewhere. My biggest concern is that there are so many places to do this: MSDN Newsgroups, GotDotNet Forums, ASP.NET Forums, WindowsForms.NET Forums, ... So the question becomes: where to post my stuff? Additionally some forums are overlapping: e.g. webservices belong to the ASP.NET Forums, but also to the WindowsForms.NET Forums. In my opinion the ideal world would be one gigantic system (e.g. MSDN Newsgroups), other sites could expose forums that are parts of these newsgroups. For example if you would post a question in the ASP.NET Forums, it would automatically be available on the MSDN Newsgroups and GotDotNet Forums. This would have 2 advantages: 1) higher chance that someone answers the question 2) people who answer questions don't have to monitor 5 different places.&lt;br&gt;&lt;br&gt;Another part of the community in which MS has a role are the articles, webcasts, shows, ... MSDN has plenty of good articles, so I don't see a problem there. Webcasts are a great way to deliver information, I love them! My only request is to make them available offline. Recently MS switched from Interwise software to Livemeeting, so at this point the only possibility is to watch the webcasts online. The ideal world would be that the webcasts would be available to download, not only to desktop pc's, but also to mobile devices (see my post weblogs.asp.net/jan/archive/2003/11/07/36354.aspx). Shows like MSDN TV, the .NET Show and .NET Rocks are great too, although it would be nice to see a higher frequency!&lt;br&gt;&lt;br&gt;So these are my thoughts about the Microsoft Community. Thanks for asking this question and I hope you'll be able to make this community even greater!&lt;br&gt;&lt;br&gt;Jan</description></item><item><title>re: Community and Developers</title><link>http://blogs.msdn.com/jerbos/archive/2003/12/26/46006.aspx#46087</link><pubDate>Sat, 27 Dec 2003 07:53:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:46087</guid><dc:creator>Phil Weber</dc:creator><description>Hi, Jeremy: If the answer exists on the 'net, I can find it in 10 minutes or less using Google. :-)</description></item><item><title>re: Community and Developers</title><link>http://blogs.msdn.com/jerbos/archive/2003/12/26/46006.aspx#46093</link><pubDate>Sat, 27 Dec 2003 09:06:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:46093</guid><dc:creator>Shannon J Hager</dc:creator><description>First off, if MS really wanted to help, they would use Google for searching the MSDN site.  Seriously.&lt;br&gt;As far as the commnuity section, I would like to see something like codejack/artifact (www.codejack.com), or CodeLib, but have it more free/web-based.  Aaron Bertrand's ASP site was/is an outstanding example of a great code library, but it wasn't a community, so to speak.  Something like that, a real code library or code knowledge base would be immensely helpful.  Newsgroups and forums rarely help me as much as a google search does, even though the google result that helps me may point to a forum post at a site I am a member of.  Newsgroups have too much noise, trolling, and attacks for me to even bother posting.  &lt;br&gt;But the stars do shine through and are recognized, the MVP program is a definite plus.</description></item><item><title>re: Community and Developers</title><link>http://blogs.msdn.com/jerbos/archive/2003/12/26/46006.aspx#46107</link><pubDate>Sat, 27 Dec 2003 15:08:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:46107</guid><dc:creator>denny</dc:creator><description>also the local / regional MS stuff is very good. I am working on going to the local stuff as often as I can.  a small'ish presentation with lots of time for the audience to ask questions is a good way to help us all meet and share. Russ just moved from north east to gulf states, he is a good example, we spent an afternoon at a theater in Largo FL and it was like a SIG meeting in many ways....&lt;br&gt;&lt;br&gt;I may not have the time or the cash for a &amp;quot;PDC&amp;quot; but I can find the time to go to a 3-6 hour session acros town. and the cost is almost none.&lt;br&gt;&lt;br&gt;I know this would be hard... but just as an idea:&lt;br&gt;&lt;br&gt;take the PDC / big events and have them at say 3-4 sites at the same time, hook the up via satalite to share some of the presentationts and keynotes.  then the local  and regional MS teams can stay with the loacl attendees. more developers can go and have less travel time and costs. each location could have sessions presented by the local MS teams -- same sessions at each site done localy.&lt;br&gt;&lt;br&gt;some costs would be high, but I bet it would work out in the end, a larger event by at least 3-4 times.... but each location having a more &amp;quot;Home town&amp;quot; feel.&lt;br&gt;&lt;br&gt;just another idea...&lt;br&gt;</description></item><item><title>re: Community and Developers</title><link>http://blogs.msdn.com/jerbos/archive/2003/12/26/46006.aspx#46108</link><pubDate>Sat, 27 Dec 2003 15:11:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:46108</guid><dc:creator>Simon Stewart</dc:creator><description>&amp;quot;What is the ultimate community experience for developers&amp;quot;&lt;br&gt;*peer-to-peer.  Where the aim is to share information without pushing product!&lt;br&gt;Preferrably some kind of regular meeting.&lt;br&gt;&lt;br&gt;Some of the things I would like to see / am trying to include in our user group:&lt;br&gt; CD of .NET shows, MSDN TV, etc ... (download time is a deterrant)&lt;br&gt; increase awareness of PSS and the importance of *actually* logging bugs&lt;br&gt; increase awareness of local user groups to the MS Partners locally.&lt;br&gt;&lt;br&gt;&lt;br&gt;&amp;quot;how do you find all the answers from various resources? &amp;quot;&lt;br&gt;Google / Codeproject.&lt;br&gt;Quite often, searching leads to blogs.  Especially over the past few months.&lt;br&gt;I use MSDN more for a API/usage reference, but look forward to the next version where blogs/developer posts will be included (from what I saw at PDC)&lt;br&gt;&lt;br&gt;&lt;br&gt;&amp;quot;How do you research and store that information for a later date?&amp;quot;&lt;br&gt;Normally re-search for it using Google or check offline newsgroups/list server posts.&lt;br&gt;&lt;br&gt;Great topic to start off your blog, btw Jeremy.</description></item><item><title>re: Community and Developers</title><link>http://blogs.msdn.com/jerbos/archive/2003/12/26/46006.aspx#46109</link><pubDate>Sat, 27 Dec 2003 16:06:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:46109</guid><dc:creator>Paul Laudeman</dc:creator><description>From my perspective, the biggest challenge is finding the information that is out there (like others have mentioned). I always turn to Google first, usually by using it to search the newsgroups first like so:&lt;br&gt;&lt;br&gt;&amp;quot;my query&amp;quot; group:microsoft.public.dotnet.*&lt;br&gt;&lt;br&gt;or by using the Google search engine and taking a look at what the Microsoft sites have to offer first:&lt;br&gt;&lt;br&gt;&amp;quot;my query&amp;quot; site:microsoft.com (or site:msdn.microsoft.com, etc.)&lt;br&gt;&lt;br&gt;and then doing a more generalized web search if none of those fail to produce any relevant hits. &lt;br&gt;&lt;br&gt;Beyond that, I'll check the other developer groups such as DevelopMentor (discuss.develop.com) and the ASP.NET and Windows Forms.NET forums.&lt;br&gt;&lt;br&gt;The biggest challenge, as you might be getting a sense of, is the sheer number of sites that I have to search and browse to find what I'm looking for. If you could somehow build a single meta-search entry point into all of your resources (with the effectiveness of Google), that'd be a great start. Also, the addition of RSS feeds to almost all of the Microsoft sites has been a *great* addition.&lt;br&gt;&lt;br&gt;Additionally, it would certainly help to have some sort of way to check Microsoft's internal bug reporting system to see if a bug has been reported before and, if so, what the fix was. You can do this by searching the KB articles, but this only reports on bugs that have fixes, workarounds, or noted to be fixed in a future release. It would also be helpful to see that bugs have at least been logged into your systems to be looked at, if nothing else. Easier bug reporting would also need to be implemented.&lt;br&gt;&lt;br&gt;Also, and finally, in conversations that I have seen in the newsgroups and forums, I have noticed that there are occasions where a Microsoft employee will respond to a request for help, but not really be around to follow it through to the end to make sure the problem was resolved. &lt;br&gt;&lt;br&gt;Lastly, nomiate more MVP's with specific coverage areas (e.g. ASP.NET, Winforms, etc.) to help you out in all the ways suggested above!</description></item><item><title>re: Community and Developers</title><link>http://blogs.msdn.com/jerbos/archive/2003/12/26/46006.aspx#46141</link><pubDate>Sun, 28 Dec 2003 01:45:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:46141</guid><dc:creator>Ken Cox [MVP - ASP.NET]</dc:creator><description>Hi Jeremy,&lt;br&gt;&lt;br&gt;&amp;gt;how do you find all the answers from various resources?&lt;br&gt;&lt;br&gt;A Google search (web and newsgroup) is almost certain to turn up a lead. Microsoft's search has improved, but it has a long way to go. &lt;br&gt;&lt;br&gt;It would be nice if Microsoft provided a dedicated search page that focuses exclusively on its own newsgroups. These are an incredible resource for past answers. Why go out to Google for that?&lt;br&gt;&lt;br&gt;&amp;gt;How do you research and store that information for a later date?&lt;br&gt;&lt;br&gt;For newsgroup messages, I have a &amp;quot;NetAnswers&amp;quot; folder in Outlook Express where I copy any message that strikes me as valuable. I can do a very quick search there.&lt;br&gt;&lt;br&gt;I also keep a Web application on my server that contains the working examples that I've posted or plucked. Because I have a poor memory for syntax, it helps to be able to pull them out.&lt;br&gt;&lt;br&gt;&amp;gt;I hope to hear from you about what you like and dislike about community and what you would like to see more of the community.&lt;br&gt;&lt;br&gt;For me, MS should boost resources in peer-to-peer newsgroups because, unlike bugs, most specific issues can't be handled by an article on a static Web site. By posting troublesome code in a newsgroup, you get hundreds of extra eyes to catch that silly error you lost a morning on. In fact, many questions in the newsgroups come from people who are bumping against code in tutorials or books.&lt;br&gt;&lt;br&gt;I think MS could do more to make sure code in published articles is ported to VB. It seems like very advanced developers are more comfortable in C#, so that's the language of their samples. Trouble is, the people who need to learn their techniques are probably less advanced in C# and would find it easier to follow code in VB.&lt;br&gt;&lt;br&gt;I'd like to see NNTP protocols and Outlook Express support a way to alert posters that someone has replied. I know this is done in www.asp.net forums over HTTP. No idea whether it is feasible in newsgroups.&lt;br&gt;&lt;br&gt;It annoys me when viruses, porn, spam and advertisements invade the newsgroups because, unlike ASP.NET forums, there's no moderation. Removing the litter quickly - especially on weekends - is important to maintaining a healthy, cooperative, non-commercial atmosphere in the newsgroup community.&lt;br&gt;&lt;br&gt;Thanks for listening Jeremy, and keep up the good work!&lt;br&gt;&lt;br&gt;&lt;br&gt;</description></item><item><title>Community Profiles</title><link>http://blogs.msdn.com/jerbos/archive/2003/12/26/46006.aspx#46505</link><pubDate>Tue, 30 Dec 2003 03:40:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:46505</guid><dc:creator>Jeremy Bostron's Blog</dc:creator><description /></item><item><title>re: Community and Developers</title><link>http://blogs.msdn.com/jerbos/archive/2003/12/26/46006.aspx#81711</link><pubDate>Sun, 29 Feb 2004 11:42:00 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:81711</guid><dc:creator>Homeless</dc:creator><description>why are asp.net forums not convenient to ya as a community?..</description></item><item><title> Jeremy Bostron s Blog Community and Developers | Wood TV Stand</title><link>http://blogs.msdn.com/jerbos/archive/2003/12/26/46006.aspx#9673102</link><pubDate>Mon, 01 Jun 2009 02:48:14 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9673102</guid><dc:creator> Jeremy Bostron s Blog Community and Developers | Wood TV Stand</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://woodtvstand.info/story.php?id=6035"&gt;http://woodtvstand.info/story.php?id=6035&lt;/a&gt;&lt;/p&gt;
</description></item><item><title> Jeremy Bostron s Blog Community and Developers | Weak Bladder</title><link>http://blogs.msdn.com/jerbos/archive/2003/12/26/46006.aspx#9706011</link><pubDate>Mon, 08 Jun 2009 04:52:19 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9706011</guid><dc:creator> Jeremy Bostron s Blog Community and Developers | Weak Bladder</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://weakbladder.info/story.php?id=1280"&gt;http://weakbladder.info/story.php?id=1280&lt;/a&gt;&lt;/p&gt;
</description></item><item><title> Jeremy Bostron s Blog Community and Developers | Cellulite Creams</title><link>http://blogs.msdn.com/jerbos/archive/2003/12/26/46006.aspx#9711746</link><pubDate>Tue, 09 Jun 2009 05:41:13 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9711746</guid><dc:creator> Jeremy Bostron s Blog Community and Developers | Cellulite Creams</dc:creator><description>&lt;p&gt;PingBack from &lt;a rel="nofollow" target="_new" href="http://cellulitecreamsite.info/story.php?id=52"&gt;http://cellulitecreamsite.info/story.php?id=52&lt;/a&gt;&lt;/p&gt;
</description></item></channel></rss>