Auto-Lite and its 98,000 dealers bring you Mr. Charles Boyet in tonight's presentation of... Suspense. Tonight, Auto-Lite presents a story about a man who successfully played both sides of the law. A true story which we call The Docs, Final Case. Our star, Mr. Charles Boyet. Hi, Harlow. How are you feeling? Just like an Auto-Lite stay-full battery app full of pep, plenty of endurance, and set to start anything. But the Auto-Lite stay-full needs water only three times a year in normal car use, Harlow? Right, Harlow. That great battery has fiberglass retaining mats protecting every positive plate to reduce shedding and flaking and give the Auto-Lite stay-full longer life as proved by tests conducted according to accepted life cycle standards. That's proof enough for me, Harlow. And millions of other smart drivers have. So friends, visit your neighborhood Auto-Lite battery dealer. He services all makes of batteries and has an Auto-Lite stay-full for your car if a replacement is needed. To quickly find his location, call Western Union by number... And ask for me, Operator 25. I'll gladly tell you the address of your nearest Auto-Lite battery dealer. And with your Auto-Lite stay-full, the battery that needs water only three times a year in normal car use. And remember, from bumper to tail light, you're always right with Auto-Lite. And now, Auto-Lite presents transcribed VDOX final case, starring Mr. Charles Boyer and hoping once again to keep you in suspense. To Emil Dubigny, Commissioner of Police, Monsieur, I, VDOC, in writing this report, beg your indulgence. This case, Monsieur, is my last. When this series of robberies began, I was, as you know, no longer with a suraté. Ten years ago, I had retired and, in the last unhappy months, had been touring the provinces with a variety show. Monsieur, Madame, it gives me infinite pleasure to introduce to you that infallible, magnificent, virtuoso of crime who, for 18 years, through the greater glory of the suraté... Standing in the wings, the sad realization which for months had oppressed my heart was confirmed that, already, after ten short years, I was forgotten in the capitals of the world. Then applause grew me from my unhappy rubber. And I give you... Merci, mes amis, I shall describe to you some of the highlights of my career, show you some small aspects of my technique, and answer questions on the art of detection. Monsieur, Monsieur Lebeck, if you please, my souvenir. Advance, madame. Ah, the shoes of poignants. These shoes were worn by poignants, the brigands of Rouen, who frequented county fairs.  It was this pair of shoes which furnished the essential clue. Well, finally the bag of tricks was emptied. And that day I took no pleasure in the wild applause of the ignorant and credulous. When I entered my dressing room... Ah, Met, this young man has come to pay his compliment. Ah, and Lebeck was telling me your motto. Justitia virtutum regina, justice is the queen of virtue. My motto? No, it's Lebeck who fancies himself a classical scholar. Oh, I misunderstood. My name is Williams. I came back to tell you that you are a very great artist. Indeed, how would you know? Well, in a small way, I'm in the same kind of work. A musical comedian, perhaps? Oh, no, no, no. He is from Scotland Yard Vidoch. Oh, in a small way, it's correct. Yes, I'm over here on a case. You say the two were formerly with the Serpents? I was formerly commissioner for 18 years, commissioner. Oh, well, I'm on my way to see your present commissioner. I believe his name is Dubigny. A blackhead, a bangling fool, give him my regards. Yes, I will do that. And wish him luck in solving these recent robberies. Oh, you know about them? Oh, all France knows about them, and he's laughing at the police. One moment, you are here because of the robberies, Monsieur? Well, yes. Yes, the Serpents seems to think an Englishman is involved. Why, what do you ask? To give you my sympathies, the case will never be solved. No? Why? You see, Dubigny has been fortunate. Since he became commissioner, there have been no other crimes of this type. It involves a master criminal. It takes a master to catch a master. You seem so certain, Monsieur. Well, naturally, I am the doc. Later, commissioner, Williams described to me how he arrived at your office to be greeted by a scene of noise, confusion and desperation.  Fool, fool! But their uniforms were authentic, commissioner, and they said they needed the cabinet for evidence. So you helped carry the cabinets out of the truck. But it was an official truck. They had an order signed by you. Signed by me! Signed by me! You may leave. Get back to the private queue. Yes, commissioner. Well, well, what do you want? I'm Williams, and Scotland guard.  Forgive me. This is a most trying day. Commissioner! Yes, yes, Your Honour, Baudenay. What progress have you made in finding the criminal who stole my medal? We must be patient. And all my uniforms. General, I beg you. Unless you find a way of curving these crimes, we'll find a new commissioner. I failed to see the humor. He said it involved a master criminal. Who said this? Vidoc. Vidoc? Yes, I met him by chance. He's a fascinating man. He's a real artist. Greatly overrated, Monsieur. I can assure you. He once held this office. His methods were mostly regular. Still, in the case of these robberies, he might be able to find... Never, never! For years, Monsieur, his reputation overshadowed every man who held this office. Even I had to suffer these humiliating comparisons. Oh, how is that? Vidoc would have done it so. Vidoc would have caught them sooner. Vidoc would have known immediately. Yes, that must have been very irritating. I forgot his name to be mentioned. I took certain steps, which made it impossible for him to remain in Paris. I managed judicially to keep his name out of the papers. Now, finally, he is forgotten. Still, in the case of these robberies, he might be able to find... Never! Of course, I have no way of knowing the twists and turnings in your brain, before you make the inevitable decision. I can only say that your messenger did not take me wholly by surprise. Naturally, as my duty to France, I instantly obeyed your summons. Come in, come in, Vidoc! How are you, mon ami? Excellent, come in. Well, bonjour, Inspector Williams. Hello, Vidoc. I want to discuss these recent robberies with you, Vidoc. Inspector Williams and I have been discussing them. Shall I summarize? Please do. We are satisfied that they've all been carried out by the same gang. The crimes are all of a similar nature. Yes, the robbery of the National Museum, of the Petit Palais Royal, of the home of General Bourdonnet. Yes, the criminals have consistent teeth. We've watched all the fences closely. Nothing has turned up. Not of these, not of Roche. I think they may have been smuggled out of France. No, all the stolen goods are still here. The thieves are waiting. They have time. Then all we can do is wait. You asked the help of Vidoc. I never wait. Well, well, what will you do? Gentlemen thieves. Well, they are a very special lot, a tightly net, highly professional group where each man knows everything about the others. Yet sometimes one may be found who is jealous of another. And can be induced to talk? For the commissioners had every known dual thief in Paris picked up in question. No thief will talk to a gendarme. It's a simple fact. Dubigny never comprehends. To whom? To another thief. I once knew a gentleman thief. I doubt if he is involved in these robberies, but he is likely to know the ones who are. The Marquis de Villiers. A Marquis? No, he assumed the name for professional reasons. He gained entree into the greatest houses with such ease that he was also called Monsieur Latschke. Oh, he sounds charming. And you believe this Marquis would know? Eh, if I can find him. He isn't in Paris? He is in hiding. Has been for years. I'll get in touch with some of my old friends. You'll need some officers. Ah, what a bungler. No, no, no, none of your bullies. I'll go alone. Unless Inspector Williams would enjoy meeting the Marquis. Inspector Williams and I met that night in the Luxembourg Gardens. It was striking ten, and news vendors were crying their headlines reporting the public to patients, telling them that their infallible police were at work. Both Williams and I were dressed as sailors. We crossed the gardens and began our search, first calling on a certain woman of the Fogul Saint-Germain. Yes? What do you want? Adele. You? Yes. I am looking for the Marquis. The Marquis? Oh, sherry, I am sorry. I have not seen him for weeks. And to a certain Maître-D, in a fashionable restaurant. And to a young dancer at the stage door of a well-known theatre, without success. Finally, we stopped on the boulevard to buy white violets from an old beggar. The Marquis, Monsieur? What do you mean? Café de la Tour. Café de la Tour. Merci, old man. Café de la Tour. Here we are. Down these steps. What do you want? Madame, are you expecting the Marquis? Who are you? Two lonely sailors who have business with the Marquis. And white violets for Madame. Oh, he'll come in. He is not here yet. Eh, here. We'll take this corner, where we can see him. What a place. Is there something to drink, Monsieur? Eh, eh, two Calvados, Madame. We must hear. Yes, cafes like these are the unwashed linen Paris hides from her guests. But I feel most at home with the criminals who frequent these places. Ah, because you worked among them, huh? No, because I was one of them. Look, here, on my chest. But G-A-L... G-A-L? Burn into my flesh. The mark of the chain gang. You? I spent eight years on the chain gang. But how then? It was supposed to be fifteen, but I escaped. In the habit of a nun. Oh! But did they know when you were in the certé? Well, of course. That's why I worked there. Do you know what it is to be a fugitive? To live expecting a return to that hell where I couldn't stand it. So I made a supreme gamble. You went to the certé? Ah, no, mon ami. What was more logical? I knew everything about crime, every trick of the trade. And then? Well, then, Monsieur, inevitably, I became commissioner. Here he is. The Marquis. Madame, have you a corner table? Oh, certainly. And I have cooled some of your wine. I will bring it immediately. No, no, no. Well, we'll wait. Be ready to leave. Leave? Just when he's around. No, no. Do as I say. When you see the old woman coming back. Now. Pardon. Pardon, Monsieur. May I pass? Oh, Flo, just a moment. What is this wine you have? Oh, please. It has been ordered specially. I'd like to assemble it. Oh, oh, please. No, no. No, no, no. It is for the Marquis. Monsieur le Marquis, your butter. Eh? What? What? You take my wine? I think not. He's got a knife. Fidoque. Oh. I'll handle tea. And those with knives. Ah. Tea. When you steal wine, Monsieur. Memento mori. Remember, you must die. We all must die. Stand back. Against the wall. Attention all. Be quick. Now. Who was responsible for this fight? It was the sailor. He took the wine. Anna, why blame me? I was insulted by the Marquis. I insulted you. Liar. Enough. You are both under arrest. Here. Put out your hands. Locked together. A cozy, loving pair. Auto-light is bringing you Mr. Charles Boyer in the Docks' final case. Tonight's presentation in Radio's outstanding theatre of thrills. Suspense. Hey, Harlow. How would you describe an auto-light stay-full battery? Why, that's easy, half. It's the world-famous battery that needs water only three times a year in normal car use and gives longer life, as proved by tests conducted according to accepted life cycle standards. Well, you just can't buy a better battery than an auto-light stay-full. Tops and quality and performance, eh, Harlow? You bet, half. And it's because of advanced engineering design and a number of glass retaining mats around every positive plate that reduce shedding and flaking. It's the battery of a lifetime. You bet it is, half. So friends, visit your nearest auto-light battery dealer. He'll gladly check your battery. To quickly find his location, look for the auto-light battery sign or phone Western Union by number. And ask for me. I'm Operator 25. I'll tell you the name of your nearest auto-light battery dealer, where you can get an auto-light stay-full. The battery that needs water only three minutes. And remember, from bumper to tail-light, you're always right with auto-light. And now, auto-light brings back to our Hollywood sound stage Mr. Charles Boyet in Elliott Lewis' production of V-Doc's final case. A tale well-calculated to keep you in suspense. And so, according to plan, my plan, the Marquis and I, V-Doc were thrown in the same cell. For it has been my experience, Commissioner Dubigny, that to gain immense confidence, one must share the hardest blows of his personal fate. When you learn that, you will have taken the first small step toward mastering the art of detection. But enough. I had boasted to Inspector Williams and I believed to you that the Marquis would talk within 24 hours. But the hours dragged on and he sulked in his corner and I in mind. Finally, I gave a pre-arranged signal to a passing guard. You, on your feet, I only stand in the presence of gentlemen. Then, up, you're to come with me.  This is being taken upstairs for questioning. We have a tip on this fine bird. A tip? That you know quite a lot, Monsieur, about these robberies now much. How did he look when you said you had a tip about me? Interested, Monsieur V-Doc. And I think there was sympathy. When I reached your office, Dubigny, you were eating your dinner. Yes? Chateau brillant with sauce and ricotta. And I thought, Commissioner, how you had never lived as I had so often on nothing but bread and water. But I was in your office because of duty, so I wasted no time. Well, the marty will not talk. Ah, well, I am afraid this case is too much for you, V-Doc. Your trip is sprung, the bird is caught, but he will not sing. Because you have his stool pigeon in the next cell. How did you know? What do you take me for? His ears waved through the bars. Remove him. Any more advice? Yes.  Ah, a pleasure. Ah, after I have eaten. Oh. Chateau brillant also and pomme souffle and then a sweet. The beating was genuine. I insisted on that. The artist must make sacrifices to be near, must be willing to risk his flesh, his very life on every turn of the wheel, which is why you will never be V-Doc. It was two hours later when they threw me back into the cell. You will talk. You will talk yet. But I know nothing. Here. Let me see that cut. Oh. I told them I knew nothing. Whoever committed those robberies would not let himself fall into the hands of the police. That is right, my friend. But I must say I was flattered to think they believe that I... You are right to be flattered. What do you mean you? Do you know them? The men who robbed the petit palais, the man who planned it. Oh, brilliant, incomparable. Yes. I know them well. And so the birds sang. And I was ushered back to your office just before midnight. But it was fortunate you were alone to be near for much of what I had to say was only for your ears. Well? Well, V-Doc? Well, the case is solved. Let me sit down, please. Well, well, did the marquis confess? No, no, not so fast, mon ami. I know the names of everyone involved. I know where the stolen goods are stored. Excellent. Excellent. Well? And I know I'm very weary of crime, commissioner, of greed, and envy, and fear of men who seek success through fraud because they have no talent. All of us have poor crime. And I am weary of you, Dubigny, who stole to achieve your success. I stole? My name? The only thing of value I owned. When I left the surety, I left a monument that towered in the minds of my countrymen. You stole it. You tore it down, stone by stone. Why? How could I? You have to use your whispered in one ear and then another. You drove me out of Paris hoping that I would be utterly forgotten. Am I right? V-Doc, I beg you. You know the name. Yes. But there is a price. How much? I have composed a statement for you to sign. I, Emile Dubigny, declare that whatever poor talents I possess, I owe entirely to the master of all detectives, V-Doc. But what would you do with it? I will use it as I see fit. When I see fit. Very well. There. Now, the name. Here is the address where the stolen goods are stored. But who? If you make a raid, now I said immediately you may find the whole gang there. But their names... Harry, commissioner, do you need the names if you can catch them with the goods? I'll let you lead the raid in person. Knowing that newspapers would send reporters there, I was willing to let you have the glory for once. I remained in your office, drinking your excellent cognac. When young Inspector Williams joined me, he had been informed that the case was solved. A most charming cognac. Yes. Now tell me, the marquee was not involved? No, no, no, no. He merely disclosed the names. How many were in the gang? Seven. Yes, seven. All experienced thieves. Was there an Englishman? Why yes. I believe he said there was one who had escaped from Dartmoor. The commissioner's reasoning was correct on that. And the mastermind? The marquee did not say. But surely the doc, you know. Not of his certainty. Then I have surpassed my teacher, because I know. Oh? And who is he? You. Mr. Williams? What possible proof? Proof? My proof is the marquee. In the Cavite Latour, when you and he staged that very convincing fight, what staged, Mr. Williams? The marquee shouted, memento mori. What of that? A Latin motto. The marquee is LeBac, your assistant in the variety show. The man who fancies himself to be a classical scholar. Justitia vertutum regina. Justice is the queen of virtues. What could be my motive? I meant to rob and gain nothing for myself? Didn't you gain great satisfaction when all of France laughed at Dubigny? Bravo!  Before I go, what will Dubigny discover in this raid? Why, the stolen goods, the jewels, the general's medals, the mirrors and paintings from the Petit Palais, everything. And the gang? Oh, they have escaped. But they are of no consequence. There were only two men. And now, one is a chape marquee, and the other, well, a man who is rather pleased with himself. And so, I, the doc, beg your indulgence, Commissioner Dubigny, for the nature of this report. As I said, it is my final case and perhaps not my best. If you wish, consign these pages to the fire. There are witnesses revealed here, both yours and mine, which, I fancy, both of us are willing to forget. Suspense! A true story presented by Autolite. Tonight's star, Mr. Charles Boyer, will return in just a moment. This is Harlow Wilcox speaking for Autolite, world's largest independent manufacturer of automotive electrical equipment. Autolite is proud to serve the greatest names in the industry. They are members of the Autolite family, as well as are the 98,000 Autolite distributors and dealers in the United States and thousands more in Canada and throughout the world. Our family also includes the nearly 30,000 men and women in 28 great Autolite plants in many foreign countries, as well as the 18,000 people who have invested a portion of their savings in Autolite. Every Autolite product is backed by constant research and precision built to the highest standards of quality and performance. So remember, from bumper to tail light, you're always right with Autolite. Now, once again, Mr. Charles Boyer. Next week, the fourth member of our first drama quartet will appear on Suspense. Sir Cedric Hardwick will star as the most infamous poisoner who ever lived, Dr. Edward William Pritchard. The program will be heard on Suspense. Suspense was transcribed and directed by Elliot Lewis. Music was written by Lucian Morrowick and conducted by Lud Glaskin. The box final case was written for Suspense by Sylvia Richards. Featured in tonight's story were Ben Wright, William John Stone, Paula Winslow, Parley Bear, Victor Rodman and Joseph Kern. Charles Boyer may be seen in the fall tour of the first drama quartet's presentation of Don Juan in Hell by George Bernard Shaw. Remember next week, Sir Cedric Hardwick in another true story which we call the Diary of Dr. Pritchard. You can buy auto-light staple batteries, auto-light electrical parts, auto-light resistor type or standard type spark plugs at your neighborhood auto-light dealers. Switch to auto-light. Good night. This is the CBS Radio Network.


