This office here, this law office here on East South Cross and Clark Avenue is about three blocks from where I live. So I don't have any traffic jams here. Actually, when I went to the courthouse as commissioner, I had about an eight minute trip to downtown. My mother lives two houses down from me, where I grew up. So this is like a big time my home. And I have always had a firm belief that neighborhoods should not be thrown away. I watched a lot of neighbors move out over the years. And it's a free country. You can go wherever you wanna go and do whatever you wanna do. But as for me, I would like to honor this neighborhood by staying in here, and being loyal to it, and helping it. And not just helping the neighborhood, but creating perhaps an American phenomenon of what I call neighborhood sustainability. Where the neighborhood remains strong across the span of multiple generations. And allows people to come in and be pride filled. In their first year of getting acquainted with the neighborhood as well as in the 50th year of knowing the neighborhood. And so to me, that's why I have stuck here. And I feel the same way about other places around the city and the county as the people that live there, take care of it. Be good to them. Be in tune with your neighbors. We're there until Tommy was about 18 months old when we moved to San Antonio. And then my husband coached at South, no, East Central. East Central, yeah. For one year, and then he went to Harlandale. Harlandale Middle School, and then the High School. So why did you all choose this neighborhood to move into? Well, it wasn't too far from the school. And he didn't wanna be too close, but he didn't wanna be too far. So it was just right, mm-hm. Okay, and it was kind of an outreach of not only St. George Parish, but also of the South, that Denver High Territory you grew up in. I was, I guess, very subliminally influenced by my mother's family, which had played a serious role in the life of the community over the years, the century and a half or so. My father's family, they were sharecroppers in the dustpull of Oklahoma. Very poor. My Atkinson grandfather had a, I believe it was a third grade education. And my Ganslin grandfather, my mother's father, had a degree in mining engineering from MIT. And so it was like a vast, you know. So during World War II, it's probably happened over and over again in many ways across the globe. But certainly here, they met during World War II at Fort Sam. And this was a country boy meeting city girl. Very diverse family experiences. They had two things in common. They loved to dance, and they were good people. I got involved because I had gotten out of high school at St. George High School and had government and all that. And then I went over to St. Philip's College and had Frank Madelow for a teacher over there. So I thought that was, he was impressive. He was totally excited about changing the world for the better. And we oftentimes discussed and reflected on how poorly treated the South side had been over the years. You know, like a century and a half or two. And how the foundation for the city was along the San Antonio River, the missions, all that from the Alamo to Concepcion to San Jose Mission to San Juan de Capistrano to Espada Mission. And how, in contrast with that grand and noble history, there was the reality that the area was not well kept up as it should have been. And now, this is a picture of me surveying the condition of a median, under the County Valley median, when I was 19. So I started out kind of early, and I had a former group called the Youth Pacific Progress. And that was my organization that allowed me to learn how to organize and learn how to undertake projects and make a difference. So let's talk about, now, why do you believe you're the best candidate to be mayor? Well, I think I know the city and the county, not just its history, that too. Which is vastly greater than any of the other candidates. But, I mean, it's not even close. But, you know, those other candidates have their own traits and strengths too. But to know the history of the community is, I think, to know how to best serve it and what it needs. And so, to me, I think that's a big deal. I also think my history of having been both in the Texas House of Representatives for two terms, four years, and the Commission of Court for 16 years at the local level, the state and local experience, is a powerful combination. And there's, other than Ivy Taylor, who has about six years, I think, experienced locally. There's nobody even close, and she's not even close. I have 16, she has six. But, you know, I think that is fundamental to knowing what the priorities should be and how we might best proceed in a world of limited resources and unlimited demands for resources. If you're elected mayor, how do you think you'll be able to help relations or keep a good relationship between City of San Antonio and Bear County? I would say experience and seniority. And having relationships and acquaintanceships, I think those are all positive features of what anybody should have when they enter into a significant public office. For either an insignificant, seemingly entry-level public office is an acquaintancehip with all of the various participants, and I have that pretty well in hand. Do you think things need to be changed in the relationship between the mayor's office and the county? Is there something that you would not bring that isn't there right now? Absolutely. I think, if you think about it, at any given time, this county of 1.9 or so million people, this city of 1.4 to 1.5 million people, has 100,000 people who have either been in our jail or who are on probation, parole, or some kind of criminal justice thing. And the San Antonio Police Department is the primary entity that is checking people into our Bear County jail. It would seem to me that just as we at the county have done reentry efforts to try to make sure they don't come back to the jail, they get a job, they go to work, that they pay their child support, they pay their taxes, they pay their bills, they support their family, that those who are just entering would be qualified as to how they might also not come back. I would call that pre-entry. If the county is doing re-entry, the city should be doing pre-entry.  It is the number one mental health care provider in the county and if the mental health dimension of the incarcerated community is not addressed properly, most of the time they're just going to cycle over and over through our jail. What do you think is the role of the mayor in the city of San Antonio when it comes to these mental health issues? I think the mayor ought to be cognizant for one of who's in the jail because the city in this case is the one primarily placing these people in the jail as they are charged to do. But we ought to be aware that there are certain members within that group that we're checking into the jail from the city that if treated properly and appropriately, might more readily find themselves not back in our jail. 75% of everybody on our channel has already been there before. When you were a commissioner, you took a big stance of trying to prevent recidivism. How could you do that as mayor? What would you do to help keep people from going back into the jail? Well, I think we could initiate a pre-entry program where we try to make sure that people that don't belong in our jail don't go there in the first place. There's some pretty low level stuff that probably deserves a fine and deserves some kind of punishment.  With respect to who gets into the jail, there are just a whole lot of people that are treated the same irrespective of their either great or their very minimal problem that caused them to be there. And so if we don't use more discretion in how we treat them, they're just going to cycle through the jail over and over. Every 400 inmates cost the citizens of Bear County $8 million and we regularly have about almost $4,000, so that's about $80 million a year, year in and year out with a 75% return rate or recidivism rate. You wanted to run for county judge and you lost the Democratic primary. Now you're running for mayor.  Is San Antonio mayor a plan B for you as well? And a plan B for Mike Vary-Allenswell. You know, he had a great design to run for senator and then later on for county commissioner. That's why he's in King William and not in the Edison area where he originally began or the Jefferson area began his early years. He was redistricted out of precinct to by the commissioner that he was proposing to run against.  No, actually the common denominator of these offices is you want to serve, you want to serve, you want to make a difference, you want to lift up society. I think it was on election night when I didn't make it for a county judge. A person who said, hey, and I looked around and he said, run for mayor. And I thought, oh my gosh, that's a lot of work and no pay, basically. But I started thinking, you know what, this office won't pay me any money. But frankly, if I was into money, that's the last thing I'd be doing. I would never recommend it. If a person really wanted to get some money together, do not be a public official. You say though that there's not much money in public service, but in your county position, if I'm not mistaken, I believe that the commissioners are paid over $100,000. They are. They are. 107 was where it was when I left. I understand it was 113. So why do you say that public service isn't at least in your old position if there wasn't very much money in it? Well, because I think it's true. I think that I have a law license and that law license would catapult me way beyond this pittance of a pay that I've received. Even if it's great to some, it's not everything to others. It's respectable. It's infinitely better than the city council or the mayor to get paid 107 or 113. As a county judge, it's about $125,000, $135,000 a year. It's infinitely better, but it's not really necessarily what your full potential would bring in the private sector. To run for mayor, it takes a lot of money. Absolutely. I think your album has raised quite a good amount. Leticia has raised a lot too, and she's gotten at least $150,000 of that, $300,000. How are you doing? How much money have you raised, and what challenges do you see when it comes to participating in the arena? Well, I was told, and this is the grit and the gumption that has driven me all of my life in whatever endeavor. I have pursued. I was told when I started thinking about the mayor's shift, the mayoral office, that it takes a million dollars to run for mayor. And my reaction to that is an outrage. That is a threat, and that is a clear and present danger to the well-being of our community. For you to have to be so deeply mortgaged to the privileged elite of the community, they need to be served too, but not exclusively. By the time you get through raising a million dollars, you will serve them quite exclusively. And you may never want to admit it. You may deny it into eternity, but the reality is you are heavily mortgaged to those folks that brought you there. So, you know, a million dollars, I think is an outrage. How will I handle it? I've probably put along with Karen, my wife, 120 or so thousand. So you're personally invested deeply? Yes, hugely. Hugely, 120,000 we've raised, about 50 will raise another 100 or so, but I'm going to raise a million dollars. And is that going to get your, you've got ads going on TV now too, right? Yes. And that appears really expensive to maintain. Very. Very. How important do you think those ads are? They are very important. That's the bar to everyday people serving as mayor, even if they're really well-qualified, even if they have great ideas, even if they have an impressive work history or an impressive public official history, the money becomes the price of admission, a big time, the price of admission to higher public offices. So you have two ads, the standard ad that talks about who you are, and then you have one that focuses on Senator Vandipie. Why did you feel that this other ad was necessary? Because I think the truth has not come out yet about the money laundering that's going on, the lack of transparency with respect to what the law requires in terms of not accepting donations. There are donations that are way over the $1,000 limit, and I mean, significantly, not just a couple of $5,000 donations, I think, $25,000 was one of the figures I saw. But I just think that if the enforcement mechanism for the obedience of a candidate to the law of limitations on campaign financing cannot address the problem, then maybe taking our message to the people will help address that. A lot of people talk about Center City, wanting to redevelop downtown, wanting to redevelop near downtown. Do you think that we should be focusing so much on downtown San Antonio? Do you think there are other areas of town that you want to do? Frankly, it's kind of like picking one area over another. I think downtown is very special. I think we all treasure downtown, but we cannot let that blind us from the reality that many neighborhoods are highly underserved. And the city cannot be fixating strictly on a few areas to the derogation of everything else. What do you think the mayor and city council should be focusing their attention on, you know, kind of July? Back to basics. Crime-free, safe, and sustainable neighborhoods. Road infrastructure, including curves and sidewalks. Walkability of our neighborhoods. Flood control at $2.5 billion plus in unmet flood control needs and expanding local businesses. So would you say that flood control is like one of the, you mentioned it, but flood control is like one of the, we're a very floodable city. We are. We are. And part of that, it derives from having $2.5 billion in unmet flood control needs and deflecting our attention. Oftentimes on these big important, one might say vanity projects as opposed to the everyday, not so glamorous, but very critical needs that the city has. So what can you as mayor do about that? Well, you can get on the ball with the flood control efforts. And, you know, the legacy projects, the vanity projects need to take a back seat to the basics. They don't have to be eliminated. They just need to be more reasonably. Could this be addressed with bonds? It could be. It could be, yes. Uber and Lyft have left. Do you think that it's worth trying to bring them back? Well, I think that the next time we reset the process for dealing with transportation, they should feel like they're welcome to make a proposal. And I think the council needs to set out the standards by which we will judge cabs as well as the ridesharing industry and make sure that we have everybody on as level of playing field as we can. And I would be very open to that. When it comes to companies like Uber and Lyft, is this something that should be decided at the city level with local control, or do you think the state should weigh in and draft its own legislation for it? I like local control. I just think it's more responsive. It's more appropriate, more suited to the people than to have somebody in Austin giving you a cookie cutter. As a former chairman of the Metropolitan Planning Organization, MPOs, Pedestrian Mobility Committee, I believe we need to provide as many options as possible. And I think the city ought to catalyze a process that brings about robust alternatives to conventional transportation. Julian Castro had the SA-2020 initiative to kind of plan for the vision of the 2020, and now Ivy Taylor has SA tomorrow, which is supposed to reach out to 2040, but to be more strategic and address some transportation needs. What do you think is the value or the role of those programs if you become there? Well, those are visionary projects that, as is said biblically, a nation without vision will perish and so will a community. We have to know where we're going or we'll be lost, and I think that's true of humanity across the globe and across the span of time. We need to have a planning process, and I think what gets measured tends to improve and gets done. And so we should say, this is what we'd like to see happen. This is what we think is good. If others come along and say, we don't agree, let them bring something else on. But they'll have to overcome the logic and the thrust of what had been put in place before them. And you do support those initiatives? I support all those initiatives, and I think that it's a healthy thing. So what would a Mayor Atkinson do in the negotiations with the police and fire contracts? Well, I'd ask him to come to the table and let's work this out and not leave the table until we get it settled. I think it's not unlike calling a huddle or calling a goals clarification session, whatever you want to call it and making sure that the Mayor is involved in this. I think that we've had a power vacuum in the Mayor's office for some time. And a power of whores vacuum is the old statement. And that means that when people are not moving forward and getting things done, that we begin to slide into a malaise. And that's where we are with the Fire and Police Contracts. Can we talk a little bit about City Manager Cheryl Smilly? What are your thoughts on how she's handled the police and fire negotiations, the lawsuits that have come out? What are your thoughts on her handling of this?  Well, I think, in general, I think she's smart. I think she's capable. I've had a pretty good relationship with her husband at the county and I've had a long-standing good relationship with Mike Scully. But I think with respect to the fire and police contract, the power vacuum was too compelling or tempting, whatever, for her to resist and she ended up interjecting herself into it in a way that I think an elected official would normally have done. Do you feel she's overpaid or overcompensated? I do. And what would you do as mayor to address that? Well, I think you have to do exactly what she's asking the Fire and Police to do and that is to come to the table with some concessions. And what if she leaves? Well, you know, Alex Prasigno has the record for the long-standing city manager, eleven years, and after that, Lou Fox is about eight or nine years. I think Cheryl has around ten years. So really, these city managers are not for life and it's out of all due respect, but maybe it's time for us to change gears. Frankly, the million-dollar golden parachute is in addition to the bonuses, which, you know, when you get a bonus in the front part of the year for work that's supposed to be accomplished during the year, that's really odd. What is the million-dollar code for that? Oh, there's a deal that said that if there's an inappropriate departure, or let's say termination, I guess would be the word, by Cheryl Scully from the city that she would have a million dollars awarded to her for that. If a voter came up to you on the street and asked, why should I vote for you, what would you tell them? Well, I think my track record of solidarity, of courage, of ubiquitousness, which is what Phil Hardberger says I was, ubiquitous, which I didn't understand at the time completely, but I looked it up just to make sure I knew it was okay, because we haven't been friends for a long time. But it means you're everywhere. And to me, whether it's the Tea Party, or people upset about the trolley, or people upset about any facet of government, usually the presence of the leader can help sell the dust on a lot of that. And I know this has kind of been a thorn in your side for a while. The situation with the emails and the Third Court of Appeals saying that you should turn these things over. And you mentioned that you may just finally give up the emails and people would be greatly disappointed. Well, they will. Are you planning on turning over the emails just to get this thorn out of your side? Well, I think, you know, frankly, I don't have time to mess with. I put a lot of money, almost as much money as I put in this campaign, into the effort to basically preserve my private property, my Fourth Amendment privileges rights as an elected official. And I thought that the law did support me at the outset, but the powers that be changed it in this last session before the session is going on right now. And the emails they sought at that time were emails basically between myself and citizens to expect to have a measure of privacy. But because of the Open Records Act, may well not receive any privacy. And I also felt like that all the Valero and the AT&T and you name it, employees across the spectrum of San Antonio and Bear County who serve on boards and commissions are going to be subjected to this. So they would hope that their conversations on their emails are not impinging upon and detracting from their own employers. And their employers, I think, would expect that their employees should be given measures of privacy and what they cut up that may impinge upon or detract from their company's business. So what I believe the disappointment of the emails will be for the Express News and anybody else who's interested in knowing is that I've had conversations with various citizens including Terry Hall who I think was at the eye of the storm on the anti-toleroid fight. I've paid a huge price. When people say, elected officials, oh, we're against torwards. I have fought against torwards. I don't think so. My last part of the question is Bear County was ordered to pay the costs that Hearst invested in the lawsuit, but Nelson-Wolf said that you would be taking care of that personally. Yeah, I've taken care of about a hundred... Why is that important to you? I've taken care of about $120,000 already. And what's left is not much. But it's important to me to take care of responsibilities and obligations but it's also important to me for the county to acknowledge some of its own participation. I would not have been sued had I not been a county commissioner. They wouldn't have any reason to waste their time on me. I mean, I didn't even talk to me. I don't know. But it certainly would not have had any interest in this. And so, actually, every elected official has the jeopardy or the prospect for being hauled into court to give up a whole array of emails that you may think should be private or that those who sent them to you expected that they would be private. Such as a person that may say, I want to tell you that my son has been dilly in drugs and I think he's about ready to be busted. Can you please tell me who as an attorney I might seek advice and counsel from? And maybe that's all prospective talk about a son that may or may not be involved in drugs. But you can see the danger that lurks there and even for an elected official. Or a board and commission member to be subjected to this I think should suggest caution. And I think the county has an interest in every elected official. Certainly the county official's protection of certain manners that should be remain private. But I'm looking forward to resolving it and hope that we can move on.


