Open Stack

To further push this task. I would like to propose we pick a new joint
meeting schedule for both SIGs together.

The first steps should be we share same meeting time and schedule, also
share same event plan (as Witek suggested). And we can go from there to
discuss if we need further plans.
I also would like to suggest we move our meeting place to
#openstack-meeting so we can have chance to have more people to join.
Let's have a quick doodle polling for time,
https://doodle.com/poll/98nrf8iibr7zv3kt
Please join that doodle survey if you're interested in join us:)


On Thu, Nov 28, 2019 at 4:57 PM Rico Lin <rico.lin.guanyu at gmail.com> wrote:

>
>
> On Thu, Nov 28, 2019 at 4:37 PM Witek Bedyk <witold.bedyk at suse.com> wrote:
> >
> > Hi,
> > how about starting with joining the SIGs meeting times and organizing
> > the Forum and PTG events together? The repositories and wiki pages could
> > stay as they are and refer to each other.
> >
> I think even if we merged two SIG, repositories should stay separated as
> they're now. IMO we can simply rename openstack/auto-scaling-sig
> to openstack/auto-scaling and so as to self-healing.
> Or just keep it the same will be fine IMO.
> We don't need a new repo for the new SIG (at least not for now).
>
> I do like the idea to start with joining the SIGs meeting times and
> organizing the Forum and PTG events together.
> One more proposal in my mind will be, join the channel for IRC.
> >
> > I think merging is good if you have an idea how to better structure the
> > content, and time to review the existing one and do all the formal
> > stuff. Just gluing the documents won't help.
> Totally agree with this point!
> >
> > Cheers
> > Witek
> >
>
>
> --
> May The Force of OpenStack Be With You,
> Rico Lin
> irc: ricolin
>


-- 
May The Force of OpenStack Be With You,

*Rico Lin*irc: ricolin
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.openstack.org/pipermail/openstack-discuss/attachments/20191218/af9d8df5/attachment-0001.html>