Welcome to the First Unitarian Society of Madison. My name is Kelly Crocker and I'm one of the ministers here. Today I'm joined by my colleague, the Reverend Kelly Asperg-Jackson and the worship team of Drew Collins, Linda Warren, Stephen Gregorius and Daniel Carnes. The vision of First Unitarian Society is growing souls, connecting with one another and embodying our UU values in our lives, our community and our world. Immediately following the postlude, we ask you to help keep everyone safe and not linger here in the auditorium or in the building in general, and you're welcome and invited to socialize outside. Kelly and I look forward to greeting you after the service at the Atrium Doors. If you're a parent of a child in our religious exploration program, please remember that the children are picked up out on the strip of lawn near the landmark building. Today, we'd like to bring your attention to our Journey Circles Covenant-Based Small Group Ministry. Registration for this year's Journey Circles begins this weekend, and you can find the registration link and more information about Journey Circles in the news from the red floors on our website. These small groups of 8-10 people meet each month to explore our monthly theme. There are a wonderful way to meet others and get connected here, and we hope you will consider joining one. I invite you now into a moment of silence to center yourselves and bring yourselves fully into this time as we join together once again in community. Some people are used to keeping rules. Don't cross the street when the light is red is only sensible. It turns out that keeping rules isn't the same as keeping covenant, which asks us instead of keeping a bright line to keep our promises. To what have we promised ourselves? To this moment in time and place, to this community and even tenderly interconnected this planet, we promise ourselves to the idea that we are each and all human beings. We promise that there is something moving between us that we cannot tame and cannot measure. The chalice is a reminder that what flame we keep inside us cannot light the way. The light must spill to shine. The thing you must be is yourself. Unadulterated, shedding the willingness to journey alone, as though you are made of something hard and unforgivable. You are human, you belong right here, right now. And together we will chase away the sickness, the secrets, and leave only the open possibility that the future is a space for growth. And I invite you now to join together in our words of affirmation as we light our chalice. For every time we make a mistake and we decide to start again, we light this chalice. For every time we are lonely and we let someone be our friend, we light this chalice. For every time we are disappointed and we choose to hope we light this chalice. Rise up, O flame, by thy light glow to us beauty vision. Please sing with me our opening hymn number 324 where my free spirit onward leads. Those worshiping with us in person are invited to hum. There is a story from the Buddhist tradition about a certain person who was walking through the jungle one day and as he walked through the jungle he spied in the distance a tiger. Now obviously that was a very dangerous thing to see even a long way away so he turned around and ran in the opposite direction and he was running from that tiger when he came to the edge of a cliff and fell. He didn't fall all the way down though. He was able to grab a hold of a branch just below the lip of the cliff. It's a good thing too because it was a long way down. Now as he was hanging from that branch he looked up and he saw that the tiger that he'd seen over there before had come right up to the edge of the cliff. It was licking its lips excited about the prospect that it might get an easy meal. He looked down below far, far down below and not only was it a long way to fall but wouldn't you know it there was another tiger down there. So here he was hanging by this branch and as he was thinking about what he wanted to do two little mice very small ones came out of two little holes in the cliff face. They started to nibble on that branch that he was hanging from. Well that was quite a predicament wasn't it? So he was hanging by this branch a tiger above him, tiger below him, two mice nibbling at it. He noticed something else right beside the branch. Just a little bit further up there was a red ripe strawberry. It was so beautiful and he reached up with as much strength as he could muster and he picked that strawberry and he ate it. Now as good Unitarian Universalists we might think a few different things about this problem that the man in the story was facing and how we might like to address his various needs and this strange and unfortunate circumstance he was in. Maybe we could get a very tall ladder and climb up there and help him down off of that cliff and maybe we could gently restrain the two tigers and make sure that they didn't menace him quite so much anymore and maybe carefully delicately we could find new and better homes for those two mice but whatever it might be that we would want to do to help this poor soul and this strange and difficult predicament it begins it begins with the taste of the strawberry how sweet how fresh it was even as he was hanging by that branch. I invite you now into this time of giving and receiving where we give freely and generously to this offering which sustains and strengthens our community here as well as our outreach offering recipient and this week's offering is shared with RISE or the respite center the respite center provides emergency childcare and respite for children ages birth through 14 parent support and crisis counseling seven days a week in addition to quality child care the respite center helps parents and caregivers access important resources to help support and stabilize their family so you'll see on the screen that you can donate directly from our website fussmedicine.org you will also see our text to give information there there are also offering baskets outside all of the doors of the auditorium and we thank you for your generosity and your faith in this life we create together. She wanted to find God that's how she explained her decision to her family they were perplexed and concerned it wasn't a choice that had made much sense to them they were Catholics yes and had raised her in the church but they were not a particularly pious family and now this shy bookish daughter of theirs who rarely disagreed with her parents or went against their will made it clear to them that she was adamant teenagers are notoriously willful but this was no passing whim for the young woman her mind was set and seeing this her parents decided the best thing they could do was to get out of her way so it was that in the fall of 1962 Karen Armstrong entered a convent of the society of the holy child Jesus embarking on a spiritual quest to become a nun you may recognize the name Karen Armstrong she is a contemporary scholar of comparative religion her books on Islam and its relationship to Judaism and Christianity have been quite successful and she is a sought-after public lecturer and on television and radio but just as she was entering adulthood Karen chose for herself a path with rather a different destination in mind as she put it to lose my adolescent self in the infinite and ultimately satisfying mystery that we call God for the next seven years of her life Karen Armstrong would work and study and pray in pursuit of a holy life and a spiritual communion with God she advanced from postulate to novice to professed none she made the walls of the convent and the strict order of its rules and expectations into her world following their rhythm and flow she walked the path for as long as she could but try as she might she couldn't find God there so Karen left the society not in anger or bitterness but with frustration at herself and a great deal of uncertainty about her future outside the boundaries of religious life strange new challenges awaited her in the first years in the convent she had been almost completely cut off from the outside world when the Cuban missile crisis broke out soon after she joined the society her superiors told her and their other charges that the world was teetering on the brink of nuclear war they neglected to inform them when the crisis had passed however so Karen and the other young women lived through several weeks of terrifying uncertainty before the mistake was corrected when she became a full-fledged nun Karen's work required her to study and teach which took her outside of the convent walls but she remained set apart and aloof from the wider world then she left her order and the world seemed to come rushing in again from 1962 to 1969 she had missed seven years of politics art and culture almost nothing made sense to her in this new secular world newspapers were a confusing jumble of unfamiliar names and problems no longer a nun Karen was now just a university student trying to find a place for herself in an alien environment at her first college party she tried to fit in and adjust to the strange world she had decided to rejoin the lights seemed too low the music too loud the young men and women too comfortable with with each other's bodies and their own trying to make polite conversation Karen asked another guest what band was playing on the stereo the Beatles of course her friend shot back and then under the dawn of a terrible realization she asked you have heard of the Beatles haven't you now it may be that some of you are so tuned in to the music world that you've never had this exact experience you've never been the only person at the party who's never heard the band on the stereo before but all of us can find some empathy for what that feels like that sense of being so completely out of our element Karen Armstrong had left the strict rigor and discipline of the religious life behind the social and political upheaval of the spring of 1969 she found herself a stranger in her own country a place where she spoke the language but no longer understood the idiom learning to live in this new and different world could not happen overnight it would take many long hours much hard work and much so much discomfort and uncertainty now in the world of amplified sound there is a concept called clipping which you can get from over driving an amplifier when the device gets more voltage from a guitar or other instrument that it was designed to handle the sound becomes distorted the edges of the sound waves if you could see them with your eyes would appear to be clipped instead of moving back and forth smoothly the edges are all flattened out the peaks and the valleys stop rather abruptly becoming blunt the new sound is considered dirtier and more gritty it can only be reached by using the amplifier in a way not quite intended by the manufacturer but it's an effect sought out by some artists in Karen Armstrong's near perfect innocence of the popular culture of 1969 she was almost certainly unaware of Jimi Hendrix and the other pioneers of the age great masters of the electric guitar who had chosen to explore this new sound including clipping and other forms of musical distortion the singer songwriter and guitarist Ani DeFranco titled one of her albums living in clip in reference to an over driven amplifier because of the songs she was playing in the way that she was playing them her amp was spending most of every show handling too much volume and putting out intentionally distorted sound the plight of the over driven amplifier was also a metaphor for living life outside of our comfort zones past the margins of the manufacturer's warranty living in clip means living in uncertain places beyond the limits of what we already know we can do it is far from the easiest sort of way to go through life and in the case of amplifiers and other such things it probably has a negative impact on a lifespan of the appliance it's not easy on us humans either it can be frustrating and it can be dangerous but it is also the only way that we learn joshua four published a book some years ago about his quest to become a world-class player in the field of competitive memory there are in case you didn't know multiple tournaments held each year at the national and international level in which people compete in various contests to prove the speed and accuracy with which they can memorize things like random lists of names or numbers or the order of a deck of playing cards joshua started out with a journalistic interest in the sport and became obsessed with developing his abilities to a competitive level in the course of his training he learned a lot about how to learn one of the key insights was staying out of his comfort zone when we first start to develop a new skill we fumble and make mistakes and even that usually takes a lot of focus over time we become more effective and efficient at the task until finally we reach a level at which we can cruise we've become as good at the skill as we need to be at least for whatever we're doing with it just then and we can keep that performance up more or less automatically the key to actually learning and growing in areas that have already become automatic for us is to push past the point where our autopilot breaks down as for puts it amateur musicians tend to spend their practice time playing music whereas pros tend to work through tedious exercises or focus on difficult parts of pieces similarly the best ice skaters spend more of their practice time trying jumps that they land less often while lesser skaters work more on jumps they've already mastered in other words regular practice simply isn't enough to improve we have to be constantly pushing ourselves beyond where we think our limits lie and then pay attention to how and why we fail it is not easy to push past ourselves push ourselves past what is easy in order to become more and more the people that we wish to be to step willingly into the unknown and uncomfortable is an act of courage there are many places that such courage can come from hunger will give you all the courage you need to steal a loaf of bread anger can make you brave enough to strike back against your tormentor even fear can make you bold enough to propel yourself in the opposite direction the character of aurora munro once said to kurt vagner in 2003 is now largely overlooked superhero film x-men 2 sometimes anger can help you survive her wise observation receives a humble but equally wise response so can faith there's an english language expression that pronounces a curse in the formula of a blessing may you live in interesting times the tradition of the idiom is to present it as a traditional chinese curse but this has no basis in actual fact in english and in other languages sometimes we may choose to present an idea which is useful but uncomfortable as coming from somewhere else conveniently foreign and far away we comfort ourselves a bit with the assurance that the disquieting call is not in fact coming from inside the house but if i tell you friends that we live in interesting times surely there is no one within the sound of my voice who does not have some sense as to what that means dwelling on a planet becoming hotter weirder and less predictable enduring the chaotic disjunctions of late stage capitalism witnessing an ongoing violence against the pretense of democracy and weathering the alienation of a pandemic which now persists largely due to our collective inability as a species to care for each other interesting times indeed last week kelly crocker gifted us with a sermon an epistle really of encouragement for living through and growing through these interesting times that we are all in together she rightly described our contemporary condition as a place that is an endless dance of shadow and light hope and grief that is not a comfortable place our world at this moment is not a comfortable one no but it seems to me to be a little like an amplifier living in clip stretched to the outer margins of what is possible perhaps beyond what is advisable we feel the strain in our relationships in our hopes for the future for ourselves and our children and for some of us in our own bodies and it takes a toll on each of us and all of us in the Hebrew Bible we encounter the character of Jacob the grandson of Abraham a character who spends most of his childhood and early adulthood getting by on luck and wit and a clever trickster like roguishness again and again he faces some danger or some challenge and mostly he escapes by outsmarting his adversary changing or inverting the rules in order to get what he wants even when he has to flee the home of his childhood it is a fate of his own making after he tricks his brother Esau out of his birthright and their father's blessing jacob fears his brother's rage but he seems to do so with a spring in his step like jack of beanstalk climbing and giant slaying fame jacob is never down for very long makes a new fortune and a new family for himself and then he comes time to go home to return to land of his birth and face again his brother whom he cheated for perhaps the first time in his life to confront the real consequences of his actions and experience real discomfort uncertainty and fear the night before he is to meet his brother jacob is attacked by a mysterious figure even in the text itself it is ambivalent the strange assailant is referred to both as a man and as god elsewhere in the bible we see them referenced as an angel but in the story itself they pointedly refuse to reveal their name jacob and the man the god the angel whoever it was wrestle through the night the stranger strikes jacob brutally on his hip marking him in a way he will carry for the rest of his life he will never be exactly the same again but still jacob will not let go of a stranger dawn breaks and they are still wrestling the stranger for whatever personal or mystical reason needs to depart at the onset of day but jacob wounded though he is will not let go though not until his opponent blesses him first and so in order to be released the stranger gives jacob a new name which he will use for the rest of his life israel one who wrestles with god as unitarian universalists we are not waiting on redemption from outside of time we do not look to a god who intervenes in history to save us from the mess that we and other human beings have made our individual understandings of the source of hope and salvation vary some of us know it as god some as the human spirit some of us do not claim to know it by any name at all but if we disagree on this one small point we enjoy a blessed and uncharacteristic agreement on the much greater point of how exactly the world is made whole things get better tears get dried mouths get fed chains get broken by the work of human hands by the individual and collective action of human beings so our faith demands from us that we work for justice because justice isn't coming any other way it falls to us to repair the world just as it did to those who came before us just as it will to those who come after us just as it does to everyone else on earth now as individuals and as a congregation we must continually ask ourselves what comfortable ruts do we need to drag ourselves out of what vital form of justice making do we need to challenge ourselves to undertake the condition of this moment that we are all in together this time of living in clip is the product of circumstances beyond our control but it is subject to our choice whether the result from it shall be noise or music whether we choose to toil burdened by the curse of life in interesting times or to embrace the breath the blessing of life in a world and at a time that needs us karen armstrong spent a long time living in clip it took her most of a decade to make sense of her life after she stopped being a nun there were failed studies failed relationships a failed career a long while spent trying to adjust from the world she left behind to the new world in which she lived but one chance meeting led to another strange opportunity until after many years and disappointments karen found herself wrapped up in the study of god and religion as a scholar of many faiths this time rather than a woman religious of the roman catholic church in that work the work she is still doing karen found some echo of the wholeness she had been searching for in the course of studying and trying to teach what she found in the wisdom of human religion karen found god not the god she had set out originally to find but a source of meaning and purpose in her life nonetheless i invite you to join me now in an attitude of prayer and meditation as i share these words from sandra fees the moment comes when a choice arises a holy moment a decision must be made do i remain as i am or do i risk inching leaping flowing in another direction do i risk what i think i already know and already am do i forfeit my security for the possibility that a simple shift may alter the course of my life even perhaps the life of another i long to let go of all that restrains me so that i might pursue the impossible and surmount the insurmountable to let go of anger to let go of the need to be in control to forgive a friend to forgive myself to refuse what thwarts my spirit to refuse what limits my mind to surrender to what will come to surrender to this holy moment i have let slip away for too long are we where as our chalice is extinguished and offer you this simple charge go and do what your heart demands that you do where you have bread and others hunger give where you have strength and others falter lend where you are lost and others know the way listen where wrong endures yet people still struggle against it hope amen