Hey Vlad. Hey John. Hey, good morning. How's it going? Fine. That's good. Hey John. Good morning. How are you this glorious Thursday? Thursday. Yes, it's Thursday. Don't good, don't good. Hey Vlad, I've been asked you just, I'm just curious, where are you actually located? I mean, Bucharest, Romania. So it's evening actually, but yeah. Cool. Okay. I was curious. I love it because I can easily fly everywhere in Europe or Asia. Right. Okay. Hey Ginger. Hey Doug. Hey and Tommy, are you there? All right. Thank you. And Heinz, are you there? Yes, I am. Hello. Oh, hey Eric. Actually, maybe a really short call. I didn't notice any updates to the, so I'm not sure how to interpret that. Hey Kristoff. Hey. Yeah, I noticed you this time. The next three weeks, I'll be on vacation. So I'll mark you a vacation next three weeks. I'll mark you on the attendance thing for that. Thank you. And Doug, are you there? I am. Good morning. Hello. Hey Aviar. Hello. There's someone in the zoom with an idea of, I can't tell what's an L or an I, then B-E-R-K. If you could do me a favor and paste your name into the chat. So just so I can mark your attendance, I appreciate that. And hi Klaus. Oh, Lucas. Hey Klaus. All right, Lucas. Thank you. Hey Jeff. Hey. Oh, hey Colin. Hey Doug. How's it going? I'm good in yourself. Pretty good. Pretty good. Mike, are you there? I'm here. All right. And Ryan. Yes, I am. Hello. Excellent. Hello. We'll just get started at three after. So just get that one. And hey William. Oh, type. Kind of weird. There's no Clemens. It's unusual. Let me go ahead and ping him because I like to get an update from him on a part of the doc. If he's not around, I can do my best to speak to that. Oh, cool. That'd be great. Okay. Did I miss anything? I think I had for a bit, right? Oh, there we go. Mark is running. Hey Mark. Oh, Mike. Hey Doug. Hey Mark. And Lionel, are you there? I'll be bailing in a little bit for that other presentation on Cloud Events. Yep. Thank you, sir. Hi Doug. Hey, got your Lionel. All right. It's three after. Why don't I go ahead and get started? This is Mohammed, by the way. Oh, Mohammed. Cool. Thank you. I missed you. All right. Let's do this thing. Excuse me. In terms of AIs, I did reach out to a couple different people in the CNCF organization, in particular Liz Rice, who tears up the TOC. And she said it was okay for us to send a note to the TOC as opposed to a formal presentation, just update them on our status. So Mark and I are working on that. If you're really, really interested, you could look at the tail end of the situation discovery doc, if the rough draft they're working on. But I don't think there's anything too controversial in there. So once Mark and I settle on the exact wording, I'll just send that out as an email to the TOC. And I'll probably BCC one of our mailing lists here. So you guys can see that when it goes out. With that, community time, anything from the community that people would like to bring up moving on. Kukani you. So I did create a planning doc just to gather all of our thoughts and activities there. So I bring that up here. So a couple of things. First of all, if you are planning and going, please add your name to the list here, just so that we can keep track of it for face to face planning purposes in terms of making sure we have a big enough room. And also, we will be having a kiosk if they ask me anything kind of booth thing. And I want to know who I can hit up for potentially manning that booth. So don't use this as an excuse for not putting your name there. We will leave out here. So please. Okay, so for the 35 minutes session, I'm still trying to find out from the workflow guys, who's going to be presenting there and what their abstract is going to be. I think they've been busy or sick or something. So I haven't been able to sync up with them. But the current status is a five minute quick update on cloud events, followed by the bulk of it on the workflow stuff. Okay. Now for our intro session, we agreed to a quick update on cloud events and then an overview of the subscription API. I don't mind doing the cloud event stuff. And that's someone else really wants to do it. But if you do either want to do that or the subscription API spec, just put your name here. Just because you see a name in any of these things, don't hesitate to put your name if you really want to do it as well. This is just for the list of people to choose from. And then we'll figure out who's actually going to do it later. So don't be shy if you already see a name on any of these spots. On the deep dive, here is the abstract that Scott gave me that I sent in anyway. And he's volunteered to be a speaker there. Given it's a hands on lab, we probably don't need too many speakers per se. But if you do want to join Scott on the stage to talk about stuff that'd be great. However, we will probably need several people to help out to walk around the lab to help the actual participants do stuff if they get stuck. So we will need as many people down here as possible. So please think about adding your name here as a lab helper. And as part of this, we probably also need to decide which SDKs we're going to focus on. Is it going to be just one to keep it easy for us maintaining this stuff or our presentation perspective? Or do you want to potentially have a couple of different ones people can choose from? No decision on that yet. But be thinking about that one. My plan there is, I want to set up like a few levels of like there's a hello world and then there's maybe something a little more complicated and then receiver and so on here. And then implement that as references in so sort of GitHub repo. And so people can pick their language and then try the exercise and they get help and then they can cheat off the actual version of the source if they want. Sounds good. Vlad, your hands up. Will everybody use their own laptop or how will this be? Yeah, it's bring your own laptop. Yeah. So when I get closer, I need to remind myself to make sure that I tell the event organizers to update the description to here to make sure it's perfectly clear that if you're going to attend this session, you really need to bring a laptop. Otherwise, it's not nearly as exciting. Right? Yeah, I was thinking like a five minute intro and then 30 minutes to kind of walk around the room and help people go through the exercises. Yeah. Okay, any other questions about that a little bit? Okay. Now question for you guys. I did confirm that we will have an answer bar ask me anything kind of a thing, which is the booth in one of the big halls there. And apparently there are three different options we could do. We can do dedicated kiosk all to ourselves, but it basically means someone has to be there full time or has a man full time, I should say. The other options are either halftime, dedicated AM or PM, or they describe this one as shared kiosk staff a few hours. I didn't know what that meant. I'm assuming it means more like it's just sort of random, whatever people are available, they stop by kind of thing. Not 100% sure. However, I'd like to know from you guys how you feel about this. Do you want to try to staff it full time? Do you think there's going to be enough interest in people from the audience? Because I can be the nag to try to get everybody to sign up if want to do full time, but I don't want to pester people if everybody thinks it's too much. Any preferences? Scott says halftime. Anybody else have a preference or opinion? When you say full time, do you mean full time throughout the conference or just for the first day? I think it's full time through the conference and here are the hours up here. So it's a non-trivial task. I'd say look to staff it during any of the parties or other bigger events that might be occurring within it. Okay, that feels a little more towards like the third option. I'd say this is gender. Nat said this last at the San Diego one and I will say the first day, if you're doing it all the whole time, first day is a very, very long day because you have the regular hours and then you've got the sponsor showcase, so the FYI, it's a very long day. Was there a lot of traffic? Thankfully, we had a lot of traffic but Derek was also in the keynote, so I think that helped our traffic. With regards to the other kiosks, I think Prometheus was right next to us. They had quite a bit of traffic throughout the whole conference. I couldn't really see the other ones as much. I know Fluent D was next to us and they had a booth the whole time but I will say that they didn't have people there the whole time, even though you're supposed to. What they did is if you only booked for certain hours, they would come out and switch the signage. Whoever the staff is that would do it. I don't know if it's CNSCF staff or if it's the conference staff, but they would come out and switch the signage. If it's cloud events for the morning, then it would have a cloud event sign and then if it was somebody else in the afternoon, they would just change the sign to a different project. Okay. Well, thank you. That's good to know. Yeah, but it was, I think it was very worthwhile for sure. So based upon your experience, just to put you on the spot here, if you were to choose of those three options, which one would you choose for us? I probably would pick part-time if the people that are attending the conference want to go do anything else. Just because, like I said, if you're supposed to staff at full time, the CNSCF does want someone there that can speak about the project pretty well all the time. Right. Let me say part-time. Do you do that option two or three? I would say two. Three is kind of weird. I'm not quite sure about that. Yeah. Okay. Vlad, your hands up. Thank you, Jinder. Vlad, your hands up. Yep. Can we post a schedule or something if we choose the second or the third option? I remember in San Diego, I wanted to chat with somebody at the booth and there was nobody there. It was unclear which were what. So having like a public timetable or something, and I don't mean public in the sense that in the working group. I mean public, like on the CNSCF website, SCAD whatever, that would help a lot. I can take an action item to ask about that from the staff. They do have that on the schedule. And so if you look at the schedule, it will have something like meet the maintainers or something like that built into the schedule. And it'll have your project and it'll show when the booth is staffed. I did not know that. Sorry. No worries. I just know because I saw it on the schedule when I had to be there. Yeah. Okay. Personally, I'm a little more towards number two just because this third one just confused me and it seemed a little too random for my taste. So I'm leaning a little more towards two. Scott, I know you said two as well. What do people think? Landing on two? Anybody have an objection with that? Well, I guess the only question is, is it always AM or always PM? Because otherwise I don't see how that's... Yeah. Maybe we can do one day and one PM in case people are going to have some flexibilities. So we have a little, I don't have to sign up till February 14th. So I can take the action item to find out a little more detail, whether it's, if we say AM, it's always AM or do we have to pick AM PM per day? I can ask about that. Good question. Oops. Okay. Cool. I can do that. Okay. Let me think of anything else. So I think we'll be able to get a room for the face-to-face meeting, but they won't be able to tell me until February 14th, which isn't that big a deal if you are already planning on going. However, if your travel approval, travel plans, whatever it may be, are contingent upon us having a face-to-face, you may not find out until February 14th, which I think is within that, right around that four-week window for our governance talk of announcing a face-to-face. So just be warned. You may want to get your travel approval in now and maybe, not necessarily lie, but tell your manager or whoever that you think there will be a face-to-face meeting. We just, we can't know for sure until then. Okay. All right. Anything else relative to who come we need to talk about? You can always say that you'll need Doug face-to-face. That's always exciting. Yes. I'm sure they'll get everybody on board. Yeah. Thank you, Mark. Can we get a room outside of the conference if we have to? I'm sure someone has an office around Amsterdam. That is definitely a possibility. That would make it harder though, because it'd probably be, it probably had to be more after hours then, which makes it a little bit more difficult to get our way together, but we can definitely look at that. Yeah. Yeah. Okay. So let's hold off and see what they say. Like I said, I think it'd be very odd for them not to be able to find a room for two hours, but we'll see. Okay. Anything else relative to the face-to-face? I'm sorry. Impressive. Okay. Vlad, I assume your hand is old? Yeah. It was old. Okay. Cool. Okay. I think we already talked about all these things. That's good. All right. SDK. We did not have a meeting last week, so nothing to talk about. I believe we will have a meeting today, right after this one's over. So anybody on the SDK side of the house, please be prepared to join. Kathy, I believe, is sick, unfortunately, so she's not on the call. Do you have anybody else from the workflow subgroup on the call who wants to give status? No. Okay. In that case, in terms of issues for cloud events itself, these are still being worked in the background, I assume. However, this one is new. I don't want to necessarily talk about it too much here other than to poke people to take a look at it, because it's a question about serialization of JSON. And I know that we talked about this in the past, and I just could not remember the definitive answer. So I was hoping maybe like Scott, since you're obviously heavily involved in the go-long SDK, maybe you could take a look at this and give your take on whether there really is a problem or not, or if not, why it's not a problem. So that's okay, Scott? Yeah, I'll take a look. Okay. Appreciate it. Thank you. And of course, anybody else is free to look at it. I just know, I think Scott's played in that area, that's why I was picking on him.  And I know we went back and forth, I think, a man a couple of times. Okay. Anything else relative to the cloud event spec itself before we move on to the new spec? All right. Moving forward then. Okay. Since Clem is not on the call, Mike, would you like to update us on the status of things? I don't have any major update to provide other than the comments in the doc. I'm trying to get everybody, I propose the time tomorrow to talk, right here back from everybody. Okay. Unfortunately, I did not notice very many edits really at all in the doc this week at all. So that leads me to believe we may not have anything to discuss. And we have a very, very short phone call. So let me open this up. Are there topics on the spec that people want to bring up at any scope level? Hey, this is Ron. Yeah, I can just confirm that. Unfortunately, for the subscriptions part, majority of us had a combination of heavy travel schedules and being sick over the last two weeks. So we didn't meet this week, but we do have a follow up on Tuesday. So we'll hopefully have a more meaningful update next week. Okay. Just dead accuracy. Was Clemens one of the other sick? No, I believe it was Kathy and myself. I know Clemens has a pretty heavy conference schedule this week and has been doing a bit of traveling. Okay, okay. I was going to give him a hard time. But okay, if he has travel plans, then I can't avoid that. Okay. Yeah, go ahead. If we have time. So last regular call, we also talked about the subscriptions on sort of the back propagation of a subscription up to the original publisher. And what Clemens is not on the call, what he said, it's a difficult topic. And he kind of wants to push it back and I thought a bit about it. From my perspective, it's not so difficult. So I don't know if it's appropriate of not stop me if we discuss in this detail now. But my fault is it's actually not so difficult because you have the filters and you just take all your filters, you propagate them up one step. And then the other guys can do what they want with these filters. If you apply filters on your events that don't apply to events, it's fine. So I don't see where he thinks it's so difficult. Anybody want to comment on that? I don't have an opinion right now myself on that. I'm tempted to say that might be a better discussion for that other phone call or to wait until text appears in the spec to comment on it. That's just my initial reaction. Yeah, so I have been thinking about this also quite a bit. So that's also why I added this eventing domain section further down. But I also agree that maybe in the other call we can discuss it. Do you want to discuss it now? It's up to you guys. We have nothing on the agenda to be honest. Depends really. I mean, I brought up this abstract model of eventing domains because, I mean, there can be different messaging technologies behind. I don't know, Christoph, what scenario you have in mind exactly. So if it's also about using different protocols, so then you might have something that's bridging between different eventing technologies. So if you're propagating a subscription upstream, you might need to create things like queues and then delete them again if the subscription is deleted. I don't know. Yeah, could happen. I mean, maybe first we can discuss if we want to really have this discussion right now. I don't want to keep other people on the call and board. I think I won't be able to join the call on Tuesday, but I can try to make it. You could send a note to the mailing list to get your thoughts down on paper for people to read it. Yeah, that would be an option. Or, I'm sorry, just add it straight to the dock here. At least, because you don't have to wait for the subgroup to add comments to the dock. You can add your own, just to make sure it's out there for people to think about. Okay. And by the way, Christoph, it would be great to meet you on Slack. I mean, we're in the same time zone, I suppose. So one of the few guys I can discuss during the day. Okay. I'll try. I'm pretty busy with work right now. Okay. I'll try to join the Slack channel. Okay. Okay. Anything else you guys want to talk about? Colin, you can come with me. Yeah, just with the eventing domain. I mean, I think you get a lot of this stuff for free with most of the protocols. And this looks like it's trying to address the limitation you have with HTTP because there's really no central server. So, Bo, go on. Okay. So that was not the intention. So actually, we are working with an MQP broker below this. So the reason I wrote all this is more to establish something like a control plane for the eventing aspects and hide the messaging bit more. So it's not really supposed to be a new broker or something. Oh, yeah. Yeah. I wasn't insinuating that this would need to be a new broker. Now, I get that. I was just sort of stating that with all the protocols listed, and I alluded to this in a comment as well, it looks like we've got a real discrepancy between the behavior of the HTTP protocol and the others, which are broker-based. And what I was just saying is this eventing domain is very, very easy with a broker-based protocol, right? So MQTT, Nats, whatever. But then when you get into HTTP land, this becomes actually very difficult. And I see the problem you're trying to solve. I'm just sort of stating that there may be more here than this could get into a very deep pit. Okay. Yeah, I see. So yeah, for HTTP, as it is usually point-to-point, I agree that's more difficult. So an extreme example of an eventing domain would be just a single, I mean, a point-to-point connection. So you wouldn't then have a lot of producers and consumers, but just a single one and combine them then by a link, basically. And then it wouldn't really be really a dedicated domain or something. It'd be just hidden inside the producer and the consumer. You could also think of it that way, because you would still establish something like trust between those two. So yeah, it's meant, I mean, there are a lot of messaging products and also services and then the cloud providers. And it's true. It was more with those more PubSub-oriented services in mind. That's true. Yeah, I think it's a good idea to call this stuff out. This is good. Okay. Anything else? I left a comment on defining a goal around how consistent we want to be across protocols. So one thing I really, really like is when products just work out of the box. And I know it's a really lofty goal, but it would be great if we could provide some guidance around same defaults so that you can just switch between MQTT and NATS or MQTT and HTTP. What have you with minimal configuration changes? And setting a goal to this would help inform what this wire protocol might look like and maybe even bubble up to the API. Sounds reasonable to me. Is there actually text you can think of to just stick into the spec right now that the other sub team may be able to pick up and grab? Not off the top of my head, but I could take a stab at it. Yeah, but I would say do so. I mean, it seems reasonable to me. Okay. Anybody else want to comment on that? I know Klaus, you're commenting in the chat. Anybody else? I think everybody wants easy. So that's good. Oh, I don't know. Maybe Vile wants to vote for Harvard. Okay. Any other things you want to bring up, Klaus? Well, yes. It's not really about the subscriptions. It was actually the issue I opened more than a year ago, I think, about the nested events. So I've still got that action item and I'm honestly a bit clueless after our last discussion. So originally I brought it up in the SDK call two weeks ago because I thought it was just more or less an implementation detail in the SDKs. But the interesting enough, the discussion brought up that it's different. So as you can see, I brought this up in February 2018. So it was even before we had 0.1 of cloud events. And I think for me at least this nested event case is not really relevant right now, but still as I brought it up and it was an interesting discussion. So the idea is, we had the idea, I think, in the discussion further down. Doug, you proposed, I could just write an example where one event, like a structured encoded event, would be nested inside a binary. And when I tried doing this, I ran it to the problem that we determined by the content type that what the event in that message is. So doing this, what is shown here, this example is not possible and it's also not really that came out in the discussion two weeks ago, really against the spec as we say that. No, I think it was against the spec. Yes, that's what I said. Sorry if I somehow didn't express that clearly. So exactly. So the idea of the spec and that I wasn't aware of that too at that time is that even if you do structured encoding, all the attributes from the structured encoded event can also be replicated to the header. So this case that you have one event in the header and another one in the payload is not really possible, at least if you use the normal content type of the cloud events plus JSON. So I really wonder now how this could be solved and or if it needs to be solved. I mean, could also be just some note somewhere. I think we could work up an example in the goaling SDK where we make application JSON plus cloud events and they would interpret it correctly. Yes, so I've been reading a bit in this about this media type specification, this RC and so on. Plus cloud events is really strange, I think. So I mean, the plus something part is supposed to be a structure encoding part and I don't know, see cloud events in the line with JSON XML and the others somehow seems to be strange to me. But yeah, so just I'm just interested to hear some more opinions on this actually. I just read the issue for the first time. The thing that comes to mind there is in that API gateway issue is causality that there might be an independent event from the API gateway. It could reference that it is caused by the other event. Yes, but isn't that really just talking then about maybe adding additional attribute to do a relationship? Were you talking or does that directly affect the nesting aspect? I mean, I would question if you need to nest events or not. Yes, I said I created that issue in the beginning when I still was trying to make my mind about all this eventing and by now on our end, I would say we definitely want to avoid this nesting. But one example where I saw something like this or where it might occur is actually in canative eventing. With some of the sources, I think like the Kavka source, I think they create their own event types like Kavka event. And then they already get a message from the log that already contains a cloud event. I think then you would have something like a nested event. But I still think that it's more like an accident, not really desired. Yeah, I think that particular case is about being canative. Okay, nevertheless, if you rely strictly on structured encoding, you could nest events and some SDK that gets one structured event nested into another one. And for some reason would like to transcode it to binary on the top level would kind of run into this issue, I guess. So I'm trying to remember the phone call we had about this. And I came to recall you became the conclusion that this example here was technically invalid. And I think part of the reason was because these properties here did not match the properties here. And if these appear here, they're supposed to basically be a duplicate of what you see inside the body. Am I remembering correctly? Yes. Okay. The one thing that always kind of bothered me about that is I know that the spec says you can copy things up. But does it mandate that if, for example, C type appears here, it has to match what's in the body? It doesn't say that it says that the authority is the body. Right. The processor would just look at this and say it's formatted incorrectly. Okay. So well, or worst case scenario, he looks at these and says, because of this value here, everything's supposed to be in the body. So if I'm going to be looking at the body, I can just ignore these. That's right. Okay. Thank you. So would that then imply you can't do nested? No, you can. You just have to say the application content type is application JSON, maybe plus cloud events to signal that the processor that processes the body pops it into a cloud event. So flip those two things and I think it just works. It would work, but it looks definitely strange, but maybe yes. Well, just out of curiosity, what happens if you don't do the plus cloud events and you just do this? Is that? Yeah, that's valid too. That's absolutely. That is valid, right? You would serialize that as cloud event JSON structured object and it would just work. So Klaus, is the answer here to put something in the primer that says if you want to do it, as of right now, this is really the only way to do it? Yes, could test. I mean, we can test the Go SDK if it does it. I mean, if it receives. Yeah, I can add a test for this and we can add a custom decoder for the application content type or sorry for the media type of application JSON plus cloud events. Yeah. Okay. I mean, probably it's already wasted effort as probably it's not that relevant. Although actually thinking about it, you don't really need that. That's a hint to know what the format is, but it's really just JSON and cloud events doesn't really care about the opaque body. Okay. That was a bit my question. Why do we have to have it like in the spec? You have like the data and in the data, you can have whatever we want, including another nested event. So that's up to you if you really want to do it. But then you don't get all the transformation from one protocol to the other, obviously. But that's not up to you. So you can do it if you absolutely have to. Well, I don't see the value of adding the complexity of all this nesting into the spec. Okay. Yeah, I agree with that. Yeah. But I thought your Heinz you're looking at putting it into the primer just as guidance, right? Something like this. Yes. I mean, we can also just close the issue actually. Well, I think it's interesting. I mean, because I was just thinking about this is obviously this is one way to do it, right? You have structured around binary or binary around structured, but it might also be interesting to show a structured within a structured where I think as Christoph was just saying, this stuff doesn't appear here, but there's another cloud event in here. And then you have the content type up here and what that would look like. Yeah. I mean, in that case, you could choose cloud events plus JSON. But it's just that in the binary case, the content type is yeah, somehow used and yes, just special because of this binary case. Yeah. I mean, as I said, technically, we don't think we have to do anything, but I always think that if we come up with a question and we're the experts on this stuff, it may it's useful then to put into the primer for people who are not in our position. You know, even if it's just for informational purposes only. Okay. So yeah, I can add that to the primer. Then I guess the recommendation would be in any case to just use this application JSON even for the structured case. Otherwise, it would be really confusing. I mean, if you do one structured event inside another one, you could technically still use cloud events plus JSON instead of just JSON, but you must be there for a second because I think did you say that if it was structured, you can just use the application JSON and not application cloud events plus JSON? Yes, otherwise, yeah. I think closest is correct because I don't think it would round trip converting a wrapped message between binary and structured if it wraps a structured object because I think it promotes the content type. In that case, you get into the same situation of the above example. So it seems like primer text is probably in order if you're going to wrap cloud events. Are you okay with that, Klaus? Yes, I think so. Yes. Okay. Any other questions or comments on this one? Okay. Any other topics at all then about either the new spec cloud events or anything? Any plans to cut a new release of cloud events? Or is it just minor tweaks? I think we've only had one tweak, which was the sentence that says it was a draft, right? I don't think we've changed anything else yet. Did I miss something? No, I was just thinking about our ability to rev the spec independently of the version of cloud events, like the bug fix sem-verb section or something. I'm not quite sure what you're asking, but I apologize. I'm not following. We could still send 1.0 events, but the spec is 1.0.1, for example. Yeah. I'm trying to remember, did we say the spec version required how to be sourced? I don't remember if we ever talked about what would happen if we do a patch version, if this version would change. I don't think it would change. Because patches should be completely compatible. But they wouldn't have the new features. It would be 1.1. I think that'd be a, yeah. That's why I said patch, not minor. So what's your actual question then? I apologize. So if we do a 1.0.1, so like a declarative text in the spec, and we want to ship a new version of that because it's better, but it didn't change the API. I think off the cuff, I would say the spec version string itself does not change. Right. Okay, great. But that's just me. I don't think we have to actually send that in the spec, and maybe that's something we need to add, or we can wait till we get to it. I'd agree with this. I mean, if we have a typo and we fix it, and we really want to release a patch version, I don't see why a new spec version is relevant in any way to anybody who uses Cloud Events. Yeah, that might be something worthy of mentioning someplace in our primer or something that just so people understand our versioning scheme. I'll double check. I have this vague recollection. We may actually say something about that someplace, but I'll check. And if not, maybe I'll open issue just so we can think about it. Okay. Anything else people want to bring up? Okay. Did I miss anybody for attendance? I think I got all the people who showed up at the end. All right. In that case, we are done. Thank you guys. And if you were interested in the SDK call, go ahead and stand the line. We'll start that one up in about two or three minutes just so that people leave. Thanks, everybody. Thank you. Bye. Bye. Bye-bye. All right. Any topics? Otherwise, it's going to be a very short call. Scott, you usually have something exciting to say about the Go SDK line. I'm sorry. Go line SDK. Scott is taking a small break. You have your eyes on him. Interesting.  Okay. We'll wait. Anybody else have any topics they want to bring up? Okay. We'll wait and see if Scott has anything when he comes back. Otherwise, it's, we signed up to go to Kukan. Not too bad. So, really, are you able to actually see when he comes back? Oh, yeah. He needs to make sure he knows we're waiting for him. It's all about Scott. Yeah. Don't tell him that. He's a big ego. Yeah. I mean, you know, when he comes back and if we happen to be in the middle of a discussion, how terrible the cloud Go SDK is, then I'm sure he would be super excited to join the conversation in the middle, just throwing it out there. Yeah. Yes. Oh, hey, why are we waiting? There was that face-to-face meeting between Knative and Kata. What's the next step in that? I thought there's supposed to be a follow-on meeting. Has that been scheduled yet? I don't think it has been scheduled yet. There is a Kata call at, I think it's in like whatever, 20 minutes or 10 o'clock my time. So the next meeting slot. And I think there's some jatties about that. I know some folks played with the interaction with the K-native and Kata and seeing where it would kind of fit in. And this morning in the channel's working group, we also chatted about making sure that we start, there's the whole channel spec on sort of kind of what the channels look like. And there was some talk about making sure that in the spec, we do not assume too much of a push-based, but we also allow for the venting based, sorry, pull-based models. And so I basically wrote some folks volunteered them to go ahead and take a deeper look on what does that mean. Did you either hear of or take a look at the work that Alec is doing around Kata integration? I think you might have talked with Scott yesterday, but I didn't know if he pinged you as well. Yeah, he didn't ping me, but yeah, I'm aware of this. This is Islam. Yes. Okay, cool. Okay. So is Mr. Scott back yet? He minus five seconds. Scott, you there? I am back. All right. Thank you. So no one has said anything to bring up. I was wondering if you had anything to bring up from the go-language case out of things? I do, I do. We are going to go do a version 1.0 release. There's a bit of staging that's going to happen. Like massage the EPI a little bit. Some of the deprecated things are going to get removed, so we don't have to continue forwarding them along. And then we're going to start doing strict semper. Okay. So I haven't been following the go-lck for a while and now got back and looked a bit more into it. If I understand that correctly, so there are those two approaches right next to each other, the bindings and the transports. And yeah. So at the moment, the plan is we're going to do a 1.0 release that's going to capture the original method. And then because we're going to do semper, everything else in the repo is going to start having to become API compatible for changes. There's going to be a 2.0 release that drops the original transport implementations in favor of the bindings. Okay. So that's kind of where it's going. But the hope is that if you depend on a certain part of this, the SDK, you can do semper fuzzy match and you can stick with 1.0 if you need to, but it's going to be end of life in probably, I don't know, six months. So V2 is scheduled for around six months? Is that what I heard? Yeah. I think that sounds about appropriate. Okay. So the 1.0 release, if I get time, it's probably going to be cut next week. So before the next meeting for cloud events, it'll be 1.0 and semper.  And we've been coding this strategically. So there's pieces that are leveraged in the 2.0 implementation that get migrated out or copied out of the 1.0 version. So we're aware of the strategy. And then the other thing that's going to come is we're going to document the 2.0 architecture so that it's a little more clear what exactly we're doing and how to add a new binding, your own custom bindings and stuff. The goal is to get 1.0 walk down released for KubeCon and for integration. So this comes because there's been some people that would like to integrate with the SDK, but are unwilling to do this in the read me. It's like, by the way, you're going to break you willy-nilly. And there's customers that do not want to take on a dependency that doesn't follow center. So even though it's maybe not production ready exactly, there's still some stuff to figure out. We're going to lock the API down. Makes sense? Yeah. Any other questions for Scott? Okay. Any other topics you guys want to break up? You scroll down a bit. Are you joined this call because I was interested in Tim's question from the other week. So GoLang SDK, Superstable, very much evolving. What is super-involved and maintaining it. C-sharp SDK Clemens obviously uses it for Asians. Asian stuff is maintained, it's stable, so on and so forth. Do we have like a list of maintainers for the others? Should we do that? I'm starting to have some interest in health events, but a lot of people are a bit off by the state of the SDKs. Yeah, unfortunately, I didn't do my AI. I was supposed to poke the bottom four people in terms of who the owners are. I can't say who they are offhand other than I think Fabio might own the Java one. I was going to just take a look at the commits and see who did all the commits and poke those people to find out the status of these things. Well, maybe we need to have official leads that are kind of accountable for these things. That would be a good thing to document that someplace, yes. In the specific repos of you. Yeah, another AI for me that I'll forget to do. Thank you. Sorry. I was like praising CloudEvent and they were like super happy about it. They wanted to do Python. My first question would be why? Why Python or why CloudEments? Why Python? A lot of their app is already written in Python. They do all Python. Why not get with that? There's a surprising amount of libraries available for Python, especially they're doing a lot of lambdas. And Python is super well supported there. Whatever makes the money. Yeah. All right. Anything else? That's it. All right. I believe we are done then. Thanks, guys. And we'll talk again next week or run the SDK in two weeks. Have a good one. Bye. Bye.


