150,000 Ukrainian troops fighting in new counter-offensive. Ukraine has deployed 150,000 troops to bolster its renewed counter-offensive, Politico reported, citing Pentagon officials. While multiple Western-trained brigades are attempting to breach Russian lines, the surge in manpower has achieved little and reportedly left Washington disappointed. Kiev has spread the 150,000 servicemen across three attack axes with the best NATO-trained units attempting to penetrate Russia's multi-layered network of defensive fortifications near the village of Arkhov in Zaporose region, the officials told the outlet. The Russian entrenchments have proven formidable with the Pentagon noting that Ukraine's gains are being measured in the hundreds of meters. Politico paraphrased, "'They are making mostly small, incremental gains,' an anonymous official said. They are still facing stiff Russian resistance, second and third layers of defenses. If Ukraine's supporters were hoping for a breakthrough, they were sorely disappointed. Politico surmised. Kiev launched its long-anticipated counter-offensive against Russian forces in early June. The Russian forces held firm and have mostly kept their discipline in the first seven weeks, absorbing one attack after another, often counter-attacking to recover lost ground and mounting offensives of their own in Luhansk and other spots on the front line where they sensed weakness. But Ukraine continues its counter-offensive.


We're at three minutes after and we've got 10 people in here. So let's go ahead and get started. Hey, let's do a quick review of the agenda. Take a look at the agenda and let me know if there's anything that I've missed before we get started. Anything you want to modify, change, et cetera. Into it in the chat as well. Are we good on the agenda? All right, let's start out with release updates with the team. Oh, sorry. And folks, don't forget to put your name in. Attendees section that lets us know who is here and maybe who might have missed in some information. It's important to some of the stuff. Okay, everybody. Go for it. Right. So the, the main highlight of the last two weeks of work has been release of forgetting for eight. It took us quite a while to to push it through mostly because of our strict. Upgrade scenario where there is no way for us to manually add an edge that we have to pass it through CI and CI runs disruption tests, meaning the test would fail if we disrupt services API or end user workloads using rather more than 1% during the upgrade. You turn over and bug, we were disrupting at around 10, 13, 15% in some cases. So we tried to push it through to prioritize it, but unfortunately it wasn't, hasn't been fixed. So what we now do is we run the tests, the very same test to it, but without disruption test. So now we can add an edge from for seven and OCD to for eight. Any further upgrades like from one for eight to the other don't need that hack and disruption is within the acceptable limits and so on. And moving forward, we would be more strict about this but this is a one time hack we had to do. And thus, we now have finally more or less updated cubelet version 121. I think it's to order for and we'll have cubelet surveys from now on monthly. Same as OCD does. In other news, Christian is probably not here. He's attending. He's attending keep con and I don't want to steal his thunder but apparently he's got quite a lot of progress on arm 64 images. So we'll wait for him to, to then all that. We're also we're working on their metal API progress. We have, I think all the beats finally in place in for 10 nightlies. Unfortunately, we don't have for 10 nightlies yet we need to push a few more changes to see and we'll have them available soon. Another topic we would need to discuss, not necessarily today but soon is the groups we to in for nine we have all things in place. And we just need to decide how exactly do we want to enable them probably the safest way would be publishing a guide how to do this today, all you need to do is just one machine config. Then we can enable it for fresh installations. And probably in for 10 we can automatically add this manifest in during an upgrade. But again, all depends on the testing feedback we get. And I believe that's all we have for today, there is some work to rebase the 410 to fedora 35 but we haven't really started the it's just in the plan so much to report on. Yeah, we should, we should consider the 49 nightlies have just started right so we should consider making 49 nightlies just do see Group B2 by default just. I think that, like, before we start getting to our C phases like we're just doing nightlies for nine. Let's just do it. Like it's not like the C Group B2 has been beaten the crap out of in fedora so since we run on fedora coral as as opposed to rel coreos, this becomes a lot easier because we already know that for the vast majority of cases that are in the C groups of flicks, things are in an okay shape now and so then it's really a question of making sure whether the rest of the integration points between open shift and and coreos is okay for this kind of thing. And, you know, they're nightlies right like people don't just get auto switched to nightlies. And if we have people like just trying nightlies, and we just straight up do see Group B2 or nightly upgrades to nightlies deploys to nightlies new new deploys to nightlies. Let's just do it and see how it goes because I don't know how else we will get like the requisite feedback to make sure that we're getting this right in time for like saying, do we want to do it. We want to see Group B2 for new installs on stable. We want to do it on upgrades, or do we want to defer upgrades to 410. I think the best way to be able to get that is just just start doing it in the nightlies and see how that goes. Well, I'm excited and I want C Group B2 now. The main difference is OCP is late and for nine cycles, so we can enable C Group B2, but if we find some bug in builds, uBlood or something like that, probably kernel's implementation is very good now for like, what's been like 10 years or something. But all other places are not that well prepared for C Group B2, so if we find a bug there, it would take us a while to actually get it lumped back to 4.9 because we have to wait the freeze before the GA and things like that, so that would take a couple of weeks. Next, how exactly to enable this, we can differentiate between fresh 4.9 installs, get C Group B2, the rest are remaining on C Group B1, we can do, everyone gets Group B2 unconditionally, we can do, here is a guide how to enable it and we can have a dedicated CI job to do this. I'm thinking fresh installs is probably the safest way, we will automatically get this tested in CI. Yeah, my main concern is that existing things like builds probably would take the biggest hit, the Qubelet is probably well defined out of work with containers and C Group B2, but things like builds are probably the riskiest part and showing this to the new installs would be the best solution. Okay, so I think we have a tracking ticket somewhere and I will post an implementation guide there and we'll see where it takes us. Okay, I mean I'm fine with us doing it for new installs with 4.9 now if we want to. I just, I want to just push the button, I want the button to be pushed for C Group B2 basically as soon as possible because like part of the problem that I've seen so far with the C Group B2 stuff is that we're now stuck in this catch 22 cycle of pain where like we can't shake out the remaining issues with C Group B2 until people just straight up start using it because that's what happened when Fedora switched to C Group B2 by default like literally zero of the container tooling, virtualization tooling, etc supported C Group B2 until the forcing function happened. And because choreos reverted that when they, when they, you know, made their releases, we never got that back pressure into the Kubernetes world to fix this, because nobody was really doing anything with it. And I just really don't like the fact that this has just been stalled out for so long and I and a lot of the underlying runtime stuff has been fixed over the years in, you know, 122 Kubernetes 122 which I think is what the relationship for nine is actually based on has support for C Group B2. So at this point I just kind of want to. I want us to be a proper forcing function here, because otherwise I don't know how, how it's actually going to like get over the hump. Basically, I think we understand at this point, get bit given from the, the amount of UPI problems that are CI is not a good substitute for real world interactions. So, while the CI definitely covers a strong subset of it. I want us to just start having users just, you know, follow the normal steps as if they were doing an open shift deploy, and get, you know, OKD 49 on a fresh install with C Group B2. That's the only way to get through it. So I think one of the things if we look at, and actually Timothy is going to be talking about this in a second, if you look at like the F cost group. They have a testing day or testing week is the case maybe it might be helpful to actually organize that for something like this call out to the community and say hey, here's something we particularly want to test. If you click on the link to the, but Timothy is going to talk about there's, there's basically a matrix that people can check boxes for installation, etc, etc. So that might be one way to approach this is to call to the community, provide them something that they can easily fill in to let us know how it went. Right. Yeah, for sure. Yeah, who wants to be in charge of that effort. Who wants to do the initiative of creating a little grid or pending something that we can send out to the community. Anyone. Yeah, I get the idea. I think it's a great idea. Yeah, it's a great idea. I just, I don't have time right now to do that. I'm already like strict super thin right now. It's a great idea. So someone has. Yeah, it's a great idea. I just hope I hope my enthusiasm would make someone else also enthusiastic about the idea. Like I just got my first demo okay before a deployment run POCO deployment working. Just just the past day in our open stack so like, it's been it's been a rough ride so far. My colleague is going to start filing issues and submitting documentation PRs for some of the stuff that turned out to be the words I would say are not quite right. Because we encountered some interesting quirks in our in our open stack based deployment trying to use IPI. Mostly in the realm of like, odd wording in complete information in some cases and like, just some missing coverage and stuff. We've got some hands raised I want to make sure we get to the folks that have their hands raised. Mike, go ahead. Yeah, in general, like I totally, I totally agree with Neil's kind of optimism enthusiasm, etc here I like the idea of getting the groups veto kind of out the door getting people using it. The hesitancy or the I guess the only thing that would be kind of concerning to me is that like yeah we get it out there and get people installing it. And then we get like a glut of people who start to have issues based around something there, which is what we want. But then like how do we manage the other side of it from the OKD community side like is there someone who's going to be helping to open bug zillas or, you know, like, having someone in the community to help organize this effort in both directions. I think would be really useful. All right, why don't we do this? I'll do the guide Vadim has has volunteered to be the point person on this. So Vadim and I will do the setup for it. And since I actually did a little bit of work on the F cost is working groups, testing day stuff. I can sort of duplicate the same thing for our group and we'll go from there and we'll check in at our next meeting and let you know where efforts are. Okay, Neil, we're going to get you at some point to do something though. We will rope you into. I'm sure I mean there's there's already a couple of things I'm already working on and then the fact that like, I'm finally getting an OKD deployment. Working in our in our internal open stack, you know, with IPI, like is basically like, that's been like the starting blocker that we've just struggled to get over. So now that I can have this, I need to make this deployment reproducible so I can blow it away and make it again and again. And then once that's all shaken out. I'm hoping that I can actually start doing some more interesting stuff because like part of the blocker has been for me is that it's a little difficult for me to do more than just like kind of cursory look at things try to know guide people about that kind of stuff when I can actually get the bloody thing running. And now that I have it running a sort of, maybe, I don't know it just started it just started working last night so like that's posted on your efforts for sure so that we know that you've got that well ideally we'd have a matrix of okay so and so has access to such and such resources. That's kind of like, that's kind of I think where we want to go here because like. Yeah, I haven't had time to basket the glory like it literally started working at like eight o'clock last night. And then dad and I were like, okay, we're done. We could finally log in we spent like, we spent a couple of days trying to figure out how to fix the networking so we can actually access the open just posted that was just a whole different set of issues. So, yeah, like, I think it's actually a great idea if we can get like, you know, community resources, community matrix of some kind of like, people are using okay D in this particular platform and configuration, so that when there are things that we need to test. We have a fast track to make sure that those things can be evaluated like, for example, like my hope is that with our new open stack deployment that we have internally that we're running. Okay D on in our proof of concept setup right now and I'm hoping to figure out how to productionize it eventually. That will make it easy for me to go into the future and say like, hey, we need to test this thing. Can I just like, you know, YOLO a few resources on our in our internal open stack to just do some testing and stuff and I'll blow it away afterwards and they'll be like, sure, why not. And that's the kind of thing that like, that's what I'm trying to move towards because that way I can say hey, you know, for open stack IP I stuff, I can help. Right. And that's that's the kind of thing that that's really where I want to get to next because like, it's a little hard for me to do much else without having the first part in place and I know, you know, I haven't, I haven't actually said it all this much but like this has been like one of the problems with trying to do stuff up until now so like I'm super excited that I finally have something because it's a real it's a huge also okay before eight looks super cool. Like, laying around with the UI it's very very nice. Anyway, um, all right well we keep us posted and let us know if you can do more than log in and, and, and automate that so that'll be helpful. In similar news actually I have access to vSphere again so I'll be doing my vSphere based testing again and using my stuff which pretty much automates vSphere UPI. Let's see, who else had a hand up someone else have a hand up anyone. Okay. Okay, let's, did you have anything else Vadim, did you maybe as we transition into F cost did you want to talk about issue 210 and okay to machine OS the conversation that's coming between J11 and yourself and through what that points to. Yeah, we circled back to rather, the Rock West team has reached out and told us that rebuilding the Rock West is a bad idea. Um, I don't know. Sometimes we must have different package versions that certainly not ideal so we would need a way to overlay the necessary RPMs and we don't want to go back to unpack RPMs and layer them as files that's the, that was a terrible decision. So now what we do is we take a list of packages to request installs batch them add additional ones and make our own floor across like each operating system. That's also a terrible solution but on a global scale a better fix would be open shift with rather machine config operator would one day learn how to layer different images which contain always three comments and pack them together, and you would have a properly function system but we're pretty far away from that. And the short term goal is to reuse as much as possible to reuse artifacts built by Fedora course project as much as possible so that we could just simply add a couple of packages from us and some configuration files but there are lots of hurdles in a way. I would appreciate some looks into the discussion we might want to move this to slash okay the repo. Because we also want to have a failsafe way to pin some particular packages like we have to do now due to Kubernetes issues but we also don't. I'm not very excited about to building operating system on every full request. So, that's going to be a long discussion but it feels it would be productive and that would help us shape the whole open shift. And a new fashion gives it was mostly the change of why and earth are we building an OS on every full request it's us and braille cross well changing how open shift eventually would start overlaying different always three comments on one system dynamically just building them from a bunch of images. So, I recall. I think it was like six months ago. RPM OS tree gained support for being able to enable and layer modules onto it so like the modular cryo can now be layered per matching versions and stuff like that. And I think a few weeks ago I want to say with the last RPM OS tree release, you now have the ability to replace based packages with over with layered packages. So like if you want to delete a package and or replace or swap out something. It's under RPM OS tree EX I think it's replaced or something like that. I forget what the sub command is, but basically the API exists for now being able to do mutations like that. Without having to rebuild the entire base OS tree image. Which I think is necessary for certain particular configurations with open shift. You know, switch from a non modular to a modular version of a component in fedora coral s, which may be necessary for something like using particular versions of run C or C run or whatever that have both modular non modular variance. So that should actually be in place now. I guess the the remaining effort would be to wire it up demco if I'm right, Vadim. Yeah, but it still doesn't. It's great and that might find its uses, but that's not the problem we're facing right now. So we initially hit the modularity problem. We kind of worked it around by fixing upstream cryo builds in open susu.org. All of them as plain repos and we just mix in the repo there so what switching back to modularity might be a solution which we would pick but that just feels like additional steps because the very same people build it upstream and the very same people build it in fedora. Why would they bother running to build instead of just one. When it comes to replacing a package that might find its uses but again, some packages are not that easy to replace for instance we're now hitting a problem where we have to roll back the selenux policy. That also brings a bunch of dependencies so probably we're missing some of the updates because of that. And a simple swap of the RPM won't fix it the same problem would be if we would want to swap. We might not be able to see but on a much larger scale of course. So these are the problems we would need to discuss in this ticket and find a decent solution. Perhaps we might have to fall back to rebuilding in some cases and the usual happy path would be using the orc or s artifacts so all the cars are on the table we just need to pick which ones to which features that we want based on. Quite extensive periods during the last two years we had all kinds of failures so I think we have really good set of features we want from from the system. So how do we move forward with this then how do we how do we tackle this do we dedicate a period of 1520 minutes to every meeting and start discussing it or how do we approach this. So, yes, this ties into the future roadmap for federal courage so can you make it correctly first. Okay. The main idea is that we're trying to move to model where we have a base image and where we allow people to have customization. We have layers that you would ship, just like we ship container images with the base image and layers on top. And so the idea that our industry would be able to pull basic image and then apply layers on top on the OS directly which fits really well with the MCO model where we essentially ship the OS as a container. We would just ship like so specifically use on top so one layer would be for example cryo and everything like that, or potentially it could be any replaced packages or think that that would be of use for for Katie. We're doing that both for federal careers and our course, red out chorus, the open shifting in general. But the idea is to make this generic but not fully generic you won't be able to do all the changes you want in the in the US but like that replacing packages until that would be actually possible. So yeah, the basic idea is not that we don't like people rebuilding federal chorus. It's that when people do so well they lose all testing that we do. And essentially we lose all the testing that that everybody else do. So it splits testing into and so that's not great for us. So that means that we essentially never test a well we never ship anything to keep you directly and OCD never uses for the record is directly so we don't, we cannot really use OCD to test for the process in CI. So yeah, the basic idea is that we try very much to bring us to closer so that we can in the end. So that means that we run OCD and to end testing in CI, for example, in federal chorus, at least for the releases, maybe not for PRs and I think that at least for release like making sure that when we do release passes and to enter single OCD, which will be like basics. So yeah, so that nicely turns out into the notes of this meeting. Which is yes, which is around testing mostly so we have a testing week right, which happened, which is happening right now where we're focusing on federal certified changes. So we're rebasing for federal certified this time we're going to try to rebase really really close to the federal certified release so it's going to happen like something like the day or the week. So they like details but it's going to happen really really close to the release. Right now federal certified so the next stream is based as sort of the federal chorus, the next stream is based on federal certified and the testing stream will be based sometime later. So any help here to test would be great and hopefully. That would break too much things in OCD too. That's where we're in the most testing probably. And yeah, and so we have full AIR 64 support right now you can find the artifacts on the download page and everything like that. And on the same year on the same team or testing we're trying to bring Kubernetes upstream. And this is doing end to end testing on federal chorus node with cryo and we're trying to bring that into our own CI so that we can at least for the release to maybe at the beginning. Tests that the upstream communities test us with cryo on federal chorus so all that should bring us much much more closer to having making sure that most of those things like work in the default OCD installation. You know, in federal chorus like we don't need changes of course. Yeah. And then potentially having a full OCD testing in federal or CI. So yeah, the goal of this is, is very much not to to shame anybody on on building federal chorus. At the point it's more about making sure we don't duplicate testing. Excellent. So, what I'd like to do is keep this ticket. And this is. Again, number 210 issue 210 in OCD machine OS it's in the notes want to keep this in our meeting regularly so we talk about this regularly so that doesn't slip by, and that we can continuously address it and also I'll make sure that folks have ample warning when the F cost testing is coming up so that we can leverage our resources to test F costs underneath the various OCD releases and try those together. Timothy, do you want to move on to the rest of what you have. I think I've covered most of what I have so if there are any specific questions. We can go ahead. Right. Let's move on now to docs Brian. Okay, so we've done most of the work to switch over the MK docs.io site. I think for red hat to change the DNS over. So, the most has gone to main, the github's automations kicked in that's all in place now. And the sea names being added to it. So, it's already just to switch over. As it says in the notes, we've incorporated and how to change the official docs. So that's the docs, okay.io, the product documentation. And we've also got a section how to update the okay.io site within the new content. If you want to have a look at it, if you go to the repo and go to the github pages and being served by github. You can actually see the new site. But hopefully soon we'll get that switched over in the DNS. Not really much more to add to that. Another thing that came up that I think Michael was on the call. Yeah, Michael's still here. So, Michael is helping us with an issue where there's 4.9 references and okay D docs. So, Michael is there any update on that. Yes, okay, we updated that main okay D docs. So docs.okd.io page now has version selector for 4.0 docs. And we dropped some of the earlier versions of three. Awesome, right. So let me know if that's what you all expected or any other improvements we can make. Let me know and we can take care of it. Awesome. Thank you so much, sir. We'll take a look at that and then folks, if you run into any issues or you want to see something different. Let the docs team know and then we'll bring it up at the docs meeting. We'll talk about that there. And Diane grabbed a code of conduct. And so this is pilfered from the Ansible folks because they actually ran it through a bunch of legal. So check that out and then we'll take a vote on it at the next full group meeting. Basically, the idea is that we'd have this code of conduct in place on the website and also announce it just like CNCF does at the beginning of our meetings. Just to make sure that the people are aware that any event or thing related to the group. Adheres to the code of conduct. So take a look at it if there's changes you want to make suggestions. Something's unclear or anything like that. Be prepared with those maybe write them out and send them to the larger group and we can talk about them at the next meeting. Any questions? I did create a docs PR. Okay. So if you do want to make comments, you can make comments directly in the docs PR. Okay. Or in the GRE issue either way. Okay. Excellent. We'll put a link to that up there. Oh, yeah, I should have done. I'm sorry. It's in the it's in the GRE issue. Okay. 244. Okay. Okay. And Sandro is not here. But you can see the updates there. And I'll read these off really quick just to, okay, so for the folks that don't know the okay virtualization special interest group of okay D. And why don't you go ahead and read these off since you're a lot of this deals with stuff that you're dealing with in terms of the website and everything. Okay, so they're moving their docs to okay D. And they initially did set up their own site so they have to have raised a pull request to actually move that over. That actually did raise a couple of issues around conversations we had at this meeting two weeks ago around social media. They created their own social media communities. So there was a question of. As this group, are we okay with that as we sort of decided not to do social media for okay D and having a work group that has a social media presence is that something that you want to support. So that's sort of an open issue. Initially they actually altered the dock page and they put a whole bunch of custom CSS and some HTML to actually put like a Twitter tracker on their page. Didn't like the way that implemented that so asked them to actually do that as a template. So the page stays pure markdown. They've decided to actually remove that tracker. So that's an open question on a pull request. Are we okay with their social media links. So that's an open question. Other than that, within the work they're doing, they've successfully tested for eight installation on bare metal UPI. And I've got a guide for it and they're going to put that onto a page on the site. And they're working with the root.io community to get root set operator to the community okay D operators, which I think is going to be goodness all around. And then they're working with assisted install a project to support okay D virtualization as well. I don't know if anyone knows any more about that. And then they're also adding automation for testing a hyper-converged cluster operator with okay D and I've got a link to that, which is in the hack MD notes. There's any questions come out of that. Ideally, we want an answer. Do we want to support social media? Are there any objections to that or how do we feel about that as a group? I mean, does it does it make sense for us to sort of promote their own social basically it's their social media, right that they want to have their own social media for the subgroup or special interest group as they're calling it. So the docs group sort of decided against doing one of our own and instead like having it go through the open shift Twitter and whatnot, just because we don't really have people to man, something like that ourselves right now. And plus there's a wider audience if we go through the open shift Twitter and commons and stuff like that. A lot of this depends on are they already using that Twitter is that already like an established communication channel for them that their users are expecting because if that's the case. I don't see the harm in having a section on their docs that says like, you know, for updated information go here. But I agree with Brian like we don't necessarily need to have the embedded, you know, iframe showing like the scrolling tweets that are happening in real time or something. Yeah, they do have they do have their their Twitter is established they have 62 followers. All of those followers sort of came at once. And it looks like they post every, like once a week or a couple of times a week or something like that since they started it. But there's not a lot there. So, yeah, I don't know that we'd want to scroll because if you have a scroll of social media that doesn't have really any updates it actually doesn't look so. You know, which is what Diane's concern was about ours, right? If we did. And I agree with that concern if you have a social media and it does anything like it kind of makes you look more dead than if you didn't have one. Right. Yeah, I mean. Brian and then Mike. Okay, I was just I also think in a way it's disconnected that group from the rest of us because they don't use any of the communication channels that the other working groups use this main group, the documentation group. And so I think several people on this meeting wanted to be involved in the project and nothing comes through any of you that okay D channels, you have to go and use their social media and to find out there's even meetings going on that they're not plugging into any of the established communication channels that the community would know about. We can we can fix some of those things. So for example, I have access to the calendar, the Fedora calendar and a couple other folks here we could add a Fedora calendar event for them. Which would post to the working group mailing list that automatically gets sent to the working group. I don't know Diane hasn't gotten back and in terms of how timely forwarding stuff through the OpenShift Twitter would be but we could theoretically forward either a fresh message or whatever could be posted directly from the OpenShift Twitter or the OpenShift Twitter could forward what they have either way. It definitely does feel splintered a little bit but some of that might be our part of being overwhelmed and not doing enough to get them sort of once their website is within ours then it changes things a little bit. Yeah, it just feels that we obviously want to support them and we want to get people using and testing and playing with their stuff. I just don't know how people find their stuff if they're on the either the Slack channel or they're listening to the Google group mailing list or anything. Well, let's I'll touch base with them. Diane was talking about setting up a meeting with them another meeting with. Let's set up another meeting let's invite them again because I think Diane invited them again. Let's try again to have them get some representation here. And this is another thing is is there all of their members are from one particular region. Right so it's kind of the inverse of the situation that we have right now. A little bit Timothy it's a little bit later and it's like what APM there's something like that for you. You know so it's it's a little bit later for some other folks here, but generally we can all sort of attend with them it's like very different, you know, availability so let's invite them again and then we'll go from there. Does that seem like a plan just to get more conversation going. I was just going to say like I didn't you know, like I give him what Brian's kind of talking about and what in the discussion here like it. I think it's right and there's less value to include like their Twitter stuff in the official docs. You know it's perfectly fine if that's the way they're going to you know they want to have their Twitter and kind of do stuff there but I would my preference would be to see like yeah how do we do outreach to that virtualization group so that we can get kind of the support of the full like OKD community behind them. So rather than saying well you guys have your Twitter and whatnot like how do we be more inclusive so that we can get your message out along the channels that you know we're preferring to use. Yeah, well let's do that as anyone interested anyone else interested in being in on a meeting with them if we have to do something sort of outside of the bounds of this meeting to accommodate their time anyone else want to be in on that. It'll probably Diane myself and Brian anyone else. All right, well, we'll do it Mike we hadn't in that direction. Yeah, I mean I'm happy to join and help facilitate however I can I don't I don't have a lot of specific technical knowledge going into that virtualization group but you know, yeah I mean I'm happy just to help from a community perspective. I think from a community perspective you're good at facilitating. So, let's do that. Let's move on now to before before we move on I had my hand up before I just I wanted to ask Brian a question, technical question about the docs. Are the work are the workflows there working properly because I I tried to clone something out of the workflow and one of the directories was not looking quite right for me so I didn't I just wanted to ask I you know I didn't open up a bug or anything because I wasn't the pool chain was a bit different than the one I was using so I just didn't know. And as far as I'm aware, yes. So obviously the automation, the automation is fully on. GitHub uses GitHub actions to do all the bills on on POS and if you find a problem, please let me know. Because obviously I'm aware people use different operating systems and then we may have to update the instruction so yeah just ping me and. No, no, I mean if it's if it's if you're seeing it working coming out of that repo then it was probably just a configuration issue that I was. That's all good. Okay. And this actually came up at the docs meeting is how do we document how folks can contribute to the documentation and you know. Being able to use pod like a container with like pod man to run the software and stuff like that to generate the site and stuff like that so docs on that forthcoming so that everyone can sort of participate in. Yeah, I'm also thinking of adding a dev file. So anyone that wants to use code ready workspaces or check can also do it on cluster. That would now that would be awesome. That would be super awesome. And big round of applause for Brian and awesome work that he's done. This has been like very, very helpful to fix our web presence. Okay, moving on to the next piece of business is the release change log. Vadim you weren't at the last meeting but this came up. And if you're still around here, can you explain a little bit about what happened with the chain logs and we've received several issues related to the change logs and the commits look like they disappeared. Yeah, they did disappear in fact. The problem is, we have two forks. And which is installer and MCO. So every time we make a new MCO release we pull in changes rebase hours on top and push them so the old comet unless it gets tagged or somewhere. It gets burned by GitHub eventually. And the change logs are dynamic. They are kept in cash so when I check them they are looking fine because the kid happens and pruned it yet. When I look back after a week, the GitHub has pruned the comet. Change log has been evicted from the cache. It tries to fetch it, GitHub doesn't find the comet and we get literally nothing. The current solution is we, well, we got away. The color is merged in for nine so that problem goes away, would go away eventually. The MCO issue still remains. My current workflow is that I tag with some nonsense tag like for seven and current date like October 12. Push the tags and so on. So the solution is manual just to make sure that GitHub keeps all the commits but coming forward what we need is well either on board or for correctly but that would prevent us from rebasing our changes on top we cannot force push comments there we would have to. We would have to merge all the coming changes between our comment and the previous one we were based upon so that's pretty tricky. Or we have to stick to well being careful and tagging the existing comments. There is a CLI command which can build you the difference between two images of the OC admin for as something like that you can build a change log between two so it's never gone but it might be unavailable for some time in release controller so that's that not much we can do about this because of the hacky way we build machine or machine configure brain store for some time. Can we add something to known issues so that people are aware of this so that if we keep getting tickets on it that we can just point them to something without having to repeat. Yeah probably it would be a good idea to file a PR which mentions that they get in the known issues so that we won't have duplicates. We can also come up with the manual work around finally codified properly. Okay. Good. All right, there wasn't anything did anyone want to pull anything out of the discussion section of the repo did we have any discussions come in that were. It out in any way I didn't see anything and pull anything out but if folks saw something they want to discuss real quick we got a few minutes. Okay, and. New business and this brings it up so location of the main. Main community. Vadim we talked about this at the docs group we talked about this at the main group meeting. Two weeks ago, the idea is that there's a lot of bush to get a set of repo that we can all participate in. Right as opposed to this current one. Basically it's you and Diane, some people who aren't really involved much, you know and Christian I think. Is there any downside to just a new get repo and moving this stuff over. Obviously Diane's going to do some looking in terms of like any legal stuff she said she was going to do that. But do you see any downside to just moving issues and discussion. And the other sections into a repo that we can then access to that more people can participate. Now they will work, but the problem is that we cannot be part of open shift organization because everyone there has to be. That had employees and it's like centrally controlled by CI. Moving out of the org maybe a new work. Yeah, it's just a matter of naming. Maybe we should move to give lab or some. Finding a nice name. Yeah, open shift CS organization. Diane can find us somebody who can create a repo is just as well post sticks there so well so in the docs meeting we talked about that a little bit and apparently that's the open shift CS stuff. Is to people who like gave her access and ability and those people have like moved on. And there's other people who've moved on and they've changed their name multiple times. So the just the docs group in the discussion in there and the discussion at the main group had two weeks ago was just a completely fresh org and repo. So not connected to do you see any downside to that. That shouldn't be if OQD is OQD is an organization that would be nice, but we will still have quite a long confusion period where people don't know which repo file to get said and things like that. But other than that, I think, I think it should be fine yeah. Does anyone else have any thoughts on that is anyone opposed to the idea. Is there a downside that you think makes it more. The benefit smaller than the downsides. Okay. I guess everyone is enthusiastically. Oh, yeah, go ahead. Yeah, yeah. Did I miss here? I thought I heard Vadim say get lab. No, I he said get lab. Yes. And I seconded that. Yes. And so I'm using get lab as well. Self hosted version. But the world seems to be against us. So maybe Vadim could say a little bit more about what was in his thoughts. So I was just thinking we could have a nice URL get lab.com slash show kitty or maybe slash open shift. And how it's there so that we would not be controlled by our CI which prevents us from using it. My only concern is naming a lot of problems. I'm pretty sure we can tackle. If we can use different get hosting for our repos. That sounds good. I'm pretty much open to suggestions, just a matter of getting a cute name so that. We could list them all on our pages and people would not get confused where to defile issues and where they discuss different stuff. And I'll be honest, I like get lab a little bit better just from a technical perspective. So. There's a little more because they also have a troll like task word. Yeah, which I haven't found on GitHub yet. Pretty much. They have one. We've used it for the meetings early on. Yeah. The get up 1 is just bad, but that's the only problem with it. It just kind of sucks. It's super hard to connect to issues and things like that. And it's, it's not. It's not easy to connect them to work connect work items to task items to schedules. Like. It's, it's a very rudimentary and frankly, quite annoying implementation. As opposed to both get lab and packer, which tie. Cards on the board to actual issues themselves. And so the tracking of work items is synchronized with the tracking of issues. Yeah. All right. I don't want to spend too much more time on this. We've got 4 minutes. We've got a couple more things to do, but it sounds like everyone's on board. At the next meeting will devise a plan for starting to move things to a new place. And at that point, Diane can chime in with what she learned from legal. CRC subgroup. Sorry, Timothy. Yeah. We can't hear you. We can't hear you. Okay, sorry. My only concern is moving to get lab is how much pro support do we have in get lab like can we still use the currency? Everything was it just for non production repose. I think the idea is that we are not using prow anyway for any of our stuff as the okay to working group to begin with. So it is a non factor. So nobody, nobody in the working group can use prow at all anyway. That is deep control by employees. So it is not useful to all the rest of us. Okay, so that we will move essentially. All the non building repose to this organ keep like. Okay. Yeah, exactly. It's that weird thing with red hat where they have open source projects and they support community except you can't get access to the resources for those projects to do. You can, you can make the ours. And we can approve them that they're safe to test because you can make a malicious PR which exposes some of our secrets. That's the reasoning behind this. You cannot be the owner of the repo. So I'm not feeling excited about okay to testing every single PR we do for our working. So probably prow is just not a good fit for us, but anything code vice anything which lands in okay the release image. It absolutely must use get have it absolutely must come from open shift. Repose and must use a prow. Yeah. But in terms of management, the website, the documentation stuff, any of those things. None of those have to none of our working group items have to none of our scripts none of our tools none of those have to. Right. Exactly. Okay. CRC subgroup. Neil, do you have an update on that? No. That's fine. That's fine. Fair metal testing CI group. There was discussion about that. We'll talk about that next week. Or next meeting. The office hours is tomorrow at 5pm Eastern promote the link. Oh, I don't have the link there, but I'll put the link in the document shared out for your social media Diane has shared out via Twitter and whatnot. And it's myself and Vadim you're going to be there. Who all is going to be there it's Charo myself Timothy. And I think there's like four or five of us that are going to be there so it'll be lots of fun it's only half an hour but hey it's something during Goop gun, which is cool. This will be the last time I think that we have Chris short sort of narrating for us since Chris short is moving on greener pastures. Okay, I think that is it. Anyone have any last minute things. All right, well, cool. Yes, please promote the event tomorrow and Vadim and I will talk about the things that we have on our task list. And there will be a new task list written up based on this that will be added to the notes and then I'll send an email out with the tasks and who's responsible for them. So that we can be a little more timely with our tasks and a little more on top of them. Awesome. Thanks folks. Talk to you next time.


