Now I’m really confused.
Is it Jim or James?
---
JamesLowder wrote:From what the line developers told me, John and the Kargatane members were not formal editors on the book, but advisors on the line. They were supposed to comment upon the RL continuity, as they understood it. They were not supposed to be rewriting the other authors, especially those outside their circle. There's a difference between getting the draft and providing feedback and getting the draft and rewriting the text with no participation by the original author--the person whose name is going on the published text.
Again, let’s remove from the picture JWM’s mythological bad temper (he’s going to hate me now if I continue writing about this

). It’s something that belongs to him, when the poop hit the fan, later in the story.
When things were sent to him by the developers, John took the role of “shadow developer”, and it surely suited the editors well since he was catching many of the continuity errors they didn’t see. That was never contradicted by them in public, so John’s claims about his important role are true, and it's backed by all former kargatane.
Now, being de facto developer probably gave him a wider licence then just advisor for continuity. Was it assumed by John or given to him by the editors? I don’t know.
But I still can’t believe that the type of work John was doing wasn’t known by the editors. If they really didn’t, they were careless IMHO. There are so many ways to review someone else’s text editing!
Now the developers told you John and the K were just advisors? I believe you, but I don’t think it’s the best of way to describe what John really did.
An aside--didn't the Kargatane have a very public parting of the ways with WW because of creative differences? Doesn't that make it clear they were not the official final word on the line, with absolute power over everyone's text?
Sure, but that wasn’t about the Gaz IIRC, it was about how other products were handled.
----
Again, I’ll quote my old managerial courses I took a while back.
Sadly for humanity, in an organisation the authority lines have to be clearly defined, and everybody must know and understand who is who and doing what. Whether you are in a vegetable canning plant, an engineer firm or a team of editor and writers, this is true.
Otherwise, chaos has a good chance of putting its nose in it. It’s a classic in managerial studies.
I don’t want to pinpoint anybody, but the lack of clear structure led to what happened:
- I believe John assumed he was a “shadow developer” (or was given the role) and took his role with professionalism and with the burning passion of his personality.
- When the Sithicus text was sent to him, John edited a text which the editors had told you woundn’t be edited by John or the K. But was this new specific data about Sithicus’s text communicated to John? Something was done carelessly somewhere.
- the text wasn’t reviewed when it came back to the editors: they didn’t see the changes / didn’t realize perhaps – very odd IMHO.
- So it was never submitted your way, for whatever reasons. Was it John’s role to send you back the edited text? I don’t know, but to remove the confusion over this part of his role surely wasn’t his job.
My humble conclusion: I’m not sure the blame should be on John or the K, if my assumptions above are correct. I’d say blame the confused structure and the other people around. It led to this miscommunication mess.
JamesLowder wrote:The only instructive part of the discussion is what it reveals about the inherent flaws in shared world/work-for-hire projects. The problems with the Gaz--and big parts of the rest of the RL line, whether run by WW or TSR/WotC--speak to why writers that care about their work often avoid shared world projects, or leave the line after they've gone through the often-destructive process on a couple of projects.
Are you right! The mess in this particular project is very interesting to dissect for all wannabe authors.
Clarify the roles and remind everybody through the project on what you have agreed at the start of the project. It’s not fun, but it might help clarifying things and avoid mess.
Joël