http://huddledmasses.org/redefining-community/ You can do more than breathe for free... Tue, 02 Dec 2008 09:27:11 +0000 http://wordpress.org/?v=2.7-beta3 hourly 1 http://huddledmasses.org/redefining-community/comment-page-1/#comment-121257 Karl Prosser Mon, 29 Oct 2007 00:45:08 +0000 http://HuddledMasses.org/redefining-community/#comment-121257 Shell Tools has also said it was transforming powershell live into a customer support area. And a number of forums have been locked, some others deleted and some put in an obsolete group. On one sense it is sad to us, the death of a dream, but on another sense its a relief as we just didn't have the resources to develop it to the level we'd want. With PowershellCommunity.org we have the resources to give it a good go IMO, even though i'm sure there is much tweaking needed along the way. Shell Tools has also said it was transforming powershell live into a customer support area. And a number of forums have been locked, some others deleted and some put in an obsolete group. On one sense it is sad to us, the death of a dream, but on another sense its a relief as we just didn’t have the resources to develop it to the level we’d want. With PowershellCommunity.org we have the resources to give it a good go IMO, even though i’m sure there is much tweaking needed along the way.

]]> http://huddledmasses.org/redefining-community/comment-page-1/#comment-121188 Don Jones Sun, 28 Oct 2007 17:59:09 +0000 http://HuddledMasses.org/redefining-community/#comment-121188 It's unfortunate that you didn't feel comfortable contacting me directly to obtain answers to some of the questions you raise here, or that you didn't feel comfortable making suggestions about the community either in our forums or directly to me. We're all quite happy to act upon reasonable suggestions, and we've tried to be clear that the community is still in "soft open" and is being adjusted. In fact, this weekend has seen a major set of adjustments finally made live after significant development. It's honestly tough to try and do something valuable for the PowerShell user community and then have it attacked rather viciously without any kind of chance to explain, to follow-up, or to accept constructive criticism. I hope in the future you'll feel that you can participate by offering actionable suggestions and perhaps even helping out - you're certainly welcome. You've made comments here which I'll choose to interpret as questions, and I'll try to answer them in my own blog entry this week - but you're more than welcome to follow-up directly; I certainly don't mean to start some intra-blog flame war and will try to take some pains so that my response doesn't come across that way. It’s unfortunate that you didn’t feel comfortable contacting me directly to obtain answers to some of the questions you raise here, or that you didn’t feel comfortable making suggestions about the community either in our forums or directly to me. We’re all quite happy to act upon reasonable suggestions, and we’ve tried to be clear that the community is still in “soft open” and is being adjusted. In fact, this weekend has seen a major set of adjustments finally made live after significant development. It’s honestly tough to try and do something valuable for the PowerShell user community and then have it attacked rather viciously without any kind of chance to explain, to follow-up, or to accept constructive criticism. I hope in the future you’ll feel that you can participate by offering actionable suggestions and perhaps even helping out – you’re certainly welcome. You’ve made comments here which I’ll choose to interpret as questions, and I’ll try to answer them in my own blog entry this week – but you’re more than welcome to follow-up directly; I certainly don’t mean to start some intra-blog flame war and will try to take some pains so that my response doesn’t come across that way.

]]>