<div dir="ltr"><div class="gmail_default" style="font-family:tahoma,sans-serif">I'll be joining from APAC, though happy to wake up as early as 6am and stay awake as late as 10pm for IRC meetings.</div><div class="gmail_default" style="font-family:tahoma,sans-serif">Though nice to have the voice meetings every now and again, as well.</div><div class="gmail_default" style="font-family:tahoma,sans-serif"><br></div><div class="gmail_default" style="font-family:tahoma,sans-serif">+1 re the irc lounge plugin Chris, looks good. Haven't tried it on my mobile or setup any of the notifications, but on the whole slack-like in being somewhat user friendly. Missing the emoji responses per message (which is nice for feedback loops).</div><div class="gmail_default" style="font-family:tahoma,sans-serif">None the less as a first iteration for being more inclusive +1.</div><div class="gmail_default" style="font-family:tahoma,sans-serif">Best, Flanders</div></div><div class="gmail_extra"><br><div class="gmail_quote">On Thu, May 12, 2016 at 2:12 AM, Ghe Rivero <span dir="ltr"><<a href="mailto:ghe.rivero@gmail.com" target="_blank">ghe.rivero@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div text="#000000" bgcolor="#FFFFFF">
I'll be joining from Europe, although the proposed time works for me
(a bit late, but I can do it)<span class="HOEnZb"><font color="#888888"><br>
<br>
Ghe Rivero</font></span><div><div class="h5"><br>
<br>
<div>On 11/05/16 16:08, Christopher Aedo
wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<div dir="ltr" style="font-family:Arial;font-size:10.5pt">
<div dir="ltr">On Wed, May 11, 2016 at 2:29 AM, Jamie Hannaford
<a href="mailto:jamie.hannaford@rackspace.com" target="_blank"><jamie.hannaford@rackspace.com></a> wrote:<br>
> Is it possible to move the meeting time so it's friendly
towards folks in<br>
> Europe?</div>
<div dir="ltr"> </div>
<div dir="ltr">Thanks for bringing this up! One of our
intentions is to find times that can include interested
parties from lots of different time zones. Considering the
time we have right now was intended to work for folks in the
US as well as the APAC region, it's not friendly for people in
Europe. Other projects have seen success with alternating the
meetings times so every other week there is one that works
well for at least one half of the contributors. I am all for
this, only question is who would be joining us at a time that
works for people in Europe?</div>
<div dir="ltr"> </div>
<div dir="ltr">Would it make sense to start a new thread calling
out our interest in capturing feedback from people in Europe?</div>
<div dir="ltr"><br>
> Also, <a href="https://irccloud.com" target="_blank">https://irccloud.com</a> is a
great web-based IRC client which is both<br>
> user-friendly and free. IMO its UI/UX is far better for
newcomers than<br>
> something we can write from scratch.</div>
<div dir="ltr"> </div>
<div dir="ltr">I'm familiar with IRCCloud and it was discussed
in the other thread (titled "working group comms"). The
drawback is that the free tier is not persistent, so it ends
up being not too different from just hopping on <a href="http://freenode.net" target="_blank">freenode.net</a>'s
web-based IRC for the brief duration of the meeting, and then
being offline until the next meeting. Though that satisfies
the "lets meet on IRC" piece, it doesn't help much with
getting newcomers to IRC integrated into the larger community.</div>
<div dir="ltr"> </div>
<div dir="ltr">I am not proposing we write our own thing from
scratch at all, that would be crazy :) What I'm proposing is
that we host a version of "The Lounge" which is a web-based
IRC client very similar to <a href="http://irccloud.com" target="_blank">irccloud.com</a>. It's FOSS with an
active developer community and an excellent user experience.
You can see the project page here: <a href="http://thelounge.github.io/" target="_blank">http://thelounge.github.io/</a></div>
<div dir="ltr"> </div>
<div dir="ltr">-Christopher</div>
<div dir="ltr"> </div>
<div dir="ltr">><br>
><br>
> Jamie<br>
><br>
><br>
> ________________________________<br>
> From: Christopher Aedo <a href="mailto:caedo@us.ibm.com" target="_blank"><caedo@us.ibm.com></a><br>
> Sent: 10 May 2016 01:30<br>
> Cc: <a href="mailto:user-committee@lists.openstack.org" target="_blank">user-committee@lists.openstack.org</a><br>
> Subject: Re: [User-committee] Application Ecosystem
Working Group Post<br>
> Austin Summit Priority List<br>
> <br>
> On Wed, May 4, 2016 at 5:12 PM, Christopher Aedo
<a href="mailto:caedo@us.ibm.com" target="_blank"><caedo@us.ibm.com></a> wrote:<br>
>> On Tue, May 3, 2016 at 11:11 AM, Callaghan, John
<a href="mailto:john.callaghan@hpe.com" target="_blank"><john.callaghan@hpe.com></a><br>
>> wrote:<br>
>>> Coming away from our productive working group
session we established the<br>
>>> following three priorities for the group for the
next cycle.<br>
>>><br>
>>> A link to the session etherpad is listed and
welcome to input here:<br>
>>> <a href="https://etherpad.openstack.org/p/AppEcoSystem_WG_Austin_Meetup" target="_blank">https://etherpad.openstack.org/p/AppEcoSystem_WG_Austin_Meetup</a><br>
>>><br>
>>> Working Session Goals:<br>
>>><br>
>>> Define top 3 priorities from Agenda for the
Newton cycle<br>
>>><br>
>>> 1. Review Charter<br>
>>><br>
>>> § (Task Force - Subgroup determined from next
post summit meeting)<br>
>>><br>
>>> § Volunteers: John Callaghan HPE,<br>
>>><br>
>>> 2. Python SDK - First App and get it
published We need a win for<br>
>>> Python whether it be pythonsdk, shade or libcloud<br>
>>><br>
>>> § Craig Sterrett to drive with SDK owners<br>
>>><br>
>>> § Preparation for training to add value in
Barcelona<br>
>>><br>
>>> 3. Consider IRC in addition to 2 x monthly
calls<br>
>>><br>
>>> § Christopher Aedo to drive with foundation
through User-committee<br>
>>> mailing<br>
>>> list<br>
>> <br>
>> Thank you John for sending this note out and keeping
us on task here :)<br>
>> <br>
>> Regarding IRC there has been a different thread
(subject "[User-committee]<br>
>> working group comms") where we've been having a
conversation around the<br>
>> tools we can use for enabling IRC (and other
communication channels.) For<br>
>> those that haven't been following along, I
volunteered to work with the<br>
>> OpenStack Infra team to provide a web-based IRC
client. The first step of<br>
>> this will be for me to write a spec, and following
that we'll set up a<br>
>> server that will be available to interested parties.
Expect this service<br>
>> to<br>
>> be offered on an experimental basis at first, as
we'll need some time with<br>
>> real users to work out the kinks, but I expect the
experience to be<br>
>> largely<br>
>> painless for working group members who are
interested. The end result<br>
>> will<br>
>> be web-based access to IRC that also offers
persistence similar to Slack<br>
>> (i.e. when you close the browser, your persona is not
logged out - so next<br>
>> time you connect, you can "scroll back" to catch
yourself up on the<br>
>> conversation).<br>
>> <br>
>> Additionally, Leong from Intel shared a cheat sheet
that lets anyone<br>
>> quickly<br>
>> and easily hop on IRC from their web browser:<br>
>><br>
>> <a href="https://docs.google.com/document/d/1m--DFSwTPqKmxGNxP7ThDYuNr017wI_bUQOtqyaeyG0/edit" target="_blank">https://docs.google.com/document/d/1m--DFSwTPqKmxGNxP7ThDYuNr017wI_bUQOtqyaeyG0/edit</a><br>
>> In the short term I think this is great. In the long
term though, I hope<br>
>> to<br>
>> provide an even better experience that keeps folks
around on IRC as well<br>
>> :)<br>
>> <br>
>> Regarding having our meetings on IRC, Andreas Jeager
pointed out the<br>
>> communication standards we've agreed on for OpenStack
projects at large<br>
>><br>
>>
(<a href="http://docs.openstack.org/project-team-guide/open-community.html#public-meetings-on-irc" target="_blank">http://docs.openstack.org/project-team-guide/open-community.html#public-meetings-on-irc</a>).<br>
>> We can debate the applicability to working groups,
but I'd argue we have a<br>
>> LOT of evidence that holding meetings over IRC scales
well and is very<br>
>> inclusive. To that end I propose we hold our
bi-weekly IRC meetings on<br>
>> one<br>
>> of the established IRC channels. If we intend to
continue with the same<br>
>> schedule for now (3pm PST/10pm UTC) we can use the
IRC channel<br>
>> #openstack-meeting. If there are no objections, I'll
submit a patch to<br>
>> the<br>
>> IRC-meetings repository to officially reserve our
time slot.<br>
> <br>
> Enough time has passed without any objections to this
plan, and the<br>
> intention was confirmed in the App Ecosystem WG meeting
today. I submitted<br>
> the following patch which will reserve the IRC channel
"#openstack-meeting"<br>
> on a bi-weekly basis at our normal meeting time:<br>
> <a href="https://review.openstack.org/#/c/314322/" target="_blank">https://review.openstack.org/#/c/314322/</a><br>
> <br>
> We also agreed to give this time slot a few weeks in
order for the existing<br>
> members to get comfortable with IRC. If there are
additional folks who<br>
> would be interested in joining but find this time
inconvenient, we will<br>
> coordinate a poll for a new meeting time (i.e. something
that engages our<br>
> friends in Europe). For now though, the plan will be to
continue having<br>
> weekly meetings, alternating the venue between conference
call and IRC each<br>
> week.<br>
> <br>
> -Christopher<br>
><br>
><br>
> <br>
><br>
> <br>
> ________________________________<br>
> Rackspace International GmbH a company registered in the
Canton of Zurich,<br>
> Switzerland (company identification number
CH-020.4.047.077-1) whose<br>
> registered office is at Pfingstweidstrasse 60, 8005
Zurich, Switzerland.<br>
> Rackspace International GmbH privacy policy can be viewed
at<br>
> <a href="https://www.rackspace.co.uk/legal/swiss-privacy-policy" target="_blank">www.rackspace.co.uk/legal/swiss-privacy-policy</a>
- This e-mail message may<br>
> contain confidential or privileged information intended
for the recipient.<br>
> Any dissemination, distribution or copying of the
enclosed material is<br>
> prohibited. If you receive this transmission in error,
please notify us<br>
> immediately by e-mail at <a href="mailto:abuse@rackspace.com" target="_blank">abuse@rackspace.com</a> and delete
the original<br>
> message. Your cooperation is appreciated.<br>
</div>
</div>
<br>
<br>
<fieldset></fieldset>
<br>
</div></div><span class=""><pre>_______________________________________________
User-committee mailing list
<a href="mailto:User-committee@lists.openstack.org" target="_blank">User-committee@lists.openstack.org</a>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</a>
</pre>
</span></blockquote>
<br>
</div>
<br>_______________________________________________<br>
User-committee mailing list<br>
<a href="mailto:User-committee@lists.openstack.org">User-committee@lists.openstack.org</a><br>
<a href="http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee" rel="noreferrer" target="_blank">http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee</a><br>
<br></blockquote></div><br></div><br clear="all"><div><br></div>-- <br><div class="gmail_signature"><div dir="ltr">=================<div>Twitter: <a href="https://twitter.com/dfflanders" target="_blank">@DFFlanders</a></div><div>Skype: david.flanders</div><div>Based in Melbourne, Australia</div><div><br></div><div><br></div></div></div>