To je spirit, sprit, meni, kongolečnosti. Vse je od 8000, ne znam, kako je meni, stafano Zahjoli. Čekaj. Čekaj, meni, topečno, nekaj v debijenu, da je odličnja taj, bof, in prijev. to so zelo kar, ki se počutijo. Zaj je to dobro. So zelo je prišljeli kvalifikacje, kajsih a priste si je v teret dialo. In so meneo, da黑a vse.  Vse vse je vse podandil z nijegovosti z Vzločev, kaj neезdavno je tapo in povrati. Tako. Patej, da se nekaj prišlično zbijaj gobi 05, gobi infinite, ki se všim je napravil, in početil vse c11-money dokument. Vse je včešlje, ki so všim ni vse vse izgledaj. Patej, da nekaj smo prišlično vse v sessonu. Početaj, da ne znam, da si vse ne znam, da se prišlično zbijamo, da se izgledaj, kako je zbijamo. Zato. Znam z prind. Zato, kaj je prind?  Tudi je to vzela, ker je zelo, ker tega začala in še dobro tako površena, in je tudi vsega, da je dobro, tako neče, in moj profil in dojda in so vziv sa poničenem. In izgledajte, da je ima pravi fonamentalne vsoče veli handy vsoče, da vedem, ki sem tukaj. Svinz in debjan je velika traditivna. V Evrstu nici cubec in v 2005, na pova, da antar. To je nischi tukaj, od kako they zdrav zamo in, na debičnjih vrštih gradov. To je z dvega korezina, v korezina, pri korezina, na večo vrštih z vse delati. To je z nimi nekaj vrštih. V 2006, za 3 dvega, vrednjih nekaj vsega vrednjih dejbianja, kaj nam ne zbilo debičnji, narednjih je invento, that institution can contribute to Debian by simply organizing sprint, organizing meetings where people meet and stay together and act on whatever they want as long as it is Debian related. And I think this has been a great idea, a wonderful way to contribute to Debian, and I think it has also taught us how beneficial those kind of activities can be for us. They've been doing that for three years and then in 2008 they sort of stopped organizing that. The sprint program is something I've done in October 2010. It's by no means something which has invented the notion of sprint in Debian. Sprint has always existed in Debian, but it was just an attempt to streamline a bit the procedure to have a sprint, make it clear what you should do if you want to have a sprint, and as a side effect of that encouraging having more sprint in Debian, and also a way of learning from other free software projects how they are doing things and try to improve what we are doing by looking at what others are doing. In particular I've been in touch with the GNOMI people and with the KDE people to actually share some best practices on sprint organization. So all the material related to sprints is on the wiki at wiki.debian.org.sprints. There is a list of sprints you've been doing because I think it's important to show to people which donate their money to Debian how we use the money. And you also find pointers to a couple of documents.  At that point you still don't know if your sprint is going to happen or not, and when you have a tentative budget you go to the DPL, you say, OK, this is our agenda, this is what we want to do when or is planning to come, and this is how much it will cost to Debian. So I stress the point that this Debian cost because some sprints might have a sponsor, so you need DPL authorization essentially only if you want to use Debian money, and at that point either you get approval or you get a refusal. I think I've approved every single sprint that people have asked me, so the chances that yours will be approved are pretty high. And at that point, well, you add a wiki page under wiki Debian auger sprints using the nice template, which is there, you announce the sprint, this is very important, I think it's fundamental when we use money that we are transparent and that when we do work in a sprint, we do all we can not to cut off people who could not attend the sprint. So announcing that there is a sprint and maybe explaining how people could participate remotely is a fundamental step in having a sprint. You have the sprint, you have fun, at the end you prepare a report, you send a minute somewhere, ideally it's the most appropriate mailing list for your needs, might be project for something general, might be your team list for something specific to a team, and at that one, once all this is done, you ask for reimbursement. This point is put at the last on purpose, because ideally it was a way to first you be your public, first you announce everything, you send the minutes and then you ask for the reimbursement. So this is how you do that and probably the most important message of this buff is you can have a sprint too. So it's not only for core teams, it's for every group of people in Debian, which is willing to work together for a couple of days or a week or whatever, is willing to be transparent about that and try to work with people who cannot attend, and really is for every kind of possible team or group of people that we might have in Debian. This is a brief report that I have also blocked a few days ago about the sprint we have had since April 2010. I go back only to that, but essentially it's the moment in which people started asking me if they can have a sprint or not, so I didn't manage to go through, I didn't have the time to go through the archive and look past that. But still you can see from this that in 16 months we have had 15 sprints, all of them in Europe, about half of them in Germany, that's surely because we have a very active community and also because we have some facilities in German which are really friendly to us, like the Linux Hotel, I think, which is very friendly and a welcome place for sprints. The number of participants varied a lot, so we have had sprints with 25 people, but kind of weird because those sprints are those where we have also had external sponsors, so most of those people are not necessarily people coming on behalf of Debian, but maybe by other entities interested in Debian. We have had sprints which cost us nothing because external sponsors came in and decided that they were willing to sponsor sprints, and all of this has costed something like 10,000 euro, so I have normalized the cost in Europe where they were not in Europe, like for instance Pound in UK, but this is the cost, so essentially a bit more than one here of sprints costed to Debian 10,000 euro, so this is the cost which is, I think, pretty low compared with the result that those sprints has produced, and if you look at my blog Post on the Matter, you will find that every one of these sprints is linked to a report in which you can say, you can see the agenda, the announcement and the minutes, so you can track what I've been doing in the value sprints and compare that to the price. So this is for the sprints, and sprints is just one of the ways we use money for. So there are other important information about money that I feel we are not always aware of, so just to stress a point which has already been made in the previous talk, Debian by itself does not have any money because Debian for the legal world sort of doesn't exist, so it is not a legal entity which can hold money, so all the money that Debian has are actually money which are hosted on the alpha of Debian by the trusted organization, what we call trusted organizations, so this is explicitly mentioned in the constitution. All trusted organizations are equal, so we use to have a special casing for SPI and then we generalize that with our vote some years ago. Even though we use some trusted organization more than others, in particularly most of the money we use and we deal with are in SPI in the US and in FFIS in Germany. Money come in via donations and donation goes to those trusted organizations and are used, the decision of how to use the money is the decision done by the DPL in consultation with the developers, so I have no problem admitting that I have not been particularly good in doing this in consultation with the developers, it seems to me that we have a tradition that the DPL decides which is can be a fine interpretation of the constitution as long as we have good method for reporting to developers how we use money. And this is exactly why I'm very much interested in the work that the auditors can do because I really think we need to be more transparent in how we use the money and also on how the DPL decides how to use the money. So how much do we have? At present we have $55,000 U.S. dollar air market for Debian at SPI. This includes also the Debconf air market at SPI because during Debconf we decide to have a separate air market to make dealing with money easier but they are all the same money so Debconf money is also Debian money and we have 76,000 euro at FFIS. If you do the conversion today that's something like 100,000 euro. Unfortunately, it's not necessarily the spending power we have because as you might have heard in previous talk of this money we can have money which has already been pledged for specific purposes but not yet paid. So there is some degree of uncertainty and that is something we should work on to improve and this is again something we are going to work on with the auditors. But the ballpark numbers are like this. So what do we use money for? So even though a very important line in the Debian yearly budget is Debconf, that's not actually something we use money for. Better, we use money for Debconf but over the years is a sort of amortized euro cost. This is a goal we have set this year in discussion with among the Debconf team and myself but it's also something which has actually happened over the past 3-4 Debconfs. So if you look at the budget of Debconf you have some here in which Debconf is particularly expensive so we spend more money than what the sponsor give us but in other years they are particularly cheap so we get more money from the sponsor than what we actually spend. So if you take this it balances out very well and we have set out as a goal that of having Debconf completely amortized zero cost event over the years. So this is not one of the things we use money for at least ideally. We have money for travel sponsoring Sprint is a big line on that front but we also sponsor developers going to specific events when they go there as a representative of Debian. So that does not mean that you can come to Debian and ask for the first them tickets or for whatever event you regularly attend. This is when people invite us to be present at some event and when they are not willing to pay the trip themselves it is important for Debian to be there. So it has happened to me to authorize travel reimbursement for this kind of cases. And also we have some special purpose Debconf related sponsoring for instance you might have heard of the Debconf newbies initiative this is something we do on outside of the Debconf budget but still I believe there is quite some value into it. This is probably the biggest line in our budget probably again because we are trying to have a report with the auditors but we don't have them yet. The second big line is DSA hardware so we need to buy machine we need to replace machines sometimes we are able to get donated material sometimes we are not so we go out and buy material and also we have some hardware related services I've mentioned only warranties here but there might be more services to maintain the hardware current. Then we also use money to actually buy hardware for these. This is something I've been trying to advertise a bit it's not happening very often actually it has never happened in the last one year and a half at least but it's something we could do so if you want to account some specific hardware doing porting for instance you can and you cannot afford yourself the hardware you can come to me and say okay need to buy this hardware for this reason and what I usually reply is okay first we see if we can get it donated to you by the other vendor then we can check out why not we can actually buy the hardware and then there are probably other stuff which I forgot and which will come up in the discussion last two information there are a couple of sort of documents I'm trying to write and maintain one is sponsoring guidelines which is what I expect from you if you are going to ask for money and the principle is simple be transparent so if you are going to an event that you are going there and to report back before you ask for reimbursement once more the idea is being transparent so you are going there on money which has been donated to Debian so it's normal to expect it to be transparent I mean you have been a Debian representative so once more the project expects you to be transparent on what you have done and the second document asking for money is essentially the kind of things you can ask money for so what I've told in the previous slide if you don't remember the URL go to the Wiki go to the Teams list and there is a sort of fake team which is the DPL team made by myself and you can find it there so that's about it for the info I wanted to share and what I would like to discuss with you and in particular what I need your input on is the topics you can find here so what should we use Debian money for what else should we use Debian money for which minimum amount of Debian money should we keep around for instance if one day half of the hardware we have breaks down in the same minute we need some money to actually pay back that hardware so what is the safeguard you think we should keep in the specific case of sprints what can we do to have more sprints I think we should have more sprints so the KD project has a budget of which is like 10 or 20 times our budget for sprints and there are big software development project but I think the project the size of Debian could use having more sprints and in turn having more sprints might encourage more donation and actually as Martin would say increase the cash flow of Debian which is good if we know how to use the money properly and similarly what can we do to attract more donations let's assume that next year we have 10 times the sprint we have had this year we will need some money to prepare and correct to do for Debian to actually attract more donations so that's it from my side and I welcome your input Martin here please note down on gobby what people are gonna say it's really needed and helpful and stand up okay I just have a very quick question which might be easy to answer sprints and Debian there's not that much of a difference why are we keeping them separate still that's a good question not that easy to answer so one reason I can imagine is that we have a tradition of gathering sponsor for Debian which I think is something which is fairly easy to do while gathering sponsor for individual sprints is not that easy I think but yes I mean there are one of the small side, one of the big size of essentially the same thing so I agree with you I think in the past we have not looked at sprints as some sort of first class citizen so something that used to happen but not really streamlined or organized in any way but yes why not probably also we don't need a big team to organize sprints I've been doing that myself I'm looking for someone to take over the organizational sprints but we don't need a big team for sprints for instance I'm basically just wondering because after every DEBCON we either have a deficit or we have more money left over and as far as I understand that has always been that stayed in Brazil for a long time and then it stayed in Edinburgh for a long time and it was always difficult and we didn't consolidate it back into Debian and we didn't in cases where people weren't able to get sponsorship but we just simply didn't have enough money just get money from Debian and I think we might want to because this is just the biggest sprint that we have Do you want to take on this one more? Well, I think that's to some extent a fixed issue as of the last year of those discussions So the issue is sort of fixed saying that with the general goal that DEBCON is a zero cost event over time we fork off a DEBCON budget at the first time we need to and we merge the budget into proper DEBCON budget at the end but regarding the fact that we keep money in different places we actually benefit from them with sprints for instance, if we have sprints in the UK we ask Debian UK to do their embrosement that's fine And as far as I understood the Debian auditors are keeping track of the money anyway we are still keeping the money together as Debian project Correct So what more can we do to actually use our money to benefit the Debian project or any other input you might have of course take nothing some investment on stock options maybe Martin I do have a general question in terms of how is that money currently invested in just liquidity? I hope so so I trust the from SPI I see the reports I hope it's just checkings and not stock options I'm asking because we are seeing inflation on the rise you want to do something about it You're right I think we are not spending money on stock options and so on it's money held in trust and as I said we would violate against US policies as far as I understood Yeah, that's right as I certainly understand from SPI's point of view they do have a couple of accounts one's a standard a check-in account and one's a savings account so there is an attempt to maximize the investments while still keeping that there's been an issue in that traditionally Debian receives a lot of in kind donations as well so traditionally if you just received some money you'd have to spend a lot more on hardware you'd have to spend more on hosting and we get quite a bit of that one of the things that's been mentioned in the past is getting legal advice on contentious things things like the patents or things like what we can do with things like legal or not fortunately we do have SFLC who's a sponsoring organization of us so we can get quite a bit like that while I'm stood up I'll just mention the second point which is as well as the minimum amount of Debian money we should keep I'd also considered the maximum amount of Debian money we should keep and while I was on the board of SPI this is for two reasons firstly if you've got a lot of money for SPI it is a non profit organization and it's not meant to make a profit and if the amount of money it keeps getting keeps going up there's a problem there the second one is that people who donate to Debian expect it to be used for Debian not to sit in a bank account so it can be very useful to spend it traditionally there's always been the question of what if we get sued and I agree with BDL here if it happens that we get sued Debian has never asked the public for money in a big way before so if this unfortunate situation does happen I'm fairly confident we could raise a lot of money very quickly to do that so I'd certainly be interested in looking at spending of the money we already have so I completely agree with that so I'm not in particular afraid of not having enough money the day we will need them regarding the you made a point sort of our responsibility for the organization like SPI so I've been discussing this point with BDL and also with SFLC which happens to be the legal consultant of both SPI and in some way also the director of Debian and they both make a good point that SPI make these sort of risk assessments in the moment they accept a project so I think SPI as accepting Debian as a project as some sort of assessment of our risk it is to have Debian as a project and I don't think we should hold back in taking decision ourselves unless they tell to us no please stop this is dangerous for us so either you stop or you go away so I don't think we should be over concerned about that and about the specific fear of having too much money I think what we have right now it's ridiculously low for someone who want to sue SPI for the advantage of that but yes the point you made of using having received donated money and sort of having to use them I completely agree with that From DSA point of view if we are talking about taking over more Debian.net services to Debian.org machines we will need more hardware in future and especially server hardware professional server hardware we are speaking about something like 6.000, 8.000 euros per server which then can help several virtual machines which we are currently doing for the new machines anyway so I'm curious how would people feel about going the Wikipedia way of having periodic banner saying please donate to us so who would be in favor of that who would be against that Ashish can you motivate I'm curious I'm in favor of it if we actually have some use for the money it seems like we have I guess I have to keep standing it seems like we aren't in desperate need of money but at the moments when we are I think that doing that to the frontpadeofdebian.org would be valuable but I actually think that the giant Wikipedia donate banner could have had an even bigger CD of the download banner that would probably be at least as useful for the project can someone note down this stuff in the gobby document well I think in part the opposition for many of us to this idea is because we have done this when we need this we usually don't need it but we have for example this specific donate to the conf banner it's right now there but it doesn't have to be there the whole time and it's as unobtrusive as it can be actually it is not donate to debconf it's just a link to the debconf website and on the debconf website you have a call for donors right you have to go through a second page yeah but at several points in the past many of us have to think on a way to get sponsors and we have made this click and pledge and similar ideas but we usually don't need this don't need anything like that for debian as a whole debian doesn't need more money than what it has actually no click and pledge is very often to donate to debian and the substantial amount of that money you see there comes from click and pledge but you have a point so the fact that you think it is the case it clearly means that we have a problem in showing how we are using money so I think that's a very good point but we do use money and we do receive quite some donations for instance of those 100,000 euros we have received in last year at least something like $30,000 of donations this is a couple of sometimes actually I can remember very well but we do receive money via those channels and we use them but we don't need the money I mean that we usually can get it in many ways that are not something that gets in front of the people what really bothered me about Wikipedia I have to block all the banners from there because they were really obnoxious I think that if we actually start to publish the information that we have the financial information which we are going to do as part of this auditing process that a company sees who wants to sponsor Debian because they use Debian and it sees that we have 200,000 euros in our account is going to think twice about how much money we actually need and might not donate anything because 200,000 euros is a lot of money what we I think need to think of first is how to reduce that money in the greatest way possible how to spend all of that money in the minimum on the other hand I'd be tempted to say that minimum can be really low because if actually a machine goes down and we are in desperate need I'm pretty sure that between all of us we're going to come up with the funds to re-select that machine and even if it's only on a low basis so I don't think we're going to have liquidity problems for such small issues but on the other hand so that says that we managed to go through 190,000 euros of those 200,000 in a year and here's what we did 25 sprints and Debian for 600 people and we supported this other upstart of a project then a potential donor is going to feel rather positive about giving money to that project in my opinion may I directly answer to that we ask for machines for example for snapshot Debian org and well, directly on the Debian news mailing list and answers we got where you can have that desktop sort of machine we have we have certain criterias as DSA, we want to have out of band access to machines in case hardware goes we do a kernel upgrade something breaks most of us we get hardware donations I am on the hardware donations alias is more or less desktop related hardware what's the minimum liquidity what's the minimum liquidity you want to have I think you're applying to two different points so what you're saying is that the day we need we will able to find the money while you're applying to a point that the day we need hardware we will get the hardware for free which is not quite the same thing it took us more or less half a year quarter of a year to get acceptable hardware for snapshot Debian org so this point from DSA is essentially that it's easier it's quite difficult to get donated the right hardware we need while I agree with you that if we go ask for money we'll probably get quite easily them for the hardware I agree but this is actually another point of using money providing statement of how we use the money to actually gather some I just want to respond to something that Martin just said where he said if a company sees that we have some whole bunch of euro in our bank account they might think twice about donating with that I quasi disagree with the next part you said I totally agree which is if we say and we spend 190,000 euro in a year and here's a beautiful document we produced that says that we really spent it on things that are cool then people will give us money I just want to emphasize that having money in the bank account I don't think it's realistically disincentive like having worked at some millions of dollar nonprofits and that's not the problem showing you can spend it is the problem it's not what I was trying to suggest that if there's 200,000 in the account this year and next year it's 205,000 and then it's 210,000 and we don't actually do anything we don't actually have any cash flow report with what we've been doing with that money then the company we can summarize that by saying that only saying we have that money in the banks would not look good but when that money is very low compared to the cash flow it would not be a problem Martin, anything else? I guess the question is how can we spend more money for instance you mentioned pledging for this other project which is something that historically don't feel particularly good at because they think that people who donates to Debian wants that money to be used in Debian and not to sponsor external project so this is what I've been replying to a couple of requests in that direction I think a good way to spend money is helping boost people or event people getting appropriate banners real banners not website banners merchandise material and so on which we which later on like when we print t-shirts we get that money back anyway I agree and I've been very happy to give money to the events people and actually also pushing them to do something like the event box which will have some cost but it's something that we can go to a booth look some sort of professional or at least not 20 years in the past or something like that so yes I agree there is no suggestion on specific specific things you might buy to actually improve our booth or actually improve our merchandise in general because as an idea I think we all agree on that but when it comes to you know this is the plan, this is the expected budget it will cost please say yes or no and arriving at that step from my point of view is not that easy I have an idea maybe I mean I'm gonna be shot down in a second after this incredibly successful dunk tank experiment that we've had how do I could think of a number of things that need to be done in our project which are not particularly exciting is our project ever going to think that it's acceptable for us to hire someone for I'll put it as administrative task and one of the things when we talked about earlier was one person that is there to organize your sprint for instance not a particularly geeky thing not particularly awesome but maybe one person that it could be awesome everything is awesome if you do it for free software can I just have a quick show of hands who is in favor of considering such an idea and who is absolutely against it I have a complex answer but Ganev is first Ganev leaving out the point if you are against or before it if we are ever going to hire a person we need to be very careful how we are doing it and need to ask SPI if they are actually able to do it because there are some special rules for non-profit organizations and we need to follow them exactly so on that fund there are examples of free software projects that have been hiring people for administrative tasks for instance the example I made with Martin before was the KDEV people which as far as I know I've hired only one person and she's indeed the person which is organizing the sprint the other example I'm aware of is the Gnomi Foundation I think that the executive director the Gnomi Board is hired and paid by the Gnomi Foundation so my personal take on that is that at the moment I consider a bit of a failure that as a community we are not able to attract volunteers working also on non-packaging stuff and I think we should be able to attract people which are enthusiast about Debian even if they are not computer geeks and which they like doing management stuff it's not easy I think we are not doing a good job at that and I think we should try but we should also at some point be ready to say okay you know what we have been trying for two years it's not working so what do we do what do we do either we accept that we don't have any people able voluntarily to do management or we do not accept that and we go as Martin suggested well on the other hand if we cannot attract people doing that for free we should do that I disagree I mean we are able to attract packaging contribution for free by people who are doing packaging in their own work life why shouldn't be able to attract management people which does management in their life you agree yeah you just said the same thing oh sorry I was just gonna make the point that yes you say we might have some job we haven't found someone for two years but before we give up and hire someone to do that you can also consider making the same amount of effort as it would take to hire someone in actively finding someone as in not just a mailing list post somewhere that says we're looking for it but if you imagine all the effort would take to hire someone and the processes and the interviewing and so on if you did a fraction of that there's a good chance you find a volunteer and obviously things like the sprints and so on again well I'm not necessarily saying everything should be put into one big team it might destroy things a lot of the debconf work is pretty similar and we have a lot of volunteers who want to do that that's true another idea that we had during lunch earlier was that rather than hiring an accountant or someone sorry I didn't mean to say accountant someone for a job such as the one I suggested earlier can we maybe use money to bootstrap teams and one of the teams that we were talking over lunch today that was with Penny after the Debian women stuff is for instance it seemed that wasn't there but it seemed that what was needed was some sort of like person that knows where manpower or women power is needed in the project and can then like match make project, newbie and mentor and I think this is a beautiful job for volunteers to do but it also seems like it's a fantastic task to do like just start so we could have a sprint obviously and start these things as a sprint or we could potentially take money and throw it at someone who has experience in this area for six months with the explicit goal and here I'm thinking of Debian installer and Debian edgy and all these projects that have been funded or where people have been funded with a specific goal to bootstrap a team not to do the work but to bootstrap the team yeah, of course there is a potential issue that once you do start paying someone for doing admin task or going out and being the people who know where to find the manpower womanpower whatever it's incredibly difficult then to go back away from doing that the very point when you start paying somebody to do admin work we will never find volunteers for admin work anymore they will be expecting to be paid in just the same way Paul there is a question from common way Paul I think a more fruitful approach is possibly instead of Debian hiring people directly try and find Debian funders donators who I mean there is one organisation when we have somebody from another organisation who works half day a week for us that solves all the problems with employment and if that ceases to be a donation in kind from that company then that possibly avoids the situation that Steve is because that person for the duration is not actually an administrative or Debian it's either a contribution or somebody who is being contracted in kind as well so my take on this is that so I've been in another volunteer organisation where in the beginning they were completely volunteer based and they decided to hire someone not related to computer science at all and my very tiny experience in that front is that you have a problem when you have side by side people doing the same thing someone paid and someone not paid to some extent we already have this problem in Debian because there are people which are lucky enough to be paid to also work on Debian but it's a bit different at least emotionally when also actually conceptually when it is the project itself so my personal bar on that would be in an area where we have always had volunteers well you should not put someone else which is paid to do the same at least not paid by the community of volunteers which will stay side by side with them if you are going to have entirely new area like for instance management or auditing or management or whatever this problem seems to exist but still I would personally consider it a failure because Debian is such a big project such a sort of society in which I hope we can attract volunteers working on everything the society itself needs but I would put the barrier in if it's something completely new well maybe if it's something we have always been doing in volunteer basis well no but that's a very personal take not necessarily representative of all of us just gonna say as well in terms of that volunteers and people working together it's not just that it demotivates the volunteers and they get fed up it also happens the other way around that the people who are in a paid position can feel very threatened that there are volunteers trying to take away their job from them and actually end up in a kind of political infighting with the volunteer people trying to stop the volunteers from doing work so that they justify their own paid existence well and the reason I raised my hand to have when Martin asked about this is that when the dunk tank experiment was made we were in a moment of crisis because we were at the hardest release cycle we faced and well yes, things were going very bad for the project as a whole and I think that was like a desperate maneuver to try to get things back on track that it worked partially it failed partially, yes it can be seen different ways but the thing is right now we are arguing about a completely hypothetical situation maybe you will correct me but I don't think we have any need of paid work right now the most boring tasks for some people are being carried out with passion by other people who find them interesting so I don't feel right now we have shortage of voluntary work well, if we have companies willing to pay someone with in Debian for doing a specific task in Debian like we already had I think with Debian installer parts of the Debian installer I'm completely fine with that if a company said I want this extension or this whatever in Debian as a Debian developer for that that's perfectly fine but I think we should not spend Debian assets on hiring persons within Debian I would like to mention that maybe hiring people is not a good idea but it's still interesting to consider how we can use money to bring some project to completion quicker, quickly I mean, for instance right now you have Tolef who is working on tool to convert system.dnit.config file to ccinit script is doing this on spare time it's surely going to take a lot of time maybe if we could say we're going to cover your living cost for a few weeks so that you can spend more time on this we could give this short you know, well more quickly than otherwise and I'm sure many people would love to use this money to solve this problematic discussion or should we have system there when we can have both with a bit of work but this work is not happening quickly enough I know there's not much time left that does sound incredibly like dunk tank a project which we need to complete more quickly like a release and it was meant to be covering two people's living costs for two months I think so we can get the release out I know we don't certainly have as many flame wars anymore and maybe we miss them and want to try and have more again but I'm not entirely sure if that would work another thing we can do which we haven't done in the past is advertise and recruit advertise and recruit actively, we haven't really issued press release and saying we need people who will do this please come and join the Debian project and really push for that it's all been fairly organic so that may be a way of attracting those people who we haven't had before so Raphael knows that we have debated quite often and I disagree with that, I think it's not worth even if we only consider the side effect of the huge debate that we create which I think is not a debate worth having even only that would not make it worth but besides even if I put it aside even in that model even if you're not hiring someone and actually what the other open source project are doing when they actually hire people they do not hire, they do exactly as you said so they contact them for six months but that does not solve the issue of people working side by side one volunteer and one paid so sorry time is up so thanks a lot for your input


