Grazie molto e prima di iniziare, voglio dire grazie al Paetano per invitarmi a parlare con voi oggi e anche io voglio dire grazie anche a Paul, Matteo, Amber e Kian per il supporto per oggi. Allora, cominciamo perché ho un po' di stuff per raccontare con voi e quindi io avrei avuto velocemente e velocemente con il topico di oggi. Allora, io provo, in il prossimo minuto, a parlare con voi la differenza di la Taurosa e la Taleca e cosa dobbiamo creare la Taurosa e la Taleca e perché dobbiamo creare la Taurosa e la Taleca in un'organizzazione, in un'organizzazione. Allora, per provare a parlare con voi la Taurosa e la Taleca io uso un progetto, un progetto che ho imparato da 2016-17. È un progetto dell'Unione europea, perché ho lavorato per l'Unione europea e questo è un progetto di labor market. Allora, cominciamo a mostrarli questo progetto e poi faccio in dettaglio un'altra approccia e un'altra metodologia per analizzare i dati. Allora, parlo di il top-down approccio e di un altro approccio. Allora, alla fine del mio progetto, vi presento 3 differente tecnologiche. Non lo vedo in dettaglio, ma se volete parlare con me online, avremo molto di tempo. Vi presento le tecnologiche per supportarci, per supportarci, per costruire la Taleca. Vi presento i dati.io, Udi e Asber. Allora, vi presento a me, io sono Mauro Pelucci, ma potete anche chiamarmi Mauro Pelucci perché è tipico da inglese il mio nome è Mauro Pelucci e è ok, non è un problema. Sì, nel 2016, ho portato questo progetto per l'Unione Europea, principalmente da Eurostat, Cedefop e ETF. Eurostat, credo, è abbastanza nulla. Cedefop e ETF sono due dati europei che pensano di vocazione, quindi pensano di sviluppare il mercato labore di vocazione in Unione Europea. Cedefop, principalmente nei paesi che sono parte dell'Unione Europea, ETF, principalmente per i paesi che sono fondamentali dell'Unione Europea, come Morocco, Tunisia, Giorgio e Ucrenia. L'unico lavoro è dove ho portato il science globale. Che facciamo? È molto particolare, vi presento nel prossimo slide. È un'università di studiamento in Bergamo, e in Vemiliano V.Cocca. Questo è il mio contatto. Se volete contattarmi su Twitter, e mail, sentite free to write me e anche in LinkedIn. La presentazione è pubblica, quindi se andate a questa reposizione di Github, troverete il mio slide. Credo che avrò il slide dopo la collezione, la versione la più visibile in questa reposizione di Github, potete usare questo slide come volete. Iniziamo per il tema per oggi. Il progetto che voglio presentarvi è di esplorare l'Unione Europea. È un periodo di tempo, un periodo di informazione, un periodo di informazione, un periodo di informazione, un periodo di informazione, un periodo di informazione. Iniziamo per esplorare l'evoluzione dell'evoluzione. Perché, 5 anni fa, 6 anni fa, l'Unione Europea ha capito che l'evoluzione dell'evoluzione è in continuo evoluzione. Quindi, i tati officiali non sono abbastanza per esplorare l'evoluzione e si chiedono per costruire la tua casa per costruire l'evoluzione dell'evoluzione. Quindi, l'evoluzione del professionale, l'evoluzione del skill, l'impatto della globalizzazione e anche alcuni che, in ultime 2 anni, hanno stato terribili per l'evoluzione perché, you know, noi eravamo in pandemia, abbiamo l'Ukrainian War, abbiamo molto di nuove regalizzazioni, quindi tutto questo topic, ovviamente, ha cambiato l'evoluzione. Quindi, come abbiamo tentato di aderire queste richieste? Quindi, per tentare di creare un sistema che ha tentato di capire l'evoluzione quindi che è una casa di l'evoluzione. Quindi, ovviamente, abbiamo iniziato dall'evoluzione del professionale, di solito, ovviamente, ma queste evoluzioni di professionale non sono abbastanza. Perché? Perché abbiamo molta informazione di fortuna, non abbiamo una informazione fresca, non immagini le statistiche puckri che parlano the language of employer and the language of employee, of course. Quindi, abbiamo int recycled the web, So, in 2016, assouth we started to collect data from the web mainly job management online job management in all of European Union To build at our house, At the end we have at our house So, for me it's 20 years that I work with at our house quindi non è un nuovo topic di Towerhouse. All'inizio ci rilisiamo in Annalytics, principalmente ci rilisiamo in Dashboard e con questo Dashboard, l'Università Europea, le proprie di allenamenti, l'università, può adessare alcune questioni sul mercato sviluppato. Quindi, questo è un link per il tool, questo è un tool pubblico, che si può accettare al tool, che è costruito su un tavolo di Dashboard e sotto il wood, abbiamo in Towerhouse la dimensione di un mercato sviluppato. Quindi, cosa dobbiamo fare è abbastanza semplice. L'anno, io ero qui rimodere e presento come coltiamo le data da scrivere. Quindi, principalmente, cominciamo a scrivere le data dal web, dal portale online, dal dashboard, dal site pubblico, del servizio pubblico, principalmente per scrivere. Ovviamente, facciamo una cura di qualità di data. Abbiamo creato una grande data lake con tutto il data che abbiamo e, su top di questa data lake, abbiamo rilasciuto le data in Towerhouse, principalmente. Quindi, alla fine, abbiamo una data in Towerhouse dentro di un'organizzazione che ha provato data per il nostro secondo. È quello che dobbiamo, ovviamente, muovere le data dal Towerhouse per la data lake. Abbiamo applicato le tecniche e le tecniche di AI perché le data che abbiamo colleggiato dal portale online sono abbastanza differente, you know? So, speaking about my profession, so, you can call big data scientists, but in some organization, I am a data engineer, you understood very different, in some organization, I am a senior data scientist, in other I am or head of data science. So, all this profession are quite similar and it's difficult to analyze the very information for a user maker if we don't normalize this data. So, what do we do is before to create a data lake we evolve information and then we produce Towerhouse. Visit Towerhouse is is not public, of course, but all the national statistical institute can access to visit Towerhouse to release statistics, information, reports and so on. Under the hood we have a lot of technology, of course. Mainly we use Spark, PY Spark to process information. We use a lot of machine learning to normalize the data. To build the data lake, of course, we don't use only one technology, but we use a bunch of technology because for each question we need to choose the best technology. For example, we use AWS string to store the information because we need to reduce the cost. We use Neo4j and Elastic to release some data to our security. We use Tableau for representation. In some cases we only use Python and matplup in the deep. It depends by the question. So, let's return now to representation because what we need to understand is why we need the data lake in Towerhouse because when I teach in university a lot of students, I don't know, social on the web on Google and okay, the Towerhouse are died. We don't need to create the Towerhouse. But really we need the Towerhouse because we need the quality data. So, but also we need the data lake because the two Towerhouse the Towerhouse data lake really are four different questions. So, let's start with the topic. I have a question for you. It's not my question. I took this question from a presentation of Cook here in 2014. So, from this TEDx talk you can find the end of the web. So, what is in your opinion the America's favorite type of key? Apple pie. Thank you. So, okay. Thank you. It is the same response of 10 years ago, of 80 years ago, sorry. So, it is the same response. It is a beautiful question for me because I asked you what is the more favorite type of cake and you are applying in your mind the typical BI process, this intelligent process. So, I try to recap the process in your mind. Of course, you collect the data. In this case usually we use the retail sales data to respond to this question. In your mind, you are applying techniques to optimize the information. So, to aggregate the information we can call them this bunch of approach ETL. So, extract, transform and load. You build the Towerhouse in your mind with the list of the type of case. So, apple pie and also the other. And then you use the turnover to take the first one, apple pie, right? Okay. So, it's a typical BI process. If you retire to 2004, Solomon described the BI process as the bunch of processes in organization that take care about the collection of the data. The cleaning, the improvement of the quality of this data. The store of this data in Towerhouse to release question, to release answer for decision maker. So, there is a typical BI process. But this process usually, always start from a question. Starting from a question, we apply, we select the source system. In your question, we select the data from an ERP from an enterprise resource system to respond to the question. We collected the data. We store the data. I don't know where. We provide the data and we create an application. It is a typical BI process. And I reuse this process to take care about available market data because what I do for the European Union, of course not with the type of cake but with 100 terabyte of data, it is the same. It is the same. I collect the data from online job website. I try to address a lot of issues about the quality of the data that we collect. I store the data and then I create something to provide the data to my stakeholder. Of course, my stakeholders are quite complicated because a lot of politicians. But of course I try to simplify the dashboard for them because they need this data to improve our training system, our labor market system and so on. So it is a typical top-down approach because we start from a question, we select the data to address this question and then we make something to produce answer. But I need now to return to the beginning because the question it was what is America's favorite type of cake? And we need to understand the different favorite and retelless data because so in our mind we make the process but I don't know if favorite it is the same of retelless data. Speaking about one or two years ago during the pandemic I needed to buy a printer because I have three children at home and I didn't have a printer before and I choose one printer, not the best one, the printer available. So speaking about the question I don't know if favorite is the same of retelless data. I don't know. So of course now we have a lot of new data with a lot of new question. It is not the same of 20 years ago when I started to work and I have only surveys, surveys, surveys, surveys. Now we have a lot of new question coming from our decision maker, our colleagues, my wife and so on. And we have a lot of new sources. Of course we need to understand what is the question and what sources we can use. So we need to change the approach, not the top down approach. So starting from a question but we need a bottom up approach. Starting from a question is right because we can go quick, quick click. But we need to understand but we can also address a new question. So we can use a bottom up approach. We can store everything. Now not only the data retelless data but we can also store social media data, web data, data coming from Amazon e e-commerce. We can store everything now and then use machine learning, AI, pattern recognition to extract a new insight for our seconder. Let me to give you an example. I started in 2016 to collect data about labor market. My first question from the decision maker was what are the top five occupation, profession, more requested European Union? And okay, I build a machine learning model and try to normalize the job titles. I try to build a machine learning model in the 45 different languages because in Europe there is no English but also Spanish, Italian, Portugal, Basque, Catalan, Galician and so on. So it was not easy but now we are at our house. Last year the same decision maker asked me what is the request of remote workers? So, new different question, new question. Of course, using this approach, I started to use the raw data that I stored in seven years of project and I released that the remote working before February 2020 was not present in Europe and after now is present. Spinging about the green transition, how to measure now the impact of the green economy in the labor market? Because we have the data now, I can now respond to my decision maker not to build at our house because at our house is built with fixed dimension. So, occupation, contract, working hours, I don't know employer, salary. These are different question. Of course, if we use a bottom up approach, we have a lot of challenges to address starting from the use of machine learning. So we need a way to integrate data, AI, machine learning, tool for analysis. We need a way to introduce any data and any sources because online job posting are okay but now we have also job platform. I can call data about the labor market from Facebook, Amazon, Twitter. I'm starting to watch also Twitch because it's on our channel. Three years ago, I found one job advertisement inside the HTML code of a company. A company, in this HTML code, if you go to the source code of a page, there was a job advertisement, of course for technician. So when I collect data, I need to take care about the evolution of the sources. And of course, the HTML code is not like the job description but usually I find on, for example, ad ecco rasta, so this typical job boards. So, of course also the accessibility of the data. Why? Because when I, for example, provide the data to the decision maker, they can access only to the final data. I don't want that they access to my kitchen where I prepare the data. I don't want. But of course, when I have a lot of good scientists, my colleagues, I want that they access to the data and play with the data. Because they can found new patterns, new, I don't know, new metrics. Speaking about new metrics, one month ago, one my colleague started to play with the data. Started to play with a new model, new model. Model of 40 years ago, but a new model, about the context. We apply, for example, a model coming from econometrics. It is called economic complexity and we found something interesting. We present to my economic colleague, it is okay. And we are working on it. So, I want that video scientists have access to vero data. But I don't want that the decision maker access to vero data because they cannot understand the complexity of the data. So, we need data warehouse. We need data warehouse because data warehouse are like the signal that we have in our organization. We need this signal to understand what are the state of organization. Because data warehouse are clean, are integrated, are sandwiched oriented. So, we don't have raw question in data warehouse. Data warehouse are built in two response to pre-definite question. Of course, we need also data lake. Why? Because in data lake, we can found a lot of new inside, new question, but currently are unexplored. Okay. So, of course, data lake are more complex within the warehouse because we have machine, we need to prepare the environment to be machine learning needed. We need to give access to vero data. We need to be schema free. Please, not schema less, but schema free. Okay. Because every information have a schema. Okay, sooner or later. So, we need these characteristics and also we need tools and techniques that support or rapid change of the information. So, I love this representation of data lake. I don't know because I found it on the web and it's beauty for me. So, I don't know who prepare it. But as you can see, because I love, because it is my 20 years experience recapping was live. So, as you can see, we have data coming from ARP. We have data lake where we can store vero data, where we can store our process to improve the quality of the data and we have the old tower house. So, as you can see, we have the access zone where the data are available. So, it is the same of the BI process that I presented 10 minutes ago. It is the same. Only the name is changed data lake. The name is changed because the approach is changed because we have a bottom up approach. We don't start from a pre-definite question. Yes, we have an access zone as some pre-definite question. But also we leave the data to speak. We leave the data available for our data, scientists, our data analysis. So, speaking about the process, this is a recap of what we do in my organization for the European Union. As you can see, we ingest the data from scraping. We have some stage that clean the data and apply some preprocessing techniques. Then we apply a lot of machine learning to extract the single information from our old question. So, we extract the occupation. We try to extract the skill requested. And we have 30 different dimension, classical dimension of the labor market. And we build the lake. Of course, we have 100 terabytes of compressed columnar data. So, it's difficult to handle this change also because, so, every six months, they are changing the occupation code list. So, we need to reprocess all the data. So, in this case, we use a particular technology that we present in one minute. Of course, this area is available but only to me and my data scientist. Then, every month, we copy the data. Really, it's copy and filter the data. We move the data in quality. Only the data by the quality are moved to our house. And it is not the end because before the data are available for data analyst, decision maker, and also citizens, we apply some validation rule. Why validation rule? Because we don't have the control in this case of the source of the data. We don't have the control of the 35,000 different websites that send us the data. So, every month, we have a WS batch process that can better apply statistical task, distribution check, and so on to the data. If we detect an issue, we stop the release of the data to the citizens, we watch the data. We understand if this change is okay or not okay and then we release the data. So, speaking about technology, mainly the data warehouse and data lake that we build is based on these two technology, Delta Lake, Delta.io. Is a technology mainly supported by Spark because in the other various fabrics. And Udi, Apache Udi is a public project. Also, Delta.io is a public but with a different agency. Apache Udi is mainly minded by Uber and Apache Foundation. So, we use these two different technology to build our data lake. And also, there is Iceberg. So, currently, I'm not using Iceberg, but it's a beautiful tool. So, I want also to present in one slide Iceberg. Iceberg, it is mainly, it is the same technology, of course, with different approach from Netflix and WS. So, why we are using Delta.io? Because we need a library that can help us to merge the data. So, mainly in certain data because every month we can reprocess our entire data lake. So, with the technology of Delta.io, we found a tool integrated with Apache Spark and also integrated, so it was easy to integrate it on WS because we are using WS.io Mare to release the data, to process the data, to classify the data. So, we found Delta.io, a beautiful technology that help us to merge the data. Because, of course, Delta.io support also the time travel, the schema enforcement, support the change of the data in the partition, but really what I was looking for years ago, it was a technology that help us with update, insert update and delete. Because, you know, classical Corumbal format, like, I don't know, Avro, Parquet, ORC, doesn't support merge and updates. So, Apache Uzi is another technology that we use. Why? Because with Delta.io, we have some issue about the bulk processing of the data because it's quite slower in case of big bulk process and because the maintenance task, so the compact of the table, the vacuum of the table are not automatic. So, we have different process with Delta.io that support the maintenance and we need to take care about this stuff. With Apache Uzi, we simplify last year this approach because Apache Uzi has an automatic compression and with a different view that Apache Uzi release, so we have a read optimized view that is with less latency and with more latency and less cost and we have also a real time view with less latency in this case, but with more cost. So, with this type of different views on the data, we reduce the processing cost and the processing times about the from one to, so we are 10 more faster now. Why? Because Apache Uzi, it's designed for batch ingestion. So, in case for us, it is important to reprocess the data every month, every two month with a process and we apply all the machine learning model to 100 terabyte of data. More or less in our data we're out now, we have 400 million job posting and we also have HTML, the description, so on. So, with this optimization about batch ingestion, we simplify a lot the processing and also all the compactation and the vacuum of the table is integrated. Apache Iceberg is another good technology because in this case, I only mention one topic about Apache Iceberg. It is because we don't have the dependency from Spark. So, in this case, you can also use other technology. So, speaking about the main difference, I recap in this slide, so you can watch it if you want. Only one topic because I have 20 years of experience. Take a watch to the contribution because when you choose, you know an open source solution, you need to take care about also the support. So, it is because we started from that.io four years ago, as you can see. Mainly the issue, in my opinion, my opinion of that.io it's that it is only supported by Databricks. It's good, but you have only one company that now support the revolution. Second, we are moving now to Apache Union. Why? Because it's why my internet, while integrated with AWS, a lot of support, there are a lot of contributors. So, it's usual, so when I speak with my younger colleague, they want to use the latest technology. In this case, data lake at our house are for long decision, you have to be a long view on what you are building because you cannot change the data format every two months. So, I choose four years ago that.io because it was the only one really ready for production. Now, I'm moving into Apache Union. Why? Because, in my opinion, it is in the future with more contributors, it's better. So, thank you to everyone. If you have any question, please use the mic right here. So, thanks, Maro. Very impressive setup you have there. We have time for five minutes of questions. If there's any in the hall, please come to the mic. And if we have any remote questions, you'll let me know. Great talk, thank you. I have a question, you said that you have two types of data. You have like census data, which is very strong high value and then you have all this data. And then you mentioned that you use statistical tasks to clean your data before you publish it in the data warehouse. Can you go a little bit more into detail in how you use the first data to clean it again? Okay. We want to ask a question, thank you. Okay, so, about the data and about the quality process. It's important when we built our data lake of course to store everything. So, in our data lake, we have two main area. We have the raw data area when we store everything as is. And then we have the data clinic, not ready for the citizen, but ready for the scientist. What do you mean? So, in this area, we apply some classical processing techniques. Mainly I apply two techniques because the main issue that we have with job data is about the duplication of the data. So, I can find the same page in a lot of different website or from a different website. So, what we apply mainly in this case is one model, it is like a spam model, like your email spam model, that for each page that we collect, decide if the page is a real job posting or it is a fake job posting. Of course, we don't delete the... So, we delete from the data warehouse the fake job posting, but we store it in another table because, for example, three years ago, one European Agency asked me to release a report about the informal economy. So, in this case, I use the fake job posting to answer to this question. So, mainly we use the spam model. Second, we use the duplication model. The duplication model is built with a sort of fuzzy matching between the HTML code and the job description. The second duplication model applies machine learning because, in some cases, we have the same job posting published in different languages, for example. So, starting... So, only to give you a number. Starting from four million job postings in the European Union, only 100 are really job postings. So. Thank you for your description, your process and your talk. I had a question in terms of the data quality. Could you comment on the differences between... So, obviously, if you have sampling biases or other biases within your data, then that's going to affect the insights that you get from your analysis. Obviously, the kind of bottom-up data-like approach helps you to be less biased in your postings, your hypothesis and stuff. Yeah, yeah, beautiful question. Beautiful question, thank you. It's very difficult for me to address the question. So, I try in a few minutes and then we can chat. Why? Because... So, speaking about the classical data that we have from a survey, from a company, we have the idea of the population. So, if I ask to you how many... If I ask to Paul how many participants I have in this room is easy. We have a sensor, I don't know, of the door and we have the idea of the entire population. Speaking about job data, we don't have the idea of the number of job posting that we have in the European Union. We don't have the real number. So, when... Usually when a decision maker asks me, okay, do you have all the data, all the job posting? No, because I have only the web job posting. But you have all the web job posting? I don't know, because I collected data from 35,000 different websites. But I don't know what is the number of websites we have job posting in Europe. So, it would be a good number, a bad number, I don't know. So, usually we compare the data offline, in this case, not online, with classical statistics. Of course, so, speaking about statistics, we have different type of data because in this case we have flow data, classical statistics more or less, are with stock data. So, we use techniques to try to create a sort of representativeness of the web data that we have in comparison with available market. It's something that we are trying to address in visia. Thanks a lot, Mauro. We have to go to the next talk. So, please put your hands together for a very interesting talk.


