Welcome back to the long and the short presented by trade station trade station is a leading fintech company and online broker providing and award-winning trading and investing experience with the support education and tools to help you navigate the market. Well tech IPO activity has increased But should we expect to see a boom here in 2018 some of the most anticipated companies have yet to even announce plans to go public Those are Airbnb Uber or even slack However within less than two weeks of each other Spotify and Dropbox both filed to go public So what does the future hold joining us now is Daniel I've she's strategy officer at GBH insights and Melissa I'm a owner of the Stock switch. It's great to see both of you this morning. Melissa we're gonna go ahead and start with you Spotify last week said that it's opting for a direct listing. We knew that ahead of time But they actually filed the paperwork just last week So do you think this is actually gonna set a new standard for how tech companies are looking to float public shares? But an IPO alternative Well, I think it's gonna it's going to be interesting to see how they fare with it Because if you look at certain companies that did do the IPOs if they weren't priced right then they had those huge spike ups Or they fell immediately and then it took them several years to turn around and rally like snap came out 2017 That still hasn't really turned around that stock. It's still in a downtrend So I think this is kind of gonna be interesting because it's very rare It's very rare that you see a company do it this way In fact, I can't even think of a time that I've ever even traded one like this So I think it's going to be experimental. We'll see how it turns out. It could turn out being good for them But the problem is you when you have an IPO They're in it and usually you have people that's sticking it out with this kind of thing if they can sell it They can buy it. They can dump it There's no there's no what's the motivation? I guess to hold it for a long term It could have a huge spike up drop off and then may take even longer to recover Then then because of Twitter Twitter hasn't recovered at all actually since it first came out that had the big spike fell Twitter's still in a downtrend Facebook turned around and a very short period of time considering what happened to them with the IPO But I think this is going to be an interesting experiment. I'm not sure how it's going to work out It's rare that it happens and it might have a spike drop and then take even longer to recover Yeah, a lot of people I think focused on that volatility that could come of course the company even saying and it's filing that it Could be a very volatile situation and I do believe that every shareholder or investor is able to sell It's set for 10 cents so something that in terms of the trading aspect that a lot of people will be looking at Daniel We want to bring you in here as well Of course the past profitability and the actual profitability of these companies so important and increasingly important We should say here with these IPOs a Spotify not yet Profitable, what is its path to profitability that you see it? How close is it? Yeah, I mean with the nature of that model, it's definitely an uphill battle when it comes to profitability me look five Five billion year in terms of revenue. I think the big thing here is about paid user growth I mean 70 million from 48 a year ago I do think there's a path to profitability But look they're in a battle versus Apple Pandora a bunch of others So I do think this is near-term an investment model Which speaks to why I think it is a volatile situation in terms of how it's going to trade And I think a lot of unicorns are watching this to ultimately see how it plays out But I do think from a growth perspective They definitely gotten through you know some significant hurdles But I mean you've seen it with a billion-dollar loss This continues to be an uphill battle in terms of the profitability profile of just this business model Right well Melissa let's bring you in here What does Spotify have to do to avoid becoming another Pandora Pandora has yet to turn a profit and it's actually an annual profit I should say and it's been public for years Pandora, I love Pandora, but you know what I don't pay for Pandora. I get it for free I just listen to the commercials. That's the problem that Spotify needs a niche in order to make money besides the Subscriptions and also they have to get you don't want to pay for the subscriptions And I think the problem with Spotify is you have the Apple you have the Apple streaming now as well And you pay for Apple, but everybody's got an Apple phone and now Spotify and I think it was last year now They have to pay 30% of the subscriptions through the iPhone They've got to pay to Apple that was a little bit of a monopoly there But they ended up having to pay it and raise the prices So Spotify has to set themselves apart as some kind of unique thing that young people Millennials such as the go-to for music I don't I don't know how to do that I mean but Spotify's got to find a way to do it and to get off of people wanting to go to Apple because if you're looking to compete with Apple, I mean you're competing with one of the most successful companies in the world and You know like you said the Spotify is showing a loss and they're gonna come out with this direct listing I don't know how it's gonna go But the one thing I will say that's really exciting as a person watching in in this age That there's so many IPOs. I mean you just named before we started talking over all these other ones that have yet to Do anything like they keep coming and coming and coming and coming it makes it really exciting to watch these companies See who thrives see who succeeds see who fails, you know, it's exciting Pandora hasn't done well I love Pandora, but it's at four dollars a share a lot in the pipeline Of course We've got to wait to see whether or not it comes to fruition and whether or not some of these private companies where it is easy To raise money in the private markets actually do want to come public Daniel Let's bring you in as well here of course Dropbox another highly anticipated at tech IPO Certainly a unicorn. We know that the company has 11 million paying users 500 million registered users do use its cloud service for free How do you think Dropbox could successfully convert those customers those 500 million into paying full-time customers? Yeah, I mean look that's the challenge for them a competitive space when you look at the cloud market little Dropbox done a commendable job over the last few years But you know you're seeing pricing continue to fall there and I think for them It's going to be the monetization capabilities in terms of that conversion Now I think investors will have a bit of confidence here as they've shown it It's really about a conversion monetization model I think they put a pretty good iron fence around their core customer base You know if you go back a few years ago, I think a lot We're sort of worried that this model couldn't really succeed But now it's really about monetization growth and that kind of profitability profile Ramping into 2018 2019. Well, I want to get both your takes on this Daniel. Let's stick with you for first Pandora dropbox rather actually filed at a time where its biggest competitor box was at an all-time high But then box just reported worse than expected earnings and at one point last week dropped over 13 percent How does this fair for Dropbox? Yeah, I think that's more of a speed bump for box So I don't think investors are gonna look too much into that I think anything it's a positive for for for Dropbox and But ultimately look if you look at box and over the last few years and they've also you got to give them you know Definitely been a feather in the cap for those guys in terms of what they've been able to perform I think net net, you know, there's more of a long-term story for Dropbox next three years I think investors are going to see far as through the trees and I think ultimately it's a more positive environment for Dropbox as There's more of that sort of appetite for an enterprise playing this space Melissa, we only have a short bit of time here But of course Dropbox expected to IPO Spotify expected to IPO do you think one how one offering goes will affect the other I Don't think either one's gonna have anything to do with the other one I would say if you'd be more interested which one to watch I'd say Spotify looks more interesting just the way they're opening it just because I think it has more Potential than Dropbox Dropbox has to compete with box and other software storage units And I think again it goes to you've got to get revenue coming in for the company to have profits Which is what subscriptions for both those services or? Advertising dollars and the big money really does come from the advertising dollars too And you've got to pull in that advertising revenue and what's the why would you want to advertise on Dropbox? So these are the things again the companies have to innovate and find ways to get revenue coming in the door Or I'd see a Dropbox could look like box. I'm looking at the box chart right now that came out in 2015 It had a huge terrible gap down just a couple days ago. That's stock does not look good It's under the original open of the IPO bright price now three years into it to 18 something opened at 20 back in 2015 It doesn't look good. Yeah, I mean, you know This is one that did make new highs but then a drop gap down and to be the chart looks lower And that's not what you want to see and so you know, I don't like this chart right now We are gonna have to leave it there Melissa and Daniel Thank you so much to both of you for joining us That's Daniel eyes chief strategy officer at GBH insights and Melissa Armo owner of the stocks, which always great to see both of you Thanks so much