Welcome in to go Mustangsports.com post game interview with women's ice hockey head coach Tori M off after the Mustangs fall To nothing to end the cot coach. You guys match them stride for stride your overall thoughts on the night tonight Um, we need to show up and play full 60 our first period heard us You know, we came out a little bit flatter than we would have liked picked it up in the second And then that one minute of terror and the third Was not fun for us, but really we came back hard We never gave up even in those last few minutes when we pulled the goalie We were going hard and that's all I can ask But the difference in this game was endicott capitalized on their chances and we didn't Annika had a really good night between the pipes tonight She did and she's been playing great all season and so has Annie and our goalies have just been giving us more than we Could ask for so we're very happy, you know with the net minding It's just taking care of you know putting pucks in the back of their net I have to imagine is it as a first-year head coach a weekend like this against endicott Which of course you didn't make this year schedule, but it's almost like a heat check weekend Almost like a status check on where your team is. We've been saying it all week. Um, you know, it's really going to be a test to see if We are where we think we are So losing this game was definitely tough for us as a team We really wanted to win this to kind of prove to ourselves We've made the strides we need to to be the team we're trying to be Um, we just fell a little bit short today All right. Well, you get one more chance tomorrow before a big long break. So go get them tomorrow and uh, good luck tomorrow. Thanks paul