So yeah, I think it's time to let my a5 go I love her I do but I realized I'm not fan of keep opening up these rings Let me get some of my jewels my thing and putting things out that I like to use So I do I like her but I realized also that it was I've kind of stripped her down a little bit. It was mainly The book the cover so I see where some people take the rings out and use the cover But I don't know. I I like the softer version of Of like I can feel a board through here. Maybe if that board wasn't in there I don't know. I just like the soft version like of the foxy fix things like that so we're just gonna rest her in peace and We're gonna get the planning in Our new happy planner.  So anyway, we're planning for my birthday week. Okay, so I have now One more. This is my planner set up now God pray for me. Okay, and I don't even know what to do with half of them. So I'll ask you guys on instagram and in another video. What should I do? What should be my everyday carry? So I'm thinking this is going to be for my social media I'm thinking this is gonna be My everyday carry, but this one doesn't start to july So what I think I'm going to do is just add to it. Well, you know what? I think we're gonna use this one because this one's feeling a little slighted so Let's just open it up And let's go to april And see here's my issue already I don't like the colors, but we're gonna make it work We're gonna make it work. I'ma find a way we're gonna make it work I want to change the colors and I really like nude I like it just to be black and white and let me just add Whatever I want, but it's all good. It's all good. So I got this birthday printable from Htp planning. I actually printed another one But I don't know what I did with it. I thought I printed another birthday I bought another birthday something, but I may just add it to something else and then this goes with another printable I got from mint gem and paper code mint gem paper code So let's just kind of hop on into it I got my white out and I think I'm going to go ahead and white out April Let me see. Let me just play with it for a little bit Let me play with it. So already I'm going to start with these boxes here and I'm just gonna cover those up Up top I had actually printed some balloons And I was going to just Do balloons over a whole spread. That's when I was just in my a5 That's what we're gonna do. So we got these pretty sparkly Now the dates aren't that good, but we don't need those dates Here's a pretty cake So I think this is kind of going to be my everyday carry the only thing is my birthday is tuesday I have a luncheon to go to for my birthday I don't know why the last couple things I've cut On my sticker paper. They tripping. They haven't Come off pretty good birthday spirit So what I'm gonna do since I didn't um Print the other one or can't find it. I just think I didn't print it to be honest I downloaded the birthday Thing and I just didn't print it because I had some things on my Computer I needed to delete and I was trying to add stuff to my Um hard drive my new outer Hard drive or whatever that is So yeah, my birthday is tuesday Oh, look at this the 23rd So this it'll probably be up right like cake pops a little doggy Okay, monday. Do I work monday? I do work monday I'm gonna use some other boxes out of my new sticker books that I'm excited about you know what Let me look at this like See if I can kind of run this Get rid of that when I take some washi tape.  So I gotta go back And hole punch these which I don't like to do I'm so excited to have this book. Let me explain something to you. I'm so excited. I'm gonna use I think I'm gonna use the rose gold to use a big chunk like this but elaborate on that side I want to put I gotta cover this green here. So now I know I saw Some note boxes. Oh, there's silver. It'd be nice if they had rose gold They got gold, but let's see rose gold. Nope No rose gold. Got a pink. I'm gonna take this today's focus It's not big enough. It's not big enough What I need is like a good Quote box or something Oh, here we go. Today is a good day Let's try this one. Today is a good day for a good day Let me wipe that out Because I'm gonna still have to wipe that out Y'all still hanging in there with me? We ain't doing this. I'm gonna just need white out just for these books. So this one Plant smells grow laughter Gotta find something else I want one of those long And I decided to go ahead and talk through this because I said well some people like talk through videos, but It's hard. I don't know. I know I'm not the only one, but it's hard to like plan and talk through enjoy Celebrates we don't use celebrate up here We're going to lunch this day I'll whip this out. Let's see. I got one two three and it won't So I'm just gonna lay that here. Hey, you all know that's like a work day This here Make sure it's even Thursday You know how I feel about this on Thursday There we go Quarterbox Cover up April and notes. I know it's something like I'm probably overlooking to do Let's see notes to do I'm still in the farmhouse. I love this book. I love that ever since I think um At home with Rita had showed it Let's see here. Let's add some more of these florals I'm over here the bottom Really kind of wasting my time Yeah, what y'all think so far we're doing good. We're doing good Let me do another little one Right over here Just to kind of give it a little bit of a balance some rose gold to do today's focus priority I'm loving this book Let's find something that say the weekend something a little purpley or something we need something Okay, I have another little quarterbox from the little birthday thing Now I'm in color story. I'm just looking for some boxes Something that will go with Spread here. I'm really thinking I'm just kind of done because Here we go Let's rip this one out might be a little crooked, but okay Tell you what Those gold or rose gold those aren't rose gold I'm gonna take these two little nice pink stars here Put them on Wednesday For some functionality And I need this flight sticker my daughter's flight leaves on Monday, but they don't have the color That i'm looking for here are some nice ones, but they got black in it Also, uh, the young lady and I uh, we were in the joins today.  That's creative and it was so funny because we were talking about um How creative and how um well That um at home with quila just comes up with stuff and she said genius She said she's a genius. I was in stitches. I just couldn't stop laughing. I thought it was so funny I was like, yeah, maybe so I said because i'ma tell you I said, I thought I was creative but some things my mind can't like Begin to you know when I see somebody do something like out of the ordinary, you know, you like I get out of here. You just like I can't believe you thought of that So, yeah, so it was too funny. I just thought it was so funny. She was like genius so Y'all this thing is about 30 minutes long. I cannot I cannot She holds y'all for 30 minutes I'm thinking i'm done though. I almost forgot what I was looking for. Let me see Oh, I need some more girls. Let me go into my stash So this what happens when you get Too many sticker books and you don't even know what to do with yourself I'm looking for some functional boxes. I need them in my life and I can't Can't believe I can't find any She said a rose goes something saying that we can but they don't So i'm over here fighting with this I'm gonna leave that alone So this completes my spread you guys My first classic happy planner spread Thank you all so much for watching and I will see you all in my next video. Bye