WBBM FM Chicago the makers of Wrigley's Spear Mint chewing gum invite you to enjoy life life with Luigi a comedy show Created by Psy Howard directed by Mack Benoff and starring that celebrated actor mr. J. Carol Nash with Alan Reed as Pasquale Friends the makers of Wrigley's Spear Mint chewing gum are glad to bring you life with Luigi because they feel it's a friendly good natured show That offers you relaxation and enjoyment, and you know Wrigley's Spear Mint chewing gum offers you relaxation and enjoyment, too It's pleasant to chew on a smooth piece of Wrigley's Spear Mint whether you're working Shopping listening to your radio or doing just about anything Wrigley's Spear Mint gum tastes good. It's refreshing and the good easy chewing gives you comfort and satisfaction So chew Wrigley's Spear Mint gum often every day Millions enjoy it and you will too Now Wrigley's Spear Mint chewing gum brings you Luigi as he writes another letter describing his adventures in America to his mama basco in Italy Tonight is it gonna be the first day of my new night school of term, and I'm all ready I bought the new pencils a new eraser new notebook, but as the one he won the trouble. I still I got the same all the blend I So exciting the first day of a new term tonight when I start to my 3a class I'm gonna be just like a millions of other American kids are starting in the 3a Except that before I go to class. I'm gonna take a shave And also to make extra special impression and in my beautiful teaching Miss Spaulding I shined up my shoes and nice and a brighter put on my best suit, and I'm gonna wear a white shirt with a tie Mama me believe in me tonight. I'm gonna look good enough to be kept enough to school She's a such a wonderful a girl in my school How beautifully you look just like a dummy in a store window Thank you for Scotty. That's a very nice of you to say that What's happened you ask Rosa for a date no Pascale reason I'm dressed up is it because today is the first day of the new term So that's why you took such a shorter haircut so your head is gonna have more room for new brains All right, you're gonna make a fun of me, but but I'm still gonna keep going tonight school. So so goodbye.   I don't want to be late for the first day of school Now wait wait, Luigi Rosa did a hair up a little different tonight I want you to take one look at her before you go. Who knows you might change your mind Well, all right, Pascale, but Call it out only just to say hello. Good. Good Rosa Rosa Rosa Baby, well, Luigi She looks a nicer Pascale Thank you, Luigi. You look beautiful too Well, Luigi, you got an appetite to get married now Pascale, she's got enough appetite for both of us and I'm not the hungry Wait for Luigi. No, no. See you later Pascale. Goodbye, Rosa Papa, what are you gonna do with me? I don't know, but whatever I'm gonna do. I'm not gonna do it with Luigi The first day of school is always the most exciting, isn't it fellas? I wonder what what's it give and miss budding. Huh? What is everybody so nervous about? Look on me. I'm I'm as cool as a coocomba Oh Here she comes. Yeah, look look she never looked the more beautiful. Good evening. How are you all tonight? Well, what are you staring at? Mr. Schultz the cat got your tongue As long as he leaves me my eyes. I ain't complaining Gorgeous tonight miss folding a real lullaby lousa Thank you just a new dress. I'm a sporting.  Oh, how thoughtful And that's a perfume with a friendship name, but you're gonna smell it sweet in any language Thank you, mr. Vasco miss balding a little something for me to you. Thank you, mr. Harwick and something for me to miss balding Why thank you, mr. Olsen and here's my bribe Thank you, mr. Schultz class. Why the sudden burst of generosity? We are just doing our charisma shopping a little early this year Hey now miss budding. We we we just want to show you miss budding Our appreciation for having a such a wonderful teacher and we're just so happy that we're lucky enough to have you For another five months.  I'm not going to be your teacher this term I came in to visit you for a moment before I go into my own class Our principal assigned me to another 3a class for this term How you mean We're gonna have another teacher. There's nothing I can do our principal. Mr. Orth feels that a change of teachers is good for pupils that it gives them a fresh viewpoint But we love the old view by He can't do that to us by yingily It is against all the sacred principles of democracy at work There in the majority of a group has the right to decide for itself its own future rule And besides the old ones stop already. They are stealing our teacher away and you are filibuster Hey miss budding couldn't you complain about about about losing your class? Well, as a matter of fact, mr. Basco, I did but mr. Orth can get very stubborn at times I'm sorry class.  What would I do with a dozen lace handkerchiefs? Miss folling if you're not our teacher, who's gonna be the new one? Well, uh, it's not going to be pleasant news Good evening miss folling Me we got the mr. Heine. Oh, no the grammar school gestapo Good evening, mr. Heine just coming in for old time's sake a miss folling. Yes. Yes kind of well I'll be seeing you gentlemen Goodbye miss folling Come see us when you pass by take care of yourself Pray for our lives Mr. Heine, they're a wonderful class really and I know you'll have a lot of fun teaching them this term Yes, I'm looking forward to it with pleasure. He must have gotten a new whip Well, goodbye Mr. Heine last term I know this class only too well on two other occasions I have substituted for miss folling and you've given me nothing but trouble now. Listen to me all of you Mr. Schultz, why are you staring out of that window?  Schultz I'll get this in your head's class. I am not a substitute anymore filling in for an easygoing indulgent pretty blonde teacher Should only happen to us Mr. Schultz, were you whispering under your breath?  Yes, yes, why I don't you ever let me hear you say yes sergeant again Yes carpenter What did you say speaker? I said yes, yes, yes, mr. Heine that's better. Mr. Basko Mr. Basko, how far did miss Spaulding take this class in american history last term? I I think it was up until the civil war You think don't you know that's right What's right? I think I don't know It can one pupil yet. I don't know the time is as young yet Sit down mr. What's your name? Horowitz whole name and stand up when you're speaking My name is natan horowitz. I'm 46 years old and I have three children Is that supposed to be funny mr. Horowitz?  Horowitz? That's funny Mr. Uh, awesome that right sir Perfect Yeah, I must say mr. Heine you do have a wonderful memory. Yes many people have remarked on that I have also heard from your former students that uh, you have a wide educational background And that you have developed your own unique methods of indoctrinating pupils with useful knowledge Yes Oh, butter him up, but don't grease him to death Stand up I'm going to make an example of you to the whole class This is what can happen to any one of you for the next five months Himmer That all you can say before I decide on your punishment Yeah, but please please let me have one look at my wife and children before I go Before we return to life with luigi Here's a suggestion that'll help carry you through a busy strenuous day feeling more relaxed and satisfied From time to time, especially when you're tense or under pressure chew a stick of wriggly spearmint gum You see the good easy chewing goes right along with what you're doing It helps relieve that feeling of strain and tension so that work goes smoother and time passes more pleasantly Wriggly spearmint chewing gum tastes good, too It freshens your mouth sweetens your breath and gives you long lasting enjoyment and satisfaction So when you've got a job to do and you've got to keep going at your best Chew refreshing delicious wriggly spearmint gum Millions find it helpful and you will too And now let's turn to page two of luigi basco's letter to his mother in italy Well, mamma mia looks like we're gonna have a terrible time this time in the school with mr. Heine All day. He's a holler on us. He's a givers test and at the home. We got a double homework Only thing he don't do is a hit us That's only because we fought there is a one in And about the third night of the new term we decide to hold a meeting in my antique shop and talk over what we're gonna do As president of the united nations of north hollstead street. I call this meeting to order Will the delegate from sweden kindly summarize our grievances against the common enemy yo-ho And mr.  I second the motion Comes now the time for action Does anybody have a suggestion how to subdue the enemy and get back to civilization which means balding The delegate from israel has the flu I say we must meet force with force. You mean knock his brains out Now we can be more subtle Attack on attack on his chair Glue on his chalk Maybe cement down the border. I said yeah on the border But if we do all those things and maybe they're gonna throw us out of the school So what does the prisoner complain when they force him to leave alcatraz? A yard the delegate from sweden has the flu off. Thank you A gentleman the enemy is crafty, but we must be more crafty Perhaps if we made a direct appeal to miss balding well, also, and I did that you spoke to miss balding Yeah, I saw in the in the lunchroom and I begged her she should talk with mr. Art and he should let her come back to our class. What did she say? Well, she tried and he said no Well, the crafty ways have failed. Let's go back to the baseball bat theory of thinking Does anybody know where we can pick up a second hand atom bomb cheap? Hey, wait, wait, sir. I got a big idea the delegate from italy just got a big brainstorm Olson was right who we got to be smarter than mr. Heine He's not gonna let us go But there's one person who maybe could convince mr. Heine to go back to his old class who his wife pure Why not? I know my wife runs my house.  I think you hit it on something women, you know a very Zostarded and sentimental so we're gonna appeal to missus. Heine to get mr. Heine to take back his old class She must notice how chumpy and angry he is since he's been with us But gentlemen just one question. What if there is no mrs. Heine? Well, there is also and I heard him talk about his He's a wife and and as a kid. You're so what he could have eaten them all up by now Yes, we stopped there Lou video, are you sure he is married? Yeah, awesome come to think of it. I heard him talking about his wife too Oh, yeah, he must have a wife. Heine couldn't be happy unless he was torturing some poor miserable creature full time 24 hours a day Luigi, is this the address you found in the telephone book? That's the Horowitz. And there was only one Heine more than one. They couldn't stand Ring the bell, Lou video. All right You missus. Heine a wife of mr. Heine the night's gonna teach you. Yes, what do you want? Oh Mrs. Heine we We belong at your husband's night school at class and and we came here to ask you a bigger favor very well I'll give you two minutes. Come in We uh, he was thinking oh man Well, how was it?  Have you lost your tongues? Mrs. Heine we came ahead to ask you about just a moment you there. No me. Yeah Put out that cigar. I don't stand for cigar ashes on my rug And as long as you're in my house, don't lean against the furniture. It's newly polished. Is that clear? Him and Mrs. Heine is Mr. Heine without the mustache Is that supposed to be a wisecrack? Oh, I'd call up your husband and tell him to give me a zero I Don't speak out to be nice And mrs. Heine we just we just came here a little friendly visit to ask you about it. Speak up.  Well, your husband is a nice fellow, but But he's a little bit too strict to with us. Ain't all this strict Aidan! When will I know it? Hitler is still alive! This is all ridiculous. My husband is just as fair and impartial. And then he's supervisor of a change-in Come on fellas. We got to get back to school before the keeper misses us Wife informs me that you tried to influence her to get me to exchange classes with mrs. we did. Frankly, she looked like the squeela type. Mr. Schultz, you'll speak when you're spoken to. Yes, sir. Just about fed up with the low grades you've all made in the last few daily examinations. If you don't do better in today's oral test, I'm going to recommend to the principal that you all be expelled. Expelled? No, no, no, no, you can't do that. All right then. Close your books. Keep your eyes front, heads are X. Speak only when spoken to, and the first one I catch whispering in answer goes down to the principal. First question. Mr. Horowitz. Give us the grammatical rule for the use of a period in a sentence. Would you mind please repeating the question? Zero. That's not the way you said it the first time. Mr. Baskill. Please. Tell us the rule about the period. Well, a period that should have stand on the end. I mean in a sentence and wait, wait, Mr. Heine, I know, but I'm a little bit nervous. Set down. Zero. Mr. Schultz. He got me right where it hurts. Mr. Schultz, you may tell us. Yeah. Mr. Schultz, why are you trembling so?  There's no need for concern if you've done your work. You may tell us, when do we use the exclamation point? When we give a command, for example, stop bothering us. Yes. And stop needling us. Needling? What are you giving us? Educational vaccination. Mr. Schultz, I've had enough bits of ordination. I'll see the principal right now. No, no, no. Please, Mr. Heine. Have you all thrown out of school? Now we've got no misspalding. And no school. He ain't just studying for nothing. Now, Mr. Heine, I've been examining their test papers and this plus everything you've been telling me about them proves that you're right. That class has fallen down in scholarship. No interest whatsoever in their work, Mr. Roth. I can only repeat what I've been strongly urging that they all be expelled. Very well, as you say. They'll receive their dismissal notices in the morning. Good, very good, Mr. Roth. I must admit, that's quick. Thank you. And now then, Mr. Heine, what are your plans for the rest of this term? Plans? Well, I'll be teaching my class.  You have no class. Looks as if you don't have a job anymore, Mr. Heine. Oh, Mr. Roth, I can take on some other night school class. There are no others, Mr. Heine. Of course, you are at liberty to seek employment in some other school. Wait, now, wait, wait, wait, look. Let's not be too hasty with this class. Shall we, Mr. Roth? Perhaps I can get more out of them. I hardly think so, although Miss Balding got very satisfactory results from that same group, I believe her secret lay in treating the individuals in a way exactly opposite from yours. Please, sir, please, let me try. I have changed my teaching methods. I'll try. I'll try humoring them a little. Very well. Good luck to you, Mr. Heine. And let's see what happens. Yes, yes. We'll see what happens. Come now, Mr. Vasco. In what year did the United States purchase Louisiana? Eighteen hundred. Your clothes. Try again. Try again? Yes. You sure, Mr. Heine? Sure, I'm sure. Let's try it. Eighteen hundred and... Eighteen hundred and one? No. Eighteen hundred and two? Eighteen hundred and three? Stop. That's perfect. Now, now let me see. Who shall we call our next? A Schultz to what's happened to him? It could be softening of the arteries. Mr. Schultz, what did you say? I said you could be suffering from softening of the arteries. It's funny, funny. Maybe I'm wrong. Maybe it's softening of the brain. Well, now we'll call on Mr. Olson. Oh, no, no. Don't bother to stand up, Mr. Olson. We need an axiform. We need him? Luigi, are we in the right cell? Mr. Olson, I don't think I'll bother to ask you a question. You are a wonderful student. That is correct. Uh, Mr. Horowitz? Nathan Horowitz, I'm 46 years old and I have pre-children. Oh, how funny! As a matter of fact, you are all doing exceptionally well today. So far, not one zero. Call on me, Mr. Hein, and I guarantee to break the ice. Mr. Schultz, okay, give me the zero. No, no, no, no. I thought that remark was very witty. Then why didn't you laugh? Come on, Mr. Hein, you can laugh better than that. Mr. Hart, this is the end. Good evening, gentlemen. Good evening, Mr. Hart. Well, Mr. Hein, I'm glad to see you're getting along so well with this class. Oh, they're a wonderful group, sir, and their grades certainly are improving. Good. I was going to tell you that I had decided not to expel this class, but rather have you exchange classes with Miss Spaulding. But since you get along so well with them, perhaps I'm going to let you keep them. Oh, no, no. We demand a lawyer. Good evening, class. Gosh, Mr. Orth, it's wonderful to be back here with my old class. It seemed to be the only sensible solution, Miss Spaulding. Hey, Mr. Hart, you mean we're getting Miss Spaulding back? Yes. But you said before... I know it.  Well, come on, Mr. Hein. Your old class is waiting for you.  Hey, isn't that funny, Mr. Hein? Yeah. So what do you think, honey? The makers of Wrigley's Spearmint Chewing Gum hope you enjoyed tonight's episode of Life with Luigi, and they want to remind you that chewing Wrigley's Spearmint Gums is the easy, enjoyable way to sweeten your breath and help keep your mouth feeling fresh and clean. There's lots of lively, full-bodied, real spearmint flavor in Wrigley's Spearmint Chewing Gum, and you can chew and enjoy a stick of Wrigley's Spearmint as long as you like, any time, any place. So do as millions of people do. Keep a package of Wrigley's Spearmint Chewing Gum with you all the time.   That's Wrigley's Spearmint Chewing Gum. Healthful, refreshing, delicious. The makers of Wrigley's Spearmint Chewing Gum invite you to be sure to listen next week at the same time when Luigi Basko writes another letter to his mama Basko in Italy. Life with Luigi is a Sy Howard production. The script is written by Mack Benhoff and Lou German and directed by Mr. Benhoff. This is starred as Luigi Basko with Alan Reed as Cacuale, Jody Gilbert as Rosa, Mary Schiff as Miss Faulding, Hans Conreed as Joe Forte as Horowitz, Ken Peters as Olson, Earl Ross as Mr. Hine, Gail Bally as Mrs. Hine, and Herb Butterfield as Mr. Orr. Music is on in the direction of Lud Gluston, Charles Lyon speaking. This is the CDS Radio Network.