That's what I'm talking about over here. Good afternoon, I'm Sergeant Benjamin Miller. This conversation has been exciting thus far, and it's been testing me pretty well. I'm learning a lot, and I just know that we don't know everything, but we're out here to get better and train. Go, let's go, man. Gotta move faster, boss is present. Hand-flat back. As he's breathing out, he's breathing out. Shields on. Shields on. Blade leading is controlled. What's that? Blood on the chest. Check face on. See one? I like serving the Army because I like to value customer service. Prior to joining, I worked at a restaurant, and I loved the interaction with all different kinds of people every day. Although the job was the same, I met different people, and it was fun. So I decided to join the Army because coming out of high school, I didn't know what I wanted to do, and my thought was I'd use it as a stepping stone in my floor, get my GI bill, then get out, but here I am still four years late, and I just re-unlisted last year for another five, so something must have gone right, and I'm enjoying it so far. I enjoy serving because every day brings something different, and I am learning new things literally every day that I can take out into the civilian world when that time comes around to be competitive and getting paid while everyone else goes to college and pays for that experience. I'm just getting it every day for free. Basically, I always had a passion to be in the military because I wanted something that's going to challenge me. I wanted something that's going to push me and make me better, and that was the main reason why I decided to join the first place. Huh? You're going to get caught in that obstacle. Good thing. Halfway you start thinking, like, start humbling yourself. Try to figure out how to get to the end, and that's the goal. Just got to put one foot in front of the other. Yep. Cramp in. Cramp in, but just keep going.


