On Aug 24, 9:30 am, Ryan J Ollos <[email protected]> wrote: > > I can see this as being very valuable. My group has tried to use the wiki > for requirements and design docs, but an author typically ends up editing a > page for several hours at a time. It is quite frustrating to then go to save > the page and find that it can't be saved because someone else has performed > edits as well. Merging these edits can be a nightmare.
I agree, this process needs streamlining. The solution doesn't even have to include all the fancy-schmancy history playback and other advanced stuff of Etherpad or Wave, just a way to see who's working on a doc and join in whenever without disrupting each other. This does bring up a new level of issues to be handled, but I think they're all solvable with not too much effort. I have a lot on my plate already which is why I'm looking to to do collaboration first and solo running as further second. Definitely don't want to waste hours figuring out something elementary which maybe the other guy would've already known, etc. -- You received this message because you are subscribed to the Google Groups "Trac Development" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/trac-dev?hl=en.