There we go. Okay, so welcome everyone to the second public forum of the Jones library building committee specific to the all user multi stall restrooms that are planned for the renovated and expanded library. This is a public forum it is not a meeting of the outreach since I do not see a quorum. But I do have with me today, Sharon Sherry from the library director, Craig to Carlo and will Fernandez both from collars our owner project manager. And I am Alex Lefebvre, I am the chair of the Jones library building committee outreach subcommittee. So I see we have some attendees in the audience welcome thank you for coming. This meeting is being recorded but we definitely welcome anyone to raise their hand at any point during the presentation. We're here to answer any questions that we can or take any information that you want to provide. So with that, I'm going to ask Sharon to go ahead and pull up the presentation and we'll get started. Can you see it. I can thank you. And if you can keep an eye on hands that would be amazing. And I don't know that I can do that and share my screen at the same time. Let me see if I can do that. I think I can do that. Yeah, I can do that. Okay. Okay, great. So, welcome. So, go ahead and turn to the next slide. So, the Jones library building committee has agreed to use all user restrooms, all throughout the building so on the garden level are on the entry level off amity street, the second floor and third floor they'll all be single occupant, all user restrooms. And then on the garden level which is the community space is where we would have a all user multi style restroom so what we're really talking about today is that restroom because it's the one that would not be a single user restroom. And so the decision was made sharing you get a little. Yeah, there we go. So the decision was made because all user restrooms have been found to benefit the widest range of people and that includes parents with children of different gender, people with disabilities who may require an accompaniment of an attendant of a different gender as well as gender diverse people. So we still all user restrooms also maximize space and minimize bathroom lines which since we are dealing with a pretty compressed tight space in the library to meet all of the library needs, having a bathroom that maximizes space is really good. And there's a link on this presentation and this presentation is available I think on both the library as well as the town website. There's a, it's actually an architecture firm has done a video called stalled which I think Sharon's going to click on here. And it's just if you're, if you're new to all gender restrooms it's got a lot of information that you can look at in terms of what some other designs look like, you know how they've been implemented why they've been implemented, etc. So it's just a nice little resource to have. So on the next slide. So what is currently being proposed and this is what I said previously so all bathrooms will be all user single occupants on the first second and third floor and then the multi stall. So, this design right here is a preliminary design that was provided by the architects. It was preliminarily approved by the Jones library building committee. The red dotted lines are not wall but could be wall if for some reason we wanted to separate those spaces it allows for it to go back into, you know, sort of gendered restrooms. We are based on the public feedback we've gotten to date, likely asking the architects to come up with a more open design. It doesn't necessarily have people choosing which way to go into, but instead, you know more of an open visible design because we're hearing a lot of people saying, you know, they would be comfortable if there were visibility around security issues. And one of the issues that we deal with at the library, because libraries are for everyone is that we do have people who have addiction, you know, problems that they're dealing with addiction. And so using library bathrooms can often be a place where people might overdose and so we want to be really, really cognizant of making sure that we can keep all of our patrons safe. And that if someone does overdose that the library staff which is trained on using Narcam is aware that somebody's in the bathroom that they need help and that we can get to them in a quickly manner to make sure that they survive. So that's one of many factors being under consideration as part of the bathroom. And so we had Sharon go to the next slide. So one of the things that we're looking at in terms of the bathroom is the type of stalls. So a standard privacy stall is what you would see in most what we would think of as sort of traditional bathrooms that were installed in the past in public places. There's a divider between the stalls and there's about a 12 inch gap above the floor in between the dividers you can see everybody's feet somebody drops the toilet paper you can see it etc. They're the least expensive to build an install but they're also the least private. They also have the least amount of security concerns because if somebody has overdosed passed out, you know, it doesn't even have to be an addiction right it could be somebody who's passed out for another reason they're really easy to see a patron can report back to staff that somebody's on the floor. The semi private option has dividers that stop short of the floor, it can be a gap usually between four to eight inches. It's moderately more expensive than the standard privacy, and it offers often a nice balance between people feeling like they have the privacy when you're in an all user restroom, as well as the security concerns of being able to possibly see feet or other issues to make sure that everybody is safe in the bathrooms. And then the third option for doors is maximum privacy. And this is, you know dividers installs extend fully from the floor to the ceiling. To do that code requires a floor drain light fixtures and sprinkler in each stall so as one can imagine that becomes the most expensive of the option because of the additional code requirements for those types of stall. It's the most private, the most expensive but then also creates security concerns about patrons who may be in need of assistance and you may not be able to see or tell. So, go ahead Sharon to the next slide. So these are just a couple of all user multi stall restrooms that have been used in other public spaces and they are included in this just to really get the dialogue going. Some people have used all user multi stall restrooms some people have it and so we thought it was good for people to see sort of other ideas to help with the thinking of what's possible. So this particular design is used at a synagogue. It's a pretty straightforward, you know Florida ceiling maximum privacy, one row of stalls on one side bathrooms on the other. Go ahead Sharon the next. This is a design at a university. So this is a little bit like what our design potentially looks like now. You could necessarily have but you'd have stalls on both sides with a sink in the middle. And so that's offers a slightly different feel and flow a little bit more open than the prior design. And then this is a design actually at an elementary school so this is the most open design where, I mean this is obviously a school hallway but where the sink area would be potentially open out into the public which would allow for, you know, security concerns to be eliminated and what we've heard from some people is they would be more comfortable because it doesn't feel like a closed in space where they might feel uncomfortable using restrooms with people of all genders on the gender spectrum. So those are just three ideas in terms of getting the conversation started. Yep. So the timeline for the decisions that the Jones library building committee which is a town committee needs to make around the bathrooms is here and so the first public forum. We had last Tuesday on January 3. This is our second and final public forum. And then there's a survey that we've started on December 22nd, and it will close on January 15 and we'll in a minute show people how to get to that. That survey is available online but there are also paper copies in the library that people can fill out and complete and put into a box and then those just get manually entered into the survey results. The Jones library building committee and design subcommittee are meeting on January 19 and January 26 at 430 where it's anticipated conversations around the community feedback will be had in those meetings, and then a possible vote is scheduled for February 2 or February 9 in terms of giving final direction to the architects. And then a possible date for us to make any changes to the bathroom. February 9 is the absolute drop dead date. No changes will be made to the bathroom design after that. So we really want to make sure that everybody is filling out surveys and giving us feedback before January 15. Next slide. So the survey has, it's super short, very quick to fill out asks if you've ever used a multi stall all user restroom. If you did, would you like or not like about it. We asked people to vote on the proposed stalls. And then we asked people just generally to share their thoughts about any features design elements that they'd like to see. The last bit is just a couple of demographic questions in terms of age group gender identity. Do you have children are you a caregiver things like that to help us hopefully make sure we're reaching the widest spectrum of community members to have input from everybody. So ways to share your opinion. There's a link to the all user restroom survey. So this is actually available if you go on the Jones library website. There is a link there to the survey. There is, I think also a link sharing if I'm not mistaken if anybody uses a public computer in the library, there's also a link to the survey there. The weekly newsletter that goes out from the Jones library also contains a link so if you're on that weekly newsletter that comes out on the weekend, you'll find a copy of it in there. So, yeah, so this is a survey it's super quick to answer. There are a couple things that are required. But again, like I said, super fast. And then so like we did for the broader open comments at the beginning of this process we've created this padlet. So the padlet has a link to the stalled online. It's got a link to the survey, but then this isn't also a place where people can add their own comments they can rate designs that they like and then they can also actually upload their own pictures. So we have people here who are, you know, three people have rated the different designs they've added their comments keep scrolling down Sharon, they've added their comments. And also of note if you click on any of the pictures, it will actually make them full screen and you can scroll through pictures this way so you're not looking at teeny tiny pictures. So these are just different bathroom designs. I think click the X Sharon. And then if you keep scrolling down you'll see I think some people have added their own. So, you know, these are different things that people have added you know, some somebody wants a sanitary product station which is great somebody included this as an open design and then more people can just Yeah, so it's a nice space to be able to share comments thoughts photos and vote on other ideas. Oh, yep. So go ahead and close out of that. So, X on the top right of the tab, I think, yeah. You need to close out of this to go back to the presentation. Okay, there we go. Thanks. Sorry about that. Okay. And then the info at Jones library.org. Oops, cancel or close. Please. Okay. info Jones library.org so that's the same email that we've been using throughout this process. So folks can send an email to info Jones library.org it's a different way to share information with us about the bathroom thoughts or comments. And then the submit a comment form. You can also click on that link, which is also in the library website. And the thing to know about this is when you enter a comment using the comment form. It doesn't give us your email address. So if you use this form. And you want a response from us we actually can't respond to you because we we don't know who you are so it better to use the info at Jones. If you'd like to respond to something. So I think that is it for yeah. So we've gotten I think about 135 responses so far to the survey. I think we've had I think 20 people go on the padlet and use that. So it feeling feeling good that we're getting a lot of nice conversation a lot of people have a lot of a lot of really great feedback and thoughts about what they'd like to see in the bathroom design and I'm certainly grateful for all of that feedback and people taking time. I think it's really important to encourage people. If you fill out the survey if you do it online, if you could forward it to anyone and everyone you know the more people we get to fill out the survey. You know, the better, the better represented the community is in terms of the conversation and dialogue. So, that's it. I don't know if anyone in the audience has any questions, comments, thoughts, you're welcome to come into these raise your hand if you're interested. Thank you to attendees I'm happy to bring one of you, both of you, either of you, whatever you guys want, we're happy to bring you into the room and it, you know, to have a conversation, I think is really helpful, because there are things that we take for granted and, or things that we may not be thinking about. Or there's always the thing, yeah, we take for granted that people, you know, are watching meetings and know the thought process so yeah. Okay, seeing no hands. I see that I did exactly 17 minutes which is what the last before I did it 17 minutes as well. So, these are recorded they can be shared there on the town website under recordings I think so. I appreciate those of you who showed up for the, the public forum. Hope you'll complete the survey if you haven't hope you'll pass it along to others. And we look forward to hearing from everybody. Well, thank you Colliers for coming yet again. Appreciate your time. Certainly, and I just want to say, fantastic job, filing all this information and making it accessible to everyone. That's what we do or try. All right. Thank you everybody. Good night everyone. Good night.