Welcome to Tick Mill Weekly Market Outlook for week commencing the 22nd of June with me, Patrick Mullerly. It appears that the markets are trying to come to terms with the daily swings in the new US coronavirus cases, although the increase in total daily cases is now above 25,000 mark, this does give some cause for concern and we did see some late weakness in the equity markets on Friday. Looking ahead, the market will be paying attention to a couple of key themes. One, news on US relations with China and any news about a fourth US stimulus package will also be closely watched. This is expected to be announced before unemployment benefits end in late July. On the US data side this week, it seems that there is a slight slowing in the improvement in the employment situation. Thus, Thursday's initial and continued claims will be closely scrutinised. We'll also see May existing home sales, May durable goods orders and final reading of June consumer sentiment. We'll also hear from the Federal Reserve's Charles Evans and James Bullard. We'll expect then to echo with HomeSeachare Powell's view that the recovery will be a hard-fought battle. Note, however, that the financial system seems healthier. Drawings on the Fed US dollar swap lines have dropped to 280 billion from 445 billion over the past couple of weeks. From a technical perspective, the dollar index has stayed a recovery from the symmetry swing objective at the 96th level. We're now just coming into the first level of resistance here with Friday's close up towards this 97-70 area, which is symmetry swing resistance versus the last corrective phase in the dollar. Looking early in the week to see if we get a key reversal Monday, Tuesday, which then could set the tone for the next leg lower, certainly to retest prylos at 95-70, ultimately on route to the 94-60 objective. However, if we don't get that early reversal, then I'd be looking for a move higher to extend up into the next resistance area, which is the equality objective versus this structure at the 98-20, and then we also have some sending trend line resistance at 98-70. So again, watching for bearish reversal patterns in this zone to set short positions, targeting certainly the retest of the prylos, but ultimately looking for a move down into this 94-70 area. The euro experienced some late losses on Friday in the wake of the European Commission's Recovery Fund meeting that concluded really in no accord, but some consensus on certain parts of the proposal and crucially perhaps no critique of the idea about mixing grants with loans. This week, the European Data Calendar will focus on the flash-dune PMIs and the German EFO. Look for further modest improvement in the EFO expectations index, but it will take some time to return to levels seen at the start of the year. Any manufacturing PMIs above the 50-level, however, would be great progress and could certainly help the euro. Given the big take-up in the ECB's Teltro 3, we could see peripheral debt spreads, particularly at the short end of the curve, continue to be contained. From a technical perspective, the euro dollar is set now to test its equality objective at this 1,1140 to 1,1150 area. If at the beginning of the week buyers step in and take advantage of the pullback, then I'd be looking for key reversal patterns to set long positions, ultimately targeting a retest of the year-to-day highs at the 1,1490 area. However, if buyers fail to step in early in the week, then I'm looking for a deeper corrected pullback to retest the area of the 1,1020 to 1,10. Again, watching for bullish reversal patterns if we do trade down to this area, as this will provide a set-up on the long side, certainly to see us look for a retest of the 1,13 handle in the interim. Despite the Bank of England's delivering a tapered version of QE extension, i.e. the pace of asset purchases set to decline in the remainder of the year, Sterling failed to benefit as the market remains focused on the odds of negative rates. While not discussed at the BOE meeting, it was not ruled out by the governor during the press conference. This is important for Sterling's prospects as the stalling of the UK-EU trade negotiations suggests that the market will likely take a glass half-empty approach and keep Sterling risk premium in place, both from the economic side as well as the possibility of negative rates. On the data front this week, UK June PMIs released on Tuesday should continue their gradual recovery after the COVID-19 induced slump. Despite the increase, all forward-looking indicators should remain in contractionary territory. Given the volatility of PMI numbers, I don't rule out an upside surprise this week, but this is unlikely to have a long-lasting effect. No key negotiations are scheduled on the trade front. Sterling weakened into the close. We're sitting, as with a bunch of these pairs at the moment, at the equality objective of the 1,2320. Again, if buyers step in early in the week and a key reversal Monday Tuesday could look to set long positions from this area, certainly targeting a retest of 1,26 and the descending trend line now coming in at 1,2758. However, if buyers don't step in early in the week, then I'm looking for a move down to test support at the 1,21 area before we might see a recovery. With the reflation trade on hold, at least until investors feel more confident about second wave COVID risks, the dolly yen has sunk back into range. One month realised an implied volatility is just above 6% compared to levels above 10% in early April. As such, the dolly yen's daily correlation with the S&P 500 is not particularly high right now, suggesting the JPY story remains in the crosses. In the week ahead, markets will be watching Japanese foreign bond buying. After a very quiet few months, Japanese purchases of foreign bonds have picked up over the last couple of weeks. This may owe more to the greater confidence in the foreign debt story rather than strategic buying of foreign bonds when the dolly yen approaches that 105 handle. But a consistent pickup in purchases will start to attract greater market attention. From a technical perspective, dolly yen is sitting just above the 10650 area. I'll be looking for a move down to ultimately retest the 106 recent cycle lows enroute to the ultimate objective of this equality target at the 10430 before we could see a more material recovery in the dolly yen. The calendar for next week doesn't show any key releases for Australia. With some attention though, we'll be given two remarks by the Reserve Bank of Australia. I'm going to fill it low on Monday. The two hot topics for the RBA now are one, the tapering plans and two, whether the strong Aussie dollar is becoming a factor in monetary policy decisions. Next RBA meeting will be on 7 July. China-related sentiment has started to creep back in as the main driver for the Aussie dollar and this should continue to be the case. Despite some encouraging signals that the second wave in Beijing may have passed its peak, news of transport disruptions following some new restrictions may hit appetites on the China-sensitive currencies which are specifically the Australian dollar. From a technical perspective, we close on Friday. I'm looking now for the Australian dollar to test the equality objective at the 6680 area, certainly against Friday's highs at the 69. So when we get down to this 6680, I'm looking for bullish reversal patterns to set long positions, ultimately looking for a test of the 71 handle. If we fail to find support at the 6680, look for a deep correction to the 65 handle before we attempt to set another base. That concludes the weekly market outlook for a week commencing the 22nd of June.


