Everyone here knows the benefits of wiki. When a "trust but verify" approach is applied, the return from allowing open edits far outweighs the risk of mis-information.
But what about in a controlled orginization? Where there is desire to use a wiki but policy or procedures prevent it. Perhaps a simple module can go a long way to address the situation. The hypothetical module gives users the option to view the revisions last edited by AuthorizedGroup or the "wild revision" (edits by users not in that group). Pages would default to the authorized revision if that is newer than the wild type but there would be an indication on the authorized page if a newer wild revision where available. The biggest problem I see with this is broken links or inappropriate references due to mis-qualified page links. But the more I imagine the implementation the less I think this would be an actual problem? Thoughts? Would this be easy or difficult to implement? I'm happy to post this in the wiki feature request, if people think it's a worthwhile feature. -George ------------------------------------------------------------------------------ Increase Visibility of Your 3D Game App & Earn a Chance To Win $500! Tap into the largest installed PC base & get more eyes on your game by optimizing for Intel(R) Graphics Technology. Get started today with the Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs. http://p.sf.net/sfu/intelisp-dev2dev _______________________________________________ Moin-user mailing list Moin-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/moin-user
