AnnualCommunityReview2007FridayNotes
Simon
I had a skype call with Ward, Mark, and Spark, here are some of the thoughts I was having afterwards.
- Ward talked about the vision of aboutus and maybe being the wiki SecondLife for corporations. Well I just don't know how that would work, SecondLife fills more of a company to users field or an internal chat room collaboration. We can maybe do the first one; but, the second one can really only be done on a corporate wiki. Too much talk that isn't suppose to be repeated and/or can't be controlled is on there. Can AboutUs be build to have that sort of community interactions with the page? The Wiki way as I sort of see it is nobody owns any sort of area, well that wouldn't quite work out for corporations and isn't how it works in SecondLife. I help build corporate wikis and also help with making internet policies on editing Wikipedia and other wikis. AboutUs isn't allowed in most of those cases. --Simon | talk 10:57, 24 August 2007 (PDT)
Ward
- Good points. The issue you bring up isn't about the graphics, but about the ownership and confidentiality, much more important ideas when we are talking about how people work together. Here is a test case. Imagine that an organization wanted to collaborate within themselves on a press release. This would then be released to the community through AboutUs where healthy collaboration ensues. Would it matter that some privacy were afforded the organization while it got its own thoughts together? Is this in contradiction to the "free and open" that was mentioned several times on the call? Or is that open a different concept from privacy. I would be inclined to call a wiki open if everyone who could read it was also welcome to write it. -- Ward 12:54, 24 August 2007 (PDT)
- Very good point a wiki can still be open if its only people that can see it are staff. The bigges problem with corporate wikis is having everybody involved. Why when you have a corporate wiki would you bring it to AboutUs? --Simon | talk 15:18, 24 August 2007 (PDT)
- In the example I gave (the press release) the content was to be eventually made public so I am presuming that it would be convenient to develop it in its eventual place.