Hi -- I've gotten bounces from openstack-private before, but the emails are actually going through to the list.
On Tue, May 17, 2016 at 10:30 AM, Matt Jarvis <matt.jar...@datacentred.co.uk> wrote: > We've noticed that as well, is everyone getting strange bounces from > openstack-private ? Any list admins lurking here ? > > On 17 May 2016 at 17:20, Chris Morgan <mihali...@gmail.com> wrote: >> >> very good point. Currently a bit flustered by apparent bounces however. >> Will fix this though >> >> On Tue, May 17, 2016 at 12:19 PM, Matt Jarvis >> <matt.jar...@datacentred.co.uk> wrote: >>> >>> Hi Chris >>> >>> Good round up and a good start on the definition. Don't forget the public >>> cloud operators though, it's not all about private cloud ;) >>> >>> On 17 May 2016 at 16:51, Chris Morgan <mihali...@gmail.com> wrote: >>>> >>>> I'm new to this, but here goes: >>>> >>>> Meeting held on IRC today at 14:00 UTC to jumpstart a new process for >>>> arranging OpenStack operators mid-cycle meetups. >>>> >>>> Nice minutes from Tom here >>>> >>>> http://eavesdrop.openstack.org/meetings/ops_meetups_team/2016/ops_meetups_team.2016-05-17-14.00.html >>>> >>>> etherpad here : https://etherpad.openstack.org/p/ops-meetups-team >>>> >>>> In short there was consensus behind the mailing list locking in a >>>> region and approximate time slot for each meetup and then making an >>>> open call for meeting hosts/"underwriters". The region would be one of >>>> : north america, europe or APAC in such a way as to oppose the region >>>> of the following OpenStack summit. There is also desire to cap numbers >>>> and somehow encourage operators/users and discourage vendors from >>>> attending without getting to the level of having to vet >>>> individuals. To that end I volunteered to propose a definition of >>>> users, and so here goes: >>>> >>>> ------ >>>> >>>> The openstack operators meetings have a preference for 'users' >>>> vs. 'vendors' since the vendors have every opportunity to get their >>>> message across at the Summit in the vendor sessions, the marketplace >>>> etc. Meanwhile, operators need a venue to share frank, unfettered, >>>> possibly highly critical info about products and core openstack >>>> components. >>>> >>>> For the purposes of getting the meet ups organised then, the following >>>> definition is proposed: >>>> >>>> Definition: >>>> >>>> All attendees at an OpenStack operators mid-cycle meetup ('the >>>> meetup') should be willing and able to discuss issues arising from >>>> operating OpenStack for private cloud at some kind of scale, including >>>> ideally having direct experience of OpenStack private cloud operation >>>> or expectation of that in future. Representatives from organisations >>>> having both a vendor and a user role in the OpenStack community should >>>> wear their user hat for the purposes of the meetup. Attendance by >>>> those fitting these guidelines is highly encouraged. >>>> >>>> >>>> -- >>>> Chris Morgan <mihali...@gmail.com> >>>> >>>> _______________________________________________ >>>> OpenStack-operators mailing list >>>> OpenStack-operators@lists.openstack.org >>>> http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators >>>> >>> >>> >>> DataCentred Limited registered in England and Wales no. 05611763 >> >> >> >> >> -- >> Chris Morgan <mihali...@gmail.com> > > > > DataCentred Limited registered in England and Wales no. 05611763 > > _______________________________________________ > OpenStack-operators mailing list > OpenStack-operators@lists.openstack.org > http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators > -- Blog: serverascode.com _______________________________________________ OpenStack-operators mailing list OpenStack-operators@lists.openstack.org http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-operators
