A warm welcome to the 27th session of the third module of signals and systems. We have now embarked upon a very different kind of signal and system paradigm where we use discrete time systems to do what you would like in other continuous time system to do. And I think it is appropriate that we give some concrete example. Let us know that. Now, let us take the example of wanting to process a speech signal. Now, of course, you will recall we have talked about this before. Speech is typically band limited to about 4 kilohertz. So, if we look at the terms of the spectrum or the Fourier transform and if I am talking about the cycles per second frequency which I am denoting by f, we are talking about an occupancy from 0 to 4000 and minus 4000 to 0 on the other side, on the negative side. Now, we have been talking about sampling and reconstruction. So, we can of course, put down a requirement on sampling. We need to sample the speech signal at greater than 2 into 4000 or 8000 when I say hertz here. So, we have the right samples per time per unit time. So, for example, remember you know we wanted a margin. So, let us choose a sampling rate of say 10 kilohertz, whereupon what we expect is that if we have the speech spectrum, let us take what we call a prototype speech spectrum or let us just draw some spectrum for the speech signal. So, you know instead of keeping on writing 4000, I will divide f by 1000. So, I will write 4 and minus 4 here and have some spectrum. I will just show it by something like this. Now, you know I must caution you that when we make diagrams like this, it is essentially for conceptual understand. We must not take the shape of the spectrum too seriously. You see it is just to explain what is going on and in fact, when I say a prototype spectrum, I am talking about simple shapes, where I can ensure that every point in the relevant part of the spectrum has a different magnitude and I do not bother about the phase. Anyway, coming back to this, if we sample this, we get a spectrum that looks like this. I compressed the frequency axis a little bit and so on. This is the original spectrum here and these are the aliases. Now, what are we doing when we do discrete time processing? We are not in a hurry to reconstruct and that is the whole theory we are now going to develop. We are not going to be in a hurry to reconstruct. We would like to do something to these samples inherently. So, I have this spectrum of the sample signal, I have a stream of samples coming. I operate a discrete system on them. Now, let me recall how I understood discrete systems. How do I describe a discrete system? Let us write that down. The discrete system takes the sample signal as input and produces a concurrent output train. What is the input sequence here? The sequence of speed samples. It produces an output sequence. And this would again be a sequence of desired speed samples or processed speed samples. And having generated these processed speed samples, you can now subject it to a digital to analog converter. What is a digital to analog converter? It is essentially a reconstructor. Now, that reconstructor of course needs to have a few analog components which we have not discussed in detail. That is also true of the digitizer. So, you have these analog samples which have come from speech. How could they have come? For example, you could have been recording the speech. Today, of course, we know about digital recording media. That is not a problem.  And then you are essentially using a device which automatically converts it first into a train of samples and then each sample generates a stream of bits. Now, you know, since we do not assume a knowledge of electronic systems for this course, I am not going into the electronic circuit here which could do analog digital conversion or digital to analog conversion. But for those of you who are interested and who have a background in electronics on electronic circuits, those of you who have a hobby are interested are strongly encouraged to go and look up these terms. Analog digital conversion in a book on digital electronics or in a book on electronic systems. They are not difficult to obtain. Look up analog digital conversion and digital to analog conversion. What I will do right now is just to give you a quick feel of the idea behind analog digital conversion. So, you know, there are different kinds of analog digital converters. One of them is called a successive approximation converter. So, I will just give you the principle of it. You know, how you go from the continuous time sample that you had that is the analog value to the corresponding stream of bits which represents it in the digital memory. Let us see you have an analog sample which has come. And let us assume that you have a device which can make an analog comparison. On the other side, we have one memory or one discrete time stream of bits. We convert this into an analog value by using a system of resistors and voltage sources. What is called a voltage combiner and that gives you an approximated analog value. These are the two inputs to the analog comparator. The analog comparator generates a difference or it says more or less generates a binary output more or less which then tunes the discrete stream of bits. So, you know, let me explain what are we really doing here? For example, suppose this discrete stream of bits had 8 bits in it. You know, I think many of you would understand what I call a binary representation of a number. So, for example, in a binary representation of a number, you give places each of which holds either 1 or 0. Just as when we write a number in the decimal system, we give places and in each place we write one of the digits from 0 to 9. We, of course, also have what is called the fraction point or decimal point and that concept would be there in any representation, binary representation or decimal representation. And the idea is you look at the most significant place. You know, let me take an example here. So, what we are saying is, for example, suppose your number is 14 or 14, let us say little, you know, let us put a fractional part there as well. So, let us say 14.5. So, you can write this down in binary. In binary it will be written as 2 raised to the 3, that is 8 plus 2 raised to the 2, that is 4, 8 and 4 makes 12 plus 2 raised to the 1, that is 14 for you and then you have 2 raised to the minus 1 plus half. Essentially, you have written it to the base 2. Now, how would you write this actually in terms of 1s and 0s? You would write places which denote powers of 2 with a binary point or fractional point. This point would correspond, for example, to 2 raised to the power minus 1. This is 2 raised to the 0, 2 raised to the 1, 2 raised to the 2 and you have 2 raised to the 3 here. And you can now fill in the values. In each place, you need to fill either 1 or 0. That is easy to do. So, all that you need to do is to put down, let me do that for you. Put down a 1 here because there is a 2 raised to the 3, put down a 1 here, put down a 1 here but there is no 2 raised to 0. So, you put a 0 there and you put a 1 here. Then, of course, you can put 0 subsequently. This is the binary representation. Now, this is what is called the most significant bit and this is called the least significant of the bits. By the way, bit means binary digit or the number filled in the binary place. So, the philosophy is you start by questioning what is the most significant bit? Is it a 1 or a 0? Now, if it is a 1, the number has to be more than 2 raised to the 3. So, you put down a 2 raised to the power of 3, that is 8 and compare it against the number. If you find that the number is more, then you should retain, retain 1 there. In contrast, suppose for example, we had the number 7 and you made 2 raised to the power of 3 place equal to 1. You would get the number 8 on making it 1 which is more. So, you know the number actually is less. So, if you find that is what I meant you know in the previous drawing when I said more or less that is what I was talking about this thing you know this more or less. If you find the analog sample is more, then you keep a 1 in that place and if you find the analog sample is less, then you make it 0. And you keep doing this bit by bit starting from the most significant bit and moving towards the least significant bit. This is one essential idea that can be used for analog digital conversion. I just gave you this idea although I have not shown the full detailed circuit, if some of you are interested you might want to look up how all these things are done. But no, we should have a conceptual idea and we are talking about all this analog digital conversion, we must have some concrete idea what is happening. We will see more about this system in the next session. Thank you.


