What is or what is meant by the son of God as well as the son of man now? This is a pretty difficult question and probably bears me having to do a more in-depth study But because people oftentimes use these two words without quite knowing what they are I just want to give a quick little lesson over what these words actually mean most people when they refer to the son of God or a son of man they tend to kind of Exchange both of the meanings for the other meaning meaning this most would say or many would say that the son of man would refer to Jesus's Humanity whereas the son of God it will refer to his divinity so starting with the son of God It actually has different meanings depending upon its context And so what it actually refers to especially in the Old Testament is it's really God's workers for example his angels Are called sons of God and there are times where you'll see his followers human beings call also sons of God even in the New Testament and so What we want to talk about is not those times when the Bible refers to son of God, but Wouldn't refers to with the article the definite article the the son of God. What does that term mean? well the son of God doesn't mean son in the sense of a father and sons relationship or Child of someone that one was produced by the other. No, it is up. It is from the genitive of Meaning this son of God would refer to a representative of God someone who's doing the work of God and More to the point. He's doing the work that only God can do such as forgiving such as Creating the world it says that he alone God receives worship, but so too does Jesus You see terms that kind of synonymizer to such as both being called father or Judge or the beginning and the end and so then we look at Matthew Where we see the term son of God as well as the term son of man kind of being both brought together So let's go there real quick to Matthew 26 verse 63 and 64 after the high priest asked him a question Jesus verse 63 kept silent and the high priest answered and said to him I put you under oath by the living God Tell us if you are the Christ the son of God Jesus said to him it is as you said Nevertheless, I say to you hereafter you will see the son of man Sitting on the right hand of power and coming on the cloud of heaven Notice how the Jews equate son of God with the Christ or Messiah Why because to them that's what the son of God is So now we're starting to get a little bit of a picture as to what the son of God means, but then Jesus Equates the two with the son of man now the son of man happens to be Jesus's most favorite term of himself Well, where does that term come from? Let's go back to Daniel 7 where the term is first found in the Bible in Daniel chapter 7 verses 13 You see Daniel speaking and he sees his vision and look what he says. I was watching in the night vision and Behold one like the son of man coming with the clouds of heaven He came to the ancient of days and they brought him before him look at verse 14 Then to him was given dominion and glory and a kingdom that all peoples nations and languages Should serve him his dominion is an everlasting dominion which shall not pass away and His kingdom the one which shall not be destroyed So we see son of man referring to Jesus as divine Messiah and and then we see the son of God Referring to Jesus's work. So what works do we see of Jesus? well him as the Messiah him as the Christ him as the Savior and so in a sense the son of man and Son of God they can almost in some cases be considered interchangeable almost like the way Jesus kind of Made the two synonymous in Matthew 26 son of God refers to Jesus's work as Savior Doesn't refer to his divinity Absolutely, the son of man refer to his humanity yet does but they both refer also to his divinity So what does son of man mean son of man refers to Jesus's divine nature as Messiah son of God refers to Jesus's divine working powers as Savior Do they sound similar? It's because they are


Hey what's up guys welcome to our training reviews. So a couple of people have asked in the past about me doing a review for my Range Rover Velos steering wheel. So I just wanted to go through all of the features that this steering wheel comes with and hopefully give you guys an idea of the capability of it. So let's just get straight into it. Alright so first of all just wanted to give you a little bit of an update on the actual design of the steering wheel. So it's got this nice little lever trim around it. It's very comfortable. It's got the Range Rover logo right there in the middle. Now this feels like it's made of sort of plastic but again it's pretty solid. You've got the metallic trim around the middle of it. You have this bump at 10 and 2 which basically is very comfortable when you're driving. You can put your thumb around the top of it and it keeps it nice and locked in terms of the grip.  In the winter months when you're driving you're gripping the steering wheel. It is actually quite cold. There's no heated steering wheel option much like you can get in some of the newer cars nowadays. But this metallic bit here is very cold even now when I'm touching it it's quite cold to hold so I would try to avoid using that. But you also have the shift pedals at the back of the steering wheels there. These are also made of metal. Right so the main standout feature for the Range Rover steering wheel are these two little panels here. They're both touchscreen gesture operated. So let's start off with the left one here. So here you have the menu button there right in the middle. So if you select that you'll see at the dashboard right in the middle you'll see it'll open up a menu option. So driver assistance that kind of stuff and you can cycle through by hitting the down option. So if I go open that again you can see I can cycle through. So I'm going to keep going down. So trip, the display, vehicle settings, vehicle information, driver assistance etc etc. If I click okay that'll basically update that to the next menu. If I select right I can keep going in and cycling through the different menu options. Press the left arrow to go back and then I can cycle through them again. So that basically brings up the menu and the system settings that you want to change for the actual car itself from there. Now obviously it goes back to the main menu if you don't do anything for 10 seconds. Next I'm going to be talking about this side panel here. These are the volume buttons so I can press plus or minus to increase or decrease the volume of the radio or the music playing in the car. But again if I didn't want to press I can simply just swipe and it will start giving me an option to increase the volume by going right clockwise or decrease the volume by going anti-clockwise to the left. So this option on the right hand side is for next and previous track if you're listening to music but if you have the radio station on this will go to the next station or the previous station. Like the volume controls this one cannot be swiped and taken out of context for the rest of them that only works with the volume one so this one you'd only have to press either the previous or the next ones. So if I show you an example I'll turn the radio on and then I'll click on next. It's gone to the next radio station here. The next option you have is this call button so if you press that that will bring up the phone menu so you'll be able to dial someone as long as you've got your phone paired for Bluetooth you can contact them and if you do take a call this will turn green and underneath you will have the red hang-up option there. This option here on the right hand side is the voice command so if you press that play magic radio station. Would you like to tune to FM or DAB? FM tuning to magic. There you go and that's the voice control there. Right so you notice that there's a little diamond icon here that basically means it's your favorites button and you can set that to do anything you like either via a single press or a long press so I'll show you how to do that so what you have to do is go into your Vela settings screen here go to settings all settings go into features and if you scroll down to the bottom there's something called favorite button select that you can see that there's the icon there so for my short press is to mute the music long press is to cancel my navigation so every time I use my navigation I've reached the destination I always have to go in to the menu click on stop guidance confirm and so on so this will just make it do that very quickly so it's really convenient there's loads of different options if you go in here you can see well actually there's not that many to be honest but it's probably the one of the most common parts of the features that you're going to use on the car now switching over to the right hand side panel this is basically your driving panel so set resume and the minus buttons here will be the cruise control so when you're driving you can just click on the set plus that will set the cruise at the speed you're going at at the time of pressing it if you'd like to reduce the speed and set it to something lower just keep hitting the minus and if you just want to cancel it you'll have a cancel option there as well so you hit that so when you're driving and you've pressed the brake or you've accelerated faster than the actual cruise control you can come back and hit resume and it will go back to the setting that you did this button here called limb that's basically the speed limiter so if for any reason you're in an area where you don't want to exceed a certain speed limit you hit that and it will set it at the speed limit that you're driving at at that time so if for example you want to limit it at 40 miles per hour you can do that by hitting this and then lastly you have this icon here with the lanes that's obviously the road lane assist so if you're on the motorway and you want to make sure that you don't sway into other lanes you just basically hit that it will turn orange and basically the whole steering wheel will start vibrating if it detects that you're swaying into different lanes without indicating so that is very dependent on the indicator signal so if you don't indicate and you're swaying lanes then it will warn you by shaking the steering wheel like that and wake you up again in case you're very tired and lastly you can also adjust the height of the steering wheel by this button here so you turn the knob to unlock it and then you can move the steering wheel up or down like so and then you just move it back into locked position and you're ready to go so that's about it guys i hope that was a very useful quick run through of the velar steering wheel if you have any other questions about his capabilities then do drop a comment below otherwise i'll be adding this video and all my other videos relating to my range rubber velar in its own playlist i'll have the link to the playlist in the description as well otherwise i hope you subscribe i've got tons more velar videos coming out in the future which i know you're gonna like until next time guys take care


