Trini girl natural welcome to my channel I just wanted to come on and do a little quick work review and demo of these two new Sotanical shampoos, so I have the wash and comb detangling foam and I have the sherry building but a shampoo so I do have Clip of me using both and I guess I'll just run them as I talk about them The first one I use was this one the wash and comb detangling foam and I will admit I had a PJ attack when I heard about this one because I was like what detangling foam some new wonderful thing I gots to try it and of course, yeah, the ingredients look good I'm not a fan of that he'll look aside and I'm just getting more and more convinced of that But other than that it was like a lot of moisturizing ingredients. I was I really excited to try it Water out of the juice and I give net to be chiller as to click welcome Irish more So just look really good, but basically it didn't work as a detangler So I put in and it was going good at first and I was like, oh, okay I'm becoming tired and then it suddenly kind of froze up on me and my hair started Panicking my hair was getting stripped. So I had to abort abort and just resided out immediately And then proceed to deep conditioning So I do think this might be nice as a regular shampoo, but it's not something that can spend 15 minutes in my hair I just need to Shampoo rinse and go on about my business So that's how I'm going to use this one My for me my personal Recommendation is don't try the time with it. But if you have it just use it as a shampoo So I have some people also give good reviews of this just using it regularly as a shampoo and not try the time Go with it. So don't try to be a hero like me. Just use it as shampoo and You know, maybe that's a pretty good one. It's definitely cleansing. I can say that much for it The next one I have is the sherbet but a shampoo and again, I got excited with the whole butter shampoo idea So a shampoo that was like a butter and like a solid kind of thing because you know, usually Shampoo is like running watery liquid stuff, right? So like a butter shampoo She knows how to get me like I don't know how to get me because I just love innovative creative new things And she just loves creating innovative creative new things. So it's a kind of match made in Peter heaven Except my wallet may not agree But yeah, I try this because it also looks interesting and of course the ingredients also look good I love the Ayurvedic herbs and everything This was actually the opposite of this one because this one was super moisturizing and conditioning But my scalp just didn't feel cleansed and this one super cleansing but too strong So too strong and too mild for me, I guess. So I'm probably gonna try and mix for them I don't know we'll see but basically I have to try one go Just trying to get it to do something and my stout just didn't necessarily feel clean My first impression of this is great slip and moisture, especially for a shampoo But it didn't really make my scalp feel as clean as I like my scalp to feel I work out and I just want my scalp to just be singing and just happy with me at the end of a week and right now my scalp is still like I don't know if I like it. I don't know if we're friends. First impression I kind of almost want to reach for another shampoo or co-wash just to make my scalp cleaner But I don't want to push it. So I leave it like this and maybe mid-week and my co-wash if I need to or something I think this would be better as a co-wash So I recommend using this as a co-wash if your scalp already kind of feels clean and you just want a little refresh Then this will be good for that. So I did like it my hair felt soft and moisturized and stuff I just wish it was a little more cleansing a little more I don't know usually when I use like she said to blueberry co-wash and Camilla was caramel co-wash My scalp feels clean after and feels so that my tub doesn't feel itchy You know usually it's itchy when I'm just like dirty. So I don't know like this just never really got there for me I'm not usually a share-butter person either but a share-butter. I hope didn't affect me Maybe that's why I didn't like it. I'm not a share-butter person. Share-butter just sticks and it's really hard to get rid of So maybe that's why my hair didn't feel clean enough like this just couldn't overcome the share-butter in it Both that have look a side of the share-butter on my radar now Well been on my radar, you know, but I on my radar and I have to stop paging and just buy myself because it look interesting But anyways, it's like a nice fluffy whip texture. I really like the scent. It's like this really Musky it smells like a sexy Trini kind in the 90s like This kind of musky cologne kind of like those incense sticks kind of thing I do have the same I love the texture and everything I love the concept I just wish that for me have turns my scalp a bit more and it never formed for me either I don't know.  I didn't reapply product or anything But you know my hair have been stressed put it that way with you know, everything I have been stressed my hair I've been stressed. So but it did say that if you love that formula serious and so on conditioning and whatever So I expected it to form and it didn't really form for me But at least it didn't ship for sure and strengthen and nourish I guess know that I really close way in there I'm gonna try the cocoa one because I have the cocoa butter shampoo and the conditioner So I'm gonna try that as a wash day video coming soon. I'll let you know how that works I'm probably gonna try it when my scar doesn't kill me So I'll be able to test it more as a cool wash and let you guys know So have you tried any one of them? What did you think? Let me know in the comments What's your favorite shampoo? Do you have a favorite so time because cleanser co-wash? Let me know because I really would like to find so time it goes Cleanser and gel like you know, I'm still kind of looking for those. I like the so time it goes these season evens I'm just looking for a cleanser and gel. Thanks for watching I really hope it was helpful to all of you guys who wanted to review I've been getting a lot of requests for this So I hope that finally you have it my review and I'll see you in the next one. Bye


Hi everyone, Joe for jaspyscasebreaks.com coming at you with 2021-22 panini flawless basketball random hit break number two From jaspyscasebreaks.com big thanks to this group for making it happen Thanks to the people who bought their spots straight up and congrats to the people who won their spots in those fillers You're guaranteed something We'll type in the hits in that blank list there, but first we got to open up the case and show you the hits And that's right. There's four teams left and pick your team three. I did promise that if Those four teams that snapped up before this break is done I'll do that hour-long break before I take a break. My breaks aren't very long So you wouldn't have to wait very long if that sold out out during my break Now are they gonna do a second second happy Gilmore? Maybe maybe use this. Well, it's technically not a merger Between the PJ and live They're actually creating a brand new entity a brand new company. It's highly encased hits here They're gonna create a brand new for-profit company and That entity is gonna get He's gonna get the financial backing of the PIF the public investment fund So and then I don't know what Yeah, I know everyone's been saying it wrong Rex is what I'm saying everyone's mistakenly Labeling it as a merger, but I think that's probably the easiest way to say it but in the Technical sense it's it's not it's three out of five Andre drumming Crazy times for golf. We'll type these hits into the order there Well another train whistle hit for somebody three out of three is I hear Williams rookie autograph But yeah PJ tour and live are not merging together The PIF and the PJ tour are working together. That's that's the Quote-unquote merger I guess Yep, exactly Justin Is Dell curry? 14 out of 15 Steph and Seth's dad Is it just the two of them Desmond Bain 9 out of 15 draft gem signatures The Aaron Fox a fox in the box. That's the 25 6 out of 10 Jalen subs rookie autograph nice and not a 25 magic Johnson Team USA basketball magic Johnson nice last one here is Alperin sangoon 10 out of 15 RPA We saw the player here. All right, so that's one two three four five six seven eight And then the two hits make ten perfect All right, let's see what we got in here. I think the auto was on the right side So the gem should be on the left side Those are Naturally my not lab grown. That's with the small princess. I would like to at least some events They should wear shorts, right? Maybe the Hawaii events early in the year maybe Waste management Scott's they should be able to wear shorts there. That's a that's a fun atmosphere All right, we've got Anthony Edwards 9 out of 10 Nice diamond. All right, and on this side the autograph It's gonna be Excellence autograph excellence. Wow Josh giddy rookie auto 7 out of 15. That is excellent nice, all right The case is almost closed on this break ladies and gentlemen what we're gonna do is we're going to Pause the video. We're gonna type in all the hits and then we'll run the randomizer randomizer names randomize the hits and match Yo, but something so stick around we will be right back All right, welcome back ladies and gentlemen, so we got all the hits typed in we got the drumming the Williams the Dell the Desmond De'Aaron Jalen magic Sangoon and then the two in case cards that Anthony Edwards and the Josh giddy All right, good luck Let's see what you match up with after three and a one four times one two three and Four we got Nathan down to Carl and let's see what hit you get match up with cross your fingers three and a one four times one two Three and a one fourth and final time the eight the diamond on top the drumming out of five on the bottom And here's how it all shakes out For everybody Nathan you got the Anthony Edwards diamond nine out of ten shining bright like a diamond Matthew with the team USA Maddie Johnson autograph to 25 was seen with the Zaire Williams rookie auto three out of three All aboard the big-head Express Jason K with the Sangoon RPA nice to 15 Abraham with the Jalen sucks Autograph to 10 look we got the Dell Curry autograph 14 out of 15 Carl with the Josh giddy autograph 7 out of 15 Missing with the De'Aaron Fox a Fox in the box autograph 19 out of 25 Carl last Bob Mojo Desmond Bay 9 out of 10 and With the Andre drumming dual relic 3 out of 5 all aboard the big-hit Express There you go gang, thanks for watching. Thanks for breaking with us. Oh, we got wax party invites giveaway, too How many two I think almost forgot about that In the excitement of all these hits All right. Good luck again new dice new list top two after Four four again three and a one four times. We'll get an invite to the wax party one two three and four After four times congrats to Abraham and was seen Congrats you you are in the wax party. Check out the details on jazby's case race calm excellent prized list They're pretty awesome stuff. Check it out. I'm Joe. I'll see you next time for the next one. Bye. Bye