Now, OK, with that public service enhancement, we'll get things kicked off. My name is Ray Pake. I manage the code contributor program at GitLab. And welcome to, it's hard to believe, I'm saying this sixth edition of our quarterly hackathon. So last hackathon of the year. Excited to see the continued growth. So David Planella and I will be giving you a quick overview of the hackathon. We'll go through some slides. But if you have any questions, feel free to stop us. Either you can voice your questions verbally on the call or type it in the chat window. So we'll answer it in the real time rather than having to wait till the end. So quick introductions. So let me go into a full screen mode so hopefully you can see this better. So again, I'm Ray. I'm based in California. So you can see my Twitter and GitLab handles there. And David, I'll let you introduce you to the attendees as well. Hi, everyone. I'm David. I've got the privilege of working with Ray and other program managers in the community relations team. I'm based in Europe, in Cologne, in Germany. So feel free to ping me if I can help with anything during the hackathon if Ray's still about to start his day. Yeah, so I think we have like a good coverage being in two different continents. So any questions you have, just feel free to ping both of us. One of us should be up and around, be able to answer your questions. So thank you, David. So I'll quickly go through the agenda. I mean, if you've been participated in past hackathon or listened to previous recordings, the agenda should look pretty familiar. We'll do a quick reminder on the community code of conduct. This is something we do at all of our events, whether it's for shoulder, face to face, and we'll go through logistics and detail items on the hackathon real quickly. And like I said, you don't need to wait until the end of the session for Q&A. So feel free to stop us if you have any questions. So on community code of conduct, like all good open source project, we do have a code of conduct to make sure that we have an open and welcoming environment for everybody in the community. So I'm not gonna go through the full text of the code of conduct, but you have a link there that you can visit. I mean, we never had any instances that during the hackathon, we definitely wanna keep it that way. But even during or even outside of the hackathon, if you have any concerns or see something inappropriate, feel free to send an email to aliasconduct.gitlab.com and that email actually comes to me and David. So if there are any concerns that we need to address, we'll jump on it right away. But I mean, this is again, I mean, there haven't been any issues here. I don't wanna raise any concerns, but each time we have events, whether it's virtual or face-to-face is a good time to sort of remind community members of our code of conduct that we wanna adhere to. So moving on, a couple of slides on logistics. Obviously, we're doing a kickoff session right now. In about 40 hours, we'll have a wrap up session like a 2,300 UTC on the 14th. And in between those kickoff and wrap up sessions, we have a number of exciting tutorial sessions scheduled. We have speakers lined up for GitLab GL or replication GitLab managed stage, Multano. Not sure everyone's familiar with Multano, but if you're interested in data analytics or if you're even data scientist, I mean, that's something that you probably wanna listen to and watch recordings of. I mean, that's been gone through a lot of evolution over the past four quarters. So we're pretty excited about that session there. And then we also have a couple of speakers to talk about our new GitLab Heroes program or initiative that you probably wanna listen to. If you happen to miss any of these sessions, the recordings will be posted on our playlist. And feel free to check them out there. I usually try to post them within 30 or 45 minutes of session being over, so you should be able to find them there.  That's where you'll find, I mean, not just me and David, but a lot of our contributors sort of being present there. A lot of questions and answer that gets resolved. I mean, even I wake up in the morning, I'll go to the Gitter channel and I'll note that the question's been asked and it's already been addressed by somebody else in the community, which is great to see. So it's a great resource. So I encourage you to check that out in terms of support and network, even networking with other community members. I'll move right along quickly. I just wanted to show you the Gitter channel if you haven't checked it out yet. Last time I checked, we're well over 360 people that are part of that channel. I remember with our first hackathon, little over a year ago, we had like less than 50 people on that channel. So we've seen enormous growth over the past year or so. And then if you need to individually like ping us, let me feel free to ping like David or myself, Deeplanella or Arpeg. You can also do like a direct messaging or individual conversations. So that's a good way to get our attention. And then you don't need to even create a separate account or log in. You can just use your existing GitLab ID to log in. So it should be pretty straightforward and simple. But it's like I said, it's a great resource and I encourage everybody to check it out if you haven't done so before. And before I pause for a minute, just wanted to show you all these speakers that we have lined up for tutorials. Like I said, we have speakers for GEO, The Managed Stage, Meltano and GitLab Heroes. So Fabian Zimmer, he's a product manager for GEO. He'll be, he might actually be doing this with another coworker of ours, Tom and the GEO team on the engineering side. So we're looking forward to that. And then you may have seen, if you checked out past videos, you may have seen videos on the Managed Stage, but there's been a lot of changes on Managed Stage with several different new groups that are underneath it. So the group manager for Managed Jeremy will be there along with Garcia who's on the engineering side of things. So there'll be the two speakers and on Meltano, Yanis, I mean, he's got slides which is already posted on the Hackathon page, but he's also gonna do a live demo, which David and I have seen at GitLab Commit in London about a month ago. So I encourage you to check that out. And obviously a lot of you folks that are listening in or watching this recording, a lot of you have contributed to GitLab through code, but John and Emily will talk about other ways that you can contribute to GitLab, whether it's like a speaking at events about GitLab or writing blog posts and various posts on GitLab as well. So I'm excited to have both Emily and John come talk about, not only give you an overview of the heroes program, but resources that are available that we offer to the heroes. So you'll see the various time zones for the sessions there, but if you happen to miss them because of the time zone issues, I mean, watch the live stream, I'm sorry, watch the recordings later on. I'm gonna pause here. I think I spoke a little too much or a little too fast as well, but let me pause here. I mean, David, did I miss anything here or like anything else that's worth pointing out? No, I think that's great. I think one, perhaps one thing to, and I think you're going into this in the rest of the presentation, but feel free to check out the, if you're interested to see the progress of the Hackathon, feel free to check out the Hackathon page on about.gitlab.com slash community slash hackathon where you'll be able to see live how many measures were submitted. It's a way to see which things people are working on and how well we're doing in terms of comparing it with the activity with the previous one. It's a fun thing to watch as well, so I tend to do it quite often. Yep, cool. All right, thanks. Okay, so moving right along. So merge MRs and prizes. So a couple of things we wanna mention on the MRs. When you submit an MR during the Hackathon and me, feel free to mention me and David so we can add a Hackathon label to the MR. I mean, I'll talk about this in a minute. People in the APAC region got an early start on the Hackathon and the way I found out about their MRs were that typically, they either mentioned me on the merger quest or the other way that happened for this Hackathon was that somebody just pinged me on Gitter and said, hey, Ray, I just submitted an MR and it's for the Hackathon. So please try to grab our attention. And then the Hackathon MRs, like David was saying, the counter will be on the main Hackathon page. It'll be up in a few minutes. And then if you wanna see an individual list of them, you'll actually see it here. So I'm gonna go off full screen for a minute. So we, I mean, believe it or not, we already had like a 14 MRs that's been submitted so far, which is amazing. So yeah, and then four of them have already been merged, which is cool. I mean, a couple of these were, I mean, three of these were like a documentation fixes that I was able to merge by myself. But yeah, so they'll all be listed here after we add the Hackathon labels. So I mean, please feel free to just ping us when you submit an MR. So let me get back to the slides here. Nope, sorry. Yeah, and prizes. So there are, as we've done in the past, like a two or three quarters at least, there'll be three categories of prizes. Like anybody who has MRs merged by the deadline, I'll talk about it in a minute, we'll receive a prize. And there'll be a grand prize for individual with the most MRs merged by, I mean, November 25th, basically. But we also have a category for the second place winner. So I'll go over the prize in a minute. You may have seen it on the Hackathon page. So this worked out pretty well. And for second prize and the Merge MR prize, we were able to get a customized prize that's not available on the GitLab shop. So hopefully you'll enjoy that. So on the MRs, so in terms of submitting an MR, like we didn't want to do anything like unnatural for community members. Like we didn't want you to have to think about like which time zone that you have to time your MRs in. Like we want to just have you continue to work in your own time zone that you're in and you're comfortable in. So when you submit your MRs in the 13th or 14th, just do it in your own time zone, like whatever hours that you work. So I mean, what happened was that person in India just created something like shortly after midnight on November 13th and just ping me on Gitter, which is fine. So any window, any 48 hour window between 13th and 14th in your time zone is completely okay with submitting an MR. But we're gonna have a strict deadline when it must be merged by based on the UTC time zone. So 2300 UTC on November 25th. So you'll have roughly about 10 or 11 days after you submit your MRs to get them merged. I mean, if you have any issues for whatever reason, the review is not happening quickly enough or there are any like a tooling issues or whatever issues that you run into. If you feel like you may need additional time for your hackathon MR, just let me know. And we'll definitely look into it. And I'm happy to make any exceptions if it's reasonable. But I've just let us know at a time, but we'll be sending out reminders through various social channels to have your MRs merged by November 25th. And the winners will be notified via an issue. And if you go to the hackathon project and you'll probably be able to find the issues from the previous editions of hackathons, you'll probably, you'll get a chance to see how we announced winners in the past. But shortly after 25th, I'll create an issue with the list of the winners. So I think that's that. And then yeah, in terms of prizes. So the grand prize basically you get to spend $100 at the GitLab store, which has been very popular.  And the second place winner is, I mean, they call this a music box, but it's pretty cool. It basically is a Bluetooth earbud plus a speaker with a nice GitLab design there. It looks pretty nice. And people, everyone with the MergeMR is, they call it a tech organizer.  So on the flip side of things, you should be able to put your tablet in there in this trap. So hopefully you'll get to enjoy it. And again, that's, you know, it's got to, we customize it with the GitLab logo. So cool. And those are their prizes. And just wanted to go quickly over the stats. I mean, in Q3, I mean, about three months ago, I mean, we basically blew past the previous record in terms of the number of MRs that were submitted. So the blue graph shows the number of MRs that were submitted over the two day period. And then, I mean, basically, beat the previous record in Q1 of 2019 by like almost 50%. And people had questions about how many MergeMRs were typically needed for the grand prize. So it ranged from between seven to 13. But yeah, so just wanted to give you a sense as to how many MRs were required to win the grand prize. So hopefully they'll give you an idea. Obviously, you know, want to see the continued growth in the number of MRs. And it'll be awesome to cross a hundred threshold in terms of MRs. I think there'll be a great accomplishment. But we're already 14, that's in.  So I'm pretty optimistic. I think there may be a question. Let me see. How many people participate? Yeah, in terms of, I don't remember the number off the top of my head, but in terms of like the winners for the past hackathons, it ranged between like 20 to 30 people that we sent MergeMR awards to. So the number of people that actually participate are probably larger than that. Like there are people who submitted MRs, but didn't win a prize for whatever reason. But hopefully that answers your question. So let me type it in there as well. But so that you can see it. Well, I was, I would highlight also that as he was saying, there's other people that participate, not only submitting MRs, but there's people who are participating on Gitter for instance, helping those who want to submit their first MRs for instance, or those who are commenting on issues, including MergeQuest coaches, which are the team members who help get this MergeQuest merged. So I'd say it's difficult to say for exactly, but let's say, I don't know, if we were to say like 20 to 30 people working on MRs themselves, then perhaps you could add it up to 50 if you include those helping there. Yeah, thanks, David. I'm typing that into the chat window as well so people can see it if they're cool. Okay, so as we've done in the past, we also have like a number of issues that we suggest for a hackathon. And then let me actually go back to this page where we keep track of merged MRs and in this section right above, we have various links with links to suggested issues that people can work on during the hackathon. And well, we also wanted to highlight like a number of engineers and even product managers have labeled certain issues with the label first time contributors. So if you click on this link, like you'll get you to a query with labels accepting merged requests and good for first time contributors. So if you're interested in working on, I mean, first of all, take a look at these list of issues and see if any of these you might be interested in working on and just let us know, like David or I know that you're interested in working on this during the hackathon and we can definitely like assign these issues to you once you submit an MR. So that's one of the things that we want to highlight and there are a number of, what, sorry. There are several other issues here for UI UX. I mean, if you're interested in like working on like a Maven or a container registry, there are a few issues that you can look at as well. Sorry about that. I have a problem with my mouse, but there are also issues that we have like highlighted for more experienced users but do take a look at those. I mean, these are just guidelines if you want to work on something else like an issue that's not on this list or I mean, there may not be an issue that's been opened. I mean, that's completely fine. We accept all contributions, but we just want to give you a guideline or suggest a list that you may want to take a look at if you have a hard time deciding what to work on during the hackathon. Let's move on here. And David like already covered some of these. I mean, during the hackathon, I mean, hopefully David and I can answer most of your questions and we're available when you have an urgent question, but there are other resources. I mean, Gitter, we already talk about like a community members are definitely a good resource. And the Merge Request Coach that David talked about is well, if you're not familiar with who these people are, I mean, there are a couple of links here that you can check out and find out who they are and where they're based. I mean, these are GitLab team members, but they're specifically, I mean, volunteering to help with community contributions. And for whatever reason, if your MR is not getting reviewed in a timely fashion or it just fell through the cracks by even me and David, I mean, feel free to mention like GitLab Merge Request Coaches by typing at gilab-workslashcoaches and then you'll get coaches attention and I'm actually in that group as well.  So that's a good way to ping people if people are not being responsive. And then the final thing, you can also find the appropriate reviewers and maintainers of various GitLab projects by going to this link in the handbook. It's a pretty long list. We probably have like over 300 engineers at GitLab right now, but if you're interested in like, which of the engineers are responsible for which of the stages of GitLab projects, that's a good page to start looking at, although it's pretty long. So I think that's the end of the presentation. David, anything else I may have missed or anything else you want to bring up? I can't think of anything else. I'm really good at doing the contrary. All right, thanks. And yeah, and I'll, any other questions that people want to like ask verbally or like a type on the chat window, I'll give it 30 or 40 more seconds for people to ask questions you may have. I mean, if you happen to like, you forget to ask me a questions if you think of something later, obviously just ping us on Gitter. I'll be happy to answer them as well. Just one more check on any questions or comments. If not, well, thanks for your attention. Happy hacking and I'm sure we'll be seeing you online over the next few days. Thanks very much. Thanks everyone. Everyone, bye-bye. All right then. Thanks a lot. That was really good. Thanks, David. Bye. All right, cheers.


