Alright, so so topics that I have were here and I'll just share my screen and we can go off the shared screen topics that I have for Jenkins documentation office hours are. Okay, so Jenkins contributor summit. Jenkins 2.271 change log and 277.1 change log and upgrade guide and then she code Africa. Sponsorship status report. Yes. Yeah, they got you got response on that nobody's ever responded to me on my other thing I even pink her in directly to see if I posted it so. Yeah, it was a bad idea. Well, I, yeah, and I, I'm not going to claim one way or the other. I had specifically poked them in slack and then asked the question and then was willing to poke again and had the additional benefit that Alyssa was also helping with the poking. So, so multiple pokes, maybe the magic solution. And really nothing to report officially so but but conversations look promising for at least one corporate sponsor. And that's that's a good sign. Yes. And then Mark will is willing to coordinate project proposals for the Jenkins project. So, so any other topics from you contributor summit change log and upgrade guide and she code Africa. Looks good to me. Okay, so then let's talk contributor summit the crucial thing that I need Vlad silverman can't be with us today he's he's out on an unavailable away from his desk. So, the question I had for you is, I saw that you hadn't registered for the contributor summit yet, and Vlad hasn't registered. I preemptively assumed you're both registered anyway and put you on the list. But now the question is, when would it work best for the for you, Meg, for us to do a contributor summit documentation track for one to two hours, either Tuesday afternoon, or Wednesday afternoon your time. I'm pretty flexible. Step back, I have, I don't know what we're doing what's happening Tuesday and Thursday mornings I got that I didn't know I was supposed to register for something so yeah and and my expectation was that if you didn't register because you and I had talked about it so much it didn't matter that you didn't register no requirement that you need to register no expectation that you would register. I was using the registration just as a way to pull people, which areas were interesting to them. I know yours documentation and which times were available for them and I know yours in general it's afternoons in in US time zone, you know in California time zone afternoons. So what I was trying to do here is say, Okay, if we met at this time tomorrow, or this time Wednesday with that work okay for you or is an hour later better or two hours later better. I think let me. Let me go check my calendar but okay, I think my afternoons this week my mornings look I've. Okay, what happens at these sessions that are for me started seven in the morning. You actually don't particularly need to attend those. Oh, my hero. Well, I can tell you what happens in them so the first 90 minutes of the Tuesday session will be a summary of the results from the last 12 months of development work in Jenkins. Very valuable, but it's just a summary and you could watch it later. It'll be recorded okay absolutely and then the last 30 minutes is a coordinating session, where we find the times when the tracks will work best for track participants and since you and I are already doing that. There's no reason for you to be up at that early hour of the morning to attend to attend that session so. So the intent here is let's, let's not even assume that you will attend that session or the Thursday session because the Thursday session will just be a summary of the results of all the tracks. Again you can watch the video of that you can watch the recording of that. So in these afternoon sessions what happens in those. Those are the working sessions where we talk about where we're going where we review, for instance, will do review exercises around the, the framework or the outlines that I'm going to assemble hopefully on site. We'll do discussions about hey, what would it mean to have search site search enabled on the Jenkins documentation site. What would it mean to have an improved site search on the plug in site. And those kind of questions will discuss with Gavin Morgan, and others Gavin happens to be an exactly your time zone and he tends to prefer your, your style of working hours, at least a little closer to yours than to mine as he's a good candidate for the Tuesday afternoon or Wednesday afternoon session as well. Okay, looking at my schedule. I have one meeting tomorrow from two to three and it's a very, very flexible when it could easily be moved. Okay, so that I'm open. And right now it's your time it's three. Um, yes. Okay, so it's so Tuesday afternoon after three after 3pm works for you is the same for Wednesday Wednesday afternoon. Yes, I would say afternoon on either really because the it's just no well and I were just going to go over front matter for the courses. Okay, and it's you know, she just threw it up as a time and said, you know, move it I don't care. Okay, so that it's as good as any other time but there's nothing just two of us and all right great so and I'll, I've still got to check with Vlad to see what his calendars like I know and I don't know Jonathan's either. Jonathan I think strongly prefers this time slot because of his work schedule this is just after his working day has ended in Brazil. Okay, so my bias is towards choosing this time slot again because I'd like Jonathan's input he's one of the key players in the site search questions and right hey what are what are the things that work well and what don't. Okay, so. So that's that was the crucial thing for me. And then just as a reminder day one starting session is a 90 minute overview, and then 30 minutes coordinating the track meetings, and we know there will be two docs tracks, at least one for Europe, Europe and Africa. And one for West Coast US. Okay, I'm actually three o'clock California is like 7am isn't it in Australia and. Okay, I didn't know that but that's interesting. I think. I think the Australians ran. I'm just saying that that that late afternoon one might let us say that it was open for Asian Pacific to. Yeah, so can invite can welcome Asia Pacific. Asia contributors at that time. I'm also welcome. I'm also willing to meet during a time that works very well for a contributor from Asia if they come. That's that's one where I've got several that have expressed interest from Asia specifically from India in documentation and I want to send them a meeting, send them a question saying hey you've expressed interest in this. Would you like to meet at this time or at this time to discuss further. Some of them, some of them didn't actually I should show you well I can't show you just a minute let me turn off. Let's see am I screen sharing I am right. Yes, yes. Okay, so I'm going to briefly pause my sharing. Bring something up and show you this really now I guess I can't because we're recording, but I've got what I've got is the people who have registered have provided. So the, the people that have registered have provided their preferred times. When they can meet, and I want to use that. Use that to suggest time to even before we start the meeting tomorrow because you can imagine 3pm UTC is terribly early for the US West Coast, and almost unbearably a bad time for Asia Pacific right for Japan. It's that's just, or Beijing China that's like the dark middle of their night. And so, so many of them who might have been contributing who might have been interested may not be available or willing to attend that open session, but they might be willing to suggest hey if you could meet at this time, Tuesday evening or Wednesday evening or Wednesday morning whatever. They might be might be willing to contribute so. So I'm going to offer ask that question later today to them in an email. Now, what am I expected to do in these sessions. Be a listen, comment, discuss and bring your ideas. Somebody else is leading right who knows what I will lead right I'll be leading the docs. So, so I'm the I'm the leader for the docs sessions and for the platform sessions. And I have some some draft agenda ideas that I've assembled and I've got more agenda topics than we will then will reasonably fit in a two hour session. So, so we've got a lot of topics you know hey how do we improve contributor onboarding. How do we add site search. Google summer of docs do we want to do it. Those kind of things and I've got a bunch of those as candidates current outline review process. That's the one we had discussed over the course of the last several weeks hey we need to. Let's talk about the chapters in the Jenkins handbook, and which content goes into which places in those chapters and which content doesn't fit in a chapter. So I think we've got lots of places where good dialogue between us could really help. Right, right. Oh and if you'll be there. You know, I mean I have ideas but I'm still.  Well, and I just had experience with was who was it Janet Janet Gregory I think it was who introduced me to a tool that that I may try as an experiment in the docs. I think it's called Jamboard. Google. Yeah. So it's this post it's post it's on a big whiteboard digitally. So we may do something like this in the docs in these docs sessions just to try to get ideas collected etc. So, so I've now learned a new tool and having a new tool I may have to see if this problem is worth hammering it. So. So yes, so do we know. I mean, we have are these people like glad and Jonathan who mess a lot with tools or they a lot of writers or. We have, we have two or three different categories of people involved right so Jonathan. Let's take, let's take going from East to West. So, Zina is has been predominantly a writer but has has a little bit of tooling experience but predominantly writing for us. Then Kristen whetstone, lots of tooling experience she wrote the thing that the original implementation of the thing that extracts pipeline documentation, and makes it publishable on the Jenkins that I oh site so lots of coding and tooling has been a connection in the in the Czech Republic has lots of tooling experience but I'm not sure he'll attend. Then as we come further we've got me who I've done mostly writing not tooling. And then you and Vlad, where it's a mix of writing and tooling right Vlad's done, done some tooling and, and certainly plenty of writing. And, and then we've got a number of people whose names I simply don't recognize, therefore probably first time contributors fabulous. Well, if, if they attend great.  Jonathan, Denise, Jonathan more ice as well is a is clearly a tooling expert who's also done some writing, but it's his real forte is clearly tooling he's very very good at it. Okay, so we've got a mix and, and we'll try to shape the conversations to fit whichever group is in that particular session so if, as I suspect in the Europe and Africa session we get Jonathan and Zina, we will likely likely spend about half time tooling and half the time on content and structure, because Jonathan was the initial initial one who helped us through a content and structure exercise so he's interested in that but he's also deeply interested in search and search and other tooling. Okay. And then the, the US West Coast when I think will be dominated by writing portion, unless Gavin chooses to join and if Gavin chooses to join, then we'll talk pretty deeply about what search means, and what he's learned from the plug in site, where he implemented search using a commercial search engine. So, so that's an awful lot of words to say we'll, we'll adapt as we go. Right, just kind of want, you know, wrap my mind about what the sort of parameters are so. Right. And then. Yeah, for my schedule. Anything from noon until 3am is a no brainer, but I can be flexible on the other sides of that so. Okay, excellent. So, very good. Okay. So I think we covered that the crucial parts are there. I've got actually maybe I should show my slides let's talk about the doc slides because I've created some slides for the contributor summit. And I would love to have feedback on them. If you want to if we can just go two or three minutes through them it's it's like like one or two slides and see if I missed something. I'm good for whatever summit here it is. Okay, so here is the slide deck. And we'll have welcome and intro why we're doing this what's the schedule. And then we skip rapidly down to Jenkins releases Jenkins user experience. Okay, so here's my piece. Oh, I need to put artwork on this just a minute. Okay, which, which Jenkins artwork do we want to choose. I don't know I still want I want Jenkins holding a book and Jenkins with a. Yeah, and I don't know which is the one that is the closest approximation to that already use that one for platform. I think I like the the one with the rapier the sword here. Because that's my preferred one so far because we don't have one with a book. Right. I've used this one before. So I'm going to go ahead and just grab that one for now. Okay. And if we get a better one we can always insert a better one later. Right. Because we did have we did have one from somebody in in the in Asia if I remember right where they had a, a like a scholar kind of thing it wasn't a book. Yeah, that's if we're looking for training yeah we don't see a book one. Okay, so there we go. All right, so what I said was hey, we've had made great progress on migrating documentation to GitHub, over half the plugins have migrated, which is actually quite amazing. With as many plugins as there are and in the varying states that they're, we completed Google season of docs, and that means we've got dramatically better Kubernetes Kubernetes documentation thanks to that work from xenobu car. Do you want to slide. What's that. Do you want to mention what was accomplished out of season of docs. Yeah, good. Kubernetes Jenkins on Kubernetes. Bernadies. Is enough of a car. And special thanks to Gavin Morgan. Gavin Morgan for tooling. Oleg Natasha for promotion tutoring. Wiki migration in progress, slow progress needs structural help. And twice weekly, we've got Europe and Africa to attending regularly. And we've got US West, US West Coast, two to three attending regularly. I don't know where Jonathan is today, but I know where Vlad is he was unavailable so. Three to four attending regularly couldn't we. Yeah, yeah. The year we've had a lot of times when Vlad and you're on a dinner roll. That's that's fair. Good point. Okay. And then on the what's next in documentation I said, Hey, we want improved site search on the plugin site. We want site search for the Jenkins docs site. Change log automation. And I don't know how to, that one makes me a little nervous because that one really needs Oleg and I'm not sure he's available. But I'm going to put it there just in case. Okay. Okay. Inventory the current documentation. And proposed document proposed destinations. So this is the, this is the work that we've described earlier. And improving the contributor onboarding experience that one is, is definitely a need. We've seen with Xenob that the documentation development has to have a for for most convenience you need a Linux computer and that's not something every contributor has Linux or macOS and again that's particularly in, in what you might call underserved communities. They're more likely to be running windows than anything else. Right. Okay, anything else that you recommend there I will double check these tonight but your suggestions are welcome. I went along improving the I'd like to see us getting more new contributors into the doc stuff. But maybe that's implied by that industry. Well, let's add more contributors I like that. Yes. Yes. The real the real goal is add more contributors maybe we should say it that way. And we need to improve the contributor onboarding experience because otherwise they may arrive and leave. I like the current contributor onboarding experience if one is running Mac or Linux is that good. It is. Yeah. This is a windows issue. Yeah, so she called Africa's she called after a project ideas. Okay, you're going to have to split split the slide don't you. Yeah, and really maybe we should do that already is admit that it's going to be a split, because what there are more contributors because that stuff up there is sort of known and in place, and then this other stuff. Yeah, I like that. Very good. Okay. I hope to well and inventory the current documentation really needs a converse, you know, more discussion what does that mean and why are we doing it. These are sort of pie in the sky going future those are other things that are sort of in progress sort of known. Right. Yep. Good yeah so the yeah I like that because these things. I'm quite confident we're going to make happen. Right. We're going to make things so that it will be a push. Yeah, some of this will probably happen but you don't know exactly what part. Right. Yep. Okay, very good. Excellent. All right so let's. Okay, anything else on contributor summit. Looks good to me I will listen and learn. All right, so next topic was Jenkins 2.277.1 change login upgrade guide and that's a. This one is there are four major areas changing in 2.271. That is table configuration UI changes. From the table, the HTML table to div transition. Then there's the some HTML internal changes from the jQuery update. Then there is the authentication the security framework update from a CG to spring security framework. And there's one more that is oh dear what is the fourth topic there. Oh yes, extreme upgrade. And on fork. Sorry for using a non word. So, so those, those four need need some alert and discussion and framing them in user terms, and the release candidate is scheduled to be available. Wednesday, the 24th with final delivery release. And then for March 10. So this one, the change log and upgrade guide it would be very desirable to have it ready for the release candidate. So that people can review the release candidate and review the upgrade guide and the change log. Now there's also additional benefit for others with this that, for instance corporate products oftentimes can base their change logs on. Change logs on the Jenkins. Whoops on the Jenkins open source change log. And so I have people who are asking from a business perspective, hey, when do we have the change log available. So, further motivation to get this thing done. I love to have reviews of it, but the reviews are somewhat complicated because it's done using a, it's a data driven change log that has a very specific style guide. Daniel Beck has been my primary reviewer and he's absolutely wonderful reviewer with Daniel back what else you need. So, but there's the style guide and it talks about rules and regulations. And then the change log itself appears here look like this. So this is how the change log looks, and the upgrade guide is in a also accessible from that same page. What happens with documentation changes that might be necessitated by new features. Is it expected that whoever contributed the new features updated any documentation or Yes, so if they're well depends on what you mean. So, for instance, if there's something that is changing a core component, then then it's expected that they will submit new features to the documentation to support that that change in the core component. Jesse Glick for instance submitted as part of the, the extreme and the, the, let's see, it was extreme, and it was extreme. Yeah, CG as part of that he submitted two different blog posts, or a blog post that then I supported with another one so this was his blog post on pay here these major changes coming. This is what it means and this is where you go for more information you go to either this page, or you go to this page. You go to see if there are open issues you click these links to see okay, any issues open, none for that one. Any issues open there, none for that one. Okay. I haven't even looked. Do we have screenshots all over the play the, the change in the doing the tiling for the managed shaking page and all that sort of thing. Are there any screenshots that have been impacted by that all over and we do and those have not been updated so, for example, we did just Zina just submitted the updated Jenkins installer for windows screenshots and they are correct and complete. But for example, the, any pipeline screenshots or let's take a different one pipelines probably a poor choice because it's actually not largely not affected by, by this 2.271 7.1 but if we were to look instead at system administration if there are any screenshots here. We expect them to be now be out of date because because things have changed let's see what we've got here so for example, monitoring doesn't have any screenshots, securing no screenshots. Oh maybe they've gotten clever and cut back on the screenshots. And given the relatively low, low small amount of information that's available in these, and their focus on administrators it's it's uncommon for these particular things to have screenshots. Okay, but any place that does for example if we look at managing Jenkins, the managing plugins, it's probably got yeah, here you go. Here is a here is a screenshot of the managing plugins page. And if we look at remember that page I'm now going to bring up the current Jenkins page that looks, I do know what it is that you don't have any lists there. Well yeah so let's let's see this so here's manage Jenkins manage plugins. And this is available and it looked for find bugs, other than how amazingly fast it is. If we look at this. You'll see a rather different user experience there so let's maybe drag this. Let's put them side by side. So there's one. And now you see, okay notice there's a message about deprecation. There is information here about when it was released, that is no long that is not in this screenshot version number so yes we definitely need an update to our to our screenshots, and we haven't done it. I think the pros around it probably needs to change to. So how is that handled I mean, obviously we can't always get that at the release, but do we at least generate an issue that this the section needs to be updated or we do not commonly that's a good point that a review of the sort of as an example here we go this from the web UI page this HTTP proxy configuration screen will look quite different with 2.277 so now, if I go there and let's go to the plugin manager and first notice that Jenkins is not catastrophically broken on a narrow window I love it it's brilliant. Yeah, go to advanced. Okay notice the difference between these two pages so here we've got the field is left edge oriented and expands to fill the whole space, instead of this have a label and be require a minimum width. Right. So now with this thing I can actually shrink this, and it still works make, and it doesn't put a horizontal scroll bar in it and. Oh it's much, much better, but it is different, definitely different. No improvement. And the other question because we don't have versioning right and huge numbers of people are not updating so what happens to the old people they've just lost their documentation. So what they do is they see a screenshot that is more attractive than the screenshot that they have and now I, I did that as a test case with with a certain plugin that I maintain. And, and have had no complaints at all about it. Oh good. So this thing has been switched so that all of its screenshots are now. Oh, here we go. I changed this screenshot as an example. This is the new UI. And yet, there are old screenshots in here that I still need to take again. So, so this is a good example of needs more work to update the screenshots to reflect the new UI because the new UI is much more attractive in terms of its layout, then this layout is great. So, so when did the screenshots get updated. They don't. Okay, unless somebody does it. That's maybe we ought to put that as as a topic, because really. So screenshot updates updates based on the 2.277.1 user interface, and that that might be an excellent candidate for a she code Africa project project to get better screenshots to get. You know, you had all the plugins and stuff a lot of those were good first projects but this is another thing that would be good for somebody with coming new to it. Right well and, and this is this is more of a documentation effort than it is a plugin code development effort. Right. So we could also do pipeline pipeline examples submitted to to plug in source code as as a as a another candidate and that would be more development focused but with an HTML spin on it. Right. Whereas this one is mostly doc with with a doc. And all strikes. Good. That's, that's a good one. Thank you for helping help and discover that. All right. So, let's see anything else to discuss on 2.277.1. I'm good if you got what you need I don't have to produce this thing. I've got to spend the time on it today and tomorrow and squeeze it in between in between things so yeah I think I'm set. Good. All right. That's very promising actually the notion that we could use she code Africa contributors as a way to update the documentation for the screenshots would be really attractive. It would be how many do we have. We have the one do we have a group of people in she code Africa. It depends on how many are funded and, and which projects they select, etc. So, I, I don't know right now and they won't know until they see how many corporate sponsors they get. Okay, I just think it would be nice. My, my impression is that women tried to code in Africa are often feeling rather alone. Yes, have some people go while you're wonderful that you can do all that stuff that it might be a chance to let them form sort of their own little sub community. Right and I think that's what she code Africa is doing right its goal is to form exactly those kind of sub communities. Yep. Okay. I propose we call an end here and I'm going to get back to work on the change log. Sounds good. Holler so you'll let me. So I'm not going to get up at seven in the morning tomorrow and Thursday and you're going to put something on my calendar. Absolutely, right. If you are you, you've only got one thing to conflict on Tuesday afternoon and if you need to conflict with it do I can move that so great. And I will what I'll do is I'll send email to Jonathan to Vlad to you and to several others proposing a time for Tuesday or Wednesday and asking for for responses back. And then, then we'll try to work that out before before the session starts tomorrow. If it doesn't work out before the session start starts tomorrow at 7am I will work it out in that session, and then send you the link so that you can see it when you get up fabulous. Alright, thanks. Thanks so much. See you tomorrow then. Bye.


