Welcome to the First Unitarian Society of Madison. This is a community where curious seekers gather to explore spiritual, ethical, and social issues in an accepting and nurturing environment. Unitarian Universalism supports the freedom of conscience of each individual, as together we seek to be a force for good in the world. My name is Karen Rose Gredler, and on behalf of the congregation, I want to extend a special welcome to visitors and newcomers, as well as you regulars. We invite you to stay for the Fellowship Hour after today's service.  We celebrate your presence among us. This would be an excellent time to silent cell phones as we join together in a few moments of centering silence as we become fully present with ourselves and one another, and come into this time and place together. Now I invite you to rise in all the ways that we do for our in-gathering hand number 347. Good morning. Let's use this to wake ourselves up. Gather the spirit, harvest the par. Our separate fires will kindle one flame. Witness the mystery of this hour. Our trials in this flight appear all the same. Gather in peace, gather in thanks, gather in sympathy now and then. Gather and strength, gather to celebrate once again. Gather the spirit of heart and mind. Gather, gather in sins again. Gather the spirit of heart and mind. Winter to spring, resound these gather. Please remain standing for our opening words in the lighting of the chalice. As we enter this shared sacred space, let us renew both our commitment and our covenant. There are those among us who have endured a loss in the past week. May their hope be uplifted again in this community of faith. There are those among us who have wrestled with questions that seem to have no answer this past week. May they find sanctuary in this community of faith. There are those among us who have cherished an unexpected joy in the past week. May their gladness be celebrated. As we commit to continue our free and responsible search for truth. May we covenant to honor the many paths that have led us to this time and this place together. And if you will now join in the words of affirmation as we light our chalice. May the light of this chalice give light and warmth to our community. When we are joyful and when we despair. And may we feel the warmth spread from our circle to wider and wider circles. Until all know they belong to the one circle of life. And if you will take a moment now to turn and greet those around you.  Hey guys, good morning. Did you have a good week? Yeah? Hey, Nolan? Did you have a good party? How's it feel to be seven? Any different than six? No. Hi Lily. Morning everybody. Our story this morning may seem familiar yet a little different. It is called the Little Red Fort. Ruby's mind was always full of ideas. One day she found some old boards. Who wants to help me build something? She asked her brothers. Wait a minute. That's right. Oscar Lee pretended not to hear her. Rodrigo gave her a look that could melt popsicles. Jose almost fell off the fence. You don't know how to build anything, they said. Ruby shrugged, then I'll learn. And she did. Who wants to help me draw the plans? Ruby asked. The boys clutched their sides and howled with laughter. Not me, said Oscar Lee. I don't think so, said Rodrigo. No way, said Jose. I am too busy. Fine, said Ruby. I'll draw them myself. And she did. Satisfied with her plans, Ruby asked. Who wants to help me gather the supplies? What do you think they're going to say? Not me, said Oscar Lee. I don't think so, said Rodrigo. No way, said Jose. I am too busy. Fine, said Ruby. I'll gather them myself. And she did. When all the supplies were gathered, Ruby asked. Who wants to help me cut the boards? Not me, said Oscar Lee. I don't think so, said Rodrigo. No way, said Jose. I'm too busy. Fine, said Ruby. I'll cut them myself. And she did. When all the boards were neatly cut, Ruby said. Who wants to help me hammer in the nails? Not me, said Oscar Lee. I don't think so, said Rodrigo. No way, said Jose. I'm too busy. Fine, said Ruby. I'll hammer them myself. And she did. Soon, Ruby's creation was complete. Who wants to play in my fort, she called. That is a fancy fort, isn't it? That is. It's not red yet, is it? Good. Good eye, let's see what happens. So what do you think they're going to say when she says do you want to play in my fort? They're going to say yes. Me, me, said Oscar Lee. Let's go, said Rodrigo. I'll play, said Jose. I'm not busy anymore. Not so fast, said Ruby. You didn't help me draw the plans or gather the supplies or cut the boards or hammer the nails. You said I didn't know how to build and you laughed at me. I'm going to play in the fort by myself. And she did. See how happy she looks? Now, what do you think? You, you think? We didn't want to play anyway, the boys said. But they did. So they huddled, whispered, and got to work. Oscar Lee made a mailbox. Rodrigo planted flowers. Jose painted the fort fire engine red. Ruby was delighted. That evening, the boys followed a delicious aroma to a fort warming party. Who wants to help me clean this plate, Ruby asked. We do, the boys said. And they did. They ate it all. Now, I really like this story. Does it remind you of anything? Yeah, the little red hen. Exactly, I thought it would be familiar. But here's what I love about this one. So does Ruby give up when her brothers tell her that she doesn't know how to build anything? Does she say, yeah, you're right, never mind? No, what does she do? She learns exactly. She learns how to do it. She keeps trying again and again. And think back to those pictures. When no one would help her and she had to cut the boards and hammer in the nails, did she do that by herself? No, did somebody help her in each one? I love that part too. Look at here. Do you see she found some grown-ups to help her do that? So she didn't give up when her brothers told her no.  Let's just have a safety announcement. Never use a power saw without a grown-up, okay? And then at the end, what happened at the end when her brothers pitched in and built a mailbox and planted flowers and painted it fire engine red? Did she, she was delighted and did she still say, there's no room for you? Or did she let them come in the fort? She let them come in the fort because there's always room for more, right? Thanks. Right, and right, it's more fun to play with others in a fort than it is to be in there by yourself. You guys are awesome. Thanks so much for listening to Ruby. We are going to rise in all the ways we do and sing you out to class. Humanly past and present people's near and far. This morning is taken from the writing of Christopher Bice, a Unitarian Universalist minister, entitled Grandmother's House. Over the river and through Atlanta traffic to Grandmother's house we'd go. That was our routine during various family holiday gatherings of my childhood. I remember looking at all the food spread out on Grandma's dining room table. There was a large turkey roasted to a golden brown. There were salads, casseroles, dressing, freshly baked rolls and a variety of vegetables to choose from, but these were of no interest to me. There was only one dish that mattered. It was served in an elegant fine china bowl with a ladle to the side. It was a delicious, piping hot bowl of spaghetti-os. I was always excited to see that Grandma had cooked my favorite dish. She had lovingly opened the can, poured the contents into a pot and warmed them to perfection. And of course, there was the presentation. I am probably one of the few people on earth who has been served spaghetti-os from the finest china. My grandmother was a southern Baptist. My father, her son, became an Episcopal priest. I am a Unitarian Universalist minister. Grandma died before I became a member of a UU church. I am not sure how she would have reacted. Perhaps she would have felt the same way as my aunt, who once exclaimed to my brother, Sam, Chris is a Unitarian. I thought he was at least an Episcopalian. This was not a diplomatic comment, considering that Sam is an Episcopal priest. Would my grandmother be surprised by my choices? Maybe not. Grandma taught me from earliest childhood that there is room at the table for someone who is a little bit different from the rest. The memory of that bowl of spaghetti-os continually reminds me to make room in my heart for people whose tastes and disposition might be different. There can be room in our hearts for all. There can be a place at the table for everyone, even the more finicky children of God. Here ends our reading. You may have noticed, OK. Thank you. You may have noticed in your order of service that there's kind of a curious mashup of titles there for the anthem. It's a spiritual, Go Down Moses. And we'll follow it immediately with an Italian opera chorus. And we'll be singing in Italian. And I wanted you to know why we were doing all of that here in our monthly theme of sanctuary. The last time a choir sang in a service, we talked about music as sanctuary. And I used as an example a spiritual. And we're doing that again today. The idea that music can protect us, that music can be a sort of traveling sanctuary and surround us wherever we go. In the case of the Italian opera chorus, and the spiritual, they're both also songs of protest. In the case of the spiritual Go Down Moses, they're singing about the Hebrew slaves wanting to be released from Pharaoh. And it was the slaves way of kind of being able to say to their slave master, let my people go without actually saying that, but actually using the Bible, the biblical verses, that they were being taught to sort of point out the hypocrisy of slavery in America in general. In the case of the Italian opera chorus, it had a special meaning. Verdi was not just a composer and an important figure in general in Italy. At the time, he was also a politician. And Italy was struggling with great divisiveness. And it was made up of many different states, if you will. And they were trying to unify it under one leader. And this movement, these agitators, went by the name resogimento, rising again, rising again. And they had great passion for their cause. Verdi said at one point, you speak to me of music? What has gotten into you? Do you believe I want to concern myself with notes, with sounds? There must be only one music. Welcome to the ears of Italians in 1848, the music of the canon. And indeed, Verdi became a symbol of the resistance because the king that they were trying to seat for all of Italy, I'm not sure why they chose a monarchy during this revolution, it ended up not working out too well. But at the time, they thought what we need here is a king. And the king's name was Victor Emanuel Reditalia. The initials for which are, V-E-R-D-I. So this allowed for this underground to shout Viva Verdi in public. Thank you, society. Choir for the beautiful gift of music this morning. The 13th century Persian mystic Rumi is often said to be the best-selling poet of the 21st century. I don't think it's accidental when you read his words. Out beyond ideas of wrongdoing and right doing, there is a field. I'll meet you there. When the soul lies down in that grass, the world is too full to talk about. What is it about a Sufi poet who lived over 800 years ago that catches our attention? I often think of these words about a magical field when I contemplate the idea of sanctuary, a place apart, a place of refuge and healing, welcome and peace. I wonder if his words resonate today because our culture is so often motivated by winning and losing, preoccupied with presenting ourselves to be right and others to be wrong, sitting in judgment about the thoughts and actions of others. Our political systems are deeply mired in differences of belief so that little or no positive action can be created. Our news is filled with stories of conflict, contentious interactions, and power struggles. The challenges of modern life can certainly appear overwhelming. This past week, I spent some time unplugged from modern life as I joined a group of 30 adults, teachers and parent chaperones who were taking 71 sixth graders to Upham Woods, an outdoor learning and education center in the Wisconsin Dells. This is an overnight trip where students spend two days hiking, participating in team-building activities, studying the microscopic life to be found in pond water, all the while creating something of a sanctuary together in the woods. At our parent orientation, a staff member shared that not every student, given this opportunity, chooses to attend. She said, for most of these kids, it is the first time away from home, away from their families and their routines. It is anxiety producing for them to be away from their safe and comfortable spaces. It's a different way of being with others, some of whom you don't know well or know at all. You have to trust that it's all going to work out okay. Every year, we have kids who stay home instead of coming with us because the thought of entering this different kind of space with people you barely know is just too much. Zenzu Earthland Manuela Soto Zen Priest recently wrote a book titled Sanctuary, A Meditation on Home, Homelessness and Belonging. In it, she writes, finding home, feeling at home, being at home, our complex, multi-layered spiritual and cultural experiences independent of the place we live. Where is home? When I don't feel at home, where can I find sanctuary? These questions become critical when we are in a situation filled with anxiety or fear. Sanctuary is a feeling of being at home, a place where we feel our common humanity, shared trust, respect and love. To feel at home, we need to be recognized, acknowledged, seen for who we are. It gives us the energy to transform ourselves, to see possibilities, to work for a world where all are respected, seen and held in peace. This is the book I was reading when I headed into the woods with middle schoolers. Does anyone remember middle school? My memories of it are not particularly filled with moments of belonging, of common humanity or trust, respect, love. I didn't know what to expect when I headed into the woods. I know I wasn't expecting what I found. The dozen kids assigned to me were a varied group, from differing elementary schools to having known one another since kindergarten, some who met last year, most having just met a short six weeks ago. They were still learning one another's names. And yet here they were spending the next 48 hours together in intentional community. When we headed up to our team building activities, they were a pretty quiet group. Two hours later, they were boisterous, proud of their accomplishments, laughing as they recalled their funnier moments, saying things like, I can't believe we did that. We were amazing. They were yelling out to me, did you see that? Did you see us? I smiled and told them I did indeed see them and that I was so very proud. I was grateful for this opportunity because what I witnessed in that time taught me a great deal more than they could know about how we create sanctuary for one another, how we create spaces of belonging. I was reminded that creating sanctuary takes imagination, trust, and determination. It also takes a great deal of relationship building. When you spend time getting to know people, when you build relationships first, it is okay to fail later. Our group began with activities to learn one another's names, gradually followed by activities that were more complicated. What began as simple talking became conversation, asking questions, seeking out ideas, reflecting on what we had done. I noticed how these seemingly simple games were really about building trust and respect, learning to see the larger connections between us. It is this foundation created through trust and respect that allows us to embrace deeper challenges together. The concrete example of challenge for these youth using that trust and respect and understanding was literally to move each person through a spider's web created by elastic cord wound between two trees. It took them 27 times to complete the task. There were many mistakes, failed attempts, and missteps along the way. I was expecting frustration, I was ready for disappointment, maybe some flares of anger, but none of that appeared. Since they had built their relationships first, had some knowledge of one another, they were allowed to take risks, make mistakes, work as a team with a larger connection and a larger goal. They learned the importance of sharing ideas with everyone and listening to the ideas of everyone. When a few people were trying to plan the next move on their own, our naturalist would yell out, can you all hear this idea? And then everyone would stop and turn and listen. Creating sanctuary means speaking up, sharing our ideas and also listening to the ideas of others. It is only through listening to the voices of all that we have any hope of moving forward. Our naturalist reminded them time and again, solo efforts are impossible to sustain. Between each activity, the team would huddle to reflect on what had been learned, how this would help them moving forward into the next activity. How many times do we rush from one thing to the next, never slowing down to ask what went well, what did we notice, what could we change? The slowing down time during those 27 attempts allowed space for the new to emerge. Pausing to reflect on what was happening, they stopped doing the same thing over and over again. They waited to see if there was something new, indeed something different trying to emerge. I didn't know what to expect when I left for the woods. What I found was a group of 11 and 12-year-olds who created sanctuary for one another, a place where they could bring their full selves, a space that held a deep recognition of shared humanity, a place of respect, a place of caring. To create sanctuary spaces, we need to be willing to do something that may seem personally scary or risky for the sake of a larger commitment that we have made, whether that commitment is to ourselves, to our families, our friends, or the values we hold sacred. It's a space that calls us to choose trust over fear. Choosing to be true to one's own self when the world insists that truth lies elsewhere and that you must quiet your own small voice. In the 1960s, the Reverend Charles Grady wrote that our churches are clearings in the wilderness of this time, places of refuge and sanctuary for the bruised and the tired, and also places of healing and renewal. They are workshops for common endeavor, schools for learning and enlightenment, transmitters and celebrators of a heritage, tools for breaking down barriers, tools for building new bridges. Our churches are clearings in the wilderness of this time. Charles passed away in January of last year and he preached a sermon just a few months before his death where he said those words again. He said that he meant them in 1960 and he still means them today. He said, I mean it now with this much trouble and exactly this much beauty swirling all around us. We need to create places of sanctuary for the bruised and the tired. We need places that hold us, places that know deep in their bones that we have a strong and holy purpose. What we do here has to be about more than the relief of finding a tribe of others of like mind and resting easy in that comfort. It is more than socializing, more than self-expression. Here you are called by name, the shimmering constellation of your identities acknowledged and here you are called to account. You are accountable to one another, to all people, all persons, every living thing. This is easy to say in words during a service. It is difficult to practice all week long and on the ground, face to face and one on one to discern for each of us what it means to be unitarian universalists in our homes, in our work or even in the woods. Margaret Wheatley said, you don't fear people whose story you know. If we really want to create sanctuary here, a place of true belonging, then we have to know one another. We have to be brave enough to start conversations. We live in a world of dehumanizing rhetoric where people's humanity is reduced and they can be hurt or have basic human rights taken away. We live in a world of assumptions and stereotypes when people who are not like us live out there. If we want to create spaces of sanctuary, then we have to move in close, start conversations. When we learn the story of another, we connect in to that common humanity we share. If 12 kids with very different histories, backgrounds, skin colors and language can do it, I think we can too. We can be brave enough to listen with a desire to learn more about another's perspective. We can say things like, tell me more. Tell me what really matters. Help me understand why this is important to you. And then we do that hardest part, listen. Listen to understand not to agree or disagree just to move in closer and learn another's story. Here's what I believe. I believe that more than ever we need to be with one another here. We need to talk to one another about what we believe, what sustains us, what matters most. We need to be friends to one another and each and every single time we are here, we need to add at least one more person to our circle. Solo efforts are impossible to sustain. Last weekend at our parish meeting, our open question asked, how does FUS provide sanctuary for you? And how might the sanctuary you find at FUS make us better able to offer and support sanctuary in the world outside these walls? As the groups reported out, we heard time and again, FUS is a sanctuary for me because here I am welcomed, here I am home. We heard the importance of being a community of welcome. The need each time we gather to be welcoming, to be of kind heart, to willingly listen to another story. Welcome every person in. Say hello, reach out so that everyone who enters is greeted. The need to be a people of welcome and open hearts to every person who walks through those doors.  At every turn during fellowship hour, someone new saying hello. Together we can create a space of sanctuary, a community where more people are meeting one another and sharing their stories, where more people feel welcome, find connection, build relationships, find a home. And in that feeling of home, living with sanctuary within themselves and within this community. The world is full of the bruised and the tired, of hungry, lonely souls. Our greatest hope and our greatest power lies in reaching out beyond ourselves, seeking both to build our relationships in community here and to encourage each other to act for change in the world around us. Find one person today after service whom you have never met and share a story from your week. I spent time with middle schoolers in the woods. What happened for you? Take the time to get to know others and to be known. Make time for the spiritual renewal that we undertake so that our own sense of serving something larger than ourselves, our own sense of shared meaning with people here grows. When we can take this time, slowing down, reflecting upon what's emerging within us and among us, we can hold sanctuary in this community, a space of healing, a space of vision, a space of holiness and peace for ourselves, for all who walk through our doors. Out beyond ideas of wrongdoing and right doing, there is a field, I'll meet you there. And I now invite you into the giving and receiving of the morning's offering, our outreach offering recipient this weekend is the YWCA of Madison. You can find out more about them and their good work in your order of service and we thank you for your generosity. In the shared ministry that is our weekend services, again and again, we are offered the opportunity to practice gratitude. And so we take a few moments in our service to remind ourselves of the gift of those who minister to us that we might come to this time together. In that spirit, we honor that our greeter today was Claire Box and we are grateful that our ushers are Brian Channis and Mary Savage. We acknowledge with deep gratitude that creating a space of hospitality through the ministrations of coffee, a big thing for Unitarian Universalists, Blaze Thompson and Biss Nitschke offered their gifts. We are deeply grateful that the beautiful flowers this morning were brought in part by Heidi Wilde and that our lay ministers this morning are Dennis Collins and Ann Smiley. This morning if you would like to have a tour after the service, we invite you to come forward here by the ramp and John Powell will offer a tour and our welcome table and information table is staffed by Dwork Bergen. Each of us is called to think of our own pathway of service as well. There are several opportunities today that we want to let you know about. The road homes work to end family homelessness in Madison County is an important service that we have been involved in in the past but we want to let you know more about how you can get involved this December. So immediately after the service at 10.15 to 11 in room C, there will be a gathering offering some information about how volunteer opportunities may be utilized, especially for our families. And so all ages are welcome and yes, coffee will be served. I hope you will join us in room C. After the second service this afternoon at 2 p.m., we will be offered a lecture entitled The Value of a Third Space presented by the founder and CEO of Infamous Mothers, Sagacious T. Levingston. The event will be held here in the atrium auditorium and is followed by a book signing and light refreshments. It is free and open to the public but donations will be accepted for the organization Infamous Mothers. Ms. Levingston's talk will focus on the importance of rethinking space and place in our struggle and work towards racial justice. And finally in terms of announcements, we have begun our journey circles but there is still an opportunity for you to find out about them and join them. Journey circles are another version of our small covenant groups. And as I have been talking with many of you over the last couple of months, now almost 70 of you, I would say over half of you by a long shot have talked about how important small group ministries, a chance to really get to know each other, how essential that is to your sense of belonging and connection here. Well, this is another opportunity to participate in those kinds of circles, probably the biggest difference of the journey circles is that there's an even more meaningful connection with what's happening here on Sunday because those groups will be exploring our monthly themes. So if you'd like to find out more about those circles, you can stop by the table in the commons and if it is a good fit or a possibility to sign up for a journey circle. We move into the cares of the congregation and I invite you to enter into that space with intention and preparation. So I invite you to find a way to be in your chair so that you feel balanced and open and well-grounded with your feet connected to the earth. And for us to let a very simple but powerful tool of mindfulness, our breath, bring us to this space. As you breathe in, let it bring you into this time, this space, into your body. Where do you feel your breath most powerfully? That source of life and spirit. And as you release breath from your body, may it be a gift to this world. Symbolic of the gift of your life, with each breath in, a call to presence, with each release of breath, a connection to all that is from that place of grounding, from that presence. We may know joys and sorrows that are part of each and every life and so in this place where we practice community, where we know that we are discovering what it means to be loved and to give love. We come together in deep strength and common purpose, remembering all those in our own lives who have celebrated moments of great joy or who are in the midst of struggle for just a moment. I invite you to call to mind yourself and those that you know and hold them in your thoughts or prayers. We also remember this morning to offer extra prayers for all of those who are imprisoned. May they have hope and a positive support group within their own life experience. May we recall that all the joys and sorrows, both those shared and those that are yet too tender to share that they are held in this place by each of us. May we remember in this time the power of being part of the web of life, inviting us to connection with all humanity, reminding us of connection with all that is. May we be grateful for all of the gifts of our life, for the power of sharing and from that gratitude may hope, care, remembrance, love be the gift we give back for this and so much more we hope and we pray and blessed be. May we rise in all the ways that we do and join together in our closing hymn, number 121, We'll Build a Land. The dibs go free where the oil of gladness dissolves anointed by anings to all the afflict those who mourn and will give them garlands instead of ashes, all wisters and brothers anointed by guise, where job will be a land building of ancient cities, raising up devastations from old, restoring ruins of Jack. Come, build a land where the mantles of praises resound from spirits once faint and once weak, where like oaks of righteousness stand her people, oh, come, build the land we seek, castors and brothers anointed by then grief, I pray this day for the courage to be humble in the face of inequity and pain, to know that the power has been given me to make a difference. I pray for the courage of endurance to keep acting in the midst of despair, to keep trying in the aftermath of failure, to keep hoping in the emptiness that follows loss or change. May courage give us patience and may we ever know love's healing presence at the heart and center of our days. We extinguish this chalice flame, but its light lives on in the minds and the hearts and the souls of each of us. Let us carry the flame with us and share it with those we know, with those we love, and most especially with those we have yet to meet. Blessed be, go in peace and please be seated for the postlude.