Hey guys it's Nate, AKA The Foot Accountant. Welcome back to the channel. It's another promo Friday inside of Festival Football, inside of FIFA 21. Summer Stars Team 2 is what we are expecting to be here inside of FIFA today. Of course, the second installment of the Summer Stars items, it just makes sense with how the schedule is going and how this is the last week of Summer Stars. It would make sense since we've already had a Team 1 and a Team 2 for PTG and a Team 1 for Summer Stars. With this promo ending a week from today next Friday, it would make sense that for this last week, we would again have Summer Stars Team 2. Now, I feel like it's a 95% chance that we get that today. Technically, we have no loading screen and we don't know anything about a team coming out today, but that is what we are expecting. It just makes sense, right? Again, EA Sports branding all of this stuff with Team 1. You can see here at the bottom, Team 1, they showed when they posted Festival Football Summer Stars that first graphic last week and they did that same thing with PTG. So it just makes sense that there would be a Team 2 today. Again, it was not 100% confirmed, but we're expecting to see it today. This could be the last promo of FIFA 21. Let's talk about that for a second. This might be the last promo Friday of new cards that are in packs with lightning rounds and stuff like that. It really might be. If they do footies, if they do maybe some sort of summer heat, that might just be SBC based and then they re-release older cards back into packs, not necessarily having a full team of new ones in. So this is actually kind of a monumental Friday, if that's the case. The last promo Friday of FIFA 21 could be today. So I want to talk about what that's going to bring. Look at some predictions. Look at the just newly upgraded PTG cards. EA went early with these again, not two days earlier this time, just one day early. I want to talk about actually why they did this and then also talk about the market and how I expect things to be moving today on this Friday of FIFA. So first thing is first, let's take a look at a prediction for some cards that could be in packs today. I think a lot of us are really, really hoping for this guy right here. And that is Mr. Neymar Jr. I think a lot of people think he should be getting a card after we had with Charleston last week. A lot of people are saying Lucas Paqueta possibly as well could be getting a card today for Brazil, but a lot of people are hoping for Neymar to headline today's promo. Raheem Sterling Lukaku, Insignac de Paul, Luke Shaw, Renato Sanchez, a very, very popular item that could be getting a card today based off how he has played inside of the Euros, even though Portugal are done. Now Thiago Silva being a part of this prediction by Simon Design. I'll put the link to this post in the description. Since we had the Thiago Silva yesterday released with the showdown SBC, I doubt that would happen, but Pedri would be a sit card as well and Mal, or Male, however you say his name, would be a dope card as well. So again, just like we saw with team one of summer stars, a lot of potential today for some really sick items. I feel like we're not going to have a 99 rated item unless they boost Neymar to 99, but there could be some big boy names, maybe a guy like Conte, again Sterling, Neymar. Those are all players that could be in team two today, which we'll find out as of course we get to the content drop. Now again, since this is the last week of Festival Football, that also means this is the last week of the preview packs being inside of this game. Now after this week, I think it sounds like it's going to revert back to normal. We'll talk about that as it comes, but for this Friday and for this week, we are going to see the exact same situation as we saw last week with a lot of supply coming to the market and a lot of people opening these packs basically for free and then deciding if they want to buy them, right? That's how these preview packs work. But just like last Friday, what I'm expecting is a lot of supply first hour. And if you guys remember with team one last Friday, you had a lot of cards drop down really low right away. Calvin Phillips is like 220,000 coins. He went all the way up to 290 before dropping down further. You also had guys like Ray Charleston go down to about 600, sorry not 600k, about 900k and then bounce back up to almost a million coins. I traded with three of those last week myself. Laporte was down at 200 flat. He went up to 300k in that first hour during lightning rounds. So you're going to see a lot of fluctuations on the cards today. One thing I will say is watch the cheaper ones, right? Again, Laporte and Phillips last week were cards that had big fluctuations. I think Esok did as well. And those were all cards that were really cheap in that first hour. So watch out today. Last week we had a lot more saved up packs. This week I don't think you'll have as many, but you'll still have a lot of promo packs that will be open for quote unquote free before people have to choose to buy them with the preview pack method, which is going to bring some more cards to the market than it would if things were still the old way. So just watch out for that supply right away in the first couple of hours to maybe knock these prices down. We don't have big games today. Last Friday we had Euro games. We had Copa America games. I am expecting some of these cards to rebound up after a couple hours or so as we get into the evening. And as these cards get rare, I would expect some of them, the brand new ones that come out today to go up on the market a little bit. Again, Cristiano Ronaldo, his price is up a little bit, four million coins. This is one thing that I want to talk about too with the cards that are coming in packs today. Let's say a Neymar does indeed come. Last week what we had with the Cristiano Ronaldo card is that the cards below right, the 98 versions of Ronaldo took a huge drop off in price. If we take a look at the team of the season Cristiano Ronaldo, he's down at 3.3 million coins after being 4.4 last Friday when the new one dropped. He literally dropped a million coins the next couple of days and has kind of slowly dropped even continually through this week. The same thing happened with the Messi special card. So a lot of people have already started to sell off this Neymar card depending on what position and what the stats are. If a Neymar were to get a special today, then I would expect this Neymar to continue dropping off more in my opinion. But if a new Neymar does not come out today and Neymar is not in summer stars team two, you actually might see this card rebound a bit because a lot of the panic selling you've seen this week for this Neymar is because people expect him to have a promo card today. So just be careful with that. That's one thing I watch out for specifically with the Neymar card. So again, since there's going to be supply coming to the market today with preview packs and lightning rounds and stuff like that, where I would be expecting to see a lot of this SPC fodder drop down to pretty good prices as well. Last week we saw the lowest point for SPC fodder being on a Friday night Saturday morning timeframe after all the supply had come in. 84s went from like 11-12,000 coins where they are tonight all the way back down to about right here. As you can see it, they went down on Friday and Saturday to like 6-7,000 coins. Friday actually during the lightning rounds all of these 84s were like five and a half to 6,000 coins at their absolute cheapest and they have doubled in price this week now up to 12k. With the content being nonstop there in this promo, I expect this to happen again. I would 100% look to buy some 84s, 85s, 86s today if they do drop and when they drop with the supply. 84s around 6,000 coins, I think is a great price. 85s around that 9-10k range is a great price and then even 86s around the high teens like 17, 18, 19, if they get down to 17k, which they did last week, I think that's a great price for a lot of these cards as well. We're going to have more SPCs coming out this week and that's just going to bring more demand for these fodder types of cards on the market this week. So that's one thing I'd watch out for. Now let's speak about content today, right? We should have some new SPCs and objectives coming out on this game as well and since I'm going to start here, since we had a showdown SPC for the Copa America final between Argentina and Brazil, we had Anhel Correa and of course the Thiago Silva that dropped yesterday in FIFA. I'm expecting another showdown SPC today for the Euro final. So England, Italy, I would expect a showdown SPC for two players from that game today as well. That would be out for a couple of days before the final. So that's my expectation of part of the content that could be coming today. They also might drop a Summer Stars player SPC as well. You know, like we've seen the Shakiri, the Kimmich, the Patrick Schick this week, I would maybe expect another one of these to come out as well. So it could be, you know, three different SPC cards dropping today on Friday, as of course these Summer Stars from last week are all expiring today. A lot of those SPCs, again, that's kind of what we see a lot of times in the Esports is a lot of these SPCs expire on the new Friday promo. They like to reset most things and boom and have all that stuff available with the new week of the promo. So that's the SPC section is what I'm expecting there. And for the objectives section, we of course are going to be, this Goosens is going to be going away. And in my opinion, what they could put here is a Spanish, a Spain nation player because we have not had a nation player yet from Spain. And of course they're out of the tournament, but they also have that Weekend League plus objectives for this weekend requiring Spanish players. So I think that is something that could come via objective if EA would be nice and maybe give us another meta Spanish card or two, because we have not seen those nation players yet from Spain. So that's one thing I think that we are hoping for. I talked about the stuff in packs, we talked about the SPC content and the objectives. And, you know, if there's, you know, if you like opening packs or you want to take a chance for today, I'm probably going to be doing this. The 80 plus player picks, probably not a bad shout if you're, if I'm being completely honest, do a couple of these and then stack them up for today's promo team. If you would like to do that, I'm probably going to stack a set, you know, maybe have 20, 30 plus of these just to open up when the new team is dropped in packs today. Of course, give myself a shot at an Amar, maybe a Conte, maybe a Benzema if he gets in, you know, Sterling, Luke Shaw, whoever, definitely going to do a couple of those player picks and save them up for later today. So let's talk about a few other things that have happened in the last little bit in FIFA. And that is the PTG upgrades, right? We had our upgrades a day early, a 99 rated Firmino card, the Acunha card is what everybody is talking about as the, you know, arguably the most craziest card we have ever seen in FIFA ultimate team history. Look at these stats, 96 pace, 94 shooting, 97 passing, 99 dribbling, 95 defense and 97 physical. This card looks unbelievable. Now with Argentina and Brazil playing in the final of Copa America, both teams are on the brink of one more upgrade, which would move all of their cards that are PTGs. Whoever wins this Copa America final is going to get five star skills and five star weak foot. So if Argentina were to win, this card would get five star skills, five star weak foot on top of all this. And just to look through these attributes, man, so many 99s. It's unbelievable. This has the most in game stats, I believe, of any card in FIFA history in terms of that. Unbelievable the amount of juice they put on that Acunha card and how he looks. And of course, Firmino being a 99 rated item as well. Actually, if you look in concepts, I just saw this earlier tonight. If you look in concepts, this is the first card that shows up in concepts in the game because it is 99 rated. It shows up in front of Pele, in front of the 99 Ronaldo and Messi, which is crazy. But a 99 rated Firmino with the upgrades that happened earlier tonight. Now of course, my Ericsson card got upgraded as well. So that's a huge GG. My Llorente card, those are the two cards that I had in my team that were getting upgraded.  This card looks incredible. And so does the Ericsson man, eclipsing 90 pace, 85 physical, 95 pass, 95 dribble. I'm stoked to try this card out once again with the upgrade on him. So that's a huge W. By the way, I packed Modric yesterday and Esok from the Guaranteed, the Summer Stars Pack, but I got this guy from Player Pick. Absolute scenes, man. I'm stoked for that one. I got to get Rammel's done ASAP to link those guys together. Anyways, but those upgrades tonight have definitely moved some cards on the market. Now again, we started talking about this a little bit on stream. There were some price range updates last night with some of these cards, which kind of moved their prices around a bit. And now since these upgrades have come out, some of these guys are moving around again, but this Verati goes to 98 rated five star, five star with the Euro final Italy and England. These Italian cards can no longer receive any more upgrades. They have maxed out since they have won all of their games so far as a part of the euros, all of their group stage games and all the knockout games up until the final, they have already gotten their six wins. Verati, Florenzi will no longer get upgrades inside of FIFA. Those cards will not upgrade anymore, but for the English cards like Phil Foden, like Jack Grealish is an SBC and of course, like Chilwell, they have gotten their rating upgrades as high as they can possibly go. This Foden is achieved its highest rating, 98 rated, but if they win the final, they will all go to five star, five star Grealish will be five star, five star Foden and Chilwell will all be five star, five star cards. If they do end up winning the final for the euros, they will not go up to 99. They will just get that five star, five star boost. But again, the Militão card actually today is the one that's moved around the most. And right now, what you're seeing is I think people have seen how these cards have gotten their upgrades and they're selling them in. A lot of people are listing up these cards because they've seen the 96 upgrade. I think the Tiago Silva SBC with being 90 pace is hurting this card a little bit as well because that Tiago could be, you know, upgrade and also get a plus two to a 96 and kind of hurt this Militão's value because right now that the Tiago Silva SBC is 291K with Premier League links and it has similar stats to this Militão. But I think what you're seeing with a lot of these cards is people see these upgrades, they're getting towards the end. And you know, just like this person who packed Militão and never sold them first owner tradable fresh Militão that was probably packed when he was like 400,000 coins. Somebody is now selling it for 880K because they thought that when he got his final, final upgrade, which this card won't go any higher to just go five star skills, five star weak foot. I think a lot of people were saving these cards for them. I think you're going to start to see some of these PTG cards actually drop off in price. Now their cards are going to fluctuate still because there's still a lot of demand for some of these items, right? Like Acunha shot up in price tonight when his upgrade first happened. He's now kind of come back down a little bit, but these cards are still going to move around. All I'm saying is I think a lot of people that have held on to these cards and we're waiting for them to reach their highest price, you're going to see a lot of people sell and with no more upgrades coming for a lot of these items, especially guys like Verate. And you know, even, even a Firmino and a Militão, Firmino's reached 99 rated, right? Yes, he could go five star five star, but that's only a plus one on his weak foot. He's already got five star skills. So I think that does not help his case at all. I think you're going to see a lot of these cards drop off in price. I think this Vinicius is way too expensive. 5.4, 5.5 mil? How much is this Vinicius Junior right now, man? I think this card is way too expensive on this game. He's 6 mil. He was just 5.5. I think that's ridiculous, right? I know it's 97 rated. I know he's got the pace of dribbling the five star skills. But I think it's, I think a lot of these cards are too inflated because they still have that live aspect to them. And I think they are going to be dropping off in the next couple of days and especially the next couple of weeks as these competitions end. And as people kind of sell them out of their teams, because I think they're going to see their prices drop and want to take the coins on some of those cards. So all I'm saying with these PTGs is be careful with them. But it's also the end game, right? So if any of these cards are ones that you've won in your team, and you know, just don't care about if their price drops off a bunch, buy the cards you want to buy, use the cards you want to use in your team, because we're in that stage of FIFA where, eff it, just do it, buy the cards you want to use, and have fun with the cards that you want to play with. That's my opinion. So again, today on Friday, brand new team of cards coming in packs with Summer Stars Team 2. That is what is expected. Maybe a new showdown SBC for the Euro final, which we'll see on Sunday. And then of course, all of the new content dropped inside of this game with the preview packs, with the lighting grounds, and maybe some saved up player picks. So if you did enjoy this video, smash the thumbs up on it, comment down below if you have any questions, and subscribe if you are new. But it's been Nate The Foot Account, and I'll catch you guys later. Peace. Out.


