there? I apologize. Yeah, no worries. So we signed a deal with Golden Harvest, which is the operating entity of Grown Rogue, which gives us access to the Michigan market. Obviously, the Michigan market is the biggest and most profitable state in the US from a new entrance into the recreational space. So they did, I think, $170 billion in sales in the last month that they reported just to give you a volume size. So like run rate, that's going to be more than all of Canada. So from one state, yeah, they use a lot of products in Michigan. That's great, great, great. $170 million. Yeah, yeah, it's crazy. And that's just, it's a crazy number, which is why we picked Michigan. We've been working on this with Golden Harvest for about a year and a half now. So trying to structure this. So when we started, we wanted to have access to the US market. That's why we listed on the CSE also originally. So we could do deals like this, and it wouldn't violate any of our listing issues. So with that, we'll be putting product of pure chews, pure polls. We'll be in store in Michigan. So we'll set up our production facility. We've been working with the engineers and whatnot to get our equipment shipped from BC up to Michigan. So that'll start crossing the border shortly. And then we'll be in production about 90 to 120 days. We should be in production for that. We'll be producing the pure polls, pure chews, plus the Golden Harvest, the Grown Rogue product. And we'll be using their sales force. So we don't have to go educate a sales force and have relationships with the dispensaries. They already have that. They're in over 100 stores already out of the 400. And then we have some distribution through another 200 stores. So we should be able to hit 300 stores pretty easily within the year of penetration through retail sales. So we'll be producing both our products, Golden Harvest, Grown Rogue product. And then we'll be doing white label products for other producers that don't have the ability to produce extracted products. And if you look at the sales so far in Michigan, about half, a little more than half is actually extracted products. So they're already making the ship from flour to extracted products. So we're pretty excited about that. We should be pretty strong right out of the chute. And the way it looks like most of the dispensaries run out of product pretty quickly when the ship. So yeah, we think we've picked a great state to start off in. And if this goes the way we think it is, we'll be expanding in the similar model with other partners into the southern states. Wow, that's fantastic. So what does this mean for your company? Like what type of revenue are you expecting based on this joint venture? Well, if you look at the market of what they're selling in our core business coming in vapes, that's about 40 to 50% of the revenue base per month. If we can capture a half a percent of that, we're talking three, four, five million dollars of revenue eventually. So we're estimating pretty low that we'll start off like a million to two once we get into run rate. So I think a million dollars is pretty low to be honest to a month as we ramp up. Sales are going to be pretty robust from what we see. Gummies sell out by the time they're shipped. So we're in four provinces now, as you know, for Ontario, BC, Alberta, and Saskatchewan. And our gummy and vape product is selling very well. So we don't believe that there should be any difference in the US to Canada. So we think we can crush it. So we're not giving any guidance yet, but if we just look at the market itself, we think we can penetrate quite well and not having to educate our new sales sports and make those relationships with the dispensary because it's a direct model in the US where we sell directly to the dispensaries. They already know all these people. So through our two distribution partners. So we're pretty excited about that. And we'll definitely do some white labeling and the core extraction for other parties that need oil products. So that will kind of round us out within the Michigan market. Wow. I have a question from Jeffrey Lutz. He likes to know how the fireball gummies are selling. Selling really well. We're really happy with the way they're selling. The product is fantastic, both from its flavor profile and a packaging profile. What we thought in the dispensaries is coming true from a consumer perspective. They love the proprietary packaging in a blister pack. It's actually what's propelling that product to the flavor profile, obviously in cinnamon fireball. Everybody likes it. We've all taken a shot of fireball, I'm sure, back in the day. So that brings back some memories. And the packaging in that blister pack, slip it in your jeans pocket, doesn't go all over you, doesn't go clumped together like the little baggies of product that you get in some of the other manufacturers. So it's been really strong and you'll see our CBD product is going to be hitting the market shortly also in a couple different flavors. So that's actually gotten some really good traction from the provinces wanting to order that in for September. I have another question from Tony. He says, I tuned in late and wonder what stores and what cities in Michigan you're going to sell through. Gauge is huge in Michigan. Yeah, absolutely. So obviously, Bruce's Gauge will be one of the partners that we'll be dealing with. I can't tell you the locations yet, because we just signed our definitive, so we're just going to the retail outlets. We'll be in 100 stores. Golden Harvest is in 100 stores today with their flower product. Every one of those partners will take the extracted product. We would think they're asking us for it. So if that call or if you call them that on YouTube, email us at info at purexcorps.com. We'll get back to you with the locations that they're in. Okay, fantastic. I also have a couple of questions myself. Let's discuss the Michigan market. When entering the Michigan market, what does it mean for Pure and what will we be producing there? What will Pure be producing in Michigan? Sure. So what it means is we transform the company into a multi-geography company. We're both in Canada and the U.S. MSO evaluations are much higher than they are in Canada. If we look at Gauge or Red, White and Bloom, their market caps are $200 million plus. We're kind of engaged or we're engaged as a Canadian-only company play. This gives us obviously access to one of the biggest states per revenue in the United States. So it means we'll be revaluated for where we are. We're not going to continue to trade. We've doubled in the last month and a half. We're still very economical and the buying has been definitely coming in from the U.S. knowing if we get the sign, which we did, from an MSO perspective, the best state to be in from a revenue and profitability perspective, because margins are still really good in Michigan, and two, having the expertise coming from Canada and the brands that we're developing that we've used in the Canadian dispensaries have already been tested. So we don't need to stub our toe on products that don't sell in Michigan. We would know what sells because we're already selling it in the Canadian market. So it means our market cap should definitely go north of where we are. I don't have a crystal ball, but when I look at my peer group, we're still severely undervalued in comparison. Yeah, and that's what I've been telling and letting everybody know that I feel like you guys have every single box checked of an early-stage company, with the only exception being the share price is lagging with everything else that is happening. You guys are growing, you're growing your revenues, you're expanding, you're in the psychedelics and cannabis-based, two very fast-growing industries, and you've got a tight share structure with growing revenues. So everything we look for for an undervalued, underappreciated, underexposed company, and the only thing lacking is the share price, which really is to the advantage of an investor, a long-term patient investor could see huge price appreciation if they're willing to invest and hold and wait for the company to grow. And in saying that, can you give us an update on your Canadian sales? Sure. So as I said, we're in four provinces now. So we're in Ontario, BC, Alberta, and Saskatchewan. We've also listed on ABBA Medical Platform that deals with the veterans fulfilling cannabis requirements to the vets, which is very important to us because of our product. They're high volume users and they need very potent and long-onset products like our vape products by our vape and the gummy products. So they chose us because of our qualities of the vapes that are long-lasting because they have some, obviously, PTSD and some other issues. We're going to give some guidance after we get a run rate into 4Q. We've received repeats from the provinces already. So the sell-through from the product has been quite nice and the orders have been in the six-digit initial load-in amount. So we're quite pleased with that and getting a listing in Ontario, products hitting the shelves I think on the 27th in Ontario. As you know, they close their product calls for new LPs listing in Ontario and they said, if anybody's not listed already, their next product call won't be until 2022. So they have to wait six to nine months for a product call. We were lucky enough to be selected for some of our products and this year, obviously in August. So we're continuing on building our experience in Ontario. So we're pretty happy that we were selected for that because obviously Ontario, although it was a slow-growing market, now it's obviously picking up steam with over 400 stores in the province. If there was anything you wanted to share with investors, someone that's new to pull, someone that's new to PurexTracks, or someone that's an existing shareholder today, if there was any information or any advice or anything you want to say, what would that be? It would be just watch us. We said we were going to execute in Michigan. They thought we could never get it done in the hottest growing state in the United States to be an MSO. Nobody thought that we could be listed in four provinces. We're listed in four provinces. When we said the share price was undervalued when I was on the show at $0.23, a lot of my core investors came to me and said, I'm taking big positions. I believe in the company. We believe in the management team. We know what we're doing because this is our first cannabis company and we're going to continue to grow the business. We're here to grow revenues. We're here to build a solid business and I think the investors will recognize we're an execution business. This is something that we've done before and my management team is all about booking revenue and expanding our footprints, now being a multinational being in the Canada and the US. We're severely undervalued in comparison to our peer group and I still think there's significant upside and we can see by the amount of appreciation, the accumulation that's going on at around $0.40. We're not having any slippage. People are accumulating the stock. They're long-term on us. We're executing and I think we have enough staying power both in the cannabis area. We're in the psychedelics. We're moving forward with our trials. Our functional mushrooms are selling nicely on Amazon. We have multi-tier revenue sources that most companies of our size don't. We're pretty happy with our structure. What do you think about Biden? He essentially became the president with a huge cannabis mandate and since he's been president there's been nothing. Is there something I'm missing? Is there a disconnect? Everyone said Biden was going to be positive for cannabis and to be honest with you, since he's become president cannabis is really lost steam. Is there something coming? Is there going to be a catalyst? I'm talking about the biggest companies in the world like the True Leaves are struggling. The cannabis grows, the till-rays that they're just not getting any interest despite the fact that they're producing enormous revenues. Cure Leaf just reported enormous revenues and the stock goes down. What do you think it's going to take to get the momentum back? Or is it just because it was summertime and are we on the verge of another bounce back here? Because typically cannabis does do well in the fall. That's typically when it does its big move is between September and February. Are we set up right now? It looks like we're set up. Are we set up for another resurrection right now? What do you think? Cannabis is very cyclical. We've seen this now for a number of years. For whatever reason, cannabis trades extremely well September to February. I don't know if it's the traders are all in Muskoka or whatnot, but it is what it is. Tillray made a major acquisition on accumulating the adventures for Medmen a couple days ago. So they're not spending $200 million because they think Biden's not going to convert this into a federally legalized product. There is chatter, obviously, that they're working on a cannabis bill to legalize this federally. I think the reality is we're going to, obviously, there's some bigger issues that they're trying to deal with at the same time. Obviously, COVID and Afghanistan and whatnot are two major issues that the Biden administration I'm sure is dealing with. But cannabis I know is on the radar screen and I know that they are working on bringing something forward that will make it federally legal. Tillray is way more dialed in than I am from a federally U.S. factor. Tillray is very strong from a U.S. administration perspective. They don't inject that kind of capital because they think that they need to own some convertible debentures. They believe that it will be federally legal sooner versus later. That's my personal thinking that has no basis in anything else that my personal thinking. I have another question from Tony. He was asking if Fireball is going to be receiving a royalty from you guys. Yes. In our deal, depending on the products that they do receive, they do receive a royalty on products sold. Okay, great. I don't have any other questions right now. Anything else you want to leave with investors before we say goodbye? Because I know you're really busy. Yeah, I appreciate that. First of all, I want to thank my investor group. You gave us support. We've been trading very well. There's been a lot of shares traded and the capital that my investors invested when we were a little bit down. So I thank you for supporting this talk to the new investors. Welcome to Pure. I think we have a lot of gas in the tank. We have a great management team, Doug and Sandy and Andy, my head of sales. They're working diligently to make this a profitable company and continue to grow the business on all fronts. Michigan is a major milestone for us and as it hits the U.S. market and the folks in the U.S. see that we're entering an extraction company from Canada has the experience that we have both from the legacy market and in the promises that we're in. And then come September with the cannabis wave that usually happens, I think we'll be materially higher than we are today. That is fantastic. Thank you for your time today. Ben Nikolevsky, the CEO of Pure Extracts. Now, remember guys, rich TV live is strictly for information education purposes. Please do your due diligence, do your research before you invest in anything that we talk about or discuss here in Rich TV Live.  Ben has been nice enough to take his time today and tell us what's going on with the company and break the news here on our show. Thank you for joining us again, Ben. Always a pleasure and anytime you have any big breaking news, we love to be one of those places where you can break it first. We love Rich TV. We'll be back. Thanks for having me, Rich. I appreciate it. Thank you, Ben. Keep up the great work and congratulations on all your milestones. And I know you guys are going to do your best to just continue to grind out more deals and more announcements and more big news and we'll be here to tell the story. I really appreciate the time. Thanks, guys. Thank you, Ben. Okay guys, if you like these videos, remember to smash the like button, comment down below, share the video everywhere and subscribe if you're alive. Thank you guys for watching. Remember, if you're not winning, you're not watching. We bring you the winners and we bring them to you first. I think Pure Extracts is undervalued, under-appreciated, under-exposed. I think the upside is tremendous for this company. Thank you guys for watching. Have yourselves a nice day.