What's going on everyone? Sam here with Layton's sports cards. We're in one box, a 23, Panini Select, WWE Hobby. Four Matthew M. So good luck here, Matthew. Let's see what we got, buddy. Two autos, one mem. Let's see a 101 for a gold or a green. Any of those will suffice. Absolutely suffice. That is a Drew Gulak tri-color there. Silver, Jake Roberts. That is a blue of Charlie Dempsey. That is going to be 249. This one here, auto 47 of 49. That is Luke Gallos. Nice one there on the red auto. Yes, they do, slightly. Yes, sir. And Montez Ford. Potentially Brody, I'm not 100% sure. I don't want to guarantee it. That is a Lecture Lopez. Silver of Bianca Belair and base. I would probably lean toward no on that one if I'm being 100% honest with you. But it will go tomorrow morning. Ivy Nile. Again, we do in personals over here on the main channel, starting at 10 a.m. Eastern time. So if you don't go tonight, you will go tomorrow morning. So you only have to wait about eight hours or so. Nice, Batista White to 125. Oh yeah, Bunk. Yes, sir. Yeah, we're on YouTube and Twitch. Yes, there, yes there. That is a Carmella Red to 175. Ooh, we got a Gold Beans on the ringside. That's pretty cool. Wow, three of 10. King Krat's Matthew. That's a pretty big card right there. There is a small dimple on that one, unfortunately. I will send the empty box and wrapper, but that is massive. That is a sick, sick card, man. Get that into a Mac for you, buddy. Really, really, really nice. Really nice Roman Reigns. That's so sick on the ringside. That's freaking awesome. John Cena and Miko Sadamura. These are just personals, Bunk. These are just personals. Thea Hale, Auto is going to be Tori Wilson. Silver, signature selections. Roxanne Perez. That is a Booker T. Tri-Color. You know who has relics in this? That's actually kind of sick. Um, no. Pat McAfee. Oh, does he really? Yes, he does. I didn't know that. Red, Gigi Dolan. I swan there, too. 149. Let's make a deal and card Monster Chuck. Rally, base. And last pack here. Good luck here, Matthew. Big Roman Reigns for everybody. Silver, Carrie Ann Bronx. Got a Dana Brook. Can't read upside down apparently. Dana Brook on the relic card. Superstar worn slash used material. And a Rowdy Roddy Piper. That is going to do it for your break there. Matthew, congrats on the hits, buddy. Get them right out to you, my man.