Welcome, my name is Dr. Friedrich Stein, I'm a bimacal researcher at the University of Queensland. At UQ, I support a very talented research team and I work alongside people living with motor neuron disease as we improve our understanding of motor neuron disease. Today, I hope to share with you a little bit about what is motor neuron disease. I'll talk to you about who gets motor neuron disease. And as I do so, I'll share with you some of the things researchers are doing to help people with motor neuron disease. Now, M&D is also known as ALS and it's very possible you've already heard of ALS. In 2014, hundreds of thousands of people all around the world started pouring ice on themselves. And they did this in an effort to raise awareness but also money for the research of a disease known as amiotropic lateral sclerosis. Now, it's important to recognize that amiotropic lateral sclerosis or ALS is the most common form of motor neuron disease. This picture illustrates some of the most common forms of motor neuron disease. What is important to recognize is that there are many subtypes of motor neuron disease and that all of these subtypes exist alongside a spectrum that is defined by the impact of disease on what we call the upper motor neuron and the lower motor neuron. Now, when we talk about ALS, we talk about people who have a disease that's affecting both their upper as well as their lower motor neuron. And generally speaking, these people present or these patients present with either a spinal onset form of disease or a pulver onset form of disease. Now, this can get complicated very quickly. And so I'm going to use this very simple diagram to illustrate how upper motor neurons and lower motor neurons work together to control our muscles. And of course, how these neurons then contribute to the different types of motor neuron disease. So the first neuron to recognize is the neurons in our brain. These are known as your upper motor neurons. And these are the neurons that kind of decode your movement and tell your muscles in your limbs what to do. And what's important about these neurons is that they send long projections out of the brain down through the spinal cord where they eventually talk to a second group of neurons. Now, these are known as your lower motor neurons or your spinal motor neurons. And these neurons sit in a very particular part of the spinal cord known as the anterior horn. And so sometimes they're also referred to as those anterior horn cells. Now, what's important about these lower motor neurons is the fact that they send long projections out towards your muscle. And so they effectively attach to the muscle and they communicate information that's coming from the brain to the muscle. And so working together, the neurons from the brain talk to the spinal cord and the spinal cord can talk to the muscle and ultimately this results in movement. In motor neuron disease, very early on in the course of disease, a person might find that their balance is not very good. Or as I've illustrated in this video here, someone might find that when they walk, they have difficulty lifting their toes and clearing it off the ground. In this case, this gentleman does not have motor neuron disease, but they do present with that very classical sign of foot drop, where the nerves that engage the muscles in the leg simply don't clear the foot during normal gait. This of course is very commonly seen in people who have what we call lower limb onset disease. Sometimes a patient will present to their clinic and upon examination, it's very clear that they only have upper or lower motor neuron deficits. And over time, if there is no emergence of upper or lower motor neuron deficits, a diagnosis can be made to suggest that they have one of those less prevalent forms of motor neuron disease. For example, if a patient after four years presents with no signs of lower motor neuron deficits, they may be classed as having primary lateral sclerosis. A huge challenge in motor neuron disease research is making sense of all the different subtypes of motor neuron disease, but also the variability that is associated between these different subtypes. On top of that, it's important to recognize that even within subtypes of disease, there can be huge variation in the presentation as well as the progression of disease. And of course with this comes further challenges in making sense how to treat and help people with MND. As an example, when a person is diagnosed with ALS, they told that they might survive for two to five years. But within that two to five year survival, there's a small group of people who may pass away within months following their diagnosis, whereas some individuals may live for 10 or more years following that diagnosis. It poses massive challenges for the person providing the diagnosis, for the team supporting the individual, but more importantly for the person living with motor neuron disease as they begin to plan for their future. Research teams and clinical researchers are taking on the challenges, making sense of all the different types of motor neuron disease, and they are working really hard to improve not only the diagnosis, but also to provide people with an indication of what they might expect from their MND. So I guess the question now is, who is getting motor neuron disease? In 2015, a very comprehensive survey was made of all Australians to figure out who an Australian is living with motor neuron disease. At the time it was found that about 2,100 Australians were living with MND, and it's safe to assume that a very similar number of Australians have MND today. Now looking within this group of individuals with MND, it was found that the majority of people, about 60%, were male, and so it's thought that motor neuron disease predominantly affects men. However, it's important to recognize that as we get older, as the population gets older, the prevalence between males and females with MND becomes about the same, and so really it's only in younger age that it's considered to be a male dominant disease. The other thing to recognize is that people as young as 20 have been diagnosed with motor neuron disease, and so it isn't a disease that can affect anybody across the full spectrum of adulthood. However, as is demonstrated here, the prevalence of MND does increase with age. Now what's not illiterate on this graph is that some people in Australia are more likely to get MND. When we think about the causes of MND, people very often remind that a small portion of people, about 1 in 10, will have a family history of MND. And for those individuals or familial cases of MND, people carry a gene in their family that increased their risk of motor neuron disease. Here is a very nice schematic that was presented very recently in the journal article that summarizes the testing of most common genes that contribute to motor neuron disease across different continents. The authors have provided information on sporadic motor neuron disease. So this is the information that's contained within the outer circles and familial MND. So this is disease that is observed across families and that's summarized in those inner circles. I imagine the first thing you've noticed or may have recognized is that the genetic contribution to familial disease across the different continents are quite different. For example, if we look at Asia, you'll find that within families, the majority of patients there will have a mutation in a gene known as the soju. Whereas if we compare those individuals to Australia, a majority of people in Australia with their family history of motor neuron disease will carry mutation in a gene known as the C9ORF72 gene. Now the other thing to realize is that the C9ORF72 gene is also observed in people with sporadic motor neuron disease. And so from this information, we now know that mutations in genes like the C9ORF72 gene could contribute to sporadic onset of motor neuron disease and therefore these mutations aren't necessarily carried from parent to child. Now the other thing to recognize is that the C9ORF72 gene is not just observed in motor neuron disease. In fact, a very large proportion of people who present with a disease known as frontal temporal dementia also present with the mutation in this gene. And discoveries around the association between C9ORF72 and the prevalence of motor neuron disease and dementia has led to our improved understanding that MND itself actually also exists along a spectrum of degenerative diseases that can impact things like thinking. And we now talk about people resisting across a spectrum between MND and FTD. So the other thing to recognize on this picture are the gray circles where areas shed in gray. This represents other genes that are less prevalent and therefore may not be tested for or genes that have not yet been discovered. And if you have a look at it, these gray areas are quite prevalent in both familial cases. So these are people carrying a family gene or a family history of MND as well as sporadic cases. And so with this we have to consider one of two outcomes. The first one is that not all of the genes that are known to cause motor neuron disease have yet been identified. The second outcome is that maybe something else in our environment is causing motor neuron disease and that's not necessarily directly related to a gene. Now the most likely scenario is of course that both of these factors work together to increase risk for motor neuron disease. In fact, research suggests that there are many genes out there that may not alone increase risk but work alongside each other to increase risk for MND. And just as with any other disease, for example diabetes, our genetics has a big role to play in our likelihood of developing disease through increasing our risk for getting a disease. But it's not until we start experiencing life, not until we start getting older that we accumulate all this risk. And so with time or with age, we increase the likelihood of getting motor neuron disease and of course if we carry a gene that already increases our risk for getting motor neuron disease these effects are going to be compounded up to the point where we develop the disease. Before I go today, I'd like to add that while this recording talks about MND as a disease of the brain and muscle, it's important to recognize that MND can impact other parts of the brain. Some people can impact their thinking and their emotions and it can cause high levels of apathy as well as anxiety. Added to this, MND impacts muscles differently across people with the disease and so some people experience high levels of disability, others find their breathing deteriorates rapidly whereas many people struggle to swallow and speak. And so we put together all of the different ways in which motor neuron disease can impact the individual. We have to realize that no one experience is going to be the same. For the person living with motor neuron disease, this can pose a significant challenge. To help people with motor neuron disease, a focus of research is to improve our understanding of different ways in which MND can impact a person but also come up with new and clever strategies to try and minimize the impact of disease. And ultimately, through improving our understanding of who gets MND and what causes MND, there is hope that we will develop treatments and preventions for motor neuron disease. And so as I go, I wish to thank all of the people and all of the organizations that support us as we work towards the world free of MND.


