[Wp3] Changes last night to Google Docs

Greg Shatan gregshatanipc at gmail.com
Wed Jul 15 20:00:37 UTC 2015 

I am a big fan of Google Docs for collaborative drafting.  I think the
model you (Avri) espouse is the one I prefer (but which does require the
editors to have edit and suggest rights, which is what I was getting at).
I think it's only top down-ish if one person holds the edit rights and also
acts in a top-down manner (we have had very good experience with the
various "pen-holders" in this group, so I am far from suggesting that being
the sole editor is top down per se; it's just a little less fluid than
having a few editors operating as you suggest).  Even if I'm the/an editor
on a collaborative doc, I would always make changes in suggest mode so they
can be seen by other collaborators.  The only exception might be clean up
(spacing, punctuation, not word editing), in which case I would still
express my intention to do so, collaborative guy that I am.

On Wed, Jul 15, 2015 at 3:01 PM, Avri Doria <avri at acm.org> wrote:

> Hi,
>
> while it can become top down, it does not need to.
>
> First you can have several editors who take a commitment to be neutral
> in accepting the suggestions/comments of others and who never accept
> their own substantive edits and who committ to put in the edits of
> people who cannot access the drive tools for whatever reasons.
>
> Suggested edits also allow for commentary and discussion in the
> document.  Editors can send out snapshots on a periodic basis in group
> where not everyone can access the drive document.
>
> And then you can do what Leon did as chair of the mtg the other day and
> talk about each edit before accepting it during the meeting..
>
> There may be better way to do BUMP  (Bottom Up Multistakeholdder
> Process) collaborative editing, but I have not yet discovered it.
>
> avri
>
> On 15-Jul-15 14:18, Seun Ojedeji wrote:
> > Well, i will not market google beyond normal, but I don't think the
> > "comment/suggest" mode is that top down as you seem to believe. The
> > ability to have your edits marked/tagged so someone see your edits and
> > either disagree/agree (or further improve upon it) seem like a huge
> > bottom-up feature to me.
> >
> > Overall its a matter of preference and not only about the idiotic
> > level of the users collaborating. ;-)
> >
> > Regards
> >
> > On 7/15/15, Greg Shatan <gregshatanipc at gmail.com> wrote:
> >> I don't think there's a "better approach."
> >>
> >> I would say the simpler and more controlling approach is to only give
> >> "comment/suggest" rights and to retain "edit" rights to the
> "facilitator".
> >> This avoids mistakes by others, but also takes away a lot of
> flexibility in
> >> the process.  This approach is more "idiot-proof" and probably better
> in a
> >> larger group, but it's also more "top down."
> >>
> >> There are advantages to giving others edit rights, as long as there is a
> >> clear understanding of when to use them, and how not to abuse them (even
> >> accidentally).  This allows control of the document to be taken by
> others
> >> when the facilitator is unavailable or if a contributor wants to
> clean-up
> >> the document.  This also allows the facilitator to make suggestions on
> >> parts primarily drafted by others, and for those others to act as editor
> >> and accept those changes.  This approach is better in a smaller group,
> and
> >> it's more "bottom up" or egalitarian.  It does take a little more
> education
> >> (5 minutes, max) and a little more care to note which mode you are in.
> >> But, since it's less "idiot-proof," I guess you have to ask yourself who
> >> you are working with on any given project to decide which one to choose.
> >>  :-)
> >>
> >> Greg
> >>
> >> On Tue, Jul 14, 2015 at 6:19 PM, Seun Ojedeji <seun.ojedeji at gmail.com>
> >> wrote:
> >>
> >>> Yeah that's correct Greg but again many go to edit straight up without
> >>> looking at changing the modes. As Avri already hinted, the better
> >>> approach
> >>> to avoid any possible mistake is using the "anyone with url can
> comment"
> >>>
> >>> Cheers!
> >>> Sent from Google nexus 4
> >>> kindly excuse brevity and typos.
> >>> On 14 Jul 2015 3:25 pm, "Greg Shatan" <gregshatanipc at gmail.com> wrote:
> >>>
> >>>> If one has "edit" rights on a document, one can change their mode to
> >>>> "suggest" (aka redline) in the upper right hand corner dropdown menu.
> >>>> When
> >>>> collaborating, it is best if all changes are entered in "suggest" mode
> >>>> (which also generates a marginal tag) or by making comments (which
> only
> >>>> generates a marginal box, but does not do anything to the text).
> >>>> Suggestions can then be accepted in "edit" mode by the person
> >>>> controlling
> >>>> the document.
> >>>>
> >>>>
> >>>>
> >>>> On Tue, Jul 14, 2015 at 9:46 AM, Avri Doria <avri at acm.org> wrote:
> >>>>
> >>>>> hi,
> >>>>>
> >>>>> under file you shoul see show previous versions.
> >>>>>
> >>>>> I did nothing to remove your edits.  the only changes i made where
> some
> >>>>> formating.  permats that replace my marks with yours.  And content i
> >>>>> changed i did in suggest mode, that is why they are so visible.
> >>>>>
> >>>>> One thing about setting them up, it is much better to give every one
> >>>>> with the URL comment ability instead of edit.  that way all the edits
> >>>>> remian visible until accepted by the lead editor.
> >>>>>
> >>>>> i would have changed that for you, but thought it a bit too
> >>>>> presumptuous.
> >>>>>
> >>>>> avri
> >>>>>
> >>>>> On 14-Jul-15 09:26, Jeff Neuman wrote:
> >>>>>> Thanks.  When I read your version, the redlines now appear as
> non-red
> >>>>> and
> >>>>>> the comments I put in are gone.  Any way to see a version with both
> >>>>>> of
> >>>>> our
> >>>>>> changes in there?
> >>>>>>
> >>>>>>
> >>>>>> Jeffrey J. Neuman
> >>>>>> Senior Vice President |Valideus USA | Com Laude USA
> >>>>>> 1751 Pinnacle Drive, Suite 600
> >>>>>> Mclean, VA 22102, United States
> >>>>>> E: jeff.neuman at valideus.com or jeff.neuman at comlaude.com
> >>>>>> T: +1.703.635.7514
> >>>>>> M: +1.202.549.5079
> >>>>>> @Jintlaw
> >>>>>>
> >>>>>>
> >>>>>> -----Original Message-----
> >>>>>> From: wp3-bounces at icann.org [mailto:wp3-bounces at icann.org] On
> Behalf
> >>>>> Of Avri
> >>>>>> Doria
> >>>>>> Sent: Tuesday, July 14, 2015 9:01 AM
> >>>>>> To: wp3 at icann.org
> >>>>>> Subject: Re: [Wp3] Changes last night to Google Docs
> >>>>>>
> >>>>>> Hi,
> >>>>>>
> >>>>>> Thanks.
> >>>>>>
> >>>>>> I just made some edits to the doc.
> >>>>>>
> >>>>>> the ones that were cosmetic I just did as edits.
> >>>>>> In a few places I suggested addiitonal text.  These I did as
> >>>>> suggestions and
> >>>>>> thus they will need to be approved by the person holding the pen or
> >>>>> someone.
> >>>>>> thanks for ground work.
> >>>>>>
> >>>>>> avri
> >>>>>>
> >>>>>>
> >>>>>> On 14-Jul-15 08:31, Jeff Neuman wrote:
> >>>>>>>
> >>>>>>> All,
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> I made some edits to the google doc version of the Staff
> >>>>>>> Accountability section last night, but not the word doc or pdf.  I
> >>>>>>> will be happy to discuss the changes today, but I just wanted to
> >>>>>>> make
> >>>>>>> sure you can all see it.  The link is at:
> >>>>>>>
> >>>>>
> https://docs.google.com/document/d/1UZG8Dye8W2trulcK_54XshBFT2fDK7-eyKlmi1gY
> >>>>>> nLM/edit.
> >>>>>>> I tried to make all of my changes red.
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> Best regards,
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> *Jeffrey J. Neuman*
> >>>>>>>
> >>>>>>> *Senior Vice President *|*Valideus USA***| *Com Laude USA*
> >>>>>>>
> >>>>>>> 1751 Pinnacle Drive, Suite 600
> >>>>>>>
> >>>>>>> Mclean, VA 22102, United States
> >>>>>>>
> >>>>>>> E: _jeff.neuman at valideus.com <mailto:jeff.neuman at valideus.com>_or
> >>>>>>> _jeff.neuman at comlaude.com <mailto:jeff.neuman at comlaude.com>_
> >>>>>>>
> >>>>>>> T: +1.703.635.7514
> >>>>>>>
> >>>>>>> M: +1.202.549.5079
> >>>>>>>
> >>>>>>> @Jintlaw
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>>
> >>>>>>> _______________________________________________
> >>>>>>> wp3 mailing list
> >>>>>>> wp3 at icann.org
> >>>>>>> https://mm.icann.org/mailman/listinfo/wp3
> >>>>>> ---
> >>>>>> This email has been checked for viruses by Avast antivirus software.
> >>>>>> https://www.avast.com/antivirus
> >>>>>>
> >>>>>> _______________________________________________
> >>>>>> wp3 mailing list
> >>>>>> wp3 at icann.org
> >>>>>> https://mm.icann.org/mailman/listinfo/wp3
> >>>>>>
> >>>>>>
> >>>>>>
> >>>>>
> >>>>> ---
> >>>>> This email has been checked for viruses by Avast antivirus software.
> >>>>> https://www.avast.com/antivirus
> >>>>>
> >>>>> _______________________________________________
> >>>>> wp3 mailing list
> >>>>> wp3 at icann.org
> >>>>> https://mm.icann.org/mailman/listinfo/wp3
> >>>>>
> >>>>
> >>>> _______________________________________________
> >>>> wp3 mailing list
> >>>> wp3 at icann.org
> >>>> https://mm.icann.org/mailman/listinfo/wp3
> >>>>
> >>>>
> >
>
>
> ---
> This email has been checked for viruses by Avast antivirus software.
> https://www.avast.com/antivirus
>
> _______________________________________________
> wp3 mailing list
> wp3 at icann.org
> https://mm.icann.org/mailman/listinfo/wp3
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mm.icann.org/pipermail/wp3/attachments/20150715/320d7b57/attachment.html>

More information about the wp3 mailing list