The United Nations International Center Unique in Nigeria has trained journalists on the importance of understanding mental health, this order, and how it should be reported to the general public. The two-day mental training workshop for journalists was organized to mark the World Mental Health Day, which is celebrated globally. Plus, the Venice correspondent Iman al-Hijian's report is presented from our studios. Mental health disorder is one of the most misunderstood health conditions amongst humans across the world, despite numerous attempts by WHO organization, psychologists, as well as specialized institutions to address it. These misconceptions about mental health disorder and ways to understand the underlying factors are the reasons for organizing the training program. Many people are going through a lot of stresses in these times, and we should be careful about mental health situations of a number of people. And we should not just say that a person, mental health, because many times we attribute that to culture, to beliefs, religions and so on, but mental health is about all of us. People who are considered to be mad or walking naked on the streets, but it's about everybody. Government has a role to put in place measures for accessible mental health support for all people. Just like you provide support for health, for other health, physical health, there should be support mechanisms for mental health. Health experts explain more about mental health disorder, its symptoms, ways to identify cases as well as support mechanisms. The engineers also will need to learn how to rest. That's number one. We must know when to say, I think I've had enough, let me go take a rest, it's very important. And then number two, for us to be able to cope very well with stress. There's need for us to understand what is causing our stress in the first place. Once we understand what, because stress for individuals are different, what could be stress for you would be different from what is stress for me. So once I understand what my stress is, I will now begin to find a way to deal with that stress.  But whereas in the actual fact that mental health conditions are like any other chronic medical conditions, they are treatable and people with mental health conditions can live a good life like any other person. This is the narrative we want them to change out there and also to be able to communicate what the government of Nigeria is doing in order to address the mental well-being of Nigerians. The role of the media in supporting the advocacy was also highlighted at the training. We have that tool, our pens, our cameras, our microphones, and the way we write is to tell the world that mental health, the interventions that are changing, and we need to change with it. People need to know stigmatization will stop, treatments are available.  But some of these things are doable and it is within our purview as journalists to push them out. And as we mark the world mental day, we should not make it a one-off, it should be something that we would follow up so that we can close the huge gap that has to come with prevention, treatment, and care. The take from this training workshop is that mental health disorder is not a disease and it can be treated with love and understanding from the family and the society in general. Hello, hope you enjoyed the news, please do subscribe to our YouTube channel and don't forget to hit the notification button so you get notified about fresh news updates.