Okay, hi everybody. Thank you for joining today's Jenkins Advocacy and Outreach SIG meeting today is September 21st. On the agenda, I have a quick update for GSOC, October FAST, top contributor project update and a quick thing on FOSTA. Anything else that we should add? Okay. All right. So for GSOC update, I have that GSOC 2023 has come to an end with two extended projects to come to an end in the next two weeks. We also had the final project demos via the Jenkins online meetup on September 14th. And I thought that went really well. I've put the recording there as well as on the meetup page. It seems like I think the Jenkins online meetup is also another way for prospect contributors to learn about what we do with GSOC. Because I think when we were doing the online meetup, I saw quite a few interests and then there's people that, you know, that's looking at the recording as well. So that helps. So many thanks to our org admins. Many thanks to our mentors couldn't have done it without our mentors and their dedication and hard work, of course. And congratulations to the all four GSOC contributors for passing their program so far. So the last two, the jury's still out. Ah, okay. So it looks promising. Okay. Good. Thank you. Thank you for fixing that. Just don't want to disclose all the details yet and then it's not done yet. Okay. Looks good. Yeah. Yeah, we got two more weeks to go. So I plan to start a post-mortem document so that we can make notes on what we need to improve for the next year's program. Anything else that you'd like to add, John Mark or Bruno? I don't have many. It's been an interesting year, fruitful. And it comes to a slow and nice end. And I think we can breathe for a couple of weeks and get ready for the next edition. Yeah. How about you Bruno? Nothing more to add. In fact, thanks for asking. I think it will be interesting to see on the project that you mentored what, how much activity will be on October 5th. I don't know. We'll see. I'll measure it. So great segue into October Fast, John Mark. I put here that we are planning to, well, we will be joining the October Fast and it's going to be their 10th year anniversary. I've listed your blog post there. So registration starts on September 26th to October 31st. And October Fast begins in four days. I plan to send out a tweet. To re, you know, just to re-emphasize that, hey, we're starting soon. What day would that be? Because it's four days. Is that include the weekends, John Mark? I don't understand begins in four days. Yeah. From what date? I looked on their website. Yeah, and I think it's four days for registration. And even there will not quite complete five days yet. Five days. Okay. Yesterday when I put the agenda together, it also says five days. Certain amount of hours, but okay, I will fix that on our. So I think it's the time to start registration where 21st was five makes 26. So I think it's days until registration. So on the 26th, this is where you can. Okay. Get the people excited to register. Okay. I'll set for a tweet to go out then. Any color you like to add here, John Mark? Well, there, there, there's some issues that were, that were marked by some maintainers for good October Fast issues or Santa issues. And some of the people are already taking these off these issues off before October Fast is really open. So there's a lot of interest in enthusiasm also in the in the intro parts there. So, so not impatience, but a lot of excitement. Yeah, that's a good thing. It's not directly linked to that, but I have a comment and a question. You told a few minutes ago that you were about to write a tweet about that. I even don't know if that is still called a tweet or a next or something, whatever. And some people say Twitter is about to die for the third or fourth time soon because Mr. Merck wants everybody to pay for that. So do we have a backup plan? Do we plan on moving or having a backup account on mastodon or blue sky or the next cool kid on the block? That's a, that's an excellent question. This is, we should listen to what people have to say on the existing channels. Yeah, you're making a great point Bruno. Yeah. So could I suggest that you start that thread, put that question in the discourse or an or a getter and then be able to start thinking. Yeah. And if needed, I have four blue sky invites just in case. Okay. So that means that X will be gone. Right. I mean, Twitter is now X so X will be gone or have to be paid for. Maybe. We don't know. We don't know because some people. I'm not going to say more than that, but people thinking about the future of Twitter acts. Come up with some ideas just to generate talk in clicks and whatever. But if it's, if people have to pay for Twitter. But here there's so many, so many. There's so many journalists politicians on on that. Now in other circles, telegram is, is a very popular. I don't know. It's a good question to see. Maybe worth trying a poll. Yeah. Okay. We'll talk about that. Out in the public. So. Moving on. Okay. So top contributor project. Where we are is that. The stories are slowly coming in. We currently have a few in the backlog to keep Kevin very busy. So Kevin has been writing up the stories. Kev. Thank you so much, Kevin. And then what I, because when I put this together, I did it last night and so what I had put on here is that what we wanted to do was create a web page on Jenkins.io. That's dedicated to the contributors spotlight project to where we highlight all our contributors or heavy contributors. And we were kind of stuck and we need somebody with the expertise to help us create this page. Okay. So this morning, Kevin mentioned that Chris Stern has signed up to do that. But we, but there, we do have a short window that we want to get this page up. So I'm hoping that, you know, we can figure out whether Chris can commit to that window. What do you think, Kevin? Chris said he was willing to help out and step up and work with us to create the page and everything. So we're in a much better spot than we were yesterday for sure. But yeah, it's just a matter of, yeah, I sent him the, the bigger thread ideas of what we're looking to do, some kind of background for it. So I'm hoping that we can figure out what we're looking for. Okay. Okay, great, great. So if we need help, if we need additional help, we will raise that flag just FYI. Okay. Anything else we should add here that I missed, Kevin? Nothing that I can think of. Like you said, we have a lot of questions. We've got about six total responses right now. And I'm also doing interviews with anyone that might feel more comfortable doing so than doing a written response. Stefan Spiker actually was just one that we had recently. So if anyone else wants to contribute or submit anything, if they don't feel comfortable writing it out, we can do something like that. Okay, awesome. Yeah, I'm hoping that we can post a story, hopefully in the next one or two months. I don't know how much bandwidth Chris has and expertise and, but that's my hope. And I think Mark, I'm hoping that we can post a story. Hopefully in the next one or two months. I don't know how much bandwidth Chris has and expertise. I think Mark is on the same page as well. Okay. So that is taking place in Brussels, February 3rd to the 4th. Thank you Bruno again for sending out the Stan application. I'm filling it out. So as of now, we are planning to have a Jenkins presence there. So more to come at a later time. And that's all that I have for today. Thank you. Does anybody have anything else? Well, No, we'll, we'll wait for, for them. We have a couple of ideas. Yeah. Ranging from small. To big. To gigantic. We might call for. Or help or whatever playing with it. Let's first start October fest and see that this is rolling. Right. We'll pick the low hanging fruits for right now. And we'll tackle the big one once we get closer. Yep. Okay. Thank you so much. For everybody's attendance. Have a great one. Okay. Bye bye. Bye.