things that can make the difference and you find yourself in battle and it's not going the way you want it to and you just can't get out of it. It's like dropping into quicksand. Introductions for these young ladies in the 4x100 meter relay under 17. Under the relay finals to come. Including the mixed 4x4. Yeah, this one was scheduled for 645 local time, 7.15 now, so they are half an hour behind. 2x100 Keiko's Islands will go in lane 1. A number of the teams here will use this Carifter to get experience for their young athletes in running the relays. And of course to blood some of their younger athletes as well. For the first time at these Carifter games we have relay action. No qualifying at 4x1 and so we go directly to the finals. We start with the under 17 girls event. Record held by Jamaica 44.95 set in 2018. Here's the lineup. The first leg runners take center stage. Terps and Keiko's Bahamas, Trinidad and Tobago, Jamaica, Grenada, St Kitts and Nevis, British Virgin Islands and Bermuda. The Jamaicans will start in lane number 4. They have Malaya Duncan on the opening leg. St Kitts and Nevis in 6 with Kamea Phipps starting off with them. There's Duncan, the Jamaican leadoff. Kylie Wallace starting things off for the Bahamas in lane number 2. One assumes that Kiev for Thomas is likely to figure heavily for the Bahamas. But of course the team to beat will be Jamaica. Cyrus Stout will be the leadoff runner for the British Virgin Islands. The Bahamians expected to have Thomas on the team. Also the 400 hurdles. Silver medalist, Dharvani Dean. The Jamaicans do start favorites though. Tremendous depth they have. Final of the 4x104 on the 17 girls. Terps and Keiko's Bahamas, Trinidad and Tobago, Jamaica, Grenada, St Kitts and Nevis, British Virgin Islands and Bermuda. Final of the on the 17 girls 4x100. First today action of Carrifta 2024. Egypt, Benjamin, the leadoff for Grenada. Kailani King for the Turks and Keiko's Islands. TCI in 1. Grenada in 5. As in a lot of running regis at these championships so far. Let's see if she can put her team in a good position from the opening leg. Duncan for Jamaica in 4. Wallace for the Bahamas in 2. Off they go. 4x100 final on the 17 girls. 14 stars for Trinidad and Tobago. Duncan now responds for the Jamaicans. Duncan hands over first and it's Jamaica in charge. Down the backs right away they go. The Bahamians responding now. Jamaica and Bahamas. Trinidad and Tobago with work to do. St Kitts and Nevis going well in lane number 6. Natrice East on the third leg for the Jamaicans. Look superb in 200, qualifying earlier today. Here's the final change. It's Jamaica in front. They are well clear of the rest of the field. But Shanalee Blake is it an anchor? The Bahamas coming forward with Thomas. They will be second Jamaica with the gold medal. Bahamas, Silver and Trinidad and Tobago with a bombastic runs. Jamaica as expected, looking up to their seeding. Coming through with the gold medal. And as we are expected, Keazra Thomas on the anchor for the Bahamas produced a good anchor leg. But not quite to the class of the Jamaicans. Trinidad and Tobago coming through to take bronze with Tiana Richardson on the anchor leg. But the Jamaicans with a fabulous team led off by Malaya Duncan. Looks like Adora Campbell is on the second leg. Natrice East on third and for Shanalee Blake taking them home. The Bahamians with Keazra Thomas coming through to claim Silver and the Trinidad and Tobago capturing the bronze medal. Here's another look at it. Duncan out brilliantly for Jamaica. Bahamas getting a pretty good start as well from Kylie Wallace. Adora Campbell the 100 on the 17, Silver medalist pouring it on for the Jamaicans down the back stretch. And this is where they really opened up the race with the fast Natrice East on the third leg. The Bahamians battling. The Trinbeconians were struggling for a long way in this race. So it's a terrific performance to be able to come through for the bronze medal. St. Kitsa Nives had a fine performance as well. Final change Trinidad and Tobago down in about fourth, fifth. But tearing through the field was Tiana Richardson to land them the bronze medal. There was no denying these Jamaicans though just too strong for the rest. And even with the outstanding Keazra Thomas on the anchor leg for the Bahamas they stood no chance. A lot of experience of course of part of passing for these Jamaicans. Not all of the island would have had as much time running relays. Jamaica 45.36. The Bahamas 46.28. Trinidad and Tobago 47.49. Your top three with Grenada, St. Kitsa Nives, British Virgin Islands, Bermuda and the Turks and Geco-Silents in that order.