Hey everyone, welcome to figure fantasy. We have here final counter strike end game for Final battle. So happy to have additional content for the game. Just a reminder guys You won't have this unless you unlock chapter 26-1 of the main story and Also be reminded that the currency that you earn here will be used in the private figurine pavilion Okay, so let's move on to each of these bosses here. So each of the boss You need to clear them Using the three brands so the three brands have their individual stages here as you can see We'll start here with Let's read. So what I did was I gave you guys a sample on For each floor. Let's say for example for each floor. This one is clearable up to The total victory this one so far at the second floor. I'm in in the hell stage and For your third floor, I'm in hard and fourth floor. I'm in common. So as you see There's a pattern where in each stage as you go down In in terms of floor or you go up in terms of floor It gets harder and harder. Okay, so What you do is you clear The the most the the furthest stage that you can clear with the lineup that you have So try to clear it because the rewards here again these ones the counterweight silver coin will be used in the private figure collection, which is this one and So far we don't have no stocks yet for For the pavilion collection. My guess is this will be We refreshed by tomorrow. These are I think additional stats stat bonuses probably skills I'm not sure yet, but we'll have to find out once it drops. So as you can see you can progress Using a specific team. Let's say for example, I'm using let's read. So I'm using this Team for let's read. I'm gonna show you guys what my team is. So I'm also using this team For the other what you call this the other stages that I have here. So including three Third floor and fourth floor. It's it's actually the same So as soon as you as you do use this team in the first floor They will be your default, but you can obviously Change up the team while you're in battle while you're progressing depending on the tactic depending on the difficulty So as you can see here as well same same tier TYR but different team we have here Tenma then for Galatea I have this team that I'm bringing for Galatea. So again This the rewards here are good. Do you have as you can see there? You have here stamps you have Clover stickers you have Stamps again, there is actually a shard for your for your yellow what they call this yellow or yellow rarity of Figure so I actually Didn't show it to you guys because already collected it So that is it As you can see I'm just gonna show you guys my proposed team composition starting with tier and This is going to be let's red so tier let's red this is my proposed team with with Sakura Megan you have here Hatsune Miku you have here What do you call this? Zantakein and you have here Milim okay so What else do we have here guys? You can actually interchange some of these One of my if you need more Minions you can actually use Harriet you can use Owie for shield you can even use rumor if you want but again these are just my proposed lineups for you guys So just gonna go through them one by one Per boss and per team. So you saw there a while ago that was for let's red Then for tier my proposed lineup will be this one You can bring in the future Mako or Iran's for this one Also Vivian not really in tier I think but for Mako and Iran's I think they would be useful in Higher or for example in higher floors for this boss Okay, and for Galatea the team that I used with tier is going to be To be lubu Zau Yun you have here Got the name of this girl. I had the Okada Zau Zau Yun or Zau you Both of them have difficult names almost the same and Zuki Liang at the back You can actually bring Erixia here as a proposed team And that's it. Oh, Zuki will be useful in other bosses. So watch out for that one So that is it for tier the next one that I have I was able to set lineups already for each brand so let's take a look at For code V. Let's red The lineup that I have here is this So Rimuru Megan Milam at Sunimiko and Ayakino It's only five that you can deploy here. So definitely Take advantage of a we damage Eric can be a good addition to here if you want to go with some a summoning team and also with Suzumi as well It's of course not a bad choice But I left her out because this is still early and you still I think you don't need healing at this point So you can use her later. Next is going to be for code V ten ma Code V ten ma my team here is obviously Crusoe's Zephyr Vasruin Zerola and Rin Other options that you can bring here would be Mako definitely in Irins and also Vivian especially if you built Vivian Probably five star peach and up then she is perfect here for a for Big mobs AoE so again Those are my proposed lineup for this one the other one for code V Just want to show you what I Used and I'm gonna use So you have Zau you Zau you you have Zuki Liang you have Lubu and Galatea They're very limited. So if you want a bolster healing you could bring in Eryxia You could also bring in Osuke for freeze and that's it So very limited for for Galatea in terms of choices So that is so far for code V and for as a zeal Let's go to let's read the way. Let's read lineup Let's read. This is my lineup for let's read alternatives for this one would definitely be Sakura AoE If you're to go again with a summon team you have You have to zoom me here as well Let's go to as a zeal ten ma or as a zeal ten ma You have here in you have Vivian already here For this one by the way for as a zeal you can deploy six not five for the other stages. So oh You can also use Actually if your sannis will build here, she can be good here as well Mako if it need an additional healer as well. So Moving on to the last lineup for that I have so as a zeal Galatea For as a zeal Galatea we have here Basically the same again. No no significant change only that usuki is here and You can bring in Erixie as well. So again, those are my proposed line-ups for final counter strike tier code V and as a zeal for each of the brands that we have So again, just a reminder all of the currencies of particularly this one the counterweight will be used in a private private figurine pavilion which will unlock a lot of you know information and Abilities or stats probably a of your favorite figurine. So that's it. This this will be a fun game of Unlocking and Getting total victory. So you have to do total victory not just this one You have to get to total victory then you can sweep this with with fish bones again That is it. So hopefully I could Bring out my if I have final line-ups already for total victory for the higher stages, I'll do also a Run of that one and post it for you guys so that you can see what the final lineup for probably third floor and fourth floor for tier and Code V and as a zeal for all of the factions. Okay, so That is it guys. So that is basically the guide for for Final counter strike. It's still the same. It's just you're farming this for another event and Again, once you set the line-ups from the start even for the first floor They can carry it over unless you want to change that lineup that you want to bring for the second floor third floor and fourth floors Okay, guys. Thank you very much for staying this far. So hopefully this helped you start your final counter strike Note again, it will be open once you clear chapter 26 dash one of the main story Okay guys, so If you're here, please do consider subscribing because this helps my channel a lot. Thank you guys. Stay safe Take care. That's the warden and I'm out of here