It is now time for Member Statements, the Member from Perry, Salma, Spokane. Thank you, Mr. Speaker. I rise in the House today to recognize the local support being shown for the Almagwin Fish Improvement Association in Perry, Salma, Spokane. The AFIA is a community stewardship program that has been involved in conserving native pickerel populations in Lakes of Seabin, Omic Lake, for over 30 years. Their hatchery is run by volunteers and does not rely on any government funding. Yet the Ministry of Natural Resources and Forestry contests the AFIA's actions and is again attempting to shut down the operation. My office has received resolutions of support for the AFIA from three municipalities to date. Last week, I tabled on this House of Petition containing 263 signatures and as I speak, support continues to pour in. These individuals and municipalities are all calling for the Ministry of Natural Resources and Forestry to take action to support the AFIA and to reinstate the community-operated hatchery. They emphasize that the biological integrity of these lakes is key to the area's economic stability through tourism and that their viability ought to be preserved for future generations. They also highlight the benefits of the education program run by the AFIA for local schools. I support this local initiative and I applaud these communities' efforts. I call on the Minister and Ministry to issue the required permits to allow the AFIA to continue their stocking program. Thank you very much, Mr. Speaker. Thank you. Member of State, Mr. Member, from Parkdale High Park. Thank you, Mr. Speaker. I rise as a revered doctor with the United Church of Canada to wish Christians around the world and in this Chamber a very holy, holy week and, of course, to pray for those Christians who are under attack around the world, including in the Middle East, and clear up some misconceptions about what Christianity is not. It is not LGBTQ-phobic. In fact, Jesus talked about loving your neighbor no matter who your neighbor was, wanting for your neighbor what you want for yourself. Also, the very first Christian convert was somebody seen as sexually unclean to the powers that be of that day. Christianity is not anti-woman. In fact, women were the last to leave the cross in the very first to proclaim the resurrection and they even changed Jesus' mind about theology. Christianity is also not anti-science and it is not anti-sexuality. In fact, some of the most erotic poetry is in song of Solomon and God gave us the gift of reason for a reason, Mr. Speaker. So to all of those who around the world are celebrating holy week or going to walk with Jesus to the cross beyond and through the resurrection, I say have a very, very blessed Easter and Good Friday and, of course, Monday Thursday. Take care. Mr. Speaker, I rise to acknowledge our province's world-class engineers. Recently, I was asked by the professional engineers of Ontario, the PEO, to take part in their Take Your MPP to work day. I would like to thank Darlene Campbell and Hafiz Bashir, the government liaison chairs for putting the event together. The good work done by our diligent engineers largely takes place behind the scenes, but one major aspect of their work, safety, affects us all every day. I commend the PEO for their leadership and developing standards that prioritize the safety of Ontarians and, furthermore, I would like to recognize them for encouraging female participation in engineering. We still have a ways to go, but with their strong support and three of the last five presidents being women, including Annette Bergeron from my riding of Kingston and the Islands, the PEO has established positive, inspiring female role models for the engineers of tomorrow. Going to the front lines is a priority for me, so I was thrilled that my visit took me to Mabardier's state-of-the-art light rail transit design testing and manufacturing facility. Their 450-plus highly skilled employees are building rail transit for cities around the globe for delivery to South Africa, Brazil, Kuala Lumpur and Vancouver. Mr. Speaker, at a time when governments are focusing on environmental stewardship and fiscal responsibility, it is very exciting that rail transit optimized to these requirements is being produced right here in Ontario. Miigwech, merci. Thank you. Thank you. Thank you. Member Stevens. The Member from Chattanooga, Massachusetts. Thank you very much, Mr. Speaker. The two finalists for the Kraft Hockey Bill were announced during this past Saturday night's hockey night in Canada broadcast, and I'm very proud to say that my hometown of Chatham Kent will face off against North Sandwich, B.C. in the final showdown for Kraft Hockey Bill 2015. What an honor. Both finalists will receive $100,000 in arena upgrades, but the winner will host an NHL pre-season game. I can only hope it's between the Leafs and the Red Wins. If Chatham Kent wins, it'll be a victory for the entire community. It'll mean just a little more to a young, special person in the community, Chad Peterson. Chad has been an inspiration to us all. Chad has been the Chatham Maroons superfan. His love of hockey and life have inspired us all. For months, he's been driving around Chatham Kent in a Volkswagen Beetle with a Kraft Hockey Bill logo on the side. This contest means that much to him. Why? Well, Speaker Chad was born with fine motor skills disability, but he has refused to give up on his dream. And recently, he was quoted in the newspaper saying, we're going to have the best huge party at Memorial Arena. Oh, yeah, we'll be live on hockey night in Canada. That'll be totally amazing. We're going to rock Chatham Kent. So let's get behind Chad and the organizers who made this possible. We've come this far. Now let's bring Hockey Bill to Chatham Kent. So go to www.khv2015.ca to vote for Chatham Kent today. Deadline is tonight. So vote now and vote often. And if we win, I personally invite everyone to the biggest party on April the 4th at the Chatham Memorial Arena. Thank you, Speaker. Far be it from me to interrupt the rant. Thank you, Mr. Speaker. And I'm proud to stand in this house and represent the people of Oshawa. And today I'd like to say that General Motors has been building cars in Oshawa for over a century. But in spite of our strong history, the future remains uncertain. This morning, Unifor released an independent study on the significance of General Motors to my community in Oshawa and the impact the province would feel in the event of a closure. It was not a surprise to hear that the result would be devastating. According to the report, Ontario would experience a loss of over 30,000 jobs and our GDP would decline by more than $5 billion. And as the government scrambles to sell our public assets to pay for election promises, another $1 billion would disappear from their revenue stream. Speaker, the Liberal government cannot continue to sit on its hands and wait. Ontario's automotive industry boasts state-of-the-art technology and innovation and a skilled workforce that is rivaled by none. But it is the government's job to make sure these advantages are not overlooked. When the industry is considering where they want to build a new plant, we need to put ourselves in the best possible position to secure that investment. In my writing, I've heard from auto workers concerned that their jobs are at risk, pensioners worried about their retirement security, and small business owners afraid for the ripple effects in our local economy. I ask that the government take these concerns seriously and adopt a comprehensive automotive strategy to help to put my community in Oshawa and others across Ontario at ease. Thank you. Thank you. Mr. Speaker, I would like to talk about a great event. I went to in my writing of Ottawa Orleans last week. The event was one to celebrate the 25th anniversary of the plein air ensemble. Twenty-five years ago, three artist brands, Pierre-Ethe Le Beauet, Charles Pratt, and Andrew Lyle organized the first painting trip to teach students outdoor painting. Nobody would have guessed at that point that this small group would grow constituently. The group's aim is to capture the beauty of the landscape while fostering the friendships among artists. Today, the group has about 75 members, which about to 15 to 20 were taking part in each trip event. Most of the artists come from the Ottawa Gannos region. Each year, they plan a spring and fall trip to different destinations. During this exhibition in Orleans, 21 of the plein air ensemble members showed works from different trips. The show highlighted the wonderful talent and diversity of this group of artists. I saw many fine artworks in oil, acrylic, watercolors, and pastel. I would like to recognize the event's organizers, Kirsten Peters and Elaine Martin, for their outstanding work on the event and many more to come. Thank you, Mr. Speaker. Mr. Speaker, I am pleased to rise to report the results of my recent newsletter survey. I want to thank the hundreds of people who took the time to respond and share their concerns. Mr. Speaker, one of the biggest concerns continues to be the proposal to locate a landfill on fractured bedrock near the Thames River, which would put our drinking water at risk. One of the other major concerns is wind turbines. People are concerned about the impacts of their health, their community, and the safety at nearby airports. 93% of people who responded said municipalities should have a say in where the wind turbines are located. Mr. Speaker, when I read the responses, I'm always struck by the impact of this government's policies and how difficult they are making it for people to make ends meet. 49% of the respondents said that their hydro bills had increased by 20 to 50% over the last 10 years, and 30% said their hydro bills had increased by more than 50%. People are doing everything they can to keep costs down, but the increases are staggering. And this government is now proposing to charge them for a pension plan. It's not that they don't want more retirement income. It's that they can afford this government's proposal. 78% of residents said they can't afford to pay 1.9% of their income into the proposed pension program. These are the numbers government needs to consider before they push ahead. Again, I want to thank everyone who took time to respond so I can continue to raise their concerns here in the legislature. Thank you very much. Thank you. Members, David, Mr. Member from Kitchener Centre. Thank you, Mr. Speaker. Recently I had the opportunity to drop in on Waterloo Region's Community Legal Services. This is a non-profit agency under Legal Aid Ontario. Executive Director Shannon Down told me that her mandate is to provide access to legal services for people in groups facing financial barriers when trying to seek legal counsel. In my riding of Kitchener Centre, I often meet with constituents who have benefited from the legal clinic with issues such as social assistance and disability appeals, landlord and tenant board cases, and workplace safety and insurance claims. The clinic is especially important to new Canadians who may not have a full grasp of our official languages. They're often vulnerable and are lacking understanding of our legal system. They don't always know their rights. As part of our government's commitment to promoting fairness and accessibility in the justice system, regardless of their income, we dedicated an additional $30 million in our 2014 budget to Legal Aid Ontario. The result of this investment has meant greater capacity for the clinic to meet with the demand that they face. After more than 25 years, our Community Legal Clinic continues to provide vital access to the legal process for those who might otherwise be underserved or excluded. Mr. Speaker, I'd like to take this opportunity to thank the dedicated service providers of legal clinics across Ontario who fulfill this very important mission every day. Thank you. Thank you for your statements to the member from Brenton Springdale. Thank you Mr. Speaker. Mr. Speaker, this Friday I have the pleasure of attending the William Osler Health Systems Foundation's second annual holy gala fundraiser. This spectacular community event took place to celebrate holy, which is traditionally celebrated by members of the Hindu faith. The festival is known as the Festival of Colours and the Festival of Love. And as such, the festival has grown to become popular amongst Indians and Canadians of all faiths and backgrounds. Mr. Speaker, on this evening at the Grand Empire Convention Centre, there is a number of colours over 700 guests, including members of all three levels of government, to partake in an evening full of fun, food and dance. There is performances by magicians, dance teams, world-renowned singers, Nindikour and Manj Music, as well as Acting Sensation Benevariani for money. Mr. Speaker, through sponsorships, donations, auctions and raffles, the organisers were able to raise a remarkable $150,000 redevelopment initiatives at all three Osler locations, as well as equipment needs at the Brenton Civic Hospital, which is in my writing. As a direct result of the proceeds from this event, members of our community will have greater access to services than the needs they require in their hospitals, healthcare facilities. Mr. Speaker, I would like to take this opportunity to thank all of the organisers, volunteers, board members, doctors, nurses and all the staff, as well as William Osler's President and CEO, Matt Anderson, for all the work they continue to do for our community. Thank you. Thank you. I thank all members for their statements. It is now time