is one.  And these words which I command you today shall be in your heart.  You shall light them on the door of your house and on your case. So we see a very important instruction the Lord is giving the children is rare and saying, okay, one thing, the first thing is about the Lord Himself, the description of who He is here in Israel. The Lord is God, the Lord is one. And second one is how we need to relate to Him. It's not a ritual, it's not a tradition, but you shall love the Lord your God. It's a loving relationship.  And then it gives an instruction for the parents towards their children what they need to do. It says here, first of all, this command should be in your heart. You love the Lord and it says you shall teach them diligently to your children. Okay, so teaching them about God, teaching them, teaching children, first and foremost, primary responsibility of parents, and that's what we see. We should teach them. And then He also says you should talk of them. Okay, so teaching is probably in a very formal setting. Maybe we are saying, okay, come, let's sit down, let's, I just want to teach you something about God, what He has done. It's a little bit formal. He also says, and you shall talk of them.  So He talks about various informal settings where you have, they're saying, okay, let's just have a chat. We're just having coffee, we're just having maybe breakfast, and we're just sitting down and let's have a chat. Okay, so you should talk of them, talk about God. So it's not, you know, you don't readily change your tone of voice and you're not preaching, but you are talking of God. It's a very normal, very real, very authentic thing. So what happens is that children also begin to understand that, hey, God is not relegated to a particular day. It's not, you know, something traditional, something ritualistic, but it's as real.  So we see these very important instructions.  It's the responsibility of parents. But you also talk of them. So the parents and children know that this is how I can relate to God. I can have conversations about God, about the reality of God, about, you know, how God, what God means to my parents and how God is dealt with them.  What are these commandments? Then you shall answer. And the answer is that, okay, this is what God did for us. So in our day and time, can testify about this is how God dealt with me. This is how God led me. This is how I came to know God. So it's very real, very authentic and it's in a family setting. So let's pray. And if there's something that we can ask God, we can ask God, say, Lord, I want my relationship with you to be real. I want it to be as normal, as breathing, as frequent as eating, as normal and frequent as everyday life. I want my relationship with you to be like that. And so that it can just flow out in normal conversation, in day-to-day things. It can just flow out and I can testify a few, right? Okay, let's pray. Father, we thank you, Lord. Thank you for this day. We thank you that you're so real to each one of us. We thank you that you teach us in normal everyday settings. Lord, we thank you, God, that you have drawn us, invited us, Lord, into this relationship with you, God. And it's a relationship of love. It's a relationship of holiness and purity and righteousness, God.  I pray, Father, God, this morning that if there's anything that is hindering us from loving you in this manner, Lord, to obey your commandments is to love you, Lord. If you said, oh, God, if you love me, obey my commandments. And so, God, if there's anything that is hindering us, Lord, I pray that it'll be broken. I pray that if there's anything that we have set up, Lord, unknowingly, unknowingly, that is stopping us from loving you in this manner, I pray that we will set it aside and put it away, God, and repent and begin to follow you. And, Lord, we thank you for those of us who are parents. We thank you for these instructions that we will, Lord, teach diligently, Lord. And we will not shirk from this responsibility, God, as parents, that we will teach diligently. And we will also talk of what you have done, talk of who you are to us, Lord, in all these everyday settings, routine settings. We just want to thank you for these instructions. We come at these today's sessions, these glasses into your mighty hands. In Jesus' precious name, we pray. Amen. Okay. Right. So, hope everybody's doing fine. I saw... Okay, this is for the biblical preaching class. I saw what you uploaded on the chat, on the classroom, classwork section. So, I saw that. Maybe we'll talk about that in the third hour. Okay. So, in the Marogen family, we've been we've been studying about... We're in the fourth chapter, right? We're in the fourth chapter about understanding roles. It's very important that the husband understands his role, the wife understands her role, and it will make for... To have clarity in this will really help the process of becoming one, right? Will really help the marriage, will really smoothen out a lot of differences, right? Will really also bring our expectations, will make it real authentic, right? And it won't be an unreal expectation. And also, our expectation will be founded on scripture, founded on the truth to say that, hey, this is what God has put down as the role of the husband. So, my expectation would be that as a spouse, you fulfill that role, right? And how can I help you fulfill that role? So, it's important for us to understand the role, right? Okay. Sir, can I see your prayer request? Okay. Fine. So, this is something that we need to understand, right? So, we looked at the husband's role last class. We looked at the husband's role and I think we went midway, right? And to look at this, we were looking at Ephesians chapter five, which very beautifully and also very in a detailed manner descriptively, charts down, lists down, what is the role of the husband? Okay. So, it talks about how one needs to relate as husband and wife, how they need to relate to each other. So, let's do a quick recap. We saw that before that, I read that passage, Ephesians five, and yeah, verse 21 onwards. Okay. Submitting to one another in the fear of God. And before that, you know, it says, be filled with the Spirit, speaking to one another in Psalms and hymns and spiritual songs, etc., and say submitting to one another in the fear of God. Give us 22. Wives submit to your own husbands as to the Lord, for the husband is the head of the wife, as also Christ is the head of the church, and he is the savior of the body. Therefore, just as Christ is subject, the church is subject to Christ. So, let wives be to their own husbands in everything. Husbands love your wives just as Christ also loved the church and gave himself for her, that he might sanctify and cleanser with the washing of water by the word, that he might present her to himself. A glorious church not having spot or wrinkle or any such thing, but that she should be holy and without blemish. So, husbands ought to love their own wives as their own bodies. He who loves his wife loves himself, for no one ever hated his own flesh, but nourishes and cherishes it just as the Lord does the church. For we are members of his body, of his flesh, of his bones. For this reason, a man shall leave his father and mother and be joined to his wife, and the two shall become one flesh. This is a great mystery, but I speak concerning Christ and the church. Nevertheless, let each one of you in particular so love his own wife as himself and let the wife see that she respects her husband. So, from 21 onwards to the end of the chapter, we see this beautiful representation or this analogy of Christ and the church in the body and he's relating that to the husband and the wife. So, we see that the husband has to love. We will come to the role of the wife a little later. So, we see that the husband has to love the wife and the word used there as agape. And husband loves the wife as Christ loves the church. So, it's unconditional love. It's a sacrificial love. It's a love that demands a lot out of us who are going to be loving our wives. So, it's a love that builds up and enriches the wife. And he uses another word, says we need to, husbands need to nourish the wife. So, we see that in verse 29, no one hated his own flesh, but nourishes and cherishes it just as the Lord does the church. So, in relating to the wife, the husband has to nourish the wife, meaning nurture. So, not only provide for physical needs as part of the responsibility, but also provide for the emotional needs, provide for the spiritual needs. So, be encouraging and be spiritually also to guide, to motivate, to enable the wife to grow, to empower the wife to grow. So, it's not a constant instruction saying you do this, you do this, you do this, but it's to nurture and it's to nurture, it's to encourage. So, for those of us who are married, it's another checklist for us to really reflect upon and say, am I doing that? Because what happens is in the course of marriage, maybe just a year into it, two years, three years, whatever, and then your spouse's, your wife is very familiar to you. And then, what is familiar, we don't normally, maybe as we don't cherish or we don't nourish, but we see that as a responsibility, as a role of the husband. So, for a single person to understand that, okay, this is also part of the package, like when it comes to marriage, just that, it's not that I just get married and then things just happen, no, but this is expected of me to nourish my wife. It is expected of me to take care of her emotional needs, you know, maybe she's discouraged, maybe she's fearful, or maybe she lacks something emotionally. How do I, you know, how do I point her to Christ?  So, that's a responsibility as well. So, we see nourishment, then we see cherishing. So, we saw that cherish is to treat something as precious, to consider something as precious. So, does or do I as a husband, do I cherish, do I treat her as something precious, or do I treat her as something that is common or worthless? How do I do that?  So, when we, when I communicate as a, when the husband communicates respectfully to the wife, the wife feels cherished, feels worth, feels valued. So, how is my communication as a husband? A wife feels valued and cherished when there is romance and not just physical intimacy, not just sex, right? So, that, that is also very important, you know. So, how do you treat the wife? So, find out, you know, at the end of this chapter, you're going to find out something about communication and also about language. Some of you may be aware of it, just going to look at that and that will actually help us to communicate in a manner and also, you know, to communicate with concern, to communicate respectfully and communicate in a manner that the wife understands, right? And also vice versa, right? So, so, there is romance. When the husband is trustworthy, okay? So, which means when the husband acts, behaves in a way that the husband, the wife can trust, right? Well, if the husband acts very suspiciously, right? Say, okay, well, I'm going to, for example, you know, the husband comes home late after work. The work got over at, let's say, six o'clock in the evening. The husband comes home at, comes home at 10, 10 p.m. And the wife asks, you know, where were you? And the husband says, that's none of your business, right? So, the husband, the wife is unable to trust the husband. First of all, the communication is very harsh and rude. And secondly, it's not open, not being transparent.  Right? For us, after work, what was he up to? What did he do? Is he seeing someone else? Is he, you know, all those questions, all those suspicions, right? So, can the wife trust her husband? So, if the husband is trustworthy, which means, you know, you know, behavior, your speech and everything is about approach, and the wife is able to trust fully the husband, then the wife feels valued, feels cherished, right? Then, the wife also feels cherished when there is sharing of responsibilities, so that burden is made easier. The wife carries responsibilities, the husband carries responsibilities. So, when the husband reaches out to say, okay, let me, let me take care of this, so that, you know, you can rest or you can, you know, you can maybe probably go out and meet with your friends and do such things and let me, let me just take care of this today. Let me take care of what needs to be done today, maybe in the house, maybe something else, right? So, when that is done, then the wife feels cherished, the wife feels valued. Okay. Now, these are just, you know, just few examples, right? But I'm sure that there's a lot more and it can be specific to that particular person, right? The wife feels cherished when the husband sets a godly example in the pursuit of God, right? A godly example, a life that is pursuing God, a life that is passionate about God, then the wife feels cherished. Now, you might say, how does that happen? So, you know that, okay, husband is pursuing God, husband is going after righteousness, after holiness, then the wife feels secure, wife feels also, you know, that yes, this is the right direction, you know, the husband is taking, you know, if the husband is not pursuing God, let's say distancing himself from God, then you know that something is wrong. Okay. The husband could potentially open his life for temptation, potentially open his life for, you know, to make wrong choices, wrong decisions, and all that could happen, open the door for the enemy to walk in, right? So, so the wife feels valued. Okay. So, maybe we never thought of it that way, you know, in my pursuit of God, you know, how will that affect our relationship? We see that, you know, our lack of pursuit of God affects all relationships, all our relationships, you know, if it affects our relationship at work, it affects our friendships, it affects our, you know, relationship with family members, when we distance ourselves from God, because we are, we are designed to receive life from him, right? We are designed to be in that connection with him. So, when we, when we do not, you know, when we distance ourselves then, obviously, you know, like the Lord Jesus says, you know, with us, the branch with us and dies, right? Okay. So, the husband is also called to lead. Okay. Okay. So, that's, that's one thing, okay, to lead. Now, when it comes to leading, when it comes to leadership, now there could be, you know, various ways of defining leadership, different methods, different ways by which people lead, autocratic, dictatorial leadership. So, here we see that it's leadership the way Christ led. So, when it comes to leading also, it comes from this place of loving as Christ loved the church. So, it's a loving leadership. Okay. Some things for us to understand. Okay. When we say, okay, the husband is called to lead or the husband is the head. We see that it's a divine order, divine placement. It's never on superior abilities, because it's very clear. We see that we are co-heirs, right? We are co-heirs, which means that we are equal in the sight of God. So, it is not based on, you know, one is superior, one is inferior. But in God's eyes, we are equal. We are valued equally. We are sure, we are valued by him equally. So, there's no partiality. So, we need to understand that. Okay. So, what does it mean when it comes to, okay, the husband is the head of the house? That means that God has designed according to the role, according to the responsibility, God has, you know, divinely placed us as husbands in this place of headship. And the leadership is not something dictatorial, meaning, okay, you have to listen no matter what. I am the head of the house. So, you better listen. Everybody shape up. Everybody listen. You know, everybody better obey. No, it's not that. Because it says, you know, even that at the beginning of the chapter, be submitted to one another. Okay. So, be filled with the spirit, submitting to one another in the fear of God, right? That's what it says, right? Submitting to one another in the fear of God. So, you have God's, you know, you pursue God, you seek God, you evidentially have the fear of God and you submit to one another out of that. So, this, we see this headship or this leadership is based on divine order or divine design. Okay. When we understand that, then it brings a lot of clarity. You know, we don't mind, you know, the wife does not mind yielding to that headship, yielding to that leadership. Okay. This is how God designed. It's not to abuse. It's not to treat one disrespectfully. It's not to put one, you know, firmly in that place. It's not to use one as a doorman, right? But it's a loving leadership. Okay. Right. So, this leadership is based on Christ's example. This leadership involves taking responsibility, which means, you know, it's, leadership is responsibility, right? It's not being responsible. It is, it is, you know, it is, what are some responsibility, meeting family's needs, maybe financial needs, maybe to make decisions, maybe to be two steps ahead. Right. So, it involves responsibility. The husband is also called to be a loving leader. We looked at that. So, the thing is, when it comes to leadership, right, we need to earn the right to be, to lead. We need to earn the right to be heard as leaders in any, in any situation, right? Even in typical, you know, wherever, even if for us, the title of leadership is given, and then we are, we are leading, even in such scenarios, people will, okay, respect the title, you know, if it's an official setting, if it's a, you know, work setting, professional setting, people will, but then over a period of time, they will lose respect if we, if you do not earn the right to lead them, right? And that comes by competence, that comes by, you know, all the other things that we've been leading, I mean, studying about leadership comes out of compassion, etc. So, a loving leadership, so we need to be able to earn the right to lead, okay? Then the other thing is that we know that the husband is, is not perfect, okay? The husband is, has the potential to make mistakes, has the potential to maybe misjudge certain things. So, to be a leader, when we say the husband is a leader, the husband is the head of the house, that does not mean that the husband is always right, okay? The husband could make mistakes, but the husband needs to, maybe, you know, in areas where he feels he's wrong, maybe to accept that, right? Maybe in areas where he feels that, okay, he does not have the expertise to take help. Maybe the wife is, you know, competent in certain areas to take help, to take that counsel. So, so when we say leader does not mean that the husband knows everything, the husband is always right, we don't, you know, we're not saying that. So, we understand that God has created, God designed marriage to be this way, and this leadership has one of the roles, one of the responsibilities of the husband. Okay, then to know the wife, okay, then let's say, of course, I know everything about, but about the other person, but do you truly know, right? What is, what is her strength? What is her weakness? What are her likes? What are her dislikes? I do know her, what are her fears, right? Well, during the courtship days, there's a lot of communication, you know, trying to find out, okay, what is it that you like, and you're doing things that, you know, buying things that she likes, and okay, okay, this maroon is the color that you like, okay, let me get something in maroon. You know, during the courtship days, all that happens, but you know, during the course of the marriage as well, getting to know your spouse or getting to know your wife specifically is very important, right? No, so that, that is also something that we need to, as husbands, there's a responsibility, okay, then honor, honor, respect, and celebrate who she is, right? All the gifts and everything, the grace that she carries, the nothing that she has, you know, have you looked at it that way? How, what has God anointed her to be? What has God graced her to be? What has God gifted her, right? And, and to really celebrate that, to honor that, saying, God, you know, you are working in her, the way you dwell in me, you dwell in her, and to honor the gifting, honor the release of the wisdom, God's wisdom that she carries, right, to celebrate that, okay. So these are some things that we see as, when we consider the role of the husband. So you see that it is, it is something for us to understand, you know, if we are single, it's something for us to really study and see, okay, how can I do this, right? Or, and to, you know, renew our mind to the truth that, to the fact that, okay, this is something that I need to do intentionally, okay. It is not something that happens by chance. It is something that I need to, when I consider marriage, when I want, you know, if I'm considering marriage, then I need to be equipped. I need to think about these things, okay. So you see how preparing for marriage is important, because we may not consider all this. You may have a very romantic view of marriage and say, okay, it'll all, you know, it'll be fine as long as I'm, you know, with this person all the time, but, you know, that it is not so, right. Because we can live under the same roof and yet be very distant from the spouse. So for those of us who are single, we need to, you know, consider this seriously. For those who are married, these are areas for us to grow in, right. Okay, let's look at the wives' responsibility and the wives' role, okay. Here we see, again in the same chapter, we see that wives are called to love, to respect, and the word that is used there, wives submit to your own husbands as to the Lord and so on. So we see here that the word that is used for love and, you know, in Titus chapter 2 verse 4 and Genesis 2, 20, the idea, you know, in Genesis 2, 20 is that of the companion and Titus 2, 24, the word used is filet, the word used for love is filet, which means a friend, to be your best friend, to be a companion. Okay, so the wife has to, you know, or the wife to be needs to understand that, okay, I'm going to be, or I'm going to, you know, see, you cannot just become a best friend just like that, right. It takes time. So I'm going to do whatever it takes to be my husband's, husband to be his best friend or companion, help meet, right, which means that I need to, as long as, okay, he is submitted to God, he is, you know, doing his bit, I need to understand that he is also a work in progress, right. He is also a work in progress just as I am. So the wife needs to understand or the wife to be needs to understand that he is a work in progress. Therefore, I'm going to accept him. So when we say work in progress, that means there is some progress happening, like intentionally, he's looking at, you know, he's progressing, he's also doing something, he's approaching God, he's seeking to change, right. So he is a work in progress. There's there's a movement there, there's a momentum there.  Okay, these are some rough edges, right. These are some areas that I see that these need to be turned into strengths. He's not there yet. Okay, now I'm going to accept him as he is. Okay, now here I just wanted to pause and talk about, you know, what we just remind us about what we looked at when we were considering the compatibility, you know, in that chapter, when it comes to preparing, you know, we looked at compatibility and we said that some things are non-negotiable. It's spiritual compatibility, emotional compatibility, we're considering a lot of things and then we are also asking a few questions, you know, when it comes to, you know, is he able to provide? Does he have a relationship with God? Is he a believer? And all those questions are non-negotiables, like the answers to those things. We are. So when we're saying that I'm going to accept him as he is, right, we're not talking about that. So now those are foundational, those are given.  He is, you know, in all these areas, he is, there is a foundation, right, we are compatible. And at the same time, I see that he's not a perfect person. He's a suitable person because he's compatible. But he's not the perfect person. He's the right person, but he's not the perfect one. There's a difference, right? So the suitable one or the right one need not be the perfect one. He is a work in progress. So, so he's a work in progress. So I'm going to accept him as he is, right? Okay. Then it's also, you know, as a wife, I'm going to love. So love means, again, just like the husband loves, it's sacrificial action.  Love is a verb. It needs to be demonstrated and it would involve sacrifice, right? It's sacrificial action. It's demonstrated through our focus, availability, willingness, etc. Love is also physical willingness in the sense, you know, when it comes to physical intimacy, you know, it's also an expression of love. So both the husband and the wife or the husband to be and the wife to be need to understand that it's an expression of love. It's an expression of, we're going to, you know, study that, of course, in a separate chapter, but it's an expression of love and God designed it. There's nothing to be ashamed of and so on, right? Okay. So submitting. So loving the husband is one, and submitting is another. So here we also saw, you know, submission is is something that is, again, a divine order, a divine design, because the husband is it. God is placed as the leader, as the head. So therefore, it requires, you know, the wife to be submitted. At the same time, we also see that, you know, you be submitted to one another, right? In the fear of God. Okay. So submission is not a bad word. Okay. It's not a bad word. It's not, you know, because a lot of people say, I will never, you know, why should I submit to another person as long as we are equal? What is the question of submission? Where is the question of submission? We are equal. Right. But the fact is this, that the submission of the wife demonstrates love, demonstrates support and also demonstrates that, okay, I recognize and acknowledge that God has appointed you, you know, as a leader, as the head of the house. I acknowledge that.  It gives the husband a lot of confidence to say that, to know that my wife is actually supporting me in this. And she demonstrates her support by being submitted. Okay. So being submitted means a lot of things. It means I'm not competing with my husband for the position of leadership. It means that I'm obedient to God.  So imagine, you know, this is actually causing the marriage to thrive and flourish. Okay. So as long as wives understand, no, no, no, the big thing is this, that the husband loves the wife as Christ loved the church. And out of that loving leadership, right, in response to that loving leadership, the wife eels in submission. So you see the beautiful picture, right? It's not the husband demanding submission is not that the husband, out of force, making the wife submit, but it's from a place of loving leadership. From a place where God has designed and from that place, as the husband carries out his role, God appointed role as a leader in loving leadership, then it becomes an actual thing for the wife to submit, to be yielded to this design, right? So we see that. So it's being obedient, it's freeing, it's also empowering the husband to lead. Okay. So we all, we see that it empowers the husband, it boosts the confidence of the husband, it empowers the husband to lead, okay, to maybe the husband, and we're just saying that, okay, wife is constantly saying, he's not leading in all spiritual matter, he's not taking decisions, but maybe that is so, but also we need to check and see, am I empowering him to do that? Am I empowering him? Or do I make fun because of my competence, because I'm better at certain things? Do I constantly put him down, right? Or do I constantly challenge him, challenge his leadership? All that, we need to look and see, wife is looking, reflect and see, am I actually freeing him to be God, to be whom God has called him to be as a husband, right? So this submission means all this, but submission does not mean that one is inferior. I think that is the greatest fear a person might have to submit or to surrender, saying, oh, how can I do that? Or maybe that person has grown up in a place where there was constant conflict and there was constant put down and the person had to really, the other woman, the girl had to really, to really rise up and rebel and to make her voice to be heard, right? In that kind of a, you know, maybe you said, which maybe she grew up in that. So for her, any kind of submitting to leadership is a problem because she's been wounded, she's been hurt and she had to really fight and struggle to be heard, to be respected. She had to do these things.  So if a person comes from that background, right? And with that understanding, now she's going to be, it's going to be difficult, but the moment the person understands, this is actually what God's design is. This is his intention, right? It is, it does not mean that I'm inferior. It does not mean that I'm, you know, I don't have qualities. I don't possess skills. It never means that. So when a person understands that, then it frees that person to submit willingly. It does not mean that I need to compromise on my individuality or lose my identity.  He has given us our identity, our identity, you know, in our relationship with Christ, our identity is strong. We have certain unique personalities and God respects that, values that, right?   So when we say I'm submitted, I'm not saying that my individuality is not there anymore. My identity is not there anymore, right? Also, submission does not mean that it's blind obedience. Well, the husband is always right. No, it doesn't mean that it does not mean that I can be a though man, I can be just used like an object. No, it does not mean that. So now, now you see that submission in the light of all this, right? We see that submission is a beautiful thing. It's not a problem in the light of this. Well, will the husband make mistakes? Yes. Will the wife make mistakes? Yes. Right. And that is why we need to grow in our understanding of our role and really take that up and say, okay, God, you know, as part of our Christ likeness, this is also one such thing that we say that, yes, Lord, I need to change to be this, to be the best husband that I can be, to be the best wife I can be. And I need to prepare, I need to let your word, but the truth of your word renew my thinking. But I need to renew my thoughts to the truth of your word. Now, society is saying something. My family is saying something. Now, this is how a husband should be. Recently, I just had the conversation, the wife was saying that the husband is doing something which is terribly wrong. The wife is saying that, my family is saying this, men will be like this. I just need to adjust and go. And then we like this. And then, you know, it's a question of, it's a thing of matter of abuse. So when it'll be like this, we need, we just need to adjust and go. No. Right. This is how God wants marriage to be. And this is how he is designed it to be. So there's no question of saying that, okay, I will be used like a domain and I will be used like an object and then, you know, and, and be considered worthless or no, it's not that God, that is never God's idea. And that is never God's design. So submission is not bad. Right. So when you look at the other thing, which is respecting the husband, then we see that it flows automatically. It says, I think we see it in efficiency, right. Wives respect your husband. So submit your husband as to the Lord and also in verse 33, let the wife see that she respects her husband. So respect is something that is due. Something it means to say, I honor you. I appreciate you.  Don't keep comparing, okay, that person is like this, that person is appreciate the uniqueness of this person whom God has brought to be a husband. So appreciate the uniqueness, right. And also help by assisting, supporting, encouraging. So we see that Genesis 2 verse 20 that God says, I will create someone to be the helpmate who is suitable, who will be companion, who will be the helpmate, right. So that's God's intent for, for, you know, why he created, let's look at that Genesis 2 verse 20. So there was not found a helper comparable to him. So there was a need 220. And then God creates and the Lord God, he took, closed up, and he made into a woman and he brought her to the man. Okay, so we see that, okay, so this particular need of companionship of helpmate is a big thing. Okay, so when the wife says, okay, can I assist, can I help, you're actually fulfilling a big role in marriage as the wife. So it's not something demeaning, it's not something that, something that is, well, you're saying that I'm inferior therefore I need to do it. No, as long as the wife understands, this is the original design and intent and I'm actually fulfilling that role. So the wife also feels fulfilled. Well, that's a beauty thing, beautiful thing. The wife also feels fulfilled and the husband is liberated to do what he needs to do. Okay, so, you know, of course, you know, if you're preparing for marriage, there are these exercises that you can do or if you are in, if you are married, then you can actually, as a wife, as a husband, you know, you can take some time to actually list down, think, list down, you know, how can I love my wife? How can I nourish my wife? How can I cherish my wife? So it's, it's, it'll be a very good exercise and maybe, you know, you can attend a marriage seminar and that'll be a good thing as well. It can really enrich your marriage. Okay, so we'll stop here and then we'll come back and we'll look at some real-life examples, you know, talk about submission and then continue that. Okay, take a 10-minute break.