Okay, okay. Hello, everyone. Hello. Hey, hi, hi, hi. Quite nice to be here, especially with the rain and stuff. So my name is Melvin. So this is my first time speaking on a PHP user group meetup. So my topic today, I guess, will be streamlining your Laval code base. Hopefully, it's simple for everyone. I only see a few hands up for Laval developers. So let's... Okay, just to introduce a bit of myself, I'm currently working as a web engineer at Tech in Asia. I have two of my colleagues here, Lester and YC, Yuan Chuan. So basically, here are my handles. You can screenshot or get it later. It will appear again later somewhere. So I've actually worked on Laval applications for about two and up to about three years already. So my first Laval application is something that I've done actually in school back in NUS. It's actually called NUS whispers. If you are not sure what NUS whispers is about, it's basically a confessions page where NMS people who actually post confessions into their website. And what we do is actually moderate these confessions and post it up to Facebook, to our Facebook page. Right now, NUS whispers has gotten pretty well, probably reaching about 18,000 lights already. And it's widely used within the NUS community for giving feedback to all the NUS administration and staff. There's a lot of sagas if you want to see. So basically, what Laval has to do with it is actually, what is powering it is actually the moderation admin where users, where we at moderators can actually accept and reject submitted confessions. Then you just automate submit to Facebook through by using the Facebook API. We also offer API for the front end to consume, which is actually currently on Angular 1.0. It's actually a school project. So right now I'm just maintaining and just keeping Laval up to date and try out new features and stuff there. After I graduated in NUS at the same year, I actually joined TechNature. And right now, I've been working on the TechNature's Laval app for quite a while. And what we've been using it is actually to handle the company database where our staff can actually manage startups, companies, investors' database where they can add and edit or insert funding rounds and stuff. And we also have recently launched jobs last year. So we use Laval to actually develop the jobs API where the front end, which is powered by React, consumes it and for applying jobs, finding jobs, sharing profiles with each other, connecting, rejecting, and all sorts of stuff. So if you can say that the Laval app in TechNature is definitely like five or six times bigger than the whisper set. So let's just talk about Laval itself. Laval is an MVC framework, like everyone knows. So this is the basic framework, basic structure of a MVC framework for Laval because there are so many different variants of MVC. So I'll just call it the Laval Edition. So what you have there is a browser going to the controller, goes to the model, the usual stuff. But some of the different things is that we have the model talking back to the controller. Usually for Laval's case, it may return back to the browser directly because it does not, for a view, for Laval, they will use something called a blade template, something like that. They may go through the view as a blade template and display it as a browser. That's assuming you're not using an API solution, base solution. If you are actually developing an API for it, you usually just send out the stuff through your controller without the need of a view as a JSON or whatever. I don't know XML if people actually use it. So the thing is that when you look at Laval documentation, you'll just see the controllers. They'll just give you a basic idea of a controller. Oh look, it looks very easy to use. They'll just show you this, show view controller and display all users with the profile and display it as a view or rather return it as a JSON if you are using an API. But in reality, the usual four of requests in Laval usually do more than just that. And then one example is like for handling a post request, you usually do something like you need to validate the post request. You need to check whether the user is actually locked in or whether the user is allowed to actually create a certain thing. Then after you are creating, you need to create, you actually do the real stuff and create the stuff in the database. Once you're done, you usually want to send notifications to other users, send email, then you may need to create more relations. Let's say you are creating a post, you may need to create categories if needed, if you want to relate to them. Or you need to log audits for data purposes. You want to know who is the one who actually edited the thing or who updated certain sets of stuff in the database. And that's a lot of things. So in reality, if you put everything together, most of the time if you ask me, I'm like, if you are new in just knowing that this is just an MV system, everyone would just say, let's just put everything together. Because you just know that, okay, you can't exactly put in the view, you can't exactly put in the controller. So most of the time, newer people like myself, like two and a half years ago, would just throw everything into the controller like this. I'm not sure the code is not actually, there's actually more than that. And this is just only the validation, but just trying to show that it can be good like this. So eventually, there's something like bloated controllers. Controllers that like 1,000, 2,000 lines long, all the time. I usually see it like when you have a, especially if you are doing in a fast moving company or an app for a fast moving company, by experience, you'll see that a lot, eventually one or one and a half years of time, you'll see your core controllers, controllers that deal with the core main resource of the, like for example, NUS confessions, NUS whispers confessions, that confession controller itself will probably be like more than a thousand lines, 3,000 lines long. So when you, when you think of this, eventually you realize that you actually need more than just a MVC to scale your application efficiently. Now, the problem is that there's two hard things in computer science. One is cash evaluation and naming things. So it's like when you want to refactor something, you need to figure out how do I name this thing? And most of the time you'll just figure out how when I'm trying to re-architect my software application, my lava application, how do I, what do I actually name all those things? How do I know how to do this? But as it turns out, we realize that how do you want to streamline and refactor your code in such a way that it works nicely and elegantly. You just realize that actually there's, lava has actually done a lot of things to like make sure that you are having one step foot right in the door. You don't really need to check like, there's a lot of things for you to help you to go and refactor application to more than just a MVC to be able to scale it. So a few things like events, middleware, observers, policies, gates, broadcasting, queue, email and notifications. They have, they have been trying to see what you actually, most of the developers really need and create a library and layer for you, everyone to like utilize it and create an application much more quickly. So I'll just talk about one of the things that are more important is actually more of like events. When, as in basically when I noticed that one of the core things like for NUS whispers, there's a moderation process of let's say a confession. We always have a state where it says, when it goes from pending to approved by a administrator and pending for rejected. So there's a case where when the time, when something happens, the proof, we will actually do something of it. For example, this time we will post to Facebook and for rejecting, we'll probably delete that confession in Facebook. For a more bigger app like Technasia, we have our jobs platform. So let's say someone applied for a job, we usually send an email to all the effect, all the job posting creators. We actually send a notification to the job posting creators as well. And we also create logs as well for the things. At the same thing for connected and skip, we also send notifications, different services like email or notifications at the same time. So when we realize that we can do that, we realize having a, we realize that you can have an event for each of the state. Most of the time you will want to do that in the sense that you can create a confession and the user. So while we will just do a create an event object and we'll just inject the, we'll say just inject the confession and the user in as well. So we'll just, in the end, we'll just refactor the code and just take out the, extract out the event itself and submit the, emit a new event call confession was approved for a sense of like annuals response in case, after approving, approving the confession. So eventually you have, you can split out each of the tasks that you need to do as its own listener. So you have like post confession of Facebook, where you can just inject the dependency inject the third party library that used, for example, this is Facebook and just submit the one. So you are like abstracting everything out and handling one dependency at a time. So even then you can just go and create a, or use the default event service provider and actually write all this down. So eventually if when you write this down, you'll probably, everyone can like have you see like what happens, what would, what did you actually do when you could do that event. So confession is approved. I will actually post the confession of Facebook. If I rejected the confession, I would delete the confession from Facebook. Now the thing is that when you are doing something like this, you are actually killing two boats, two stones, two birds with one stone. When, so for example, for us at Tech in Asia, one of the things is that when we try to send a notification, what the notification service is way over at Japan and sending one call is like eight, like eight to 16 seconds long, can be really long. So if you are doing everything in a single track, by default, Lava does everything in a single track. So you just, users can actually just wait like eight to 10 seconds just to wait for something like that to happen. So what Lava actually has is a really, really API to actually queue all this, default all these listeners to a queue task. So you can actually just set it up, create a message, connect to a messaging service right now. There's two providers that we mostly use for AWS, SQS, and Redis. For any listeners, we use Redis and for Tech in Asia, we actually use SQS. Both have their pros and cons, but SQS has a certain limit like, it's only restricted by a small packet size and you only can defer events like up to 15 minutes. But at the same time, when it comes to cost, probably SQS is cheaper because you only pay for what you send. Already you need to maintain and manage the server. So there's pros and cons, depends on what you need to see. So after that, you can actually have your PHP servers set up a supervisor instance, then have it listen to all these jobs that are sent from these providers. In a sense that you can have, you can have different instances, different instances to listen to this job. So it's a very scalable solution. If let's say you have like a few thousand over jobs being that need to be processed and you can split the workload out to different instances when you are in your production environment. So how do you actually convert that into a Qt listener? All you need to do is actually just add a trade in the event itself. So what this one does is that you will actually serialize the conversion and the user models such that if let's say the user of conversion is deleted, you will get it from the database again and when it finds it, it's like not found in the database again, you will just terminate gracefully. So in the sense that actually you are preventing race conditions from this. Then you actually add a implementation Q on the listeners in a sense that once you are just Q this listener into a Q this as a job and like this. In the sense that you can for event listeners, if you don't want to use the event pattern, you can actually dispatch this as well using the dispatch function. So if you actually want to go even one layer further for sending notifications for user, level 5.3 actually has a notification system layer API working for it. So you can actually use it to go and further abstract your notifications to send to different messaging parties like Slack or email or notification services, other notification services. There's a lot of custom notifications channels that they are available and we ourselves actually wrote a few like mandrel and actually get stream Iowl that use it for sending emails and notifications to. So what you just need to do is actually create notification class where you just create a same thing as a job application and create a function for each of these delivery services. So for email, I'll just create a new message. What you're trying to do is actually trying to interface with the custom notification channel to proxy what things you want to send to that to the notifiable which is probably the user. So you can actually eventually add this on for more delivery services in the future. Then for what you do, you can just change a bit of a code for a listener and have it to send the notification like this. So for example, you can actually send this as a queue task as well by using shoot queue and after that, send the notifications to all the notifiable. For this for example, for this is actually the function to get all the users to be notified and then send it as a notification. So testing is actually much easier now in the sense that you can actually create a controller test case that you only need to care what is the output of the response rather than trying to figure out whether everything else is like. You send the notification whether notification parameter is correct. You're actually doing things like that. All you need to do is just you can just mock the events to just expect events to go and say that expecting a confession was created event to happen when this API call was made. So you can just put a post API confessions content and check whether the status is okay or you can actually set more things like whether the payload is returning a correct ID or anything like stuff like that. Testing business is also easier now. You just need to mock the service class that you need when setting up. So for example, this time we just set up the Facebook mock and when we are handling the case, we can just create like confession. This is like a model factory that Lava provides. So if you define the model factory like a model should have this kind of fake data, then you'll create this confession and then you can actually check whether this thing will receive a post from this class and handle the create a listener to handle this. Obviously, this will fail because it should technically it should receive post. And we also can test notifications now because we can just mock the notifications. We can just fake them, then run the usual case and check whether the notification is actually sent to the user or with the correct notification class. There's also a third argument where you actually can create a closure to check whether all the data that is sent to the notification is actually what you actually expect. So tracing back all the steps, what we do step by step is that first we actually write events for each state, trigger the event at a listener and write each task as actually event listener, all the small things one part by part and attach this listeners to the event service provider. The fifth and sixth step is like quite optional but you can do it if you need to if that's like you have a lot of things like a lot of listeners that you that take a long time to process and stuff. So fifth is to kill the listeners and notifications at additional level if you will have a lot of like notification stuff to send. So here's a little cheat sheet that we do for all the crazy things that Lava actually provides already. So when you want to filter modify request payloads and you want to reach total there's middleware for that. If you want to control who have performed action or something like you want to know who can actually access like create a user or delete a user, where do you want to have all this logic to define all this you can actually create policies for this and use gates to actually control them a written error like a forbidden error for this and as soon as now we can select send you want to send to select or mail on other notifications you can use their notifications. If you want to validate your request you can actually inject a custom form request that you do into your controller. If you want to subscribe to events and listen to them like like what you do for sockets you can do there's also broadcasting and that's for this one this is actually our third party service that a library which we use a technician called Factory where we want to control how the model should like present on its response based on different little probably like based on different policies that we have. So maybe if it's an admin he probably see like he can see like certain things and certain hidden attributes and what's not. So so final tip for when working on a new feature what you do is like I will do is basically stare at the library logs for see is anything suitable or if not worst case in our research other third party libraries there's a library news where they showcase actually library packages or there's also a curated list in github that I was like I think has a lot of stars where we can see awesome level where has a lot of data where you can see a lot of libraries and code bases to where and like study and learn about them and stuff like that. So some of this code available is the real working code it's actually available at annual response github repository not all the stuff is new actually so you'll still see that bloater controller you see over there still over there so thank you that's probably all from me any questions any questions yeah um how do you just curious with your production experience with library right yeah so how do you track model changes and how do you track app usage do you use any third party libraries model changes within the library itself uh within library itself right there's a few ways for doing it uh one way to do it is actually something called model observers uh where you actually create a class that handles and even uh whether the guy is created updated or something like that but if you want to further abstract a layer of this you probably want to move uh add another layer up there and handle and observe from there at this day um what there's something called a l5 repository so you actually abstract the model into a repository repository itself and when you create uh when you create something you you send an event like the sound event code on the next one then you go and listen to that event all right so any so you impact an event that is emitted when any model changes are correct correct and then once that happens you deal with it by by persisting it a little bit yes you can do that and you can do it as a custom job so let's say i want to send a log to a log another log to audit log right let's say i change this model the database i can dispatch it as a event listener and as a cute event so the user does not need to wait for the load for that so what about application usage itself whether the model changes this person has logged in this person has uh has visited this route um for this one we actually track uh for this case it can be done on on the application level and actually on the server level what we done recently is more on the server level so we actually check the nginx logs to see what the user has done or if you actually want to have more detail like application details on like what what you uh what you want to know like who what user is using this api and everything you could actually quite write a dominatable middleware where you can actually just lock down all the things that all the things that you want to need on yet at the end personally what i work what i use is i use i use this tracker this laura stats tracker yeah available on github uh it's it's decent it's decent but i'm just wondering whether whether you've got a better solution other than hand coding in yeah tracking the all is that using this application thing is that you are adding the load to your user so your response time may be slower yeah okay thank you thank you