Section 7 of Areopagitica. ye cannot make us now less capable, less knowing, less eagerly pursuing of the truth, unless ye first make yourselves, that made us so, less the lovers, less the founders of our true liberty.  That our hearts are now more capacious, our thoughts more erected to the search and expectation of greatest and exactest things, is the issue of your own virtue propagated in us. Ye cannot suppress that, unless ye reinforce an abrogated and merciless law, the fathers may dispatch at will their own children. And who shall then stick closest to ye, and excite others? Not he who takes up arms for coat and conduct, and his four nobles of Danagelt? Although I dispraise not the defence of just immunities, yet love my peace better, if that were all. Give me the liberty to know, to utter, and to argue freely according to conscience, above all liberties. What would be best advised then, if it be found so hurtful and so unequal to suppress opinions for the newness, or the unsuitableness to a customary acceptance, will not be my task to say. I only shall repeat what I have learned, from one of your own honourable number, a right noble and pious lord, who, had he not sacrificed his life and fortunes to the church and commonwealth, we had not now missed and bewailed a worthy and undoubted patron of this argument. Ye know him, I am sure. Yet I, for honour's sake, and may it be eternal to him, shall name him, the Lord Brooke. He, writing of Episcopacy, and by the way treating of sects and schisms, left ye his vote, or rather now the last words of his dying charge, which I know will ever be of dear and honoured regard, with ye, so full of meekness and breathing charity, that next to his last testament, who bequeathed love and peace to his disciples, I cannot call to mind where I have read or heard words more mild and peaceful. He there exhorts us to hear with patience and humility, those, however they may be, miscalled, that desire to live purely, in such a use of God's ordinances as the best guidance of their conscience gives them, and to tolerate them, though in some disconformity to ourselves. The book itself will tell us more at large, being published to the world, and dedicated to the parliament by him who, both for his life and for his death, deserves that what advice he left be not laid by without perusal. And now the time in special is, by privilege to write and speak, what may help to the further discussing of matters in agitation. The temple of Janus, with his two controversial faces, might now, not unsignificantly, be set open. And though all the winds of doctrine were let loose to play upon the earth, so truth be in the field, we do injuriously, by licensing and prohibiting, to misdoubt her strength. Let her and falsehood grapple, whoever new truth put to the worse, in a free and open encounter. Her confuting is the best and surest suppressing. He who hears what praying there is for light and clearer knowledge to be sent down among us, would think of other matters to be constituted beyond the discipline of Geneva, framed and fabriced already to our hands. Yet when the new light, which we beg for, shines in upon us, there be who envy and oppose, if it come not first in at their casements. What a collusion is this, when as we are exhorted by the wise men to use diligence, to seek for wisdom as for hidden treasures early and late, that another order shall enjoin us to know nothing but by statute. When a man hath been furnished out his findings in all their equipage, drawn forth his reasons as it were a battle-ranged, scattered and defeated all objections in his way, calls out his adversary into the plain, offers him the advantage of wind and sun, if he please, only that he may try the matter by dint of argument, for his opponents then to skulk, to lay ambushments, to keep a narrow bridge of licensing where the challenger should pass, though it be valour enough in soldier-ship, is but weakness and cowardice in the wars of truth. For who knows not that truth is strong next to the Almighty? She needs no policies nor stratagems nor licences to make her victorious. Those are the shifts and the defences that error uses against her power. Give her but room and do not bind her when she sleeps, for then she speaks not true, as the old Proteus did, who spake oracles only when he was caught and bound. But then rather she turns herself into all shapes except her own, and perhaps tunes her voice according to the time, as Micaiah did before Ahab, until she be adjured into her own likeness. Yet is it not impossible that she may have more shapes than one? What else is all that rank of things indifferent, wherein truth may be on this side or on the other, without being unlike herself? What but a vain shadow else is the abolition of those ordinances, that handwriting nailed to the cross? What great purchase is this Christian liberty which Paul so often boasts of? His doctrine is that he who eats or eats not, regards a day or regards it not, may do either to the Lord. How many other things might be tolerated in peace, and left a conscience, had we but charity, and were it not the chief stronghold of our hypocrisy to be ever judging one another? I fear yet this iron yoke of outward conformity hath left a slavish print upon our necks, the ghost of a linen decency yet haunts us. We stumble and are impatient at the least dividing of one visible congregation from another, though it be not in fundamentals, and though our forwardness to suppress and our backwardness to recover any enthralled piece of truth out of the gripe of custom. We care not to keep truth separated from truth, which is the fiercest rent and disunion of all. We do not see that, while we still effect by all means a rigid external formality, we may as soon fall again into a gross conforming stupidity, a stark and dead congealment of wood and hay and stubble, forced and frozen together, which is more to the sudden degenerating of a church than many sub-dichotomies of petty schisms. Not that I can think well of every light separation, or that all in a church is to be expected gold and silver and precious stones. It is not possible for man to sever the wheat from the tares, the good fish from the other fry. That must be the angel's ministry at the end of mortal things. Yet if all cannot be of one mind, as who looks they should be, this doubtless is more wholesome, more prudent, and more Christian, that many be tolerated rather than all compelled. I mean not tolerated popery and open superstition, which as it extirpates all religions and civil supremacies, so itself should be extirpate, provided first that all charitable and compassionate means be used to win and regain the weak and the misled. That also which is impious or evil, absolutely either against faith or manners, no law can possibly permit, that intends not to unlaw itself. But those neighbouring differences, or rather indifferences, are what I speak of, whether in some point of doctrine or of discipline, which, though they be many, yet need not interrupt the unity of spirit, if we could but find among us the bond of peace. In the meanwhile, if any one would write, and bring his helpful hand to the slow-moving reformation which we labour under, if truth have spoken to him before others, or but seemed at least to speak, who hath so bejewited us that we should trouble that man with asking licence to do so worthy a deed? And not consider this, that if it come to prohibiting, there is not ought more likely to be prohibited than truth itself, whose first appearance to our eyes, bleared and dimmed with prejudice and custom, is more unsightly and unplausible than many errors, even as the person is of many a great man slight and contemptuous to see to. And what do they tell us vainly of new opinions, when this very opinion of theirs, that none must be heard but whom they like, is the worst and newest opinion of all others, and is the chief cause why sects and schisms do so much abound, and true knowledge is kept at distance from us, besides yet a greater danger which is in it. For when God shakes a kingdom with strong and healthful commotions to a general reforming, it is not untrue that many sectaries and false teachers are then busiest in seducing. But yet more true it is, that God then raises to his own work men of rare abilities, and more than common industry, not only to look back and revise what hath been taught here to fore, but to gain further, and go on some new enlightened steps in the discovery of truth. For such is the order of God's enlightening his church, to dispense and deal out by degrees his beam, so as our earthly eyes may best sustain it. Neither is God appointed and confined, where and out of what place these his chosen shall be first heard to speak. For he sees not as man sees, chooses not as man chooses, lest we should devote ourselves again to set places and assemblies, and outward callings of men, planting our faith one while in the old convocation-house, and another while in the chapel at Westminster. When all the faith and religion that shall be there canonized is not sufficient without plain convincement, and the charity of patient instruction to supple the least bruise of conscience, to edify the meanest Christian who desires to walk in the spirit and not in the letter of human trust, for all the number of voices that can be there made, no, though Harry the seventh himself tarry there with all his liege tombs about him, should lend them voices from the dead to swell their number. And if the men be erroneous, who appear to be the leading schismatics, what withholds us but our sloth, our self-will, and distrust in the right cause, that we do not give them gentle meetings and gentle dismissions, that we debate not and examine the matter thoroughly with liberal and frequent audience, if not for their sakes, yet for our own. Seeing no man who hath tasted learning, but will confess the many ways of profiting by those who, not contented with stale receipts, are able to manage and set forth new positions to the world. And were they but as the dust and cinders of our feet, so long as in that notion they may yet serve to polish and brighten the armory of truth, even for that respect they were not utterly to be cast away. But if they be of those whom God hath fitted for the special use of these times, with eminent and ample gifts, and those perhaps neither among the priests nor among the Pharisees, and we in the haste of a precipitant zeal shall make no distinction but resolve to stop their mouths because we fear they come with new and dangerous opinions, as we commonly forejudge them ere we understand them, no less than woe to us, while, thinking thus to defend the gospel, we are found the persecutors. There have been not a few since the beginning of this Parliament, both of the Presbytery and others, who by their unlicensed books, to the contempt of an imprematur, first broke that triple ice clung about our hearts, and taught the people to see day. I hope that none of those were the persuaders to renew upon us this bondage which they themselves have wrought so much good by condemning. And if neither the check that Moses gave to young Joshua, nor the countermand which our Saviour gave to young John, who was so ready to prohibit those whom he thought unlicensed, be not enough to admonish our elders how unacceptable to God their testy mood of prohibiting is, if neither their own remembrance what evil hath abounded in the Church by this set of licensing, and what good they themselves have begun by transgressing it, be not enough, but that they will persuade and execute the most Dominican part of the Inquisition over us, and are already with one foot in the stirrup so active at suppressing. It would be no unequal distribution in the first place to suppress the suppressors themselves, whom the change of their condition hath puffed up more than their late experience of harder times hath made wise. And as for regulating the press, let no man think to have the honour of advising ye better than yourselves hath done in that order published next before this, that no book be printed unless the printers and the author's name, or at least the printers, be registered. Those which otherwise come forth, if they be found mischievous and libelous, the fire and the executioner will be the timeliest and the most effectual remedy that man's prevention can use. For this authentic Spanish policy of licensing books, if I have said ought, will prove the most unlicensed book itself within a short while, and was the immediate image of a star chamber decree to that purpose made in those very times when that court did the rest of those her pious works, for which she is now fallen from the stars with Lucifer. Whereby ye may guess what kind of state prudence, what love of the people, what care of religion or good manners there was at the contriving, although with singular hypocrisy it pretended to bind books to their good behaviour. And how it got the upper hand of your precedent order so well constituted before, if we may believe those men whose profession gives them cause to inquire most. It may be doubted there was in it the fraud of some old patentease and monopolizers in the trade of book-selling, who under pretense of the poor in their company not to be defrauded, and the just retaining of each man his several copy, which God forbid should be gained said, brought diverse glossing colours to the house, which were indeed but colours, and serving to no end except it be to exercise a superiority over their neighbours. Men who do not therefore labour in an honest profession, to which learning is indebted, that they should be made other men's vassals. Another end is thought was aimed at by some of them in procuring by petition this order, that, having power in their hands, malignant books might the easier escape abroad as the event shows. But of these sophisms and elinx of merchandise I skill not. This I know, that errors in a good government and in a bad, are equally almost incident, for what magistrate may not be misinformed, and much the sooner, if liberty of printing be reduced into the power of a few. But to redress willingly and speedily what hath been erred, and in highest authority to esteem a plain advertisement more than others have done a sumptuous bride, is a virtue, honoured lords and commons, answerable to your highest actions, and whereof none can participate but greatest and wisest men.