Hi, I'm Chuck with Razorback Off-Road. Today we're at the Colorado Overlook on Hell's Revenge in Moab, Utah. And we're just been having a great day out here testing out this new Can-Am Maverick XRC Rockcrawler 1000R. I hope I got all that said right. That's quite a mouthful, but it's quite a competent machine and we're real excited to develop some products for it. So what I wanna talk about first is our folding windshield. As you can see, I got the windshield up. It comes with a manual wiper blade on it. We've got these quick lock features on here so you can quickly unlock the windshield to fold it. We also have these air vents in here like coming up here this morning, we had about a 10 mile run down the highway. We had the windshield up. It was still kind of warm, so we opened up the vents here and let a little bit of air come inside. So it's kind of neat. You get to control the air coming in and out. It also has our no pinch hinges, so it's kind of neat if you, there's no way to get a finger pinched in here. It's something we're pretty proud of. This is our own design. We think it's got a really nice aggressive look to it, the way we've done these windshield tie downs.  Some of the things that I think people overlook when you're picking a windshield is a lot of the poly windshields out here. There's a lot of dust and people wipe them with a towel and create static electricity and then dust gets on it. And you just don't get that with a glass windshield. I also wanna point out this is a DOT approved windshield. So here we're street legal to ride anywhere we want, but this is a great place to lay out your maps or just kind of hang around and visit. I use it as a shooting bench, a place to sight my rifle in off of. Today we're gonna have lunch here in a little bit. We'll have our sandwiches made out here. And it's just a very, very good windshield. We're also proud to say it's 100% made here in the United States by us. Everything except the windshield wiper blade, we're not sure where that comes from, but everything else is built by us. And I want you to know from the heart that when you buy a product from us, you're putting people to work and that's something we're very thankful for. And that's why we put such commitment into the quality of our products because we're not only representing ourselves, we're representing our country. So with all that being said, I hope to see you out on the trail.


Top tips for dealing with the recent pandemic as a foreign English teacher in China. I have been working in China as an English teacher almost for half a year. When the outbreak began, I decided to stay in China. At first I thought it would be like a seasonal flu quarantine back in my country Ukraine, when schools are closed for just a week or two. However the situation got worse, and I realized that it might be safer to stay inside my city than to go through the train stations and airports. Our life here has changed completely in less than in 48 hours. Shops gave no signs of opening after the new year, buses were just passing by the stops on their way to the bus park, communities were closed for the non-residents, in one day you got more temperature checks than in a few months. Every movement has been noted down from the moment I left my community, until I got my final temperature check and was allowed to enter back. Wearing a mask has become something as natural as wearing a coat in winter, or taking your umbrella on a rainy day. Except buying a mask has turned into a quest along with a price increase by several times. However I haven't seen people with no masks for weeks, moreover with no mask on it's more likely that your way into the supermarket or bakery would be closed. Another thing is that everyone who came outside of the town, will be placed under the quarantine for 14 days, so it's better to make sure you have your friends or colleagues, ready to provide you with your favorite cookies. I have to say, the way people here react to the situation amazes me. Despite all the small shops, malls, entertaining centers, and public transport, being out of service since the end of Chinese New Year, I can see people cheering up one another. On the official website of our city, they post articles about our citizens on the front line in Wuhan with praises and grateful comments. Many activities went online one by one, so people can get some parts of their normal life. Advertisements for healthcare activities are everywhere. You can see posts near the shops and entrances to the buildings, inside the elevators, in messages from local authorities, network providers, and of course various groups on WeChat. Fake news raises panic. In my opinion one of the biggest problems, is fake news and aggregated information that raises panic. Most of the messages I got from my friends and relatives, had such questions as will you be evacuated? Do you have enough food? And why aren't you going back? Based on the news they saw about the situation in Wuhan. To start with I live in Shanxi province, which had less than 140 cases. During this whole time, I have never experienced a shortage of food supplies in supermarkets, even in fresh vegetables and fruits. Of course masks and sanitizers became much more expensive and difficult to buy. Schools are shut down. All education establishments have been also closed for the indefinite time. More over kindergarten's and private schools will open last, so it seems at least until April I'm not going to get to work properly. I am an English teacher at the private school which started online classes around three weeks ago, but they are still a bit messy with some network problems or enrollment difficulties. Here again I am fascinated with my colleagues. With the first news of the quarantine, they made some activities for kids on WeChat. We took turns on recording daily videos with learning content, and tips on how to wash your hands properly or short warm-ups for kids. Every day students are supposed to send us audio recording with answers, drawings of keywords, and occasionally some video presentations of their handicrafts. It's obvious that parents took a great part in all this process, but we are trying to keep kids entertained and motivated to learn. Another problem was that we have to quickly create new teaching plans and materials on our own. Everyone expected to get back to work after the New Year holidays, so it's natural that all teaching plans, materials, books, and even personal computers were left at school. Our school is located inside of the Children's Educational Center which was reopened only on the 3rd of March, and only for the stuff. No one was allowed to enter the building for more than a month, that affected not only study proses, but our green friends, flowers were left inside. Here I am glad I took a TEFL course, and it was rather helpful. I used some tips from the ITTT course and even made worksheets on my own. They turned out quite handy in this situation because they can be easily sent to everyone, collected and checked. Foreign teachers in my school usually have a separate program, which is concentrated not only on teaching language, but also on teaching of the values. We aim to create a comfortable atmosphere for kids to encourage them to use more English in an interaction, like using thank you, your welcome, can I, please, and so on. Here again I got great help from my parents when my lessons started. They provided necessary objects for the lessons, so we could interact with kids almost without screed borders. For example, two kids have apples near them, so they easily can have a live conversation which is a role play, so one can give an apple to another kid. Before I started to have online classes almost a month passed. After a few days of being locked up at home, I started to feel bored and tired. I got plenty of time on the one hand, but on the other I had a narrow range of activities to do. Here are some things that helped me to feel better, and even enjoy my time at home. I am used to having my notepad everywhere with me. It's rather useful to know your lessons and meeting schedule, planned activities and things you have to prepare before the next Monday. However it turned out useless for a daily routine. Instead a simple monthly planner has proven to be my savior in this situation. You can pin it on any surface you pass at least a dozen times per day. I simply drew mine and hung it on the fridge. I marked each day with colorful squares for different activities. It got me motivated to fulfill my daily plan, so I could put a check in every square. Wake up at the same time even if you don't have work to do.   Fresh air and cleaning. It's good to have less dust at your apartments anyway. Almost every article about healthcare during the virus outbreak was mentioned the importance of regular cleaning. I marked cleanings on my planner once in two days, and it didn't take me much time to keep my home a bit better. Here in China to get some fresh air, you have to find it first. I have a useful app air visual on my phone, so I know when it's good to open windows and when it's better to shut them. Think about your shopping time. As I said before, I didn't face any shortage of food at the supermarkets in our city. Nevertheless it's still good to avoid lines and mass gatherings at stores, isn't it? I figured out that around lunchtime supermarkets are almost empty, during such called Chinese siesta even during the quarantine. Daily exercises. What do you do when you are at home and a bit bored? Usually you will grab some snacks while watching serials or reading books. If not, then you are either lying or a superhuman. First places to be closed along with schools and universities due to the quarantine in China were gyms, swimming pools, and sport centers. I know that some of my friends got short videos with some exercises via we chat, but unfortunately I wasn't that lucky. Still I have found some good videos on the internet, and I was motivated to put a check in the green square on my planner. Learn something new. We always complain that we don't have enough time to learn a new language, to read such an interesting but long book, or to finish knitting a sweater. Here is your perfect chance. Do it now and later it will become your habit. I have been in China for almost half a year, but my Chinese was still below the basic level. Last month with an Apollo Chinese I made significant improvements, and I am eager to go on. How does COVID-19 affect you? With the improvement of both epidemic situations and weather conditions, I can see more and more people going out and doing some activities inside the community.  We will get over it, learn some important lessons, and go on. Thanks so much for watching. We are ITTT, the leading provider for Teflon TESOL training courses. If you liked this video, please subscribe by clicking that button down here, and click on any of the videos here on the left for more interesting teaching tips for getting certified to teach English abroad and online.