Hello and welcome to the session. In this session we discussed the following question that says, write the zeros of the polynomial x square plus 2x plus 1. Let's move on to the solution. The given polynomial is x square plus 2x plus 1. Now we have that x square plus 2x plus 1 is equal to x plus 1 into x plus 1. So the value of x square plus 2x plus 1 is 0 when x plus 1 equal to 0 or x plus 1 equal to 0. That is we have when x equal to minus 1 or x equal to minus 1. Therefore, we say that the zeros of the polynomial x square plus 2x plus 1 are minus 1 and minus 1.  This completes the session. Hope you have understood the solution for this question.


Did I drink the coffee or not? Did I raise the coffee cup to my mouth or not? You will only know if you're empirical, right? So empiricism, it's a tenet in science or it's a method of observation in science. So an empirical method is one of direct observation. So you know that I raised the coffee cup to my mouth. Everybody in the studio audience here knows that I raised the coffee cup to my mouth. However, no one knows but me if I drank it, right? You might see my throat go like that, but that doesn't mean I drank anything, right? It just means that you saw my throat do that stuff. So the point being that empiricism or empirical, being empirical, empiricism is a method of science that allows, is for direct observation. And there is no room for interpretation of what happened. There's no belief, there's no bias. It's just I saw it, I heard it. So scientists that are empirical are extremely strict on what they accept as scientific evidence, right? I hope that makes some sense. It's very important for the field to be empirical.