Remember what Carl said? We're made of star stuff. Yeah, I explained it to my lay audiences. Oh, yeah Hydrogen helium at very high temperatures at the center of a star in some galaxy some time or another And then it started to cool down and through various means it turned into heavier elements And those are the heavy elements to this floor on this stage and you and I ourselves are made of yeah We were at the heart of a star in a different form at one time. We are made of star stuff That's a great expression And we got to go back to the stars really. Oh, yeah, we're gonna go to Mars I'm sure that oh not while I'm alive No, not maybe well anyone in this room is alive. Well, we go to Mars Maybe maybe not don't know might be many generations ahead Saturn and Jupiter and Uranus and a no not Neptune's ready. No cold. Whoa far out there Well, maybe one of those moons Europa's starting to look good. Isn't that hey Yeah, I don't know as a summer vacation, but nonetheless, it's looking better and Mars Yeah, we can do that. It'd be nasty, but we can do it cold Yeah, well take some oxygen and water along with us And then we'll see if there's any there that we can get out of the soil. Yeah, we'll do it Not you've not to Venus. Pardon me and Mercury. Whoa hot. Don't want to do that Don't want to melt them before I get there But we will go on to the other planets and we'll go to the stars. Yeah Yeah, I think we all I'm convinced of it. Oh, I wish I could be bottled up right now Brought back maybe 2,000 years in the future and I'll bet we'd be saying yeah We went to the stars. You were right. Mr. Randy. We went to the stars I was 10 years of age. They gave me a choice caves Stars I didn't have a tough time making up my mind. I said right away stars I'm going to the stars ladies and gentlemen. I Invite you to join me. Will you? Thank you for more of James Randy and the educational foundation. Make sure you visit randy.org