What is the relationship with Jesus? It means that I am connected to him through a covenant It means I live my life with an intent and it also means I never stop learning God doesn't want you to go through life God wants you to grow through life and God does not want you to become a scholar He wants you to remain a student When I was at 14 years of age and I Thought I had God figured out. I Went to a very big church. It's a over probably a thousand and a half or two thousand member church a very big church And I I don't think I've read the whole Bible through I read the New Testament many times But when we came to the United States, I knew I had God figured out and I knew what God wanted. I knew that God did not want people to raise hands during worship Because that's how we grew up and is that during worship? Well, there was no worship Just singing hymns and you're not allowed to raise your hands. You're not clapping was not allowed in the church So I knew this is what God is God doesn't do clapping and the hopping. I mean, this is complete hiddenism and paganism This is wrong and when you have drums I mean, this is the next thing to like witchcraft and like this is clubbing and when you have lights This is really bad and women do not if women wear earrings I mean it's it's bad and when you wear a tie It's an arrow point straight to hell and I knew I had God figured out when we come and some of you Don't know what I'm talking about because you did not grow up like that and praise God for you But for me when we came to the United States and my pastor comes and he begins to instate the worship means We have three songs and we sing and we we can raise our hands and I was so bottled up by that because in my mind I already 14 years of age and I have gotten God figured out. I Was able to fit an ocean into a cup And I remember debating with Ilya my cousin and I was proving to him that God hates people who dance I didn't have a scripture for it, but I knew it and Ilya brings the scripture opens up and says there's calves the people will dance like calves I was like that's for animals not for humans And I remember fighting with I was just clap all to clap your hands All your people shout to God with the voice of tribe and I'm like no it's wrong And I'm listening to myself. I am saying no to the Bible Let's say the Bible is wrong because my problem is that I became a scholar at 14 years of age I've gotten God figured out Some of you you were scholars until you came to our church You knew how the service is supposed to be that and you knew how people supposed to be delivered You've never seen one, but you knew how they're supposed to be delivered You knew what the church supposed to be like and what's not supposed to be like until the first prayer line. You're like, what is that? You became a scholar and Jesus says if you want to grow in me, you'll never graduate from student You always a student you're anointed worldwide ministry people are falling under the power of God Remain a student why because the moment you stop being a student you become a critic Every movement in Christianity that stopped being a student and became a scholar became the movement that picked up the stone That says we know how God supposed to do and that is not God every movement and We are personally in danger of that because right now we are used to what we see here and Jesus says never stop learning


