Thanks Prakash for all your effort and energy.
I can definitely help with guidelines and their testing part from Tempest point of view or you can count that as help from the community side.
My concern is almost the same as Mark, I am involved in multiple areas so if interop requires more time then it might be an issue.
As of now, I am ok to help to handle some code side part or as 2nd vice-chair hoping that would not take
much bandwidth (i think we do not need 2nd vice-chair things as such :) but no strong opinion ).
But the main issue for interop (i mentioned earlier also) is the maintainer for refstack and other repo. We really need
some developers for that.
---- On Wed, 10 Jun 2020 21:07:13 -0500 prakash RAMCHANDRAN <
pramchan@yahoo.com> wrote ----
> Mark,
> OK let me handle it as chair, but let's refer or nominate Ghanshyam too as second vice chair and if needs to vote it lets do that.
> I have submitted the change of irc channel to #openstack-interop as tested last week. and try pile all logs therein with startmeeting and endmeeting weekly to debate and arrive at how we proceed on this after tomorrows presentation which I like both of you to attend.
>
https://review.opendev.org/#/c/735034/1 > If we need anything to merge the above go ahead.
> Arkady as usual is with me on Board is there to help us all, so we do have two from Board and two from TC and community.
> So let me answer your latest email, and revise the presentation and web link for Board accordingly.
> ThanksPrakash
>
>
>
> On Friday, June 5, 2020, 12:32:07 PM PDT, Mark Voelker <
mvoelker@vmware.com> wrote:
>
>
> So let us wait and check with OpenStack staff how they can help us if they can fix the web irc/time links, if not I will try fix it over week end.
> Well, that’s sort of the point of having the meeting info housed in public repository: community members actually don’t need to go through the Foundation staff for things like this, they can just fix them with a few lines of text submitted via git! =)
> If you’re not sure how to do that, let me know…it’ll only take a moment to submit a patch so I’m happy to help.
> At Your Service,
> Mark T. Voelker
>
>
> On Jun 5, 2020, at 3:17 PM, prakash RAMCHANDRAN <
pramchan@yahoo.com> wrote:
> Mark,
> I see that using irc does help take notes for weekly meetings, especially if there is frequent meetings weekly alternate week etc.
> So let us wait and check with OpenStack staff how they can help us if they can fix the web irc/time links, if not I will try fix it over week end.
> ThanksPrakash
> On Friday, June 5, 2020, 11:49:22 AM PDT, Mark Voelker <
mvoelker@vmware.com> wrote:
>
> Prakash,
> Quick suggestion: since it looks you’re running these meetings on Zoom going forward, you may want to add the Zoom information to the upstream meetings calendar or alternately at least remove the old IRC meeting entry. See the "IRC meetings schedule” section here for information:
>
http://eavesdrop.openstack.org/ > The file that you’d want to submit a patch for is:
>
https://opendev.org/opendev/irc-meetings/src/branch/master/meetings/interop-wg-meeting.yaml > (Note that the times presented in the these files are in UTC rather than a local timezone.)
> At Your Service,
> Mark T. Voelker
>
>
> On Jun 5, 2020, at 11:06 AM, prakash RAMCHANDRAN <
pramchan@yahoo.com> wrote:
> Hi all,
> Prakash Ramchandran is inviting you to a scheduled Zoom meeting.To keep reliable zoom link have updated the weekly call to this one and see if you can join inspite of our ongoin PTG at 10 AM PDT.
> Join from a browser:
https://Dell.zoom.com/wc/join/99829924353 > Password: 101045
> Trying to consolidate what we got from PTG interactions to close the Draft updates.
>
https://etherpad.opendev.org/p/victoria-ptg-interop-wg >
>
> Closure in next week for Interop Guidline?
>
> What is the suggession for Board presentaion from team for Prakash on June 11th?
> Anything you like to add on the call, we can keep it short and try close after PTG next week.
> ThanksPrakash
>
>
>
>
>
>
>