Practice is hard to come by once the season starts. I mean, what are some of the things that you guys were drilling down on trying to tighten up? Concepts, principles we want to be, and being committed to those throughout 48 minutes instead of 24, 30, 32, whatever. Just being more, I guess, consistent in what you're doing. When you look at the offensive tape from Philly, did you feel that that kind of drought you went through was about creating advantages less or maintaining them? It's a combination, it's a combination. When we created, we didn't sometimes convert early. We got a couple of good looks, and any of those droughts there were times we got plenty of good looks, and it kind of just slows down your pace and rhythm makes your second guess a little bit. You try to, I think the mindset is you want to really focus on getting a good one, but it can take away from your aggression and your pace. So just remaining committed to playing with pace. We haven't been scoring in transition too well, so getting back to doing that, and then just sharing a ball and being decisive. This is, you guys have had one of the tougher schedules in the league to start.   One we got to defend. You don't understand what they want to do and how we can best take that away. I mean, that's what a big part of the league is about. And then be able to spin that in the transition opportunities and buckets on our own and just continue to play aggressive and free and understand that we're gonna get good shots and just keep shooting them if they're not falling. As when you look at your shot profile since you've come back early, are you getting the looks that you would want or, and or you just kind of, if you are getting them or you just kind of finding your way from, you know, having the lost time, you know, little bit of both, I think I'm finding ones that I want. I'd say a disproportionate amount of them come up a little short that left the hand feeling good. So it's just something I got to address.  So I don't really feel like I'm not getting quality looks or, you know, I'm completely out of rhythm. I'm catching them in rhythm, I'm shooting them in rhythm and they're feeling good leaving the hand. So that's all I can do and just keep playing that way. With Atlanta, one of the differences this year is they're playing a little faster and Jalen Johnson's in the starting lineup. I mean, how are you going about addressing them that was maybe different than when you played Atlanta? Just being aware of that, you know, being aware of different personnel groups, you know, Johnson's taken on a bigger role. So being aware of how he plays and how he wants to score in addition to the fact that he's shooting the ball well better than he had previously. So being aware of that, obviously the head of the snake is Trey Young. And so, you know, taking him out of positions that he's comfortable in and making it harder on him and then paying attention to those roles, being in position and just contesting everything. You guys assessed the film defensively. Are there any areas that are sticking out that are contributing to you not being where you want to be? I'd say one of them is just physicality. Physicality and then just a slight second, third effort and covering for each other. I think a lot of it is. You know, head on the swivel trying to be in the right spot. But I think we can touch teams up a little more.