All right, so this is a talk on Gutenberg. I'm Brandon. And let's get talking about Gutenberg. So what is Gutenberg? Gutenberg is first and foremost an idea. It's treating our content as a composition of blocks.  It's similar to that concept. Here's a wireframe that shows a paragraph block followed by a gallery block, followed by a quote block, followed by another paragraph block. And this is what I mean by blocks. Here's a view of those same block types in an editor. Hopefully, that's somewhat readable. Mostly, the point is to get the shape of things. So we have a paragraph followed by a gallery and so on. And here is the result rendered for readers with the same blocks. So today our content in WordPress is divided or is expressed by special cases. So first, we have media, which is used for images and other approved assets. Then we have embeds, which refer to external content and allow us to include external content, excuse me. And we have short codes. And if you're not familiar with short codes, they're another way to insert content, insert special content into your content. So for example, in WordPress Core, there is a playlist short code where you'd express the word playlist in square brackets. You just type it out. And then you would type an IDs parameter. And you have to find IDs of the things you want in your playlist, like audio clips. And then you would specify those IDs. You're typing all that out. And that's how that works. You also, a lot of plug-ins will use those as ways to make available additional special kinds of content that you can insert. Then we have featured images, which allow us to select images to be featured. We have excerpts, which allow us to provide a summary for a post that's displayed in multiple places. And then widgets, which are used for expressing content that falls kind of outside the post or your page, the page content. So this would be like your sidebar or your footer and so on. These are all different languages. These are all different ways of different things we have to think about when we're expressing our content, that, oh, we need something that's involved and delivered via short code. So we have to think about what that short code is. We have to think of what it's named, what its arguments are, these sorts of things, and that's troublesome or can be. And all those different ways are different ways of thinking. What if we could use a single language? What if we could unify all of these languages into one, a language of blocks? So me, that sounds pretty good already, but why does that, why does it matter? The first reason is the general topic of focus. So focus as a writer, actually, could we move that? Focus as a writer. So if we simply use blocks, we can reduce the number of times we have to kind of change our mode of thinking around, I need this kind of content. Oh yeah, I have to go over here and I have to change this or I have to go look up something and make sure I'm providing the right thing. Or if I want to do something completely custom, using custom HTML, that's also a different mode of thinking than if I'm just writing able to write smoothly in a rich editor. And so all of that has a tax, is a tax we pay on our focus. So the idea is that if we can use blocks, if we can use a single way of thinking, or at least a single entry point, into how we express our content, then we'll be able to maintain our focus as writers better. Additionally, blocks help us say what we mean. The ideal is that we will provide meaningful blocks that don't require so much thinking to grab. We say, I need this kind of thing. I'm just going to go grab this block and I'm going to put it in my content and fill it out. Meaning also gives us some additional benefits. So since blocks will ideally, and we can make this happen, explicitly reflect the type of content we're creating. It's better for maintenance because you're co-authors and also maybe your future self six months down the ray or even maybe a month away won't necessarily go back to some custom HTML that you wrote and wonder, I felt really clever when I did this the first time, but why did I do it this way? I don't remember, or it just doesn't have, once you've forgotten, it doesn't have inherent meaning. HTML has some meaning, but it doesn't have as much meaning as we can provide at the granularity of blocks. So blocks are the idea. That's the main idea behind Gutenberg is pretty simple. So where is Gutenberg today? The community has been developing an editor. So bringing first the idea of blocks into the editor. It's a good first step. And before we talk about more, I'll do a review of available block types. I'm slightly hoping I can get away with a cheat, which is I'm kind of going to be listing things here, but I want to talk about them. So the first blocks we have are for document structure. The first is heading, which defines the document outline. It's your H1, H2, H3 that actually define your semantics of your document and the outline. Then we have a subhead block, which I believe is made more for a replacement for the excerpt that will actually allow us to specify a summary or sort of a deeper subheading for our document. Then we have our text blocks. The paragraph block is actually very foundational to Gutenberg. We start with a paragraph block. We create things, and often our next block will be a paragraph block. Then we have lists, which are textual lists, unordered lists like you have in HTML. We have quotes for attributed quotes. So you can offer a quote and say who it came from. It offers a number of styles. We have pull quotes, which allow us to take quotes out of our articles and sort of entice potential readers with them. And then the verse block, which I was very glad to see that there. We talk a lot about code as poetry, and it is. And poetry is also poetry, and it's nice to be able to write it in WordPress in a block. Here's an example of the verse block. And it's basically, it's similar currently. It's similar to a paragraph, but allows you, has different interactions. So when you hit Enter, it doesn't necessarily go to a different paragraph. It will allow you to write verse a little more cleanly. Next, we have the graphical blocks. We have a block for a single image. We have a block for expressing the meaning of a cover image. So when we use that block, we're providing the additional meaning that this is a cover image for our article. Then we have the gallery, which allows us to select. This is sort of a portal into WordPress media. It allows us to upload or use things that are already in the media, in WordPress media, to display a gallery. And it will automatically lay out the gallery in a nice way. And here's an example of the cover image. Cover image also supports a caption. All right, next we have media blocks. Media blocks offer audio, video, embeds. There are so many embeds. I started looking through the blocks. And I believe my vague memory is that there are 20 different sites that are explicitly supported. And then there's also a generic embed block, which allows you to specify external resources from any site. Here's an example of the YouTube embed block. Let's bring WordCamp US to Phoenix. And then we have formatting and layout. So things you'd expect, like pre-formatted text. You can express as a block. You can express code as a block, text columns, so just multiple columns of text, and tables. And here's an example of the table block in the Gutenberg editor. And finally, we have supporting blocks. So we have a custom HTML block for the times where, despite our desires to have blocks that have meaning for all of our content, occasionally you find that that's not the case. We can provide custom HTML for those. We can also use classic block, which is kind of like a version of the classic editor in a block form. I don't, in my experience, I'm not sure it's one to one between the classic editor and the classic block, but it's very much like that. And it's a tiny, if you know under the covers, WordPress that uses tiny MCE as a rich editor. And that's what classic block has. Then we have a separator block and also a read more block that will allow you to take maybe a more brief portion of your article and divide it and separate it from a portion of your article that has maybe more details than you think most people would like. But you'd really like to make them available for those who are interested. It allows you to click that link, and then those details will be shown for the interested parties. Here's an example of the custom HTML block, as is. I think the thing I'm most excited about these kinds of blocks is right now, this isn't syntax highlighted. We could make some improvements, but people are actively making PRs and that sort of thing for improving this, for making this a syntax highlighted experience that we're used to seeing when we use other HTML editors. So these are just some of our building blocks. Hopefully that gives you a good idea of what's available. Now when we're writing with Gutenberg, we basically insert, edit, move, and remove blocks. We're just working with blocks. And the sum of that, the result, isn't stored another place than we normally store our post content. It goes to the same place we store our post content today, and it's saved as valid HTML. So even if Gutenberg does not load the content that we're saving, it's valid HTML that can be read by a browser. For people adopting Gutenberg, if you open a post that you've previously authored with the classic editor and with the Gutenberg editor, the pre-existing post is converted. It's currently converted into a single large classic block. And I think maybe we'll explore making that more granular in the future, but that I believe is how it works today. I'm sorry, I didn't understand. That is also true, that there is a classic editor plug-in that you can install so that when Gutenberg is a first class part of WordPress that you can express by installing this plug-in when you want to edit posts, you want to edit by default in the classic editor. That's right, thank you. So let's talk about some feature highlights. These are simply features that I personally have worked with and find interesting. The first is autocomplete. This, in practice, this is an autocompleter. So when you're in a paragraph block and type a forward slash right away, you get the opportunity to start autocompleting blocks right there. So this made me feel immediately better when I was in the editor experience writing myself that I'm not just stuck and have to go use a mouse and select the right block. I can continue keeping my hands on the keyboard and select the block I want. The more you type, the more this is narrowed down. So these are just the first 10 options as you type, you get the next 10 that are narrowed down and so on. And once you hit enter, it'll actually replace the current paragraph block with the block you selected. And there's a lot of work being done around accessibility both to make that more accessible for people who need it, and then also, at least personally, I really like keeping my hands on the keyboard as much as possible. And I'm very interested in helping out with that part of the editor. Here's another, this is a really, really cool feature. It is the ability to use to create a block and then save it to be reusable throughout your site. So in this case, we've added a quote block, and then we're converting it to a reusable block, if you can see there's a convert to reusable block menu item there. Once that's done, you can actually insert it in other places. You can insert it multiple times in your own article. Maybe there are some things that actually do bear repeating in the same post, and you could use that as a way to do that repetition, and then you can insert things in new posts. So here's how you would select that reusable block, and here's how it looks once it's inserted. Another feature that I think is really cool that harnesses some of the meaning we have with blocks is that we have an outline of an article here, and it's defined by the heading blocks in the article. And you can actually navigate via these. So if you had a very large content, you can select your headings and navigate to exactly the section you want to be in, or at least in the neighborhood of where you want to edit, and that, I think, will come in very handy for some people. So those are just some of the features. I'm sure there's probably plenty I've missed, but these are some things that stood out to me, and I decided to share those. So where's the community taking Gutenberg? We have the editor. The editor is being developed. What next? Our first step is to get the editor to a place where we believe it's a minimum viable product for becoming a first step for a block-based editor in WordPress. I have a link to this in my references, but that's currently being tracked on GitHub. The tech lead for Gutenberg has created an issue with listing the things that he believes we need to get done first, and it'd be good to follow along if you're interested. I actually haven't been able to read all the things there, but it looks like we're pretty, there are many, many more things that were done on that list than things that weren't, so that was nice to see. The next step would be merge proposal. So someone will need to make a proposal to merge Gutenberg into WordPress 5.0, and then finally it'd be actually doing the work of merging it into WordPress 5.0 and getting community feedback along the way. The next steps after WordPress 5.0 is to follow with using blocks for full site customization. So blocks don't just apply to your post content.  Anything you have that defines your regular site layout, we can model that with blocks, and we've been exploring foundations for how to make that real. Now, the following, what I'm going to show you next are prototypes. They may have no bearing on the final or may not, the final product for this may not resemble these prototypes, but here's what we've been working on. So the contrast here isn't great, but this is a page showing, imagining how we could go to a page and select an overall page layout. That sounds, I really like the idea of being able to visually see these different page layouts and choosing one and then being able to go forward here and have placeholders for blocks where we can just start filling them in. And it doesn't necessarily take as much of a mental load, at least for me, if I have a particular layout in mind, but then my mind gets set on maybe a particular subsection of what I'm creating, I might not always remember about, oh, what was I going to do over here? So I really like the idea of having a placeholder, like on the top here, we have a featured image placeholder, and it would remind me to say, hey, select a placeholder image. And here's a shot of that after the placeholder image is selected. I'm sorry, could you repeat that? I couldn't quite hear you. I actually don't know what that is to be honest. So I don't believe so is my answer. This would be more, we're iterating or riffing on the idea of how we would do site customization. So WordPress has the customizer right now. And so what would that look like when we can use blocks? I think is the bigger question that we're asking right now. That helps. Sure. Thank you. All right, so next let's talk about outcomes and then some opportunity. So the outcomes are sort of a more of a before and after imagining of how WordPress will work or things that might change about WordPress after Gutenberg is merged. So short codes, which we talked about earlier, I would argue it's a better user experience if we can replace those short codes with blocks. And so that's the ideal option. But there is a short code block available. And I believe we still like to provide backward compatibility for those who rely on short codes, which is in my perception and experience in the community is many, many people. So that's the story of short codes that would be better to replace them with blocks that give you a better, more resilient user experience. But you can still use short codes if that's what you need to do. Now for themes, I've perceived that there's been some worry about, well, what does Gutenberg mean for my theme? Existing themes will continue to work. So existing themes will continue to work. And then if you want to target Gutenberg, there are Gutenberg features you can leverage. For example, you can specify theme colors that appear in the editor when you're sort of a highlighted set of theme colors that you can choose from when you're setting colors via the editor. You can specify styles for the editor, which would say if a theme renders a particular block a different way in a really creative way, maybe you want to change how that block is edited in the editor so you'd want to restyle that with CSS so it looks a lot like what you're going to see on the front end. And themes will be able to add editor styles in that way. Themes can also add fonts. And then I think another feature that we've seen demoed with blocks often are wide images and ability to take an image and say, hey, I want this to be full left to right wide image. And that's another feature that's explicitly supported by Gutenberg, and I'm sure there will be more. So post formats. So post formats, my understanding of post formats is that post formats exist to allow us to give WordPress some hints about the nature of our content that we're writing so that when they're styled on the front end for readers, we'll be able to style those in a better way because we know what kind of content it is. The idea is that expressive blocks, just providing blocks with really expressive capabilities, will allow us to explicitly say what we want and reduce our need for post formats. But we currently are continuing with post formats for backwards compatibility. For metaboxes, metaboxes are for those who aren't familiar, and I'm actually currently just getting more familiar with these, metaboxes are a way to allow you to specify additional information about your posts and a way to allow the writer to express those things, and then you can leverage those on the front end when you're rendering your posts for readers. Now, Gutenberg supports, or does provide support for metaboxes, but metaboxes, there are some metaboxes that are not self-contained that depend on the structure of the current editor, like maybe they're doing lookups in the DOM, in the HTML, the document hierarchy, doing lookups and finding things outside of their own box. Those things, Gutenberg can break those things because the surrounding editor for metaboxes won't be the same, so metaboxes that are not self-contained can break. So if you have self-contained metaboxes, my understanding is that you will be able to continue using these, but if you have some that aren't and you have incompatibilities, you can actually explicitly mark them as incompatible when they're added, and Gutenberg will notice that they're there and take action to just load the classic editor so you don't end up in a broken space. Then we have widgets. So widgets are, again, widgets are used to express surrounding content, like our sidebars, our footers, and that sort of thing. The vision is that widgets will eventually be replaced by blocks, so we don't have, we eliminate this, we don't have to think in another term in terms of some other structure to express content in certain places in our site, we can just express blocks where we were expressing widgets. The same goes for menus. The idea is that menus will also eventually become blocks instead of being their own special thing. So around Gutenberg, there are some opportunities we have, and these are from my limited imagination. I'm sure there are way more opportunities around this that others could think of. But the first is, probably the most direct one, is custom blocks. We, there will be a place for custom blocks, for special case things that aren't supported directly by core, and maybe don't want to be. And there will be the ability to add plugins and package your own blocks. Also, as I mentioned before, themes that leverage Gutenberg features are an opportunity. Now for the third point here, for improving experiences for agencies and customers, there's some other features that are being developed right now for being able to specify, kind of hinted at it, looking at the prototypes, but page layouts, and layouts where you can specify a set of blocks, and you can lock those down, so either maybe you could lock down the blocks that are present, and those blocks could be moved around by the people editing, or you could lock those down entirely, and so you have to keep the blocks you have, and are able to just have people say, fill in this content, and don't make changes to this, and that might provide a little more control, and it does provide more control, and maybe help set expectations for what agencies can expect from their customers, and what customers can expect when they come and try to use what's been created as a layout. A really interesting thing for me is how finding new ways to leverage the meaning of blocks. I know there's some work going on to see what this means from a search engine optimization perspective. If you can actually look at a page and know more about that page and what's there, that can provide more information for search engine optimization, and there are ways maybe if you're looking at your articles in maybe a collection of articles, there are ways you could identify articles or types of articles just by what kinds of blocks they have in them, referring to your imagination, because that's what I have today, but then also around that is education, so both in using Gutenberg and also just education around how to leverage it as a developer. So if this interests you, and it interests me, how can we help? So for contributing, here's some ways we can contribute. We can install the Gutenberg plugin, we can get involved with testing it and filing issues on the Gutenberg GitHub project. We could even test the latest that's in Git. You can get into daily testing if you'd like. You can participate in design discussions around the design of Gutenberg and the user experience. You can get involved in development. There are plenty of, you know, we're moving fast with Gutenberg, but there are plenty of bugs to fix. There are plenty of issues to work on, new things to create. And internationalization here is another opportunity, but I'm not sure how ready that is right now. I'm just not certain, but eventually there will be an opportunity for people who want to help translating various bits of text that are used in Gutenberg. And then just providing Gutenberg support. So answering others' questions is a great way to learn. So you can help out on WordPress support forums and you can also look at questions that are added in GitHub and take a look and try to answer those yourself and make the experience better for others and yourself. Here's some resources. This isn't meant to just be read here. This is more just to be available for people who want to look at the slides later. But there's a great, there's a good, already a good Gutenberg handbook on WordPress.org. Gutenberg developments on GitHub. We have, I have a link to the minimum viable product issue on Guten, on GitHub. So you can look at that for some good examples. A Gutenberg starter theme that's starting to explore how themes can best leverage Gutenberg features. And then the last, the last one is just a good article about someone's experience styling themes for Gutenberg. So thank you so much for coming to my talk. And this, these, this is where you can find the slides. And I hope that's useful to you. And are there any questions? You're asking if the theme, yeah, that those are all links. Yeah. Yeah, I should have clarified that. Thank you. Oh, I, I thought I did. There was, so, so how, how, how would it allow you to be responsive on mobile or just for, I don't know for a fact about what, as far as for the default styles for Gutenberg. I'm, I'm guessing my belief is that we're making a best effort to have, you know, reasonable simple default responsive styles. But I think that would depend a lot on your theme. And so hopefully we, themes would be able to take the meaning that are added, the meaning that's added by blocks and make, make decisions about how you want to adjust for mobile. I'm sorry. I don't know if it's me, but I can't, I didn't hear you. Okay. So the question is, do, does it have a built in sort of column and row, row structure? That's my, in my understanding that's currently being built, there's nesting, block nesting, which I was thinking about showing, but last time I tried it, it was, it wasn't quite working right for me. So I decided to omit it from this talk, but there is block nesting that's going on. And you can, I think the first experimental way is breaking your, breaking your post up into columns. And I think, I think it's inherently row based already, but if you can break your post up into columns that then can nest other blocks, I think we're starting to get there. So I think there's an eye to that, but we're, I think, I think it's still in progress. Maybe even the next Gutenberg point release, actually. Any other questions? Sure. Okay. Sure. Okay. So I believe the question, and I'm going to try to summarize, because I didn't track all those things, but, or all the specific examples, but is it, is it going to be similar to a lot of the current visual page builders in all for this? So I, I personally am not very familiar with the, what's currently available for visual page builders. I believe we're going to be pursuing, I think we're pursuing the best UX we can around just having, taking blocks in, I think, I think there are talk, there is talk about drag and drop and that sort of thing. I don't think that's there yet, but I think there's an eye to that being as easy. I could, I could say that, I think. Sorry, I can't say more. Sure. Sure. I don't think there's a, there's the, there's the make.wordpress.org blog, which I know has been having posts when Gutenberg has a new point release that will list in great detail. I've actually spent very, when I'm trying to get more familiar with all this, I've spent a lot of time looking through all these different things we've done, but it's, it's in great deal about the features that are being worked on. I think as we get, as we get closer, I think you'll probably have, my, my expectation would be more high level posts about what's going on. Currently we're having more development level posts there, but make.wordpress.org is the, I believe is the core one. I think it might just be that, I thought I was able to look and just see that at the top level. It's in the neighborhood. Sorry, I can't give you the exact answer there. Sure. I don't believe that's currently possible, but I believe the, the idea is, I mean, some, some of this is still like the dream, you know, and, and so, and so we're trying to make that reality. So that, that would be the good example of something that I don't, I don't know if that would be, I can't speak for the design perspective on it. That would be something that I would want as well. I don't know if that's going to be going into core or whether, whether that could be a, even a custom block if it doesn't go into core, where you can actually specify what you want the width to be, and then that, that would be something you could do. Oh, sure. Okay. So I think for those who couldn't hear, I think that the idea is that we, we do have columns right now. They don't, in, in, in experience don't, don't seem to be responsive yet. So that's, that's where we are. But, but, but column nesting, nesting blocks within columns is, is working. Okay. So the, the first question is how, how can a, an average plugin developer, theme developer track Gutenberg development and sort of try to start targeting Gutenberg even while it's still a moving target? And then the second, second question is, will there be a lag time between when it's merged and when it's released? Will there be a greater time than we're used to with releases? So for the first question, I think the way I'd be doing it personally is, is trying to track the, those posts on, on make.wordpress.org, there, there is a lot changing and it's, it's honestly hard. And I've just been starting to get into it over the last three to six months. And it's been, it's been challenging for me to track everything. And so my first strategy was not to track everything, but tracking certain things that I care about and just try and, and maybe making, doing experiments and starting, you know, even just maybe sketches in code about how I'd be integrating with things. And then maybe as things start firming up, I can take those sketches and make them a bit deeper. That's not wonderful advice, but that's the best coping strategy I think I would, I would suggest right now and just paying attention to those blogs. And then for the second question in terms of the lag time with release, I definitely can't, can't have any, give any authoritative comment on that. But it certainly seems like a good idea with something that, that is making so many waves to, to allow people additional time to, to pause and reorient if they wish. I think the idea is, is the rest of the percent, you know, and you can't, in no way can you ever please everyone. But I think, I think the idea is that you can, so oh, I forgot to repeat the question. The question is, what's the point? Or why, you know, what's the value in doing this? What problem are we really solving? Because we already have about 30 percent. We have one, I got it, okay, I'm about, I got to cut this off. So the idea I would say is that it does improve, I believe would improve experience for existing users in the, in the ways that I talked about, but also for people who are using things like Wix or other sort of site builders to, to give, to make that WordPress more accessible to them as well. So I think, I think that's the idea. I think I don't, we, we can talk, oh sure. Thank you very much.


