[teampractices] [TOOL REQUEST] A way to "raise your hand" as a remotee

[Sam Smith]

I would say is that I found myself wanting to immediately respond to a
question and I wasn't sure of the protocol. However, I suspect that this
was heavily influenced by the fact that I was in the meeting room – I'm
usually a face on the big green – and I could see the stack of people
waiting to talk.

It's been great trying out the tool and I'm looking forward to using it
again.

-Sam

On Wed, Jan 13, 2016 at 6:12 PM, Joaquin Oltra Hernandez <
jhernandez at wikimedia.org> wrote:

> Default volume should be 5% now, which works fine in meeting rooms, you
> can barely hear it.
>
> We found very useful to keep the stack window on the big screen resized
> side by side with the big hangouts window to give visibility to the stack.
>
> Even the members of the room used it to wait for a turn, it was pretty
> useful!
> On Jan 13, 2016 17:14, "Max Binder" <mbinder at wikimedia.org> wrote:
>
>> Yea, I think the best use of sound would be something that the
>> facilitator can hear, but not necessarily everyone. And maybe simply a
>> nicer sound. :)
>>
>> I'll populate the github page!
>>
>> On Mon, Jan 11, 2016 at 3:15 PM, Joaquin Oltra Hernandez <
>> jhernandez at wikimedia.org> wrote:
>>
>>> Adam, we talked about this and it seems like showing some kind of stats
>>> with how many times the attendants have been in the room would help seeing
>>> who has participated more and who less. Would that be reasonable?
>>>
>>> We've tried it out today in a long meeting and it was definitely helpful
>>> (i monitored the queue, and it helped people queue for talking without
>>> disrupting the current conversation).
>>>
>>> We also found that the sounds are pretty disruptive, so we've added a
>>> mute button so that we can show it on the meeting screen and in remotes
>>> that are talking without bothering everyone. I want to get around to
>>> lowering the volume of the sounds, or disabling them by default. They don't
>>> seem as useful as we anticipated.
>>>
>>> If you find issues or want to request changes, go to
>>> https://github.com/joakin/stack/issues
>>>
>>> Thanks!
>>>
>>>> On Jan 11 2016, at 12:41 pm, Kristen Lans <klans at wikimedia.org> wrote:
>>>> Very cool Joaquin! I can't wait to try it.
>>>>
>>>> FYI, here's a link to a short description of the facilitation technique
>>>> of "stacking" from the group I learned it from, Community at Work:
>>>> http://tinyurl.com/hv5ufmd
>>>>
>>>> KL
>>>>
>>>> On Mon, Jan 11, 2016 at 11:55 AM, Max Binder <mbinder at wikimedia.org>
>>>> wrote:
>>>>
>>>> Thanks, Joaquin!
>>>>
>>>> I can't wait to test it in a real meeting. Maybe I'll use TPG as guinea
>>>> pigs...
>>>>
>>>>
>>>> On Fri, Jan 8, 2016 at 2:56 PM, Joaquin Oltra Hernandez <
>>>> jhernandez at wikimedia.org> wrote:
>>>>
>>>> Hi!
>>>>
>>>> I've worked on this during the hackathon, and after chatting with Max
>>>> it has the required functionality to work:
>>>>
>>>> http://stack.wmflabs.org
>>>>
>>>> Features:
>>>> * create named rooms (shareable URL)
>>>> * add yourself to the queue (remembers name)
>>>> * one person can add multiple people
>>>> * can pop from the stack (needs human agreement on who will be the
>>>> popper)
>>>> * plays sound when somebody is added to queue
>>>> * after 5 minutes of stale queue plays warning sound
>>>>
>>>> It's kind of real-time (1s interval polling to server) and it may crash
>>>> at some point, but it gets the job done for now. It's also not really
>>>> secured so a mean user can probably easily crash the server, I'm assuming
>>>> good faith for now.
>>>>
>>>> Open to comments, hope this helps!
>>>> On Sep 22, 2015 08:53, "Dan Garry" <dgarry at wikimedia.org> wrote:
>>>>
>>>> On 22 September 2015 at 08:40, Kevin Smith <ksmith at wikimedia.org>
>>>> wrote:
>>>>
>>>> I had thought about that in the past, but seeing it in this thread
>>>> really resonated with me. For meetings with a mix of SF and remote folks, I
>>>> am starting to think that it would be better for all the SF folks to
>>>> scatter and use individual computers to join the hangout.
>>>>
>>>>
>>>> This is harder than it seems. It can be quite disruptive to those
>>>> around you to sit at your desk being noisy participating in a hangout, and
>>>> that rules out a large part of the office. I've done this before myself
>>>> from the fifth floor collab space, where there are no permanent desks and
>>>> some semi-private areas, but you cannot guarantee the availability of those
>>>> spaces. When I was remote I often wondered why more people didn't do this,
>>>> but when I moved to the office, I started to appreciate the difficulties
>>>> with it.
>>>>
>>>> Dan
>>>>
>>>> --
>>>> Dan Garry
>>>> Lead Product Manager, Discovery
>>>> Wikimedia Foundation
>>>>
>>>> _______________________________________________
>>>> teampractices mailing list
>>>> teampractices at lists.wikimedia.org
>>>> https://lists.wikimedia.org/mailman/listinfo/teampractices
>>>>
>>>>
>>>> _______________________________________________
>>>> teampractices mailing list
>>>> teampractices at lists.wikimedia.org
>>>> https://lists.wikimedia.org/mailman/listinfo/teampractices
>>>>
>>>>
>>>>
>>>> _______________________________________________
>>>> teampractices mailing list
>>>> teampractices at lists.wikimedia.org
>>>> https://lists.wikimedia.org/mailman/listinfo/teampractices
>>>>
>>>>
>>>>
>>> _______________________________________________
>>> teampractices mailing list
>>> teampractices at lists.wikimedia.org
>>> https://lists.wikimedia.org/mailman/listinfo/teampractices
>>>
>>>
>>
>> _______________________________________________
>> teampractices mailing list
>> teampractices at lists.wikimedia.org
>> https://lists.wikimedia.org/mailman/listinfo/teampractices
>>
>>
> _______________________________________________
> teampractices mailing list
> teampractices at lists.wikimedia.org
> https://lists.wikimedia.org/mailman/listinfo/teampractices
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.wikimedia.org/pipermail/teampractices/attachments/20160113/2b667b81/attachment.html>