Hello, everybody. My name is Andrea. If you are new to my channel, thank you so much for hopping on watching the video click like I love the likes and feel free to comment anytime. This is actually this video is from a comment that I got on my channel, and somebody was asking a question of what do you need when you're going moving to different states if you are a dental hygienist what types of things do you need to prepare for your work in other states. What do you need to do in order to do that. So that's a very loaded question but I'm going to explain it of course for you here that's the purpose of this video, but the rule of thumb is going to be it varies so much. I've been a dental hygienist now for a while I've been in the dental profession since, since I was 19. So I was a dental receptionist dental assistant a dental hygienist and then I became a restorative dental hygienist which you're not allowed to do in all areas. I am, I am also a mobile dental hygienist so I have my own practice, which are not able to do in all states, not all areas. So my first question is, what type of dental hygienist are you, are you a registered dental hygienist. Are you a registered restorative dental hygienist.  Are you able to have your own business as a dental hygienist or do you have to work alongside a dentist. So you need to figure out which one you are. And then where you're going to move to what they allow you to do. For example, here in Ontario, we can have our own business but you can't in every area, a lot of dental hygienists still have to work alongside a dentist. I cannot give local anesthetic, but in other areas, you can. You might not be able to have your own business there, but you can give needles. I know, weird. So you really, the best thing to do is contact the Dental Hygiene Association, specific to where you're going to move to because it varies so much you guys I can't even tell you it varies so much. Contact them, either by phone, email, they probably won't get back to you right away so give it a couple weeks, but they will get back to you and they will help you. Another thing you could do is join those groups on Facebook, those dental hygiene groups on Facebook. I'm part of many. There's dental hygiene professionals group. There's dental hygienists of Ontario there's Canada dental hygienists there's dental hygienists in the states there's so many different ones feel free to join any of those and post a question. Somebody else from your area might be able to help you so I hope that helps comment below with any questions but again you guys I can't stress this enough. So please check with your local dental hygiene association where you're moving to on what the regulations are, but I will quickly state state moving to the states states. I'm hilarious not really but anyway. Oh boy, I've been working you guys all day there with me.  Anyway, the last thing that I want to say is, these things can take time so let's say you're moving from Ontario to the states, you will have to take a different board exam. If you took your board exam in the states, you can most likely not have to take another one as long as you stay within the states. But let's say you're moving from the states to Canada. You will have to take another board exam in order to be a licensed registered dental hygienist but please check with your local dental hygiene association, even if you don't have to take another board exam because you're moving within the same area per se. You will have to be licensed for that area. So just because I'm licensed here I would not just be able to move somewhere next week, and be licensed to there I have to apply for that with the local dental hygiene association you can do that online so that's another note comment below with any questions thank you guys so much for your comments, click like to this video if you haven't yet I would love that, and I will talk to you guys all very very soon.