I can't love you back. Don't give me that look. Do you think this is easy for me to do? Just go please


personality disorder or B.D.P. for shirt. First, people with B.D.P. usually feel everything is unstable. Your relationships, moods, thinking, behavior, even your identity. With borderline personality disorder, your self-image goes and even your likes and dislikes may frequently change in ways that feel confusing and unclear. As with most disorders, B.D.P. is treatable so you don't have to lose hope. Individuals who struggle with borderline personality disorder can be highly sensitive. They have a dialed up never system because they are highly sensitive, they can quickly react to things and find it difficult to calm down when upset. This kind of unstable emotions often leads to relationship struggles for sufferers and they could also indulge in impulsive and reckless behaviors which they would blame themselves for later. It is possible to overcome B.P.D. There are effective treatments for B.P.D. You can do certain things to help you get better until you get back in control of your thoughts, feelings and actions. If you think you have B.P.D. here are some things you should know about it. 1. Borderline personality disorder often causes symptoms like extreme mood shift and uncertainty in how a person views themselves and others. When a person has B.P.D. they usually find it difficult to stabilize their emotions. They feel unstable in their relationships, moods, thinking, behavior and as well as their identity. According to Mayo Clinic, B.P.D. affects how people think and feel about themselves and others enough to negatively impact their daily lives. According to Francesca Perplechikova, PhD assistant professor of psychology in psychiatry at Well Connor Medical College, people with B.P.D. don't just experience mood changes. This shift can be so severe that make a person feel overcome by massive waves of emotion. And according to the National Institute of Mental Health, NIMH, the stimulus for these extreme emotional reactions can be minor like a loved one living for a business trip. Many people without B.P.D. have a fear of people that like or love living them but people with B.P.D. often experience this so intensely that they have a hard time trusting others and will cut people out of their lives. 2. B.P.D. affects about 1% of people in the United States. The 2007 National Comorbidity Survey Replication published in Biological Psychiatry examines 5,692 people to know how many people were struggling with B.P.D. The study found that while the prevalence of any personality disorder was around 9%, only 1.4% of respondents met the diagnostic criteria for B.P.D. in particular. 3. People with B.P.D. often have other mental health conditions. According to the National Comorbidity Survey Replication, it's 4.5% of respondents with B.P.D. had a co-occurring mental health disorder. According to NIMH, the nature of these comorbidities varies from person to person and can make recognizing B.P.D. difficult. For example, intense episodes of depression can be a symptom of B.P.D. but they can also result from a condition like Major Depressive Disorder or Bipolar Disorder. Francesca Peraplechikova, PhD, says, in case of something like a substance use disorder, it may be a negative coping mechanism to deal with painful symptoms or B.P.D. In the same way, the feelings of abandonment and alienation from oneself and others along with a lack of close and stable relationships may lead to depression. 4. Bottleine Personality Disorder and Bipolar Disorder are not the same thing. B.P.D. and Bipolar Disorder are similar in some ways. For example, Bipolar Disorder also causes extreme shifts in mood and behaviors. According to an expert, these shifts are primarily between depressive and maniac episodes having an abnormally elevated and energetic mood or hypomanic episodes which also involve usually high energy and activity levels but to a lesser extent. Also, the fear of abandonment and unstable personal relationships that are typically inherent to B.P.D. isn't in the diagnostic criteria for Bipolar Disorder. 5. People with B.P.D. are at an elevated risk for self-harm and suicide due to a mix of intense emotion and impulsivity. NIMH claims that along with self-harm, societal ideation and behavior are significantly more prevalent among people with B.P.D.  It is crucial to know that the rate of suicide attempts in this community is so elevated. Some sources say as high as 60-70%. The number of completed suicides is thankfully lower than it could be. Francesca Preperechkova, Ph.D., added that when people have B.P.D., they may self-harm because it feels like instantaneous relief for heightened emotions. Dr. Dixon Gordon, Ph.D., a clinical psychologist and assistant professor who studies B.P.D., at the University of Massachusetts, Amherst, says similarly, Someone may attempt suicide as an impulsive means of coping with the deep emotional sufferings B.P.D. can cause. 6. There is no single cause of B.P.D., but experts believe that several key risk factors are involved. According to the NIMH, research suggests that a combination of hereditary, neurological and environmental factors increase a person's likelihood to having B.P.D. As NIMH stated, if a family member has B.P.D., you are more likely to have it. But no known gene is linked to the condition. It also appears as though the brains of people with B.P.D. have structural and functional changes in areas linked to a things like emotional regulation. But it's not clear if those changes are a cause or result of the condition. When you consider factors of the environment, many people with B.P.D. report instances of childhood trauma including abuse, abandonment and unstable relationships with their parents. 7. Some experts advocate for diagnosing B.P.D. in adolescence while others prefer to wait until adulthood. According to Mayo Clinic, there has been general hesitation in diagnosing personality disorders in those under 18. Sometimes, what seems like B.P.D. can simply be part of a child or teenager's emotional maturation. 7. Reports say clinicians are discovering that B.P.D. can be detected in children and adolescents. Possible signs are similar to those in adults and include impulsive rakes taken. Frequent angry outbursts, continuous interpersonal issues, markedly low self-esteem and repetitive self-injury or suicide attempts. The earlier clinicians intervene, the more likely they are to help. 8. The first line of treatment for B.P.D. is therapy. Francesca Pryplechikova, PhD, says the goal is to help our clients build up emotional regulation muscles so that they will be able to withstand the impact of those emotional waves. We cannot take away their emotional reactivity, but we can give them skills to better respond to the emotional reactions. NIMH added, one method for this is dialectical behavioral therapy, DBT, which combines acceptance and mindfulness of one's emotional state with coping skills for those emotions. Cognitive behavioral therapy, CBT, which can help people with B.P.D. identify and manage their emotions and behaviors is another common option. 9. It can be hard for a person with B.P.D. to trust their therapist, but that bond is often foundational to recovery. Pryplechikova says, this is why therapists treating B.P.D. typically emphasize acceptance and validation. There is an important distinction between accepting a statement or behavior. NIMH says, in addition to this, one-on-one model group sessions led by a therapist can also help people with B.P.D. learn how to best interact and express themselves to other people. 10. There are not any medications specifically recommended to treat B.P.D. There is no benefit yet to using medications to treat B.P.D. primarily. But as Pryplechikova admits, psychiatrist may prescribe medications to address certain symptoms that some people experience. They may include mood stabilizers for emotional instability. Also, someone who is struggling with B.P.D. who also has clinically diagnosed current disorder such as anxiety, depression and PTSD may take medications to treat those conditions. 11. B.P.D. is often stigmatized even among healthcare providers. A 2013 review of available literatures published in Innovations in clinical neuroscience discovered that certain mental health providers maintain false and harmful perspectives on B.P.D. Ordinary people can believe this myth too. Daxon Gordon says, one of the most pervasive beast perceptions among professionals and non-professionals alike is that people with B.P.D. are intentionally maliciously trying to manipulate those around them and their displays of extreme emotions or self-harm. This is false. These symptoms come from mental illness. They do not come from someone who just wants to manipulate others. 12. People with B.P.D. can be empathetic and lovely individuals Pryplechikova says, extreme emotional sensitivity presents with serious challenges but there are also benefits. People with B.P.D. are often able to understand the feelings of other people to a greater degree. Many people with B.P.D. are usually creative because they have a deeper and broader experience of human emotions from each to draw. According to Pryplechikova, B.P.D.s are really fun, creative, compassionate, beautiful people. 13. With solid therapy and hard work, the long-term outlook of people with B.P.D. can be bright. 14. Remission in B.P.D. is defined as meeting two or fewer B.P.D. criteria. Research shows that remission rates are incredibly high. A study of 175 B.P.D. patients published in Archives of General Psychiatry in 2011 found that 85% remitted within 10 years. The researchers said that most of the change occurred in the early years. A researcher also said B.P.D. does not have to define anyone. It's treatable and there's help out there. If this video has helped you better understand borderline personality disorder, subscribe to our channel for more helpful videos. We love you.