How's it going everyone Caleb here with late in sports cards next up tonight box number 81 of the Personals Almanac for Jared P Volume number two here. Yep. That's correct Ari. That is correct This round it was much easier on the site. You're able to just select your box number out of the remaining boxes Here we go 81 so that's also helping us literally just fly through these now. Oh, yeah the last time Yeah, I don't know random ever you were right. Yeah, that was kind of so I watch I wasn't working here. Yeah, I was watching it. Yeah, wow Wow Dynasty auto Vlad Carrero junior two of ten Yo, boom how about that? That is sick Jared P Two of ten as a couple of nice ones in a row there very nice 2021 tops dynasty congrats again two of ten beautiful man. We'll have that right out to you


Alright, this is a review of The Great Influenza, the story of the deadliest pandemic in history by John N. Berry. Scary title, huh? This took seven years to write for him and intended to be much shorter. I'm glad he took the time to write this classic. This is The Great Influenza and Nature's Rage, and I'm talking about the 1918 influenza flu. This disease killed more than war when these dual worlds collided, and anything said in this is not medical advice. Please consult a doctor. I have worked in a hospital so I can pick up on most of the medical terms and a bit of the culture. This book in general is not a history book, it's a cultural and lesson book. The first breakout happened in Haskell, Kansas, for all places. The first cluster, even when it has the nickname the Spanish Flu. And it was a more extreme form, body aches, nosebleeds, pneumonia, which killed most of the people. And the patients termed blue because of the lack of oxygen. They become dark, headaches. And during this whole epidemic, there was a mystery and pressure to find an answer. The plague in general killed one fourth of Europe, this killed 50 million plus around the world. It was a huge outbreak in explosions, speed of the wind, where it was nature versus modern science, and very natural like a wave, or a few waves, not logical. There is balance in the world, and there's new developments, numerical systems, measurement tools, stethoscopes, cholera, and how they found out I was contaminating my water, like typhoid. And they used to prescribe indiscriminately. Imagine that. There was a medical revolution using empiricism, math, Newton's laws, science and achievements. Medical degrees in the United States were easy to get. Europe, on the other hand, had state help to help finance it. The Johns Hopkins Medical College, got a donation in 1893, opened up a new world, a knowledge of not just doing. Science and religion. They didn't have enough supplies back then, equipment or technology, but doing things anyway. There was bleeding to relieve pressure, or they thought it would flabotomy. And it wasn't until 1928 when they had penicillin from antibiotics to help fight bacteria, which was a serious breakthrough, but that was way after this pandemic. And that wasn't even really used till the 1940s. There's a germ theory of disease during this era. William Welch, a teacher and pioneer, had germs in every case, isolated it. See if it's acceptable, or what is susceptible, and isolate away. Just that simple germ theory disease helped out. There's Dr. Koch and tuberculosis, disinfectant. And with Welch being a pioneer, he was free to do extraordinary things that helped advance the movement. And this would help cement the American medical industry. Faculty back then was paid by student fees. Other improvements led to patient care, gloves, and anything to prevent and cure disease, storing blood, linking viruses with cancer, dipheria antitoxins, the Rockefeller Institute. The testing grounds became for labs. There was bureaucratic power, hospitals and government, very important versus truth. And the risk. It cost money for all that. Any reports would hurt morale during a war. Hence why Woodrow never really talked about it. We must win the war. Everywhere is overwhelmed with patience. There are warning systems to public health. Camp Funston, about 1,000 people got sick in the army. It was unpredictable and explosion. An epidemic is local while a pandemic is worldwide. And here's some very basic medical biology and data. Influenza starts in animals. Birds can give track. Pandemics come in waves. Influenza in general kills 60,000 people a year. There's several pandemics a century. Viruses look like a membrane. Influenza enters a cell and binds. So the body has a hard time killing it. It mutates fast in viruses. DNA is hard fixed. RNA not so much. Defenses recognize a foreign antigen and the body reacts. There's immune response, swelling, redness, or fever. The immune system gets stronger. Well, as well as finding vaccines, which can recognize this. An influenza has a protruding mutation. The immune system can't keep pace. Measles antigen are the same. Vaccines take time and there's antigen shift. These connections can be man-to-man. The influenza can transmit and mutate from pigs, from birds to man, then become man-to-man. What's unusual about influenza is it dominates past forms and to get stronger. During bad eras like this, it binds nations together. It was technology in the lab versus the war and disease. What were the troops to do?  The nurses were on short supply in the United States and then just being sent out to war. So there's always a shortage. Doctors could hardly do anything. There was overcrowding, especially in the winter. And pneumonia is an after-effect and not just Adobe. Vaccinations could kill and there was so much effort to prevent pneumonia, the time, money, and efforts. It was nature's rage. It was worrisome to see the disease move from February to March to Kansas and then Spain and May, which was neutral during the war. Who wanted to accept blame but everyone else? Influenza during this time striked violently and fast. The virus changes, there was propaganda, quarantines that proved undisciplined. The second wave of this virus was stronger. It was declared over in August but came back. Don't call it a comeback. They were isolating it and containing people. It was out of control in hope of controlling and overcrowded barracks and mixing. It just didn't work. It occurs at an explosion. Docs were overwhelmed and wouldn't even admit people. Nurses were getting sick, the fear, panic. The virus tests society and the parts supporting it. There's gonna be sacrifices and morale, weak morale. The daily life has altered. In Philadelphia and the United States, they didn't cancel the parade. No, they went ahead and did it and a hundred or more had an influenza. They ignored the health professional advice. It was called the Liberty Loan Parade, a parade for patriotism. And these things had a two or four day incubation period. They did not eliminate crowding. They ran out of ambulances so they used mules and a cart to transfer bodies. It was a shorter supply of getting them. Overwork, disease, there's bribes, queuing, lines. Prisoners were used as gravediggers. Resorts were quiet and it was a time to embrace uncertainty. Interesting times. And at the height of these epidemics, there's a peak death in hospitalization where it just overcrowded and Woodward Wilson took no note of the disease. He must get the victory. No assistance. There's a bureaucracy of military and government sending boys to war and flu. Deal with it now or wait. You could quarantine and then send them on a ship which was packed and this won't remind you of a certain cruise ship. There's excellent leadership in public health but often they're ignored. Doctors and nurses are resourced. Even if they were tired, even if they knew any skill, they would come back or try to urge them to come back. Nurses were harder to find than doctors.  The doctors were ignored by the press. Undertakers were hired to dig up for the bodies. Volunteers didn't want to react with patients. And we could all understand that. It was work or fight or no work. Sick and afraid. It was a time of terror. Reluctance to health. Silence replicated everywhere. And just when they say the epidemic is waning and they said, oh, it's just dry. It was just distressed of words. How to dodge the flu. Don't get scared. All panic. There's no cause for alarm if proper precautions are taken. That is redundant line used everywhere. The news and the headlines, don't get scared. Don't get scared.  They're blaming any enemy for epidemics.  There's a destruction of intimacy from people. Just a casual walk. Fear. Wear a mask if you need spit or cough. Even the dogs might carry. They were slain dogs. Dogs prescribed morphine, codeine, aspirin for the pain or cough. Even heroin. It did not discriminate between the weak and the young. It was like a bully. It killed young adults because their immune response was so strong. And virus was a hunter in cities. Dense cities. And then followed men wherever. The Eskimos story in this is deep. Even when we reached the Eskimos. All strands on the other hand were kept the quarantine out by being stringent for the most part. And the third wave of this virus has psychological and delirium effects. However, it was the second wave that did most of the damage. Most people don't want to speak of this area. You don't hear about this in many books. This affect all class, especially high dense areas. Most governments lost trust because they lied. They lied for the war effort. We don't really know how many people died because the record keeping was not worth it. William Welch and all the doctors they gave up searching, not understanding it. And later on, even after the pandemic, it still carried on till 1930 with the swine flu which came from the 1918 influenza. It still has a lasting effect. Here are some lessons and tips. What can we learn from this? History doesn't necessarily repeat itself but there are cycles. The next pandemic are white swan events and not black swan events. The pandemic comes in waves. There's surveillance. We could see this. John Barry even calls out China as lies in this book concerning other diseases. There's vaccines which takes time. There's nothing worse than rescribing a bad vaccine. Some of the worst are inhaled primary transmissions. It's in the air. You can get it from doorknobs and humidity can help dampen it. People will eventually go void going out, hardly any deliveries. And social distancing is the key. Not crowded dense cities or military camps. Hospitals in general are cost cutters. There's profit involved. There's dysfunction.  And there's always fear that there wouldn't be enough respirators and beds or ventilators for that matter. The medical personnel can be overwhelmed and they fall ill as well. And this new area, antibiotics can help save people's lives because it gets rid of the secondary transmission, the bacteria. Flu in general kills 650K in the US annually. Swine flu killed 12,000 in the USA. And we have to ease the strain on healthcare. There's supply chains, disruptions. Go simple, food, basic walk, quarantine. Enforce rigid quarantine and have rigid hospital care, no shortcuts. Hand washing, stay home if sick, cough and elbow versus hands. And a big lesson is to understand the media and the government. And when I talk about this, I'm talking most about the government and the truth, because they can buy out the media. There is denial. It poses a threat. And during some times, certain governments want to capitalize on patriotism. Overcrowding is really bad in general and will shape the future of cities. Having control and self-control, self-discipline and not going out of control with the emotion versus reason. And media can minimize this, the emotional effects. And another dynamic is to understand the business and economy and the politicians. Disease exists. It's an economy of war. So you can say, sir, excuse me, there is a disease out there. And by doing more work, you're making it worse for yourself. In other words, you're gonna make more work for yourself in the long run. And doctors on the rise died to find a cure on the job training, on the job death. So here's some other books to check out. As I wind this down is Gun, Germs and Steel and the book, Sapiens, which I did do a book of you on. And here are my last thoughts. Quarantine and isolation works. There's lessons to be learned from this. As this is not just a history book. Say no to crowds and you want an honest government. Truth and lies, it is better as a lie to save panic. There's truth and lies. Is it better to lie to save the panic? They can suppress the information. We can all gain by not having them do that. Be careful of volunteers. They really shouldn't be volunteering. There should be upgrades in personnel and quarantine. And you can look back at honor and raise male doctors as well as male talent. There is that trained medical staff that is lacking during the crisis. Being prepared is king. Hire talent who actually work. And if you don't do that, you're adding more kindling to the tender box. When you light that box of matches, drensen, gasoline, you're gonna get what you're gonna get. Use sanitary methods. No overcrowding because this is gonna create more work for you in the long run. Discipline is freedom. And they were creating in the past a bigger prism for themselves. It's not an era of work, but slow like an elephant or the bear market. There's nature's rage. And when it's crazy out there, we need good leadership. Good medical expertise. I'm not just a transporter. I'm a transporter of the truth. And I do not promote volunteering in a hospital. There's always room to hire in the hospital. And this is a great book. Make sure you read this.