Hello, I'm Dr. Sunil Kini, consultant joint replacement and arthroscopy surgeon at Manipal Hospital's Bangalore. To start with, there are four important ligaments in the knee joint. One in the front and back, which we call as the anterior cruciate ligament or ACL. One in the behind is called the posterior cruciate ligament or the PCL. There are also side-supporting ligaments on either side of the knee. One on the inside is called the medial collateral ligament or the MCL. And the one on the outside of the knee is called the lateral collateral ligament or the LCL. So, the physiotherapy for various kinds of these ligament injury and post-surgery is slightly different. So, I'd like to mention about the more common injury in about 80 to 90% of the cases, which is the ACL or the anterior cruciate ligament injury. So, once the surgery is done, it's important to start with the physiotherapy as soon as possible. The physiotherapy after an ACL surgery continues for up to nine months after surgery at the point of time at which the patient can start sporting activities also. The knee ligament ACL surgery immediately after surgery, the patient has to be on a brace, what we call. For the first two weeks, it's going to be a straight knee brace. And after that, after a stitched removal for the next four weeks, we usually put the patient on what we call as the hinge knee brace in which the patient can actually bend the knee by himself or herself. The other exercises which we strengthen upon immediately the day after surgery is the static quadriceps exercises or also what we call as the thigh-squeezed exercises. We also start about heel slides, hamstring exercises, assisted or passive knee bending and knee straightening exercises as well. Immediately after surgery, the patient is expected to have some amount of pain and will be using a crutch or a walking stick say for about the first week after which it can be slowly discarded. During the second and third week, it's also important to continue with the physio. The initial goals of physio is to get back the knee range of motion and secondly is to reduce the pain and swelling and also thirdly is to strengthen the muscles around the knee. After the first couple of weeks, we start the patient as I previously said on a hinged knee brace in which the patient can bend himself. So after six weeks, usually the brace is discarded. The other set of exercises which I said the open chain exercises are next started in which the patient is encouraged to do also do a stationary bike as well at the end of six weeks which continues up to three months. So there's various sets of exercises which we divide as the first two weeks after surgery, two to six weeks at three months, six months and nine months. So at the end of nine months, patient would have a pain-free range of motion in the joint as well as the strength needed to carry on with the sporting activities as well. It's also important to emphasize here that after an ACL reconstruction in which we put a new ligament into the knee joint, the first six weeks to three months is the time limit at which the graft which we put in is at its weakest. So after three months, the graft has attained a reasonable amount of strength after which certain exercises can be or certain activities can be carried on.