Thank you for this honor, and I'm very happy to now consider myself a part of the Suez family. Also, I love this green color. Thank you, Professor Banda. I'm very moved by those wards to continue to set the world a light. Perhaps because so much in the world today seems so dim and so desperately in need of light. And congratulations to you graduating students. One of the things I was most looking forward to was to have the opportunity to sit there and check out your shoes. You're very fortunate to have studied here at Suez. This wonderfully multifaceted place that is steeped in diversity where difference is normal. This place where you can study so many different non-European and European languages where different people from different parts of the world converge to then and to question and to grow. You now have the knowledge to enable you to set the world a light. And so however you want to go about doing that, do not ever let anybody tell you that you should not try to change something because that is the way it has always been. Every political, economic and social structure we have in the world today was created by people and can be recreated by people. I knew very early on in my life that I did not want the things I was supposed to want. And I felt lonely in this knowledge because I felt that I was the only one who felt this way. I now know that many other people in the world do not want the things that they're supposed to want. I did not want to become a doctor. I did not want to aspire to domesticity. I did not want to reduce myself. Instead I wanted to tell stories. I wanted to ask questions. I was very alert to the ways that our cultural mindsets so easily uphold different forms of injustice. I wanted to change a small slice of food. I knew very early on also that I might not succeed, but I wanted to try. I was determined to try. I don't know why I write fiction. What I do know is that I have to write fiction. It is how I make sense of the world. It is what gives me joy. To write fiction is to embark on a long walk, knowing that you will trip and fall many times, but still very keen to take the walk. In writing my novels I would often get stuck. I would know intuitively that something was not right, but I would not know how to make it right. And in such situations I would take to my bed and eat a lot of chocolate. But even in the middle of the chocolate binging, I knew that at some point I would get up and try again. And it seems to me that this is not a bad way to look at the rest of your life. You will trip many times. It's part of the journey. Don't be surprised when you fall. Maybe even lounge in the dirt a little.  Always get up. Thank you.