Should I, uh, click this? Oh. Daniel Mullins. I don't know who that is. Devolver. I know who they are. They've made some great games. Okay. Okay. Okay. What is that? My cranky crew. Did that for great gameplays? And today, we are here in inscription. I have heard a lot about this game, uh, specifically from Mark. Mark was like, you should play it. It's really, really good. So I said, okay, I need things to record. So here we are today. I don't know if I'm going to do a full playthrough, uh, or what. It kind of depends on what you guys think, um, but we're going to at least do this first video. So continue, but I, I haven't played this, uh, new, what, continue? But I haven't played the, I just downloaded this game. Why does that say continue? That doesn't make any sense. Uh, all I know about this game is that it's a card game, which usually I'm not crazy about. Another challenger. It's been ages. Perhaps you've forgotten how this game is played. Allow me to remind you. Uh, yeah, I have forgotten actually. Squirrel, Stoat, Wolf, and Wolf play the squirrel card.  You're lacking sacrifices for that game return. Okay. Squirrel. Just anywhere. Now player Stoat. Uh, yes, uh, on, on top of that, uh, an honorable death, an honorable death, play the Stoat. Now the wolf, wolves require two sacrifices, you don't have enough. Ring the bell to end your turn and commence combat. Your Stoat stands up, stands unopposed. The number on the bottom left is its attack power. Okay.  Your Stoat dealt me one damage. I add one to the scale. You win if you tip my side all the way down. Like this. Okay. My turn. Who are you? A coyote! Your Stoat stands in the way of my coyote. Okay, but he's only got one. Or wait, he, no, he's got three, but you deal two. So that means he leaves only one. These really don't have a lot of stuff, do they? My coyote dealt two damage to your Stoat. Okay, that means your Stoat's death, or your Stoat's health is too less. If a creature's health reaches zero, it dies. Okay. Now it's your turn again. You may draw from your deck, or you may draw a squirrel. I'm gonna draw from my deck a river snapper. How reckless of you. So I can't, I can't attack. But he has one attack left. Or has he done so?  I realize what I've done wrong. Wait! Because you are learning I will pass. Okay. You've drawn all the creatures from your deck. A squirrel is your only choice. The river snapper demands two sacrifices.  I'm gonna play a wolf. If you're not the beast of sacrifice, but not removed from your deck, it's suffering was real, but you will see it again. Okay, the wolf goes there. Okay. Oh. Oh! Three damage dealt, three ways. Three ways on the scale. You're passing again? Okay, I'm gonna take a squirrel. He's still going, baby. He's still going. You've won this match. It won't all be so easy. Let me recall your story. Oh, yes. Oh. We were lost deep in the forest. A single path revealed itself. Damn. This is really cool so far. Two denizens of the forest approach you tentatively. I'm gonna do this. The undying cat sacrificed in the poor beast does not kill it. The caustic adder. Declared from its poison bite, it's always lethal, always. You may only grace your, only one may grace your paltry deck. Never dying, eh? I'm gonna take this guy. Another creature joys your caravan, joins your caravan. I might be able to get one later. Some of the creatures of the forest seemed willing to follow you. You came across an abandoned sack. You found a squirrel in a bottle, breaking kids of emergency, and have a second. Two? Another useful implement. I'll allow you to tip the scales with it. Markipliers. There's three as much as, uh, three as much as you can carry. Okay. Cool. Okay. Death time. Is this our first battle? Boulder. You were ambushed while crossing some rough terrain. Okay. There's a boulder? You sacrificed me while I was sleeping. It was the right play. I get it. Maybe. You mad at me? You, you'll help me? Play along for now.  You may now see my noose ahead of time. Okay. All right. I'm gonna play a squirrel. And I'm gonna play a cat. Cat's gonna go here. And I'm gonna, can I? When a card bearing this sigil is sacrificed, it does not perish. Hell yeah. Cool. That's sick. That's so cool. That's a good move. Okay. Uh, great. Um, let's see, one, okay.  Oh, that, I get it. Mind the ambitious wolf cub. It ages swiftly. Okay. Let's take another squirrel. That guy here. I really like that. A bat. Okay, cool. Whoa. Airborne bat flies over creatures to attack directly. Oh man. Oh man. My bat flew right over your river snapper. Wow. Okay. So let's pull a guy. Okay, cool. Let's sacrifice, uh-huh. And we're gonna put you here. Okay. Damn. That's cool. The bat is sweet. Okay. What do we got here? Okay. We're gonna do this and this. Wolf. Can I? Whoa, it's my hand. Let's do that. This is really cool. I really like this so far. I like how the scale is used. Okay. I guess I'll put this here.  I shouldn't have really done anything, should I? Or maybe I should have. Is that game? That is. You prevailed and trekked onwards past the now-bloodied terrain. I really liked it. I liked this so much more than I thought I would. Wolfcob. Young wolfcob. It grows into a wolf after a single turn. Okay. Oh, and it's only one. Sparrow. An inexpensive, if feeble flying creature. It only deals one, but I really like, I'm gonna take the sparrow because I like that it can fly. I feel like that'll be useful.  You've stumbled into some strange stones in the mist. You're compelled to choose a worthy sacrifice. One that will be lost forever. I guess the sparrow. The cat's really good, right? I feel like the cat is really good. I'm gonna sacrifice the sca- sparrow. Pick me. What? Whoa. Whoa, whoa, whoa. Whoa, whoa, whoa. What an honor. Yes, chef. Great.  The ghastly spectacle. But the soul of the sparrow now lives in the stove. Whoa. That's cool. So it can fly now? That's dope. Good to know. Good to know. Behold my totem. It inscribes my canine cards with the airborne sigil. That seems OP. That seems really OP. He's completely insane. I see that, right? No care for the rules. Pathetic, really. Oh, my gosh. I kind of like you. Only keeps me around to watch me suffer. Are you talking to me or about me or the other dude? Okay. Uh, we're gonna do this. We're gonna do this, uh-huh, and play that there. We're gonna do this, sacrifice you, put you here. What did you say? Back at the board. That's right, you are. Okay. This is a little spooky. I forgot I should have looked. Two, one, one, two, four. Okay, cool. Let's do this.  Oh, boy. My totem has granted my coyote the power of flight. Oh, no. Oh. Oh, my God. Uh, Jeepers. Uh, do I, should I, no. No, no, no, no. I'm gonna use, I'm gonna use one of these squirrels. And then bam, bam. Wham, bam. Thank you, man. I'm gonna do this. Yep. Okay. I think this might be good. Maybe. You're four damage away from winning. Uh-oh. Uh-oh. Uh-oh. Did I just die? Okay. Uh, this is kind of all I can do, yeah. Hoo, hoo, hoo. Hoo, hoo, hoo. Oh, that's very close. I mean, I guess I kind of have to do this, right? Okay. I'm gonna put that here. And the turn. Bam. Go away. Coyote. You're out of space. There's no more room for that card. Okay. Uh, oh. Can I? So, okay. I guess I just have to keep ending my turn to see. Hey, nice. I think this will do it. Nope. We're really going back and forth on this one. Yes. Nicely done. Nicely done. Impressive. You may yet survive this ordeal. Knock on wood. My desk is not made of wood. It like, the finish, I don't know if it's wood or not. No, it is wood. I remember when I drilled into it. I drilled into it to put the legs on. I want to make that very clear.  Porcupine. The ornery porcupine. Sharp quills await those who dare attack it. The stalwart snapper. A near impenetrable defense. Or a wolf. Vicious contender. Uh, I mean, we already have the wolf and the snapper. Let's go with the porcupine. I might as well, you know. Hmm. I don't know what the fire is, but the totems are... Let's do the cat. Let's sacrifice the cat. Hmm. Yeah, let's do this. With... Damn. We would need the wolf though, wouldn't we? Maybe let's not sacrifice the cat. Or have I already done it. Let's do a strong defense. I think... I'm gonna keep the cat for now. I'm gonna do this. Even stronger defense.  Look at that. Damned it. Damned it. Once again, this is the first time I'm playing this game.  Well, you know. For both of us. It's somewhere in this fowl cabin. Be silent or I will tear you to shreds. Grand fur. What do you have? Grizzly? This spot? You sure? Yeah, I guess that was kind of a bad decision, wasn't it?  Yeah, that was really bad, but I can't undo it. Oh, no. Okay, so I need maybe one of these guys over here. For sure. I'm gonna take this guy, put him out of here. I'm gonna take this guy. Oh, Bobby. Oh, yeah. This was a bad choice to make. This...   Oh, my gosh. Oh, my gosh. Okay. Yep. You can't draw blood from a grand fur. Oh, no. Please. Kill him. Put him here. Sure. Doesn't really matter. Okay. Um, let's see. Oh, can't do that still. This might be the end for ol' Ethan. Wait! Wait, what? You've lost. Using this as a learning opportunity may be the only way to mitigate my disappointment.  Get up from the table. What? Fetch a candlestick from the top of the barrel beside the door. Oh, whoa. Oh, boy. Interesting. Bring it here. Oh, over there.  Okay, let me explain something to you. Oh, that was one of two mistakes you can make here. If you make another, I must sacrifice you. Now, where were we?  Let's go here. We haven't done the campfire thing yet. The adder, the river snapper, and the bullfrog. The watchful bullfrog. It leaps in the way of attacking fires. Let's take the adder. Now we go here.  Faces shrunken from starvation. They huddled around a campfire. They look upon your group of creatures and beckoned. Come warm one of your creatures by the fire, one said. Warm up by the fire. They will enhance its power, said another. You notice one of the survivors wiping drool from their mouth. Interesting. I don't know about this one. Hmm. Uh-huh. Will it enhance the power? Huh. Fire warmed the poor stote, enhancing its power. One of the survivors reached toward it. Another gnashed their teeth. Without a word, you pulled the stote away from the fire and left. That did seem a bit spooky. So it might be dangerous to do the fire thing. The trees seemed to close in around you. There's a chill mist ascended. In the distance, you could hear the clinking of metal and stone. A hobbled figure stood on your path. That was the prospector! Oh, hi prospector. All right, prospector. What do we got here? Oh, this guy. Oh, this guy here. So how did you kill that before? Because it can't be perished.  I don't remember what the pliers do. I'm sure we'll find out one day. A pack mule. Whoa. Interesting. Put this here. Uh-oh. Ah, the adder. Put this guy down. Let's do this. But he's got an adder, too, which is immediately going to kill my wolf. But we'll do some takesies, you know? Whoa. Whoa, whoa, whoa, whoa, whoa. That's sick. Dagnabbit, my mule! A serpent perhaps more deadly than man. What the heck? Wait, whoa. So we have another cat. We have elk. Frog. Uh, there's nothing else that we can really do. Did I neglect to mention overkill damage? Excess damage is not wasted. It carries over to the card behind the mangled corpse of the victim. Lucky for you. Oh. I guess I shouldn't really have done that, should I? Because I already have two. I could have pulled another card. But he's doing the prospector again? Easy boss. The mules key. Oh, yeah. Now the mule I really got. Might as well tip the scales. I hope you don't think it would be that easy. Ah, we have to do it twice. There's gold in them cards. Whoa! Whoa! Whoa! Gold. I've struck gold. Okay, Christy. What do I do with these? There's nowhere for the card to be played. Bloodhound? Whoa. So, I mean, I don't get ahead of yourself if you need to draw a card first. Ah, yes. Let's get this guy.  Just a little bit of damage. Oh, wait. Why did I do that? I should have put the cat down. Because the cat can't. Oh, wait. I can't sacrifice. Let's do... Yeah, it seems good. Let's take this guy again. Let's... Well, that's all we can do there. You're at a hem. Wait. Why didn't he take any damage? Oh, so he can't... I get it. Well, I've already played it. So, can't really do anything. A wolf bar. Battle had taken the toll on you. Your supply of creatures was exhausted. Starvation began to set in. Uh-oh. Whoa, starvation. Okay. Let's do an elk. Why is he not dead yet? Come on. Jesus. Uh-oh. Uh-oh, this is not good. This is not good. Uh-oh. That's the game. I can't do anything. I don't have anything to do. So that was, uh... Not ideal. This isn't purgatory. Tough. You may think of it that way. Though you may think of it that way. Before you expire, I must ask you a favor. I would like a memento. Your very own death card. It's quite plain at the moment, isn't it? We will work together to amend that.  Here's some cards from your mediocre deck. We can put them to good use. Please choose a card to draw the cost from. Cost of two blood from the river snapper. Uh-huh. Add another. This time I'll reuse its power and health, the numbers. Okay, well, I mean, I guess it doesn't really matter. Now choose a card from which will extract the sigils. A sigil of many lives from the cat. I never did ask you your name. There is now but one final matter. The portrait. Ah, the portrait. Are you ready? Ah, thank you. So glad you got that. So glad. Here we go again. Another challenger. Perhaps it is time. Perhaps you can understand bones. The resource for opossum costs two bones. You gain a bone when one of your creatures perishes for any reason. Interesting, okay? From the death of your creature, you've gained a bone. You will not lose this until it is spent, or the battle ends. So I need, I need two bones. There's the thing. Whoa, boy. Okay, well, what do I have here? Ah, the bullfrog. I should have done that. I should have done that at all. That's okay. Squirtle me, boy. There we go. Two things on there. Got more bones. Damn it, why did I do that? I should have stuffed one in it. There we are. Well, I never thought that I would like a card game this much. How brutal of you.  However, in my game, such feats are rewarded. To be precise, a tooth to keep from each extra damage dealt. The trapper may be interested in your spoils. Damn. All right. Well, I am going to end this here. I like this game a lot, depending on how you guys like this for the video. There may or may not be more videos, but I definitely would like to play this on stream, regardless of what happens. But if you guys are down and want to see some more, let me know and we can do that. Yeah, we've never done a like goal. I just want this series to continue and more of these. Let's get 10,000 likes on here and I'll do another video just to see, you know? So yeah, that was fun. I really like that a lot. So thank you guys so much for watching. Hope you enjoyed. If you did, make sure to slap that like button right in the face. And I will see you guys in the next video. Love you all. Stay cranky. Bye.