We at Modulite have had an incredible experience here this year. It's very great to be back in person and meet everyone in person. It's been very successful and productive and we're happy to be here and we can't wait for next year. I've learned so much about optics that I didn't know before, met so many more vendors that I can actually use for my PhD and I've had so much fun meeting other PhD students. The best part of this is that everybody who is here is really wanting to be here. There is simply no substitute to being in the same space with a person and having a real conversation. See you next year!


Ladies and gentlemen Salah Mike here again talking about technique We're talking about the bench press and although we've talked about the bench press a lot We've talked about all these things a lot and you can always refer back to those videos We do have a playlist of bench squat dead for all the informational stuff that we go over but something I keep seeing time and time again from You know middle tier middle upper tier and beginning lifters is not getting our Elbow position correct in the bench press now people are talking about tucking Tucking your elbows and that was kind of a cue I guess started in the bench shirt because it's just so important because you can't stretch the Material on a bench shirt with going elbows out now Over tucking is also very common and then choosing your grip placement and we talked about this a little bit too Boris Shaco Roughly translated says that you should choose the widest grip possible and over my years I used to not necessarily agree with that But the more I bench the more I coach the more people I see bench I Starting to agree more and more and what he means by that isn't that everybody should be full legal grip Which means pointer on the ring, but you should go as far out as your shoulder mobility as thick you are as Comfortable as you can bench because that's what gonna allow you to do is obviously cut down range of motion Same reason we kind of arch or we try to stick our sternum high now We're not gonna overly arch but if it can cut down range of motion and help stability We're gonna help do it and same thing goes with that grip with if we're wider out That stability in the range of motion shortens and over time if you build a right musculature in that position with proper programming and technique You will be able to bench press the most amount of weight What I see is people benching too often about shoulder width now when you talk close grip You know old-school close grip guys are benching like this and that's great to build the tricep But it puts a lot of pressure on the shoulder what happens is is you can't get that range of motion The range of motion is longer the closer you're Benching you get internal rotation of the shoulder To try to touch the bar to your chest now causes an immense amount of pressure onto the front delt and people always talk about Oh the front of my shoulder hurts my bench the front bench hurts the front of my shoulder blah blah blah blah You know what I mean, and so what we can do is obviously tuck that shoulder down Move that grip further out and now my elbow is traveling less Distance past my body see if the closer it is it has to go way back here behind my body To touch my chest if my grips moved out my shoulders tucked my sternum high now I'm touching my chest and my elbow is is Equidistant or in line with my body and that's going to allow for again less range of motion But less pressure on that shoulder and then we can build a muscular to our chest tricep shoulders either through accessory or through That movement itself the other big key factor is with that same position We don't have to overly tuck and rotate that elbow We can just keep our elbow in line with our form in line with our wrist and as long as our shoulders are tucked and down My elbow will end up in the right position when people are talking about tucking their elbow The real issue is is that people are shrugged up and then elbows out and again? That's a very long distance that my elbow has to travel for the bar to touch my chest My shoulders internally rotating causing pressure here And now we have a long range of motion a lot of pressure on our shoulder and our elbows traveling way past our midline Which is causing more pressure on our peck which is where all the peck tears happen And that's where that cute tuck your elbow happens, but if I control the shoulder joint Pulling it back and pulling it down pulling my sternum up grip natural width a little bit wider than you may expect We're gonna be a lot safer and a lot better position to press for long term The other thing is again with that elbow position people will bring that grip way in maybe shoulder width Maybe just outside and not that this is wrong I just don't think it's optimal for most and our elbow will end up on the outside of our wrist again Now we're turning that thing into a tricep extension think about tricep extending your heaviest weight now No one would say this is a good proper push-up position or a press position So then why would it be a best bench press position to lift the most amount of weight? Safely move that grip out keep our wrist form and elbow stacked as much as possible Keeping that shoulder tucked back and in Sternum as high as you can Leg drive and all these other factors will help you keep that in position by pushing yourself back onto your traps And then we're gonna have longevity good programming over a long period of time Mixed with the good technique will not only build the right muscular cheer to get strong But also build the proper form that we won't get injured and we can live for a long time So today is my second bench day of the week and I'm purposely doing kind of a closer position With my elbows outside my forearm to build my triceps again that extension movement will help build triceps along with my pecking shoulders So I'm using a little bit less weight doing sets of five to eight with a putting myself at a disadvantage in form So then when I go back to my form competition style peak whatever it may be everything's gonna move a lot easier lots move it Concept of underloading using less weight making the form or exercise more difficult So we can build strength over time a pause squat is more difficult Then your regular squat because you're losing that elasticity that rebound out of the hole So you use less weight, but you make the exercise more difficult so you can still get stronger Well handling less overall load less overall systematic stress Same applies for overhead, but obviously now we're vertical so How we stack our wrist and elbows gonna be a little different because we are kind of internally rotating So our grips gonna naturally be a little bit closer to get those forearms On top of our elbows with the bar on top so a wider grip now we have that same issue of almost over tucking So that's not gonna be optimal either watch out Move the grip in stack it up straight up and back ladies and gentlemen build your bench press We do have free bench press program peaking program always available below free infinite program It's a repeatable four weeks customized to yourself read all the directions there before you start DMing me all these Questions read the directions that come with it We explain how to use and how to customize it for yourself guys. I'm selling Mike. I'm out of here appreciate you


