[User-committee] Application Ecosystem Working Group Post Austin Summit Priority List

Ghe Rivero ghe.rivero at gmail.com
Wed May 11 16:12:27 UTC 2016


I'll be joining from Europe, although the proposed time works for me (a
bit late, but I can do it)

Ghe Rivero

On 11/05/16 16:08, Christopher Aedo wrote:
> On Wed, May 11, 2016 at 2:29 AM, Jamie Hannaford
> <jamie.hannaford at rackspace.com> wrote:
> > Is it possible to move the meeting time so it's friendly towards
> folks in
> > Europe?
>  
> 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?
>  
> Would it make sense to start a new thread calling out our interest in
> capturing feedback from people in Europe?
>
> > Also, https://irccloud.com is a great web-based IRC client which is both
> > user-friendly and free. IMO its UI/UX is far better for newcomers than
> > something we can write from scratch.
>  
> 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 freenode.net'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.
>  
> 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
> irccloud.com.  It's FOSS with an active developer community and an
> excellent user experience.  You can see the project page here:
> http://thelounge.github.io/
>  
> -Christopher
>  
> >
> >
> > Jamie
> >
> >
> > ________________________________
> > From: Christopher Aedo <caedo at us.ibm.com>
> > Sent: 10 May 2016 01:30
> > Cc: user-committee at lists.openstack.org
> > Subject: Re: [User-committee] Application Ecosystem Working Group Post
> > Austin Summit Priority List
> >  
> > On Wed, May 4, 2016 at 5:12 PM, Christopher Aedo <caedo at us.ibm.com>
> wrote:
> >> On Tue, May 3, 2016 at 11:11 AM, Callaghan, John
> <john.callaghan at hpe.com>
> >> wrote:
> >>> Coming away from our productive working group session we
> established the
> >>> following three priorities for the group for the next cycle.
> >>>
> >>> A link to the session etherpad is listed and welcome to input here:
> >>> https://etherpad.openstack.org/p/AppEcoSystem_WG_Austin_Meetup
> >>>
> >>> Working Session Goals:
> >>>
> >>> Define top 3 priorities from Agenda for the Newton cycle
> >>>
> >>> 1.       Review Charter
> >>>
> >>> §  (Task Force - Subgroup determined from next post summit meeting)
> >>>
> >>> §  Volunteers: John Callaghan HPE,
> >>>
> >>> 2.       Python SDK - First App and get it published We need a win for
> >>> Python whether it be pythonsdk, shade or libcloud
> >>>
> >>> §  Craig Sterrett to drive with SDK owners
> >>>
> >>> §  Preparation for training to add value in Barcelona
> >>>
> >>> 3.       Consider IRC in addition to 2 x monthly calls
> >>>
> >>> §  Christopher Aedo to drive with foundation through User-committee
> >>> mailing
> >>> list
> >>  
> >> Thank you John for sending this note out and keeping us on task here :)
> >>  
> >> Regarding IRC there has been a different thread (subject
> "[User-committee]
> >> working group comms") where we've been having a conversation around the
> >> tools we can use for enabling IRC (and other communication
> channels.)  For
> >> those that haven't been following along, I volunteered to work with the
> >> OpenStack Infra team to provide a web-based IRC client.  The first
> step of
> >> this will be for me to write a spec, and following that we'll set up a
> >> server that will be available to interested parties.  Expect this
> service
> >> to
> >> be offered on an experimental basis at first, as we'll need some
> time with
> >> real users to work out the kinks, but I expect the experience to be
> >> largely
> >> painless for working group members who are interested.  The end result
> >> will
> >> be web-based access to IRC that also offers persistence similar to
> Slack
> >> (i.e. when you close the browser, your persona is not logged out -
> so next
> >> time you connect, you can "scroll back" to catch yourself up on the
> >> conversation).
> >>  
> >> Additionally, Leong from Intel shared a cheat sheet that lets anyone
> >> quickly
> >> and easily hop on IRC from their web browser:
> >>
> >>
> https://docs.google.com/document/d/1m--DFSwTPqKmxGNxP7ThDYuNr017wI_bUQOtqyaeyG0/edit
> >> In the short term I think this is great.  In the long term though,
> I hope
> >> to
> >> provide an even better experience that keeps folks around on IRC as
> well
> >> :)
> >>  
> >> Regarding having our meetings on IRC, Andreas Jeager pointed out the
> >> communication standards we've agreed on for OpenStack projects at large
> >>
> >>
> (http://docs.openstack.org/project-team-guide/open-community.html#public-meetings-on-irc).
> >> We can debate the applicability to working groups, but I'd argue we
> have a
> >> LOT of evidence that holding meetings over IRC scales well and is very
> >> inclusive.  To that end I propose we hold our bi-weekly IRC meetings on
> >> one
> >> of the established IRC channels.  If we intend to continue with the
> same
> >> schedule for now (3pm PST/10pm UTC) we can use the IRC channel
> >> #openstack-meeting.  If there are no objections, I'll submit a patch to
> >> the
> >> IRC-meetings repository to officially reserve our time slot.
> >  
> > Enough time has passed without any objections to this plan, and the
> > intention was confirmed in the App Ecosystem WG meeting today.  I
> submitted
> > the following patch which will reserve the IRC channel
> "#openstack-meeting"
> > on a bi-weekly basis at our normal meeting time:
> > https://review.openstack.org/#/c/314322/
> >  
> > We also agreed to give this time slot a few weeks in order for the
> existing
> > members to get comfortable with IRC.  If there are additional folks who
> > would be interested in joining but find this time inconvenient, we will
> > coordinate a poll for a new meeting time (i.e. something that
> engages our
> > friends in Europe).  For now though, the plan will be to continue having
> > weekly meetings, alternating the venue between conference call and
> IRC each
> > week.
> >  
> > -Christopher
> >
> >
> >  
> >
> >    
> > ________________________________
> > Rackspace International GmbH a company registered in the Canton of
> Zurich,
> > Switzerland (company identification number CH-020.4.047.077-1) whose
> > registered office is at Pfingstweidstrasse 60, 8005 Zurich, Switzerland.
> > Rackspace International GmbH privacy policy can be viewed at
> > www.rackspace.co.uk/legal/swiss-privacy-policy
> <https://www.rackspace.co.uk/legal/swiss-privacy-policy> - This e-mail
> message may
> > contain confidential or privileged information intended for the
> recipient.
> > Any dissemination, distribution or copying of the enclosed material is
> > prohibited. If you receive this transmission in error, please notify us
> > immediately by e-mail at abuse at rackspace.com and delete the original
> > message. Your cooperation is appreciated.
>  
>
>
>
> _______________________________________________
> User-committee mailing list
> User-committee at lists.openstack.org
> http://lists.openstack.org/cgi-bin/mailman/listinfo/user-committee

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/user-committee/attachments/20160511/df023954/attachment.html>


More information about the User-committee mailing list