<p dir="ltr">Default volume should be 5% now, which works fine in meeting rooms, you can barely hear it.</p>
<p dir="ltr">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.</p>
<p dir="ltr">Even the members of the room used it to wait for a turn, it was pretty useful!</p>
<div class="gmail_quote">On Jan 13, 2016 17:14, "Max Binder" <<a href="mailto:mbinder@wikimedia.org">mbinder@wikimedia.org</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>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. :)<br><br></div>I'll populate the github page!<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Mon, Jan 11, 2016 at 3:15 PM, Joaquin Oltra Hernandez <span dir="ltr"><<a href="mailto:jhernandez@wikimedia.org" target="_blank">jhernandez@wikimedia.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div>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?<div><br></div><div>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).</div><div><br></div><div>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.</div><div><br></div><div>If you find issues or want to request changes, go to <a href="https://github.com/joakin/stack/issues" target="_blank">https://github.com/joakin/stack/issues</a></div><div><br></div><div>Thanks!</div><div><div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On Jan 11 2016, at 12:41 pm, Kristen Lans <<a href="mailto:klans@wikimedia.org" target="_blank">klans@wikimedia.org</a>> wrote:
<br>
<div dir="ltr">Very cool Joaquin! I can't wait to try it.<div><br></div><div>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: <a href="http://tinyurl.com/hv5ufmd" target="_blank">http://tinyurl.com/hv5ufmd</a></div><div><br></div><div>KL</div></div><div><br><div>On Mon, Jan 11, 2016 at 11:55 AM, Max Binder <span dir="ltr"><<a href="mailto:mbinder@wikimedia.org" target="_blank">mbinder@wikimedia.org</a>></span> wrote:<br><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div>Thanks, Joaquin! <br><br>I can't wait to test it in a real meeting. Maybe I'll use TPG as guinea pigs...<br><br></div></div><div><br><div><span>On Fri, Jan 8, 2016 at 2:56 PM, Joaquin Oltra Hernandez <span dir="ltr"><<a href="mailto:jhernandez@wikimedia.org" target="_blank">jhernandez@wikimedia.org</a>></span> wrote:<br></span><div><div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><p dir="ltr">Hi!</p>
<p dir="ltr">I've worked on this during the hackathon, and after chatting with Max it has the required functionality to work:</p>
<p dir="ltr"><a href="http://stack.wmflabs.org" target="_blank">http://stack.wmflabs.org</a></p>
<p dir="ltr">Features:<br>
* create named rooms (shareable URL)<br>
* add yourself to the queue (remembers name)<br>
* one person can add multiple people<br>
* can pop from the stack (needs human agreement on who will be the popper)<br>
* plays sound when somebody is added to queue<br>
* after 5 minutes of stale queue plays warning sound</p>
<p dir="ltr">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.</p>
<p dir="ltr">Open to comments, hope this helps!</p>
<div><div><div>On Sep 22, 2015 08:53, "Dan Garry" <<a href="mailto:dgarry@wikimedia.org" target="_blank">dgarry@wikimedia.org</a>> wrote:<br type="attribution"></div></div><blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div><div><div dir="ltr"><div><div><div>On 22 September 2015 at 08:40, Kevin Smith <span dir="ltr"><<a href="mailto:ksmith@wikimedia.org" target="_blank">ksmith@wikimedia.org</a>></span> wrote:<blockquote style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div dir="ltr"><div><div><div>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.</div></div></div></div></blockquote><div><br></div></div><div>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.</div><div><br>Dan</div></div><div><br></div>-- <br><div><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr">Dan Garry<div><span style="font-size:small">Lead Product Manager, </span><span style="font-size:small">Discovery</span></div><div>Wikimedia Foundation</div></div></div></div></div></div></div></div></div></div>
</div></div>
<br></div></div><span>_______________________________________________<br>
teampractices mailing list<br>
<a href="mailto:teampractices@lists.wikimedia.org" target="_blank">teampractices@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/teampractices" rel="noreferrer" target="_blank">https://lists.wikimedia.org/mailman/listinfo/teampractices</a><br>
<br></span></blockquote></div>
<br>_______________________________________________<br>
teampractices mailing list<br>
<a href="mailto:teampractices@lists.wikimedia.org" target="_blank">teampractices@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/teampractices" rel="noreferrer" target="_blank">https://lists.wikimedia.org/mailman/listinfo/teampractices</a><br>
<br></blockquote></div></div></div><br></div>
<br>_______________________________________________<br>
teampractices mailing list<br>
<a href="mailto:teampractices@lists.wikimedia.org" target="_blank">teampractices@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/teampractices" rel="noreferrer" target="_blank">https://lists.wikimedia.org/mailman/listinfo/teampractices</a><br>
<br></blockquote></div><br></div>
</blockquote></div></div></div><br>_______________________________________________<br>
teampractices mailing list<br>
<a href="mailto:teampractices@lists.wikimedia.org" target="_blank">teampractices@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/teampractices" rel="noreferrer" target="_blank">https://lists.wikimedia.org/mailman/listinfo/teampractices</a><br>
<br></blockquote></div><br></div>
<br>_______________________________________________<br>
teampractices mailing list<br>
<a href="mailto:teampractices@lists.wikimedia.org">teampractices@lists.wikimedia.org</a><br>
<a href="https://lists.wikimedia.org/mailman/listinfo/teampractices" rel="noreferrer" target="_blank">https://lists.wikimedia.org/mailman/listinfo/teampractices</a><br>
<br></blockquote></div>