I'm not sure what the answer here is, as you're right about the multiple differing views issue.
My take on it (and it is a little one sided) is to approach the pages as a User tries to find something out, usually (inevitably) as a Java dev. Not sure about a better way fwd tho ... will ponder. Marnie On Thu, Feb 12, 2009 at 2:32 PM, Jonathan Robie <jonathan.ro...@redhat.com>wrote: > Marnie McCormack wrote: > >> Being honest, I like the old page far better - escpecially since I just >> added to it/updated it :-) >> >> From my pov, I think it's quite frustrating that all the >> broker/implementation boundaries are becoming blurred in the docs & the >> way >> we link to them. >> >> > > One problem we're having: there are many ways we could organize this > information, and when people do individual pages, they each use a given > organization. Sometimes we see multiple approaches to organization on the > same page. > > Is that inherent to our group editing approach using a Wiki, or is there a > good way to get a handle on this? > > > Jonathan > > --------------------------------------------------------------------- > Apache Qpid - AMQP Messaging Implementation > Project: http://qpid.apache.org > Use/Interact: mailto:dev-subscr...@qpid.apache.org > >