Welcome, everyone. This is the Jenkins documentation special interest group. Let's get started. I'm going to share my screen and we can look at the agenda and talk through it and then go through the material. So on today's agenda, we've got report of previous action items. And I've put in a documentation progress status report, including a couple of demos and some discussion. Then developer meetups are a topic for this time. And then we'll look at some statistics on contributors and contributions to close out the session if we have time. Let's capture those statistics on contributors and contributions just in case we need them. And that's it. Oleg, anything else you'd like to be sure we include on the agenda? No, nothing specific. Well, one topic would be about Google Season of Dogs. But yeah, maybe we need more people to discuss it. And it's not timed pressure. Okay, well, but that's a that's a very good one. Let me put that. I'm going to put that down to the end right before the data report, because as we consider participation in Google Season of Docs. It needs a lot more preparation. Good. Okay. All right, thank you. Okay, so report on previous action items. I had created a poll request, but it was empty for Docs project ideas. I've closed that rather than spent waste time in the poll request queue with it. The idea that I've got is I'm going to map the pages and concepts from the wiki to Jenkins.io, then create tickets for those concepts so that we can then have anybody pick up a ticket as a newbie friendly ticket. And use that as a way to make progress on this. My apologies that I haven't done this yet. It's coming. Yeah, one thing I don't understand here is so for me newbie friendly documentation tickets and Docs project ideas were quite orthogonal. Because newbie friendly tickets are small tasks for those who want to just start and documentation project ideas were rather for Google Season of Docs and other bigger programs like community bridge. So they would have been rather about major projects. So both activities make sense, but I don't think that newbie friendly ticket. Yes. The thinking I had on that was that newbie friendly made sense for some of the tasks because they may be purely a transposition of content from one place to another and small tasks like that could easily be newbie friendly. It is a separate as a separate topic. It just for me it fit with if there's something on the wiki that is in fact easy to transform that justifies being newbie friendly. There are other things which are not easy and really are a major idea that won't be newbie friendly. Yeah, to understand that, but what I was trying to say that newbie friendly tasks are not Docs project ideas. Ah, okay. You're saying that those are too small to justify being a project idea should be a major effort. Yeah, so well, it still makes sense. It's probably just another action item because we need newbie friendly tickets. That's for sure. Yeah, so, but if we have a documentation project, for example on community bridge, then while we could take 100 plugins and say we are going to make a documentation project, but to be honest, I don't expect it to be exciting for whomever works on that. So I would rather not plan such project. Right, right. I agree. I think I think the concept I had for newbie friendly is fair for you to your observation. Your observation is accurate that, hey, that may not belong in a project idea. We just put up as part of our newcomer package. If they would like to contribute a documentation, they click through to the newbie friendly and they can get them. That's good. Yeah, I like that. Okay, so other gaps. Okay, thank you. So then as a regular action item and ongoing action item, I have a I need to I send out a summary of the doc SIG to highlight that for the governance. I assume that's still okay Oleg that I don't need to report those. The JEP we had agreement is okay or the governance board is okay just receiving a summary by email. So I think that it would be nice to have, for example, summary as a death list. That's for sure. I mean, for example, quarterly summary or monthly summary doesn't matter. But if you talk about bigger scope, for example, if you wanted to highlight all the work which happened since the beginning of the SIG, it might make sense to have a blog post. In my new year blog post, I just added some stats. But if you want to write, let's say a separate blog post about documentation SIG, I think it's a great opportunity. Okay, good. All right. And then we've we had the idea that we want to do a developer meetup. And I think I've got an additional additional idea for developer meetup that we'll talk about later on here. Well, correctly, Oleg, this the developer meetup, this one probably won't happen in January. It seems more likely a February or maybe a March topic. Yeah, it looks so. Great. All right. We have some regressions which are not related to documentation SIG, but right now we are not ready to deliver on that. Right. Okay, great. All right, then on to the documentation progress report. So I wanted to show a demonstration of the plugins.io static site. I am thoroughly impressed with how how much good and solid work Gavin Mogan has done. And what a wonderful piece of work this is to show to people. So, instead of a dynamically generated site, it's now static. So if I click here, here's the plugins index. And it was the page opens quickly. Now, if I choose some plugin, let's say mailer. There it found it and bang, it's up and running no generation process. This came from GitHub. It's been extracted from the read me as code. Likewise, we get the same thing with their plugins now that are allowed to have a table of contents. Like the get plugin now has this automatically maintained table of contents here. Thanks to it being an ASCII doc. So with config with documentation is code. We've got a much better set of documentation for plugins and the plugin pages load much faster. As far as I can tell our search rankings seem to be improving. We've got got good results happening. If we look at things like configuration is code. It shows a really elegant use of badges to highlight the progress of various pieces of the of the code so it's got a link to its code quality pages. It's got all sorts of helps for users. Now there's still more to be done. There's active discussion. Should we collapse these dependencies. How should we present but Gavin has done simply an amazing job on this. Any things that you wanted to be sure we highlighted here. All right, so then in addition to the progress that's been made on the plugin site. We've also we're in progress on migrating documentation for plugins from the wiki to GitHub so that instead of maintaining documentation separate from a plugin it's inside the plugin source code. A really nice plugin migration progress report that Gavin provided for us as well and that is now hosted on Jenkins.io. And delighted to see that we have over 200 plugins that have completed their migration to documentation as code. And several even in this top list have pull request pending that are ready to ready to go for the next release of that version of that particular plugin. To be specific we have around five or sorry around 50 plugins which have pending pull request opening releases. But we have some implementation issues which still need to be delivered. So I'll talk about it later. So the next topic by the way. Oh, great. Yeah, but right now there is much more than 90 plugins waiting. Excellent. Well, and I think that's good to talk to the next one. Why don't we go on to that next topic. Oh, like, oh, right. Oh, like, let's have you take on the documentation migration topic. Okay, just a second. I can't hear you like my back online. You are back online. Very good. Okay, so. Okay, let's keep our fingers crossed that this network is better. Okay. Okay. So I just wanted to add a few things to what Mark presented. I'll just share my screen. See, I think I have to stop sharing. There you go. I've stopped. So now you should be able to share. Okay. This my screen. Yes. So by the way, one thing Mark forgot to talk about to say about plugin site that the plugin site is also now mobile friendly because before that in the previous implementation, we had some issues with styles, etc. But now it was updated and it looks much better on mobile screens, which is important because now we can just reference links in social media and they don't look like crap. Yeah. And I am, I am delighted with the mobile layout. I think he's done a brilliant job with it. Yeah. So thanks a lot. Okay. Now let's go to the immigration status. So, as I said, what we have on the, the reason for that is that we basically, am I still online? You are. Yeah. No. Yeah, because in my case, it works just makes everywhere. Okay. So our problem is weak exporter that it pulls information from just from her code at the least of pain and cold requests. And for us, it's a moving target. So I spent some time this week to adjust the query GitHub and to find all the pending call requests. So what I can say that we have 24 plugins, which already have merged the documentation migration to GitHub, but which haven't been released yet. And 19 plugins, which have been a request and if you're maintaining one of these plugins, probably you would like to take a look. So, okay. So, and the status of those pull requests is reflected in the column that they occur in. So it's automatically updated when someone merges it moves that move something from left to right. I cannot automatically automate that because automation. Well, I will need to update it a bit. The default automation on GitHub for Kanban horse is to down. Oh, it does. Okay. Yes. So I will need to update it. But right now, automation is disabled for this book. So you have to look at this. More than a month of requests, which emerged. So I cannot. Okay. And I, I admit that the, the crucial thing here is when a change for wiki doc for to convert GitHub documentation from to to get a documentation from wiki happens. The merge is necessary, but it's not sufficient because we need to release of the plugin. And that's not a column that's represented here. Oh, well, there is done, which basically means release. For us, it's not a problem for moving from merged to done because wiki exporter. If you go here. It's for released plugins, it posts information from the update center. So when you take a look at this status, oh, basically this information comes from the update center. So it has some luck. But once you release a plugin in a few hours, it will be moved to bring status here. So you do not rely on this board. But it's rather for our information as documentation seeker. So that we can look here. See. We need some nice. Because. Yeah, that's what we have. And yes, we probably can start this migration, but yeah, the status for the most used plugins becomes better and better. And we know that all pipeline plugins have been migrated. They just need to release. So, oh, so we've got a and now are the pipeline plugins that have been migrated but need to release. Do they appear in your project board they do. Because I captured some requests. Maybe not all of them. Yeah, for example, here, change your roles for each plugin to point to GitHub. So it's for pipeline model. We finished declarative. For other pipeline plugins, I might have missed the pull request to be honest. So I need to double check because again, there is no automatic creation of this column. Because plugin maintenance just create whatever they want. We need to capture that somehow. And if I want to add things to this board, is there something particular or some propitious permission I need to be granted or as a contributor to Jenkins, can I already do it. As contributor to Jenkins, you can do that. So how I configured the board. Just so settings. No, I just edit documentation. I stick members. Yeah. It's not everybody. Oh, okay. Well, I can basically open the floodgates if somebody wants. But yeah, This is great. The people who are doing the work are listed there and can record it. That's, that's wonderful. Yeah. Okay, so let's go back. Okay. Yeah, so this board, well, basically is better than the implementation we had before, but it's still far from the video. Here you can just query things. For example, so how I do that, for example, GitHub. Yeah, I killed that. You can find some cool requests. For example, here there is a Google auth plugin, which is not listed. So we can just drag and drop it to this column. Yeah, so you can use more advanced queries to capture these plugins, but yeah, it's still a lot of missing, missing plugins. Yeah, moving docs from wiki security. So here, for example, we can see that the status is merged. So I just go to the pool request. I can see that it's moved. I can check the commit. Here I can see that this request has been actually released. So just has already been released yesterday. I just put it to them. So I don't need to worry. And yeah, you can see that, for example, there is pipeline support plugin. So one was referencing, which is missing. And here we can see that it was rated, but it wasn't released. It was released. So that's again, when you would drag into the done column. Nice. Yeah, right. So it's mostly clean up, but you can see that there is a bunch of such plugins. So whomever wants to maintain that basically what you need to do for automation purposes, you just drag and drop them to this column. Because the rest doesn't matter. It's just a history cleanup. Unfortunately, there is no good automation for that. So it was released. So they can. But yeah, it's not all process. Not the deal. But it gives us it gives us a very visual visual picture. Now, I assume that the wiki exporter report once they've released, they should also appear in wiki exporter. Okay. So Oleg, I think we may have lost you again. They released. For example, we know when support. We cannot release.  So you said something about a support plugin released. I just said, yeah, I just said that we had the pull request, which we reviewed on the board. And if you go to the status, you can see that the status is green. Okay, good. So the so the wiki exporter is showing the correct, correct status as well when it's all the way to release. Good. Yes. So it doesn't hit any kind of dashboards on my directions. Eventually it will be there. So this board is rather for in progress pull request.  Right. Excellent. Okay. So that's what I wanted to say. And in parallel, I'm also doing some migration for non-plugging documentation to Jenkins. You said you were doing your back. You said you were doing migration of non-plugging documentation. Exactly. Because we still have a lot of other docs on wiki. I moved a team jack, I moved a bunch of governance docs and moving the remaining docs gradually. Sometimes we had to use advanced migration, for example, for governance board meetings, because it was just not sustainable to keep the agenda on the plugin side, et cetera. So we improved the tooling there. Okay. I can just show it to you. So here's for example, governance meeting. So now we use combination of static website and Google doc. But Google doc is embedded. So even if you don't have permissions to this Google doc, you can just go and suggest changes directly from the Jenkins IO page. So you don't really need to worry where this Google doc is located. You can find it here. So there are more such things, but it requires additional steps for the migration. So the work is in progress. Excellent. Thank you. And I know how much I've enjoyed interacting with that style of page. That's been a great improvement. Thank you. Okay. So before we move on, I'll just move it here. I'm not sure whether I'm able to show the next demo. So I can definitely show it, but with network stability, it makes sense to show it right now. I can try. Yeah. Okay. That'd be great. Yeah. I would love it. I put it in there specifically because of how pleased I was with what I've seen and how much it's made my job easier doing work on chainzlogs. Okay. So let's just spend some time on that. Okay. I can just do the demo from my laptop. Okay. So for those ones who is watching this meeting, there is a change log for Jenkins IEA. It's hosted here, but this change log actually has a machine readable format. So it's a change log YAML, which is hosted on Jenkins IEA. So I will just find it here. So there is, so yeah, there is a weak YAML file. This YAML file, it has fixed structure. So this structure includes references to issues, public requests, messages to be displayed, references to your fees. And actually there is additional, there are additional features. For example, we can put multiple references so that users can see additional information referenced. And you can see an example here. For example, we have removed and changed logs using this mechanism. And we're also working on referencing contributors. So if you scroll down to the recent change logs, you can see that the format expanded because here we inject authors to changes. And there will be more changes before it's really visualized on the Jenkins program interface. But at least there are some changes that every time you cut a release in the case of Jenkins, it's at least to be clear. Somebody has to create the full request and to submit this change log. So at the moment, it's Mark Wait who is doing that. Before that, it was Daniel Beck. Sometimes I was doing it in emergency cases because nobody likes my change logs. But the problem that somebody has to do that every release.  Like the rating can be even full request. So in order to do that, there was a tool which was originally created by Daniel Beck, which is called the Jenkins change log generator. Basically it's a tool which was able to draft these YAMLs for particular versions. And it also supports LTS change logs because our LTS change logs are slightly different. And the most of users use them. So yeah, these two can also generate this kind of change logs. I won't be showing it today because it requires access to Jenkins Jira to pull additional information. And I don't want to expose password there. So yeah, no demo for stable change logs, but I will show weekly. So this tool was created by Daniel Beck, but historically it was quite difficult to use because it was a bunch of Ruby scripts, which wasn't running, for example, on my machine. I'm a heavy user of Windows and they were not running on modern machines, which were not using Bash as a default interpreter, et cetera. These scripts were still working, but they also had issues with the format because they were not representing the change log format strictly. So they required a lot of minor elections. And yeah, in November and later I spent some time in order to make that. So you can see that there are some releases. And now the tool operates in Docker and it also generates change logs, which are much closer to the final format than they used to be before. There is still a lot of things to be done, but at least everybody can take these change logs and just generate them. So let me show it to you. I am using official Docker container. So we have Chinese delivery configured for this repository. And if you need to cut a change log, you basically run it with your Bit Hub credentials, with Bit Hub in order to access the REST API to pull information about the request. And if you generate stable change logs, you also need access to Jira because our important metadata is actually in Jira, not in Bit Hub. It's something we could improve, but yeah, that's the current state. So I run this tool. I didn't pass version parameter and it will be just generating change log for the incoming weekly release. So basically based on all pull requests, which we have integrated, and the tool can also generate divs between versions if you need that or generate a change log for particular version. And here you can get this change log. So it's generated automatically. Here you can see that, well, basically there is a pull request. Fixed by JC, which was merged recently. It's a bug fix, references pull request issues, and it includes a draft of the message. So currently the draft includes pull request title. So similar like we do in release the draft of pipelines. And it also includes proposed change logs because Jenkins pull request template for Jenkins code also includes proposed change logs. So Jenkins CI Jenkins CI Jenkins. So we can just take a pull request. I haven't seen what's this request, but it's from Daniel and he followed the template. So here you can see that there is proposed a change log, which is the text which will be added in addition to that. So then when Mark or somebody who is a change log copy editor, he will just take this text and process it to the final change log. We can improve it later, but at least generate some stops. And it can also break down the change logs if needed, because the main purpose of this format is to actually supply multiple change log countries if needed. And it's a problem with release drafter because for release drafter you have to go to the peer title, modify it to include all the text, et cetera. Here we resolve it in a different way. It could be supported by release drafter, but it's just not supported at the moment. So that's how it works, but it wasn't enough for us because we also wanted to make it a part of a continuous delivery pipeline so that there is no automation, no even need for running that. And it will build the ideal to provide users for change log of incoming changes so that users can see what's going to land. Maybe on Jenkins.io or at least on GitHub repository. For that purpose, we don't have a tool at the moment. We didn't have a tool, and now we have a hook. The most of our repositories use release drafter. And for Jenkins, you can see that there was release drafter, which was again generating a YAML stuff, which is similar to what the core change log automation tool does. But yeah, it was generated by release drafter with a lot of hooks. Starting from the next weekly release, it will be reverted and now we generate user readable change logs. So there is a glitch and the change log gets duplicated. I still need to figure out why, but yeah, we'll fix that. Well, it's likely because of inheritance from the master file. But at least now there will be a markdown change log, which is released immediately after the weekly release. So you don't need a full request towards the master change log to be merged. And now it's also possible to see incoming changes. What we do, I spent some time to make this Docker container actually compatible with GitHub actions. It's not documented, but you can use it from GitHub actions and I will show it to you. So yesterday, Mark was grumbling about the Travis demo during the Jenkins seed meeting. Today I'm doing GitHub actions demo. Yeah, what we have, we have a simple pipeline here. It's called workflow. And it actually involves multiple steps. So it invokes a step for GitHub release draft. The one I wish you've already seen, it also invokes our change log generator. And then it invokes publishing. And for publishing, I first started publishing to release draft. It costs some issues. So it's not something I'm going to use at the moment. But we also have change log demo. So here I just inject the change log draft, which is generated by this tool in the artifact being generated by GitHub action. So what it means, if you go to actions, you can see that there is change log draft action, which has been triggered on every push at the moment. Later, I will implement support for tech pushes so that we can easily access change log for particular tech. But right now you can just see that there is a bunch of full requests. And here, for example, we have full requests for the last week here because it's a change triggered by KK. So for example, we can just go here and see change log draft generated for the previous release. So there is a bunch of actions and there is generate YAML change log. So what you've seen in my console, you can also see it here. But for real change log, here's a draft being generated on the GitHub actions. And after that, this draft is being uploaded. So I'm not sure whether it's available for this. Oh, like I think this one you picked was not the release from KK. This is one of yours. I think you picked one line below. Yeah, one line below because release from KK basically cuts the release and the change log for incoming release will be empty. Oh, I see. So you had to do it. Show this. Yeah, right. So that's why I want to implement support of text so that it will become more trivial. But yeah, I haven't gone to it and got to it. And here there is change log YAML. So again, it's generated by two. We can just download it. Unfortunately, it will be the same, but just in archive. So you can upload, download YAML, take it in, submit a full request to Jenkins.io website. So this is what we have now, what we can do later. We can automate creation of full requests. We can improve this formatting so that there is pipeline which basically delivers full requests to Jenkins.io. We also can add support of text so that it will be explicit where to look. And yeah, this is just one of my next steps for this generation. In addition to that, what we want to what we need to do for the next releases is to automatically generate update guidelines. We started doing some changes on that front. For example, now there is a new pull request template which requires people to specify update guidelines if it's applicable. So for example, here it's not applicable, but we can take full request. Here we have labels for that. Label, and here we have, we have too many labels. But yeah, great guideline needed. So there is a tag here, and you can see that there are seven pull requests stuck. And the last one is for example from Jeff Thompson for removal of agent protocol. The change that we announced for the previous speaker. And here you can see that we have a text of these proposed change logs. So we updated our review guidelines and now we expect submitters with breaking changes to propose update guidelines right here. So we can use the change log generator tools to generate upgrade guidelines. Well, not final ones, but at least drafts. So that we can have a page here and again mark this page. Oleg, your audio is breaking up unfortunately. Could you take that last, since you arrived at this page we've lost a bunch of your audio. Could you describe it again? Yeah, so what I was saying is that these guidelines are structured. So if you open this change log you can see that there are multiple entries. And these entries again, they're using machine readable format. So this guideline is generated. And it means that we can also generate templates for that. So let's take a look. I'm just planning to show one example. So... Yes, Oleg. Somewhere here. So my network breaks again. Okay. My plan is to start generating this as key dogs so that we can consume them later. This is just amazing. Excellent work. I am so pleased. Thank you very much. This is really great. Yeah. So we can call this to set out to Daniel Beck or something like that later. But basically it automates the work which Daniel was doing for years and thanks a lot to him. And now Mark is doing that. So yeah. Let's try to automate it a bit. Thank you very, very much. It's exceptional. I know how much I enjoyed. How much it has improved since I started doing it and how nice this tooling is. Looking forward to the tooling improvements that are coming. That's even better. Thank you very, very much, Oleg. What a great experience it is. Thank you, John. So I guess that's it with my demo. There is no people to ask questions. But if needed, you can ask in Gitter. Right. So the DocsIG has its Gitter channel available as well. So it's just quite active thanks to Gavin and team. It is. It's been very active. That's really great. Thank you. So next topic that I had on the agenda was Janka's Developer Meetups 2020. And one of the ideas that came to mind as I was looking at the configuration as code plug-in, I submitted a pull request to it for a minor change and saw a very impressive array of tooling that they automatically invoked that I had never used before. So yeah, I know how to use dependabot and I know how to use release drafter, but I've never used Codesy. I just started using Sonar source, but they also have an LGTM.com that appears to do security checks. And I assume there are other services like that. And my thought was it might be good for a developer meetup to bring the configuration as code team or others together to say, hey, here are some things that are available in the community, in the open source world that could help you do better at your plug-in development. Oleg, your comments, what do you think? Is that viable? Is that a reasonable thing? Are there other tools I should add here? Well, there is a lot of tools we could integrate because if you take a look at Jink's organization, there are around 20 different need hub applications which are connected mostly for different static analysis use cases or code style checks. So Codesy, Sonar and other tools that are just examples of these tools. And if somebody wants to come to the meeting and change information, it would be nice. Or especially if somebody wants to document guidelines about how to use these tools with Jink's plugins. Because here we have guidelines for these drafters, we have guidelines for dependable, well, in some sense, Google Doc, but not for other tools. So why not? Good. So good point. Can I assume there's a way for me to query and see what the applications are that are used and which plugins are using those applications, then I could potentially reach out to the authors, the maintainers of those plugins and say, hey, would you like to join us for this session and tell us how you're benefiting from this? Well, in order to get to the list, you have to be a GitHub organization admin. I'm not sure what you have. Okay. So I do not. I'm not an org admin. Yeah. I can provide some links. Actually, it's even more than 20. So yeah, if you just create an action item for me, I can provide this mapping. All right. So the plugins that use them. Great. Thank you. That feels like to me a very interesting, and I'm not sure we could assemble it in the roughly one week that we have prior to me going offline for about a week to do FOSDM. So I assume this will be a February or later developer meetup. But I would like that, and I'm happy to convene it. I would, I would love to moderate it and gather the people together. Well, if you need to meet up in one week, I could do a review of Dependabot because I have everything to run it if needed. So it will be likely a shorter meetup, maybe 30 to 40 minutes with all of the review of discussion, but I can do it next week. Yeah. And for the rest of the tools here, we can just start doing it in the background. This is after something we already presented. Right. That was done in a previous, in a previous developers meetup. So do you have a, do you have a, you would be okay if I scheduled something for next week? Yes. Great. All right. I will do that. First day of Friday. I guess Friday will be the best reason, the best day. Great. I will do that. Thank you. Okay. Thank you, John. All right. And then we had a topic on the Jenkins palm and bomb. And you had indicated there's probably some additional work there. It needs to happen development side before we host a meetup. So that when we let wait for a few weeks and let it continue revolving. Yep. Excellent. So yeah, then we do topic for dependabot. And yeah, probably I'll try to get somebody else to cover the JavaScript part because originally I didn't want to cover that, but we have some examples. So yeah, we can just announce one thing. So yeah, also I will cover Docker. That's for sure. Oh, okay. Good. All right. So, and that's one that I know how to use the Java one. I've never used the Docker one. So that's good. Java one works better. But Docker kind of works. All right. Great. Excellent. Thank you. Okay. Thank you too. All right. So Google season of docs. We are, we are, we are actually past time. Oh, like I'm prone to say that's shift Google season of docs till next week's meeting. We can talk further about it then. I did want to go over a brief look at the data from the contributors and contributions. Yeah. Really elegant. Thanks for your work on the time from pull request to engagement. We are averaging under 85% of our. Pull requests get some acknowledgement. Well within one day. And we just went on the latest bump to slightly over one day. But our, our. Output is really good. And the data from the whole clientile is very nicely in the one hour that the pull request backlog on Jenkins. I. Is looking really good time from PR open to merge. Likewise is looking good. We've merged six over 60 pull requests in the last month. And we've only got 11 open pull requests at this moment with 27 over 2700. That have been merged over the life of the project. really good. Let's keep doing it. Anything else you wanted to note there, Oleg? I think from my side. So yeah, one interesting start, which I posted in the New Year blog post in that we had 187 documentation contributors just during the last quarter. So it includes basically everybody who modified Markodon or SkiDoc files within JKSI organization and also within JKSI. So it's not an accurate number, but it provides some approximation. Excellent. Yeah, just for your thoughts. Thanks very much. Thank you. Thank you. All right. I'm going to go ahead. I think we're done. I'm going to go ahead and call this as a done session. Thanks very, very much for your time, Oleg. And notes are here. The recording will be posted to the YouTube playlist for the Documentation Special Interest Group. Thanks, everybody. Thank you too.