Good morning, the ten of you. Thank you for waking up earlier. We are going to talk here about the two Google Contests. Debian is participating. Maybe you will have known the Google Summary of Code. Silvestre, I'm going to talk about the Google Summary of Code. I am going to talk first about the Google Coding. That is a contest that Debian was participating this Christmas. It was a bit different to the Google Summary of Code, in the sense that we have a high school student or secondary student. Pretty much it was between 13 and 18 years old.  We watched. I found that amazing. The contest was a whole version of something else that Google tried one or two years ago, in case you know it. Besides the name, the contest was about doing a lot of more things that use code. Most of the Debian tasks, as you will see later, were related to Quay, documentation, translation, and so on. It was very, very, very small. It was only 20 mentoring organizations. And it was also lasting a lot of less time than the Google Summary of Code. It was only seven weeks. So basically how it worked. It was very different to the Google Summary of Code. Basically all the mentoring organizations create a list with all the tasks that the students called do. The students were claiming the task, reading the instruction, not always. They were delivering the result of their job. Then the mentors of every project were looking at what the students did. In some cases, the work was perfect. That's done. In other cases, the students need a bit more of time for completing the task. And in other cases, the student was unable to do the task. So basically in most of the cases, I have to say that in Debian, the students were unable to do the task. They were very underestimating the job. But when the students managed to do the task, the quality of their job was very, very good. For example, you can see that the tasks in Debian were very, very simple, except in one case. That was the fix at the piggyback. Actually, a student did that. We end with a lot of man-page, a couple of query or law that's made into the archive. Serial translation. Most of the tasks, if you think about that, is what a contributor can do in one or two hours. But for most of the students, it usually took one afternoon or maybe two. If you are curious, when the project ended, I blocked and I put all the tasks that have been done. So what the students got? Basically, most of the students were doing that because the t-shirt, when a student does a t-shirt, they get one from Google. That for the students is to be very cool. And when they did three tasks, they got some kind of check of $100. Also, some students got to know how to start contributing to the difference Debian, no, free software projects. In our case, Debian. What Debian got? Well, we got about 30 students that managed to complete at least one task. And in the end, we got 39 tasks. The list is on the link I gave previously. Those of the 30 students, two students are still contributing to Debian. One of them is very, very active to the point that I started sponsoring him and he had to look for somebody else because I didn't have time for him. He was like every day one package. He's maintaining right now 13 packages. So basically, he has been adopting a package every two months. Sorry. Every month he has been adopting two packages. Also, there is something that we told in Debian from time to time that is having some kind of mentoring scheme. And some people mentioned having a small task so contributors can start helping. In this case, we tried that scheme. But the results were good. But I don't know if they are applicable to all Debian because we have very, very little number of mentors. So after telling all this, how you can help? Well, we really need mentors for the next edition. This year, we only were active like four or five people. And we have a lot of students. If you don't have tasks and mentors in the first week, students go to another project and they never come back. The involvement is very, very low. If you compare, for example, with the Google Summary of Code that you need to stay all the summer, basically, if you have one week and can have two or three tasks, it's quite fine. We also need people with administering the project side because sometimes a mentor disappear, or a student has a problem, and some of the other is not a mentor can help him or help her. Also, the most important thing is that students don't have a lot of patience. Sometimes they have a problem, and they have help now. Maybe making them to wait, I don't know, one day is fine. But when they have to wait two days, they can move to something else. What happened with small kids? OK, this was everything about the Google coding. If this year is held again, I am expecting that. It will be probably starting around November and it will end in the fifth week of January. So when you see the announcement in the end, I hope you will join. Thank you. Now, Silvester and Arthur are going to talk about the Google Summary of Code. Good morning, everyone. So this has been the sixth year we've been participating in the Google Summary of Code. And every year, bring something new. So if you've already been to this talk this year or this year before, some of it is going to be the same. Some of it is going to be different. So I'm going to remind you, still, some of the goals of the program. The idea is to get more open source code created and released. The goal of Google is to inspire young developers to begin participating in open source, mostly. Also, we also get students that are already involved in various open source programs. And from the point of view of the open source project, it's a way to identify and bring in new developers. And for the students, it's a way mostly for many students to be able to do something that is remotely related to what they're studying. The idea is to flip bits, not burgers. It's also something very interesting because it gives students the first exposure to real-world software development, with many things that are specific to the open source world. But that also exists in the general development world, such as distributed development, software late sensing, and how to properly write on a mailing list. So Sylvester is going to explain to you how the program actually works. So basically, Google, they've got a lot of money. So they don't know what to do with it. So they are going to share some of them with us. Through the Google, some have got projects. So basically, Google is funding some project like us. And so they are selecting the organization. Basically, you will see the schedule after that. But they are selecting the organization in doing math. And after that, the organization, they have to start to propose some project and select and ask some new mentor to come in the team. So Google is going to fund all the students and the mentors. So every student is getting $5,000 US. And each mentor 500. The mentor, it depends on the organization, is keeping the money or living into the organization. So here is some figure about this year, Google Summer of Code. So as you can see, more students than last year have been funded. Last year, it was something like 1,000 students. And they also increased the number of organizations. So now we have 1,115 students for 175 organizations, which is something like 30% more organizations than last year. A lot of students submitted a proposal. So as you can see, about only 20% of the projects are accepted. I'm not taking into account the duplicate proposal. But still, it's a lot of proposals. And as you can see, pretty much a few mentors are managing two projects. And the budget is quite important, $7.2 million. About us. So this year, we had nine students. They all passed midterm. We had 30 proposals submitted, which is normal for Debian, which is not something which is different from the last year. We have also 30, usually Debian developers who are registered on the interface. So that means that many people in Debian are interested by that, or at least looking at the project and so on. And we had only 20 subjects suggested on the Wiki. So I hope next year we'll be able to put more subjects and prepare things before, because it has been a bit hard to get all the subjects in the right time and in the right condition for the Google Summer of Code. So right now, I'm going to present to you the various projects which have been selected and managed during these few months. So the first one is managed by Wookie, who is a mentor of this one. And the student is Gustavo Prado Alquim. Oh, right on time. Gustavo is designing a modern automatic packages built system for the QAE, a multi-arch area. And we won't go into the detail. If you want more information as Wookie or the student, it will give you all the information. So the two next ones are mentored by Michael Vogt. It is about APT and DPKG. So the first one, the second one, the Delta APT native packaging is to improve the user experience of APT. And the second is changing the ordering of the Lib APT for unpackaging and configuration and so on. So the fourth is mentored by Steve Lagazek about DPKG declarative diversion. So this one is to replace the DPKG divert command with a new control and the declarative system. So I won't go into the detail of this one. If you want to have more information about the one mentor by Matt and Stefano of the Natan Handler Project, you will have a look to the video. Stefano made a presentation of 45 minutes on this. So you will find everything you need. But basically, it is to manage the patches coming from derivative and all the program related to derivative distribution. About the next one. It is tomorrow here at 3 o'clock in the afternoon. It is mentored by Tom who is in the room and myself and the student is the guy who is in charge of the camera over there. So it is basically just a few words. It's basically when you are downloading the Java virtual machine, it's a huge package with everything you don't need inside. So basically, you split it into various modules and you just take whatever you need. So it is a very interesting project, but obviously because I'm one of the mentors. The next project is a Python build for Python extension packaging. So it is mentored by Pyot who is in this room. I won't say his family name to spell it badly. The student, it's Metsukan Kurt. It's about creating a tool to build Python extension for all Python versions supported by Debian. And the last one, we are going also to have a presentation today at 2 o'clock in the wrong room managed by Andrea Steele and developed by Sukir Singh. Sorry about your name, he's also in the room. It's about how to measure the activity into a Debian team. And the last one is a mentor by Stefan Muller. And the student is Rudi Godoy. And the goal of this project is to enable developers to easily use computers cluster, such as a Calypso OpenStack. So now, Arthur is going to tell you more about how to participate to the Google Sumof Code. This year, we would like to highlight how to participate to the project, what we are expecting, and how we are expecting things to come and what we need from you if you want to become a Google Sumof Code mentor. It says, but we don't have to speak louder. So how to participate? Because we only admins, and we're not doing most of the work here, doing the most of the work. Where you can be a student or a developer. So when I did this talk at 4 o'clock, I usually talk a lot about what's on the floor. Do you hear me? Yes. So at 4 o'clock, I talk a lot about what students are expected to do, which is very cool, because usually, the room is completely packed with students for some reason. But we are at DevConf, and most of you are developers. And we need you to help us mentor students. And you have many questions, and we have many things that we'd like to tell you about it. So the question I get the most often is, what exactly is a good GSOC project anyway?  We have several criterias to accept projects and to see what projects is really good for us. The one that the first test is, try to replace Debian by Fedora in the proposal. Does it still make sense? If it still makes sense, probably it's not a project that is relevant to Debian in particular. And this is a test where many projects proposed by students fail, because they send the exact same proposal to every single Linux distribution they hear about. We're here to do projects that benefit Debian, that exploit the particularities of Debian, that work on the very specific infrastructure of Debian. So we don't really want to do GSOC projects, whereas the real focus is not on Debian. The second most important thing is the time scope. Is a project going to fit in two months? It shouldn't be too short. It shouldn't be too long. A summer is supposedly three months, but you have to take into account that the student is going to take three weeks to figure out where everything is and be able to ramp up to a development speed where it can actually get things down. So that takes a few weeks off time. And then at the end, there's all kind of frapping up things and preparing a release, hopefully. And that also takes our time from the summer. So you have these two months in the middle of the summer where you need to get everything done and ready. And at the end, we want to see something released within Debian. So that's the time scope. The other focus is Debian focus. Whose work does a student's project replace? Many times, we have packaging projects that usually fail because it's replacing the work of one single DD, one is a DD. And some other time, it's subjects that really are not really relevant to Debian. It's more upstream work. When the work that is replaced by the student is supposed to be done by upstream, then it shouldn't be our job either. So that's also the question of broad interest. We have this subject. How many DDs are enthusiastic about this project? Is this some kind of thing that one person is interested in? Is it something that only one person actually understands within Debian? Then it might not be something that is very good for this project. First, because of the bus factor. And second, because we want all the DDs to be able to interact with the students, the work, the release product. And we want it to be used broadly. The one interaction, as I just said, the student in the course of his project has to be able and has to have the need to actually interact with as wide as possible spectrum of developers within Debian. If it's a project that is only concentrated within one single team, the student will never really get to see what the social aspect of Debian is. Having to interact with other developers that we don't necessarily work every day with, having to talk with people that we don't know, working with on different subjects, and having to get the help. This is something that we think is very specific to Debian and something that we want to be able to have in a project. On the other hand, these are all restriction projects. And something that you have to keep in mind is that there are 175 projects. When the list of projects get published, we get a giant, there are a group of students going to this giant list of projects. And they go to everyone and click on the ideas list. And so there are literally hundreds of different projects to choose from. And these are not students that are necessarily captive to Debian. So it's a competition. If we want to get students, we have to propose something that they have to be enthusiastic about. The kind of projects that students find exciting are projects that have wide interests within the project. It's something that, in the end, creates a product that many people will use within the project and outside the project. It's a project that creates skills that they can reuse somewhere else. If it's a project that is about fixing one particular aspect of one particular sub-module of one particular software within a project, and this is something really tedious that no one cares about and that uses an obscure language, it's probably something that is not going to be interesting to the student. Even though it might be very important for the project to get down, it's not something that you're going to attract students with. And finally, the work of the sum of code is it's an interaction between the student and the mentor. The mentor might come with the idea. The student might come with the idea. But most often, because the mentor is the person with the most experience within the project, he often has a huge set of requirements. He has a very firm idea of how it should be done. And we should always leave room for design for the student. It's his project, and we want him to be able to feel a sense of freedom within the project, being able to interact with multiple people, being able to propose ideas, propose ways to do things. And that is something, I think, that creates very exciting projects. And we really need to work hard to attract all of the students. So for next year, it starts now, really. We need to have detailed projects with some objective posted to the Wiki. We have to start now, because when the deadline comes and we have three days to come up with hundreds, well, at least a few dozens project ideas, it's very hard to come up with these ideas on the spot. And all around the year, you're doing things within Debian. And you come up with things that you want to do, but you don't have time to do it. Or it's kind of an excursion from what you're currently doing. And maybe it requires something that you don't really know. And maybe some student really knows about it. This really happens. So during the year, keep in mind that during the summer, there are stuff that can get done. And so not shut down what you think you'd like to do, but you don't have time to do. Or something that you're passionate about and that you'd like to have a student to interact with and do with you. You really need to start thinking about this now, writing them down. Something that we think about every year is that the Google Sumof Code doesn't really enforce that students, selected students, have to be complete newcomers to the projects. They can be existing developers. And many projects actually use Google Sumof Code as a way to find their current developers. We at Debian have the position that we accept both, but we would prefer to have newcomers, of course. We want new developers. And if we have both newcomers and existing developers for the same project, we, of course, have higher requirements for Debian developers because they have already an existing set of skills of contacts within Debian. So the schedule, as I said, organization applications start in March. That's still in quite a while. And the student application starts during the end of March. And within a few weeks, we have to decide these students are going to talk with every single organization. They're going to look at all our projects, ideas, lists, and choose some Mac applications, usually just a few. And at the end of April, we are going to have the list of students that we're going to select. Sanjay Jisok goes through the summer with an evaluation at the midterm, which is mid-July, which is just right before. And a final evaluation at the end of August. So really for next year, think about things to propose. The larger the list of ideas we have, the larger the list of exciting ideas we have, the statistically larger proportion of students we can attract to Debian and possibly keep as Debian developer for the future. Thank you. So we are going to accept questions, or if you actually have a project ideas right now, we'd love to hear it. So I think one question that comes up is, maybe can you explain a little bit about how many projects Google is likely to accept and a little bit about the process of how to be successful in proposing projects for Debian? Do you mean from the point of view of the organizations or from the point of view of the students? So there are two applying processes within the Google Summer of God. First, the organization has to be selected. And last year, 175 organizations have been selected. And we usually get in the range of few hundreds, I think, organizations applying. Most of the big organizations like us get selected every year as long as we don't do anything stupid, which has happened even for high-profile organizations. Google is a set of critters for acceptance. The first one is there has to be room, of course. They have a defined budget. So every year, they have different set of projects that they accept and that some smaller medium-profile projects get rotated. And they're all kind of different reasons why you might get selected or not. Maybe Sylvester can tell us something about us. Sorry. Tell us more about it, because we as Debian haven't really thought to get selected because we are kind of high-profile. But for smaller organizations? So you mean basically to explain why he's saying that. I'm also an admin for another software, which is Sylab. So you are meaning that Sylab is not a major software? Basically, it's pretty easy. In fact, the perception of Sylab outside of the scientific world might be low. But it's a bit software with a lot of references. It's three million lines of code, so it hasn't been very hard. Just have to make sure that Google knows that you are a major project in the field you are working. And after that, to answer one of your questions, the number of slots that we are getting is basically an algorithm with a number of mentor we've got and the number of application we've got. It's basically an algorithm. But there is a funny part in the Google Summary of Code where you request a number of slots. So basically, last year, we think we request something like eight, and we add eight, something more or less. And there is a funny part where you can exchange slots with other projects. So as Sylab, I gave some slots to other projects in the Debian community, which we are not Debian, but you can exchange them. And you can request for more, and you can start to send email crying that, oh, I want more slots, and so on. And usually, it is working. So they are very relaxed with that. So from the point of view of the students, and the thing is, it takes a lot of effort to make a good application. And most of the students can get one, two, maximum three applications that have quality that is good enough to get selected. I participated once the first time in the Google Summary of Code the year before I began admin. I made two applications, one for Debian and one for Tor. I got selected at both, and I chose to go to Debian. But it really took a lot of time to write the applications. The applications itself was in the range of, I think it was like 4,000 words. It was a real outline with schedules and everything. So most students will do about an average of two applications. We have some students that try to do spam applications. Like I said, if you can replace Debian with Federa, and it still makes sense, then we're not interested. So some students would write this one application and send it to 10 different organizations. That usually doesn't work. Pretty much for students interested in participating in Google Summary of Code in Debian next year, around January, beginning of March, they should start looking how Debian works. So in the beginning of March, when there is already the fifth projects, they can select, they can get in contact with the mentor, and they can start working. Because how many, two, three weeks they have for submitting the proposal is very little time. Any other question? Okay, thank you very much everybody for coming.