Welcome to Quest for a Meaningful Life on the Road here in Quebec City where I'll be spending the winter trying out this whole work from anywhere experience now that the lockdown of so much of organic real life has led to this opening up of working online. This idea of doing business through a screen and in fact doing almost everything through a screen and this has led me to think about what it means to have community. Now hopefully we all have some friends and family and it's important to have some people around us but what about having a larger community they don't always have to be they don't all have to be people that we are friends with even people that we like even but it seems like there is value in having some kind of a community having people around us other than some kind of anonymous collection of people that we have no interaction with. Now of course growing up in a city I'm used to being anonymous ever since there are big cities of thousands millions of people certainly that can't really be a true community because you can't actually know any of them or really even interact with thousands and thousands of people so we're used to this kind of anonymous feeling living in a big city but now it's become even more so as the world's become even more urbanized and the cities are getting bigger more people living in the cities and beyond that this kind of global city of the internet where we've all been gradually moving more and more into it does feel like being part of one giant city that spans the world and we we've been moving more and more of our lives into this this world where it leaves me to wonder what's left outside this world of the internet the world of actual humans face-to-face having some kind of interaction in some kind of physical space because of the concerns one might say panic about health risks we now no longer have very much interaction person to person in the physical world and leaves me to wonder what can or how can we have a community if we can't have it in the physical world if where we're not really having physical interactions then we have to do it through this online imaginary screen world and that leaves me to wonder how it can even be done so when I when I look back at history and the way that communities once were there would simply be people around you if you had your your village your your part of the world there would be people living there and you would to some degree know them and this certainly has both advantages and disadvantages as anybody living in a small town can attest that it's not all positive to have this community you also have people that are in your business all the time and people that have a lot of very strong opinions about what you should and shouldn't be doing and they're there in your face whereas the the city and the mega city of the internet even more so allowing us to be anonymous one of the best descriptions I've heard of it is that or the one of the best positive things about it is that people will just leave you alone to do what you choose to do and know the the downside of that is that everybody's leaving you alone so actually nobody actually cares what you're doing but the upside is that you do have that openness and freedom to do what you choose whereas in traditional community it seems like you're always answering to other people and there's they're always a presence but still as much as it's good to be free and undisturbed it seems like we can't really have a complete meaningful life without having some kind of community and in the mega city internet world we don't have any automatic community we can find people through that maybe they have a shared interest somehow but with the interaction being through a screen it leaves me to wonder how can we make actual community how can we have a community in this new internet mega city landscape and so I would like to hear some ideas of how you find community is it just the community that you had you know outside the internet from your family maybe school friend group that becomes your community and it simply moves online or do you have ways that you develop a true feeling of community out of the online world so I'd be curious to hear how you're doing this