Hi everyone. Can you see my screen Susan? Yes. Perfect. Hi. I'm Susan Tenby and I'm going to talk to you about the events piece of community management and ways to kind of bridge the online and offline so that you use events as a way to punctuate activity that's happening with your online community and to bring your community together between your events. So me, I'm Susan Tenby as I mentioned and I am a social media and community builder. I have been with Tech Soup for I'm embarrassed to say 17 years so quite a long time doing online community and offline community building the entire time and you can reach out to me after this event or at any time at Susan at caravanstudios.org Caravan Studios is the division of TechSoup and at SUZ BOOOP that's Suze Boop on Twitter and you know the my title with Caravan is Community and Partnerships Director but really a lot of what I do has to do with events and I also manage so I do a lot of on on the ground events and I also manage all these online channels that you see right here mostly primarily Twitter and Facebook but these are just the places you can find us so we have public good app house Facebook group we have Caravan Studios non-profit Facebook group we have a Caravan Studios and safe night app Twitter account you can see the rest of what we have this is just a sampling of the community online that we manage between events and the kind of events that we run for Caravan this is the main event series that I run for Caravan which is the apps for change demo series and it started a couple years ago we have approximately six events a year sometimes a little bit more and these on average I have about 150 RSVPs with about 30 people 20 to 30 people on the waitlist which translates into about 80 attendees in the real room they're all live streamed and as you can see these are events that showcase apps for social benefit these are demo events where people from the tech sector and engaged community members and app developers who have built public benefit demo them to a group of people in the room that are half nonprofits and half technologists who care about social benefit and public good technology and what you're seeing in the upper right is some online excitement from these events on Twitter using that hashtag apps for change demo and the other series of events I run is I run a monthly event called OC tribe which stands for the online community tribe and that's an evening event the other events I was talking about or morning events and this is a monthly meetup that's been around since 2006 and it has about 50 RSVPs online which translates to between 15 and 20 on the ground attendees it's run by volunteers entirely and it's really a networking event whereas the other one the previous event is an event to showcase social benefit apps and try to get people to use them more this event is very much a networking event for people who do the kind of job that I do which is online community and on the ground community management and these events start at seven and there are kind of evening networking events with a short presentation the man you see presenting in that photo is from Adobe and these are ways for us to showcase our sponsors but also ways for junior and beginning community managers to talk about what they learn and to share best practices and share their expert tips with a friendly group of other community managers and this group actually yielded $21,000 of sponsorship money last year so even though it's a volunteer run group it's been pretty helpful for us getting sponsors and these are the online channels that exist for that community between events so we have a YouTube a Facebook group a Twitter handle sorry a Twitter hashtag which is OC tribe and the meetup group itself as you can see over 2,000 members and although those events are very different they are some there are some similarities which you can expect with most events in general and so this kind these kind of similarities you think that these types and all events have in common are for example you might have noticed that in both events even though the numbers were scaling very differently 50% is a really good expectation for a free event so if you have a hundred people on your RSVP list 50% is a good is a good day so might be 40 people that show up just so that you know free events even though there might be free beer do not always yield 100% attendance and actually in all my years of throwing events and they've all been free we've never had anything different than 50% sometimes 40% attendance so just to expect that and also the ways that you can kind of expect across events the best attendance would be to send at least three reminders don't be afraid to over remind people because if you think about your own behavior on the web you're you're gonna appreciate a reminder you get we all get so many email that we really do appreciate getting over reminded and you want to remind people across channels so you want to send Twitter reminders and Facebook reminders and reminders within the meet-up or event bright or whatever event tool you use and some email because you know you want to meet people where they're at and some people are only on Twitter and some people are only on Facebook for example and you want to make a graphic for your presenters to help them share the meet-up widely so that might be you know we call those assets visual asset and in that you also want to craft some prefabricated tweets and some Facebook message and some email sharing messages and don't fall into the trap of including too many because then people just get option paralysis and they don't really know which one to choose so it's best to just kind of include two tweets a link to a tweet they can just hit the retweet button if they're feeling a little lazy they don't want to do their own tweet and the same goes for Facebook maybe one Facebook post and a link with a Facebook post to share and with that you want to make sure that your Facebook message is set to public so when people share it they can share it widely with their networks without having to have some kind of restriction on where it can be shared and similarly when you ask them to share you want to make sure that in your tweets you mention all the critical information in the tweet don't just include it in the graphic I feel like that's a common stumbling place where people include all the information in the graphic as if it's a poster but what they don't realize is that when people are viewing Twitter through a listening dashboard or you know some sort of XML reader those images often just look like an image link so that all the critical information is lost so make sure you include the date and the time and the topic in your tweets and also finally you want to create an atmosphere not only that's easy for your presenters to share but you want to create a shareable environment so you want to pick presenters that know how to share on social media it's really critical because otherwise you're very much working on your own so it's much it's much easier for you if you pick presenters who have a big audience and know how and what the best strategy is for sharing their own talks and you want to make them you know hold them accountable for it so as I mentioned you want to give them some pre-crafted messages to share and coach them on speaking not only about their product so it's not going to be a sales pitch but it's actually you want to coach them to speak to the audience that they're speaking to but also remind them to and get their agreement to share at least three times with their network so what you see here below is one of my speakers from the OC Tribe event Nicole Banks I had her present not only from her own share it not only from her own Twitter account but also from the Twitter account of her company and Albert Chan spoke at OC Tribe and he has a large he is his own brand and he has a group called Albert's List which is a very popular with tens of thousands of members job sharing tech group so I just got his commitment to share on his own account and to use our trackable links so I could see and I gave it's important to give them the right hashtags so you can see that he used our own hashtag but he appended some other additional hashtags to catch some other people who might be following for example the hashtag SF and the hashtag events with a hashtag social media so that that's an example of you know picking your presenters who really know how to share and holding them accountable so that they really help you with your work of filling the room and one of the documents that Susan referred to earlier is a pre event checklist so this is for the people who are helping you put on the event this is the equipment so things just so you aren't kind of stuck on the on the day of the event going oh my goodness I forgot my tripod so you want to it's just easy to have this you won't forget anything if you have this list on hand and like for example we note that we need two iPads one for Facebook live and one for the timer of the event so just making sure that you fill out a checklist you have it as a template and you use it for every event and it's a physical tech checklist that you can share around and similarly the run-of-day sheet so you want to create an agenda that has the flow of the event so that you are so that you are working with a group of people who know exactly the timing of everything going on you're not just kind of operating on your own they know that by the time on this event for example for 1040 rolls around the welcome announcements are going to be completed and the demos are going to start so this is to share with not only the producers of the event but all the presenters and anyone who's kind of behind the scenes so that we also included that and here I'm going to show you a little video because volunteers are similarity across all events and they're critical to your event success so I'm going to just share a little one-minute video really good experience I found out about the media manager finishing school I kept it up with Crystal, I'd seen her in a few other events and seeing a TV manager was tough with mine I ended up getting a job as a TV manager at Infinity Live for a TV company and I'm totally loving it and it's so nice for the media and that was really just paying it forward because when I moved up here about three years ago I did have connections did have an hour and this was one of the first media groups I found I tweeted a lot at it and volunteered for the group and that ended up getting me noticed by the community manager and me who brought me in so that was a video from my volunteers at the OC tribe online community media group and as you can see you know it ended up getting her Crystal a job at Google starting out as a volunteer so you really want to make sure that you help your volunteers grow skills that are portable for them and that are valuable and marketable so that they can find the volunteer role valuable and help share it out so volunteers and recruit more volunteers and retain them and you want to make sure that your volunteers really have autonomy and ownership of your community and of your events and you want to keep in clear contact with them so that they're engaged you want to have kind of regular volunteer meetings like whether it's monthly I do kind of quarterly just to get their feedback what's working for them what's not and I send out every single meetup of volunteer lists like this which these are the needs that I have these are the things that I might need like I need somebody to buy name tags something that you might not think about but you just have to kind of put all the needs out there and let people sign up for the roles that they want this is really critical and I also as Susan mentioned included something like this for you but just to remember all the pieces so that you're not stuck on the day of the event without any people to do cleanup for example and sponsorship I just want to talk about sponsor love for a second don't be shy to mention that you're looking for sponsors sponsors want to tie themselves to events that are successful with happy volunteers so at the beginning of your event and at the end of your event looking for sponsorship open for sponsorship opportunities mention it on your meetup or event pride page create a sponsorship kit so that if somebody is interested you can quickly just send them something like hey right away I can actually send you this kit so create it ahead of time like a pdf kit with a video like that maybe or something along the lines of a presentation for your sponsors and you want to highlight your sponsors at the beginning of your event and in slides when people are walking in the room and in voice when you announce so you can see me on the left here giving my sponsors some sponsor love and then I announce my sponsors as they come in in a separate dedicated email through the tool through like meetup.com or event pride or in a separate email giving them that kind of benefit and amplification and then again thanking them after the event on social media and finally make sure that you create unique value for your sponsors whether it's coming in and doing a focus group with the special membership or providing swag or asking your members for to fill out a survey but provide them with unique value that they wouldn't get by just attending your event and back channel super important so the hashtag that I showed you earlier OC tribe during all my events all my all of my events always have a dedicated hashtag so people can follow along between events and also during the event itself using a tool like tweetwall or twitter feed or twitter fall these are these are tools that help you show the back channel for the people watching remotely while they're watching on facebook live and they can respond to questions and answers using the hashtag but also a lot of these people have these hashtags now put into their hoot suite or whatever twitter listening dashboard they use so that they can be a part of the community between events that's kind of what I was talking about the pillars to hold up the community between the on the ground events and remember to have purely social events like happy hours so that you're understands that this is a networking there's value in attending and build in networking as well to for that matter into your events because that's why people come in real life otherwise they would just watch it online but the reason that they would come on the ground is to talk to other people so that's really important as well and the video from the live event that I mentioned is really great for archiving so you can do things like create bite-sized videos like one minute videos to repurpose they're great for seo you can edit together kind of a montage of people talking about your event itself and use that in your sponsorship kit you can get these you can caption these videos so that you can people can watch them as you know 80 percent or you may not know but 80 percent of video is not watched with sound so you can caption these videos and make them into sponsorship videos or videos about what you're doing and curate playlists on vimeo and youtube to share around and finally you want to make sure you recap your events using all of these elements so tools like story fi help you put in the videos as well as the hashtags as well as the compilation of the tweets from and facebook posts and advertisements from other people all around the web and to one easy to share link that is a story essentially and that not only is good for seo but it helps you kind of share your event between events and give a final boost of amplification to thank and reward your speakers and with that I am done with my part of the presentation and open for questions great thanks so much Susan you shared a lot of really important content and I want to address a couple of questions that we got in one is the folks that don't attend your event per se but they watch it in the recording how do you both identify the metrics that you're using and how do you collect that data and then try to make the event better or try to reach out to those folks who maybe couldn't attend so often when people are attending the event virtually they still have rsvp'd on on the meetup site so I I always send a wrap up survey I use kind of like a survey gizmo type tool either survey gizmo there's survey monkey there's jot form but I use an online survey tool and ask them the important thing about serving is that you ask very very limited amount of questions otherwise people get survey fatigue so I might ask eight questions to get their feedback and in terms of collecting the data I just kind of I capture how many people signed up versus how many people attended versus how many people online if that's the kind of data you're asking about yes thank you thank you thank you for clarifying that another question we got I know you're actually really good at this can I see you do it how do you get sponsors if you were just starting out and some of the folks on this webinar are brand new they haven't had these types of events or you know they don't have the amount of experience you've had how do you get started with asking for sponsorships and then you know with the recruitment retention and recognition part of it uh-huh that that's um uh recruitment recruitment and recognition of volunteers or sponsors um sponsors uh sponsors okay so yeah I mean I when I got started I I literally passed around a hat like a literal hat and said you know our time is voluntary uh but we do have to pay for the food that you're eating and we'd welcome you know and be grateful for anything that you can contribute if you want to toss in a buck but you know as time goes on and you you have regular events you know at the beginning of every event you tell people you know this is this is a volunteer run event we have to pay for food we we are open to sponsors we'd love uh to talk to anyone who's interested in having you know a bigger profile in this event and we do make announcements out on social media that we have sponsorship opportunities and then once we get a spot we talk to people that come from larger companies and ask them if they're willing to host an event and then usually with that hosting comes paying for the food and drink so that's a nice easy way to kind of get it's like a sponsor starter kit and then you can say hey you know we had our event at Twilio and they are a sponsor and now you have some sponsor logos to thank people for and then once people see that there's you know it's the same concept of nobody wants to dance alone at a party once they see there are other people dancing there are other sponsors on the docket then they want to be a part of it and then you can kind of reach out to different companies and you look at your attendee list before every event and see who comes from larger organizations that might have a budget and then you just reach out to them and then eventually they come to you great um perfect in terms of retaining sorry this is the part two of that question in terms of retaining them uh i would say you know just make sure that you religiously thank them you show their logo you um reach out to them like have a regular check-in even if they don't initiate it and say i just wanted to give you a heads up of what's going on in the oc tribe community lately and here's some people that you might want to reach out to about your product and um let me know when you want to come and give for example a panel presentation at our at our event that kind of thing okay thank you thank you and the other question we did have it's almost the same exact question but about volunteers so again some of these folks coming in are just right at ground level they're just getting started with doing this how do they recruit volunteers for these particular tasks and i know you have some great handouts which i've included in the course but what was your strategy when you first got started be pushy don't be shy you know just tell people you know hey i'm doing this on my own i'm looking for volunteers have you enjoyed this if you find it valuable please you know i asked you know nina who's our intern at caravan studios knows that i you can vol you she was vol and told to help me you can help you can kind of be pushy and say to people you know if you want to attend we'd look i need everyone's help yeah this is a group effort and after a while people will come up to you and say you know this is this is great how can i how can i help you and also this is really important in your rsvp registration form always include an open field that question that says do you want to volunteer yes or no and if they say yes and they have to include their email address and then you reach back to them because a lot of people you know they see the value and being a part of the smaller community as crystal mentioned in the video you know it ended up eventually getting her a job at google so you know there there is value you just want to make sure that you're transparent about the value you're providing thank you and actually nina is here with us today so she was nodding her head as well and i i think in this dialogue that we're having about volunteers you demonstrated very very clearly in your testimonial you know crystal speaking about her experiences of volunteer and nina was nodding her head as you were saying you know vol and vol and told but but folks that get involved if they are treated properly and like you said you retain them by doing certain things for your volunteers most specifically thanking them and being sincere and being authentic and i think you also used the word transparent about what they ask is what they will be doing and giving them autonomy to complete the task um do you have like volunteer roles that are specifically laid out for volunteers yeah i do and i have a regular volunteer kind of uh manage the volunteer managers kind of meeting and so it's kind of for the core members i have like a council a leadership council um in a way of saying it uh with my volunteers and i as i mentioned i regularly meet with them i take their ideas and i implement their ideas like hey what do you guys think like should we do kind of a speed geeking session or should we do a party i take their ideas and i implement what they suggest so that they have ownership and um you know i also figure out who's good at what because some people you know there's what i always say about volunteers is there's a role for everyone even the painfully shy volunteer don't put them as a greeter put them as somebody you know who helps you with something else like maybe they help with the tech stuff but there is a role for everyone you just kind of have to figure out and be intuitive and i also try to have coffee or a drink with all of my volunteers i always try to do an after hours check in like i did one yesterday with a former volunteer i'm always trying to keep them engaged thank you um before we sign off i'm giving folks another minute to to chat in any other questions they might have but i want to also tap into something you said i've been taking notes in case there's anything else i can add to you know the course archive um but you said something that i think is really important um as a volunteer manager and folks that work with interns or volunteers or as everyone on this webinar starts to go out and begin these community events um you made it personal and i've seen that first hand susan because i did it some of your apps for change events and you know each person individually and you know them by name and you do make it personal and i think that that's something that folks that are going to do this do need to understand they do need to invest some time um in developing volunteers but that it's such a worthwhile investment because in the long run as we can see from your testimonial those are folks that are going to carry your your vision of this and your message forward yeah it's really important and and giving them the tools to do it on their own to scale it like crystal moved to colorado and she actually was talking to me about starting her own oc tribe so it's kind of you want to give them the tools so that they can grow you don't it's hard to kind of let them go because obviously of your own selfish reasons for wanting to keep your best volunteers but you have to give them a clear career path of the latter so that they can you know as you mentioned take portable take their skills and make them portable so that they can grow in that role thank you thank you um susan you have covered a tremendous amount of information and you've also answered answered a lot of questions um i really want to thank you for your time and the amount of effort to put this together and to join us today we are very grateful for your time and expertise also all of the learners that are on this course are folks that watch this recording we thank you for attending and if you do have questions you can reach out to email susan i had forwarded that out to you and i will also put it in the course so please do reach out to her with any other questions or you can also reach out to me as the administrator of the techsuit course platform we thank you and susan you're awesome thank you for your time today thank you so it's really fun thank you very much good i'm glad you had fun and i hope everyone on this had fun as well all right everybody bye bye