This trustee August is hotter than ever at Appalachian Wireless, as they are slashing all normal contract pricing on all smartphones by 50% when you sign up for service. Better service, bigger saving, serving you for the last 25 years at Appalachian Wireless. The new University of Pineville Kentucky College of Optometry has reshaped the landscape along Hambly Boulevard and brought a new group of students to town. But officials at the school say its true impact is statewide. In 2011, Kentucky passed the Better Access to Quality Eye Care Act, allowing optometrists to perform some minor surgeries and treatments that were previously reserved for ophthalmologists. Part of the reason why Kentucky, the legislature, was so wise in passing that scope of practice we have is because we have unserved and underserved areas. The legislature looked at us and said, we need to serve the amount of blindness that's in this area. The new optometry school in Pikeville is the only one in the state and one of only two schools in the nation to integrate training for the expanded services that optometrists can now offer in Kentucky. They take 65 hours just in ophthalmic surgery procedures. So they have to take a lot more. They'll be seeing patients when they go out there. They're clinical hours. So just like every doctor in Kentucky had to go back and retake that training, our students will take that at even a more depth level. The hope is that the majority of new optometrists graduating from the Kentucky College of Optometry will stay and practice in Kentucky where they'll have more extensive training than many seasoned optometrists who are still working to learn the new procedures. The big thing here is how experienced they'll be when they're out. Many of the other states have students who are going to watch procedures that are being done. Our students will be doing them again under the very careful supervision of their faculty but they'll be doing the procedures. In four years, the inaugural class of the Kentucky College of Optometry will graduate, ironically in the year 2020. Reporting in Pikeville for EKB News, I'm Shannon Deskins.