What's happening, Magnus Sacks? So apparently Matthew McConaughey has reacted to Star Wars, teaser trailer number two, and all its epicness. So let's see what Mr. McConaughey had to say. I'm a rhyming motherfucker, nigga. Let's do this. That's an interstellar footage. I haven't seen an interstellar yet, I still gotta see it, y'all. I heard it was really good. They're totally pieced together good. The way he's looking. Mr. Repsion. His reaction to the first start in every single shot. Go check out Mr. Repsion. His reaction to the trailer. Almost exact same.  It touched Mr. Repsion very deeply because he, the big car of his childhood, I think he said. Anyway, so that was funny. Post your comments down below. Let me know what you think. One million subscribers. Woo!


Russell Fork Pharmacy is your locally owned pharmacy offering fast, friendly service with competitive prices and free delivery. Call<PHONE_NUMBER>. Visit RussellForkPharmacy.com and download our free mobile app for refill requests and more. The Pot County Fiscal Court took action at Tuesday's meeting to declare the county will now be a Second Amendment Sanctuary. Hundreds of people packed into the Fiscal Court Room to hear the reading of the resolution, which states that the county will officially oppose any gun laws which may run contrary to the Second Amendment of the U.S. Constitution. The Pot County Fiscal Court hereby declares its attempt to oppose any infringement on the right of law bodies citizens to keep their arms. We, the people of Pot County, Kentucky, to this resolution hereby declare a rise. Our free delivery is guaranteed by the Constitution of the United States of America. We can serve hand. This is the 7th day of January 2020 and the resolution is adopted. The resolution received universal support at the meeting from officials and those in the audience. The way the Constitution is right now, why are we going to water down the Second Amendment? What's next? We're going to water down the freedom of religion. We like to go to church every third of Sunday, the second month of the year. And then you water down freedom of press, freedom of speech. We can't start watering down amendments because I know I have buddies that get there alive for this and for what's going on here. I don't see how any of us can stand down and stand by watching me take it. Too many people's given their lives, too many people still today are being employed for the same reason. We all dance around the, we all dance around the true purpose of the Second Amendment. It's not for un-deer and it's really not for protecting a house from a wild camera. It's for protecting yourself against those people who want to pass these hot laws. It is a symbolic resolution that says that we're going to oppose any efforts to undermine the rights of these folks here. You know, when you see people running for president, the first thing they say is we're going to take your guns away. Well, these people here tonight are law-abiding citizens and, you know, they came out, this was a huge crowd. It was a peaceful assembly and people were concerned over this and they have a right to be. When you see a complete shift in Virginia's government to the point where law-abiding citizens are at risk of being felons overnight simply because of a change in the law, gun confiscation, gun bans, gun registration, to me those are clear violations of individual Second Amendment rights in this court and as you can see a lot of people in this county don't support that. I know how the state of Virginia's having the big problem that they've got right now trying to take your guns.  I believe in the hunting and the sporting part of it and I still say the biggest danger with the guns is the criminals that's got the guns. It's not the guns fault, it's the criminals fault, you know. The members of Pott County's legislative delegation also joined in the meeting via a live video link from Frankfurt. On the same night as Pott County, the MacGuffin County Fiscal Court also adopted a second amendment sanctuary resolution. Well, I think through the representation that Eastern Kentucky and I think most of the Commonwealth with all the rural counties pretty much support for this passing, and I think right now there's about 33 that's already passed it, that this will have a head influence on whether or not they pass any type of legislation regarding gun controls or anything that might have been Next up in Eastern Kentucky, Floyd County is expected to consider its own second amendment sanctuary resolution.