Myself, Dr. Satish Kumar Kashi, Walshan Institute of Technology, Solapur, presenting a topic, Reservoir Planning, Estimating Reservoir Capacity of a Dam by Mass Core Method. Learning Outcomes. At the end of this session, the students will be able to explain mass core technique adopted for estimating required reservoir capacity of a dam for particular inflow or clop pattern. And the students will be also able to estimate required reservoir capacity of a dam reservoir for a particular inflow or clop pattern through one example. Overview. We will have a typical view of a dam reservoir. Then we will discuss the mass core method. Thereafter, we will discuss a numerical example on this method. This is a tehri dam from India and the reservoir which is formed by this dam. And our problem is dealing with estimating the capacity of such a reservoir for satisfying a particular inflow or clop pattern to the reservoir. Outflow will be due to demand. These are different storage zones of reservoir with unguided spill bed. So this is a dead storage. This is the conservation storage zone. This is the spillway crest matching with it. This is the full reservoir level. This storage is flood control storage. This is sarsha storage. And then we come up to the maximum water level. So we depend upon this conservation storage for satisfying the demand. For gated spillway, the spillway gates will be up to this level. And thereafter, you can have this maximum water level. Then this spillway crest level. And this is the full reservoir level corresponding to the conservation storage. And this is the top flood control pool. So this is the sarsha storage in this case. Now, let me discuss something about hydrograph and mass core. Hydrograph is a plot of discharge versus time. And mass core is accumulated discharge versus time. Mass core will continuously rise as it is the plot of accumulated inflow. And if constant rate of withdrawal is required from the reservoir, the mass core of demand will be the straight line having a slope equal to demand rate. Let us see through figures. So this is a plot time versus discharge. So you will find discharge goes on varying with a time. And when we go on accumulating this particular flow on y axis with respect to time on x axis, we will be getting this particular mass core or accumulated inflow core. In the same way, we can have, if we have constant demand, the accumulated demand will come out as an inclined straight line. If we have variable demand in this way, we are supposed to get the accumulated demand in this way. Now, the very simple principle is used here. If we have accumulated with respect to time, and if you have cumulative inflow core with respect to time, at the maximum vertical distance in between these two mass cores, mass core of inflow and mass core of demand is going to give the required reservoir capacity. So here we find there are three places where departure is there. Out of that, this is the maximum departure of the mass demand core from the mass inflow core. So this particular distance we need to find in terms of the cumulative inflow and cumulative demand in terms of million cubic meter, that will give us the required reservoir capacity to satisfy this accumulated demand with respect to accumulated inflows. So let us go for two questions. The crest of ungated dam spillway is provided at RL equal to that of its maximum reservoir level, dead storage level, maximum conservation level or none of the above. One more question. The capacity of a storage reservoir can be decided by using the mass core of inflow, the mass core of outflow by both A and B and none of the above. Then we will go to the answers. The crest of ungated dam spillway is provided at RL which is corresponding to maximum conservation level, as we have seen in one of the figures. And the capacity of a storage reservoir can be decided by using both mass core of inflow and mass core of outflow. Let us go to a problem based on the mass cores. This table shows the inflow of water at hydro power generation site over a period of two years. Calculate what maximum uniformly demand can be satisfied by given inflow pattern assuming policy of using total available water. Also calculate required reservoir capacity to use this inflow without allowing any spill of water. Now, here we observe from November 11 to October 13, what is the inflow? So, we observe that the total inflow sum of this column comes out to be 1920 and that is to be utilized over 24 months. So, you can satisfy uniform demand of 80. That is why in this column we have written 80 as an uniform demand. Here we are not allowing any spill and for that we are going to calculate the reservoir capacity. So, the cumulative inflow values are shown here. For example, by the end of November 11, cumulative inflow is 80. By the end of December 11, it is 80 plus 65, that is 145. By the end of January 12, it is 145 plus 60, that is 205 and so on. In the same way, we have cumulative outflow values or cumulative demand values. So, as these are constant 80, 80, 80, it will be coming as 80, 160, 240, 320 and 400 and so on. Now, here graphically you can observe these. So, the monthly inflow pattern is shown by this particular graph. So, naturally the inflows are lesser in the months of December, January, February, March. Again from months of June the inflows increase than demand. Again in the next year, in the same period again inflows are lesser. So, we store this excessive water in the reservoir for which we need capacity and that store water is used in the further part of year when the inflow is less than the demand. That is why we need a reservoir capacity. Again here inflow is more, again here inflow is less than demand. Here we are assuming the constant demand. Now, here it is another graph of cumulative inflow versus cumulative demand. So, you observe here the cumulative demand comes as an inclined straight line going in this way. The cumulative inflow it is going in this way. So, here we find that the cumulative inflow is less than the cumulative demand. So, here in this case we will have to use the water which would have been stored in the reservoir in previous season. Here cumulative inflow is more than cumulative demand. So, here we are going to store the excess water in the reservoir. And then the required reservoir capacity will be some of the is maximum departure here on lower side and maximum departure on upper side. So, here again you find these two departures in between these two lines but these are small. So, maximum departure on upper line is here and maximum departure on lower side is here. So, you will find that the maximum departure here it is in say May 12, 560 minus 340. So, it will give you 220. So, this 220 deficit is to be satisfied from the storage. Also we need this additional 160 that the departure here in September 12 to store the incoming water. So, if you have reservoir capacity of 380 MCM, then you will be able to satisfy this uniform demand in any case even though there is fluctuation in inflow. So, these are the references which are used for developing this presentation. Thank you.