Live from Miami, Florida, it's theCUBE. Covering IBM's data and AI forum. Brought to you by IBM. Welcome back to Downtown Miami everybody. We're here at the Intercontinental Hotel covering the IBM data, AI forum, hashtag data, AI forum. My name is Dave Vellante and you're watching theCUBE, the leader in live tech coverage. Ritika Gunnar is here. She's the vice president of data and AI, expert labs and learning at IBM. Ritika, great to have you on again. Always a pleasure to be here, Dave. I love interviewing you because you're a woman executive that's had a lot of different roles at IBM. We talk about the AI ladder, you're climbing the IBM ladder and so it's awesome to see. And I love this topic. It's a topic that's near and dear to theCUBE's heart. Not only women in tech, but women in AI. So great to have you. Thank you. What's going on with the women in AI program? We're going to cover that, but let me start with women in tech. It's an age-old problem that we've talked about. Depending on what statistic you look at, 15%, 17% of the industry comprises women. We do a lot of events, you can see it. Let's start there. Well, obviously the diversity is not yet there, right? So we talk about women in technology and we just don't have the representation that we need to be able to have. Now when it comes to artificial intelligence, I think the statistic is 10 to 15% of the workforce today in AI is female. When you think about things like bias and efficacy, having the diversity in terms of having male and female representation be equal is absolutely essential so that you're creating fair AI, unbiased AI, you're creating trust and transparency set of capabilities that really have the diversity in backgrounds. Well, you work for a company that has a chairman and CEO that's a woman. I mean, IBM generally, we can see this stuff on theCUBE because IBM puts women on. You get a lot of women customers that come on. And not just because we're female, because we're capable. Well, of course, right, it's just because you're in roles where you're spokespeople and it's natural for spokespeople to come on a forum like this. But I have to ask you, as somebody inside of IBM, a company that I can say, the test to relative to most does pretty well. Do you feel that way or do you feel like even a company like IBM has a long way to go? Oh, I personally don't feel that way. And I've never felt that to be an issue. And if you look at my peers, my lead for artificial intelligence, Beth Smith, who you know, a female, a lot of my peers under Rob Thomas, all female. So I have not felt that way in terms of the leadership team that I have, but there is a gap that exists not necessarily within IBM, but in the community as a whole. And I think it goes back to you want to, when you think about data science and artificial intelligence, you want to be able to see yourself in the community. And while there's only 10 to 15% of females in AI today, that's why IBM has created programs such as women AI that we started in June because we want strong female leaders to be able to see that there is great representation of very technical capable females in artificial intelligence that are doing amazing things to be able to transform their organizations and their business models. So tell me more about this program. I understand why you started it. Started in June, what does it entail and what's the evolution of this? So we started it in June and the idea was to be able to get some strong female leaders and multiple different organizations that are using AI to be able to change their companies and their business models and really highlight not just the journey that they took but the types of transformations that they're doing in their organizations. And we're going to have one of those events tonight as well where we have leaders from Harley Davidson and Miami-Dade County coming to really talk about not only what was their journey but what actually brought them to artificial intelligence and what they're doing. And I think, Dave, the reason that's so important is you want to be able to understand that those journeys are absolutely approachable. They're doable by any females that are out there. Talk about inherent bias, humans are biased. And if you're developing models that are using AI, there's going to be inherent bias in those models. So talk about how to address that and why is it important for more diversity to be injected into those models? Well, I think a great example is if you took the datasets that existed even a decade ago for the past 50 years and you created a model that was to be able to predict whether to give loans to certain candidates or not. All things being equal, what would you find? More males get these loans than females. The inherent data that exists has bias in it even from the history based on what we've had. Yet that's not the way we want to be able to do things today. You want to be able to identify that bias and say all things being equal, it is absolutely important that regardless of whether you are a male or a female, you want to be able to give that loan to that person if they have all the other qualities that are there. And that's why being able to not only detect these things but have the diversity and the kinds of backgrounds of people who are building this AI, who are deploying this AI is absolutely critical. So for the past decade and certainly in those past few years, there's been a light shined on this topic.  And the women in the audience like, dude, no way. And he did the right thing. He goes, you know what, you're right. Any backtrack on that. And that was sort of another inflection point. But you talk about the women in AI program. I was at a CDO event one time. And IBMer had started the Data Divas breakfast and I asked, can I go? Yeah, you can be the data dude. Which was, so you're seeing a lot of initiatives like this. My question is, are they having the impact that you would expect and that you want to have? I think they absolutely are. Again, I mean, I'll go back to, I'll give you a little bit of a story. You know, people want to be able to relate and see that they can see themselves in these females leaders. And so we've seen cases now through our events like at IBM, we have a program called Grow which is really about helping our female lead, female technical leaders really understand that they can grow, they can be nurtured and they have development programs to help them accelerate where they need to be on their technical programs. We've absolutely seen a huge impact from that, from a technology perspective in terms of more females staying in technology wanting to go in those career paths. As another story, I'll give you another point of view, Dave. And that is, when you look at where it starts, it starts a lot earlier. So I have a young daughter who a year, year and a half ago when I was doing a lot of stuff with Watson, she would ask me, you know, not only what Watson's doing but she would say, what does that mean for me mom? Like, what's my job gonna be? And if you think about the changes in technology and cultural shifts, technology and artificial intelligence is going to impact every job, every industry, every role that there is out there. So much so that I believe her job hasn't been invented yet. And so when you think about what's absolutely critical, not only today's youth, but every person out there needs to have a foundational understanding, not only in the three Rs that you and I know from when we grew up of reading, writing and arithmetic, we need to have a foundational understanding of what it means to code. And, you know, having people feel confident, having young females feel confident that they can not only do that, that they can be technical, that they can understand how artificial intelligence is really going to impact society and the world is absolutely critical. And so these types of programs that shed light on that, that help bridge that confidence is game changing. Well, you got kids, I got kids, I have daughters, you have daughter, are they receptive to that? So, you know, I think they are but they need to be able to see themselves. So, the first time I sent my daughter to a coding camp, she came back and said, not for me mom. I said, why? Because she's like, all the boys, they're coding in their Minecraft area, not something I can relate to. You need to be able to relate and see something, develop that passion and then mix yourself in that diverse background where you can see the diversity of backgrounds. When you don't have that diversity and when you can't really see how to progress yourself, it becomes a blocker. So, as she started going to girls start programs, which was something in Austin where young girls coded together, it became something that she's really passionate about and now she's Python programming. So, that's just an example of, yes, you need to be able to have these types of skills, it needs to start early and you need to have types of programs that help enhance that journey. Yeah, and I think you're right, I think that is having an impact. I mean girls who code obviously, does some amazing work. My daughters aren't into it. I try to just send them to Coder Camp too, and I don't do it, but here's my theory on that, is that coding is changing and especially with artificial intelligence and cognitive software replacing human skills. Creativity is going to become much, much more important. My daughters are way more creative than my sons. I shouldn't say that, but- I think you just admitted that. But in a way they are. I mean they've got amazing creativity, certainly more than I am. And so I see that as a key component of how coding gets done in the future, taking different perspectives and then actually codifying them. Your thoughts on that? Well, there is an element of understanding like the outcomes that you want to generate and the outcomes really is all about technology. How can you imagine the art of the possible with technology? Because technology alone we all know, not useful enough. So understanding what you do with it, just as important. And this is why a lot of people who are really good in artificial intelligence actually come from backgrounds that are philosophy, sociology, economy. Because if you have the culture of curiosity and the ability to be able to learn, you can take the technology aspects, you can take those other aspects and blend them together. So understanding the problem to be solved and really marrying that with the technological aspects of what AI can do, that's how you get outcomes. And so we've obviously talked in detail about women in AI and women in tech, but there's data that shows that diversity drives value in so many different ways. And it's not just women, it's people of color, it's people of different economic backgrounds. Underrepresented minorities, absolutely. And I think the biggest thing that you can do in an organization is have teams that have that diverse background. Whether it be from underrepresented minorities, where they come from, because those differences in thought are the things that create new ideas that really innovate, that drive those business transformations, that drive the changes in the way that we do things. And so having that difference of opinion, having healthy ways to bring change and to have conflict, absolutely essential for progress to happen. So how did you get into the tech business? What was your background? So my background was actually a lot in math and science and both of my parents were engineers. And I have always had this unwavering need to be able to marry business and the technology side and really figure out how you can create the art or the possible. So for me, it was actually the creativity piece of it where you could create something from nothing that really drove me to computer science. Okay, so your math engineer and you ended up in CS, is that right? Computer science, yeah. Okay, so you were coded, did you ever work as a programmer? Absolutely. My first years at IBM were all about coding. And so I've always had a career where I've coded and then I've gone to the field and done field work. I've come back and done development and development management, gone back to the field and kind of seen how that was actually working. So personally for me, being able to create and work with clients to understand how they drive value and having that back and forth has been a really delightful part in the thing that drives me. You know, that's actually not an uncommon path for IBMers, predominantly male IBMers in the 50s, 60s and 70s and even 80s who took that path, they started out programming. I just kind of think of some examples. I know Omer Perra, who was the CIO of Etna International, he started out coding at IBM. Joe Tucci was a programmer at IBM. He became CEO of EMC. It was a very common path for people and you took the same path. That's kind of interesting. Why do you think so many women who maybe start in computer science and coding don't continue on that path and what was it that sort of allowed you to break through that barrier? You know, I'm not sure why most women don't stay with it, but for me, I think that every organization today is going to have to be technical in nature. I mean, just think about it for a moment. Technology impacts every part of every type of organization and the kinds of transformation that happens. So being more technical as leaders and really understanding the technology that allows the kinds of innovations and business transformations is absolutely essential to be able to see progress in a lot of what we're doing. So I think that even general CXOs that you see today have to be more technically acute to be able to do their jobs really well and marry those business outcomes with what it fundamentally means to have the right technology backbone. Do you think a woman in the White House would make a difference for young people? I mean, part of me says, of course it would. Then I say, okay, well, there's some examples. Think about Margaret Thatcher in the UK, Angela Merkel in Germany. It's still largely male dominated cultures, but I don't know, what do you think? Maybe that in the United States would be sort of the tipping point. I'm not a political expert, so I wouldn't claim to answer that, but I do think more women in technology, leadership roles, CXO leadership roles is absolutely what we need. So politics aside, more women in leadership roles? Absolutely. Well, it's not politics, it's gender. I mean, I'm independent Republican, Democrat, conservative, liberal. More women leadership, absolutely. Yeah, well, companies, politics. I mean, you certainly see women leaders in Congress and the like. Okay, last question. So you've got a program going on here. You have a panel that you're running. Tell us more about that. Well, this afternoon we'll be continuing that from women leaders in AI, and we're going to do a panel with a few of our clients that really have transformed their organizations using data and artificial intelligence, and they'll talk about their backgrounds in history. So what does it actually mean to come from one of the panelists, actually from Miami-Dade, has always come from a technical background? And the other panelists really etched in from a non-technical background because she had a passion for data and she had a passion for the technology systems. So we're going to go through how these females actually came through to the journey where they are right now, what they're actually doing with artificial intelligence and their organizations, and what the future holds for them. I lied, said last question. What is success for you? Because I would love to help you achieve that objective. Is it some metric? Is it awareness? How do you know it when you see it? Well, I think it's a journey. Success is not an endpoint. And so for me, I think the biggest thing I've been able to do at IBM is really help organizations, help businesses and people progress what they do with technology. There's nothing more gratifying than when you can see other organizations and then what they can do, not just with your technology, but what you can bring in terms of expertise to make them successful, what you can do to help shape their culture and really transform. To me, that's probably the most gratifying thing. And as long as I can continue to do that and be able to get more acknowledgement of what it means to have the right diversity ingredients to do that, that's success. Well, Ritika, congratulations on your success. I mean, you've been an inspiration to a number of people. I remember I first saw you, you were working at Pitchiano's group and you were up on stage and said, wow, this person really knows her stuff. And then you've had a variety of different roles and I'm sure that success is going to continue. So thanks very much for coming on theCUBE. Thank you so much, Dave. You're welcome. All right, keep it right there, but we'll be back with our next guest. Right after this short break, we're here covering the IBM data in a AI form from Miami. Right back.