presenters. This was my original talk title, which is composing project archetypes with SPT auto plugins. I also wasn't real happy with my title, and I'd like to change it. I had some feedback suggesting that, okay, great, archetype with plugins, why do I need to do that? So for the sake of explicit motivation, I'm going to rename it right now to combating multiple build maintenance hell with archetype auto plugins. Does anybody know what auto plugins are? Okay. So what is multiple build maintenance hell? It's the new term that I've been working on. It's kind of loosely defined, but it is, it occurs when you have very limited visibility and control over many project builds to the point where you feel paralyzed to maintaining any kind of consistency across your projects. This is why I asked like who's got so many SPT projects? And by visibility, I'm talking about what libraries are we using across all of our projects. Do we know what versions are we using? What plugins are we using in our builds and versions of those two? By control, I'm talking about how easy is it to move these projects to whatever we decide we're going to be using for like what scala version, what version of our libraries? And we want consistency for if for nothing else just to minimize the cost of context switching, right? When we go from one project to the other, we have to have this whole other set of libraries we're using and versions we have to be aware of different bugs that may exist in other versions, things like that. So to illustrate how we might get into multiple build maintenance hell, let's imagine we're starting a company together and we're going to build a service oriented architecture kind of platform, a bunch of services. And we decide that our services are going to be built with scala, obviously, ACCA and Spray. So we get started and we create our first service. It's an SPT project. Let's call it service A. And we start by defining our plugins that SPT, we're going to define our SPT project. And we know we want SPT native package because we want to be able to generate deployable artifacts. And we of course need to use scala form so that we can actually have a coding standard. And then we have to define our build that SPT, which will look something like this. We have all of our, we have our scala version declared our library dependencies. So great, we got our first project ready to go. So we get it in production. We, oh, that's the soundchecked. Apparently there's a soundcheck going on upstairs. My theme music, thank you. So I'll try to talk a little louder. Okay, so we've got one service, we have another service to our platform service B. What do we do? We copy and paste project A, right? We make a few changes. Doesn't make much sense to invest in our build our infrastructure this time. So we have new version of scala that we go ahead and upgrade to. There's a new version of ACCA and Spray. We don't bother upgrading our first service because it's running. We're kind of not worrying about it right now. But we do also decide that we need some scala style to be enforced by our build because we've been having lots of code reviews that we're spending way too much time arguing about our style. So this process repeats itself a few times. But first, okay, we get the, we do it again. We have another service we're adding to our platform. And this time we decide to change the HTTP client we're using. So we're no longer using dispatch. We're using Spray client. We have a few upgrades to our plugins. We're getting kind of messy. We only have three SPT projects. We have two different versions of scala, three different versions of ACCA and Spray and two different HTTP clients. But still we're just still just talking about three builds. Not a big deal to maintain. Now imagine we hired somebody new and we task them with create our next service. And this new engineer doesn't really know this kind of policy we've implemented by copying, pasting the most recent project. So they just look at our biggest service that's running in production, that's service A. Copy, paste that. Nobody really pays attention during our code reviews because we're all way too busy to worry about build files. So we have a new project that is not enforcing our scala style standard. It is on old versions of plugins, old versions of scala and our dependencies and back on dispatch as our HTTP client. Something we've decided we don't want to use anymore. Still we're only talking about four projects, big deal. But imagine this keeps going and going and going. We get up to 26 projects. We have not just web services but we're also creating libraries and command line applications. At this point you look at these lines and this is a visualization of what our build files might look like. So if you map it to code, we've got all these plugins.sbt files, all these build.sbt files or build.scholars. This is multiple build maintenance hell. This is what I'm talking about. I don't know about you but I don't want to be maintaining all these lines of code in our build files. It's not my idea of fun engineering. So hopefully I've convinced you it's actually a problem. You might not apply to your company if you don't have lots of different build files. It sounds like maybe it applies to you guys. Yeah, okay. Good. I was worried we might be alone. So I forgot to introduce myself. My name is Mark Shockey. I think I skipped over that slide. I work at the Allen Institute for Artificial Intelligence. We're a research institute nonprofit founded by Paul Allen about a year ago. And because of our research institute nature, we got into multiple build maintenance hell really fast. We had projects all the time. And within our first year, we've created, we already have over 52 different sbt projects. We have 18 engineers working on these things and we definitely got into multiple build maintenance hell. But we did come up with a way to deal with it because we felt like we absolutely had to, we'd had no choice. And I think it's safe to say that we are now no longer in multiple build maintenance hell. So for the rest of the talk, I'll be showing you how we designed our solution and what we came up with and specifically how we're using auto plugins. All right. So we decided we needed to solve this problem. We set some goals. The first one is we just want to maximize. We want to get some control over this variance across all of our projects. So how can we be consistent as possible, minimize the number of scholar versions we're using, minimize the different versions of library dependencies, and also making sure that we are enforcing our standards. So we want to minimize the complexity of our builds, which you could measure that by lines of code. We also wanted to be agile and be able to as easily as possible move these projects towards our new, our new standards that we may agree on. So we change our mind about some style that we want to enforce or some formatting change. We don't want that to be too difficult to, to, that we feel paralyzed to be able to make those kinds of changes. We also want to allow for projects to straggle. So sometimes it just doesn't make sense to upgrade a project right away. But when it is time to upgrade a project, we want that to be as easy as possible. So these are our goals. Some other really important considerations that we talked about were some projects are just very similar to others. Obviously all of our web services are going to have a lot in common. But there's also a lot of core settings that are really universal for our organization that we want applied to all of our projects. These are things like formatting and style. We also have a plugin that we've developed that generates, get, commit information as a resource into all of our artifacts so that we can see at runtime what version of code we're running. So these would be what would be considered our universal core settings. So our solutions seem pretty obvious. We've got to write some SBT plugins, right? We're not talking about Maven archetypes we're generating code. We want to be able to leverage SBT and be as flexible as we can. So we decided that these archetype, we wanted to have archetype plugins and that the idea would be that a single version of an archetype should provide these core universal settings that apply to all of our projects. And then on top of that do things like bring in special build settings just for archetypes. So for a web service might be bringing an SBT native package or making some default settings to make it simple to do our standard deployment. For libraries, bringing an SBT release and making it simple to publish libraries. And then also the specific dependencies for archetypes. So library dependencies, this is really what I'm talking about here. So to visualize what I'm talking about, this is what we had for our web services. We have all these lines that really map to plugins.sbt file and build.sbt files. What we want to do is minimize those lines which translate to some lines of code to something that looks more like this. So our plugins should wrap other plugins and bring in whatever dependencies are needed for that particular archetype. Leaving basically our build.sbt files. The goal is to only really have stuff that's really custom to that application. Not something that we can abstract out into an archetype. So that was web services. This shows some of our other archetypes that we have. So web applications, libraries, and command line tools. And if we wanted to say upgrade service A and service D to whatever our latest and greatest version of Scala that we're approved to use within our organization, it should be as simple as just pointing those two projects to the latest and greatest plugin version. That's the idea. And code, this would really, this would look like this. So this is before an archetype plugin will be applied afterwards. We wanted to be that simple. That's our goal. Okay, so we still had to decide how we're going to implement archetype plugins. Oh, it was, okay. So the second line you're talking about, this one. Oh, sorry about that. Yeah. Yes. So enable plugins is I'll get to that. But it's basically new for SBT 0.13.5. It's how you enable an auto plugin. So this is this is actually just copy basic code that we actually have. And so sorry for that distraction. Okay, so we want to implement how are we going to implement these archetype plugins to make our lives easier? Yeah. So for implementing these plugins, we need to figure out how are we going to wrap and depend on other plugins? What's the best way to do that? And obviously, for each of our archetypes, we also want them to bring in our core settings. So what we really want is something that looks like this, where for us, these are the archetypes that we've we extracted out of our set of projects. So we'd love to be able to just have four plugins that we can enable in any project that provides those archetype specific settings. And the the idea is we would also have some auxiliary plugins that we could use to compose our archetype plugins. So each of our archetype plugins would use our our core settings and would bring in some of these other plugins that you can kind of think of them like they're mix mix ends. So even though our library automatically brings in a release plugin which would wrap SPT release, it's there's nothing keeping any of our other projects to mixing in that as well. If they want if like we could have web service, we also want to release as a library of the code for the web service. So we had a choice to make it this was earlier this year and SPT auto plugins weren't really totally baked yet. At least I think it was master candidate stage. So one thing we could do is is just use the plain old SPT plugins that everybody's used to. Who here's written an SPT plugin before? Okay. So in our teams experience we had written a few plugins and we were a little bit intimidated by this idea. We found that the kind of minimal API of the plugin was really forced us to think a lot about adopting our own conventions and you know having to really define some conventions. So if you've ever looked at some of the really popular SPT plugins out there, they all have different ways of doing just something as simple as just applying the default settings and it didn't seem like there really any clear convention how to do this. Fortunately for us, SPT auto plugins had just been released and in case you don't know, auto plugins aren't a specialization of plugins. They're really the new standard going forward for plugins. Starting in SPT 0.13.5. So what are auto plugins? Auto plugins are a really well-defined plugin API. At least I think they're really well-defined, which frees us from needing to worry so much about conventions. But the real killer feature for us, for our use case, is that there is a very specific way now using the auto plugin API to compose plugins and that is done by a method. So this is a partial view of the interface of an auto plugin. There's several other methods, but the only ones that really matter to our use case here are this requires method and the project settings. And the way it works, and I'll show some examples here in a slide or two, is whatever plugins that your auto plugin requires are guaranteed to be enabled for the project that's enabling your plugin before your plugin is enabled. Does that make any sense? And what happens when your plugin is enabled is your project settings that you've declared here will be applied to the project. It's pretty simple. So for our core settings plugin, this is our plugin. Sorry about that. Okay, so for our core settings plugin, this is our plugin that we want really to, yes, you can. Yes, you can. So it requires is specific to auto plugins. You can only use it to require other auto plugins. You can, like I'll show you here, I think in a couple slides, how we're actually bringing in dependencies on other third-party plugins that are not auto plugins. So we can't use requires for that. But we can use requires to kind of build up our own plugin infrastructure really, I think elegantly. Okay, so this is our core settings plugin, which defines our universal settings. So this is enforcing our format standards, our style standards, defining the version of Scala that we expect to be using in all of our projects. And now I know we need to add to this Scala C options. What is it we need? Yes, X fatal warning. So that will be in our next version. Cool. Okay, so this is pretty much all the code that is in our core dependence or core settings auto plugin. So what happens is when we enable this plugin in a project is this is really slow for some reason. So we enable our core settings plugin. So the first thing to have is it says, okay, first go enable my required plugins. So our style plugin and our version injector, this is the thing that injects as a resource or get commit information. Those are applied first and all of their project settings. And then finally, our project settings from this plugin are applied to the project.  So taking this the next step, we have this is our web service. If you can't read that, this is our first archetype plugin that we are going to now use our core settings to compose our web service plugin. So our web service plugin wraps SPT native Packager. I'm sorry, I said that wrong. So our web service plugin requires our core settings and another another plugin, which is our deploy plugin, which is a wrapper around SPT native Packager and applies a bunch of settings that are specific to our organization. It also, our web service plugin uses the SPT revolver plugin. So this is a third, this would be an example of a third party plugin that does not, is not an auto plugin, so we can't require it. And you can see all we're doing is there's an import somewhere in this in this file where we get the revolver object. And it's just like if you looked at their GitHub page, this is how you add the default settings to your project. Well, we just add them to our plugin project settings. Does that make sense? Okay, so when we when we enable the web service plugin, the first thing that happens is we see we go all the way down to the lowest level. The style of versioning plugins are enabled followed by the next level of plugins followed by the project settings in our web service plugin. So you can kind of see how this is like recursively composes your plugins. So we can kind of take take this, we can apply the same pattern to all of our archetypes. So for us, we have these four different types of projects, which is growing, we're starting to do some spark application development. And I imagine we'll have a few more archetypes here pretty soon. We also have a web application archetype, which is a super set of our web service archetype. So it actually requires another archetype plugin. It's really pretty simple to do with auto plugins. How am I doing on time? Okay, so I'm going to just show you what it looks like in the SPT console when we apply these plugins. Okay, so I've got this project is just an empty SPT project. The only thing that's defined is this name. Everything else is commented out. So I don't have to waste your time with me typing. So if I start up SPT, one of the nice new things about SPT 0.13.5 and forward is there is a plugins command, you can type in the console, and it will list you all of the auto plugins that are available. It's pretty cool. And notice that there's four auto plugins already available. That's because SPT itself has been refactored to use auto plugins. And these auto plugins bring in the default settings and there's kind of a gotcha when you're writing your own auto plugins and you want to depend on the default SPT settings, you have to require that the JVM plugin, you have to require the JVM plugin or else your settings could be blown away by SPT just to keep in mind. That is documented. So now what happens when we bring in our auto plugins? So this is a little misleading. It's still the same call to add a plugin to your SPT project, but it's singular. You can actually add with one add SPT plugin. It adds however many auto plugins are discovered in that dependency. So I think I've seen somebody request that it be renamed to add SPT plugins. So let's see what happened. Wow, that shouldn't happen. It's probably been a while since I did that. Okay. So now you'll see there are 10 more plugins. These all came from that one add SPT plugin in our plugins that SPT. And you also see which ones are enabled. And it might be surprising that we have some plugins of ours that are already enabled. And that's because one of the methods that I didn't bother to point out on auto plugin is something called trigger. And you can define auto plugins to be automatically. And I think this is probably why they're called auto. They can be automatically applied to any project as soon as the trigger condition is met. So you override the trigger method, you specify the conditions that need to be met and it'll trigger it. So an example where you'd want this is if you wanted to define a plugin that only if some other plugin is defined then been enabled me automatically. There's all sorts of examples around SPT web for this. This is actually I think what we're using been trade, which is the recommended place to publish to and they are public. So if you wanted to use our archetypes, you're welcome to do so. They probably won't really apply to your organization very well. And that's a really I actually had a slide that was a recipe for how to do this and it included publishing to been trained. I think I got rid of it though. Yeah, for us we the reason for making our core settings plugin triggered automatically is because we want it to apply to all projects even if it doesn't fit into an archetype because this is really enforcing our standards, right? We're trying to be making sure that we're formatting all of our code right and the right style and stuff like that. But for us know the only one that is triggered automatically is our core settings. Okay, I had a couple other things I wanted to show here. So let's complicate things a little bit and make turn this build into a multi project build. Good. Emax bindings work. And I think, okay, so this is going to make this really long too. So reload the project and now you'll see all those auto automatically triggered plugins are now enabled for all those sub projects. But we still don't none of our archetypes are enabled. So let's start enabling some archetypes. So the way to do this in SBT is this enable plugins. That's the whole thing. This is new as a zero out 13.5. And you just pass it a comma delimited series of plugins. You can have as many as you want. So like this is where I saying these other plugins can be considered mix ins because you can if it's a library plugin, you also want to deploy it some for some reason. You could just mix in the deploy plugin by adding it to your enables plugins. All right. So what is interesting here? I probably should have done one at a time, but I think it's probably it's all right. Let's just look at the library plugin, which is here. Notice that it's only enabled in core. It's the only one we enabled for it. But because the library plugin also requires a release plugin, its release is also enabled for core. See how that works? Similarly, because our web app plugin requires our web service plugin, our web app, the web service plugin is enabled for the web app as well. And just to show that we don't have to have an archetype, this other project, the no archetype, still gets all the core settings, and it also gets our deploy plugin enabled. So that's pretty much it. See if I can figure how to get back to my presentation. All right. So I do recommend the SPT docs on the plugins are up to date and they'll recommend use auto plugins. The old plugins are still around, but as far as I know you shouldn't be using them going forward. SPT native packages are just about to release a new rewrite, which is all using auto plugins. There's a new tutorial that just came out about a week ago that is a pretty nice introduction to using auto plugins. And we have open sourced our SPT plugins, our archetype plugins at that repo. So feel free if you want to see how we're doing it. Maybe it can help you get started if you want to do something similar.


I'm Mihaela Konstantinescu, the storyteller for Sardina Systems, a cloud platform company building on OpenStack Kubernetes NSF with zero downtime operations. We at Sardina Systems are thrilled to join the Open Infrastructure Foundation as a founding member. OpenStack is the platform of choice for enterprises wanting to rapidly, reliably and cost-effectively deploy, operate and manage cloud infrastructure. Also, as organizations adopt Kubernetes, the integration and leveraging OpenStack to manage infrastructure, multi-tenancy and authentication, storage and networking shines through a de-enterprise ready solution. We are here to help our operators to address the unique challenges of operating OpenStack Kubernetes NSF at scale and drive down the TCO. We look forward to a great collaboration with the Foundation and the community. Thank you.