Boy Finds Person Lake recognizes photos inside. He opened the purse as his uncle stood over his shoulder, watching intently. The contents were all water damaged, but there was one item that his uncle was shocked to see. His heart raced as he grabbed the photo, wiped it, and looked closer. Quickly, he asked young Brody to confirm his suspicions. He dropped it and called 911. 11-year-old Brody Brooks was so excited when he received his new fishing rod for his birthday. He loved to go out fishing with his uncle and the boys. For him, there was nothing more fun than a fishing adventure. However, Brody never thought that one of his adventures would lead him to a purse full of treasure and mystery. After arriving at Lake Hartwell, Anderson County, with his uncle Ben Myers, they got on their boat and set out on the lake. With their fishing rods ready, they passed the time with some chit chat. Brody waited patiently for a fish to nibble, completely unaware that today's catch would have to be turned into the local police. Brody learned everything he knew about fishing from his uncle. He helped set up Brody's rod, and proudly watched as Brody began to improve steadily. Brody hadn't caught much fish so far so Ben was pleasantly surprised when Brody's rod began to bend before he did. But his pride for Brody quickly turned to worry when he saw what was on the other end of Brody's line. Brody learned everything he knew about fishing from his uncle. He helped set up Brody's rod, and proudly watched as Brody began to improve steadily. Brody hadn't caught much fish so far so Ben was pleasantly surprised when Brody's rod began to bend before his did. But his pride for Brody quickly turned to worry when he saw what was on the other end of Brody's line. It was a purse. At first, he was upset that it wasn't a big fish like he hoped. But then he realized it was heavy. There must be something inside. Brody's uncle watched as he hauled the soap mysterious object from the water. He cleaned it, revealing a lovely colorful design. As the purse began to take shape, so did Brody's imagination. He wondered about what kind of treasures he would find inside. Little did he know, there was a lot more than treasure awaiting him. There was no doubt the purse was old, but there was one item inside the purse that would give astonishing evidence as to how old it truly was. He opened the purse and peered inside. Brody opened the purse as his uncle stood over his shoulder, watching. The contents were all water damaged, but there was one item that Brody's uncle was shocked to see. Ben was surprised to see many photographs among lipsticks and other womanly items within the purse. Although the photos were damaged, it was still possible to just about make out what was pictured. Ben and Brody looked closer. Ben jumped back as he realized he recognized the faces in the photos. Faces that hadn't seen the light of day for a long time. Two questions were burning in the back of Ben's, how long ago was this purse plunged into the lake? And where could the owner of the purse be? Ben began to grow suspicious. He asked Brody to help him spread the photos out so they could dry. Then he realized he could be tampering with evidence, he quickly called the police. Ben knew this face, even Brody said he recognized it. She was a friend of the family. I went to school with her nephew, but I haven't seen her in 10 years, Ben said. How could this woman he knew have their purse in the lake? How long was it at the bottom of the lake? Worry set in as Ben realized that this might be proof of something and he was interfering with police business. After they alerted the police to their mysterious finding, Ben scoured the internet in search of the woman that seemed to have disappeared. It wasn't long until he managed to find her nephew, who was shocked to hear Ben's story about the purse. The nephew wasted no time in calling his aunt to relay what Ben had told him dot what happened. The purse's owner was April Bolt, now 49 years old. She couldn't believe that her purse had finally been found. I couldn't believe it. I was lost for words. You never think you'd see it again, she said in an interview. She had lost it back in 1992, an unbelievable 25 years ago. But April believes that her purse disappeared under suspicious circumstances. April had attended a cookout back in 1992 at Lake Hartwell. We were on the boat and my parents had a condo there and we were grilling burgers and we parked the boat in the slip. There were two guys there fishing in, I hate to accuse anybody, but when we got back I was like, my pocketbook is gone, she explained. At the time, April had been devastated. I was crying. It wasn't a whole lot of cash, maybe like $60.  It was devastating, she said. My favorite lipstick was in there and the color was discontinued. But it wasn't the lipstick or the cash that April was most upset about losing. Among the items that Ben had found inside the purse were baby photographs of her son. My son is 26 now, but he was 15 months then, and I had all his photos that were professionally taken in my wallet. They have water damage but you can make him out, April said tearfully. When asked about their amazing catch that day on Lake Hartwell, Ben and Brody still can't quite believe it. It was pretty wild, Ben told ABC News. You fish up a purse, for one, then you actually know who's it was. Brody, on the other hand, hadn't been as thrilled as his uncle to have caught an old purse instead of a fish. The boy's disappointment was all over his face when they reeled in the leathery old purse. But it was Ben who had recognized the catch for what it was.  Ben recalls, laughing. But what did April think about being reunited with her belongings that had been missing for over two decades. She simply said that the purse's recovery meant the world to her. But she still has some unanswered questions.  And by whom?  And by whom? Secondly, she wonders why it has been returned to her now. She believes that the universe must have its reasons. Everyone keeps telling me, there's got to be a meaning to why you're finding this so many years later, she reveals. I'm sure God will reveal that in time. Meanwhile, she is enjoying the memories that the items in her purse have brought back. It's just so precious to have it back, she happily concluded.


Now we need a highway. We know the anatomy inside the tongue that's going to receive the taste information, and we've delivered that taste information from the taste bud to the sensory neuron. And now we need a highway. How are we going to get to the brain? In fact, where are we going to go in the brain? And what path are we going to follow to get there? And why? And you know what? I want you to push pause. This little guy is peeking around the corner right now, and he's like, please let me out, I've got the answer, but you first go and think about it. See if you can figure it out, see if you can hypothesize, where would you expect the fibers to go, and through what highways would you expect them to travel? And I know you can do it, because look, this is the picture that shows you, okay, cool, we actually do have a path that we're traveling.  Because I love this stuff. I love it when we put together pieces. I think this might be my favorite unit in anatomy, because all the pieces build and then you're like, oh, what, what, who is this? Who is that, what is that path that looks like it is bringing information from the anterior two thirds of your tongue? And remember this cranial nerve number seven, which was responsible for carrying sensory information of taste from the anterior two thirds of your tongue? Yeah, I know you remember that. Who is responsible from the posterior two thirds from my little tongue here? Who's bringing this information? It's another neuron that is synapsing with my taste buds, who's this guy? Remember that was cranial nerve nine, hypoglossal. Glossopharyngeal, it didn't sound right. Glossopharyngeal is cranial nerve nine and is receiving taste sensation from the posterior one third of your tongue. That's all review. You guys are like, boom, I could have figured that one out. So now we've got the information coming in. Okay, you can figure it out. Where would you expect it to go next? Well, first of all, and this is true for the rest of the entire lecture, there are details that we are leaving out.  We're getting comfortable with the idea that, you know what, we need a road. We need a road to get somewhere. And we're going to make our roads structures that we've already done, structures in the brain, nerves that we've already looked at. Let's make use of them now and let's see how they actually play in a pathway. Yes, there are some other stops along the way. There are some stops we do first. But there's like five billion more stops that our book doesn't even go into. And so we're just going to take it one step out because we want to see the big picture. We want to get overwhelmed by the crazy details, right? We always want to avoid overwhelming you in anatomy. Okay, where are you going to expect to go next? Craneal nerves are going to ultimately go where? Wouldn't you expect a stop at the thalamus? Who is the only sense that doesn't stop at the thalamus? The only one was smell. Everybody else stops at the thalamus. Everyone else synapses at the thalamus. And so you can just imagine that, yeah, we're going to take a cranial nerve to the thalamus. Yes, there's another pathway in there, but we're just going to... I want you to know cranial nerve and ultimately to thalamus. At the thalamus, what's the thalamus going to do? Is this worthy of consciousness? And if it is, where's it going to go? This is something, we're talking about our chocolate here. Let's send the message on because you know what? Let's be aware when we're eating delicious chocolate that somebody bought you because you're awesome. Where are you going to go next? Remember? The insula. The insula is the lobe of the cerebrum that's responsible for processing conscious sensations of taste.  Now, once you've tasted it, our sensory pathways are going to get the information there.  You could be like, hmm, that's so yummy. You could be like my kids who, if it's brown chocolate, they're like, mm-mm. And the darker brown it gets, the more they're like, this stuff's awful.  Maybe you feel it spit it out. But if you're me, maybe you do a little happy dance, like, life is good. We're eating that chocolate, mm-mm-mm. And look at all those other muscles that just got all excited and did their thing. And who's sending the message there? Whoa, isn't the nervous system fantastic? And isn't it kind of cool to put the pieces together here? All right, let's talk about smell next.