Okay, as some of you may know already, it's been seven years since the beginning of the Debian Woman project, and Mike Rahesha will be talking to you about it. Thank you. Right. So, yeah, as the introduction said, the Debian Woman project has by now achieved quite a biblical age. We are now actually at this step in celebrating our seventh birthday, a fact that most of us, when we realized it, made us feel very mixed. We felt happy that we're still around and we're still growing.  And of course, there's also a good moment to look back and look at the project, see how the project has developed, how Debian as a whole has developed with respect to the Debian Woman project. And basically, I just do a short review. So first of all, who am I? Well, as mentioned already, my name is Mike Rahesha, some of you might have seen me before, heard me talk before. I've been a Debian user for quite a while now. I joined the Debian project quite shortly after its foundation in 2004. I got there in 2005. I really went the usual way. I used Debian. I liked it. I thought maybe I could do more, join in somehow, become a part of it. I didn't know where to go. I turned to the Debian women. They were really friendly. They welcomed me. They showed me the ropes. After a couple of years, I thought, okay, I should apply for a full Debian developer status. I did and have been ever since. Right. So much for me now. Let's talk about the Debian women project. Seven years ago at Debcon 4, 2004, a couple of ladies who you can see here sat together and got thinking. They noticed that there's a surprisingly low number of women in Debian. And they thought that maybe this is something that should be changed for the sake of Debian. And then they got together and they pondered how to do this. And they thought the best thing would be to really have a Debian subproject that took care of that. They consisted of men and women who thought that the number of women should be raised and basically offer a first contact point and a way to contract all the actions that can be done to achieve this. So they got, actually, this is really, really light. So they got working. And what they did was basically the first thing, they set up a website and they explained what the Debian women project is about, what they do, what they don't do. And very quickly, we learned that more importantly than having to explain what Debian women does, which is quite obvious, is to explain what Debian women does not do and more specifically what it doesn't want. So what we do want is more women in Debian, more female contributors, more translators, more developers, more maintainers and so on and so on. And we don't want this for the abstract reason that there should be more women everywhere because women are a great thing to have. And so they should be equally represented in every given group of people. It's because we think that it benefits Debian as a project, as an operating system and as a community. And in order to achieve this, we set up a whole lot of communication channels. There's IRC, there's the mailing list. We had a wiki of our own, which is by now moved into the Debian wiki. We've got the mentoring program that offers the possibility to get into package maintainership.  And really what we had to do most of the time, especially when giving talks about the Debian women project, was answering questions. And those questions were often rather worried because people asked, well, you know, those Debian women, are they not just some kind of mailing list police, really?  And of course, that is not what the Debian women project is about. What we are about is making the Debian community an inclusive one and a welcoming one. If that means flaming people to a crisp, we will do it. But it's not the main purpose of the Debian women project. Also, we do not want to create a Debian fork for women. This is something that's always coming up. There's always people asking, you know, why do you have a sub-project? Why do we have a mailing list of your own? Why did you have a wiki of your own? Why do we have an IRC channel of your own?  Do you want to make some women Debian? You know, like, I don't know, pink default colors or I don't know. And of course, that's not what we want. It's never what we wanted. Another thing is that when you stand on a stage and say, I want more women in Debian, there's always people who say, well, what's the point? What's the benefit of having more women in Debian? Do you just want it because there should be more women everywhere? And if that's the point, are we going to get a quota next year? Or are we going to make, I don't know, the new queue, give us few bonus points to female uploaders? You know, like, one copyright goes free or something. It's a silly thing to say, and I feel silly saying it.  So you found this funny little sub-project that basically tries to bully men into giving you a leeway. So we don't. Really, we don't. And then there are those who approach you after a talk and they say, you know what Debian women is great ever since I've been working with the Debian project. I felt that the Debian developers, they're harsh, they're rude, they're technical, they're really, really aggressive. It's good to have some women in there. You know, finally, I have some friendly people to talk to.  And so this is not why you want women in Debian. We don't think that Debian as a whole is unfriendly, so if we add some women, they can be like the friendly front desk towards the world. It's a woman can be an equally unfriendly developer if she wants to, she has this right. Nobody should, of course, but it's not something that was the motivation for us when we thought that the Debian project would benefit from more women. Also, it's not like the Debian women is this kind of project kindergarten where everybody who's unhappy with the project or feels mistreated or treated unjust in some way can go and then we all huddle together and make a comfort hug and I don't know what. The Debian women project, just as any other sub-project of Debian does focus on technical excellence, we do want to communicate knowledge and we want people to use that knowledge and if they don't do that, we're just as unhappy with it as anybody else. And the most of all, as you may notice if you look around in this audience while we are called Debian women, we are by no means a women-only project. In fact, wherever you look, if you look at the mailing list, if you look in the IRC channel, actually the majority of the Debian women are men. So then that's actually a thing that we are really proud of because it shows that the Debian women project is not a bunch of disgruntled women who say, I know we should really have more representation and the project is also a whole bunch of disgruntled men who say the project is somewhat lacking with respect to diversity and maybe we should do something about it, not because somebody makes us but because we think it's the right thing to do. So this is what we set out to do and this is what we did and we've been doing this for seven years which is a horribly long time. And by now the Debian women project has somewhat slowed down. If you look on the mailing list, it's not as much traffic as we used to have. The channel is still really active but more on a social level really. So things have gotten quiet around the Debian women project. Also, this is actually the first talk about the Debian women project itself in five years. So we've had them at the early Debcons in 2004 and five and then everybody knew the project so we didn't feel there was a need to explain once more what we do and who we are. And yeah, over the time there's a feeling that maybe we have outlived our purpose. Maybe we are there, you know. Debian is now a nice and friendly place. There are women everywhere. Like if you look into the respective teams, it's quite likely that you also find a few female members. We are now much nicer. We are even seriously discussing giving ourselves a code of conduct which could not in any way have happened five years ago. This is actually a place I got to think that when I talked to Bida recently, where people are happy to bring their daughters, which is I think the best sign for a project is being really friendly and welcoming. So this is what we feel and this is what we perceive and of course we want to look at some numbers and see if these feelings and perceptions are correct. What you see here is a diagram that shows first uploads by women. So basically this is a diagram over time. We are beginning in 19, this is horribly tiny, but this is 1997 here and then it goes all the way on to today. And basically every time a woman uploads a package, she was never done so before, so every time there's a new female uploader, line goes up. And it's quite nice to see if you look in the colored area, this is the foundation of the Debian Women Project and you can see that the line does rise quite steeply. So obviously there was an effect. There's quite a lot of women who decided that maybe they could use the new skills they got among the Debian Women hopefully to bring them to life, put the package in the archive, maybe two. So this is actually quite nice to see. So yes, things did get better. Now let's look at some other numbers. Let's look at the Debian developers. They're always an easy measure because they can be counted. There's a database, everybody's in there, so it's really easy to just go there and count them. And I remember when I did this talk the first time, which was in 2005, we had something like 0.5% that was really, really low. And now I counted again and we had an increase of 325%, which is awesome until you make the math and you realize that's 13 people. So we have now by today 13 female developers instead of four. That's not a whole lot really. If you want to have some visualization, this is 13 in 927, which is how many developers we have today. So I am tempted to say there's room for improvement. Again, just to make this fact really reach you, these is 927 people. 13 of them are wearing a rat t-shirt. So if we had a Debian group photo tomorrow and all the women got the rat t-shirt, this is what it would look like. So please realize it is a small number. Okay, now why is that? If the number of female uploaders is rising and rising and rising, how come the number of female DDs isn't rising? And there's actually quite an interesting thing to say. Again, this is an excess over time. This time we're beginning at the very birth of the project in 1994. And then we've got women joining one by one. Here's the first and the second and the third, Samaria and Petra and Helen and so on. Again, the colored area is the foundation of Debian women. And again, you see really a steep increase in numbers, which is really, really uplifting. And then in 2008, something happens right here, it stops. It actually falls for the first time because we have the first ladies going missing in action or resigning from the project and no one comes after them. So we've got one joining here that's actually just Ronda setting her agenda to female in that case because of that showing up in the database. And apart from that, we haven't had anybody apply for Debian developer status in three years. Luckily, this spell has now be broken by Francesca. So yeah, we had this really, really long dry patch that lasted until May this year when Francesca got her DVD status. So now we are back to 13, which was our all-time high, but it's not rising anymore. So there's an obvious question as to why this is. Yeah, this is a complete status to the said. There are some possible explanations. One explanation is that with all the support maybe of Debian women, also of the greater, now more friendly Debian community, women now find it easy to step into the community, learn how to do a package, find a sponsor or a mentor or something and upload packages into the archive. That's a good thing. However, something keeps them from applying for DD status and that's something that personally puzzles me a lot because I was quite happy to apply for my status and I'm loving it. So one explanation for this could be that they still perceive this as a barrier. Somehow they feel maybe it's too hard, maybe the questions in the new maintainer process are too hard or maybe they feel that if they become DDs, they will be exposed in a way that they don't feel comfortable with or maybe they don't want to become so public about the Debian involvement or whatnot. I really don't know. And this is why right now I'm asking you, if there are any ladies in the audience who have a package in the archive, but are not DDs, would it be okay to tell us why you haven't applied for a DD status yet or? Laziness, okay. There we've got one. Anything else, maybe? No, okay. You're scared? Scared, lazy? Scared? Just lazy? Yeah, I can repeat this or we can hand out the mic. Well, I really don't have any explanation for that just because I never thought, I never came to a situation where I'd like to do something that I couldn't do without being a DD. All right. And I've been involved in Debian for many years, but I really never said, okay, I'm going to be a DD and I'm going to apply. Just, well, it's also personal question issues that I didn't have the time to... Oh, you did, it's okay, I just... It's not, I don't see any really big problem and... Okay, so in short, you didn't see a need to become a DD? Yes. Okay, there's another one over to your right. Well, I think today that I need more packages. I only have one. Oh, one package is enough. I was actually waiting for Debian Conf to meet some people so that someone can advocate for me. Okay, so actually we have quite a nice mixture of reasons. We have like some people who say, well, really, I just didn't get around to it. As Sam said, I'm a bit scared. There's another, yeah, very much not. Okay. I just wanted to point out that having, I mean, the interest in caring about packages is not the only way, the only contribution that qualifies to become a Debian developer. So every kind of contribution they are giving to Debian, if you're willing to do that on a, you know, on a sustained basis, if you feel committed to a project, then you have no excuse. There goes my conclusion. Well, thank you, dear leader. All right, now, back to the point. Yeah, so we have people who didn't get around to it. We have people who felt a bit scared about the whole process. We've had people who simply didn't feel the need and some who were really just waiting for the opportunity to get the whole thing moving. So this is basically the second explanation that I found as well. People actually do find it easy or manageable to become DDs, but they don't see why they should. Because, yeah, what are the benefits of being a Debian developer?   Now what, I thought about this myself, because really in my everyday life it's not often that I realize or come to think, wow, thank God, I'm a Debian developer. I couldn't have done this particular thing if I wasn't. But if you sit down and think about it, a Debian developer status of any kind is a lot like a citizenship in a country that you live in. Now, if you live in a country and you do not have citizenship, you can find a job, you can buy a house, have a family, et cetera, et cetera. You can live a happy life in this country. But if this country at any point in time decides to go into a direction that you don't like, there's nothing you can do about it. You are not in the position to make any change or to make any effect on that country. You just live there, but there's no way that you can exercise influence on the people who run this country. And it's really exactly the same thing with Debian. I mean, there's this kind of like government-like structure of all the DDs sitting in this huge virtual plenum.  Now, I don't think we'll do this any time soon, but still, maybe if you think about this and if you compare the DD status to a citizenship, to the right to vote, to propose votes, to become leader one day or something, maybe this might be a reason for you to also invest this work and become a Debian developer. Because otherwise, what we will get is an operating system that, let's say, half of the users are male and half of the users are female, but it's run by a kind of proxy, like the guys who run it, there's the guys who run it, and then there's the people who use it. And we actually have this to a degree. There's an anecdote, yes, that I can't tell. So, a couple of months ago, I was using a program that is really, really exclusive for women. Let's say it's a program that lets you keep track of your lady days, okay? And I discovered a bug, so I went to the BTS to file it and I noticed that all the other bugs are filed by men. And I was somehow surprised about that, and then I thought, let's do research. I know there's another one of these programs. Let's check that one. And also, all the bugs of the other program were filed by men. Now, I don't doubt that the users of these programs are by large women, but if they have a bug to file, apparently they have a man do it. This is not what we want. We don't want a huge number of female users having to communicate with the project via mail, bug filing proxies, and package proxies, and sponsor proxies, and voting proxies. We want them to show up and to work in the project themselves. I can see people checking right now when the BTS going, really? So, yeah, there's a few questions that we should ask among ourselves, and that we should also discuss in the buff that is to follow, and that is how we can solve or how we can improve the current situation that we have. So first of all, we want to find out what keeps women from applying for the DD status. We've had a few examples here, and I think this is really a quite good cross-section of the different reasons that you can have. So maybe we should get some more numbers, identify some main reasons, and then try to mitigate them in some way. Also, obviously, the benefits of being a Debian developer are not yet obvious enough. There are some more benefits. Like you can read the Linux weekly news for free. There's lots and lots of honor and fame connected to it. But maybe that's just not so attractive to everybody. So we should, as a project, sit down and think about the Debian developer status and ask ourselves, is it really important that people do become developers? Do we want them to? In that case, how can we make them? One way is, as Stefano mentioned, that it's really silly to say that you can only be a developer or a voting member of the project. If you maintain packages, there's people who invest a lot and a lot of work, but just not into packages. So we already tackled that. But maybe we should just also, once more, make clear why it's so important to become a DD, and why you can't just say, well, let the Debian people do what they want.  Because Debian is more than that. And you don't switch Debian, really. Also, I think, within the Debian project, we should sit down and very clearly redefine our main tasks. Like, when Debian was founded, it was a time that I called the Wild West days. Because really, then, what you did as a Debian woman was quite clear. You had a really clearly defined, I'm almost tempted to say, enemy.  I will find you. I will let you know what I think of you. You got death threats. You got silly graphics.  You had stuff on the mailing list where you thought, ah, Debian project, you are embarrassing yourself. And it was really, really clear what our task was then. And today, the situation is much more complex. The silly people have moved on. I don't know where they are now, but they are not harassing the Debian women anymore. So yeah, I don't know where they went, but they don't show up on the mailing list quite so often anymore. Also, the mailing lists, our mailing lists have gotten a lot more nice and peaceful, so we don't need to do the mailing list police anymore and tell people not to do this and to remove the porn pictures and so on and so on. So while these tasks have disappeared, we still have other things to do, but these are more complex. They're not as easy. They're not as black and white. It's not us against the sexists anymore. So we should sit down and redefine our purpose and redefine our tasks and discuss what we want to do, what we want to work on. So just to prevent the Debian women project from somehow dwindling into inactivity and basically just being this yet another group of people who hang out a lot and talk and just not do anything in particular. So this is why I'm saying the same thing as the talk before me. Do come to the Buff on Thursday at 10. Yeah, really, I'm really, really asking all of you to come and join us in this discussion because this is a decision that we should make together. It's also why I'm not giving you a slide saying, this is what the Debian women project should do and this is what we want and this is what we don't want because I'm only speaking for myself and I really want this to be a common decision among all the members and contributors and so on of the Debian women project. So while this talk has been looking into the past and at the present, I hope that we'll then be able to look into the future together on Thursday morning and we can begin with this now. We have 15 minutes for questions. I can do this 15 minutes. All right, I'll use the microphone. I saw your graph, it's kind of depressing to see a graph like that with like actual names every time there's a little tick. Well, it's only 13 people. That's not that much work. It just brings it home really but the other thing about it is you say, I mean, maybe I missed that part about apparently there are lots more female DMs. Have you plotted that on the same graph and can you see the relationship between them? I can, we can compare the, I can give you a comparison of the numbers. This is the graph that I used first. So we now have since the birth of the project or since Marga started taking the numbers because all the numbers are Marga's work. So thanks a lot to Marga who's watching us now. There's a page called Debian women statistics on the wiki and all the numbers here are taken from there and she's been the one who's painstakingly researched them. Anyway, the maximum number that we have here is 41. So by now we've got, we had 41 different women who uploaded a package into the Debian archive at some point in time. And you can compare this to the top number of female DDs being 13 ever. Right, but that obviously includes people who uploaded a package a long time ago and then went away. Yes, exactly. Is it's, we don't have that many, we have, we don't have many numbers to work with. Unfortunately also, I'm not entirely sure if it couldn't be possible that women just changed their address at some point and had another uploading address. Also the 41 includes of course the Debian developers. So I guess you can maybe, look if you, if I had to bet I'd say it's probably more or less something like 30 really different women who did upload at some point and decided not to become Debian developers. Why don't sponsors or mentors suggest someone?  Don't you want to apply? Is there no such thing going on that sponsors or mentors suggest to their minions or whatever you call them to apply? That's actually a good point. Let's ask the people in here who have sponsored packages. Do you encourage your sponsors to become DDs and stop bothering you? Yes, yes. Yeah, yeah. Thereby hangs a possible problem as well if a sponsor is maybe somehow less likely to suggest to a female sponsor, I don't know. I don't know whether you would be able to tell. I think mostly women or everybody really tries to approach a sponsor who they know feels friendly towards them. So I guess if there was a DD who had a latent tendency to not invite women into the project, he would not be the one who was contacted by women about package sponsoring. I mean, usually this goes via the mentors mailing list and I would certainly hope they're not hanging out there. One thing about what advantages gives Debian being like a DD, I was thinking that it's sad and it's wrong, but I think a lot of actually male have somehow badly integrated that women might be less good at technical stuff. And I think that's untrue. But still, it's more or less integrated. And I was thinking, when you're a DD, you get a dbm.org male address and that writing with this address gives some kind of certification that you are technically able to do a lot of different stuff. And I think I would like encourage women to actually get such an address because that might help to overcome this kind of stupid integrated ideas of a few male that you have to interact with when you're doing free software. Not entirely sure if I got your question. Sorry. Let's take it as a remark maybe. I think we lost the audience, Mike. It's back. Yeah, there was some problems a while back with abuse of women involved in Debian. There was some really nasty stuff going on. I'm hoping, please, if you can confirm that there haven't been any more incidents like that recently. Well, things did get a lot better to give a number when I sent out the announcement about the Debian women IRC tutorials.  However, the trolls did get more courageous. This one gave a real name and everything. So they are now past the nicknames. But it was only one. So this is a lot better than it was in the past.  Yeah. And they're also doing this on private now. They're not sending it to public made lists anymore. So yeah. So I wonder if you have some comparison with other free software projects? Because for instance, I remember one of the very early work on how many women there are in free software, they were rightly comparing with how many women there are in computer science. Because it's already low there and the software was even lower. So I wonder if you have any idea or maybe you have thought about comparing, I don't know, with GNOME or with other community projects to see how good or how bad Debian is scoring with respect to that. I'm afraid the only hard numbers I have from the Floss Pulse project, but that's also already five years in the past by now. Maybe one thing that can serve as a bit of a comparison was that after the foundation of Debian Women, a whole lot of free software projects founded their respective dash women project. There was KDE women, I think GNOME women, Fedora women and possibly, I don't know, for sure, Ubuntu women, which is very active, that I know. It might be worthy to look at all these projects and see where they went and see what became of them, but I guess it's really hard because often they only like the Debian Women project, only work inside the project and they don't really have that much outside visibility. I've got it. I think Gaudens was waiting for a while. I was, you didn't say anything about the mentoring project. I was wondering if you know what's going on there because the two mentors I had so far, they very quickly disappeared again and they had no contact at all with them. If that's a general experience mentors have or if there are some success stories that just didn't go to me. I don't know of any numbers myself. I can say that the mentoring program is still running. We still have girls or women occasionally inquiring about it. As far as I know, each one has been assigned a mentor. There's no real lack of mentors, I think, at the moment, but people on IRC correct me if I'm wrong because I'm not actually that much involved in the mentoring project currently. I don't know, is anybody here a Debian women mentee or mentor? Well, I'm a mentor and I can only agree with you. I get one time a mentee, exchange two males and then never heard of her again. And I really assure you it was not by the style of my males. Okay, so do we have success stories maybe? Was anyone here a Debian women mentee? Unliked it? Okay, I'll take this as a pointer towards reviewing the mentoring program, maybe. I've got a comment on the previous question about numbers in different projects. In Apechi, we've got like 3,000 committers and the percentage of women is about two. Who's we? Apechi. Ah, okay. Sorry. So can you say that again? So it's like 3,000 commits and? 3,000 committers and 2% of them are women. 2%, that's actually quite good. It's more than, wait, a bit. Yeah, I think it's optimistic 2%. Yeah, okay. I want to ask a question about the mentor program.  I mean, if I make a package, what does the mentor does for us? Well, basically, a mentor is somebody who will show, who you will turn to when you have questions towards packaging or towards the project itself or about the new maintainer process and all that. You can, if you want, your mentor can also be your sponsor. So you can give him or her your packages and then here she will upload them, check them first and then upload them if they are okay. This doesn't have to be, though. It's just as well that you just find a sponsor on the Debian Mentors mailing list or something and really just have your mentor as a, say, a personal friend or something who you can turn to, like, if you get the root remark or if there's something that confuses you or if there's any type of question that you don't feel comfortable asking on a public mailing list. There's basically the idea behind a mentor is that there's somebody who you can ask everything. So if you want your mentor to also be your sponsor to show you how to package stuff and so on and so on, here she can do that, but not necessarily. You can also find your own way into the project and really just have this mentor for questions or to have somebody who you know you can trust and ask private things too. But later on, if I apply for a DD, I can count on him, her to be my advocate or something like that. Can you repeat that? When you are a DD? When I apply for a new maintainer process, I can count on the mentor to advocate for me. I should hope so. Yes, well, of course, if your mentor feels that maybe the amount of knowledge that you collected is not yet enough, he will not advocate you, but I should think that he or she will tell you before.  But it's not a guarantee, but I'd say, yes, usually, of course, your mentor who knows what you can do and who knows what you've learned will also advocate you. Okay, so regarding the earlier question about people not applying to be DDs, maybe the perspective of a sponsory would help a bit. So, I've been involved in DBN I think for about 10 years now, or I think 11 years ago, I decided the first time, oh, I really need to be a DD. And every time I thought I really need to do that, I had some time constraints or whatever. And by now, I don't really need to do that. I don't really need to be the DD. You said earlier, yeah, if my country goes in the wrong direction, I can participate. But if it comes to that, and I really think I need to save the DBN project single-handedly, then I will apply to be a DD. And what we heard earlier, having a addebian.org email address, I think it's, some people feel better or more official in doing what they're doing in the free software community with that kind of address and with showing their project affiliation. Yeah. But for myself and some other people I know, they can live without it and they can live without the official status being a DD. So I think some of what you're seeing might be related to that. Okay. I think we... Not only regarding women. Can take, I think there was one more question right here and then I'm afraid we'll have to move the rest to Thursday. So the statistics that you have shown, they were mostly quantitative, but have there been any research in qualitative direction? That means what kind of areas are usually inclined to have women sort of a sign up and upload and participate in? Well, the short answer is no. Really the only numbers we do have is what we get from the database and so on. We also for example have no numbers at all on translators. We do very much suspect that the number of women in the translators community is much, much bigger than in the developers community because everybody knows a few women who do translating, but they are organized in lots and lots of groups and mailing lists and there's no easy way to assess them. So we know from experience that there are fields like translations, documentation, artwork and things like that that are by tendons more attractive to women or where you find more women, let's put it that way, maybe they're not really more attractive, they're just easier to get into or I don't know, but we don't have any hard numbers on that. Okay, I'm actually happy to see that. There's quite a lot of room for discussion. I hope I'll see you all again Thursday morning. It's 10, it's really not that early. And I would be very happy if you all came, if we could continue this discussion and maybe do this in a way that has us end up with a few nice results to present in the end. For now, I thank you for your honest answers, for your interested questions for being here and yeah, thank you.