Hello friends, a new mystery gift is just dropped in Pokemon Scholar and Violet. For the first time we have the availability of a shiny Pokemon being given away as a mystery gift in these games but it is running for a limited time only so make sure you check out everything in the video so you don't miss the chance to get this exclusive Pokemon while the event is running. So this specific mystery gift is running in conjunction with the North American International Championships which is happening this weekend. It's covering all of the games in the competitive scene from Pokemon Go, TCG, Pokemon Unite and importantly VGC which is the one format that is giving out this mystery gift. So to access Oconine in your game you're going to need to come to your poker portal and once you're connected to the internet come down to your mystery gift and get with code or password this will open this screen and the code that you're going to want to put in is PaulEU1CWIN and the code as always will be on your screen and the event itself will be running from today as of recording this video the 30th of June until July the 3rd which will be Monday at 23.59 UTC so you have a very small window to get this mystery gift but as you can see Paul's Oconine you click into it and you will receive this mystery gift in your game and there we go the mystery gift Oconine from Paul's winning team from the EUIC and it is a shiny Oconine which is such a great mystery gift to get the mystery gifts that we've had so far this year none of them have been shiny you got your Oconine and you can check out all of the details of the Oconine itself and it should be transferred into your party along with it you're going to get the item safety goggles that Paul ran on his Oconine it's going to be in a cherished bowl as well with that grass terra typing with a moveset of flare blitz will always protect and extreme speed and it is evade exactly how Paul used it in the tournament and timid it is the ability and it will have the battle champion ribbon as well attached to it with an adamant nature so a great gift like I said to get and something that's going to be really nice for you to take advantage of and you can see the Oconine in full force here the shiny Oconine of course getting the shiny is pretty nice as well just a free shiny in your game so that is everything for today's video remember it is only a very short window for this mystery gift event do grab it while you've got the chance in your games use the code like we said in the video and have a lot of fun getting your shiny in your games let me know if you do grab this mystery gift over this weekend and do you think we'll be getting any more shinies anytime soon in the games maybe a rare shiny this is a lot better than that give me go on for sure thanks for tuning in friends if you've enjoyed today's video do drop a like do subscribe to the channel as always to stay up to date with all of our Pokemon scholar and violet content check out and I see over the weekend while it is running and I'll see you all in another video very soon so until then take care of yourself and bye bye