The statistical framework of data assimilation allows for the use of new remote sensing data to update forest databases by combining existing data with each new dataset, utilizing all available data in proportion to their quality to improve prediction. Extended Kalman filtering was used in this study on 137 sample plots over a period of four years at a test site in southern Sweden, resulting in predictions closer to the reference value than predictions based on single time points for variables such as lawy's mean height, basal area, and stem volume. The median reduction in root mean square error was 0.4 m, 0.9 m2 per hectare, and 15.3 m3 per hectare, 2%, 3%, and 6%, respectively. This article was authored by Niels Lindgren, Henrik J. Persson, Mathias Nystrom, and others.


Okay. Here we go. Welcome. I'm Miro, the track chair. This is Microsoft invited as a featured speech about redefining the mind shift at Microsoft. Yes. Thanks a lot for showing up here, and I'm really excited to have you here, and thank you, and I'm really eager to hear what you're having to tell us. Thank you, Miro, and thanks to the organizers of this conference for this really wonderful opportunity to be here today. My name is Grace Francisco. I'm actually from San Francisco, believe it or not. That's true. Then what's also true is I do work for Microsoft. I've been working for Microsoft for eight years, and the last two and a half years, believe it or not, has been all focused around open-source community work. I am on Twitter, that's my Twitter ID, GraceFR. If you're looking to find out what I'm eating or where I'm going, you're not going to find it there, but I try to share some useful tidbits. Along with me today, along with me today, I have Mark Brown, the teddy bear-looking guy over there. He's a technical marketing for Azure. Sorry. By the way, on Twitter, you're likely just to be offended by what I have to say rather than what I'm eating. And on his other side, Brian Swan is a technical writer, also on the Azure team. And then Mikayla Kraft on the end there, the beautiful Mikayla Kraft. She is a local person in Western Europe that covers this area. All of us actually focus on open-source. That may or may not be a surprise to some of you guys, but we actually have hundreds, thousands of people in Microsoft that do something with open-source in the company worldwide. As a company, we actually are very committed to openness, and we demonstrate that in three very specific ways. We really have a commitment around playing well with others, and we do that by being involved regularly in standards, by really being involved in making sure that open-source technologies work with our technologies as well. We listen very carefully to our customers, and as a result, we look at ways to combine our technologies with other technologies to ensure that we're providing innovative solutions that are cost-effective for them and efficient. And we are open in the cloud. We're open in the cloud today. You can actually develop on Azure, which is our cloud platform, and use Java. You can use Python. You can use PHP. You can use Node.js today on Azure. And Mark is gonna be talking in a little bit here about more specific things that we're enabling with open-source project on Azure. So I'm gonna take a minute here to talk a little bit more about how we're investing in standards, what we're doing with embracing and enabling these open-source projects. This may come as a surprise to some of you guys, but Microsoft has actually been involved in standards work for over 20 years, and today we're actually part of 150 official standards organizations and part of 400 working groups. And we do that because we see that as a critical and essential way that we enable interoperability with other projects, with other open-source projects and other technologies. And that is because we all want happy customers. No single vendor can possibly offer all of the solutions a single customer's complex environment might need. And so we do that so that we have a happy customer that can use any device connected to any system and have it work the way that they expect. A few other factoids about the stuff we've been doing with open-source. In a single year, because of all the work we're doing to enable these open-source projects in our platform, we had 400% growth just in a single year alone. So we have over 350,000 projects that zero scooted over on Mark's Mac. Sorry. And that's $350,000, not 35, $350, it's $350,000 projects working on Windows. 23 of the top 25 open-source projects actually work on our platform. CodePlex, some of you may or may not be familiar is one of the open-source communities that we've been fostering. That continues to grow with numbers of open-source projects that we and other people in the community continue to contribute. And we have 300,000 registered users that also is continuing to grow. Microsoft Web Gallery is where we have a listing of many of the web applications that also work on our platform. And we have well over 5 million downloads. They're since inception over three years ago. One of those, actually two of those popular applications that's being downloaded is Acquia Drupal's package. And the second one being Commerce Kickstart. And I'll mention also the third, since Brian's team is here, Bing Joomla. And here I'm gonna turn it over to Mark so he can talk more about how we're involved with open-source and our product groups and how we're enabling those. Mark? Right, thanks Grace. So I think everybody kind of remembers the famous Linux as a cancer comment that our famous CEO made some years ago. While that was something that stands out in the news and certainly stands out in people's mind, it actually internally at Microsoft was something of a watershed event. As a lot of people who have been with the company for a lot of years actually were involved with the open-source community and understood open-source for what it really is rather than what the perceptions were internally among the leadership of the time. I mean, and one of the big things that kind of fell out of that was for us to really organize around open-source technologies and to work to try and integrate and interoperate with them. And one of those things was the creation of our open-source technology center. And through that technology center, we basically hired a lot of Linux developers and low-level developers to try and work with Linux and then try and work to interoperate with Linux and other open-source technologies. Some of the things you'll see out of that or have seen out of that is a lot of contributions we've been giving to Linux and in fact Microsoft now is one of the top contributors to the Linux kernel and we provide drivers for Linux and also provide integration with our Hyper-V virtualization technology. One of the other big contributions that came out of that group was contributions to PHP, beginning with version PHP 5.3, Microsoft and along with guys like Pierre Joy who was up here in the session just beforehand, along with a lot of other PHP core contributors, essentially took and rewrote all of PHP and then created a build for Windows in there. So a lot of PHP and of course the legacy for PHP is on Unix and of course Win32 and our operating system and libraries work a little differently. We wanted to make PHP work really well on Windows and so instead of maintaining a consistent code base, we decided we'd maintain consistent APIs and then optimize the source code underneath and optimize that for Windows and a lot of that had to do with a lot of file IO and some other stuff involved in there. The result you get now is essentially parity for PHP running on Windows as you would get on Unix or Linux. What else have I got in there? Oh, and then other stuff around Samba. I think everybody's aware with our contributions and work with those guys as well. Yeah, next slide. Yeah, Brian, you want to talk a little bit about SQL Server and the work you guys have done? Put me on the spot here. Sure, why not? Okay, so towards making sure PHP not only runs well on SQL Server but that you have a full range of functionality that you would expect from PHP running on Windows. We put a lot of work into a PHP driver for SQL Server. That is an open source project. It's on, I think it's now on GitHub. It used to be on CodePlex but we've recently moved it to GitHub. What the biggest request that we've had for that driver, I mean we've had lots of little requests and we've tried to implement those but the single biggest request that we've had has been that it runs on PHP running on Linux so that you can have SQL Server access from PHP on Linux. We recently released an ODVC driver for Linux, a SQL Server ODVC driver for Linux and if you put two and two together you can see that since our PHP driver now sits on top of ODVC APIs on Windows it's not gonna be too long before that scenario is enabled. So some of the other stuff we've been working on certainly around our web platform and around particularly our IAS product. IAS used to be pretty awful frankly as a web server back in the IAS five and six days. That largely changed with IAS seven. We've just basically just chucked a lot of it and rewrote most of that from scratch. FastCGI or implementing FastCGI on our platform to host PHP applications was a part of that. A lot of the other work that went into making it better though were a lot of code we wrote that we actually ended up just open sourcing in general. WinCache is kind of a functional APC cache so it's an opcode cache for PHP and then also a user cache for data that you may pull out of MySQL. That's completely open sourced. It's actually contributed to Peckle as well so if you go and install PHP on Windows you can go and pull down this Peckle extension and then automatically get 200% plus improvement for PHP on Windows. Managing PHP for some, at least in the Windows world can be a little confusing. So another project we created was PHP Manager which is just a plugin for IAS and we decided we would just open source that as well. So that's also available. Quite a few years ago we created this thing called ASP.net Ajax. And what we realized is that it didn't make a lot of sense for us to create our own version of kind of JavaScript library so we ended up just chucking that thing and then adopting jQuery and now we're actually one of the largest contributors to jQuery and we actually ship jQuery with our tools in there. The point I'm trying to make there is that even within our own .net community there was kind of a mind shift happening that was growing out of just people that were working strictly with kind of the Linux and the PHP communities into our own web developer communities and realizing that it makes much more sense to contribute to existing successful projects than it is to try and compete with them even if you do open source the code that's with there or within them. And so that kind of mind shift kind of just started trickling up and out within the company and so after we started doing contributions to jQuery the team that basically does all our web platform stuff for all the ASP .net stuff said well maybe we should take that same approach with our own technologies and so some of the other stuff they've been doing now is they've now taken an open source pretty much the entire code base for all the ASP .net stuff. So ASP .net MVC, there's a web API and then we have a razor view engine which is like an MVC view engine and then another thing called the entity framework to kind of the point they're making is that the whole understanding and how to work with the open source communities was now starting to kind of grow outwards and touch a larger section of the company and even into our own .net engineering teams there. Another slide. Right and so that kind of continues now actually and the leadership that's been a part of that part of the company is now largely running a lot of our Azure and our cloud stuff. So some of the work we've been doing now and includes not just Drupal but other web communities like Joomla and then of course there's other open source communities in the .net world like in Brocco and .net Nuke and now that's going even further now with work with Java and Node.js and then kind of finally the big kind of big coup was support for Linux itself within our own cloud platform. So now if you wanna go and host your applications in our Windows Azure cloud platform you can choose Windows if you want or you can choose Linux or if you want you can upload your own flavor of Linux even. So it's actually now really to the point where that mind shift is actually kind of reflected in the products and the services that we wanna come to market with because we really believe that the choice is what matters and the ability to make that choice. So I think now it's kind of really come full circle for us as a company. So one of the, as Mark talked, just said the where you're seeing a lot of the change now is in our Azure platform and where you're seeing, where you'll see that if you go to any one of our one of our dev centers. What we've realized in, one of the things that we've learned in being committed to open source and interoperability is that documentation cannot take a backseat. It can't be an afterthought. And if you take a look at there's just a screen shot up there of what's available on our dev center and the various languages that we are supporting and trying to provide documentation for. Certainly presents its challenges in trying to document all of these other languages that other groups and communities are producing and document the interoperability between those languages in our platform. One of the things that we learned was that MSDN didn't work. I don't know if any of you have tried to use MSDN documentation but that was not something that was gonna work for us. What we needed to do was get documentation in front of where people are reading documentation, where you guys go for it and put it in a format that you're used to and can digest easily. So you see a lot more blogs that are focused on open source technology. You see a lot more, you see our documentation, we've contributed documentation to PHP.net. And if you take a look at the Windows Azure Dev Center, you'll see an entirely different format different from the MSDN format as well. And I think the crowning jewel at least in my view about documentation is that all the documentation is also open source. It's all in markdown on GitHub. So when you see that bug in the documentation that says, wait a minute, that code example doesn't work or something isn't explained clearly, you can fork it and submit a pull request and have that merged into the documentation and it gets published on a weekly basis. So that's, you know, we're taking not only the mind shift that has gone into the product and the services that we're offering, you know, is also reflected in the documentation and the processes for our publishing documentation. And as far as the work that we've done to increase our openness with Drupal, I've actually been working specifically in the Drupal community for the last two and a half years and some of that work actually started well before I took on my role. And just to give you a sense for, you know, the work that we've done over across this timeline. In 2010, we actually partnered up with the commerce guys and sponsored the work that they were doing around the SQL server integration. And then we extended that work to also include SQL Azure and Azure itself. So they actually built and contributed modules to Drupal.org that people could use to enable SQL server integration, SQL Azure integration and Azure deployment. In terms of listening to customers, I started working with Jacob Redding and the Drupal association was really, you know, when I started out this work, I spent a lot of time listening to feedback, listening to what the needs of the community were all about. And some of the things that came back pretty readily was, hey, you know, we have some of these windows developers and you know, they try to download the modules. They're all in tar file and some of them just don't know what to do with that because they're new to the platform. They don't understand what to do with these tar files. Wouldn't it be great if actually we had zip file formats by the way we're doing a Drupal.org, you know, revision of the website. And so we talked about, you know, helping and sponsoring updates to the site overall, which also included zip files format. So anytime you actually upload a new module that automatically gets converted to zip. And a year later I'd heard Robert Douglas actually say, you know, it's something like 44% of the downloads were actually in that zip file format. So that got put to use pretty quickly. The other piece of feedback that I got was, you know, Drush was the de facto tool people were using and you know, people were really trying to cobble this together on windows. You know, somewhat successfully, but not really and it was a really painful process. So we invested and sponsored some work with pro people, which is now Wunderkraut, yeah, pro people, which is now Wunderkraut. But back then they were pro people and I also sponsored some work there to get Drush compatible on windows. Last March in Denver, Moshe was doing a big Drush session, which he's doing right now actually in another room. And one of the things he said was, it's arguably easier to install Drush on windows today than on any other platform. And that was due to the investment and really the partnering that we did with Moshe and Greg Anderson and folks in the community that volunteered as well as pro people in their work and making that compatible. We also invested on actually creating a set of content to be delivered in person in Denver, which was Drupal at scale on windows, because we got a lot of questions over and over again at the booth about, you know, we don't have the guidance around this, how do we deploy this at scale, you know, what's the equivalent of the things that I'm using on my lamp stack to Windows Server. So we enlisted the help of a Microsoft MVP who happened to also be a Red Hat Atlantic certified engineer. And he was able to talk and create training that was in terms of what you guys know and understand. And so that was delivered in Denver and we actually have that online for free on channel nine. So you can actually consume that content now. The other thing that we did this past year is we actually contributed directly a couple of modules. One is the WinCache module to be integrated directly with Drupal. That's again performance optimization. Mark referred to that a little bit earlier. And OData, which is unless a standard basically for data exchange. And so both of these modules have been contributed to Drupal.org directly by our teams. We're also an inaugural Drupal supporting partner. And this is our seventh DrupalCon and we've got several more that we've already enlisted subscribed for in this coming year. So you're gonna continue to see more and more of us and you know, we are really happy to be here and talking with everyone. So please we're here to listen to your feedback. We'd love to talk to you more. You've got any questions we're at the booth and we'd love to talk to you. Mikhail? My great set, I'm working in the field and I'm really the counterpart. Can you hear me? I can hear you. Yes. I can hear myself as well. Let's do it this way. Better? Good. So I'm the counterpart to my colleagues from the US. So I'm really working in the field and I work a lot with the Drupal shops to make this partnership more lively. And on this list, you can see my daily work. So on one hand side, I'm helping sponsoring different events. But what we have also started really to do is if you are planning a code sprint or something like this, you can contact us because we have in all the country's offices and we are more than happy to give you these offices for free, use all the facilities. On one hand side, this is taking away a lot of organizational, overload to you folks. And you can really come together as a community and use these facilities for your code sprints or whatever events you are planning. Then we have also started roughly one and a half year ago to work with the CXO community of Drupal. And twice a year, the CXOs across Europe, they meet and they also use our facilities and I participate in these kind of events because Microsoft did also grow as a company and we had also our challenges. So I can really help and support the CXOs with different questions like how can we do better marketing for Drupal? So also really some business topics. Yeah, and we are also doing some projects together. So for example, one year ago, one of the Drupal shops contacted me and he said, hey, I have a big customer who has SharePoint and he would like to use Drupal. So I was really helping this shop or this project to come together and we have now a running project in the Netherlands where we have SharePoint and Drupal integrated together. And this is also very positive for the community because you don't have very often the Microsoft knowledge. So we can really bring together some specialists and help you to gain the knowledge but also on the other hand side, the customer is really happy if there is also a bigger company behind where they have already some licenses installed. Another project is Microsoft Health. I don't know if you ever heard about Microsoft Health. It's a specific solution for the health environment. And a Drupal shop who is now a Microsoft partner as well pinged me and he said, hey, I have a big hospital who would like to use Drupal and the Microsoft Health solution together. So now we have integrated both products and this hospital is publishing some information of his health environment using Microsoft Health. And we are also working a lot now with the government. So as you might know, the governments are in front of open data projects and also here the question is how can we help each other to really bring open data, open government projects together with Drupal. And we have now some projects in Ireland, in Austria, in Germany, where we really made this kind of partnership life in projects. So this is a little bit what you can expect from us, from myself, if you have something in your mind, feel free to ping me. Now, one question I get a lot is, how do we connect the dots to you guys in the Drupal community and things that we can offer? And actually as a company, we offer a number of different programs that are the things that are probably most relevant for you guys to know about is two things. BizBark, Microsoft BizBark is actually for Starts. It's a program that enables startups to have access to our developer tools, our platform technologies like SQL server, Windows server, and even our cloud platform for no fee access. And this is really to help bootstrap their businesses as they're a fledgling startup and getting their business up and running. And then similarly, Microsoft WebsiteSpark is a program targeted to individual website developers as well as web agencies, small web agencies. And again, it's to reduce the sort of startup costs associated with having a business, and you're trying to build or test for your customers who are on Windows platform or on Azure, and it enables that easy friction free access to those licenses. The program also provides special offers that our network partners have in terms of special discounts for their services and fees. We often sometimes have special events and local venues that we'll invite our members to. So these are great programs to consider if you're either a startup or a small web agency or independent web consultant. The Commerce Guys specifically, we recently announced two, three months ago, they were accepted into our top tier, BizBark One program. BizBark actually has three tiers. So the first entry tier, most startups are qualified for, most young startups are qualified for it's BizBark. And there's BizBark Plus in that program, you have to be sort of nominated in by local folks in the offices and you get access to more Azure hours and benefits. But BizBark One enables them to have closer ties with us at Microsoft corporate. They actually have a specific person that they're assigned to as their portfolio manager at our corporate offices and they have increased benefits as part of that program. And then the reason we have this program is we're really trying to identify high potential startups. And we saw Commerce Guys as being one of these types of startups. And so we really want to ensure by having someone connect the dots for them within corporate because we're such full, kind of a big company being at 90,000 people. You kind of need help, sort of navigating our system. So they got help from a number of people actually both corporate and worldwide in our offices to ensure their success on Azure and their deployment. And lastly, I want to just talk about how a lot of this stuff comes together in a customer success story. SAG Awards, so that's a Screen Actors Guild. They have this huge Hollywood awards ceremony that happens in January. Now for most of the year, their traffic pattern is pretty flat. It's not a whole lot of traffic that comes throughout the year. But leading up to that ceremony in January, starting in November, they start to see spikes in their traffic. It's not very consistent. They're literally seeing the traffic spike up because of some announcement. And it's like up some more. And obviously in the days leading up to the event itself, they see a tremendous surge of traffic that happens. They've got a huge amount of content, huge amount of traffic spikes.  But even in throwing all that hardware, they would still see system failures and go down. And this past year, what they did was they decided they were gonna place their bets on Azure and move their Drupal, Drupal 7 website to Azure. And I say that a lot of this stuff comes together because in doing that, they actually use the Azure and SQL Azure modules in the commerce guys. That helped to enable this particular scenario. And on top of that, in the migration process, they actually use Drush on Windows. They use Drush on Windows to automate a lot of the migration, including pulling out the content from their MySQL databases and importing those into SQL Azure. And so that automated a lot of what would otherwise be a manual process. And that actually used Drush, which I thought was wonderful. So in that single night, that one premiere night, what they saw was basically over 300,000 visitors, just in one night alone. And 800,000 page views. As compared with the year before, they only saw about 200,000 visitors and about 300,000 page views. So the lower number of page views tells me, people got to this site, but they weren't able to navigate around because of the extreme traffic loads. Azure enables you to be able to scale up and scale down as you need those resources and be able to manage the type of low that you're experiencing at that point in time. So I hope that helps with, understanding some of what comes together when we work together as a community. So I really see, especially this being a success story of not just the work that we've done at Microsoft, but the stuff that we've done together with you as a community. And with that, I'm gonna open up to questions. Anyone have any questions or yep. So the question was, is the Drupal SharePoint integration to be published as open source? And Michaela's answer was just on that. It was developed between Microsoft, two Microsoft people and three Drupal people and it's available as an open source module. It's published on Drupal.org. Any other questions? We don't bite. You may see that at some point. They're doing some integration, I think, with CodePlex on there now for projects. I'd give that a little more time. I mean, TFS is the primary source code and CI for Visual Studio, but it's opening up, right? So that Visual Studio actually sits in a different part of the company and they're starting to get some of that religion as well. So that's right. And then TFS is gonna get support into it as well. Yep. The Drupal test boxes? Yeah, that's that thing that sits over in University of Oregon, I think. What the heck's that thing called? That's right, I think we're hosts on the servers, aren't we, in OSTC, to do all those Drupal core tests, the compatibility testing. Yeah. We started working with Gabor back in the six days to try and get that all set up. So we got, I think we've got all the test harnesses and everything that Drupal uses to do its core builds. For, yeah. No, that's, I think we even, that started like over two, three years ago. Yeah, I don't know if NetCraft has numbers like that. No, but the Acquia team has actually been sending me just logs of the folks that are actually deploying onto our platform so that you guys probably know they have a web crawler that they send out and check where Drupal is deployed. And they're definitely seeing that that's increasing. I don't actually remember the specific number of websites the last time they sent me a report, but we're seeing that grow. And I, you know, my sense is that's definitely growing with every Drupal con that we've been to and it started with London. We were seeing streams of people coming in and saying, hey, you know, I used to try to do the stuff manually on Windows and I found WebPI and that was so much simpler. And so it was pretty clear that as people were, you know, stumbling on WebPI or hearing about it from us that they were starting to actually use it to deploy on Windows because it wasn't as painful as it used to be or they didn't realize that it worked at all. And so, you know, a lot of this is an education process for us still to let people know that it works on our platform. Yeah, and a lot of the other problem is getting an accurate count because a lot of, at least anecdotally than the people I'm talking to, a large number of them are doing them behind firewalls. So you can't always, it's even with the, even with Dries's crawler, it's really impossible to get an accurate count. And then another huge chunk of those are in pub sector. So a lot of education universities and federal agencies are using Drupal because then they're already using Windows. Any other questions? I'm sorry? Mikayla, I think that was you that you answered that. No, just sent me an email and we figured out. Any other questions? It's pretty much hands-on work on the demand of the community. What's your Twitter alias again, Mikayla?  So either you use Mikcraft as a Twitter alias or Mikcraft at Microsoft.com. Any other questions? Yeah, actually I'm getting ready to deploy a Drupal site, actually running on a couple of instances of Ubuntu on Azure right now. Yes, I'm a user as well. Yeah, and we do have other sites that are actually deployed on Drupal. We actually acquired a site called teach.edu. I think it's now teach.org. That's also a Drupal site. And so that's part of our assets and that's something that they're moving to Azure as well. Yeah. See, and that's changing, right? So like our contributions to jQuery, I mean we basically just checked out our AJAX stuff, right? And just said that jQuery's better and it's already there and it's already being used by pretty much everybody. So let's just contribute to that. The other area where we're leveraging existing stuff that's already going on is in Node.js, right? So we have command line tools that you can use to manage sites and VMs and services in Azure. For Windows, we use PowerShell, right? That's kind of our bash, right? Well, that doesn't work very well on a Mac or it certainly doesn't work on Linux, right? So we built command line tools for Mac and Linux using Node.js because it's small, it's portable, and it's easy. So there again, we're trying to use existing technologies, open source technologies, and by the way, contributing to them as well because we want to make Node run great on Windows too, right? So you can actually use those same tools and run those on Windows if you want. You don't have to use PowerShell. But there again, we want to leverage something that's being good. Oh, and then, that's right. And then Hadoop is another thing as well, right? Where we basically chucked all our, what was that called? Power, something? I forget what that was called. Yeah, whatever, yeah. Basically, we're creating our Microsoft version of Hadoop and then just realized, you know, just why don't we just work with the Hadoop guys, right? So you can now actually go and sign up and try Hadoop on our Azure platform, right? And use the little JavaScript console and actually go and work with some big data. So yeah, just more and more examples, right? And that's, you know, it started small a few years ago and now I think it's largely kind of the way we want to do stuff. The use of GitHub is another example. I mean, that's to sort of sweeping product team, right? Right, so not only with the documentation, but all our SDKs are now open source and sitting out on GitHub for Azure, right? So our PHP SDK, our Node SDK, our Java SDK. Actually, the .NET one isn't yet, but it will be. They just gotta clean it up a little. We've actually been at the company long enough to actually personally witness a lot of these changes ourselves. I've been with the company eight years, Mark, you've been. 12 years, right? And I was an open source developer before then, right? So I used PHP back in the very early scary days and actually, so back in the four days before I joined Microsoft and then first, you know, .NET came out and I started doing that stuff as well, but it's been interesting watching the evolution for that company. Yeah, question. Yeah, I mean, it was a business, right? That was an argument, that was a statement made by a business guy, right? A C-level executive, not by an engineer, right? I don't think the engineers. Yeah, so what's happened is that people at the company that understood it finally got the message through and up into the leadership ranks in that company, right? So it was a small group of people at first, right? There's a guy named Sam Ramji who no longer with the company, right? But he spearheaded a lot of that mind shift at the company very early on a long time ago. And then others, you know, they joined the company and I think at some point you just hit a tipping point, right? Where it's like, look at this stuff, it's not gonna bite, right? So in fact, working with it makes much more sense, right? So, you know, who knows, it's never off the table, right? And there's two things that's going on, right? I mean, certainly creating interoperability and open sourcing the client bits that make that happen are one thing, but actually we're contributing to these projects as well, right? So that's another very big shift that's kind of happened over the last eight to 10 years here, so. I think your skepticism is definitely fair, right?  That's completely fair, but time is gonna tell and what I've seen in the last, I've only been here at Microsoft for five years and the excitement that you see among developers who are actually, I mean, they're developers at Microsoft. They get to now play with, they can kind of come out of the closet, so to speak, right?  Like Paul and I just did the other day. Right? But there's this kind of new excitement among the developer ranks and that's just kind of bubbling up and I feel good about the direction that things are going and feel pretty good that it is gonna continue to bubble up to the top. But I understand and respect your skepticism. I don't know what that means other than just being an interesting alliteration. I don't know what you mean. Yeah, well, you know how standards bodies work, right? Okay, so no, that's never gonna happen, right? Because it's impossible to do that with a standards body, right? I mean, within standards bodies, there's a history of every company trying to do something like that, right? So we're not alone in that. It's just the way that process works, right?   So I mean, within the open source communities themselves or those projects, there's a standard for, right? And a process for how you get stuff committed into it, right? So to your point, are we gonna try to extend it or whatever you say? I have faith in that the open source process works, right? And that I don't see ever that being a problem, right?  That's just the way that the whole process works, right? So just to comment on your, you know, us dog-fooding some of the things that we're contributing to open source projects. That SAIC Awards example that I gave to you, largely that work was done by our internal consulting team. So they were using it. They were using it for an external customer, but they were definitely pounding on the SQL Azure and using Drush themselves directly. And so as part of that, obviously they found certain issues that we were part of the process to help ensure it got fixed through the community, the people that we sponsored, and that we were doing things the right way and making sure those went back into the project. Yeah, and by the way, we dog-fooded every day the Hyper-V support. We contributed to Linux to actually host it in Azure itself, right? So we're actually, that's actually going into a service offering in itself, so. I think this is a very small example, but for writing a lot of our documentation now, since we're doing it in Markdown Pad, we're doing it in Markdown, we use Markdown Pad, and we started using that and found a ton of problems. We had engineers then contribute the changes to that project to make it work better. And I think that's the kind of thing that you're talking about is using those projects and then actually contributing to make them better. Really small example in Markdown Pad, but I think what you're talking about is entirely possible on a bigger scale. And just a side note, Drupal.org, we contributed some documentation to that site and I was personally the one that was funneling some of that content to Drupal.org. Took me well to figure out how that all worked and as part of that, I figured out that there were some issues too, so I actually posted those issues back to Drupal.org just so that you guys knew what I ran into as I was an end user at Drupal.org. Any other questions? By the way, in case you didn't see this, this is Mark's laptop, it is in fact a Mac, and everyone goes, aren't you gonna get in trouble? And that's not the case, actually. That's the best, it's actually the best Windows laptop I've ever had in my life. It's actually running, I'm actually running Mac. Yeah, they should be an OEM for Windows, don't you think? I think we'll ever do a Microsoft Linux. I don't know if we would have the final say on that. But there's others that do it better, let's say, right? Why bother, right? And that actually, I think to some, would probably look like an extender, an embrace, an extend, and another thing, right? So, let's just say that's probably best left to the experts, right? So, yeah. We're pretty tight with, you know, Shuttleworth is pretty happy with us right now.  Well, and don't forget, we now have Linux on Windows Azure. Yeah. Right, and that's actually the way we did that, is those guys are the guys that are actually offering it on there, right? So, it's actually, you know, they're distros, they maintain it, they provide service for it, right? So, and that's really the right way to do it. They're the experts, not us, so. That's why we, I think we're doing it right this time. Yeah. All right, well thank you everyone for coming to our session. Appreciate it. Thank you. The SQL Server stuff, I just left. It was? Oh, I just looked at it and assumed that was you, Brian, I'm sorry. I don't wanna talk with you. I shouldn't. Oh, it was? I did? Yeah. Oh, I'm sorry. Hi. Oh, absolutely. Hey, did you talk on after this? It is, yeah, we've met before. A long time ago. But I was trying to work out. You know what was, it was at, it was at Ebay at the Dream of the Pompers. No, no, I didn't go to that one. You weren't? Could it be back when, way back, I used to be, I used to run a Linux ISP in the UK, called UK Linux, and I used to be the sponsor of the dot org village at all the Linux worlds in the UK. Did you come to any of those? I was sitting there and thinking, I've met you before. Yeah. The only other place would be, I was, I spoke at Bill's. You know what? I didn't go to Bill's last year. Oh, that's okay. So I was there, I was there. I was the only, because I was speaking, I was allowed into the speaker's lounge. But everybody else who was speaking was a Microsoft employee. So they had this huge debate, was I allowed in the speaker's room? In the speaker's lounge? Because, yeah, you were a speaker, but it's a safe room. Right, right, right, right, yeah. An NDA room, right? Yeah, so I had to sit in the corner. That's terrible. Work with Vishal, my matrix team. Oh yeah, Vishal, right, right, yeah.  Maybe I met, it might have been during that time, but I didn't go to Bill, but if you were hanging around those guys, I mean, that was my engineering team, right? It was those guys back then. So, we've definitely met. We've definitely met, I just don't remember where now. Unless it was on sort of Linux days, when I was in the UK, but... I don't know, I mean, I just spent a lot of, I don't know, did you go to FOA's? At all? Yeah, all right. What else do I go to the UK for? Well, I don't know, tons of shows. Yeah, there's not, there aren't any anymore, really. Yeah, not any more. The only one left is the bat, which is the educational, which is huge. It's like the only exhibition left that has a computer in it. Or I wonder if it was... I went to a show about four years ago, it was at Alley Pally, actually, five years ago.  It was like a big hack fest. They had Doctor Who on the whole freaking time, on the big screen. No, also no. Was that, no, all right. Yeah, well, we've met somewhere. We've met somewhere, but it's good to see you again, yeah? It was funny, I was in Chicago, and I saw you with Brian Prince, was giving you the Azure presentation. Yeah, yeah. And he was like, you've got to be about the different Linux distros and the Stove and Sousa and then he says, it's sentos, it's sentos, you know, I never know which to call it. And sentos was founded in the same office that I worked at. Oh, serious? So there were three guys in the office. Really? Really? The self was founded during that. My partner founded sentos. The other guy we left actually was a piece. So not surprisingly, the piece had just died. Oh man. Yeah, I was thinking that as well. I'm going to go grab a cigarette before I set up. Yeah, I'll go with you. I'll go with you. But yeah, yeah, I was thinking that.