Hi everybody, Sean from jaspyscasebreaks.com here doing the random number block randomizer for 2020 illusions 8 box intercase break pick your team to dolphins packers eagles cults and Patriots So we've got our list of customers here from Gary down to Chad with last spot mojo and our numbers from zero down to nine As you know with random number blocks We randomized customer names one through and zero through nine Everybody gets a number if you end up with number three you get all cards with three being the first number next to the slash on the left Side of the slash so for example the card is thirteen out of ninety nine three out of twenty five forty three out of forty nine Ninety three out of ninety nine and so on number three will get the card all redemption cards go to the zero spot Even if it is a known one-of-one redemption It will still go to the zero spot all in person one of ones would go to the one spot There are unnumbered cards that we will would will randomize to one person in the break for all of these teams at the end of the break itself, so Dice roll to randomize the list six and one seven times One and seventh and final time from David down to Chad and seven times on the numbers Seventh final time from four down to eight So David with four Jason with six David David Baker with four Jason Johnson with six David Tran with two Dijonna Cardona with zero Gary Muglock with nine Kyle Evode with seven thong vu with one Gary Muglock with Five Sean Maddock with three and Chad Boone last spot mojo with eight Quick trade window Very quick trade window speak now forever hold your piece. No trades Perfect Dijonna with spot zero you get any and all redemptions even known one-of-one redemptions thong Obviously, we'll get any in person one of ones. That's the randomizer That was the random number block randomizer for 2020 illusions eight box inter case break pick a team two For the dolphins Packers Eagles Colts and Patriots. I'm Sean Jaspies case breaks calm illusions pick a team two coming up next