All right, this works much better, at least for now. Okay, everyone should be able to see this. Hopefully, yes, awesome. Yep. Cool, all right, give me a moment. We're gonna give folks a few, a minute or two to join. Apologies for the delay, we had Zoom issues. Okay, do the music stop? There shouldn't be any music? There should be no music. Since it's gonna take like five of us to replace Amy, what tasks do you wanna assign to me for these, since I'm kind of available? That's a really good question, because I know. So on this one, you're gonna actually open up the votes. You and I are gonna talk about like how, like after this meeting, we are going to do like the votes for like over in Sandbox, so. Gotcha. With that. Okay. I'm gonna go ahead and drop camera and good to see everybody, hurry up. All right, everyone. Hello, today is April 9th, it's our Sandbox meeting. We're gonna go ahead and get started. I'm gonna apologize because I have lost the ability to see chat, so as I discover it, I will follow along if someone could help moderate for me. That would be great. So let's talk about Kairos. Is there a TOC member who has looked at this project and would like to start our discussion on it? Yes, no? Okay. But from the tag runtime perspective, we looked at it, I think maybe if you can scroll down, I think we already said that it was okay to. Yep. Apply for it, Sandbox. Okay. Do we have any other questions around Kairos? So I think one of the events on the web I mean, earlier than one of the comments that it's on board for TOC discussions or distributions more generally, but flat guy is already in the due diligence process. And I think we'd agree that we were kind of okay with that. So I really don't see why not. Kairos. Okay. So are we good to move Kairos to a vote then? Good with tag runtime. This is a project that allows you to create distribution. So there's some tooling around that. So not necessarily the same as flat car, but similar, right? But not necessarily the same, but. Yep. I think I'm definitely in favor to go for what resembles for Kairos. I think this might be a good opportunity for us to clarify TOC position on operating systems and distributions. And I think sandbox is going to be a good position for us to observe how it's doing and what is the community feedback on it as well. Yep. Great. Others, there's Dems. Yeah, plus one from me. I think one of the things that we were looking for this one was licensing issues of some sort, but it looks like they are clean. They are able to generate from many different existing operating systems. So from that point of view, they are a layer above the operating system itself. So I think, yeah, we should give them a shot. All right, yeah. Let's move Kairos to a vote. Amy and George, sound good? Awesome. All right, connects. Anyone want to start our conversation on connects? This project is returning, I think, because we've had a lot of discussion on them already. And the last review, we had asked them to talk to tag network and straighten out the issue of whether we want RPC projects within the CNCF. And so Lynn, I think, did you talk to them? Anyway, from the notes, it says that tag network was happy to accept them into tag network as a sandbox project. Yeah, I'm looking through sounds like, well, this is Nick Jackson commented on it. So we do have a recommendation from tag network then. Same thing, yep. Okay, so we've talked about this project in the past and I think the TOC had some, we've already had some conversations around precedence for technology. And so I think that we're all in alignment that this one can probably just move to a vote at this point, other TOC members. All right, cool. I think there is a discussion to be had with projects that are related to similar technologies within the ecosystem, but then choosing to have their own projects. So this is definitely they have, they have some association with your RPC and might be within the same sub ecosystem outside. And I think this is going to be the case for our next project, which is going to be Cuban, which they decided, instead of actually going with CubeSpray, they decided to have their kind of own product. And definitely this is addressed in both yours. I think the general thread here is that it is easier for community members to create their own kind of mini product, a version of a product, because it seems to be quite difficult to integrate with existing projects in their community and road map as well. So I think there's like perhaps a higher, like a deeper conversation we need to have of what we can do with these projects. I can definitely associate or join a different project which already exists within ecosystem rather than create their own mini version event. So let's, I agree that that conversation needs to happen. Let's, so connect, we'll move to a vote. Let's talk about Cubion because this is really where that conversation started. So Cubion was a project that we previously looked at and we asked the project to have a conversation with CubeSpray because it seemed very related. We thought it could be within scope. They have since provided us with some additional information. I think it's this one, yeah, this comment that provides a little bit more of like a comparison and a contrast within the ecosystem against projects like Strimsy and CubeSpray, how Cubion and CubeSpray are related but with separate focuses and separate functionality. But one does complement the other. They do work together with some, I'm trying to remember, where is it? With some differences between the two of them. So for this one, I think the project has made a reasonable case as to why they should not be included within CubeSpray. And I think that makes sense. Other TOC members, what do you think? And tag leads and chairs, what is your perspective, Dems? Yeah, I think it is good to have them separate as long as they are working together for sure. I think there was some conversation around like, can you replace CubeSpray with something else as well and give an option to the folks? I think they were fine with it, I guess, going that route as well. So overall, I think within the, Kate, Sigs, it might not fit. So it's better to have it here in the sandbox for sure. Okay, Katie and then Erin. My additional comment here is that considering how engaged they are throughout this application process, very much in favor of having them as a sandbox project because they definitely seem to be having a very clear vision for the project and a very clear differentiation between QB, Q-E-N. I don't know how to say that correctly and CubeSpray as well. So this engagement definitely puts kind of confidence in faith at least in this project as well. I'm moving forward. Yeah, just one more tidbit there is, this is from the Dow Cloud folks and they have been showing up in the Kubernetes community a lot. They were at least 10 to 12 of them in Paris. From that point of view of engagement and I think we should definitely give them a chance. Erin? I don't really think have any additive. The only thing I was gonna say is the separation is good because there are projects that we've unnecessarily grouped together in the past, just based on usage and then that becomes a detriment to them graduating. Spiffy Spire is probably the best example I can think of historically. So plus one to that piece and plus one to their effort in seeing this through. I think it shows a healthy project. Yep, Ricardo? Yeah, I just wanted to add because this was a sanctomy they replied really quickly to all the questions we asked and they were pretty clear about it, so plus one. Yep, all right. Kudos Cubion for being responsive and preventing the additional detail that we wanted. Erin, your hand is up again? Or still? No, I just didn't lower it, so apologies for that now. No worries. Thank you. All right, so we're gonna move Cubion to a vote. Awesome. Coordinator, anyone take a look at this one? Have comments, insights? Let me scroll down. Go ahead. Oh, unless the tide lays one to take over. I'm happy. Just say my comments after. Ricardo? Yeah, I think they went back and talked to these groups and there's a comment at the bottom that they say that they're okay with, yeah, coordinator should be in the sandbox because we asked them to talk to the WG batch. Okay. Other Ricardo? Yeah, I was just gonna say the same, like the project is actually quite active and yeah, it's important that they stay in touch with the different groups in Kubernetes, not only batch, but also the upcoming serving and accelerator working groups. But I think they fit here, yeah. They've been informed on the expectations for staying involved in those bodies, is that correct? Yeah, I think they even joined already the batch working group session and they discussed it there. So they're all aware of each other. Okay, and one thing I forgot to check is who are the folks from which company or companies? Do we know? Alibaba Cloud. Okay, thank you. It's from Alibaba Cloud, yes. Okay, thank you. Any other discussion and concerns on this project, Katie? So my question was, since it seems to be a scheduling specific tooling, what were their discussion or conversation kind of outlines with SIG scheduling? Either any perhaps consideration to join them or collaborate with them as well? I think that was the point, Katie. They were put in touch with the batch working group of SIG scheduling and they kind of- Oh, okay, so it's Andrew, okay, Farina, cool. Yeah, there were three people from the Kubernetes SIGs that responded on that thread, so we agreed. All right, are we okay to move this one to a vote if there's no further discussion? Sounds good, awesome. Cube Slice, multi-cluster networking for pod-to-pod communication across clusters. Anybody wanna start the conversation while I look for notes and synapses? Looks like tag network, had some recommendations. Hey, I apologize, did you want some, I can give some input on Cube Slice. Yes. I didn't know whether I was allowed to give any comments or whether it was just listening in. You are welcome to provide us your insights and observations. Oh, I apologize. Yeah, so with Cube Slice, I've had quite a good look at the project. We've done some demos with it. I think the project looks really solid. I think it's solving great problem around some multi-cluster, specifically sort of multi-cluster across cloud or hybrid cloud, which is a great benefit to the Kubernetes ecosystem. It also seems to be pretty solidly put together from a technical perspective, also from a security perspective, they've got some good stuff going on there. And they seem to be pretty engaged with us as well to want to kind of drive it forward and build community and make it a community project. So our recommendation is we'd love to see it sandboxed and yeah, we'd be happy to help them with whatever they need. Some additional color from me, at least one of the founders or the startup exec folks, they are in Massachusetts. So I did get a chance to talk to them maybe a year and a half to two years ago and kept in touch with them over a couple of Cube cons. So they have a business for sure, but they want to do this the right way. And they were talking all the right things and some of our folks ended up in, the company's name is Avesha. So all good stuff from me. I'm hearing nice things from them for sure. Okay, Ricardo, go ahead. Yeah, sorry. Go ahead. I think it looks like there's a comment from Josh as well saying that the community files look fine. Yeah, the only comment I had is that I think in one of the comments, Lynn raised a concern about the lack of GitHub activity but actually looking a bit deeper. They have several repos and the operator repo seems to be pre-active and there was a gap on the releases in the last six months of last year but actually this year they picked it up and it's been pre-active. Yeah, they said they skipped one of the releases because they had a major feature change, I think is what the comment was. Katie? Again, I just want to give kudos for very good engagement from the maintainers. I think a similar question to coordinator, is there any perhaps chances or opportunities for them to collaborate with similar clusters as well? I know it's focused on the networking component but might be a good collaboration to have with that group as well. I believe they are doing that already, Katie. I think they are showing up in the different Kubernetes six, though not in like sign networking for sure but the other ones that you were talking about. Kathy? Yeah, can you hear me? I just... Okay, I have gone through this project. I think it's a useful feature. Yeah, it's set up multiple virtual network domains for different tenants and different workers. So the slice mechanism, I think it's very useful. Okay. Nick? Well, yeah, I just wanted to add about the releases. I did give them a recommendation that even if they don't have a major feature release, they should try to create and cut regular release security patch releases. And they did say that they were going to start implementing that. That is kind of a like a weekly release or something which will just kind of help things whilst they're working on big features. Yeah, and those will eventually be requirements for them to move to incubation. So they've got a little bit of time but definitely worthwhile to give them a heads up on that now. Okay, thank you. To UC members, do we have enough information to move this project to a vote for inclusion? Yes? Yes. Awesome. All right. Next up, the Starrocks. Anybody want to start the conversation on this one? This one I think we're probably going to end up deferring because it looks like there are some open questions around licensing and it's already a Linux foundation thing but the trade, but the owning company doesn't appear to be in there or something. So what we can do is we can defer this to CNCF staff to let us know if there's anything potentially problematic with this before we spend a significant amount of time reviewing the project. How does that sound for two UC members? And also I took a look at actually the project itself is safety but the roadmap is out of date. Also no presentation to the tech storage yet. But technically I think it might be a good addition to the ecosystem because it's a database project. Okay, so Amy? I'm not sure exactly what we're supposed to do here. Like I believe that the roadmap thing we should update but like it's unclear what the request is. So for us, I think based off of the conversation that's been going on just on the issue regarding the licensing is just clarity that there aren't any license issues or conflicts associated with the project. It's already a Linux foundation project. There is a reference to a company. It's unclear how that is this just older documentation that needs to be cleaned up or is there something else that needs to be closed out before we should start looking at incorporating this project. Licensing stuff set aside, is there any technical reason or information that we are missing that would cause us to defer this? Because what I would like to be able to do is start moving the licensing questions and concerns over to CNCF staff to do as part of the onboarding into CNCF because that's the current process that we have. We can certainly call things out and make them aware and say, hey, this looks weird. But if that is the only reason for deferring a project, I would prefer that the TOC come to the technical recommendation for inclusion or exclusion, not necessarily contingent on the licensing because that's a whole nother workflow. Second reason is that they don't yet appear to have been a presentation around it to any tag. So we don't have that as a requirement for Sandbox yet. We do ask for it because it does help us in determining whether or not a project is a good fit, is aligned with our principles, aligned with the expectations and best practices of a project in that given domain area. It certainly helps and we have been returning projects back to tags as a result of that. So I had one quick question, which was on the blog post they had when they joined the Linux Foundation, there was something about talking about moving either to LFAI in data or the CNCF and saying that probably they would fit better in the CNCF. But maybe expand a bit on the cloud native part because clearly the operator is part of the cloud native area, but maybe write a little bit more about... Yeah, so there was, so Josh asked this question and they had come back and asked for the definition of cloud native, which we provided, but it seems like the only portion of it is the support for kates and containers through that operator. Geefy, if you're talking, we cannot hear you. Double mute, it's awesome. So licensing things. If the TOC votes on a project and there may or may not be licensing issues and the TOC approves for the project to be, move down part of the CNCF, is the TOC okay if CNCF staff then immediately go, nope, we're not allowing this in because there's too many, the licenses are too hot? Like are you okay with CNCF staff vetoing a TOC vote? So I'm gonna push back on the language there. It's not necessarily that the staff are vetoing it, it's more that the Linux Foundation and CNCF have made a determination that the licenses presented associated with the project are in conflict with the Foundation's charter for acceptance. Functionally the same thing. Yes, yeah, it comes the same. Let's say that that's probably not gonna play well. They're also moving to the public forum. I'm like my concern is by shifting things off the TOC and onto CNCF staff, don't get me wrong, we can do that. It's gonna be accomplishing the same thing. It's just the perception will be different and the perception might be somewhat negative. Right, which is why like, this is why I wanted to ask the question is because in the past, there is an expectation that projects that are in the Foundation have already gone through a licensing review and a license exception process and that the governing board and license committee have already done all of the research that needs to go along with it. And the TOC is providing the decision that it should be included provided those things are resolved. When projects already exist, we don't move to a vote on the project to move levels until that licensing check has already occurred and the governing board is given their sign off on it. We have not run into a situation where the governing board has said no for a project that already exists in the Foundation. So while the TOC might say that this is a great idea and we should include it, ultimately if there is a licensing conflict, that's not for us to override. Dimms and then Kevin. So I have a feeling that if we should do the thing beforehand, a license check and copyright check kind of thing, like if we'll put them in another bucket and let the CNCF staff come back to us before we look at it deeper. But just from the comments there about CNCF, sorry, cloud native definition, I don't think we should be entertaining them at this point, but I don't know if you want to make the decision now or differ for coming back with additional information. So let me go to Kevin and then I'll come back to that part, Kevin. Yeah, I just want to check because in the process, like TOC voting is the last step. Once we vote and it got passed, it's likely the CNCF staff is going to share the result to everyone. So we really need to check the license thing before we go into a new vote. Another thing is that whether we should kind of point out all the relevant questions. For example, checking license thing as well as asking for deeper collection connection with the cloud native where we go back after the license check passed. This is where we need to double check, I think. Okay. All right, so let me recap. TOC would like to have CNCF perform a cursory licensing review of all sandbox applications before they are placed in the upcoming queue for the TOC to review and make a decision or move to a vote on, is that correct? Emily, I don't even want to say that in the sense that it's okay for us to go through this process and see something and flag them for the CNCF staff to look at. Okay. Erin? Wouldn't it be nice if that was automated dims and it doesn't even come into our queue if it has that? I'm just thinking in terms of our ability to scale. Like if there are checks that can be done prior to it hitting the pipeline here. Right, I think of it the same way we think about like, hey, we should send it to the tag, right? Okay, Katie? That was precisely my comment. I think we should engage the legal committee in the same way we engage the tags. And if we think that requires an extra review from them, then we just engage them. At the same time, we cannot expect for them to do this for every single project applying for sandbox, but I think at least engaging them on this kid breakings basis will help us. Okay. So I'm hearing if in the course of our review, we find a potential licensing question associated with a project that we are going to request, we are going to defer the project from review, we're gonna request staff take a look at it. All right, Duffy? I think that would be a fine step forward. However, I do think that it is absolutely possible for legal to have some automation that describes like low hanging fruit that they could actually, that they could speak to that would be useful in every review. All right. I think we talked about the licensing portion on this one a lot. Nikita and I will take an action to have the conversation with staff to make sure that we're all on the same page for how this should work. So setting aside the licensing portion for Starrocks, there is an open question on how the project aligns with the definition of cloud native and whether or not it actually constitutes a cloud native project by our definition. Note the TOC definition on the repost on these to be updated from the governing board approved definition. That being said, given all of this, and it seems to be that the only cloud native specific ad that this has is its relation to Kubernetes and containers through the case operator. Is this sufficient for us to consider inclusion or exclusion in the CNCF? And do we have any other questions for the project that would prevent us from making a decision to move it to a vote? Do we have any other projects that were operators and we accepted them within Sunbox? Because for me here, I would say it really depends on the end user engagement. And if they would, I mean, it seems like a product which one of the installation options is for a case operator and management process can be on a Kubernetes cluster. So for me, being a case operator sometimes is not sufficient. But this is where it's very blurred. Like if we had any other projects within the same kind of thing, kind of work. We said no to operators selves. The framework is part of the CNCF but not the operators themselves. That's been our standard in the past. It's also the discussion we had around plugins for VS code. I think we ended up on the same kind of trajectory for standardizing a yes or no, but we can always revisit that if people feel like they need to be included. Correct. And to Ricardo's point in chat, Stremzi is an operator. Now that was accepted into the CNCF, not with this TOC, but with the prior one. So there is some precedence for including it but that was also, and I don't remember the timeframe associated with it. That was also at a time where we were much earlier on in the CNCF than we currently are today. This particular project, StarRox, is more than just the case operator. The case operator though is the only connection it seems to be into the cloud native ecosystem. It is still a database, an analytics database. Dems. Duffy, I know your hand is up but I'm not sure if you have a follow up. Okay, Dems. So they still haven't talked to tag storage. So we should put them in that bucket and revisit. Okay. Do I have a TOC member that's gonna volunteer to summarize what we expect the project to do before we can rediscuss and bring it back for a decision at the next sandbox meeting? Duffy. Cool. Thank you, Duffy. If you could go on the issue and assign it to yourself, that would be great. Okay, next. Cartography. Anyone wanna start with this? This self-maintaining map of your infrastructure. Anyone? Hey guys, hey, this is Lee. I just, hey, I was just taking a look at the project and cool project. It does have a significant dependent, well, I shouldn't say significant, but it has required dependency on Neo4j as its database. And the licensing around Neo4j, well, it is not in alignment with the... It's a spin dude, but they just shot down. Yes, sir. And so, and so, I don't know how much that came through. Anyway, there's one to open up a question around the, its dependencies and the licensing of its dependencies, specifically Neo4j. I think it's a good call out. Others? I guess, as long as they are using Neo4j as an external dependency, it seems okay, unless they are making some changes which will cause issues. Yep, I believe, right, I should be more intelligent about this, raise it better. I'll try to go look. I don't know that it was just a copy left thing. It was more like a point of usage thing, such that if anyone were to use Neo4j in a production environment, there's, I guess I'm speaking out of ignorance, just out of an old memory from a couple of years ago that I thought that there was a purchasing requirement or they were, yeah. Found it, I'll paste it in text. Thank you. Okay, so there is a concern on the impact of the Neo4j dependency on the project being accepted into the ecosystem. Is there any concerns associated with its cloud native fit, its capacity to be a viable project in the ecosystem or any other concerns or considerations associated with this project? I wish Matt was here. He would have allowed this one, Matt Young to watch for it. It has some cool applications for sure.  So from that point of view, you know, there were two or three examples that they pointed out which were really nice to see. So I have a feeling that we should do something like this, but yeah, Neo4j is the question there. Yeah, I don't think that we have very many projects in the ecosystem that actually fulfill this particular set of use cases. I think this is one of the things that we've talked about wanting for a while but not necessarily very clear and articulating what that want actually is. So I think this would be nice. It's also been around for a long period of time. So I think it's in a healthy position for acceptance to Sandbox and might move quickly to incubation afterwards. So for the licensing portion of it, is this something that we would like to engage staff on to help us understand any potential gotchas in accepting this project or at least moving it to a vote? So far we don't have a requirement that an end user of a CNCR project has to be, I don't know, how do we have it returned on that they should be able to use it without using any other license? I think that's probably a reasonable expectation, Erin. Yeah, I think it's a reasonable expectation, but I don't know that we actually have that documented. I think we assume that dim. So I think it's a great thing to point out that we need to improve in the documentation. I did wanna ask separately because it is a mature project, would they be better off actually applying to incubation instead of just going through the paces of Sandbox and then incubation? Or do we feel like these things that we're notating are significant enough that it should stay in Sandbox for a limited time? Good question. Nothing would stop us from having them move into Sandbox once all the licensing questions are resolved and then they can get to a point where they feel they're ready for incubation because the project has been around for a while, it's fairly robust. I've not looked at it against the incubation criteria and I'm sure the project would like to be able to do that especially since we recently clarified that. They could move fairly quickly. Ricardo, your hand was up. Yeah, I was just gonna add, I had a similar feeling when looking at it and maybe one way we can do it is just go for a vote now for Sandbox but still request an updated presentation to attack to also clarify what could be missing for incubation so that they could consider applying for incubation right after but we could sort out onboarding things in advance. Okay, so here's, this is what I'm hearing and I wanna just double check this. We would like to have the CNCF take a look at the licensing associated with the project specifically to Neo4j to ensure that there isn't any conflicts that would prevent us from accepting it into the CNCF provided that there are no conflicts. This project should be okay to move forward to a vote with a recommendation that they also present to tag security or do a refresh presentation to tag security and consider applying to incubation. Did I get that right? Dims, you're off mute. Yeah, sounds good. Okay, is there a- The only other thing I would add is it doesn't need to come to like we can do async vote on it when it is ready. Yep, is there a TUC member that would like to assign themselves and put that comment in there so that we can have staff appropriately engaged? It's assigned today I think right now. Someone else can assign. I don't think Dave is here today. Otherwise I can take it, yeah. Okay, Ricardo, if you are up for doing that, go for it. Yes? Yes, yeah. Awesome, okay. Next up, Radius, open source cloud native application platform for on-prem and cloud. Anybody take a look at this project? I have, it's quite an interesting project in terms of refocusing kind of the CNCF landscape on what it means to have an application and what it means to be a developer in the ecosystem. And I think it has a lot of potential. And I do know it has quite a bit of interest. So as far as like identifying healthy communities and momentum, I think it hits the bar on those. Yep. Karina? So what Aaron said, the only thing I wanted to at least raise is that currently it supports Terraform and Bicep both are not, well, we know Terraform, but Bicep is also an Azure project. I don't see anything right now in the roadmap for a non-proprietary project for creating resources, but I think that's just something that could be addressed in their roadmap, but I think it's a very interesting project and we liked it in tag app delivery. Kathy? This looks like a very large project. It helps complicated applications to automatically run. Deploy run on the scale. So it looks like it can combine multiple projects together, like including KIDA, including Kubernetes and CSI drivers. My question is, because it helps application to deploy run on the scale, right? So it has to define how this, to define the application, it can use YAML or Helm charts. And also, but there are other specifications too. So I'm just wondering. It also mentioned it can use it's home abstraction mail APIs from a tool like Bicep. So I'm just wondering if there are so many different ways of defining application, how should user choose? Yeah, that's my concern. But I think it's a good project. It's an interesting project. Maybe the app delivery team can help us with that, you know? So tag app delivery has already looked at the project, sounds like they're good with it. Regarding the support for proprietary or for proprietary software Terraform and the other one for Azure. In the past, when projects have come and applied and they only have one cloud service provider that they integrate with, we've had them go back and get another one or at least support for two cloud service providers. There should be, we have not accepted a project because it only supports multiple proprietary infrastructure cloud service providers pick your flavor of technology that's proprietary. So I think here it's reasonable for us to ask that they provide a roadmap for integration with other open source projects in this space. However, I don't know that we should withhold their application just because they only do two proprietary ones, Dems. Yeah, I'm good putting it to the vote and going forward. All right, let's move radius to a vote. Q plus, it's a Kubernetes operator to deliver applications as a service for multi-instance and multi-tenancy. Yeah, if you scroll down to the bottom, I think the main concern of one of the first concerns that I ended up looking at was like it's a single person repository. So we might need a little bit more community around that before they come here, I think. Okay, Kathy, your hand is up. Oh, sorry, I think I need to roll on the hand. Okay, I agree, Dems. I think that it's one person is not enough anymore for sandbox projects coming in. We really need a stronger start from a community perspective. There's also some interesting dialogue here around the difference between the enterprise, if I'm understanding that correctly, what the commercial offering is in comparison to Q plus, so a better clarity in distinguishing those and how they plan to manage that, I think it's going to be important. But given that, and given that it is a single maintainer right now and it is a Kubernetes operator, are we okay moving this project to a vote or is this a come back later when you have more people and more maturity? Yeah, I would go for the second one, Emily. Don't want to say no with a vote. It's more demodalizing then. Okay, is there a TUC member that would like to assign themselves to this to provide that expectation back to the project with an estimated timeline or specific milestones that we would like them to achieve before they can reapply? I can do this, Emily. Thank you, Dems. Q plus is going to come back later. Report, Cloud Native Application Orchestrator. Anyone look at this with recommendations. Looks like we've had a few folks comment on the issue. Similarities between three port and radius. Yeah, that's what I was going to bring up is that it is similar to radius. It's also, we're seeing a lot more of these show up in tag app delivery. And so that's the creation of the new working group for application development. Recommendation from the tag is to move this forward. Okay. Well, I had a note here about the project seems pretty young though. It's like a few months old. Unless I'm looking at the wrong place. It also seems like they have only one major contributor. Yeah, go ahead. I was just pulling up my notes on it again. Like you said, it is one major contributor and it's not as active as radius, obviously. Going from the last project could suggest that they go back for community development. But it is, it's still a very interesting project. Yeah, I had the same note. Like it looks very interesting, but maybe come back in a couple of months and we give them pointers on how to build a community. Although in this case, it's not just one. It is just like there are two people working together, Richard and Randall and then someone new just showed up and started contributing. So it's not quite the bus test. So it sounds like we would like the project to be a little bit more mature, have a slightly larger community, but not necessarily significantly larger. We also talked about whether or not they need to have more than one maintainer. And I, Ricardo, I see your comment and chat that would need to be updated if that's the expectation we're going to be setting for projects moving forward and future applications. So building a little bit more of a community around it, bringing in an additional maintainer and a minimum, as well as just a little bit more time to attract more interest, more attention to the project, grow it slightly more. Is that correct? Yeah, I don't think the maintainer one because there are three active contributors here. So I don't think we can get away with that. Okay. I would add one more thing. They seem to have some AWS specific stuff. We should get them to see if they can go beyond one cloud provider. Yes, they should be going beyond one cloud provider. All right. So they should be working beyond one cloud provider. We'd like to see the project a little bit more mature. We'd like to see the community grow slightly more. And then I needed TOC member to assign themselves and provide those recommendations back to the project as milestones for them to return later. Anyone? Okay, I will do this one. All right, we've got six minutes left. Hydra monitoring services made easy, real-time alerts seamless integration with Prometheus and GitHub actions. Do we have someone that can talk to this one? Kathy, I saw that you were assigned. Have you taken a look? Yeah, I have done through this. I think it looks like it's very early for an assignment by outside presentation. It is scoping so that we take it and there's no roadmap information. Yeah, I would suggest it comes back. And they also suggest they present into the tag observability and get the tags feedback. Yeah, I have a few more notes there at the bottom.  Same. Plus one to what Kathy said as well. All right, so sounds like project needs to become more active. There's a licensing question associated with the project. What other items do we need? No roadmap. No roadmap? Tag observability. Yeah, tag observability. All right, presenting to tag observability, getting the feedback. All right, Kathy, since you're assigned, do you want to provide that comment on the issue? Yes, yes, I think of that. OK. Awesome. And that brings us to the bottom of our queue for today. Anything outstanding or missing? Good job, everyone. Yeah. I do want to... Or do you want to raise your hand? Duffy? Do you want to raise one thing, which is that in the new section, maybe this is just me not knowing how to do the thing, but like in the new section, we now have the SpinCube project. And in the existing projects that are going for Sandbox, there is the Watson Cloud project. And they seem to... Seems like Watson Cloud's been in there for quite a while and SpinCube showed up like three weeks ago. And so I think that's raising some heckles. Oh, wasm... Can I just add wasm cloud to the list or...? Wasm cloud is an accepted Sandbox project already, so it's applying for incubation. Oh, OK, that makes more sense. Yeah, wasm cloud is applying for incubation. SpinCube just applied for Sandbox. That makes more sense. OK, anything else? All right. Cool. Thanks, everyone. I will see you all next time. Thank you. Thank you. Thank you. Bye.