Okay, so welcome to the etch-in app, some things I kind of want to talk about or what exactly are we going to update, when are we going to update it, and who is going to be doing each part of the work. One of the things other people are going to be talking about. Do most of you know what etch-in app is all about? For the record it's just the idea is to add a new upstream kernel, possibly new extravers, maybe, you know, I've heard maybe the others come up, but in addition to new features, new hardware support, and an update to etch. New features or just new hardware support? New hardware support, I don't necessarily know about. When new features, only if you are very, very, very interested, don't play against it. So basically it's a node. Of course if you say you have a new module, you can load it only if it's loaded in a new feature available, it's not loaded, it doesn't. Seven I would say yes, you could do it, but I expect most cases it's just a node. At least that's my personal opinion at the moment. I think that's the good place to be. Although you will get screwed over with new versions of drivers if they don't work.  Basically one of the things is that we don't want to drop any existing drivers at all. So we are also going to drop the existing kernel, we are just adding a new kernel. We are not making automatic updates. So if some of the updates in the kernel is screwed, please go back to the kernel you used to have that used to work for you, which is of course not what I really want to do, but it's still better than totally screwing them. What about the installer? I don't think it's a final decision yet. Part of the job is to figure out what should we do with the installer, but the third idea is that somehow we are going to do a new disk, or do a new disk with the old installer, or if you need this new stuff for the installer already, because your hardware is so broken with old things, you need to use the lany installer installed in an edge, or whatever. It seems that it's not yet decided, and you can see we can't decide. It's this moment because we need to know more what's in the new kernel, how deployed such hardware is it can't even use the installer for a story only. I think that's my critical desire today, is to make sure that we have a stable install disk that I can install on Intel hardware that has been built in the last year, because the current stable kernel can't boot on that. We're not going to install one. By the way, doesn't it boot AHCI? Really? Stated drivers. Oh, okay. And the E1000, lack of E1000 and AHCI drivers. I can't be talking about the current version. The current stable install existing cannot boot on the E1000. They might have E1000, they don't have updated AHCI drivers. AHCI moves from per device IDs to class-based, which means I can take the new AHCI drivers and run them on hardware between our chip again. This happened to me, 2.6.21. I think so, yeah. I'm not exactly sure what kernel test they're going to model. It's assumed that it's open. It's not changed. We could easily backport. I think it can be easily backported. Okay, so that's something I'd like to do earlier. I think we've talked about we're doing actually a half of them between nine and 12 months after release of Edge. Instead of starting this fall or most likely this winter. But if there's things that are safe to backport into 2.6.18, I'd rather do that sooner than later. Things that you can show that don't break other hardware. One of the things that we definitely will add in 2.6.18 are things like new GCI IDs, for example. Just so that you can get in the best of what you want to do now, and what would be already for the Edge 2.6.18? Have you read the latest Lehnun Super 3 new article? Basically the other vendors are having same problems. There's a talk between kernels developers they're having some problems... Basically Lehnun is shipping, although you know, and the price limits, and updates the kernel with heavy backwards. So basically, we are checking now the 269, and they're backporting, constantly backporting stuff. And this is becoming a model. So now discussing maybe the way to go is to shoot the latest option kernel, as is. So it may well consider to see what other distributions do with that. We're not young enough to have a problem. Yeah, we'll have a monster on the side, but it's still a problem. I think that's the big transitions they do over the last years. Intel has gone from pay to the data, and that makes it impossible to install. That's kind of a showstop for stable distribution, when we don't ship unstable install data. So I think looking at other distributions and seeing what they're planning to do, Max on the kernel team, wants to look and see what kernel other distributions are doing. That's going to be a good guiding point. But specifically, is there a hardware besides Intel stuff you already know about? Is there other hardware that's becoming popular about the new release that you already know about? I think any of the others seem to be one of the ones that have changed depending on what kind of new you're using. But does it mean the future drivers can't install the hardware? Or does that mean we are not really using the hardware? You can install one, you just don't have it. Which is pretty bad. But it's not as bad, because if you could say for example, it takes a new kernel as a USB stick, install it into a layer or whatever. It's not something I like, but it's not as bad as I would say with Intel ones. It's just a bit less bad.  I agree. It's not that much, it's way stronger with distribution. What's that for the field? So the NVIDIA drivers, do you know what the details are? Is it the NVIDIA ICIDs? No, it's just a new virtual driver. So there are new motherboards that we have done. If you're not running the most basic kernels, it's just not working. So maybe we should come up with a more general process, like some way of tracking new hardware that a lot of people are using that doesn't work and trying to figure out a approach. So probably by reporting it's 2618, it may not be the best approach. I think it might be. So maybe it would be something that would work for people to track new hardware, or do we just want to go by it? Let's go to a new upstream and figure out what we're doing otherwise. It depends. If you're handling the main controls for things that are going to the new upstream, it might not be the best approach. Well, like you were saying, we're never going to drop the 2618 on edge. That'll always be there and be the fault. So a new upstream would just be on the side. I think it's a question of would it be on the internal media then? That's to be determined. What problems we're talking about with those? How easy would it be to keep the kernels in sync? Do we run a risk of having a new upstream or a new kernel? Right. How easy would it be to keep it in sync and such? And if you have a pathway where you can make a change, like you're originating the ID stuff, you can do a smaller button for them to make it, then you can install it with the app. So Francis, in order to explain more about what is reasoning for the linear stall there was, so if the issue is that he wants to not maintain two branches or whoever to maintain two branches, is it still reasonable maybe to build a copy of the linear branch to install it with the Edge kernel? I mean, they can get really tricky. We do try to support old versions of the kernel for as long as we can. It's really hard to say what we're going to have to do with having too many changes and how we support the modules in the old process still works. So to say how I get to these. Another thing you need to consider is that newer kernels, many times, require newer user space like you did or something. Yeah. We had a problem with Star that didn't have the internal space, but now I think they're not squeezing away from it. I'm testing soon. But you may need an update on other things. Currently the new kernels work pretty okay on Edge, so it's not really a problem again. So as long as it's not going to be a problem in the foreseeable future for this time around, you don't need to worry about that problem. We need to look on a case-by-case basis, I think, because every time it can be totally different in the future. And of course, if you just notice that there's been a change in the kernel, it's not solid fire, because the kind of user version can continue just to remove that change. Yeah, it's really a case-by-case basis. If you're close to that, if you're close to that, if you're near a time where it's allowing you to set a kernel, then you can't set a day what you wish to do. It's the first basis to set a kernel, not the fourth step in quality. Okay, so I guess all we can really do is figure out what exactly we can't do. What do we know we can't do today? So, for example, would we want to do this without B-server and SIN support? Do we consider that a must? Do we have B-server and SIN in our kernel? Yeah, we could just ask you if you could speak a bit slower and louder today, because I'm really not too well still, so normally you can just understand American people who speak slower, who speak with a little lower voice like Troy, for example. So yeah, my question was trying to figure out things that we wouldn't do. Is one of those things, a kernel without B-server, too many negatives in there, what do we do an edge and a half with a kernel that doesn't have B-server within, do we consider that a must? I would not like to drop the virtualization techniques, especially a newer hardware which you buy to virtualize it. You want to have those techniques available. I think it might be a better approach to get rid of architectures, because Intel is the architecture which mostly has new hardware, and the other architectures maybe we can get drop some architectures for the edge point half kernel. Actually, coming back to B-server, if we only say that it's a small kernel and a smaller sub-work that we have of B-server, I would say yes, we keep B-server, of course. But if we say that basically we can't do B-server, we have to take it to the edge kernel because there's no B-server development happening the next year, what I don't expect, basically. Then I would say that what your difference would have to make for us, so it depends. We need to decide on the edge, but I wouldn't say dropping B-server is a total no-go. It's one thing I would like to avoid, but other things might happen. You don't want to have big regressions because it's not your question. B-server is a question mark. It's just that it's not a flavor. What we do is say we want B-server kernel which doesn't work then. That would be a regression. The same if you don't provide B-server kernels, this is... Regression in a feature set. I don't have thought of the future of B-server. I don't think there's any doubt that I like B-server and I'm not a B-server myself, so I have to do a profit from it. Drop here some architectures. It seems to me that there's a different chance that some populations don't have the support of B-server and B-server as well. To be honest, I've never really worried too much about other architectures being there. If the newer kernels don't work very well, then you still have the older one there. So the problem may just be if they don't build for other architecture that might consider dropping it, or is there another reason you're thinking? I'm just thinking is it even worth it seems like most of the problems are in the mental hardware and there's a little bit smaller problem so is it even more a problem than you actually have to release everything or those kind of problems? There are two reasons why we would like to have the same problems as everywhere. One is, of course, to be dead and say we are doing things consistent over all architectures, of course. If there are no issues, why should we drop it? Because it's probably even easier to just build it if it works. My question is just what's more important? If there's a problem that's coming up and we just drop it or we just make the extra effort to work even though it might not be worth it? What I would like to know from the kernel team is just that if you could just say that how many issues do we have for these other architectures? Do we have the management systems or is it mostly just working? Because I really don't have what, for me at my professional point of view that somehow it's all stretched out in the kernel team and always worn on. Pictures are through the market which doesn't give much input for the better. Basically, the build values are already already involved, because you have a kernel in unstable anyway, so the build values are going to result soon enough, I think. Well, around time failures there are bugs, there are variations or something. If someone has a mixed kernel that doesn't work, but builds, you can always use that. I mean, the build time failures, yeah, we fix them anyway. Yeah, and if the build values, some of the recent ones were fuel chain issues. I still think we'll be building with the edge fuel chain. So we're going to be dropping the signal on the edge to be building with the edge fuel chain, just to make it rebuildable. It might be a good idea to push that kernel from default update to sit for something like cv, so that we have more people testing it. Even if you build it with edge fuel chain. Yeah, it would probably be an older update because before we do it entirely. I think you need like an edge and a half for both updates. Well, it'll certainly be the, for the kernel, it'll be the buildserver.net and that'll be built, built into daily build. And of course, you can even now, because if you include it in the edge, it needs to be in the false updates anyways. You definitely can add a prototype to resources list. There is this automation list because nothing gets linked, that isn't the view by the status of this team. So that would be the test base for it, of course. But I'm not too sure if it wouldn't help to also have it added an unstable for more testing. Because we know that unstable is a large test base as well. People who don't mind so much booting sessions as more stable users. Simple questions. Well, they're not simple, but what do we name the source package? Because we want to have 1x26 there. Do we do 2x618 or 2x623 or whatever? I hope. I think that would make more sense. That's the most often the solution for me. And we'll need to deal with the meta packages. So right now there's 1x26 1x image 2x6-686 or something. So 2x623-686 something like that. The meta messages are to provide for a default kernel and if the convention is to keep the default as it is you don't need to provide new meta packages. But if you're running 2x623 just take the other number you'll want to follow ABI changes to security updates. We already have 1x1-2x6 meta packages as part of the main meta package as long as ball is the version of this. No. We'll say that again. 1x1-2x2.21-666 the model already exists. Oh, I don't think so. I have a passion to take this. Does it? No. So 1x, we think there's 1x1-2x6-6-6-6-6-6 2x666 No. I don't know. I think so. I know. About 10 of you have just need to invent new meta packages. Yeah. Some 2x623 meta packages. So I guess what the X people made is a good thing about the X people talk about what you want to do and then I'd like to come back afterwards and start talking about time frames. When do we conclude? People are interested in X server or X driver updates. If you are. The new X server 1.1.3 if we're a center on it. So we really can't back forward it. Very nicely done. So you can't back forward that. The only driver updates I've noticed that we maintain are the Intel driver 2.0 and the new NV driver both of which provide new hardware support. The Intel driver can build on server 1.2? Correct. So that could be back forwarded. And then NV should be back forwarded fairly trivially. Probably have few modifications to the code. The new server H as 1.1 2.3 is there. We could probably do a new one. So how large if you say back forward to H how large does it change? Do you think we should do a new package or do you think we should just fit trumps in the current package? NV we could probably just update and it's not a huge change. Intel will be able to do a new package because it got renamed anyway so it's almost like begging to be in the package and that way people don't get screwed. Basically I don't see necessarily correlation between the changes, between the current and it's full of might one if you have the extra is early or later available. I don't see reason to not just do them when we have them. Except of course I don't think that we need to update to kernel and to X at the same moment of time. We can't just do it whenever it's available. Maybe we should back forward to 0.0 I mean that's me in the bug experience. If we add a new kernel if we add a new extra and just a new package I don't see really what we are testing before. Maybe we synchronize the kernel packages and the X packages because their kernel changes are required for the new... Okay. So we need to have the kernel changes at least before the exchanges. No, unfortunately in order to talk to new Intel hardware we need to do a kernel driver to map memory to adjust the hardware. Is that the change that we can back forward to 0.618? I think that it was supposed to be in Edge or what? I hope that we can add one hour before we are ready to send. So we need the DRAM But that would be for Edge 2 or whatever. DRAM So we need the DRAM for 9.5 and G33 as well. The stack only goes so high that's about as deep as it is. At the maximum you are going to be at the absolute maximum you are going to need a couple of programmers which are trivial. DRAM, Mesa, Xover, and drivers. That's absolutely the maximum that you need. It sounds bigger than it is. Mesa is not small. So would all be getting new package names because they failed to run off and turn? No, the Mesa changes, the kernel changes and the live DRAM changes do hardware support PCI which is effective. And they don't depend on new kernel? No, they depend on it. Is that something that's just not fair anyways? Should we just do it as soon as possible? The base says actually do we depend on new kernel? We need to get a new package name I guess for preventing people from creating new kernel packages. They don't need a new kernel. If we haven't done anything in the first kernel but they need the driver update kernel driver update. So that you mean we can do the changes after we push them out to some longer quantities to some longer quantities. But doesn't that mean that you would need to update the current 2.6.18 kernel anyway because if you push out the new X packages without updating the current 2.6.18 kernel you would not be able to use X anymore with that current kernel. And we are going to go into updates that we in Damian are going to so we force our users to update the kernel. Which part do you mean? We are going to update the kernel now for L1 anyways and my basic assumption is that we will still go on in an update in 2.6.18 regardless of things like device IDs. Yeah, I agree. It depends on the extra sum half kernel or not. But it means that it will depend on the H0.5 kernel for these X changes. If you want to do them you also have to update the 2.6.18 kernel because you cannot force people to switch to a 2.6.23 kernel just because you want to update X. Well, it is backwards for bad changes. The new X can work with the old kernel and it needs some good data. There will be some limited functional limitations. As far as I understood the updates of the 2.6.18 kernel are enough to last as packages. It doesn't I don't think so. The changes that are necessary for the new hardware support are new PCIDs and small amounts of code that are dependent only on those PCIDs. So there will be a switch statement for the new PCIDs and the new PCID will have different code. So those changes are in line with new hardware support. So there will be no regressions for any current users? I think that's the goal. So the kernel drivers do not introduce regressions for existing drivers. I think that's something we can do with 2.6.18. I don't see a reason to make any special things about any X driver. What? My father leaves the box. If new X software introduces no regressions at all for current users then I don't see a problem. The new kernel modules. The other two pieces that we need are changes to the 2D X driver and we have two routes so we can do that because the changes to the new hardware are on top of the X or 2.0 driver at this point. Ubuntu, Red Hat and Novell have all taken those changes compared to their old X server 1.1 based drivers. We can steal those drivers and ship new packages on top of Edge. If we want Ubuntu maintenance because all of a sudden now we have a fork. Now we have the old packages and we have the new packages and we can maintain essentially two total parallel tweets of packages. I don't know if we have Danwood but the other piece that we have been updating in similar fashion is the Mesa GL library. Again the hardware support for new Intel chips is on top of a year and a half, two years of development of Mesa and so back porting those has been done by other distributions. Do you want to take their patches review them and incorporate them into our stable series as well? For what sort of reason? Mesa and all of them It's pretty solid. I think it's been pretty good. I think the server is a lot because the server has been more sensitive than Mesa. Great stuff accidentally. We have a bunch of regressions of the current Mesa that are breaking the test speed. The other option in the back porting is to update the server. The other option in the back porting is to shipping desktop bits but to some extent that doesn't seem appropriate to me. It seems appropriate for us to get basic hardware functionality to make sure that people can get their systems up and running and then decide if they want new features support including fancy hardware support they need to move to a new distribution. I think that's a reasonable position because obviously SnowVal and Red Hat are in a different space but they're guaranteed five years of support and those developers are in a world of hurt right now and while they have staff that are in fact Intel has paid staff to help them with that I don't think we're in a position to be able to offer that kind of support. What new hardware did we feature? We have this new logic. Some parts of it and a bit of new logic for our system but of course we can't say we will always have the better end of stuff so I think that the extra one half thing is just a good middle position between everything and nothing. I think my goal for the ongoing stable support is to make sure that hardware that I ship today we can install. That's a good thing. I think that's a basic level of functionality and that people can use the system in some limited capacity and decide whether they want to go to a more recent distribution without having to... If I were to describe in one sense what I think is going to happen is to show that Deviant can add hardware support so I don't want to I think the first time around I think the first time around we want to add hardware support definitely not risk breaking anything just to show that we can do it right. But I think that needs to be tempered by the cost of what the hardware support is going to be for something like the hardware support for adding generic class-based HCI drivers for it absolutely I think as it approaches the hardware support but when you talk about adding Intel 965 graphics driver support we could do it but it would need a new extra What if we just did skip the base on it and just give it to you I mean it's crap but it's an all sort of package and you say well at least you got this if you're really honestly newer I think that might be appropriate where we offer limited functionality at the point where people can use the interface that are familiar and friendly but comfortable with to get to installing this... Being able to get to a useful 2D desktop from Edge and whatever so that you can then make the decision to do the testing seems like a reasonable place to try and go I know that one of the challenges we as a distribution is the fact that as recently as now there's a whole new ration of hardware that you just can't install on Edge so... So Zovell asked on IRC if the security team can think about these updates as for the kernel I'm happy with maintaining the second one assuming we can make it as close to drop as large support as possible I won't be happy about maintaining four kernel source trees at the same time but when we go down to two or just to sort of overlap what do you think about Edge Well the parts we're talking about the facts we're talking about now are debilitating on people on desktop with good problems recently it's mostly being on all the common stuff which wouldn't be effective with the common stuff and so I don't think Edge is the main problem here with the kernel we should probably go for something less than the 12 months of close to high support being provided for the common problem so this should only be a step towards landing for eventual next release and honestly it'll be easier to maintain the Edge kernel than the Edge kernel so that you're happy with it security wise? security wise I know there's a lot of institutions that have not yet switched to an Edge do not plan to switch to an Edge for the foreseeable future but are going to keep on running search Limitly search limiting security support for kernel like that going to have a major effect in the usability of Debian for large institutions well then you have to switch to Edge but not for Edge on behalf would you simply do enough resources if you asked me to choose I would say ok let's not include a new kernel Edge but let's do it continue security support wasn't the proposal to have a shorter security support cycle for the Edge on a half kernel? ok keep that timeframe for the Edge kernel yeah and my comment was once we get past right now doing the start support is going to be very difficult because I have to manually appeal every architecture once it gets to it's just too early and the Edge on half kernel will be easier to port to in this new world I think it won't be too much to keep going with it as long but you know I think 268 gets priority no I'm just going to start back to the X issue it's probably too early but what is the situation with the humidity I believe Julian you mentioned that we're going to add Intel Alur and NV oh it's not ready but probably by the time that it's in a half no I don't really know I haven't heard of it but it's really early days it's just announced like a week ago so it's really early days I don't know that it's really ready to ship to people it's very not ready do you know about the new world models this is like yeah I really need proper maintainers no one in the X-Track Force has an EVO as ships supported by an EVO none of the X-Track Force members have an EVO so we haven't really heard of the work I've heard a call for new world maintainers two people responded but NOAA has not really followed up on that neither has this other guy do you want hardware sure if you have PCI Express hardware send something out to the X-Track Force and if you have a staff to do the maintenance for this I can buy you over okay I'll pass it to Andrew I'll let you know if it's a hardware problem I can fix that I can't fix the staffing problem right I have to work on it yeah so that's been an issue we haven't had the hardware that's easy mostly just PCI Express ports okay so that's your answer what is that is there a list of drivers that was present in the X-Track Force that is no longer present in the current set problem I've had problems from the X-Track Force because the module was lost by situation and like the old firmware firmware I got doesn't work anymore that kind of problem hmm? well I didn't see for the hand made upgrade of like back port of Carlos so no I didn't there is an issue I know the BCM 43 FX module which is for Broadcom wireless found in Power Books but they changed basically they're using a newer firmware now by Broadcom so the new gallery depends on the newer firmware so I've been very familiar that's an issue so no matter I don't have that list we should probably make that list we got a complaint from the DGDU user that his old X-Track race controller doesn't work anymore and then we have the TV input it seems like this old current module is no longer present in the current and we have no idea what the new name is and it doesn't act that so maybe it's just published um you can just make it different well sure if I had the machine yeah well I'll be there you're talking about actual file differences in modules sure that needs to exist but let me tell this back to this conversation a little more what if 2620's whatever doesn't have a certain driver that 2618 had do we consider that to have if it's required to support for the hardware but 2618 is still there so the hardware should drop the driver so basically we're talking about a new system like an Intel newer one that gives a hardware that isn't supported in the newer current I don't think that's a relation actually I think that's the same it's the same as that we hope to be so if you want to like it if you can afford it but not at all cost so it's important things it's a big game as the name when we go to a newer current version but it's also a kind of niche piece of hardware if you just go to the hardware it's supported for PCI as graphics I would say yes to the question and hardware I would say no but I just have a piece of hardware that I expect that they can ever use it might enough document it as a nice note so my personal perception is that the transition from Sarge stable to Dutch stable was difficult for some people because of things that we decided to change and what we're building and delivering might not be included in the keyspan the real question is are there any meaningful reductions in the list of delivered drivers from the 18 to whatever that's been supposed to place for a pension and a half I don't know the answer if some truly obscure something got dropped by from.org upstream between those two versions I wouldn't spot that too much but if there's something where we've made any decisions or fixed the number or we forgot to fix that and took something else away for a pension and a half yeah of course because the situation for example with the keyspan and serial stuff the motivation for taking that action was quite clear to everyone for reasons that rationale understands what the point is but it was a situation where one day hardware that many people have and use in the system used to work after they did an update and that's the kind of regression that I think you have to be careful about sort of doing intentionally that's the way if you don't know if you were already here when it was casted but we are definitely not intending to change the defaults so that people get the new kernels out making a voluntary choice about it and they are still supporting the old kernels so I'm not as much concerned as it would be because of these languages now there may be a choice to make between do I want this new thing or lose something if the new one breaks they can just go back okay now it's all go back to your question and the action is on I mean some way you make a list of what we'll say on this not that much is that as simple as a configure for something no I always think that the configuration can change names I don't think we can mind play with the difference it would be great if someone you cared about this can get involved in at least now yes it's cool basically if someone has a new system that doesn't work with the current kernel an adopted kernel that doesn't work with the new kernel the kernel doesn't support him how can we support him there is a kernel that supports him how can we do that I don't think that anybody in the current scene is interested in developing vipers such as Vopset so all these vipers we have to make a hard decision we either syspun or syspun and then we have to just decide which is less or bad of course you prefer to just support all so if you have a question we don't say when we can either support syspun we just say we don't support users with all we just support but has some minor stuff to support I think it's easy to answer I think we have to have a discussion about that when we really go to the decision survey what is our open currency which is a danger for us which are the things to be gained we have to make a decision I don't have enough I don't see what will happen with the kernel in the next half year to make any decisions about well let's document inside the kernel source tree in the schedule of future renewable and it only lists really really obscure junk they are extremely cautious by dropping existing drivers they even maintain the whole completely obsolete open sound system back from the old 90s just because some of the obscure legal hardware nobody knows any more is not supported by ALSA so don't take that back to the issue the main thing is whether there are rewrites of drivers like you had with Macerate when new drivers support really ancient hardware not most supported by the old driver anymore because basically the guy who did the rewrites did not have access to that ancient hardware anymore and also had something like I don't care enough for new support 20 year old with great support just the same with PCMCIA there was a major rewrite of PCMCIA in user space stuff those are big transitions and all stuff does get lost in those transitions but that's a dream's choice and if people want those re-questions fixed basically if they have the hardware they have to get involved and of course it's not the ASA cache it's the KVG cache and then it's the ASA cache and you have to do so one thing I'm not sure the partner should just be enabled for points like this I don't think we want to break upgrades between edge and edge yes especially with the HDA SDA changes which we're not prepared for at the moment speaking of that there might be a little on topic for this but do you think that the persistent gaming stuff will help solve that problem Colin told me earlier this week that he has good things for that in the I in the I we need to work together with you guys the current team to transition in upgrades support and that may even involve getting it into an edge point release at some point to have things own people's system as much as possible but it will be a major edge landing upgrades attic so 10 minutes left should we is it too early to start talking about time frames for this all I know right now is 2621 now but beyond that there's half what did you say if it's supposed to be edge and a half then it's a monster I think we need to get quicker you need to start quite quickly if you want to think the oddest thing I've been mentioning is just doing continuously there are two things that we could include in edge R2 which we don't have so I think we should do that as soon as possible just that on my base one is now mostly close so it's just R2 which would be okay and then we could get at least a new little harder version of edge and I hope we are able to get out edge R2 in two to three months that would be good and if we have that I think the most I hope that's all there's more to it and so it takes a new quality it should be another whatever 5 months of that 8 months from now I think my default would be to want to take 2623 as soon as it's unstable and start making a back port branch sort of probably 2623 can I go to those releases to break things separately like 631 was breaking many stuff because of the dynamic these things and you don't know what's going to be on 2323 but when it will be at a pretty stable release for example we know that for sure but we don't know that yet it might be that we see that other distributions start going on 22 when we do that actually I've learned not that so much if AppStream tells us that this kind of release is going on at a stable release so we have to all focus on any release or basically you will have but when they say the next one is going to be very unstable you can't believe them actually that's too far and they said that for 21 yes actually we are going to take it to 21 of course when do you expect 23 upstream they've been pretty regular I believe it's every two months are they doing upstream releases 2 to 3 so 22 I have a late summer I would guess people on the current I've heard I've seen some of it come in September it would seem likely that it would be before or right after the historical and I want to drop a new release just before I don't know September September I think it's about time to start September it's going to get unstable and then initially it will it's happening at the same time as long as it's coming from Europe and in Cambridge this year it's not just next year so all of this 88 changes that means the device that is happening after so after so we will see the changes anyways so we don't have to care about that now are we going to try to get the same kernel for a decent time into unstable first yes I'd like to use unstable to the early architectures building and maybe delay a possible next version in unstable to get an extended standardization period for this kernel that we target for H&R yeah either way I would ask obviously watching unstable and emerging stuff I would defer what I thought seems logical to me if you just had it like you would have H&R's edge code or which H&Rs that need further trust put an unstable, maybe stable stuff that was in its occasion get it into testing yes so then we have all you really have to work with the insoluble kernel thing on this to make sure things happen as we wanted basically the current kernel thing ignores testing completely which sucks that's not true, water is also part of the kernel team the people that manage to release us don't really ignore testing I'm not sure they ever know how to manage this because it's a kernel but yes they know what you mean but yes they can't now say anything about some people oh I don't care because you don't know how to develop I am are there any efforts going on to make sure that the SIT unstable kernels actually are buildable in that at the moment they are not because they depend on unicorrigals and all those things yeah I mean there's certainly we're not going to take the edge kernel I mean just recompile it there will be a branch of stores to deal with that stuff and I think while these have been when we have already done this dropped kernel package dependencies back with the old build system that we used in Edge and just dropped it to 21 or 23 or whatever that's all to be determined we'll figure out how to make it buildable and install it that'll be the same I would suggest to make them back portable like with only our rebuilds re-build the system actually working at when you talk about SIT kernels you can talk to Wally about that what are the edge kernels a lot of things have been blocked for a long while because of the libc transition so testing hasn't been as up to date as it would normally be that's quite normal acting just after a stable release my best major change is happening all over the distribution I don't think the fact that the unstable kernel can buildable for a while is a major issue interesting for better reason as far as I can see from that packet it does different semantics of read-link that enforce the new coroutils dependency and I'm pretty sure it's possible to write a transcript of both Edge and stable for read-link we're at a time now I'm sorry I don't have questions or anything but I think the only question that still is open but have you just left it open from now would be how do you do this in Stoner I have one small question where is the discussion fraction happening to take place on this is it getting released do you care actually we prefer to not have too many discussion on the least so we could take them in the well but if it's necessary to there's not so many people because they're still in switch to release or watch out or whatever you like because we like to avoid the discussions happening on the least because it's hard to tell if you're going to stop discussion on this but I agree that just having a kernel is probably not the right because it has a good quality impact how about the value well I guess that's it thank you