And the National Drug Law Enforcement Agency wants stiffer penalties for drug trafficking. The NDLEA wants the removal of the option of fines for drug offenders. The agency's chairman Brigadier General Buber Marwa said it had worrisome that some of the officers lose their lives in the cause of battling with drug traffickers while in the end. And some of these offenders went taking to court to just find and later returned to the same business. Marwa explained that the drug problem in Nigeria is massive, adding that an aggressive reduction in drug supply should be embarked on. According to him, the National Drug Use Survey of 2018 indicated that 14.3 million Nigerians representing 14.4% of the country's population used psychoactive substances aside from alcohol.


Hello, I'm Steve Nunn, President and CEO of the Open Group. Welcome to Toolkit Tuesday, where we highlight the various components and leading experts of the Architects Toolkit, a collated portfolio of the most pertinent technology standards for enterprise architects. During the series, I'll be calling on a number of recognized experts who will bring their particular insights on how to most effectively use the various tools in the Architects Toolkit. We'll have a mix of interviews, panel sessions and pre-recorded presentations along the way. While all standards of the Open Group are designed so they can be adopted independently of one another, the greatest value for an organization can be derived when they're used in unison. The sum of the parts should be greater than the whole. In the Architects Toolkit, we have collated a portfolio of the most pertinent ones for architects together, all in one place. For most of these tools, certification from the Open Group is also available, so practitioners can demonstrate that they have the skills required and recruiters can take the guesswork out of the recruitment process, all backed up by our Open Badges program. Our contests are the most important thing to do in the architectural cycle is think. And not just up front, but all the way around and all the way through. Why? So that we as architects genuinely understand. For me, this starts fundamentally with the context. Do we truly understand what we're looking at and what the ask is? To answer that as an architect means exploring and challenging our own understanding of what the situation is and what we've been asked to look at. Any options that we consider, any decisions we make from then on are reliant upon that understanding. So how can you test your understanding? Well, one way is, could you explain it to many different audiences? The client, the customer, the development team, the executive, of course. But what about your best friend?  Hello everyone and welcome to this week's Toolkit Tuesday. Great to have you here wherever you are in the world. I can see the chat function is already getting going with people telling us where you are, which those of you who are regulars will know we love to do. So please keep that going. It's Toolkit Tuesday, I should say today, isn't it? Wherever you are in the world, it's apart from those of us who've already moved to the 23rd of February. It's either 2222 or 2222, depending on where you are. But yeah, one of those special days, date-wise.  We'll kick off shortly with our main presentation, but just before we do, those of you who are not familiar with the WebEx tool or familiar with our Toolkit Tuesdays, the way that we would ask you to ask questions of our main speaker today is through the Q&A channel, not the chat channel, the Q&A channel. So keep the chat going amongst yourselves and whatever you want to communicate with your fellow participants today. But the Q&A channel is the one where we will look first for the questions for the speaker today. And if you can't see the Q&A channel, click the three dots in the bottom right-hand corner of your screen and you'll see the option for Q&A and click on that and then you'll have it there. So please ask questions that way. And without further ado, I'll move on except to thank Paul Holman of IBM, one of our regulars, one of our experts on Toolkit Tuesday, stressing the importance of thinking, particularly as an architect, but we all need to make time for thinking, don't we? When we're bombarded with emails and slacks and other kinds of messages, then it's hard sometimes to find the time. So a great reminder, Paul, thank you. So on to the main presentation today and I'm delighted to welcome to Toolkit Tuesday Dr. Stephen Davidson. He's Chief Scientist for Systems Architecture at the MITRE Corporation and has been the Chief Architect on MOSA-based projects relevant to the US Air Force, sorry, the US Air Force, the Navy and the Office of the Undersecretary of Defense. Steve has been called one of the founding fathers of SOSA, which is the Sensor Open Systems Architecture, and served as the Chair of its Architecture Working Group and as Vice-Chair of the SOSA Consortium Steering Committee. He was also deeply involved in the Open Group's face consortium and served as the Chair of its Enterprise Architecture Steering Committee for several years. Steve has also helped several other open systems architectures including DirectNet, OMS and Victory. And today Steve is going to talk to us about MOSA, explain what that is and take us through our best practice for developing MOSA-based reference architecture. So a warm Toolkit Tuesday welcome from the Open Group for Dr. Steve Davidson. Welcome Steve. Great to see you again. Thank you. It's good to see you too Steve. So I'm going to be talking to you about a best practice for developing MOSA-based reference architectures. And first I'm going to explain that a reference architecture is absolutely crucial to achieving goals of the modular open systems approach, which is what MOSA stands for. And most open system architectures are actually reference architectures. As Steve mentioned, I've been witness to and involved with the development of many open system architectures and as you might expect, different teams that are creating these open system architectures have taken very different approaches and often a few mistakes, repeatable mistakes have been made. So part of my reason for leaving this presentation is to help future reference architecture developers avoid making certain very hard to recover from mistakes. In particular, hacking out interfaces and defining messages way, way too early in the process. So I'm going to begin by defining MOSA. This is not my definition. This is the first and I say best formal definition of it. You're reading that. I'm just going to say boiling it down to its essence. MOSA is about modules that encapsulate functionality and the interfaces that connect them. So think of them as building blocks in the glue that bind them or bricks and mortar. MOSA was started initially as a way of getting the U.S. government out of a mode of buying monolithic systems, which were hard to upgrade incrementally. It's very appealing because through modularization and abstraction, it allows you to make modifications or upgrades to a system without impacting the rest of the system. That is, you can replace an individual element or module with minimal or no alteration to the rest of the system. You can replace that incandescent light bulb with an LED light bulb without having to replace or change the lamp in any way, shape, or form. As I mentioned, MOSA was originally intended to benefit the U.S. government, but it turns out to be a win-win for both the procurer government acquisition and the supplier, developers, contractors, vendors. For the procurer, MOSA enables technology refresh. It can be used to extend the life cycle of the system, and it also is useful for creating a more competitive landscape. From the producer or developer perspective, it helps with strategic sourcing. It reduces the risk that R&D investments won't go in the right direction because you have a template, the open system architecture, to work with. It also creates a more egalitarian environment in that developers have a seat at the table as open system architectures are defined. Open system architectures are typically defined through either industry consortia or government industry collaboration. MOSA as a concept had been kicking around for a very long time, and there were a number of attempts at getting traction, but adoption was slow. It involves changes to the way systems were procured and defined, and just plays inertia, held things up. So all of these efforts that were implemented to try to get MOSA adoption didn't go anywhere. The U.S. Congress got tired of waiting and essentially baked it into the law, that is the National Defense Authorization Act, which funds the U.S. Defense Department, and it essentially said that all systems undergoing certain developmental steps, at the time only major programs, had to be aligned with the modular open systems approach as of January 1st, 2019. Now, right after that law went into effect, the secretaries of our Army, Navy, and Air Force all got together and produced a joint memorandum that said, you're going to do it. Shortly after that, the Army, Air Force, et cetera, issued their own memorandum and made it very clear that MOSA was not optional. So I mentioned before that MOSA is about modules and the interfaces. So this would be, for example, the diagram of a MOSA-oriented system. You have a set of modules, and these modules are connected through key or well-defined interfaces, such that a module one in this particular picture could be replaced by a third party, as long as its functionality and interfaces aligned with the standard definition. So a module encapsulates functionality, exhibits behaviors at the interfaces. The interfaces are the physical and logical touch points. They are where signals or information is exchanged, could be a mechanical or electrical connection or a thermal connection, all of which are interfaces. And I should point out that in many communities the word module is synonymous with a circuit card. A module doesn't have to be a physical entity. It could also be a chunk of software. As long as it's encapsulating functionality and has well-defined interfaces, it is a module. The Braybox concept is fundamental to the adoption of MOSA and the win-win for industry as well as government. In a nutshell, it says that while what a module does, the function's encapsulated, and the interfaces and how it appears at the interfaces are fully defined, what goes on, that is how those functions are instantiated, is completely up to the developer and is part of the developer's intellectual property. It's nobody's business but the developer. So it's not a black box, it's not a white box or a clear box, it's a gray box. So for example, the architecture can specify that a light bulb produces a certain type of light. When powered on, it screws into a certain kind of socket. How that light is generated is the choice of and purview of the developer. And if an organization invests their R&D money and develops a better light bulb, they can do that without fear of intellectual property theft or they can reap the reward, the return on investment for their R&D investment. I should also give you a little bit of background on reference architectures. Reference architectures, they define, they constrain, they guide the development of instance architectures. So reference architecture is typically very broadly defined. An instance architecture is unique to a particular environment, let's say, air, land, sea. But a reference architecture identifies those common elements across all of those instance architectures. And then from those instance architectures, you may have specific designs. And one design might be selected by an acquisition organization and that becomes the contractor developing that particular system. The key aspect of the reference architecture is that, I guess I have my little laser pointer here. Yep. So that, for example, this instance design and this instance design, this one might be for the Navy and this one might be for the Air Force, they have lineage and connection so that there are aspects, architecture features that this one has in common with that one such that, for example, the light bulb used in this one can be transferred and used in that one. So you can have common sourcing of parts, common sources of suppliers, but it also opens up the environment to third parties. So the reference architecture is defined around a set of domain-wide needs, the objectives of the reference architecture. And we're going to cover that in just a moment. Now, it's important to recognize that the reference architecture has to be treated as a superset architecture. Now, what I mean by that is there may be functions in this instance architecture and then finds its way into this instance design. That isn't needed in this instance architecture and this instance design, but the reference architecture has to accommodate all of that. So one way of considering that is, as an example, my car is not a convertible. That is, it doesn't have a cloth roof that retracts so I can enjoy the sunshine on a nice sunny day. But the dashboard for my car has a place where, had it been a convertible, there would have been the buttons. Right now it's just blanked off. So the dashboard for that car is a superset dashboard that accommodates both the convertible version and the hardtop version. In the same way, the reference architecture has to accommodate all functionality that could be instantiated, but some functionality is optional and doesn't have to be used in particular environments. Now, I mentioned that my reason for giving this webinar is that there are pitfalls that people often are subject to. Two of them are listed here on the screen, defining interfaces before they clearly understand what's at either end of the connection. And the other one is going into messages without having an underlying data model. So if you create an architecture with a pile of messages and there's no organizing principle or data model behind it, it quickly gets out of control. And if you define interfaces before you have a clear idea of what's at either end of the connection, you're not necessarily creating an architecture that's responsive to the most needs for which the architecture was defined in the first place. So the process, this best practice that I'm going to describe is illustrated here. We often call this the blue box process and it consists of three phases. The first phase is establishing the foundation and I'm going to deep dive into each of these in a moment. The second phase is defining the modules in a way that are aligned with the goals and expectations of the foundation. And third in the process is defining interfaces. So the red text on the right hand of your screen says it all. Interfaces exist in service of the modules, not the other way around. So let's talk about the foundation. First, the foundation is stakeholder driven. Now a stakeholder is any entity that uses or is impacted by an architecture such as the developers, the acquirers of the systems, or the end users of the systems that will result from the architecture. You guys are probably have heard of Steven R. Covey's seven habits of highly successful people. And number two is begin with the end in mind, which is why use case understanding is crucial. So it's a stakeholder driven process. And so what we do is we say, what do the stakeholders want out of this architecture? And the answer is there's a vision, they have a set of goals, etc. What constitutes good for the architecture? These are quality attributes, quality attributes like portability, modularity, reusability, etc. There are a variety of quality attributes that are common in most environments. There are the architecture principles, which are the run rules for how the architect is developed, architectures developed, and then those all important use cases that identify how systems based on the architecture are going to be used. That information is used to define criteria for a functional aggregation into the modules. There are many ways of skinning the cat. And if you've got five different developers in a room, they will probably affinitize functions into modules in very different ways. So key to doing this well is defining the criteria by which functions are aggregated into modules. Now, let's talk about what these function modularity relationship looks like. So a module consists of one or more functions. And the idea is there are different ways of you could have defined modules so that function h, d, and m are in module one. Well, why would you do it the way it's illustrated here? Well, there's a reason. The reason has to do with the criteria. So the process starts with identifying based on the use cases, how a system is going to be employed, all of the functions that the systems are performed. And again, this is a superset. So not all use cases are going to require all functions. So you take them all together. You then aggregate your functions based on a set of criteria. We'll talk about that in a minute.  And that takes time and effort. But once you've got your modular decomposition nailed down, you have a solid foundation for defining your interfaces. The criteria that you might use would be based on what you're trying to get out of the architecture. Now, there are techniques that people use for defining modularity that are based on simple things like the number of interfaces. Well, the number of interfaces is a criteria. But it's a brute force criteria. If you're trying to do things like maximize operational life, make your modules independently procurable or testable or very important, protect intellectual property so that the functionality that might be part of someone's IP isn't extended across modules and therefore exposed at the interfaces. You're going to you're going to create a different criteria for how you aggregate those modules. So you take those modules, those criteria, you look at the functions and through a series of iterative processes, you affinitize the functions into a set of modules. And those modules then become the definition that you use or the foundation for what you use to define the interfaces. Every function in a module has some sort of an input requirement and it produces some kind of output product. So the process by which you develop your interfaces are you look at what the input needs are and you look at the output products and you look at what is the producer of those input needs and what is the consumer of those output products. So a very, very simplified version of the same three functions or modules I described before. In this case, function H has an input need will call a tasking and is provided by function F. It then produces a measurement request and that's goes to function C. Well, it turns out the function C is inside the same module as function H, whereas function F is in a different module. What does that mean? These guys that are highlighted in blue are inter-module interactions and the combination of all of those interactions then become the foundation of the interface definition between modules. In a MOSA based open reference architecture, you don't care about or you don't specify internal processes to the module. That's the developer's IP. What you care about are the inter-module interactions. The interactions that go between modules and the combination of those interactions become your interfaces. So let's do a toy example. Let's say that we have some system which has a pile of functions. We use a set of criteria and we affinitize those into that same set that I showed you before. Each function has its input and output requirements that you use to define the interfaces. So let's define what those interfaces are. So in this example, module one and module three connect to one another through interface A and there are a number of interactions on that interface. It doesn't matter. This is a toy problem so these things can be anything. What we're showing here is that interaction A1 on interface A has a source in module one and a destination to module three and then these other guys. And by building up a table like this, you now create the definition of the interfaces. So now we know what gets conveyed. The next question is how? Every interface should be treated as three separate aspects. The physical or the medium, the wire, the connector, etc. The protocol, which is the method used to convey the data or signal and the payload, which is the signal and data itself. When you've defined those informational requirements that go between module one and module two, three, etc. You then have defined the foundation of your interface definition. And now the question is, well, what's the story behind the signal or data structure? Another best practice and one of the reasons why I don't recommend jumping into message land is, and I mean by that is just throwing messages around and creating a pile of messages is to develop a data model. I do not have time to get into the details of the data modeling, but it typically operates at three levels and div one, div two, and div three, or the DODAF, the Department of Defense Architecture Framework designations for those. The conceptual data model identifies the type and nature of the data. The logical data model addresses content and things like if your angular measurement is at, you know, zero to pi. Is it minus pi over two to plus pi over two, etc. And then the physical data model is the actual structure and it's important to recognize that for every one of the logical entities, you could have more than one physical data model. That is, if you're conveying information about position, you could have three or four different ways of representing that depending on the precision and the requirement. And also, the precision related to the data need or you can represent in one case it using an integer notation in another case, you know, double point, double precision floating point type of a representation. The protocols are the means by which you're carrying the data. So a simple example might be if you're conveying a phone number, do I pause after each field or do I give you the whole number? And then your messages then become the combination of the protocol used to convey and the payload itself. So just to quickly wrap up, the best practices first take a top-down approach and establish the foundation. If you don't know where you're going, any road will get you there. That's not a good situation. So you have to clearly define what your objectives are. You then define the modules and after that use the module definition and the input output requirements to define the interfaces. So that's my quick summary of the best practice. And at this point, I will yield the floor to Steve. Thank you, Steve. We're still stopped or I know you could talk for several hours on this subject and our audience would love that to be the case. But we only have a certain amount of time. Thank you very much for that. Great stuff and some great examples along the way. I'll go straight into straight in some questions. Something you said fairly early on in your talk was about the color of boxes. It's not a black box or a white box. It's a gray box. The question came in. Why is it a gray box and a black box? I don't know what happens inside the box. Well, you do know what it does. You do know its functionality because the functionality is defined by the reference architecture. The functionality says it associates tracks or data detections and forms a track. It combines certain pieces of information and produces a product. Those are defined by the architecture. The methodology used for producing the product, however, is the gray part. You don't know that and that's none of your business. It's the developer's decision. Thank you. We've got a very international audience for this broadcast today. Has there been interest in Mosa from other countries to your knowledge? Yes. I know that the UK Ministry of Defense is very interested in it. My understanding is that there's interest and implementation in both that and NATO. I don't have specifics only because my orientation has been US-centric. I can't tell you specifics, but I do know that, for example, the open group is working with the Ministry of Defense to try to incorporate MOD personnel into the FACE consortium and also SOSA. Great stuff. Next question. I can see there are some coming in on the chat now. Does Mosa apply to COTS packages? Apply to what? COTS. In fact, COTS is enabled. One of the things you can do, on one of the first slides, we talked about the fact that Mosa is based on widely available consensus-based standards. And the COTS community has developed things like open VPX, Vita standards, and so forth that then become part of the definition of these open systems architectures. And what that does is enables COTS developers to, instead of being in a position where they have to develop custom cards for every application, they can develop COTS cards that are aligned with the open systems architecture. And now, instead of building it for custom versions, off-the-shelf becomes extremely viable. Good stuff. This is a broadcast from the open group, so down to get this question, I think. How well would you say Togaf supports the creation of Mosa? The methodology defined in Togaf aligns pretty well. For example, understanding the mission, understanding the objectives is fundamental to the foundation of the methodology that I described. You don't jump into the technical architecting until you understand what you're trying to do. Requirements are at the center of all of these things. And an open system architecture that's well-written will define, in a normative way, the requirements for how the module is defined, the performance, the behaviors of the interface, etc. So it aligns quite well. Great to hear. Quick one, do you think that Zope is a good technology to realize, Mosa? I'm not familiar with it. Not familiar. That's the trouble with specific technology questions. Last question, then, Steve, will be respectful of yours and other people's time. It's a comment, but I'm sure you'll have a comment in return to it. I do worry about this clean sheet approach being a barrier to adoption by companies with existing products. Looking for an upgrade path that doesn't throw away too much of existing investments. Can you comment on... Yeah, so I mentioned at the beginning that industry has a seat at the table. And so a well-defined reference architecture or open systems architecture engages stakeholders from the beginning. And therefore has to be aware of and cognizant of developments that are already underway. It's very important also to make a, I'll say, a gradual transition. There are a lot of systems that are out there. And if you want to incrementally upgrade them, you don't throw them away because that's costly and wasteful. What you do is identify where you can mosify, which is not a true term. I just made it up. But mosify a system by incrementally enhancing it through defining and carving out a modular portion, defining a clean interface definition around that module, and then gradually and incrementally bringing it into compliance with MOSA. Okay, great. Thank you. I said last question, but this one I had seen come in and it's an interest to myself. So I'm going to pick it. How is conformance or compliance against the reference architecture assessed? At the module level. So what we typically see is that a module is aligned with a standard or a open systems architecture and that can be individually tested at the interfaces for functionality and adherence to the API, the connector, the signal, the protocol, et cetera. That's how you do it. I know that some people think in terms of, well, you can also assess an entire system. And yes, that can be done, but MOSA is fundamentally based on modularity. So it's if the building blocks are all aligned, then the system as a whole will be aligned. Yeah, thank you, Steve. And for me, MOSA is such a great example of things we've seen elsewhere over the years of the customer pool. If the customers say you are going to do this to the suppliers and they have enough pool, then it happens. And it's great to see the consistency of demands from the major customers for this. So great stuff. And thank you in the meantime for all your work in the face consortium and the social consortium more recently. And great stuff, Steve. A number of comments coming in saying great presentation. Couldn't agree more. Thank you for joining us today and big virtual round of applause for Steve Davidson. Thank you, Steve. So that's almost wraps up for today. Just a few thanks, obviously Steve and to Paul Holman for his EA minute video at the beginning. And to thank you all for your attendance today and for the great questions. Plenty of questions coming in. Sorry, I couldn't get to all of them, but trying to keep it close to 30 minutes. A little over today, but it was worth it. We could obviously have spent more time on questions. So thank you very much. Please join us again in two weeks time. That's March the eighth for our next toolkit Tuesday, where my colleague, Dr. Andres Sokal will be talking about Actional Supply Chain Security. Actionable supply chain security, important to everyone. And some lessons from the trenches to tempt you into that one. So please join us in two weeks. March the eighth for a session on Actionable Supply Chain Security on Toolkit Tuesday. Meanwhile, thanks for joining us today and take care wherever you are. Have a good day. Bye bye.