Hi folks, this is Don Schank with Red Hat. I wanted to talk to you today about the Nougat repository and your project.json file. A little debugging tip that helped me. As you see here in my project.json file, I have the Microsoft.diasim reader set to version 107. I'm going to change that. Using IntelliSense, I can go down and see all the different versions that are available. I'm going to pick this one just randomly. I'm going to save the file, and then I'm going to hop over to terminal and do a .NET restore. Watch what happens. Because it's the latest and greatest, I think it's built using dependencies of RC3, and I can't find them. So that broke. So what happened? Well, if I go over to Nougat and look at that same diasim reader, I can scroll down to the bottom and you can see the different version history. Ah! Look here. The latest stable version is 107. So if I go back to a code and change it to 1.0.7 and save that file, and go ahead and run my .NET restore again, this time it works. So that's just a little tip I want to give you to help you when you're debugging. It can be confusing at times, and this might help. This is Don Schank at Red Hat with redhatloves.net, and please subscribe to this channel, and stay tuned for more episodes.


The room is very full. We're very glad to be here. My name is Emily. Yes, and my colleague is Fredrik. We only have one mic, so we're going to switch in the middle, sort of. But let's get started. I have an agenda here, and at the beginning we see... I planned to walk through the definition of a pipeline, but considering the audience I think that's unnecessary. So I'm going to skip that. And I'm coming from Ericsson, which is not open source, of course it's a company, but we do contribute to open source, and that's why we're here today. I'd like to start off with describing what kind of challenges we've seen considering the communication between different CI CD tools. And then I'm going to present the way we solved it. Yes, I'm going to speak a little bit louder. And also how we open sourced our solution, and how Fredrik and his company Axis started using the same solution. So let's skip this part, as promised, and instead go straight for the communication challenges that we've seen at Ericsson. So first of all, why does Ericsson care about CI CD? Well, any company that produces software should care about CI CD, obviously. We have a very complex environment. We have a lot of different products going out to our customers. Different configuration applied on top of them, considering if it's going to be to customer A or if customer B wants them. And we have many different pipelines and different pipeline tools used to produce our software. Very often they're integrated into each other.  And I'll go through what I mean by that later. We are a very large organization. We have hundreds of teams developing our products. Each one of them uses different toolings. And the demands on traceability is very high. We need to keep track of our software. We need to see which stages does it go through in the pipeline, no matter if it stops at delivery or if it goes all the way into deployment to the customer networks. We need to follow and see where does our software go. We also need to be able to monitor it, independent of whichever technology we use in the background. We need to be able to keep track of the important KPIs. And I guess also visualize it in a good way. And one visualization tool would be nice. So I spoke about connected pipelines. And what I mean by that is we usually integrate our products into each other, sort of. So they're hierarchies of products. So you've got product A and B to the left here, and they're produced in their own separate pipelines before they're together integrated into the next level of the next connected pipeline producing the product AB. This is a very common phenomenon at Ericsson where we have multiple integration spots. And it's tough to keep track of all of these dependencies to integrate upstream and see where does this software come from and how it has been tested before we integrated. And again traceability is important here all the way. So I've tried to summarize into a few questions what are the exact challenges we see? What is the problems that we need to solve? One thing is when we use different pipeline environments, how do we communicate about when our product has been delivered or released? Let's say our product A is done here. How does somebody downstream become aware of this? How can we announce this to the world? And how can we, if we have another perspective, how can we become aware when others release their software automatically the independent of whichever technology stack we use would be nice to become aware of, oh hey this version X, Y, Z is now available so we automatically integrate it into our pipeline and go for it. And how can we visualize these connections? How can we see what kind of tests has been done upstream but also downstream on our software later on? How can we see how many has downloaded our products? It would be nice to know. Were their tests successful into their environment or not? And why? So the solution for this was that we focus mostly on the communication. How can we communicate across different tools? So we came up with a solution that's like a common language if you will across these different pipelines, across different tools, across different visualization tools that could be based off the same information. And we called it Eiffel. Now Eiffel is created in 2012 so we've been using it for a lot of years internally. A couple of years back we open sourced it and it's now available on GitHub. But what it is, it's a message protocol. It's event-based. It's defining a set of events that you can use to communicate about different concepts used in your pipeline. Be it artifacts, be it tests, source code changes. You can communicate about this independent of whichever technology you use. It doesn't matter if it's a Java application, it's uploaded somewhere to a Maven repository or if it's a Docker image you uploaded it to Docker Hub. And you can still communicate about it in the same thing, in the same way. And what I think is great about Eiffel at least, you can cherry pick whichever events suit your needs. You don't have to take all of the protocol, it's a lot of events. You can cherry pick the ones that you specifically need in your use case. So let's say you're only interested in the test case related events, then you only care about those. And the events are also linked together. And that's very important for us at least to maintain the traceability between them. So you can trace back from the latest event, you can go backwards in time and see the whole pipeline chain. You can represent the pipeline. And with Eiffel, you can answer some of the questions I posed previously. For example, when we have a new artifact available, you can send out an event saying that I've now created this artifact. You see it to the left in the picture, it's called Eiffel Artifact Created Event. What comes after that could be a published event. Whenever you upload it somewhere, you can send additional events, linking back to the previously created artifact. The linking here is important. The protocol itself defines how you can link your events, if they must have or if it's optional links. These are all in JSON format, as you're wondering. Next question could be, how can we visualize our pipeline? A pipeline consists of many different steps, right? Independent of how it looks, you want to maybe tell the world about what has happened, how do we visualize this? This is a very simple CI pipeline.  Very standard case. Some of the Eiffel events that could be used for this are, for example, these. You can have an artifact created event to signify the first built. This is where you actually build your binary, whatever it might be. Then you start some tests, and then you might want to send test case events, so you've got the triggered, started and finished events for this. These can be sent, of course. These jobs are in parallel in this pipeline, so you can send them in two sets. Then comes the artifact published event, as the last one, to signify that, hey, now my artifact is available somewhere for downloading. I'm going to show you the exact same side of events, only connected in an event graph to make it clear. So start to the left, got artifact created event. This is the first one in chronological order. Then comes the test case events, which links back to the artifact, because this is what we're testing. And the link name in this case is called item under test. Makes perfect sense to me, at least. Then comes the test case started event, linking back to the triggering. And then we've got the finished event, test case finished event. This one contains the result of the test, if it was successful or not. Now, of course, if you have several test cases, you might want to group them under some sort of label that's saying, yes, I've tested it to this extent, and I want to label my artifact now. This is ready for the next level of delivery somewhere. Then you can send the conference level modified event. This is very free-formatted in a way that you can name the conference level whatever you want to, as long as you standardize it, it shouldn't be a problem. And then you point back to the artifact that you've created. So this is very useful for us as listeners or consumers of this product. We know once it has been tested enough, we know when it's reached the conference level we want it to have before we actually start using it. And once the last event comes in, it's the artifact published event, we know where we can find it, where is the artifact located, where can I download it. And I have one last wrap up here. As I said, we have open sourced this, and it's available on GitHub. And we really hope that the community keeps growing and getting more contributions, because we see that a lot of different companies and organizations have the same problems that we faced. And one thing I liked about Eiffel is that it provides one common language across different technology stacks, across different tools you might use. So you can base visualization tools on the events in this data, for example. And what's also important is the links between the events. It enables traceability, so you can follow a complete set of pipeline. You know what has happened to your software, and you know where it might go even further downstream. And I'd like to invite Fredrik to this side of the room so we can switch mics, because he's going to tell you about how Axis started contributing and using Eiffel. Set this up here. Okay, so I'm from a company called Axis Communications, and we do surveillance cameras, which is kind of a scary thing, but there's a lot of software running in these cameras, and somebody said roughly around 20 million lines of code in the camera, so there's a lot of software going into this small thing. It's basically a Linux box, but still. And we have nowhere the scale that Ericsson has. We have about 1,000 developers in total, and the teams that do the cameras are about 400 developers, and about 150 testers.  And I'm going to try to tell you our Eiffel story. Emily gave you a good background on what Eiffel is, and I'll try to go through some kind of a timeline, how we found out about Eiffel, and how we adopted it, and how we now very much would like to drive all of our pipelines using it, at least as the ambition for the future. And first, I would like to give you some context on what exactly it is that we do. So Axis is quite an old company, and we've done, in the history, we've done network-connected stuff, and which is basically just making some kind of hardware, putting it in a box and selling it. That's the standard Axis way that we've been doing it for a lot of years. And it's basically what other companies do also. They sell cardboard boxes with tech stuff in it. But more and more we've been seeing a demand from our business and from our customers that they want complete systems, they want cloud integration, they want a lot of stuff, which in turn gives a lot more software that has to be tested, has to work together. So that's where the challenge of knowing which versions work together, which software stacks work best together, and so on. So that's kind of the similar challenge that Ericsson has. But back to our story. The first recorded presence of the AFL protocol at Axis. As I've heard, there were a couple of engineers attending some kind of a conference or a meeting where somebody from Ericsson was presenting some kind of visualization tool, how you could visualize your software. I don't think it was called, I don't even think it was referred to as a pipeline, but still some kind of software flow. And they found that this was something called AFL, which was underneath here. And they got intrigued. So they started doing some tinkering on their own and trying to make something with AFL in the Axis context, which was fine but really didn't lead anywhere. And then it resurfaced in some kind of a research academia industry project that Axis had, where some of the researchers had found out about AFL from Ericsson also. And it resurfaced and they did some more tinkering and some more engineers got interested, but it was still kind of under the radar stuff. Just engineers like technology enthusiasts that did stuff, but nothing that really drove the business or was a thing. And the next big thing, in my opinion, was when Axis actually released something that had to do with AFL. So these engineers had the tinkering more and they wanted to make something of it. They wanted to, AFL, to produce something that was of value. So we used Jenkins as almost everybody else. So they made a Jenkins plugin, which was very basic. It basically produced an artifact created event when we did a build. That was all we did. So it was kind of worth us on its own, but still it's kind of a footprint that now we're actually producing AFL events. We have a message bus where there are events coming out. But there was really nobody listening, which is kind of a problem, because when doing this type of thing, the whole point is to somebody listening and acting on the events. And there is like a chain created and a flow. So our biggest problem here was nobody was listening and if nobody's listening in a pub-sub culture, it's kind of hard to know if you're making sense in the beginning, at least, because you have to know that in the beginning you have to have some kind of acknowledgement that your event, it was useful. There's value to it. So we had to create some kind of value in our minimal AFL implementation. And this is basically where I came in, in the AFL thing. I was a part of a team that does test automation and we were struggling with the testing part of our CI pipeline. It was kind of old and it didn't really want to do what we wanted to do with our testing. So we started looking to rebuilding it, basically, or changing it and so on. And I had a coffee discussion with a colleague of mine. He was one of those AFL tinkering engineers. He said, you should look at AFL. If you're going to do things from scratch, you might as well look at AFL because it's pretty cool. You can do cool stuff with it. And we looked into AFL and me and a colleague, and we really liked it. We saw that this was something that could probably not solve our immediate problems, but there was a bigger issue of the system of systems talk and knowing information about the software that goes in from everywhere. So we decided to make our new testing part of the CI CD pipeline talk AFL and understand AFL. And in this, we started listening to the Jenkins events, the lonely guy over here that was playing AFL music and nobody was listening. So we actually started listening to that and we started triggering our tests based on those events, which gave us much more understanding of what it is like to have an event-driven pipeline and what it was like to adhere to a protocol like AFL. And we actually wound up being a great listener today for protocol. During the development of our testing pipeline, we had to learn AFL, basically.  And two of them, which were kind of important, at least we thought, we had to contribute back since it was an open source. If it was an open source community and open source protocol, we said we can contribute here. We can learn people how to teach people how to use AFL. And these two libraries, the AFL Python lib, which is a kind of small library that lets you publish AFL messages and listen to AFL messages on the message bus. It's very useful if you want to get started with AFL. And then there is something called the AFL Graph QL API, which is basically an API on top of the event repository, which is basically a storage for events because if you want to look at events back in history, you have to store them somewhere. You can't just keep them on the bus. So that's basically our Graph QL, which is kind of useful if you want to start tinkering with storing events and looking back in history and so on. And this open sourcing of this got access more engaged in the community. And we actually, there's a conference called AFL Summit. It's a very small conference where we actually access actually hosted it this fall. And in moving forward, we're going to try to keep the backlogs, working with an open backlog concept. As we learned about AFL, how our journey will try to contribute directly to the community rather than just doing stuff inside and then just dumping it outside, which is kind of a bad thing. And then moving forward, as AFL is now a thing at Access, we actually have a small team that work with AFL and we're really going to try to drive all of our pipelines. We see them being event-driven in some way. Moving forward. And also we're going to try to contribute more to the AFL community, trying to, like Emily said, want to spread it, want to make more people try it out and see if it can become a thing. So we'll try to contribute more of our experiences moving forward in 2020. And that's my access AFL journey basically. And we'd like to thank you for listening to us. And here's some contact information. The AFL community on GitHub and we have a Google group and a Slack channel and a YouTube channel also with some videos if you want to learn more or get a more basic tutorial of what AFL is. And now I guess it's questions. If not, how can I do it in the jobs or say just manually to send events to the AFL? So the question was, is there some kind of a GitLab integration for AFL? Not that I know of currently on GitHub. I don't know, not yet. And I'm not quite sure how GitLab works. So it should be possible. I don't see any big technical blocking it. It's just that somebody has to contribute it and do it. So let's say, is there any kind of stuff how to do it within my, like manually, like triggering events? They're awesome. If you look at the Python library, there is some basic tutorial how to set that up, how to send events and receive events. And then there's also something called, I think it's called AFL easy to use, which is basically a set of Docker containers that you could just spin up and you get a full, like a small pipeline which produces events. It's something that Ericsson contributed. I don't know if all of it is open sourced yet. Might be, but it's basically something you can try out to get some messages going to try to get a feel for how it works. Yes, absolutely. So the question was, since we've been sending events for several years now within Ericsson, we have, of course, a lot of data accumulated. So the question was if we can look at lead times and see where are the bottlenecks in the pipelines. And yes, of course, we do have that possibility. And that's one of the great benefits that we've seen internally, at least. And that's why I think, I don't know, how many millions of events we have stored, but there's a lot of them. So it's indeed possible if you have, like, implementation of a storage somewhere, and then you can look it up and you can see, because all the events are timestamped. So you can also see lead times between the events, between different activities in your pipeline, which is very useful. And yes, Fredrik mentioned, and just like to add, because aside from the protocol, we have some example implementations of services surrounding the protocol, helping to send the events, helping to visualize them. I think we also have open source, and they're more coming, they're more planned for that. It's just a matter of prioritization and so on. Any more questions? Yes, in the back. So the question was have we tried to use Eiffel outside of development to trigger some manual activities, if I understood it correctly. And I'm not aware that we listen and act upon these events and then doing some sort of manual step. Of course it's at all possible, but the listeners usually are performing some sort of automatic task afterwards. And as far as I know, we mostly focus on up until continuous delivery sort of. Deployment stages don't really trigger on Eiffel events later on yet, at least. I can add something to that. So there are like more generic Eiffel events, like announcement events that say something, that something has happened. And you could definitely use that for signaling other people in the organization. And we actually use that to sort of a debugging thing so we know that we've gone a certain path through our testing CI system. We do announcements here and there to see okay, we've gone this far because it's a microservice architecture and it's kind of hard to keep track of everything. So it's a handy thing, but there are announcements events that are very generic, so you could use them for almost anything. Any more questions? Okay, thank you.


Atatiana Jefferson was a 28-year-old pre-medical graduate of Xavier University of Louisiana. She sold medical pharmaceutical equipment from home while studying in order to apply to medical school. Jefferson moved into her home in Fort Worth, Texas to care for her ill mother and young nephew. In the early morning of October 12, 2019, Jefferson was up late playing video games with her nephew. After a neighbor called a non-emergency number stating that Jefferson's front door was open, the police arrived at her home. Jefferson came up to her window to observe police outside her home with her handgun. Officer Aaron Dean had walked into the backyard and within seconds of seeing Jefferson, a single shot was fired through her bedroom window by Dean, fatally hitting her. Her eight-year-old nephew was present in the room the entire time. He saw her fall. Jefferson was later pronounced dead at the scene. Two days after the incident, Dean resigned from the Fort Worth Police Department and was arrested on a murder charge. Today, standing up for the rights of those who are marginalized and discriminated against in our communities and nation is more important than ever. Please support these organizations and learn more about the countless ways racism and bigotry affect this country.