So, I could make a simple prism I could have a ray of light coming in here try to make it look like as if it were the parallel case parallel rays case if they are all coming in horizontally, then I get some bending here, then I get some more bending coming out. Again each one of these bends here is based on Snell's law which I just covered I am not doing the exact algebra for this example I am just drawing a kind of abstract picture. And um so this is you know just a simple triangular shape you can imagine that it just extends the same way in what we have been calling the z direction. So, it is cylindrical in the z direction if you like and um has a triangular cross section. So, some kind of prism and I could make the upside down version of that may look something like this right. So, that is the behavior of a single ray going through a prism where there is medium 1 then you go into medium 2 let us say and then you come back to medium 1. So, this is essentially the I the principle that is going to be applied um in a continuous fashion across an entire lens. So, if I make a simple spherical lens I get something like the following. Soon I am going to stop drawing pictures and switch to slides because it gets complicated to trace all of these rays of light, but this will be one of the last pictures and say that I try drawing myself. So, so these should be look like circular arcs and there is really another dimension to where these are spherical now. So, these are spherical caps just like the way lenses look that you are familiar with whereas, this was supposed to be just the same outward. So, there is no curvature. I have my let us say I have a central axis for this a kind of axis of symmetry and I have rays of light coming in and I am going to assume this thing that I told you was fictitious which is there are parallel rays coming in and they are only fictitious if you live in a world with no mirrors or lenses. So, I guess we could have produced it through some other means, but if it came from a point light source then this is impossible, but a reasonable approximation. So, we have these parallel rays coming in and when you think about the behavior of these it is like when it comes in and when it comes out it is like having a slice of a prism right. So, that is the kind of thing to think about the slice of a prism and if these rays are coming in at a different angle then I guess it will be a different slice of a prism right. So, it represents all of that somehow it is this prism bending effect, but manifesting itself in very localized ways depending on exactly what the curvature is here right. This is not a curved surface. So, you can predict what is going to happen all the way up and down it is going to look the same, but because this is curved the bending is going to depend on where you are at along the curve here. So, as it goes through the lens we end up with let me draw a another axis here which is should be the center of the lens not very good at straight lines today. You ever have a bad straight line day you know. So, what is going to happen is in this lens is that the effect of refraction is going to cause these rays to bend inward to start to converge and if we make a simple spherical lens they will converge to a point somewhere. Let me just invent the location of that here they will converge to some point and this point is called the focal point. Whenever you hear the term focal point remember that that corresponds to what the lens would do for parallel rays right and I guess I have to start to draw what happens to these rays as they come through it is going to be very difficult for me, but let me do my best here. I will draw all of them of course at the central part of the axis it just goes straight through without any bending right. Something like that I guess I have to match these pictures a bit here I am not really sure I am probably not following the same rays, but get the idea because of course these come from somewhere inside the lens. So, do not think I have my arrows to the left matching exactly the ones to the right, but I think you understand the idea. I will start providing some machine drawn pictures or more correctly drawn pictures in just a bit. So, that is the focal point that they all converge to and this distance here is called the focal length. So, that is how we think of a simple lens in this case as a kind of engineered device that takes parallel rays and makes them all converge to a point somewhere. They do not stop at that point they keep going right. So, you could also continue onward they meet at that point, but there is nothing to stop them from continuing onward unless you put something here what might you put here like a screen perhaps I do not know. So, if you put something here then the light will be focused on whatever you put here. Remember that there is an interpretation in terms of waves I draw the waves in blue here. So, we had parallel waves coming in and now after they get through here they are getting curved in some way right. So, that is another way to look at it is when the rays are being forced to converge through the lens you are introducing curvature now to the wave fronts.  So, so you get this strange effect all right. One more I am kind of afraid to draw the picture let me see if I can just superimpose it on this. Let us suppose I have rays coming in at an angle, but there is still parallel rays. So, let me let me draw a rays coming in at some angles I realized getting pretty cluttered now. So, I just want to point out that just because they are parallel rays it does not mean that they come in perpendicularly right right. The rays are parallel, but they could be coming in at an angle because it could I could imagine that there is this light source that is off at infinity, but it could be up really high right. So, if I am sitting out here in the open air theater watching a big watching a movie on the big screen I could be and imagine that screen is gigantic and it is really far away maybe it is 10 kilometers away and it is enormous and it is a clear day and I can watch the movie like that they are still going to be the top part the rays are going to come in they are almost parallel, but they are going to be coming in at an angle right. So, in this case for an ideal spherical lens they will still converge, but they will converge somewhere else along this line. So, there may be these rays coming in that correspond to some distant feature or object the wave fronts have spread out so much that the curvature has the curvature has turned out the radius has turned out to be essentially infinity. So, that is when we have these parallel wave fronts coming in we have straight lines which is we have parallel lines which is represented by the pink here. So, that everything comes in and we end up with the focal point being I am just going to draw in some arbitrary place down here somewhere. The important thing to note you know is that they converge and they converge to another place along what is called the focal plane right. You know I think when I was talking about curvature going up and down let us see curvature 0 means what straight line, but the radius of curvature would be infinite there right. So, I got to be very careful I think it is part of the confusion in my my my speech just a little bit ago I think that. So, I wanted to say that the curvature of the wave fronts is approaching 0, but the radius of curvature would be approaching infinity. So, make sure I have said the right things at different times. So, it is just those two are inverses of each other even though the names are very similar. All right. So, there are simple formulas for determining the the the focal lengths of a simple spherical lens. And so, I want to go into some pictures of that explain some optical properties and things. We will go back and forth between the board and some pictures. So, this should correspond pretty closely to the picture that I have drawn. And oops I do not do that. Notice that we have the focal length as I have drawn it. There is also a thickness of the lens D here. And note that we have two different radii R 1 and R 2 that correspond to the curvature of the one of them corresponds to the the place where the light first hits which it looks like R 2 in this case. And then there is R 1 oh gosh darn it sorry sorry hold on a minute. The R 1 corresponds to a circular disc and that is the place where the light first hits and then R 2 corresponds to the place where the light hits second. But note that the center of the circle is before the light hits for the second circle and it is after for the first circle. So, to determine the focal point we have the following the lens makers lens makers equation. So, 1 over the focal length is equal to let us say N 2 minus N 1. I am writing it in a little more general form that I have in my notes here, but it should be ok 1 over R 1 minus 1 over R 2 plus N minus 1 no this is the place where I am I am doing it a little more generally N 2 minus N 1 D divided by N 2 N 1 R 1 R 2. And then for let us see N 1 is the index of refraction um let us say outside of the lens they could very clear the ambient um the air outside of the lens. So, outside the lens usually we mean air and usually N 1 is approximately equal to 1. But you can put your lenses under water and it will do something different it will behave in a different way. So, this is the index of refraction for the lens material there is a simple approximation that is often used to this and um I will write that here it is called the thin lens approximation this is much more common now after this approximation where we get rid of this D parameter. So, here we say D is approximately equal to 0 in which case the lens makers equation simplifies to 1 over F equals N 2 minus N 1. So, it is the difference in refractive indices 1 over R 1 minus 1 over R 2 and there is a peculiar sign convention that is used for these R. So, normally when you write R in this kind of geometric picture that we have on the um on the display here in ordinary geometry the R's would always be positive. However, there is a convention here which is for a converging lens which we have just made we have a sign convention which is that R 1 is greater than 0 and R 2 is less than 0. So, this is for a um converging lens I will put lens type here that is the only kind I have shown you so far um for a converging lens. One way to remember that is that the R 1 case is positive because you have hit the surface that that circle corresponds to before you hit the center of the circle and the R 2 case is backwards it is you have hit the the rays of light that are coming into the lens have hit the center of the circle before they actually hit the surface. So, in other words R 1 corresponds to the case of a front side which is an entrance and R 2 corresponds to the case of an exit. So, so these are these are for the for the converging lenses it ends up giving you these signs. So, there is also diverging lenses if you have seen optics before it should not be surprising. So, there is the diverging case where we can make rays of light um instead of converging spread apart and I will just mention the sign convention in this case. So, R 1 in this case is less than 0 and R 2 is greater than 0 and so, you can directly apply the lens makers equation in the original form and in the thin lens approximation to determine the focal point. However, notice that if it is diverging it seems like it should not even make sense to talk about a focal point I have parallel rays coming in and then they diverge, but you can trace them backwards that is what these dashed lines correspond to to um to give a kind of let us say fictitious focal point right. So, because once these rays spray up spread apart they will still all point backwards if you reverse their direction to a common point. So, that is called the focal point of a diverging lens. So, so the diverging lens does not cause focus to happen it is the opposite of that, but you can just reverse the direction run everything backwards and to the left of the lens you end up with the focal point right. Questions about that? I want to let us see. I want to now talk about um a very useful representation called diopter which becomes very handy when combining lenses talking about optical power and then I will give an example of it in terms of the human eye. The human eye is going to be important because it is part of the virtual reality system.