Cardiorenal syndrome, CRS, is a complex interplay between the heart and kidneys that occurs when one organ is affected by another's dysfunction. It can be divided into five distinct subtypes depending on the cause of the dysfunction. Type 1 CRS is caused by acute kidney injury due to cardiac dysfunction, while types 2 and 3 are caused by cardiac dysfunction due to acute kidney injury. Types 4 and 5 are caused by chronic kidney disease leading to cardiac dysfunction. Pediatric populations have been found to be at higher risk of developing CRS than adult populations. Common comorbidities seen in pediatric CRS include hematologic, oncologic, cardiology-related side effects, muscular dystrophy, and pneumonia bronchiolitis. Treatment of CRS typically includes diuresis, extracorporeal fluid removal, and treatment of the underlying etiology and comorbidities. This article was authored by Subbal Kumar Pradhan, Harsha Agnani, Rama Safadi, and others. We are article.tv. Links in the description below.


Fantastic, we've had a great experience. Everyone's really friendly here, really helpful, and because people are casual and relaxed it makes you feel more comfortable and confident in what you're going to do. We've always loved coming in here. Absolutely, absolutely, it's so nice to be in a space where you get different levels of expertise come together to create a great product, so this is why we like coming here. Yeah, it was a really good experience today, I was a little bit nervous coming in here, I don't do too much filming, but all the staff here made me feel very welcome and comfortable and the facilities were fantastic, so there was no hassles or setbacks, we just jumped straight into it and gave a really professional performance which we appreciated.