I'm here today with Esalt Ward, the co-founder of a charity called Food Cloud, which is based here in Ireland. Esalt, what is food cloud? We work with businesses across the food supply chain and where there is good, edible surplus food, we will do our best to redistribute that out to charities.  Food waste is a massive global problem that we're trying to deal with and this food can be lost or wasted across the global food supply chain so it can happen at a farm level, it can happen through manufacturing, distribution, retail and also in our home. So at every stage of food production we lose some of it and it's a big loss and it hurts the people mostly who can ill afford it. And it hurts our planet. All of this food that's going to waste results in global greenhouse gas emissions. So a lot of this food ends up being dumped. When it's dumped it rots down and releases methane gas which does just awful damage to the atmosphere. Yes, methane is a particularly potent greenhouse gas emission so really our objective must be that food that is meant for the human food supply chain, we should keep it in that supply chain. What can we do as normal householders to alleviate this issue? Well it is one problem that everybody can do something to solve because everybody eats and that means that we can all make an effort to reduce our own food waste. There are going to be many more people on this planet by 2050 and we need to find the food to feed them but we also need to do that in a way that looks after our planet. It's clear that with food going to waste if we reduce this and if we all make an effort to reduce it across the food supply chain that we have a much better chance of feeding people and reducing hunger whilst also fighting climate change.