I don't know about good smokers I love those guys The first thing is not the first thing The last thing Because we are winding up So if you have anything you want to tell your rockers Be full We go because Unfortunately this show we need four hours I don't know Two hours is never enough So we are watching two guys Just check out our pages Something big is really coming It's coming down somewhere It's never happening in Kenya We are looking forward to that Very soon come this April And then remember I will be metal first April is here you guys Let's pop Let's save up And we have You know there's this event that happens at Crooked Cue Like every other month The next one is coming up on 6th That is the 6th of April We are going to have Power Slide And Yeah Yeah But if people don't believe us We just wear them Walk as we explain ourselves Yeah We are going to have straight line connection By the way he is one of the organizers And Power Slide They will be performing at Crooked Cue It's actually 400 Bob And 600 Bob at the get It's 400 Bob Yeah in West T Oh Oh Crooked Now I have Edna Mwangi Hi guys I'm locked listening from Jakaranda I wish her to you Edna Please play for me Suicidal Hate By Blue October Oh that's one of my faves by the way How did you know I wish her to you I'm locked almost somebody who knows Kupenda's locked over Now it's been fun hanging out with you guys We are going to come and hang with us We are heading over to Machakos Club Euphoria We are going to shout out to DJ Tiasca He is in the building I will be MCing and he will be holding us down And then you are not ready for this And I will be handling the drinks Yes Yes he will be handling the drinks I will be MCing DJ Tiasca He will be on the 1's and 2's It's going to be fire, it's going to be late So shout out to Club Euphoria He will be here So shout out to you By the way I wish her to Mori He is on the camera He has been holding us down Shout out to you as well He's been the sound manenos I love to have family Our director He never lets us down He's a guru We are going to come through He's always there But before we go let's play you our fresh man Today on Freshman We have a Freshman song So Freshman what happens to play you a new song Like not really new new But a song that just came out maybe a week a day But today we are going to play Modest Mouse The song is Poison the Well But don't poison the well in real life That's not cool But the song is Poison the Well By Modest Mouse We will rock you later but remember The show airs every single Saturday 5 to 7pm And then we have a rerun On Tuesday 8.30pm to 10pm That's right Tomorrow we have And then we have tomorrow The guys who are We have Gospel Rock It comes to you every single Sunday At 5pm Now let's say Mashi Mashi Pop House 8pm Yes we've got you covered Each and every single Wednesday 5pm Of nothing but electronic music We've got you right So we're going to see you again next time If I didn't shout you out sorry If I meet you on the streets call me Say hi it's gold to have you And we'll see you next time Bye enjoy your weekend