This video is brought to you by my patrons, a special thanks to God of Grants, Kishu, Kyle, MyKing, Shayla and TicBiscuit. Thank you so much for your support. If you also like to support the work I do, you can join us at Patreon. The links will be in the description. This is the second video of the health bars in Godot Engine mini series. If you didn't watch the first yet, please pause and watch. The link will be in the description and if you are on YouTube, it will also be in the card at the top right. In this video, we will see how to implement the health bar node and the health bar using three different approaches. As a simple hood element, as a 2D actor element, and as a 3D actor element. So this is the most common setup for a game in Godot Engine. We have the topmost game node, which is basically what will manage all the high level logic. Then we have two layers. One for the game world, which I call level layer. And then another one for the interface. And this is the one that we will use to add our health bar. So I reorganize our project here. So now we have the interface folder and the health bar is inside of it. And I will instantiate it as a child of the interface. And I will move it right about here. Let me turn on the helpers again. I'll move it right about here. And I have a setup for a very simple game. This will be available in the link in the description, I'll put everything there. If we play it now, nothing happens, right? So the character will take damage, it will soon disappear, it will die. And the health bar isn't hooked to the layer yet. And here we have our first problem. In this scenario, how we will connect the health bar, which is in this hierarchy, to the player's health that is inside the test level, then inside the player. And here we have our health. How we will connect this to this. So since Godot Engine uses a composition design pattern, in this kind of design we try to get the most common ancestor between two entities of this context. So the common ancestor between the health bar and the health would be the game, the game node, because since the player is inside the test level and the test level is inside the layer level and the layer level is inside the game, the game will be the most common ancestor between all of these hierarchies. So here is where we will attach a new script. So let's attach a new script to the game and we'll quite simply just connect the health signals to the health bar methods, just like we did in the previous video. But now we'll use code because this way will be less spaghettified, let's say this way. So I will, inside the ready method, the ready callback, we'll try to find our player health that will be inside the level layer, test level, player health, this is what we want. And we will also want to find the health bar. So let's store a reference to it, it's inside the interface layer, interface health bar, health bar dot connect changed to help, let me just rename this. Let's connect this signal to the health bar, and then to the set value method. And let's also do the same for the set maximum or maximum change to the health bar. Set max method. So between the two videos, if you remember well, the initialized method in the previous video was a private method. But now I made it public so other notes can initialize this health. So when we initialize it will emit the two signals. So we start syncing it with whatever is connected to. So let's call the initialize method, player dot initialize, save it. And if we test this, if you move to the spike, the spike will deal some damage to the player. And you can see that the player's health is already connected to the health bar. So we already did what we wanted. Now to hook the health bar to a 2D actor, so a in-game actor, we can pretty much do the same thing. So let me show you what I mean by that. I will open this enemy scene, open, and the enemy scene is composed by this health node, which we saw in the previous video. And then this kinematic body, which will move the physical body of this enemy. And then right at the sprite, we have the health bar. So what I did was pretty much the same thing as we did in the game, the game script. So in the enemy script, we have reference to the health, to the health bar. And at the ready method, we will connect the health changed to the health bar set value, the health max changed to the health bar set max. And then we will initialize the health. Another thing that I did is that when the character takes some damage, so when a body entered in the hurt box area, it will show up the health bar and start a height timer. So when this height timer times out, it will hide the bar again. And if the health is depleted, it will kill free the enemy scene. And you can see that the basic logic of hooking the health to the health bar is pretty much the same. So let's test this out. I will go to the game scene and add an enemy as a child of the test level. I'll move it here and I will hide the health bar by default. And if we test this, it will take some damage. The health bar will appear and disappear after some time. And when the health is depleted, the character will disappear just as we wanted. So as you can see with a 2D element, it's pretty simple. It's very straightforward to connect the health to the health bar. But now let's see how we can do that in 3D. So this is the basic 3D scene that I've set up for this test. And we have here some 3D player characters. So let's open this and here is where we have our health. And now we will see how we can add the health bar in 3D. So let's create a new scene, which will be a special scene. So a 3D scene. And I will call this health bar 3D. So what we will have in this health bar 3D? The first thing is that we will also have a health bar. So interface health bar and I will create an instance for that. Instance. Now, the second thing that we need is something, a 3D element, a mesh that we can handle this health bar as a material. So let's create a sprite 3D. Let's add a sprite 3D as a child of this health bar 3D. And now here comes the trick. So let's go to the health bar and I will move it right about here, just to make it easier. And I will measure the size of this health bar in pixels. So 64 by, let's say, 344. And the reason why we made that is because we will create a new node called Viewport. As the size of the viewport, we use the measures that we just collected. So in the x-axis, 344 and the y-axis, 64. And we will add this health bar as a child of this viewport. Remove the sprite 3D to the bottom. Now we can see anything, not even in 2D. This is because this viewport is a dedicated node and everything that is being rendered there is not being rendered in the editor viewport. OK, so what we will do now is that the sprite 3D must be a child of the health bar, actually. And what we'll do is that we will create a new texture here and it will be a new viewport texture. And we'll have to select a viewport, which will be this viewport here. And now you can see that the health bar is being rendered, but it's not quite what we want, right? So let's go to the viewport and we will set up some properties here. The first thing is that I want the background to be transparent. So we can take rid of this blueish background that we had previously. And you can see that the health bar is flipped in the vertical axis, right? So in the rendered target category, we have the V flipped, which means vertical flip. So let's toggle this. And now we have our health bar being rendered in this sprite 3D. So now let's save this health bar 3D in the interface. And I will just save it right inside the health bar folder as well. Save it. And let's add it as a child of our player. So player health bar 3D instance. And I will move it right about here above the player. And from here is pretty much the same thing. So if we open the player script, you can see that we have a reference for the health and for the health bar. And in the radical back, we are connecting the health to the health bar. So if we save it and test the game 3D and test the scene. And the first thing that you can notice is that as the camera rotates around the characters, the health bar isn't facing the camera. And this might be something that we want, right? So I will close this and let's go back to the health bar 3D scene. In this sprite 3D, right at the flags category, we have this billboard option, this billboard property. So let's enable the billboard. And you can already see that now the sprite is always facing the camera. So if we save this and go to the game scene again and test the scene. Now all the health bars are facing the camera. And this is pretty much what we want, right? So this is how you can render a 2D element in 3D. So that's it. But I think I'll make a bonus video in this mini series so we can just set up this health bar. Just to make some animations when the values change. And we can also see how we can do the gradient thing that brackets did in the video, changing the health bar color, depending on the health value. But for this video, that's it. Leave any comments or questions in the comment section and don't forget to subscribe to get more of this kind of content. And if you want to sponsor more of these videos, please consider become one of my patrons. That said, thank you so much for watching. Keep developing and until the next time.


When someone has faith that the gift travels in a circle, according to its own mysterious logic, then that person will be content to wait. Waiting does not mean withholding action. It means acting when it is time to act, and not acting when it is not time to act. That is also what is meant by the Taoist concept of Wu Wei. The common translation of Wu Wei, which is non-action, is really misleading. It leads us into passivity or quietism, and that's not what is meant by Wu Wei at all. It means actually to act in accordance with the Tao. That only makes sense if there is a Tao to begin with, something that we can act in accordance with. In other words, there is an intelligence, or a logos, or a way to the world. All of that is, all of that deep philosophy is part of the worldview of gift.