So let us try to derive it now so let's assume that this is the bar magnet draw a cylindrical shape all of you I hope you have copy and pen with you you're not watching it like a movie with a popcorn in your hand okay so this just to be you know being a just to make it simpler the diagram I am taking it as just a cylinder the entire solenoid so this entire solenoid if I treat it like a cylinder okay the first let me draw the basic things so these are the two axis okay so I'll say that this is axial and this one is equatorial okay and the dimensions of this solenoid the radius is given as a okay and the length of this solenoid is also given the length of the solenoid is L okay so L is a solenoid length and the current is flowing in the solenoid that has a value of I capital I is the current okay you are measuring all the distances from this point let us say this is O okay and number of turns per unit length in this solenoid is given as small n okay so given all these things I want to find out forget about magnetic dipole moment right now okay just try to find out magnetic field at this point P okay which is at a distance of small r from this line okay and just like in case of electric dipole we have assumed that what we have assumed distance between the charges we have said that distance between the charges whenever we find electric field okay is very less compared to where we are finding the electric field into a dipole okay so distance of the point where you are finding the electric field that distance is very large compared to the distance between the charges when you were talking about the electric field due to a dipole okay similarly when we are finding electric field due to this solenoid and we are treating this entire solenoid as a magnetic dipole then our assumption here is okay this is too well sorry for that so this is too well just like in in case of electric dipole you have taken distance as to a here I'm taking distance between these two poles let us say this is North Pole and this is South Pole distance between these two pole is too well okay so it's an analog of electric dipole where too well is the distance between the pole and the tool is very less compared to where we are finding the magnetic field alright now just spend some time and see can you get an expression of magnetic field in terms of whatever is written here forget about a magnetic dipole moment the hint is you can take rings like this you know you can take you can imagine a ring like that the width of this ring is dx and this ring is at a distance of x okay just spend some time in it and try to see whether you can get something you know you may not be able to get the final expression but at least try to analyze how you can you know get the equation another hint is a question to you do you remember the magnetic field due to a ring along its axis so you have to use the formula for magnetic field due to a ring along its axis and you will be able to find the magnetic field due to the entire solenoid okay I'll just write down here magnetic field due to a ring along the axis so let us say this is the ring okay this is the ring here current going through is i number of turns on this ring is n okay I am trying to get the magnetic field at a distance r or let us say at a distance you know x from its center at this point which is at a distance x okay the radius let us say is a what will be the magnetic field you guys remember magnetic field in this particular situation would have been mu naught n i a square divided by two times of a square plus x square raised to power 3 by 2 you guys remember this yes or no please message okay so now can you find out magnetic field due to this ring just because of this ring forget about the solenoid you just have to find magnetic field due to this ring which is of width dx and the radius is small a okay get the magnetic field due to this ring here at a point p how far is this point from the ring this point p is at a distance of r minus x isn't it this is x and r is from the center so distance of the ring from this point is r minus x so get the value of magnetic field due to this ring only first of all the number of turns on the ring that will be equal to what n into dx fine and this x was what this x was distance from the center of the ring to the point where you find the magnetic field okay so that x over here is actually r minus x r minus x is distance from the center of this ring to this point p okay so we can write magnetic field due to the ring will be equal to mu naught n into dx i a square divided by two times of r minus x whole square plus a square raised to power 3 by 2 fine so this is the magnetic field due to this ring only alright now in order to get the total magnetic field I need to integrate this right total magnetic field will be the integration of this magnetic field isn't it and I know that direction of magnetic field along the axis will be straight so I don't need to worry about any components here because all the magnetic field due to all the rings okay where ever you consider ring you can consider ring here also there also you can consider anywhere you consider along the axis the magnetic field will be always along a one straight line so you just have to integrate it and the limits of integration yes same here limits of integration you are integrating what you are integrating x right and x is a distance taken from this line right so you are going from this point you're going from this to that isn't it so your first going left and then going right so the limits will be minus l to plus l fine so that's what the limit is now we are going to use an approximation which is not very obvious over here as in the usage how it is getting used when you try to integrate this it becomes very tedious okay but then if I use the approximation straight away what is this approximation that r is very large okay r is very large compared to l okay and I know that x is smaller than l right so if x is smaller than l then r will be always much greater than x fine and if r is much greater than x can I say that r minus x is approximately equal to r only yes or no so I have effectively removed this variable from integration because it is very small it will hardly affect it will hardly affect anything so I'll say that magnetic field B is integral minus l to plus l mu naught n i a square into dx divided by two times of r square plus a square to the power 3 by 2 all of you comfortable with this any doubt till now please message any doubt till now this is very important derivation okay so now that this expression has this expression has come I can you know further make it more simple you know simpler I can say that r is so large that it is much greater than the radius of the solenoid also okay so if I say that then even this I can drop off even this is gone so what I will get is magnetic field B is equal to now I will take all the constants outside mu naught n i a square divided by two r cube so I will get integral minus l to plus l dx so it becomes straight forward fine so this you will get as mu naught n i a square into two l when you put the limit minus l to plus l you'll get two l divided by two r cube okay so this is what you get as magnetic field due to the entire solenoid at a distance r from the center of the solenoid along the axis fine so I say that this is the magnetic field which is axial okay now you guys remember what we were trying to do we were trying to find magnetic field as a function of magnetic dipole moment m okay so can you modify this expression further and get the magnetic field which is this in terms of magnetic dipole moment quickly do that can you first type in what is a total magnetic dipole moment of this solenoid B's sorry m is equal to what total magnetic dipole moment of this solenoid is what all of you type in magnetic dipole moment through any loop is current into area of the loop right now here we have total number of turns n into i into pi a square now how will you get total number of turns capital n is what capital n is number of turns per unit length which is small n into total length of the solenoid which is two l this is capital n this into i into pi a square this is what is the magnetic dipole moment m okay now please modify this and do it quickly now it's not small n i a it is capital n i a small n is number of turns per unit length once you get the answer please message that you have got it or just put the thumbs up that you have got it once you got as a function of m okay poor we got it ritwick got it syme here got it with caps on okay a lot of people are getting it right so let me write down the expression here so what you'll get is this mu naught divided by 4 pi multiplied by 2 m by r cube all of you got this only m is n i a square into pi into 2 l so denominator and numerator pi will come okay so this entire thing this thing is capital m so i have multiplied and divided by 2 also so that i get nicely this mu naught by 4 pi outside which is like typical a magnetic field constant getting it so we have just now derived magnetic field along the axis due to a magnetic dipole moment fine now you guys remember electric field due to a dipole moment along the axis how much it was it was 1 by 4 pi epsilon naught 2 p by r cube so you can see how similar these expressions are okay the direction of magnetic dipole moment is the direction of the area curl your hands along the direction of current you'll get the direction of magnetic dipole moment okay so this is axial now if i correlate with electric dipole moment field and i know that along the equatorial plane if i know that along the equatorial plane electric field if you guys remember was 1 by 4 pi epsilon naught minus p by r cube so the magnetic field will be what magnetic field should be mu naught by 4 pi into minus m by r cube okay so the formulas look analogous fine now we will take up a few more i mean we'll just discuss a couple of more theoretical aspects and then we'll start solving you know numericals so just a couple of more things