If I want to propose a change to a Confluence page, what is a good way to collaborate on the proposed change?
There are several things that I see people doing on our company's wiki site now, including:
Is there any better way to do this?
For source code, we propose changes by using Gerrit. This allows a proposed change to be reviewed before it goes in easily, but I don't think Confluence has anything like this (it would be pretty snazzy if Confluence was backed by git and the repository could be checked out).
Any thoughts on better methods to do this?
The wiki-purist in me says you've misunderstood what a wiki is for. Most of the Confluence users I know simply dive in and make the changes they think they need. If someone else disagrees, that sparks a (non-Confluence) conversation about why it's wrong.
Oh, I know - the open approach can lead to wiki-tennis with pages being "corrected" backwards and forwards instead of people actually talking, but I've found trying to enforce an authorisation process on a wiki just tells me our collaberators, well, aren't collaberating.
I'd try to handle that with a light touch to begin with - ring-fence the pages/space you're worried about and tell the people who want to make changes to talk to each other. In this case, the pages really should follow your process or procedure and it's absolutely wrong for someone who is trying to change the business process to try to do it by editing the wiki. Get them to talk to the process owner - a restricted-edit page/space, combined with open comments are a good start on that, but also educating your users to get in touch if they think something is wrong is the core of collaberation.
The cases that have happened recently are when someone wants to make a change to a process or procedure. This change may either be extensive, and they need input on their changes, or they dont have permission to edit the page and want to show what they are meaning to change.
That isn't really the standard intent of a wiki, but I don't think it is an inappropriate use.
I don't know exactly the nature of the documentation, but I have imagined something like this:
I have really bad experience with track changes in Word, especially when you have to merge comments from several colleagues who have been working on their own. Using comments is nice, because the feedback is instantly available.
Badges are a great way to show off community activity, whether you’re a newbie or a Champion.Learn more
An efficient enterprise content management system, or ECM, is a must-have for companies that create work online (cough cough, all companies). If content calendars, marketing plans, and bu...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs