Okay, so perfect. Welcome to this community call from the open-air provide, so targeting always the content providers, managers, those that are managing repositories that we have in our infrastructure, in open-air infrastructure, those that are managing different kinds of data sources that we aggregate content and we provide services. So it's always a pleasure. So we didn't have the community call in the last month, but we do this in the last first Wednesday of 2023, the last community call of this year, which is a great pleasure. The idea is just to provide you some of the latest developments, novelties regarding specifically functionalities from the dashboard, but also the other components that are related with your participation in the open-air infrastructure and the service itself as the provide service. So welcome all and I see that already more people are joining, so we'll progress fast with this introduction as we want to cover a topic and the novelties on the open-air graph. So some relevant updates that I think it's important for you to be aware and we have our colleague, Tanasis Verbal, is that we'll detail those updates. I'm not sure if and Claudio, sorry, will also join you, Tanasis. But so as Tanasis have a limited time, so we'll dedicate the first part of the meeting to this and then we have Dimitris Piarrakus to also to update us on the user statistics. There are some relevant updates about the reports that we would like also to share with you and then we can first discuss the first half with Tanasis about the graph and then Dimitris about the statistics and of course, so we are available to discuss any other issue that you have. Just two minutes to highlight some recent news. So we usually share with you what is in production in terms of our graph, so the index and stats update is from the 23rd of November. It's important to highlight that, so we want to do this update as you know every month, but we did it in 20 I think around 20 of September. We didn't have an update on October and now we have this update, so it's important to highlight this that it's not a one month update is in fact two months update, so it's relevant for you to be aware of this and in the coming days you will receive because this is a subsequent action, so you will for those that have notifications from the broker events, for example you receive those notifications. Important also to highlight some things related with the full text. It's always important to share with you that in the terms of use you can update the terms of use related with the metadata harvesting and with the collection of full text, but so we are now trying to improve the information available about what we collect and you can see in explore already the numbers, so if you go to let me share here an example that I opened just so in the can you see my screen yes you still see my screen okay great if you see the landing page of your data source you will see that now we have the information of the collected full text which I think is relevant for you to be aware of the number of records that we collect that you can see in the aggregation story and the collected full text that I think is important. It's quite relevant in terms of the results of some of the inference system that we have is quite relevant for example for the links to projects as you know some of your data sources we do those links mainly from the full text and not from the metadata. So if you have questions we can reply to those questions after the presentations and we can discuss a bit that and I will also just want to highlight as I have here to slide so this is what you have in you can see and we just want also to highlight that our intention is to put also this information available we don't have it yet so you can see it publicly available in explore but our aggregation is to improve the aggregation story that you see from your repository we also improve now what you see is the what we collect what we transform and what we and the version that is indexed but we want also to put the information available here to to have for you all the information gathering the same the same place so the the idea is here in the dashboard where in the tab aggregation history is where you you see this information is where also you see when was the the the content that is indexed from your repository and available in production in our in our explore service you can see that but our idea is to improve this please also check because andre together with other colleagues did a good work to put some more information here in the in this right area of information and help so where we explain what what we mean by aggregation stage collection mode etc and you can see also some more explanations in some useful links if you have doubts about what you see and how to interpret this this information i think you can have that quite well explained so this is one highlight that we want also to share with you the other one is just to quickly to remind you about the campaign that we did about onboarding data sources and research products in the yosk marketplace there is a webinar and there are relevant instructions for you so andre can also share these links with you here in the chat for just a reminder because we were pushing you that are part of open air too it's quite easy for you to be also onboarded in the yosk marketplace to be part of the research product catalog let's say and so it's it's it's you if you didn't have the opportunity to do that so you have instructions and the webinar to better explain you and also to let you know and we will have novelties about that about the guidelines working group in the coming year but the open air guidelines we are in a in a phase that we we want to to have it as a community driven global initiative so we set big kickoff this in the open repositories last tune in the in South Africa and we will start working in a in a in a working group not only from people from open air but a global working group representatives from different initiatives from different parts of the world to be part of this working group and to govern the the interoperability guidelines from from from open air okay and with these explanations in these novelties well i will come back to this report that we published but we intend to give this information at the end i give the floor to tannasis to present the novelties about the graph so those details that i presented right now please put it in the chat if you have doubts or open your microphone at the end because we have time to discuss to clarify some of these issues so tannasis the floor is yours to to to share the screen or to share the the website from from open air graph to okay i like some of the developments from from our graph to our colleagues here okay thanks Pedro for the introduction so i selected to present a couple of new developments regarding the graph some that are important ones and that are expecting expected to improve the coverage regarding some information that the graph already collects so before starting let me also give you a quick reminder on the whole workflow to produce the graph as you all know we get the information from the onboarded data sources based on the open air interoperability guidelines that you provide to open air through the open air provide service and we also include information from some instrumental data sources like crossref data site microsoft academic orchid etc we aggregate everything we also exploit information from pdfs and xml that contain full tags of publications to extract enrichments that can be included in the graph through mining and we also de-deplicate all the publications and all the research objects we further reach uh usc inference the records that we produce for example if we have the information that the particular product is relevant to an organization and we know that this is a department of another organization we also infer this connection and then we clean and finalize the graph production and as you'll know then this graph is available through the public graph data set and the public graph api the api is updated each time that we have a new version of the graph this is in most cases once in a month and the public draft data set graph data set is being updated once in each six months and these data are also used to provide the the required information for the open air added value service like the connect the opener explore the monitor the open science observatory and others and also for third-party services that are consuming the opener and the graph data to provide useful functionalities to various community at large and other related stakeholders and of course through these services we also get some user feedback that is also included inside the graph data and based on all this uh based on this workflow we are now able to produce a graph that contains metadata and interactions for more than 170 million publications and more than 59 million research data sets and more than three hundred thousand research software and also we are covering other research products millions of other research products so you already know about all this so I would like the first development that I would like to to discuss today is the one related to the production of the fields of science the fos classifications so what is this this is a classification of the publications of the research publications based on the field based on the discipline the topic that they are related to uh so uh open air has this collaboration with Athena research center and the research team there that they are producing uh classifications for the publications they are using metadata and the content of the publications to identify to reveal the most related topics the more the most related fields of science of each particular publication and they are giving these classifications to open air to be included inside the graph and of course this is a very valuable this is a valuable information in many applications because for some areas of application like for example research assessment it is important to know the field of particular publications until now we have about we have about 40 million publications that have been already classified with at least one such field and by the end of the year we expect to have classifications for more than 100 million publications now something important to mention is that these classes these are not just some topic names uh these are classes that come uh from a particular taxonomy the sign noble taxonomy that it is uh maintained and produced by this Athena research center uh team that I mentioned uh it is a taxonomy that has multiple levels uh in the top levels you can find fields that are pretty generic like for example in this case here medical and health sciences so there is a small number of generic fields of science that are covered from level one then in level two you dive into a more specified more generic fields like here the clinical medicine and as you go below that uh the topics become even more specific and for the methodology that is used to produce this taxonomy is based on well-established taxonomies for scientific fields and as we go to the lower levels the team that produces these classifications takes into consideration techniques like topic modeling and then they are working together with experts in the respective fields to provide some meaningful names to these fields uh so uh when we are uh saying that uh we are providing classifications for fos for different publications in the graph uh this means that uh we have these classifications in different levels uh so uh you can get the uh right now classifications and until level four if i'm mistaken and by the end of the year we expect to have uh classifications in more depth at least to some uh domains for which these levels are are fine grained and worked by the community um so this is the first uh the development that i would like to discuss uh the second one is relevant to the affiliation links that are included inside the graph so uh one information that it is again important in some domains uh is to identify connections between research products and organizations research organizations we call them affiliation links and although this information is very useful because for example if you don't have these links some of the opener services that are currently provided like the opener monitor cannot work properly the coverage is very important in these cases because if you don't have the link then if you want for example to get a glimpse on the productivity or the aggregated impact of a particular organization you are missing a lot of content if you don't have a large coverage in these affiliations uh so although this is a pretty important information it is not always present in large scholarly communication data sources like for example Crossref it is provided but not for all the entries and even in cases that this information is provided in in usually it's provided in the form of affiliation strings which are strings that are described in particular organizations something that it is not always easy to map to particular organization and to know for sure that everything is related to this organization on the other hand a lot of you may already know that there are some initiatives that are providing persistent identifiers to organizations for example the error initiative provides the error IDs and if you have the error IDs of the organizations that are linked to a particular research product that is a very valuable type of information this is exactly what we are trying to do for the graph so we are trying to identify this type of connections exact connections that we know for sure the which is the organization the linked organization to do so we follow multiple approaches and at the one hand we are using full text dx and xml that we are collecting from the publisher websites to extract affiliation strings and then map them to particular error IDs and on the other hand we are also gathering affiliation strings that are provided from Crossref and PubMed to do a similar job of course for this work to be useful it is very important to have a mapping algorithm between affiliation strings and error IDs that is pretty precise our engineers have developed a such algorithm we have preliminary evaluation results that show that the precision of the affiliation links is pretty high more than 90% and the recall is also more than 85% which is pretty large and based on this activity between August and November in the versions of the graph that we had released during this period we experienced an addition of 34.3 million affiliation links that come from PDF mining 25.8 million links from Crossref and 23.5 million links from PubMed of course there are overlaps between all these sources and of course apart from this we already had the affiliation links provided by Microsoft academic the problem is that Microsoft academic has been discontinued and it is important for us to follow such approaches like those that I discussed because otherwise we were going to have a small coverage on the affiliation links for the years after 2022 that Microsoft academic has been discontinued in general we now thanks to all these initiatives we now have inside the graph affiliation links for more than 79 million research products in total and of course this number is expected to become larger month by month because we are using new versions of Crossref and PubMed and because we are processing new PDF files and with that I would like to conclude great Tarnas is many thanks so this is our very good news about the graph that are really contributing to fill some gaps in this ecosystem so thank you very much so we have three or four minutes for questions please add your questions open your microphone or raise your hand or just put it in the shot in fact Pascal Dengis already asked a question are the fields of science also attributed to other objects than publications like projects or datasets I think for datasets yes but not for yes yes for some of the datasets but not for all of them I mean the large coverage is related to publications because the current approach the signable approach is focusing on publications so it uses also some information like for example citations and references of these publications the venues that they are published so they are using as much information as possible this does not mean that they are not producing also some of these classifications for datasets that have DOI but currently limitation of that approach is that it refers only to items that have connected DOIs in the future of course this may change but currently the majority of the products that I mentioned that they get a field of science are publications and in fact I think I don't think so I'm not sure about that but I don't think it's our intention to also to do the same for projects it's only to research outputs no this is the original idea yes but if you have the fields of science for the publications based on the publications that each project has you can infer the fields of science that is related to this particular project so if this is something useful we would consider applying some kind of inference there to do this okay any other question clarification needed about these three highlights that that Tarnassis gave about the graph always the visible part of the graph you can explore a bit in explore.opener.eu but of course you then you have the also the website that Andrea already shared here where you can understand better the workflows and all the novelties in the news Pascal are the SDGs also attributed now are still in beta okay yes they are I mean okay in theory where when we are providing the SDGs and the EFOS in explore we say that this is in beta but right now we can say that this process is pretty mature we have tested it for a long period for several months we have SDGs and EFOS for our products the coverage has increased also for the SDGs I don't remember by heart the numbers right now I selected to focus on EFOS but something similar is also true for the SDG classifications as well they are also being produced by the same team the team using of course a different classification algorithm but we still want to receive feedback directly from explore if there are anything that people want to report I remember that we asked that in the past for the fields of science and also for SDGs maybe SDGs is more relevant now but Silvia, Adriana and Tomescu what standards are important are important sorry not important imported and okay and Pascal so what standards I'm not sure if Silvia is asking about what we aggregate here if it is related with one of the updates if you want to standards regarding which aspect yes if you want to clarify so if you can expose the ontological base at the ontological foundation of the graph did you use for us for example friend of a friend or doubling core for linking data how we include the information in the graph in general or how we consume the field of science that or the affiliation links are you referring I think it's the basis of the graph what we have in the graph okay okay in the graph everything that is supported by the open air interoperability guidelines if we have repositories, publishers, journals, registries, aggregators, pre-systems that are following the guidelines that we have in place maybe someone can include here the link then if we have a such entity a such data source that is aligned to these standards then we can consume from them regarding the other the instrumental data sources we follow different approach because we include them to apply additional enrichments and to increase the coverage in particular aspects that are important for the graph we put some effort in developing our own workflows for integrating them and aggregating to the context that we get from the onboarded data sources okay thank you thank you so I think we can move now so when the Tanasis you are free because I know that you would you need to be free three minutes ago already you want to say something to finish no no thank you for the invitation and the policies that I couldn't make it for the whole meeting if there are any follow-up questions you can send me an email or you can forward it here and I think that Pedro and Andre will let me know thank you all for your interest yes thank you very much Tanasis and so feel free to ask more questions if you are not willing to reply we will ask Tanasis so Dimitris you can and I think you have slides also do you want if you want to you can open just a clarification because this is why we have these community calls for people to feel free to ask questions so we have always so experiences providers that's experience providers so we can always ask and clarify things so feel free to ask questions um this question that's Sylvia raised Sylvia Adriana raised it's uh so it's it's relevant just just a clarification and then Dimitris feel free to start and you can Andre already put the link for the guidelines so when we mentioned metadata interoperability guidelines for open air we didn't reinvent the wheel of course we rely on well established standards so double in core is is there if you if you see so alignments with data set with serif with control vocabularies from co-art and others so this is what we try to integrate in a in a in a comprehensive way in our guidelines and then ask those providers to expose the metadata uh compatible with our interoperability guidelines just to to clarify that okay Dimitris now so the idea was also to highlight things from the user statistics those that are benefiting from user statistics all those that can benefit and you can always come to the dashboard and enable this service Dimitris will follow up with you about this but so we have we will have we have some lovelies that are important that so we can share with you yeah thanks Pedro I will try to present the new development in the unit scouts service in order to incorporate to accommodate the the new counter release five version of this of which is the standard for the user statistics exchange so let me share my screen can you see my screen okay okay so first of all a quick recap about the usage count service what are its main features um the user statistics services the uh the users count services the user statistics service uh for open air uh research graph the research graph which is presented by thanasis in the previous uh talk um what the the services does is to count the usage events that are related to the items in the research graph the publications the data sets etc uh we are um we are offering two different um let's say workflows for counting for collecting usage events we have the push workflow which tracks users activity using a specialized server side software and we are also collecting counter reports already available counter reports in order to somehow incorporate them in our uh user statistics database we are anonymizing the ip's in order to to respect user privacies and we are also exploiting the metadata duplication of functionalities offered by open air research graph that uh which allows us to accumulate users for the same research output the service is compliant with a counter count of of practice and provides standard basic statistics currently we are uh uh supporting release we are compliant with uh counter release four and i will present how a service is compliant with release five and in general the use of the account service uh provides offers indicators that we consider that complement other traditional and alternative bibliometric indicators uh in order to provide um a comprehensive and most importantly a recent view of the of the impact of uh the academic uh resources so up to now up to now we have uh we are compliant with a counter code of practice list four metrics which are uh offering the well-known metrics views and downloads views for the metadata downloads for full text uh download and for the future we are we have developed new metric types new concepts and new reports in order to be compliant compliant with a counter code of practice release five so the counter code of practice list five metric types we are moving from views and downloads to uh investigations and requests um i don't know which of you are are uh uh are known these changes um for an investigation is is struck when a user performs any action in relation to a content item or a title for example investigation is uh uh happens when a view an item a user views an abstract in uh in a repository or a view an html full text or views a pdf or downloads a pdf or a view or views access an article and produce an article on the other side a request is specifically related to viewing or downloading the full content item so we have investigation we cover almost any activity in the um regarding an item and we have the request which covers the the download and the view of the full item content so the definitions of these metrics um we have the unique item investigation which count unique article investigation request inside a user session we have the total item investigation which count a total number of items information which is related to an article which has been viewed including all article uh full content views the total item request which count all article full content views uh uh across all formats for example html pdf jpeg etc and this is more equivalent to the release for metric type downloads and we have the unique item requests which which count unique article full content views in a given session uh regarding of the format so for example if a user views an article pdf and html in the same session this will only count as one um i will try to provide a an example scenario which is one of my favorites that somehow explains how this new uh metrics are calculated so we have susan who is researching the history of porto in a repository in a umino repository and uh she performs a search and from the list of search results she opens she decides to open three article abstracts so up to now we have the following counts we have three i total item investigations and three unique item investigations so susan after reading the abstracts decides to download the pdf for the two of of the articles so the counts uh regarding the release five of the counter code of practice change to five total item investigations we have three views and two downloads three unique views since we have three unique item investigations we have three unique views and we have two uh total item requests and two uh unique item um requests uh so how what is the rationale behind these metric types uh for the total item requests they are considered important for providers at hell that have full text content and report the number of full text downloads or views the total item investigations we consider that they provide a big picture perspective of the total number of investigations and as far as unique investigation and request concern they are considered a powerful metric for identifying activities uh within with unique items and titles and they are also offering a more accurate a most accurate for their most accurate for cost per user analysis and measure the performance of the of the data source the data types that are covered by the release five protocol are articles book book seven collections databases data sets journals multimedia platforms and uh repository items uh there are a number of reports that are uh offered by the counter uh release five but uh for now have implemented four of them actually there are three and one is the regarding the data sets reports which is provided by which has been uh defined by uh make that account the initiative so we have the report name which is the platform master report which is a report summarizing users activity for the repository uh by month a metric type for example i total item investigations total item request and by item type we have the platform users report with a more generic report with summarized users activity for the repository by month and uh broken down by metric type we have the platform master item report which is which comes from the release four with some minor changes which is used to report items request by month metric type item type and repository and we have the data set report which is similar to the platform master item report but only for for data sets so uh i have a plan to show you a demo for of these reports that have been developed in our beta uh provide the dashboards uh i don't know if you have any questions so far regarding this feel free feel free to to ask the questions i think it was quite uh clear and with an example so it's always the important interesting so feel free to to to give the example i think it was was great but if you have questions just open your microphone so this is a community call so you can you can interrupt and ask question or just feel free to uh put it in the chat i don't think we have in the chat but okay i think it's also relevant to highlight this this maturity of the of the counter code of practice that is becoming more mature and more relevant and i think this last update inversion is is relevant and so it's good to have available and already ready to be in production so feel free to to to to give the the demo okay i can start with um the oldest have been implemented in beta so far and we will move the production soon um so if you go if you have enabled the service you will see that there is a tabbed usage counts so you are you are only sharing the the slides so you need maybe to sorry sorry sorry to interrupt and start again okay okay sorry i also have it i have opened i have opened the minute but feel free to okay can you see my screen yes yes it's working okay so if you have enabled the service you can see from the provider's dashboard you can see the tab usage counts where you can have all the information from the that has been collected from your repository the number of downloads the number of views and some graphs and you can click here to get the statistics reports so uh in the production we have uh so far the release counter release four reports but in beta we have also added the release five reports that these are the four reports that i have mentioned in the the presentation the pr the pr at the underscore p1 the ir the dsr reports for so let's see the master platform report this is a report summarizing as i mentioned the the usage activity for the repository by banth metric type and item type so we have um you can here specify the range for example you can we can have uh up for this uh from uh uh January to October 2023 and you we can get the report it's a big report and we'll take some time i think it's important to highlight when when the results are loading and then the meters can explain that what you see now in production if you have access you see only counter four okay what we want is to have in the same page the counter five and the counter four and then at some point we will discard counter four but we will keep it both yes please so you see that this is the user statistics report for this particular uh platform uh master report you see the platform which is the university of mino this is the data type the article and the the access method is regular we can also have uh tdm but it's uh uh this will be explained in our um in the protocol and the results for example for January you have 41 000 total item requests the total number of investigations the unique item request and unique item investigation this is uh for this uh for all the articles that are available in this platform in the repository in the mino repository and for the uh period of um of 10 months and then we have the books a similar report for the books etc for this particular report you can also select to have information only for metric types uh if for the metric types that you want for example total item requests and unique item requests and you can also see again see the results here and the next report is the report summarizing users activity broken down by metric type for example again i will use the same period and you can see the total reports for uh for all items uh for this particular uh platform the name of the platform is the you mino unit repository total item request for January for February etc so um this is the report the item reports as mentioned provides the the statistics for all items or for items that can be selected for example if i go here i will select a period with uh for only one month in order to get a quick report but for all items yeah you can see here that you can this the report cannot be displayed in the screen so you have to download it but you can download it here let's put it here in the zip file so if i open it can you just explain a bit that that option why why some we can see and others we can so we need to download it i think there is just yes because explanation yes because this is a big report and it cannot be displayed properly in the in the uh the browser so we have decided to uh facilitate this yes and do you provide it as a as a json file which is also the format that is supported by the countercode of practice uh directive and this is a proper uh report that can be downloaded and maybe you can process it in your premise in your side so every every this explanation is important every time that we run a query here that the the the report is yes yes yes yes okay no no no we cannot see you cannot see i cannot see because you are okay so we can see the button download report because you are not sharing the entire the entire desktop yes okay let me share okay so every time that so the so the meter is just just an explanation so about this download and see it in the in the in the browser so it's not for for the type it's for the volume of yes yes yes every time that the volume is is big so we so by default we it creates a download button yes yes it is offered by in order you can download it using the button yes can you see now yes yes yes okay this is the report yeah this is the json file that it can it's a proper json file that can be used in order to process the report okay perfect okay uh i can also provide an example of of it uh and if you if you select a specific identifier specific publication public yes but you are not finding data let's maybe the year yeah okay but so so we did we put this in the beta we did the testing i think we are quite happy with the tests so if any of you is is available so the issue here is that not so we are not only have a small number of providers the repositories that are sorry again this requires a download if i okay if i download the report there's an item report you see that in the zip file it's 66 megabytes so it's difficult to present it here so yes okay so this is more or less a similar report is from from data sets um let's see if we can have some results yeah this is the report from data sets we have the data set title the year of application the access method and the results that another title the year of application and some other results this is only for a two for a one year one month period that's why we have this uh this short list let's say so uh this is more or less what we have developed for the counter list five feel free to to join the beta provide the dashboard and play with this and if you have any uh issues please report it to us thank you very much so i was just giving that explanation that we we put it in better we are happy with the tests we made some tests with some of the data sources the limitation here for some of you is that we don't have um we only have a small amount of providers that are in better okay because we we cannot have a fully better thing for testing but we are quite happy and um so we will put that in production as soon as possible so we we want you to do it before the end of the year but i i envisage some limitations because december sometimes is short usually is short so but for sure in january we will have everything in production and in fact it's good because you can explore a bit the results of 2023 already using this this new reports i think it will be quite quite useful for you if you didn't have access if you don't have access to the user statistics you can always enable and work with us in order to ensure that you you can proper um facilitate this service for you okay and feel free to to ask questions and so because we we we can provide you support just to finish because we have only three minutes more um and so i just want to to highlight to you this this report that in fact was released yesterday some of the numbers in fact we discussed it a bit in in in september in the general assembly of open air but in but then the the the authors of this report just um put some more effort to to proper presented the and explore and analyze the results and the they yesterday uh open air and coir start the and the and the river and and spark uh europe start uh disseminating the this report so feel free to access the doi uh available in zinodo the public the report available in zinodo and also a new item that was released and re is also putting that in the shot quite quite interesting results i think it's important for us to explore this some of you may have answered this survey that the survey that was used for this report uh uh please read it uh i i have at least for me i i i had some surprises others i have some confirmations some things that are that prove the value of of of repositories some other things that prove that we need in we need to work uh more uh to to uh to increase the role and to to to improve the role that repositories plays in the in the scholarly communication ecosystem so let's work together on this our idea and after this release and feel free to explore and to ask questions our idea is that the upcoming call the community call we dedicate half of the community call to discuss a bit the results we will invite them at least Eloy Rodriguez from University of Minho our colleague here it's one of the authors from open air and from kowar is available to discuss with us the the report in the coming up in the upcoming community call so feel free to access the the the report and discuss it with your colleagues and then your countries i think they are relevant so um we will continue to try to have every every month the community call in the first Wednesday of the month we will follow this uh we don't we will not do it in the first Wednesday of January in the fact the first Wednesday of of the year but we propose to do it on the 10th of January so the the upcoming two uh we will schedule you will see it in this page open air dot you provide if an community calls and you can access the the at least we will schedule until until June and feel free to put you in your calendars so we are waiting for you on the 10th of January where we provide some novelties on the for the dashboard some recent new functionalities in the in the dashboard and and we discuss the report that i just highlighted here from the current state and the future directions for open repositories in europe this quite relevant report that we can discuss in this in this first community call from 2024 subscribe the newsletter if you didn't subscribe we try always to send the newsletter just one or two days before the community call and put it in your calendar feel free so we will try to inform you the first week of the month of the year about the the calendar of the of the community calls so and we are coming to to the end thank you very much i'm not sure if there are any other questions here in the chat if yes we can reply in one or two minutes so recordings are available slides also yes antennas please feel free to ask we have some hello thank you for very interesting novelties but i have other questions yes please i would like to ask about my very interesting very useful ticket i sent yesterday a reminder about about the ticket to Leonidas and andrei okay okay i see that now these are guys participating in this meeting and my question then we will receive answer with my colleague because we have been writing cancer from since june i june 16 okay about the aggregation of your i'm not sure if andrei have some novelties or this is important so you can always put the question so we we have a support system in place we are we also have some changes between it's important to say that antennas between the summer and now we change the the support team for the aggregation the aggregation team this is why we may have some delays other things we don't have delays for some of the things about the aggregation we may may have do you can you remind me me your the name of your repository i know that is from uh i'm looking at your ticket right now we will reply to you fine fine fine if you reply we will communicate with you and thank you for yes we try with rate with this is very quickly that's probably okay okay okay great we try to do our best so thank you for to raise that issue so if there any if you found any other missing communication etc just just ask us because we can we can we can try to do our best so antennas thank you very much so it's but but remind us about the name because people can check your repository so it's uh from from Lithuania it is very uh simple uh name Lithuanian international databases yes Lithuanian international database great thank you very much thank you for joining the community call uh if you don't have any other uh comment or request also feel free to contact us we try to do our best um to reply quickly when we found the more critical issues in terms of aggregation etc so sometimes we don't have we cannot reply quickly but we have already improved our aggregation team and i hope that we can we don't need to have delays in the future thank you very much thank you all bye bye have a nice Christmas


This is stock number 9266. We are here at Summit Automotive in Fond du Lac, Wisconsin. Your new and used SUV headquarters. We are checking out this super clean 2009 Chevy Suburban Z71. This vehicle is super clean all the way around. We shoot all of our videos in 1080p so if you have HD capabilities on your computer tablet or smartphone device turn them on now because it's like you're right here looking at the vehicle. And for the age of miles on this vehicle you'll find that it's in really nice shape. It has brand new Goodyear assurance tires with all the tread left. We put these on in our safety inspection. They are 265 65R 18s and they are on the Z71 18 inch alloy rims. Silver birch is the color. The hood and front grille are in excellent condition. It does have the factory fog lights. We shoot everything in 1080p so if you have HD capabilities turn them on right now. It's like you're right here looking at the vehicle with me and as we go down this side of the vehicle you can see just how clean that body is, how reflective and glass like that paint is. We take these HD videos so if you are far away or even if you're close by and you just cannot make the trip down but you're still interested in purchasing the vehicle you can still see the vehicle hear the vehicle and have confidence in what you're looking at before you even get here. Didn't see any denser dings down this side of the vehicle factory step bars. Back rim is in pretty nice condition here and the back tires are brand new as well. Going around to the back rear bumper is in excellent condition. No dense scuffs or cracks on it. Has a backup sensors. The full towing package which includes receiver hitch and seven pin wiring. Has the power lift rear gate that you can see works really nice. The rear gate itself is in excellent condition and the back storage area is very very clean. Those seats are removable and can come out and to close this gate just press the button right here and she'll come on down like that. You also have the flipper glass so this glass comes up all you do is press the button and that opens like that which is a really nice feature if you have a trailer or a boat on the back of it then you can still get into what you need to in the back. But the rear gate is in excellent condition I didn't see any denser dings on that and as you go down this side the vehicle just as clean as a passenger side. Back rim is in pretty nice condition as well and the back tire is brand new as well. We did four brand new tires in our service safety inspection in the shop. Down this side very very clean I didn't see any dense or dings. Has the step bars on this side. Z71 trim inside you get the LT I believe it's LT3 package so you get the black heated leather seats no rips or tears on them no wear either no you know the leather is in nice condition has the weather tech all weather floor mats throughout power windows power locks and power mirrors you got the power folding mirrors with the built-in directional signals they also power fold it like that and you hear your heated seat buttons and your memory driver seat auto headlamps turned out four wheel drive you can see that this vehicle does have the Z71 instrument cluster and that it does have 92,179 miles on it has the cruise controls on that side the leather wrap steering wheel and bluetooth audio controls on this side I believe 2009 was the first year that you could get the bluetooth integration in in the vehicle so that was a that's a first for 2009 has the factory navigation system with the nav disc included dual climate control we got power pedals backup sensors and stability track this is also where your backup camera shows up and you get the six speed automatic transmission if you got the tap shift there you got the six speed if there's no tap shift then it's the four speed has the on star has the homelink system and of course the power sunroof up there passenger seat is very clean as well no rips or tears on that seat and we got weather tech floor mats on that side as well take a quick look at the back seats and then we will check out under the hood back here we have the second row bench seating there are no rips or tears back here it does have the latch child safety system in the middle there we got weather tech floor mats throughout back here as well and the this door just shut on me but uh this back seats are heated and you have rear air and audio controls back here as well the third row seats are in just as nice of condition as the rest no rips or tears back here this vehicle smells very clean inside i don't think it was ever smoked in and like i said those back seats are removable if you wanted extra storage we'll take a quick look under the hood 5.3 liter v8 motor engine base very clean runs very smooth this vehicle has been fully safe and inspected by our service shop has a fresh oil and filter change all the fluids have been checked and topped off has four brand new tires the vehicle has been gone through mechanically 100% and it is 100% ready to go and to see more pictures of this suburban or one of our other 400 new and used cars trucks scvs minivans wranglers you name it we got it go to our website www.summitauto.com full pictures and descriptions of every single vehicle on our lot videos of every single used vehicle that we have all at summit auto.com thank you so much for checking out the video if you want to make this suburban years give us a call right now<PHONE_NUMBER> ask for one of our sales associates to make this super clean 2009 suburban years once again that number is<PHONE_NUMBER> thanks again if you want to check out more videos like this one go to our youtube channel which is youtube.com slash summit auto remember to like subscribe and share on all those videos and this video in fact in a second you see a link to subscribe to our youtube channel on your left a link to more suvs and inventory vehicle videos like this one on your right if you haven't been to our website on the bottom a link to this vehicle on our website click that check them out check out the pictures check us out and we really look forward to helping you with this super clean 2009 Chevy Suburban Z71 thanks again


Before she became a TikTok superstar and one of the most famous teens on the planet, Charli D'Amelio lived in a suburban Connecticut home with her also famous sister Dixie D'Amelio and their parents. This property recently came up for sale at under $1 million and it's the very same place Charli posted her first TikToks, only to go viral back in 2019. Once the fam stopped splitting their time with Connecticut, they decided to fully commit to the glitz and glamour of Hollywood. The D'Amelio family's current mansion in the hills is a super contemporary, trendy structure made of concrete and glass and was last on the market for $5.5 million. Today we'll take a look at where Charli D'Amelio calls home. In these videos we don't reveal any addresses and even though I've done a house tour of my own place please do not show up at any private residences because it's not safe for anyone. Charli D'Amelio is a TikTok star, influencer and dancer who's easily one of the world's most famous teenagers right now. Born and raised in Norwalk, Connecticut, partly in that house we'll be looking at, Charli was a competitive dancer for more than a decade before starting her social media career. In 2019 she started posting content on the video sharing app TikTok and well, the rest was history. Not only did Charli's TikTok dancing videos go viral, so did her sister Dixie's and they quickly amassed a massive following on the platform. Furthermore, Charli became the most followed TikTok creator surpassing Lauren Gray. At the young age of 16, Charli is already a multi-millionaire and only banking more and more with a ton of new endorsements and opportunities. She made her feature film debut with a voice role in the 2020 animated movie Star Dog and Turbo Cat and is set to start in the Hulu docu series The D'Amelio Show this year. Charli's other ventures include a podcast, book, nail polish collection, makeup line and more and let's not forget she's still keeping busy on TikTok and YouTube. She's the first person to earn both 50 million and 100 million followers on TikTok and is often credited as the app's biggest star. Hey guys, it's Charli the Vampire Slayer and I'm bringing you another celebrity house tour here on Famous Entertainment. Be sure to hit that subscribe button and ring that bell, we post a new video daily. We're gonna check out the homes of TikTok superstar Charli D'Amelio and not only the glassy Hollywood mansion she currently lives. We'll also see their suburban family home it all started at in Norwalk, Connecticut that was just sold. Here on this channel we talk about celebrity houses but if you want to know about their other lavish purchases or the latest trends in their outfits, go subscribe to Famous Fashion. Myself and some other hosts are reporting on all things celebrity fashion, expensive items and more. The most disturbing thing about these Lil Nas X Satan shoes, they reportedly contain one drop of human blood somewhere in the souls and not the metaphorical type. As always, don't forget to follow me on Instagram to chat and now let's get into this video. Let's first take a look at the house it all began. Purchased by Mark and Heidi D'Amelio in December 2011 for around 800K, it was here in this spacious yet ordinary home that Charli posted her very first TikToks, only to go viral in summer 2019. Located in Norwalk, Connecticut, a city on the northern shore of Long Island South, this home was super suburban and we can see the picture perfect lawn and American flag at first glance. Not sure about you guys but I don't hate the classic look. The former D'Amelio residence spans 3,749 square feet of space and the front of the clapboard structure is embellished in stone and grey paint. There's a long brick driveway and a stately porch with a column and rocking chair. While the premises doesn't look lived in at this point, the D'Amelios were splitting their time between this home and alley for quite some time. I guess before Hollywood was too demanding for the sisters. The unstaged interiors show up how roomy the home is and there's a living room with large bay windows and hardwood flooring perfect for family hangouts. Other main level spaces include a formal dining room and an open concept kitchen. Here there are stainless appliances and granite countertops while it connects to the family room with fireplace. There are also glass sliders to the yard. The suburban residence offers 4 beds and 3.5 baths and all of the bedrooms are located upstairs on the second floor. One of the three guest rooms boasts its own en suite while the other two share a single full bath and there's even a bonus attic room on the residence's third floor. The master suite which the D'Amelio parents used to have had two walk-in closets and a luxury bath with soaking tub. While outside there aren't many amenities to wow you just loads of grassy lawn space, the .59 acre lot can easily accommodate a pool as per the listing. Since living here life has drastically changed for the D'Amelios. Charlie has had one of the quickest rises to fame and fortune in history, amassing over 100 million followers and millions of dollars in under 18 months. Now Charlie and her fam are based on the west coasts full time and have outgrown the Norwalk lifestyle. The kinetic kit home just sold for 914 thousand dollars after two months on the market. Around May 2020, Charlie and the D'Amelios decided to move into their own Hollywood mansion. Last listed on the open market at 5.5 million dollars is believe the famous fam is renting it out for as much as 35 thousand dollars per month. The home, located high in the hills, is a trendy and super contemporary estate spanning 5 thousand 500 square feet and made up of glass, concrete and steel. The blocky front of the home opens up through sleek frosted doors and once inside. The open plan space allows you to see right out to the back deck and pool. The removable glass walls throughout make it hard to tell where inside ends and outside begins. The double height entryway sports a staircase made mostly of glass with a rock garden underneath and there is also a huge window letting in more sunlight. The common space is almost all blend together with the living space that flows into the outdoor pool area with removable glass walls. The attached kitchen is white and contemporary with a marble island bar style seating as well as a wine fridge. It's no secret that Charlie loves coffee especially her daily order. A cold brew with caramel and whole milk which even made it to the Dunkin Donuts menu as the Charlie. So naturally the high class kitchen has a meal coffee maker built right into the wall too. We can see some modern built in fireplaces also in this part of the mansion and a bar near the family room. A formal dining room also opens up to the pool much like the other main level spaces and it seems the yard is the focal point of the mansion. While it doesn't look exceptionally big Charlie and Dixie can enjoy the pool with the raised spa and deck furnished with sun loungers. There is also an outdoor fire pit with more bench style seating alongside the pool. Features inside include a cozy office, spa style bathrooms and your choice of lavish bedrooms upstairs. I wonder if Charlie or her parents get the master suite this time around. The bedrooms look spacious and offer terraces with glass balconies to take in the best views. The master suite actually has walls of retractable glass on both sides for a wrap around terrace and another sleek fireplace inside. The master bath is massive covered in marbling glass and there is more than one walk in closet fit for a celebrity wardrobe. While it might not be as famed as the Hype House just yet, if you follow Charlie and Dixie you've definitely seen plenty of this place in their videos. Even when Josh Peck filmed here for the first time, he said, is your house from the future? I'm sure one selling point was the sprawling floor plan as it's perfect for Charlie's TikToks or dance trunks. While the Hype House has a cool balcony, Charlie's is even better it seems. It offers an impressive hillside view of Los Angeles and wraps around the mansion connecting two upstairs bedrooms. While some of you might have assumed Charlie and Dixie were living in the famed Hype House, they likely just stayed here and were a part of it. Was never actually their home like many other TikTok creators. When the Hype House became a thing in December 2019, Charlie and Dixie were two of the most famous faces behind the collective. Despite not living full time at the actual Hype House, which is a shared mansion in LA for the biggest TikTok stars in case you live under a rock, the sisters often appeared in the Hype House content. This means they largely contributed and spent a lot of time there filming for their TikToks and more. However, Charlie and her sister ended up parting ways from the Hype House and now produced their content from the modern Hollywood mansion they call home. So now we've taken a look at where TikTok superstar Charlie Demelio calls home, so I think I'll wrap up this house tour. We not only saw the glassy modern mansion the Demelio family is leasing in Hollywood for 35 thousand per month, but also their former home. While the house they sold in Norwalk Connecticut is fairly ordinary, it's also where it all started. This is where Charlie started filming all those viral dances and pretty crazy how quickly things changed. After checking out both of those properties, what did you guys think? Do you like their new mansion or is it too contemporary? I think it's a cool home to create content and perfect for the Demelio sisters. I mean, there's so much open space and the backdrop in every room of the home looks super cool for any videos. Be sure to tell me what you liked about Charlie's current house or even their Connecticut house down in the comments. If you haven't, I'd love it if you subscribe to my personal channel. If you want to get to know me better, we'll link you my latest video. So Elise's missing person case, one thing that was a huge deal was a viral video of her in the CISO hotel. One of the staff, he goes up to check the water tanks on the roof. All story short, they find Elise's body in there. Thanks for watching. Don't forget to follow me on Instagram and let me know whose house tours we should feature next on this channel. I'll see you all in the next video. Bye.


Hi, my name is Dan Koshy. I'm the executive director for the Automotive Grade Linux Project at Linux Foundation. And today, we'll be talking about accelerating software defined vehicles through open source software and more specifically about how Automotive Grade Linux is addressing some of the current trends in the industry. So first, just a few words about myself. I'm Dan Koshy. I'm a Canadian, French-Canadian actually living in San Jose, California now for over 23 years because it's too cold in Canada. I still play hockey at my advanced age. And I was the former VP general manager of the Automotive Division at Montevista Software where we believe we were the first in the world to deliver a Linux-based system in an actual car. And I love wine. So I'm glad to be here in Spain because some of the best wines are here. OK, so with that out of the way, I sometimes start my talk by saying, how many times do we see this? This is the competition for software defined vehicles. It's basically our phones, right? Because not only do we see one phone with a sticky cup, we see two phones. Sometimes I've seen three phones, Lyft, Uber, all these things going on. And it's sad. And the reason it's sad is because this battery is a lot smaller than my car battery. And this screen is a lot smaller than my car screen. But yet we still do that. So you have to think to yourself, the car has a better screen. The car has a better battery. It should be better.  Let's admit it, right?  And why does it suck? And how did we get here?  Now, some of this is getting fixed, finally. Some of this is getting fixed. But the history is that a car manufacturer would request, from a tier one, would request a box with a plug in the back, one for power, one for connectivity. And what was in the box, the manufacturer didn't really care. As long as they met the spec, he needs to have this button, he needs to have radio, he needs to have this. And so a couple of years go by, they're shipping this box in the car. And then the manufacturer asks for a new box with new specs. And the new box has completely different software because either it's from a different vendor or it's from the same vendor, but they've moved on from Microsoft to some proprietary thing. Who knows? So we've ended up with, even in the same car manufacturer, different operating systems. Some car manufacturers still have to support four or five different operating systems from the past through their tier one relationships. But the bottom line is this is why we ended up in this situation. There's been no standard platform. And this is why Automotive Grade Linux was created. Now we're not the only ones, of course there's Android out there and I'm gonna talk about that where we fit in terms of Android. But just at a high level, what is Automotive Grade Linux, or AGL for short? You guys are all Linux Foundation attendees. You probably know all of this, but we're a non-profit organization, open source, Linux based collab project, hosted at Linux Foundation and 100% focused on vehicle software. And I'm gonna talk about all the areas that we address. The goal of AGL has always been to build, like I said, a single software platform that everyone can use to eliminate or at least alleviate this fragmentation problem. And so we're not in the business of building a platform that you can download straight to the vehicle. What we're building is a platform that allows OEMs and their tier one partners and their tier two partners and all these companies a single platform that they can use as the starting point and then customize it. So we've always said we wanna be like 70 to 80% of the starting point of a production project. But then the manufacturer with their partners, they select their favorite navigation provider, their favorite Bluetooth connectivity provider that is certified to connect with iPhone and Android phones. They select their favorite providers, they add this to the AGL system and then they complete the system for a given piece of hardware. So we never intend at AGL to be downloadable straight to the car, because sometimes people think that. And then with this, what we're hoping is that we have standard kernels for a given piece of hardware. Standard services layers for things like Wi-Fi, Bluetooth, LTE stacks, things like that. And then a standard application API for things like navigation, which we have, voice recognition, which we have, radio, telephony, all these APIs are standard. And so then the manufacturer can really pick and choose their favorite app provider and just integrate with AGL. And the good news is because we have such large presence now in the industry, a lot of these apps have already been ported to AGL. So it alleviates a lot of the work. So if you want to Spotify in your vehicle, well, Spotify has already been ported to AGL. So chances are it's quite easy to do because it's probably one or two weeks work, to be honest. At AGL, we're strongly a code first organization. And the reason I mention this is because a lot of other organizations in the automotive industry are spec first, specification driven. And often is the case, they don't have any code at all. They just have specs. And then what happens is vendors write code and become compliant to the spec. So they end up having vendor A, vendor B, vendor C all having compliance. But if you look at the code, they're all different. So now we're back to step one. Different code, different code bases, different kernels, more fragmentation. So at AGL, we said, we're not gonna do that. We're not gonna have a spec and we're not gonna have a compliance program. Despite a lot of pressure from big tier one companies to do this because they want to build their own platform and be compliant to AGL. And we said, nope, we're not doing that. If you wanna be AGL, you gotta download AGL from our website. That's the starting point. That ensures that everyone's using the same code. And we still have that strong motto to this day. AGL, we started at first by supporting infotainment or IVI in vehicle infotainment. And that's because this was the biggest pain point for the automotive manufacturers. Trying to be competitive with the smartphone, infotainment is the first thing we worked on. But since then, in many years now, we've added instrument cluster, heads up display, telematics. And we're also working on functional safety and ADAS, which I'll talk about in some future slides here. But we're already addressing all of the first four functions. And we have been for, wow, probably seven years now, eight years was our first release. We have 10 manufacturers supporting the project. You can see here we have very strong support in Japan. We have Honda, Mazda, Mitsubishi Motors, Nissan, Suzuki, Toyota in Japan. We have Hyundai in South Korea, SAIC in China, and Mercedes and Volkswagen in Germany. So we have a pretty good distribution geographically. Notably missing is USA. We did have Ford for a while, but unfortunately they dropped out of AGL because they're, I think, adopting an Android strategy. But nonetheless, we have quite good support. And when we say Volkswagen group, we wanna mention that it includes all the Volkswagen logos, including the very expensive cars. And I know Bugatti's been working with AGL because I met them at Consumer Electronics Show and I asked if I could have a loaner car from them so that I could demonstrate AGL and make sure AGL is fully supported on the Bugatti. And they said, Dan, we only sell 43 cars a year in America and you're not getting one. So I didn't get one, unfortunately. We have over 150 members at AGL. I believe we're about the third or fourth largest project at Linux Foundation, both in terms of membership and membership dues and things like that. We have quite a nice diversity of companies. We have, of course, the automotive companies, the OEMs, the tier ones such as Denso Panasonic, Aishin, Harman, Continental, Bosch, pretty much all of the big ones. And then we have most of the semiconductor providers such as Renaissance, Intel, Qualcomm, and XP, TI, NVIDIA. So pretty good automotive membership, but lately we've been attracting a lot of small companies, companies with 50 people, 100 people doing very specific things like security. We have companies from Israel doing security work for automotive. We have, you know, and they're not traditional automotive companies, but they're like involved in the ecosystem and that's what we wanted to do from the very beginning at AGL is include all these smaller companies that wanna be part of this new connected car ecosystem. And I think we're succeeding at that quite nicely. And then I have one more slide marketing-wise and then I'll get on to the software. Two more slides actually. We first ship AGL in a 2018 Toyota Camry and since then virtually all Toyotas and Lexus run AGL. We also have most of the Subaru legacy and outback run AGL, some Mercedes-Benz Vans, and we're expecting several Japanese makers in the coming few years, if not sooner, and also some big logos that I showed before from Germany expecting to come out with AGL-based cars. Where we stand in the market, we're actually leading Android, which is nice. This is not a chart I produced. This is a chart that came from IHS Market, a big analyst firm. And you can see orange is AGL and then the light green is Android Automotive. And as of 2023, AGL is roughly at like 18, 19% and Android is at, I don't know, four, five. So not too bad. And the reason Linux is down, that's what they're calling generic Linux. It's because it's being replaced with AGL over time. And then the one at top, which is the gray, is actually what I call the Android fork that is mostly used in China, where you don't get any Google support, you don't get any Google apps, you don't get Google updates, you get none of that.  Okay, let's talk about software now. So AGL, UCB. We named it UCB, it stands for Unified Codebase. And the reason we named it UCB was very deliberate is to kind of emphasize that we're trying to alleviate the problem of fragmentation. So it's very marketing related. We name our releases after Fish, in case you didn't know. This is a fun thing we do. Google named their releases after desserts and we said, we gotta find something cool. And Walt Minor, my colleague, he said, let's do Fish. And I'm like, Fish, okay. And I don't know if it, because we have so many Japanese members who's thinking sushi, but anyways. So Agile Albuquer was the very first release in 2016, all the way down to Magic Marlin and then I'll show you the latest releases in a minute. The point of this chart is not to show you a bunch of Fish. It's to show you that we have kind of a, we have, first of all, we're doing two releases a year every year since 2016 and we have kind of a TikTok model where the release that comes earlier in the year, meaning Q1, tends to be feature rich where we have new features that we demonstrate at Consumer Electronics Show. And then the release mid-year tends to be less feature rich and more focused on bug fixing and hardening and long-term support. And so what we recommend to companies that start projects is you should take the summer release or the summer fall. It's always around August, September-ish timeframe. Nifty Needlefish was released August last year and one of the most important things there is that we, well, a few of the important things is that we switched to Yachto long-term support release 4.0, Kirkstone is the name. So we tried to align with Yachto long-term support releases so that we get the LTS support from Yachto and then we pass that on to our BSPs and the rest of our software to the AGL stack, basically. This was the release where we started really moving to Flutter. So we're moving away from QT in terms of App Framework and moving to Flutter and I'll talk about Flutter specifically in a few slides. And this is also the release where we started supporting WebOS for OSC and Chromium. We've been supporting Vert.io for several years. In fact, the people doing the Vert.io work, if you're familiar with Vert.io virtualization, Vert.io is also what Android supports. We support the exact same Vert.io and the cool part is the people doing this work are from Panasonic. They're leading this effort and they are actually the one that have written the code for AGL as well. So now we have the exact same code for Android and AGL and why is that important? Well, at AGL we support more than just infotainment. We support instrument cluster and so if you have a Vert.io environment and a single processor, you can run AGL instrument cluster side by side with Android and that's very attractive for several automotive companies because many of them have chosen Android for whatever reason and in those cases you can still use AGL for instrument cluster because Google doesn't support that and so that's quite attractive for us because then we get to participate in those vehicles and it's attractive for the automotive manufacturer. Optimistic Octopus, which is difficult to pronounce, it was released in February of this year. This release we updated to the latest version of Kirkstone but also we added Flutter, Auto and Better and a new home screen, dashboard, new HVAC apps, et cetera. So a lot of updates based on, again, us adopting Flutter and we also did an IVI and instrument cluster demo using containers. So you're able to, you can run it in a virtualized environment with hypervisors either commercial hypervisors or open source hypervisors like KVM or you can run it straight with containers. So really all the deployment options are there and it's up to the manufacturer and their partners to decide what to do. We also added VertiO loopback support and a little while back we used to support SMAC for security and we moved to SC Linux and we enable SC Linux in the image but in permissive mode and then it is up to the manufacturer and their partners to decide what policy they want to apply. But SC Linux is fully supported in AGL now. The latest release is Prickly Pike was released very recently in August, August 10th actually. This is our 16th release. Some of the interesting work here is that we've added actually significantly updated support for KUXA. Now KUXA is a vehicle signaling standard was developed by Covesa and W3C I believe jointly and we're not sure but we believe we're one of the only hosts of actual code for KUXA in the world so that's pretty cool. So we have full support for that. We also added the, we actually updated the container demo that I mentioned before for our instrument cluster and IVI and we added DRM lease manager for the instrument cluster as well. You can find a lot more detail on the release notes on our website here. So AGL we've never stood still. When we started the project and our first release was 2016 as I showed you, there was a lot of things missing in the industry. For example, we had to write our own audio manager from scratch because in a car it's not like another device because if you have a phone call coming in and the navigation's trying to talk to you and there's an emergency situation with ADAS, you know the audio has to be layered properly with proper priorities and believe it or not sounds simple to implement but it's not. It's actually quite difficult because every car has their own requirements and so we had to write our own audio manager and we've dumped it now because now we use pipe wire and we have the ability to do that. So that's just one great example, yeah. That's just one great example where we've never stood still and we don't mind throwing stuff away that we've written if there's something better that comes along and this chart actually shows several examples, right? We started with App Toolkit, QT and now we're moving to Flutter and Web App Manager. We wrote our own audio manager, now we use pipe wire. We were using SMAC, we realized SMAC is kind of dying. Let's move to SC Linux, it has better support. We started with a IVI shell and now we have an AGL compositor. These are just examples that we're not standing still and we're always willing and open to adopt new things. So if there's something in your community or your project that you want us to adopt, we're super open to it. Just come, propose it, we have a system architecture team that will look at it and then the steering committee will make a decision and decide whether we should adopt it or not. But we're very open to those kinds of things. In terms of expert groups, these are the experts group we have today. In other communities, they're called work groups. We call them expert groups, but we don't want to scare people away. You don't have to be an expert. My colleague always says this. You don't have to be an expert to participate in an expert group. We want everyone to participate and it's open to anyone. Some of the ones that have been the most active in the past, application framework and security, connectivity, continuous integration and testing, these are all still active. Speech recognition has kind of died down now because we've completed actually Nuance and the Amazon Alexa team are the two companies that wrote the speech track APIs for us. So two of the biggest leaders in the industry wrote those and those are kind of finished. Virtualization is super active and vehicle to cloud is super active and container and service mesh is super active to the point where these two were working on very similar things. So we decided to merge them and redefine the name to software defined vehicles. And basically we've been announcing this for the past few weeks now. This is a new expert group led by Panasonic, Jerry Zhao of Panasonic is leading this effort. And in our very first meeting, we already had some really big companies participating such as Amazon AWS, Volkswagen, Arm, Virtual Opal System, et cetera, Harman as you can see. And this is a call for people in the community to participate. If you're interested in this, I think this is probably without exaggerating, probably the hottest expert group in terms of expectations and participation that we've had at AGL since our inception. A lot of companies are looking at the future of software for cars and they're saying things have to change. We have to change the way we deploy things in vehicles. We have to use containers. We have to be able to push updates not that are not entire images. We can push containerized updates. These kinds of things are the things that this group will be working on that combined with virtualization. And I think this is the future of automotive. These kinds of things will probably not be deployed in cars in the next year or two but we're talking five years out. This is the kind of thing that the industry needs in order to get out of this constant difficulty of deploying software for vehicles. And so we expect big things from this group and we hope to see a lot of participation from the community. I'm gonna talk about a few more key AGL developments. We build our own hardware at AGL. This is not well known. We don't do this to make money. Actually, we sell it at zero profit because we're a nonprofit. But we build our own hardware because it's very difficult to find reference hardware in the industry. You sometimes, most of the time, have to sign NDAs. You have to get your legal department to look at it. You have to then spend potentially several thousand dollars per board. So we decided to provide the community with hardware and so we already have these boards that we sell from, with the Renaissance SOC, it's the Renaissance ARCAR. And we have this sandwich architecture where the bottom board is the vehicle board. So you have all of the signaling, can bus, things like that. The middle board is the peripherals like audio and camera and visual. And then the top board is the SOC, the SOC processor. And the idea is that you can swap out the processor with a new processor board anytime and the software will be virtually unaffected. Of course, you need different software image to be downloaded but the overall API is everything, nothing changes. And so this is available for purchase here. We're planning to add Qualcomm SOC. That work is ongoing now in the near future. We hope to have that as well. Oh, I just wanna add one more thing. So there's actually one car company that I know of looking at this concept for actual deployment where if they have a problem with supply, like a supplier supplying a specific processor, they can quickly switch manufacturing by changing the sandwich to a new SOC and have almost little, very little effect on the actual software. And so there's a, I can't say who but there's a company looking at this for actual building cars and deployments which I thought was quite interesting. Another key development is AWS is helping us put AGL on the AWS Graviton which is a cloud-based ARM64 processor. This is great for developers to be able to develop and test from anywhere in the world, from home or from sitting right in this room. So this is yet another great option and we're really happy that AWS is helping us with that. This should be available very shortly. I don't know the latest status but I thought it was gonna be released this month so hopefully we get that done. I mentioned Flutter several times in this discussion. If you're not familiar with Flutter, it's an app and UI development toolkit. It's an alternative to QT if you will because QT is quite well known. It was originally developed by Google as an open source project and but it wasn't automotive specific and what Toyota did is they took that and applied several automotive specific features to it including different screen aspect ratios and things like that and they contributed all that code back to AGL and so we are the home of automotive Flutter if you will and we believe that this will become the de facto standard. We already know of one other big German car company that is looking at standardizing on Flutter. If that happens and Toyota is already standardizing on it it will become the de facto standard I believe. It's not up to me and it's not up to us but we're supporting it, we're part of this effort and we hope this happens. We think it's the future and so we're right in the middle of it. Vert.io is also the future. This is pretty clear because we support it, Android supports it. There's really at this point no other game in town for virtualization of IO and what's great about this is it allows AGL to run anywhere, natively or on a specific SOC or even in a cloud environment with no change and this is already being demonstrated, this already works, it's not pie-in-the-sky stuff and we hope that eventually car manufacturers will actually start using this in their deployments. I mentioned earlier functional safety so we're also working with another Linux foundation project called ELISA. ELISA is working on enabling Linux in safety application, that's what it stands for. Things like nuclear power plants, aviation, train control systems, things that require serious functional safety. ELISA is working on those things, we're leading the automotive work group within ELISA and so our hope is to bring our, our first attempt will be to bring our instrument cluster software release to functional safety ready status. And by ready what I mean is you can't get real functional safety certification on reference hardware, you need the final hardware, which is only available to the car manufacturer, we never see final hardware. And so, but we will do everything necessary such as the testing, the artifacts, the documentation needed, all these things with the goal that the manufacturer can take all that and that's hopefully like 70, 80% of what they need and then go get certified on the final hardware. And we have one leading OEM that is planning to do this for our instrument cluster. I wanna quickly just mention AGL events because this is a cool part of what we do at AGL. It's a great part of participating in our community. We had an all member meeting in Berlin recently. This is pretty funny because you may have seen in the news the Radisson hotel in Berlin had a giant aquarium that blew up. Yeah, we were supposed to have our all member meeting two weeks just before that happened. Like, sorry, two weeks, you know, our date was two weeks from that explosion. And so we had two weeks to find a new hotel and it's not easy by the way. And so that was pretty funny that our AMM was almost canceled because of an exploding aquarium. It's the fish, it's the fish, revenge of the fish. That's a good one, I didn't think about that. Anyway, so this was a very successful event and I'm glad we were able to pull it off. Every year we participate also in Embedded World and this is a great opportunity for our members to participate for free. They can participate in our booth, show a demo of their stuff running with AGL. So if your company is a member and you'd like to participate, you can contact me anytime. We're gonna be there next year again. This is a fantastic event for automotive in my opinion. We also had the very first ALS Europe this year. ALS, which stands for Automotive Linux Summit, normally is always in Japan, well now we have two. So we have one in Japan and one in Europe. And so we had the very first one in Prague in June and that was really well attended and it was part of what Linux Foundation calls Embedded Open Source Summit, which replaces the old Embedded Linux Conference. So Embedded Linux Conference no longer exists. It's been replaced with EOSS and we're planning to have another one next year and AGL will participate. We also recently had our all member meeting in Japan which was in July, that was super successful. And coming up next month we're gonna participate in the Automotive Software Expo in Yokohama and again our members can participate in our booth and show a demo of their stuff. So if you're interested in participating, you can contact me. And then our biggest event of the year is Automotive Linux Summit Japan. This will be at the Adiaki Convention Center December 5 and 6. Just to give you an idea, this event pre-COVID was attended by about 2,000 people. So very, very well attended event for automotive. And finally we're gonna participate in Consumer Electronics Show. AGL will have a quite large booth here next to Mercedes, next to Keriad, Hyundai, Hyundai Motors Qualcomm, right in the middle of the automotive stuff at CES. And again our members can participate in the booth. This is what it looked like one year where we had two vehicles showing AGL demos and then big companies like Entity Data, LG, Panasonic, et cetera showing demos of their stuff running AGL. And this is the front. And you can take a photo of this if you wish, but these are also the upcoming events. And we've already decided we're gonna have our AGL next All Member Meeting end of February, which will be in Tokyo. Probably the week of Feb 26. We're finalizing Hotel Now. And then we'll do the AMM summer in July and that'll be in Berlin again because we're getting really good attendance in Berlin. It's convenient for a lot of people. And so that's also gonna be in contract phase for July. And that's all I have for slides and I have time for questions. Yeah, yes. Yeah. Yeah, so we've had that. So the question was, does AGL support long-term support, LTS, and what's your strategy? So we've had that discussion many times inside AGL. And there's always been a debate. So some big companies want us to do long-term support. They want us to support something for 10 years. Other companies say, no, no, no, we want AGL to be an incubator of technology. We want you to focus on new stuff, incubating things, cutting edge, we'll worry about the long-term support. And you can see why because some of the tier ones make their money on the long-term support, right? Let's face it, it's a business. And so they don't want AGL to be that. They want AGL to be just incubating things that they can use. And so honestly, at AGL, our long-term support right now is that we support the Yachto long-term support, but then that's where it stops. We support our releases for up to a year and a half to two years. We do dot releases, things like that. But we don't do a 10-year release, not yet. But having said that, there's pressure to do it. And we may do it. And it depends on the steering committee. Yeah, yes. Does anybody want to know? Sure, yeah, that's absolutely true. That's a challenge for any long-term support, yeah. Yeah, so today it's mostly the large SOCs, very powerful multi-core processors. They're all ARM-based, pretty much. We do support an Intel board for reference, but I don't believe anyone's using that for production. So we don't support any kind of, I don't know, I would say small ECUs today, but it's certainly not out of the realm of possibility. But today we support, you know, renaissance, Qualcomm, NXP, TI, those SOCs. If someone wants us to support it, they should join AGL and tell us what you want. No, really, we're that open, right? If someone needs support, we will support any hardware. The only requirement is that it has to have a Yachto-based BSP, because that's what we pull from. And the other one is it has to be supported. So if it doesn't build and something breaks, whoever manufactures that chip needs to help us. They need to fix it within a day or two, or else it won't build. We don't have the manpower to go fixing a million bugs in BSPs, we just don't. It's partly, I think a big part of it is the car company's wanting something new and something more cutting edge. And the thought was that flutter, because Toyota is having great momentum, like you said, with it, and now we know of at least one large German company, maybe two, that might adopt it. There's just a lot of momentum behind it. That's the primary reason, yeah. And the tier ones too, by the way, not just OEMs. Several tier ones want us to use flutter, so that's why it happened. Yeah, I mean, we don't get involved in that as an open source project. So I don't want to comment on that, but I'm sure there's some car companies may have had licensing issues, yeah. Any other question? Oh, yeah, yeah. Yeah, actually, yes. I met with John Deere, and they said they were using AGL for all sorts of things, like the big combines to track tracking and things like that, and yeah. Coming? Yeah. Yeah, that's what I was told when I met with them. Yeah, not under NDA. So, any other, you had another question? Yeah. Well, I think it's all, let's face it, it's all commercially driven, right? So if Toyota, which we know uses AGL, they tell Spotify, we want you to port it, and then they have to, right? So that tends to be the first port tends to be a commercial reason behind it, but then once it's ported, I feel, this is what I've seen, those companies tend to maintain it because they have to maintain that one customer anyway, so then it's easy for others to adopt because they've already ported it, they already have it, then they maintain it for different. Well, that's what I've seen. Yeah, okay. Oh, wow, okay. I'd love to talk to you after and find out what companies. Okay, yes. So, of course, the code base is over 100 million lines of code, so we have a ton of licenses, right? There's not one license, but our incoming license, if you want to contribute new code, is Apache V2 for new code, yeah. No, we don't do anything special for GPL V3. We don't try to avoid it, we treat it like anything else. If it's a package we need, we use it, and if the manufacturer or whatever has an issue with that, that's their problem. It's up to them to find an alternative or work with their vendor to replace it, yeah. Yes, yeah, that's the plan, yeah. I can't say who, but I can say it's a big OEM, and they've been working on it for, wow, I want to say four years, and they have the funding to bring it to fruition, so it's not just a pie in the sky R&D project, they actually want to bring it to real production, yeah. Yeah, and that's AGL running natively without a hypervisor, so that means full functional safety, because today the way to get around functional safety, I know because I was the, like I said, the VPGM of Automotive Division in Montevista, and we did the Chevy Volt instrument cluster, and the way we did that is that we did an overlay with an RTOS underneath that was certified that does the overlay of the critical functions, and then Linux is used for all the fancy graphics and everything around it, and this overlay thing is how a lot of companies have used Linux in instrument cluster, but to use Linux natively without a hypervisor, without an RTOS, that's the goal of this instrument cluster expert group. Correct, yeah, exactly. Okay, well, sorry folks, we're out of time, but thank you very much for joining. Thanks. Thank you. Thank you.


Hi everyone, it's John with jaspyscasebreaks.com here doing a team random filler Where we're also giving away a sealed box of tops gold label This will fill pick your team number two of twenty twenty one tops gold label Where you'll either win a box or a team in the pick your team to break So 12 spots will take all 12 customers a is randomized them only randomizing customers names post the results next to this list Where on top you get the sealed box of twenty twenty one gold label down to the Royals at the bottom Here is that list copy and pasted there So and here's the list of customers from Rob Fuller down to Joe Locas with last spot mojo We're gonna randomize only the list of customers and paste that next to that list and whatever you're paired up This is what you get for the break or the sealed box dice roll one and a four five times Good luck guys fifth and final time Rob on top to get that sealed box of Tops gold label down to Travis Travis on the bottom five times on the randomizer five times on the dice Rob down to Travis So let's see how it turned out for you guys Rob like I said you're gonna get that side of that sealed box of twenty twenty one gold label baseball Ship to you Joe you're gonna get the Dodgers and pick your team to David Malel with the Mets Joe Locas with the Cardinals David Malel with the Astros Tommy John with the Brewers Joe Locas with the Twins Jeremy Port with the A's Joe Locas with the Indians Rob Fuller with the D-vax Travis Melberg with the Rockies and the Royals And there you guys that is the team random randomizer to fill up pick your team to of Tops gold label baseball the break itself pick your team to coming up next. I'm Sean Jaspies case breaks calm Thanks for hanging out. See you next time