So, hello everybody. Again, I'm Cindy Chicolise. I now work for the Wikimedia Foundation as the product manager for the Media Wiki platform team. And I'm very excited to be in that position. And I'm going to talk a little bit. My talk is called Towards a Media Wiki Roadmap. It's not called a Media Wiki Roadmap because I'm working towards creating a Media Wiki Roadmap, and maybe that'll make a little more sense as we go through my talk. So I'll start a little bit with some historical perspective. As I said before, I worked at the MITRE Corporation for 10 years-ish prior to joining the Wikimedia Foundation. And in my role at the MITRE Corporation, I created wikis for our government customers. One thing that I got asked several times as we were proposing Media Wiki as a solution to their knowledge management needs was, but this Media Wiki thing, is it going to be there in five years? Is it going to still meet our needs? Is it still going to run on the platform that we need in five years?  And the extension question was an easy enough one to answer because that prompted us actually to start open sourcing our extensions to make them available so that even if we, MITRE, were no longer involved in helping folks to maintain their wikis and grow them, this code, the extension code to Media Wiki that we created, would be out there in the ecosystem and other people could maintain it. And I don't know why it's doing this. Oh, wait. That went ahead. Stop. So the extensions would still be available. And they could edit them. They could maintain the code. They could hire other contractors to do so. But the base Media Wiki platform, I kept on saying, you know, the Wikimedia Foundation, you know, I need somebody out there to tell me that Media Wiki as a product, as a piece of software, will still be there. And as open source software, of course, we know that it will be, right? Because you can always, well, I won't say the fork word. But, you know, you always know that you can, you have access to the source code and you want it. But you'd like to know that this wonderful diverse community of software developers will continue to be working on this product and that they won't suddenly say, oh, well, you know, hey, this PHP thing was fun. But I want to now run on the grapefruit operating system using the Pimento web browser or web server, you know, something that's completely, you know, so as a, so me in 2008 to 2016 was saying, we need a roadmap. And I still agree that, you know, this is still me, but it's me in the past. Yay, we still, we need a roadmap. We need to know what layout, what the future of Media Wiki is. So I was really excited in 2017 to see that the Wikimedia Foundation was hiring a product manager for the Media Wiki platform and saying things like this person should be responsible for the roadmap for Media Wiki. That's excellent. I want to do that because I think that that roadmap is so important that I want to be that person that goes and does that. And oddly enough, they decided to hire me even though I was one of those third party community people. And I now work at the Wikimedia Foundation and that roadmap thing I wanted for all those years is my job. And wow, roadmaps are complicated. So me in 2017, I'm trying to pull together all those pieces and create a roadmap. And this is very much a work in progress. And so this talk is toward Media Wiki Roadmap. I will talk a little bit about the information that I'm gathering, why this is a hard process, and what it is I hope to achieve in terms of a Media Wiki Roadmap. And I would love to have all of your input also from your perspective on what would be a useful, what would be useful information to have in a roadmap and what form that roadmap could take that would be useful to you. So what are some of the things that make creating a roadmap for Media Wiki in particular difficult? And I'll talk a little bit about what we're doing in the future and what we've got in progress. But the Media Wiki architecture in some place, you know, you could say, hey, you know, lampstack, pretty straightforward. But when you talk about all of the components, the pieces, you know, how would an extension, if you were to create an extension, reach into the core code and change any given thing? Well, there's this great hook architecture and it is documented, but it can be sort of difficult for folks to visualize the entire thing. So it is quite a powerful architecture that's not completely documented and is a big moving target and it's continuing to change, which is great, it's changing in great ways, but it makes creating a roadmap a little bit more of a challenge. What are the boundaries of Media Wiki? You know, what do we really, when we're talking about the Media Wiki platform is when all of you are talking about using Media Wiki, and you as third party users probably see a different boundary than folks that are using Media Wiki to support Wikipedia at the Wikimedia Foundation. What actually is part of Media Wiki? Is it the extensions? Are they part of the core Media Wiki? If so, which ones? You know, the configuration, how to set up a Wiki farm, that was a big one for me, because I came up with a whole way, you know, scripts and a whole architecture of what the files and directories, you know, and I hated symbolic links so I did it without any symbolic links. Some people do it with lots of symbolic links. Is that part of Media Wiki? Is that structure? Should it be part of Media Wiki? You know, I think that there should be a better defined way of specifying Wikifarms that everybody, because constantly, I think just yesterday, didn't somebody just post a question yesterday about Wikifarms on one of the mailing lists? You know, what is a Wikifarm? How do you define it? There is no reason that there shouldn't be a standard way to set up Wikifarms. But are those, is Media Wiki a Wiki or is it a farm of Wikis? Does it matter? What part of the configuration really is considered Media Wiki itself? Yeah. What parts are core? What are optional components to support? And should there be, should there be several predefined profiles maybe? You know, the Wikimedia Foundation, you know, they, for Wikipedia and its sister Wikis have a very well-defined way of maintaining their configuration that works great for Wikis of that scale. But typically it's not that useful in an enterprise setting. Should there be another profile that people can replicate for an enterprise setting?   Who's responsible for which pieces of Media Wiki? And that's a common one, and that's one that the Foundation is working on. You know, if you find a bug in something, sometimes it's obvious who's responsible for that bit of code, but quite obvious, but quite often it's not. And so, you know, having a good, you know, and some of the code is maintained by the Foundation, some is not. So it may not even be the Wikimedia Foundation that's responsible for a particular piece of code. And so finding out, and certainly if you're using an extension, is the extension maintained? Is somebody going to respond if you ask a question? So all of these things are complicating. And then, you know, finally, who decides the future?  Well, there's a lot of stakeholders in your stakeholders in this. The Wikimedia Foundation, they've certainly got lots of stakeholders of lots of different shapes and colors. You know, so there are a lot of people who care about the future of Media Wiki, and so I guess that sort of, you know, every time I try to define the roadmap, I want to make sure that I'm not excluding some viewpoint. So at some point, one needs to put a stake in the sand and say this is the roadmap, but in a way where these different perspectives are reflected and supported. So I'm going to do, I'm going to talk a little bit more, you know, I talked a little bit about the present, and I'll talk a little bit more about, you know, sort of where we are right now, and I'm going to reach into the past about how we got there, and then I'll talk a little bit. So okay, it's not the normal order of things, but let's talk about where we are now, and then I'll talk about how we got there. So some current work that's going on in the Media Wiki platform, there's a project. How many people here have heard of multi-content revisions? Maybe a quarter of the people here? So there's some people who know it very well. So I'd say the most active project right now, as far as changing the core Media Wiki code, is something that's called multi-content revisions, and it is a project that aims to, for each page, currently you've got Wiki text, which is your, or well, there can be different, also different content handlers for different types of pages and different namespaces, but typically, like in the main namespace, your content pages will have Wiki text as their format. Multi-content revisions aims to allow you to have multiple slots for each page for a given revision, and different kinds of content can be stored in those different slots. So you may have a main slot that is Wiki text, but then have many additional, more than one additional slot that has data, perhaps stored in a JSON format that's additional structured data associated with that. The project, the primary driver behind the current implementation of multi-content revisions is a project called Structured Data on Commons that aims to allow for Wikimedia Commons, which is a Wiki that hosts imagery and video files that are all part of the Commons, and there is data associated, you know, there's XIF data associated with images, and that data is not easily queryable in its current format in the Commons. The idea would be to take that data and make it, using this multi-content revisions, have that data available in slots associated with it. So multi-content revisions in its current form is first addressing the storage layer of how to store that additional structured data associated with pages in the Wiki, and then future work on multi-content revisions will then address how would you edit these different slots associated with a single page in the Wiki. So what's going on right now is that first step, and that involves some changes to the core media Wiki code and the schema of storage of revisions within a Wiki, and the schema change to support multi-content revisions will be introduced, will be included in MediaWiki 1.31, which will be released this summer. And so again, that's the first phase of multi-content revisions, and I mentioned that in part for you guys to think about, okay, so now that this ability to have multiple slots associated with a page in a Wiki exists, what might be something that you might want to do with this capability? And I can think of a lot of things and I'd be happy to talk to y'all later about that, but you sort of to think about, okay, so now we've got this additional capability in core that may be useful if you want to do other things with structured data associated with a page in the Wiki. Okay, so that was the present real brief and now I'm going to talk a little bit about the past and how we got here, and I have to say Corey Floyd who is an engineering manager in audiences at the Wikimedia Foundation created the next two slides talking about the evolution of MediaWiki Core and so I thank him and credit him with these very helpful slides that lead to a current program called the Platform Evolution Program that we hope to work on in the coming year. So before mobile, 2001 to 2011, this should look pretty familiar to y'all as far as a high level architecture for MediaWiki. MediaWiki has the core code, it has a parser in it that knows how to parse Wiki text, it has skins, templates, extensions, gadgets, okay, really sort of a basic, very easy to understand and comprehend architecture. And then people started wanting to be able to view Wikis on a mobile platform in a way that took advantage of the form factor and the fact that a mobile device is different, has different characteristics than a desktop browser and so an extension called Mobile Front End was created and it was used as a way to allow folks not to have, this was another entry point into the MediaWiki back end that would display nicely on a mobile platform but not custom code, not native code for the different types of devices. Then there was this great thing, everybody wanted to have visual editor, they wanted to be able to edit a Wiki page and have it look, not have this transition back and forth between this back end Wiki text format and the nice front end, you wanted to be able to have WYSIWYG editing. And so in order to support this visual editor extension, a service called Parsoid was created that runs on top of a back end called REST base that allowed partially parsed information to be saved to allow very quicky, quick context switching back and forth between the edit view and the reading view of a page. And so this architecture started to evolve and you can see the little bit more complexity is coming into, but now we have this parser down here which is the Wiki text parser and this Parsoid service also and how many folks here have installed visual editor? Cool, lots of you, that's awesome. How many of you all have installed it on top of REST base and got REST base up and working as well? Really? Oh, come on, hang on, put those hands up high.  Yeah, Gerard doesn't count, he works for the foundation. Okay, anybody who didn't work, doesn't work for the foundation that's actually gotten REST base installed and working correctly. Just about everybody put their hands up for visual editor, that's interesting and nobody for REST. So it's sort of hard to install, I tried to. Oh, I should have put my hand up for visual editor and not for REST base. Yeah, a lot of us tried. It's a little bit complicated, it works super great. It is what was definitely needed for Wikipedia to be able to edit and context switch quickly. The folks that wrote it, they know how to install it and it is amazing, but it's a little bit difficult for those of us in the third party community. I guess I was wearing my 2016 hat then to install. But it's great, but it adds a bit of complexity to the architecture. And then there's this mobile content service that was added also to interact with mobile front end and you've got your iOS apps and Android. So things get, as you start adding more capabilities, more features to the platform, the architecture sort of evolved in this way that, you know, media Wiki is great and it does amazing things and Wikipedia is awesome. But it keeps, it's sort of evolved and got a little bit, you know, an extra arm over here, an extra hand over there or whatever. And it's, you know, got a little bit unwieldy. Like an octopus. Exactly like an octopus. And then there's all this other stuff. Yeah, there, yeah. It's definitely an octopus. It's really super smart and awesome with lots of appendages, but a little bit hard to manage. So again, this thanks to Corey. He coined the term just in time architecture. The architecture for the current media Wiki was not so much designed, but it emerged. And it emerged. It's fabulous, but maybe it's time for us to sit back and revisit it and maybe clean off some of those rough edges. It's got some fragmentation. There's a maintenance burden that has been incurred by the evolution. Developer impedance, you know, it's difficult for the developers to figure out what all the different, you know, how to interact with the code and wrap their mind around the architecture as it exists now. A lot of technical debt has accumulated. And the documentation just isn't that good right now. There are parts of media Wiki documentation that are amazing. There are parts of it that are very well retained. There are also cases where the same thing is documented in multiple different places and multiple different ways, some of which are accurate and some of which not so much. So there needs to be some focus on the documentation. Sure. Where's the mic? James, you have one job. So the question is, do you have a roadmap for documentation? Yeah, I'll talk about that. Absolutely. So digging ourselves out of a hole again. Thank you to Corey. So back late last year and really, you know, becoming concrete in December was this thing called the audience's technology working group. So that's an interesting name. It makes a whole lot of stuff to folks, sense to folks in the foundation, maybe not so much to people outside. So the Wiki Media Foundation, two of the primary places where developers sit are a department called audiences, which used to be called product, I think, or something with product in the name. That's really, you know, sort of product facing. And then technology, which is more infrastructure and services. And that's where the Media Wiki platform team lives. So there were a lot of folks who were forward user facing, you know, concerned with features, concerned with things like the mobile apps, who lived in audiences, who wanted to have a simplification of this architecture. And then folks who are in technology as well, who are maintaining a lot of this infrastructure core code, that both sides had opinions about the need for there to be a simplification of the architecture, perhaps different opinions about the way the evolution of this should go. So the audiences department and the technology department formed a combined working group. And I thanked Corey Floyd a little bit earlier for those slides. He stepped forward to actually lead this working group. He's in audiences. I'm in technology, and I was working with him on part of the steering group for this working group. Starting in December, 18 folks from audiences, from technology, and Wikimedia Deutschland. Daniel Kinsler, who's there, has been very actively involved. He's also the lead of TechCom, which is a group that has oversight to large architectural changes within the MediaWiki platform. So Daniel Kinsler is very involved from Wikimedia Deutschland. We had folks contribute what they thought the main issues were with the current MediaWiki platform and ecosystem. And we collected 83 issues. We didn't initially deduplicate them or try to make sure that they had complete coverage of all the landscape, of all of the possible issues that exist. But through people identified what they thought were the most important 83 things to them. And then we went through a little bit of a decomposition of them with 28 dimensions, 28 different types of things that we tried to categorize them. For us to be as a working group to wrap our minds about what we thought that the most important things that we needed to address as we evolved the platform are. And as we were going through this process, we were all getting ready as a foundation to go through our annual planning process. And with the support of the CTO, the head of the technology department, Victoria Coleman, and the head of the audiences department, Toby Negrin, together we decided to create a cross departmental program for the annual plan that also includes community engagement. Am I getting that right? The community engagement department, which is a third department that also has input in the interactions with the community. And so we came up with this thing called the platform evolution cross departmental program or CDP that will take the platform forward. So just how we got to where we are. Victoria will talk on Friday morning a little bit about the Wikimedia strategy process. We have gone through the last year through a process of trying to come up with a strategy for the Wikimedia movement to say where we will be in the year 2030. And that movement came up with a few key goals, supporting knowledge as a service, supporting knowledge equity. And those are guiding principles towards the year 2030 for the Wikimedia movement. And from those principles, those also helped guide what we wanted to support in a software platform for the Wikimedia movement. In addition, going into this, there were these position papers that were written by the audiences department and the technology department saying what they thought the issues were and how we should go forward. And then every year the Wikimedia Foundation has a developer summit. And so we had in San Francisco a developer summit in January and so there were working meetings at the Dev Summit that also helped to inform the audience's technology work group, which created the platform evolution cross-departmental program. And that program going forward will work on the evolution of the media Wiki platform with the advice of TechCom. So to give you a brief view, so whenever I try and characterize a problem, solve a problem, I always think what's the best tool for this? What's the best tool to store all this knowledge and all these pieces of information that I'm accumulating in the course of trying to do my job? And of course the answer is always a Wiki, right? So I created a Wiki. In fact, I created a Wiki farm, wikifarm.wmflabs.org. And maybe over the course of the next couple of days, I'll show you a couple of the other wikis that I've put on there. I use it for doing project management for the projects that I'm currently trying to track within the foundation. I have another Wiki farm called Cindy.wmflabs.org that's my little playground, and I created a Wiki on there called Notes. That's my little engineering notebook that whenever there's stuff that I just want, oh, so he's going to go look for it now. So I created a Notes Wiki there that I just sort of jot things down because I can't remember anything anymore right unless it's in a Wiki. So I create these little wikis that have different aspects of the things I'm trying to work. So I created a Platform Evolution Wiki. Here it is. These diagrams are generated using Mermaid, the Mermaid extension from Lua. And inside of Lua, I do some semantic queries. This got generated when I brought that page up, it queried the semantic Wiki, and it built that, which I think is pretty cool. I can click on these things. So the main goal at a five-year, we did a three- to five-year plan for this cross-term mental program because the things that we're talking about doing it, they're not going to happen quickly, right? It's not going to be tomorrow, we're going to have this thing done. So we've got a one-year plan that we proposed in the annual plan, but also a three- to five-year, we started looking from the higher level, three- to five-year plan. So our overall goal is to empower the Wikimedia Foundation to accomplish its goals of knowledge equity and knowledge as a service. Remember I said that this Wikimedia strategy process for 2030, those are two of the key goals. By evolving and investing in our technology stack to improve its flexibility, maintainability, and sustainability. So this all goes towards having a roadmap. This is sort of a high level, 30,000-foot view of what our roadmap is. And there were three main thrusts in the three- to five-year goal. Outcome one, allow engineers more easily to scale, maintain, and test Wikimedia projects. So it's basically all about architecture. First of all, figuring out what the architecture is now, documenting that, and then planning how to evolve that towards the architecture that we want to have. Simplifying that stuff. And when I was that last picture from the past of where we are now with Parsoid over here, we've got two parsers. So simplifying that stuff, coming up with the architecture of the future. Outcome number two, cross all languages. That's one of the great powers of Media WikiWrite, its ability to support multiple languages. Accessibility and usability spectrums can access the functionality of Wikimedia projects across more interfaces, devices, and form factors. Into the future, of course, is handheld mobile devices. Sure, people will still use laptops, desktops, form factors. But to see how much of the functionality of Media Wiki can be accessed, the ability to edit on the fly, on a mobile device, for example. So being able to have that capability across a range of different types of devices. And then number three, engineers are more effectively onboarded using new improved documentation that is clear, complete, cohesive. Yes. And we are talking about stepping back and looking at what we can do to have a comprehensive documentation portal. And to have that documentation, there are multiple aspects of Media Wiki that need to be documented. Certainly, front end aspect, how to set it up, server, back end, deployment of the Media Wiki platform. APIs, what's the API interface so somebody could query from a remote platform. What is the architecture? Looking at it from a high-level detail. Coding standards. How would somebody, if somebody wanted to develop an extension, what are the entry points, the interfaces for that? So there are a lot of different aspect, tools. There are a lot of folks who have written, even like, so for Wikipedia, there are a lot of people who have written tools that can mine information from Wikipedia and its sister wikis, sister projects. And so, but folks have also written back end tools to scrape to query data from their third-party wikis as well. And many of those tools can be useful for different people. So having a portal where folks can, just like we on mediawiki.org, you can see all of the extensions to Media Wiki. There's also work on a comprehensive tool catalog for tools that can interface with Media Wiki. Did I cover all of the documentation things that you were thinking that are missing? Do you have the microphone still? I think it's turned off. No? Yeah, that's good. I was looking at some of the separation of the documentation for the intended audience. Yes. And one of the things that we need to do is to look at the above the platform documentation for Wikitext and exactly have that oriented for the people that are going to build the application. Then you've got platform engineering documentation that's a totally different sort of area. Absolutely. And I'm hoping that we'll get some sort of ontology for documentation that could start the structural process for it. And I'd be happy to collaborate with anybody because that is a very serious issue. Yeah. And to get that documentation aligned so we know what pasta functions are, what we know. Yes, absolutely. And to make somebody who comes into this documentation portal have a way of, with as few clicks as possible, very quickly be able to get to that segment of the documentation that's most relevant to what it is they're trying to find. And then to make sure, as I said, right now, there's a lot of duplication. Make sure that somebody can very quickly find the one authoritative source to answer the question that they need. So. Mm-hmm. Back to you. So the question was to understand the terms knowledge equity and knowledge as a service. And that may be discussed more by Victoria when she's talking about the strategy on Friday. But really briefly, knowledge as a service would be the ability to take the combined knowledge that's in a resource like, for example, Wikipedia and to be able to use it and query it in multiple different ways. So that service, that repository of information would not only be a encyclopedia that one would walk up to and browse and search for within that resource, but you could then access it as a service in multiple different ways to create even greater and more powerful uses of that open knowledge. So that would be knowledge as a service. Knowledge equity would be making sure that there are no barriers to different people of different abilities to access the data, whether that be network constraints or language constraints or geographic or political constraints that there be equity in the access to the knowledge that's contained in these repositories. So. Okay, so that's the three to five year plan. The plan that we came up for next year is very similar. And so outcome one engineers have clear understanding of the technology stack. So again, that's, you know, the architecture being able to define where we are and how we plan to move forward with that. And outcome number two engineers are able to access more functionality using encapsulated components and well defined API's. So revisiting the API's that are available and making sure that they are available in the ways that they need to be consumed. And the third understanding the current architecture and coding standards and where to find them. And that's the documentation aspect. And just briefly, so you can see that I'm not making this up. If you click on any of those boxes, it'll take you to the drill down on so this is the drill down on outcome one and there are outputs associated with them. And each of those themselves are a page in the wiki. And so that top level view, as I said is all queried. And so I really feel strongly about the use of wikis and their power and utility and write something once and query it in many ways and display it in many ways. And I'm trying to evangelize that at every opportunity. So how do I get back to my presentation? Where did my presentation go? So I talked about the three to five year outcomes. And just to simplify and summarize those easy to scale develop maintain test all features, all platforms, all devices, all form factors and documented all those are the high level three to five year goals. And in our first year, the goals are clear understanding of our stack and what the plan is to evolve it in the future. Starting to modularize selectively across the current code base. Obviously, we're not going to throw things out as they exist now and say, oh, we're just going to give you a completely different set of code that you're going to suddenly have to big bang get everything working with. No, things are going to evolve in place. So selective modularization, that's not to say that the interfaces won't change that folks, you know, folks will have to adapt as this grows. But the idea would be to give a well defined path and good warning of how things will change in advance and then a centralized documentation portal. Quick question for you. Regression testing. Regression testing. What are you looking at? Because we have this issue of something comes out. Are all the present features supported or something broken? Or are we in an emergency situation to notify somebody? Yeah. So, well, I guess there's several different ways to answer that. So certainly, there are just have them hold on to the microphone. Testing. There are, there is testing built in to the media wiki code and increasingly more testing with time. It is a goal. So, the goal would be as there are changes introduced, making sure that things don't break or if they break, they break in a well defined way and folks are available or aware of that. But also there is a plan in place for and there is now and will continue to be a deprecation policy where things are advanced are announced in advance. If something is going to go away, he can hardly hold himself together. Give me one second and then I'll let you talk. Yes. So, there's a deprecation policy. So, you are aware in advance in multiple versions and so you are aware when you upgrade, first things will become deprecated for a while before they eventually go away and you are going to say. What is the communication policy for these deprecation things? I appreciate that, you know, you recognize the need for, you know, no sudden changes. But at the same time, if you deprecated something and that's not communicated clearly to an end user, deprecation can look just like yanking it, yanking the rug out. So, how are you going to communicate the deprecation to the users? It's going to have to be communicated in multiple channels and we will certainly for the third party community, if there are ways that will help to communicate that information better so that more people have access to that information, we are always open to that input and feedback. But there are, everybody knows, there's the Media Wiki mailing list. There are, you know, if there's something a major architectural change, it's going to go through an RFC process with TechCom and be announced. So, there are already existing channels in place. If there are things that you feel that you're, there's an answer he wanted. Yes, absolutely. We haven't mentioned the Media Wiki stakeholders group enough today, have we? The Media Wiki stakeholders group is a joint group that was created from a number of members of the Media Wiki third party community as well as folks who are at the foundation and since there has been transition of some of us original members of the stakeholder group from the third party community to the foundation, increasingly, there are channels of communication from the stakeholders group to the foundation. Yes, the Media Wiki stakeholders group is a group that meets online monthly. There is a page on mediawiki.org. There is a fabricator. There's a website, mwstake.org. Chris Corner, are you or what? Oh, Chris Corner is going to talk about it in the very next presentation. So, I can stop talking about it because I'm probably running out of time, right? Yes, it's a great group and it is a great channel of communication. If you guys are not currently tied into the Media Wiki stakeholders group, please, we welcome your participation and I'd love to see even more people every month at our online meetings. But Mark Hirschberger is our fearless leader and sometimes we forget to announce things quite well enough. Please forgive us. But yes, it is a good channel of communication between the third party community and the foundation. So, speaking of third party users in the stakeholder group, can you speak a little bit about how your work with this roadmap is tied to and restricted to the Wikipedia approach of Media Wiki use versus how other people like to implement it that doesn't necessarily parallel that use case? So, one of the things that was mentioned and multiple times by multiple people in this audience's technology working group through the course of this work is the need to consider the third party use case and to make sure that we do not in evolving the platform do anything that negates the ability of third party users to continue to use Media Wiki. So, it is very much on the minds of those who are evolving the platform. But there are questions, there are constraints in the evolution of the platform where, I'll give you an example, managed hosting, the ability of somebody to go out to a host, somebody who will install Media Wiki, a version of Media Wiki for you and maybe some extensions, but you don't have command line access, for example, they're managing it for you. There are limitations to the things that you can do without command line access currently. How many folks here actually operate it? I'm talking, aren't I? A lot. I'm behind time already? Really? I had until, didn't I? I'm way over? Okay, I'll wrap it up then. I'm just taking out Chris's time. Okay. Did I just blow right past 30 minutes and into close to 60? Wow, because I looked at the clock a few minutes ago and I'm like, hey, I've only been talking for 20 minutes. It feels like way longer than that. Okay, I'm sorry. Maybe I can, at a lightning talk, go into this a little bit more. But before, I was just going to get people to raise their hands. How many folks here work in that managed hosting environment where some other organization is responsible for their media wiki installation and they have no access. So you, okay, one. Okay, I'd be interested to, pardon me? Okay. So yeah, that's, and I'd be interested to talk to both of you more later. But that's one use case that's very often comes up as, well, we can't do anything that'll break managed hosting. And very seldom do I come across somebody who is in that use case. So I want to get more feedback from that and figure out what the real constraints are there to make sure that we aren't unnecessarily constraining ourselves, but we continue to support that use case as we can. Maybe there are alternative solutions that we can come up with that would support you just as well. Or maybe we need to continue on having that as a constraint. So yeah, at any rate, feedback from y'all on how to what really are and are not constraints on our system. And there are some other programs that we are also, so the big CDP, the big platform LV illusion thing is the big thing that we're planning for the next three to five years starting next year. There are other programs as well that we are working as a media wiki platform team have an involvement in next year. And those are some of them. I can talk about them later if anybody has questions. I think that's it. I'm done. Chris? Sorry, Chris. Cindy? So how long do we have before we have to leave for dinner or that we were planning to break? Okay. So I think Peter has a question behind it. I have the microphone. Yeah. He has the microphone. So I'm sorry. He trumps you. So if you would have to answer Cindy in 2016 asking, how can I guarantee my customers that this wonderful platform is still alive in a couple of years? What would your answer be? And what would you do to convince her? So I'm having a conversation with myself two years ago. Is that what I'm doing? Okay. I would convince her that the Wikimedia Foundation as a steward of the media wiki code base in collaboration with the volunteer developers cares very much about third-party use cases. Obviously Wikipedia is customer number one and we not want to make sure that Wikipedia continues to be supported. But there are those in the foundation who care very deeply about media wiki as it is used by third-party developers and will continue to make sure that third-party users are supported and that nothing will happen within the platform that would make it impossible for them to continue to use it. So I would try and convince myself that I can sleep well at night that there are those who will continue to make their interests hurt. Mark. As the program chair, I just want to say that we can go eat whenever we want and if that's later then we can eat later. As long as no one's stomach starts growling too loud, if I hear a stomach growling then I'll cut Chris off. Cool. And I think that's a good, I think you should go today. Yeah, I think it's a good segue into your talk. So cool. Thank you all.