It's a great pleasure to be here this morning with all of you and to be on the traditional territories of the Coast Salish peoples to celebrate sport in British Columbia and in particular the largest multi-sport event ever to be held in Northern British Columbia. This is the first time British Columbia has ever hosted the Canada Winter Games and it's right in Prince George. It's not just about sport. It's a fantastic opportunity for Northern British Columbia to benefit both economically, culturally, all of those things. It's something that can bring the type of attention to our province that you just simply will not get in any other way and it really builds on the theme of Canada starts here and Canada is going to start in Prince George in February of 2015.


One of the oldest surviving algorithms is that a kashar ibn-laban lived around 1,000, about whom very little is known. Ibn-laban describes the computational procedures on a dustboard, essentially a portable sandbox where figures could be written, then erased as needed. So for addition, Ibn-laban describes the following procedure. The numbers are set down, aligning columns corresponding to the same orders of magnitude. The values in the columns are added, beginning with the highest order of magnitude, and as numbers are used, they are replaced. And it helps to ignore all digits to the right of the working column. So for example, Ibn-laban describes the addition of 839 to 5,625. So we'll set down our numbers. So we start on the left, and since 6 plus 8 is more than 10, we actually add 56 and 8 to make 64. Then 2 and 3 make 5. And again, since 5 plus 9 is more than 10, we'll actually add 55 and 9 to make 64. Subtraction can be performed in a similar way. However, Ibn-laban avoids this borrowing that we do, which by the way is a terrible word for it, because borrowed things are usually returned, and what we borrow in a subtraction is never given back. So using the same numbers, let's subtract 839 from 5,625. So to subtract 839 from 5,625, Ibn-laban notes that 8 can't be subtracted from 6, but it can be subtracted from 56, and so we get 56 minus 8 is 48. Again, 3 can't be subtracted from 2, but 82 minus 3 is 79. 9 can't be subtracted from 5, but 95 minus 9 is 86. For multiplication and division, Ibn-laban describes the following procedure. To multiply 243 by 325, first, set the last digit of one factor below the leading digit of the other factor, then multiply the leading digit of the upper factor by each of the digits in the lower factor, and once you've found this partial product, shift the lower factor. We begin by multiplying the leading digits of the upper number by each of the digits in the lower number. It helps to read all the digits above and left of the working number. So the leading digit of the top number is 3, so we'll multiply each digit of the lower number by 3. So 3 times 2 is 6, which we set down. 3 times 4 is 12, which is added to the 60 to make 72. 3 times 3 is 9, which is added to the 720 to make 729. Uh, question in the back? Isn't it 723? Ah, that's a good question. Now, here's the thing you have to be careful with. The problem with using the Dust Board, as Ibn-laban is describing, is that there's not a clear distinction between your partial results and the numbers you're working with. And in this case, the important thing here is that this 3 is actually part of one of the factors, and it's not part of the partial product. So in fact, our partial product at this point is a three digit number starting with 7, 2. So we do read it as 720. And if you're asking the question, well, why wouldn't they, and then providing some method of distinguishing between the factors and the partial product, then you're asking the question you should be asking for everything. How can this be improved? Because at some point, everything had to be invented. And if you're looking at this thinking of ways that this algorithm can be improved, good, because all human progress comes from somebody saying, this can be done better. But to continue with Ibn-laban's procedure, we multiply 3 by 3 to get 9 and add that to 720 to get 729. Then the lower factor is shifted. And we repeat the process. Since we've taken care of that first digit of the upper factor, our first digit is now 2. 2 times 2 is 4, which is added to the 72 to make 76. 2 times 4 is 8, which is added to 769 to make 777. 2 times 3 is 6, which is added to 7,770. Remember that 2 is part of our factor and not the product to make 7776 and shift. And the only digit left in our upper factor is the 5, so we multiply 5 by each of the digits in the lower factor. 5 times 2 is 10, which is added to 777 to make 787. 5 times 4 is 20, which is added to 7876 to make 7896. 5 times 3 is 15, which is added to make our final answer. Division is handled as the inverse of multiplication. And note that in the product of two numbers, the leading digit of the product will be above and left of the leading digit of one factor. So our setup will set the leading digit of the dividend above the leading digit of the divisor. So let's divide 5,625 by 243. Again, Ibn Le Bon really likes this number 5,625. So we guess the leading digit of the quotient 2. And again, it helps to read all the digits above and left of the working number. So when we were multiplying, this 2 would have been multiplied by each of the digits and added to the partial product. So now we'll multiply this 2 by each of the digits in the divisor and subtract it from our dividend. So 2 times 2 is 4, which we subtract from 5, leaving 1. 2 times 4 is 8, which we subtract from 16, leaving 8. 2 times 3 is 6, which we subtract from 82, leaving 76. And shift. Now we guess the next digit, 3. And again, 3 times 2 is 6, which we subtract from 7, leaving 1. 3 times 4 is 12, which we subtract from 16, leaving 4. 3 times 3 is 9, which we subtract from 45, leaving 36. And this gives us quotient 23, with remainder 36. In the division 5,625 by 243, we obtained a remainder of 36. While continuing past the whole number units might seem to be the obvious next step. This wasn't taken until the work of Abu al-Hasan al-Uqlidisi, who lived in Damascus in the 10th century. The only other thing we know about him comes from his eponym, al-Uqlidisi, the Euclidean scribe. This suggests he made his living by making copies of Euclid. And among other things, al-Uqlidisi solves the problem, increase 135 by its 10th, and the result by its 10th, and so on, 5 times. So to do this, he sets down 135, and marks what we call the unit's place. Then he sets another 135 below it, but shifted one place over. And adding will give 135 increase by a 10th. But we want to increase this by its 10th, so we'll set out a 1485 shifted one place over. Then add. Then lather, rinse, repeat to complete the increase.