What's up guys? Top of the morning to you and welcome back to another reaction video. My name is Jacob and first and foremost I want to say thank you so much for clicking on this video. I hope, I hope that you've enjoyed the series so far. For anyone playing along at home today's day is the 29th of August. I feel like we've been on this mission to complete this list for the last week. I did give myself a month, a month all up to shoot the videos, edit them and then begin publishing them. So with that in mind I've got another three weeks and we've got another 72 players to go. But today's player, I'm not going to say the player is surprising to see but certainly the number that he's at is very surprising. Last year he surprised me seeing as he was number four on the whole entire list. Michael Thomas wide receiver from the Saints. This year he's been dropped to full 68 spots and lands at number 72 but seeing as just the top six percent of the entire league even get a sniff of being on this list it doesn't really matter whether you're number one or 100. You're still pretty damn good or at least that's what your fellow peers around the league think. Anyways this video is about what I think about what this video is actually about what I think about what they think about this player and then your comments down below are going to be what you think about what I think about what this guy thinks about this player and to be honest it's all good.  Sup guys first and foremost thank you for clicking on this video secondly this video is brought to you by none other than the Ridge makers of the world famous and now YouTube famous at least on my channel Ridge Wallet. In less than two seconds I'm going to show you exactly what the hype's all about. That's what it's all about this wallet holds just as much as this yet this one is bulky ugly and outdated now this one being that it is a Ridge Wallet holds 12 cards it's sleek it's stylish it holds cash there's over 30 different styles including this one which is matte black and this one currently unopened which is 18 karat gold not only does the look and design speak for itself but the packaging is next level also and when it comes to giving a gift when it comes to even gifting yourself when you deserve it of course that's a win the whole entire wallet is the exact size of a credit card and the way that you access the cards is to push up from the bottom let's be honest 40,000 five star reviews they don't lie there is a lifetime warranty on each of these wallets if for whatever reason you're not happy you have a 45 day window to receive a full refund i've got to be honest at first i was skeptical i have seen it advertised on other youtube channels youtube channels i respect actually and enjoy watching so it was only a matter of time until i tried it out for myself it's not only wallets the website does have an entire range of products designed to carry less and live more and that is a quote that i've actually lived by for years head over to www.ridge.com slash jacob use code jacob for 10% off and i guarantee you this will be whether it's in black or 18 karat gold the last wallet you'll ever use guaranteed because there's no way in the world i'm going to be carrying something like this round anymore cheers guys and enjoy the video okay here we go let's get into it guys from number four to number 72 now at the very least we're going to hear something about that surely so let's see what's up we're obviously keyed in to someone like michael thomas throws near side like tom's car midfield okay so we're hearing we're hearing from a bronco's safety talking about marking the saints wide receiver michael thomas guy that you know is going to be a high volume target and still get the receptions and still find ways to get in the end zone does he deserve to be a top 100 player even with missing as much time as he did um in my opinion i feel like that's uh that's a definite yes okay first oversight he was actually number five last year not number four second oversight he was injured so with that in mind let's look up his stats uh not to be confused with big mike thomas who was a running back back in the 70s i believe this is michael thomas not to be confused with mike thomas a wide receiver born in 1987 drafted to the jags i believe but but career didn't quite pan out this is michael thomas a wide receiver born in 1993 or is it 1994 no there he is michael william thomas junior is six foot three 212 pounds went in the second round of the 2016 draft he went to ohio state and he's been at the saints ever since quick reminder of his pre-draft measurables that's absolutely ridiculous he's got a hand size of 10 and a half inches that's bigger than javaslandry's he runs a 40-yard dash in 457 he's got a 20-yard shuttle in 413 a three cone drill of under seven seconds vertical jump of 35 inches a broad jump of 10 foot six and 18 reps of the god damn bench press and at 212 pounds ripping out 225 pounds for 18 reps that's not bad okay this is not good this is not good let's look at his stats he played seven games five games he started only 40 receptions for 438 yards no touchdowns one rushing attempt for one yard all right so as far as his injury during the 2020 season he was placed on injured reserve on december 19th due to a lingering ankle injury which actually first came about in week number one against the bucks he recorded three catches for 17 yards before exiting the game due to a high ankle sprain he was set to return in week number five but on october 11th he was declared inactive for the game by the saints after he punched cj gardener johnson in practice made his return finally in week number nine and i assume he played out the rest of the season which would make sense he played seven games in the regular season two in the post season we've got 438 receiving yards in the regular season and 73 in the post season so what do we got seven seven regular season games as opposed to something like 16 438 receiving yards in seven games he most probably would have snuck past at least a thousand yards and if we look back to his previous four seasons 1137 1245 1405 1725 so for his season to get cut short last year that's that's tragic he was on course to reach 2000 yards would that have been the first time in history let's check most single season receiving yards kelvin johnson set the record for the most single most receiving yards in a single season with the detroit lines amassing 1946 yards in 2012 so 2000 yards is still yet to be broken anyway moving on to his 2021 season it's it's not looking too good on july 23rd on july 23rd about two months ago it was revealed that thomas had undergone ankle surgery in the past month now whether that's the same ankle that was giving him trouble the year before i don't know but he was placed on the pup list three days later which is what michael thomas expected to miss the start of the season after undergoing ankle surgery expected to miss the start of the season could be a four month recovery the saint by comes in week six they could be eyeing a week seven return for michael thomas anyway that gives us a bit of an idea as to why he may have slipped down the list by 68 or 67 spots but let's continue i think when healthy i think he stole that guy michael thomas's 2021 season will be delayed due to ankle surgery in 2020 he played just nine games but still caught his way into the record books in just his 69th career game thomas eclipsed the 500 catch mark 11 games faster than any player in nfl history really nice work by mike thomas you know what that's good that is good that even though he's missing games there's certain records that only apply to games played i like that faster than julio jones larry Fitzgerald even the go gerry rice that's insane you don't break a nfl record by accident right he's one of the angels that he was an author he's so physical with his hands i'm trying to see some one-on-one his his hands are 10 and a half inches you're gonna do well to pry that ball out of them not only that but he's six foot three he's a big body out there and almost like a fight some aggressiveness you turn on mike i actually want to break that down wait for it makes the catch whilst stumbling i guess he does actually brace himself pretty well for the contact but how does he absorb it but well he don't flinch toughness is another part of his game that he definitely deserves praise for mike thomas you really discount how physical he really is running in the middle of the field weekend and week out you know you're gonna get hit he holds on to the football makes a play for the saints it's not every day that you have a number one receiver that's willing to do it's at times like that where you're running into traffic that you just hope that your quarterback throws a good pass right because if they throw it behind you and you're still expected to go and catch it but yet your path is now crossing right in front of a defender who's going to snap you in half as soon as you catch that ball you're still expected to go and catch it so at the very least give us a good pass kubi might not be a tougher route in the NFL right now than catching mike thomas on an inside sling that physicality you can really learn something from that just the way he likes that technique oh no the most impressive one ality you can really learn something from that was this one so he's done a a bit of a shimmy with the arms to get the man thinking then he's gone a left right and a left and he's away and i absolutely love it he's one of the put in a category to just have free cans it's down deep short contested yeah freaky big hands he's gonna catch everything even if you look like you're in position to make a player to make a hit we're still gonna throw it and we're still gonna make the play michael thomas with a nice contested breath injuries are always part of the game you know when you're talking about some of the best wide receivers in the game i find it pretty hard not to put michael thomas in there look at those grills so as we see javaslandry pop up the one thing that i'll always remember about javaslandry is his hand size the one thing i'll always remember about michael thomas is the fact that he's got bigger hands than javaslandry so with that in mind best of luck to the both of them and best of luck to you guys thanks for watching that's another video down in the next one we've got a browns player by the name of baker mayfield am i surprised he's landed in the top 100 no not at all he's only been in the league for three short seasons but he is a bit of a cult cult figure around the traps isn't he and i cannot wait to hear what his fellow players fellow colleagues around the league think about him in this next video so guys thank you for watching and peace out