 Good afternoon. I'm going to talk about Something that is the result of a period of several months and Several years I would say from the moment we started to talk about this and to the moment we are studied to deploy it Some first times ago we are starting to talk to some people of the Open document foundation about having a development dashboard for LibreOffice and all the other periods around the opening document foundation umbrella and Basically we're a company that they're producing free software for doing this kind of analysis I'm going to present it later So at some point where it's an agreement and we deploy it the first version of the dashboard Which is with now it's online and I'm going to tell you they are right now So there are two talks now by myself one is this one which is basically for Explaining how the dashboard works and the second one is probably more interesting because it's about how they work They work straight how the dashboard Is that internally and how you can query directly all the data because right now we have for three data sources of your development We have all the information stored into a nice elastic search database that can be queried in any way you may want So that means that probably on some of the metrics that some of you could be interested in having are only a couple of Three elastic search queries away from you. So let's go to the real thing First of all, I'm going to very briefly talk about some context about myself and the company And then I'm going to talk about the dashboard and I'm going to spend the first 20 minutes talking about the dashboard So the dashboard is online as I said well Let me go on Briefly so me that's my that's myself even when it doesn't look like I'm both at the university and at the company So I've been working in software metrics for a while But my approach to the software matrix is not looking at the source code But looking at the activity and the processes that's what the dashboard is about so some time ago We decided to start a company and the company is basically producing and using only free software And that's what we use it to deploy that the dashboard and the dashboard is here so here you have the link you can there's a thing life if you want and If you try it with a phone it doesn't render wall, but try it with a tablet or with a Laptop it's dashboard the document foundation org so it was updated like yesterday. So all the of the information I guess it's pretty up today and There are several views for the Information first of all we have like a three Roche in the main entry point where which it's one corresponds to one of the data sources you have kid you have good it and you have a batilla and then on the Left you have numbers which are summaries of what's happening in the private now and then you have the columns This is about activity. So that's commits code reviews or tickets and this is about the persons So that's all sorts of commits that's people starting code review processes and this is People opening tickets and then you have some summaries on the right. They have less information is probably not required yet But still we can have an idea so we will some heuristics based it on the email address Which means that if basically if you are using a gmail address for instance You are in the unknown part if you are using a corporate email address. Usually you are in the part of the pie Let's go to the real thing Which is over here Okay, nice As I said, this is the main overview of the project and First of all everything is Actinable so you can click and filter and more things. So for instance, you can Rearrange the icons somehow you can remove one of them if you don't want to see it You can also Enlarge them if you want to make more clearly what's happening and stuff like that and of course if you don't save Anything happens for the next user and you cannot save so no problem for that You can filter and a step. So let me go to the git Panel and I'm going to show you how to use it very briefly So this thing that you see on the top of filters. So those red boxes So we have to default filters for filtering out empty commits I mean those commits that don't touch any file and bots for bots. We have some heuristics I don't know how good they are for this as well, but basically they can be minted with a manual for In any case filters can be Actinate on you can just click here and basically it removes the filter which means that now the information you see once the thing is done is basically Everything like it was before bed without the filter. So I'm going to activate the game and You can filter by organization so that if you want to have a look at what red hat is doing in this repository We can very easily go there click and filter and now the thing is the same But now for red hat activity and you can also of course came to Any other of the parts like I want to filter on and specific repositories for instance This one and I want to check specifically what's happening Well, this is the information for some of the things. There is nothing Every time you click on something a new filter appears and filters can be removed with that by just by clicking on The trash can which I'm doing right now Okay, so this is again the whole activity for the for the repository Coming back to what's in the git repository you have information about the different authors. So probably this is a bot that should be filtered You have organizations of a time where you can have a look at the commit activity of a time and look at who is performing those commits by Affiliation This is just curious because you know that indeed you have the local time of the commuter and All that depends on how well configured the laptop of the developer is but otherwise. Well, this is basically the American West Coast, this is the East Coast and later America. This is Europe and Africa. This is Asia This is Australia and so on so you can get up first a rough idea of where your developers are Of course if people has UTC zero in the laptop because they travel a lot while they are here though That's why this this big here In any case the information for a git is not let's say that interesting because in many cases you already have it But if you come to worried Information has started to be probably a bit more interesting. This is basically the number of Code reviews of a time it seems that you started to use your it intensively at some point in the last year So we can filter out The rest of the time so on the top light on the top right you have a date filter So I'm going to get with only with the staff from the last year On the that's for enough Okay, now you can see the code reviews Sorry there the code review information as you have it now and If you look at this one, it is by a status if you want to to learn what status there you have New amandone and March so you have some new down here So you have some of them don't know all over the place and most of them are more that's Number of code reviews by by month Of course, you can again click and you can maybe focus on the currently open. I mean new Code reviews and you can see how you have new code reviews from last year, but most of them are Well, pretty recent from the last I don't know three to two to six months I'm going to remove that one Then you can of course do the same for for Repository so that you are interested in what's happening in the dictionary for instance. This is a code of activity there And again, you can come down and see a bit more detailed information like the number of patches per changes So how many people how many times developers has to resubmit until they get accepted? Those are numbers that start to give you a idea about how efficient the process is because you know if you have a lot of Cycles that basically means that while the new versions that developers are sending are not good enough They have to review it again. They have to be asking the game for a new version and that's not much efficient You can filter by persons and you can filter again by by organizations I'm going to skip some of the Menu entries for lack of time, but you can go later. Let me check go read back look Because it's probably that the most interesting one for developers This is the current backlog of great issues that you have right now So speaking with you can look at the time of structure of those so this is Time and this is the number of new transits. I mean 10 sets in the new state So as usual most of them are recent, but the year starts here So you can see this is very weak now So you can see how you still have some that are two to three months old and you have some that are very old In many cases you may be interested in learning which ones they are to go and look at them That's what you have on the left. So on the left you can go and see okay I have this backlog and I want to learn what's happening with this specific for instance This has been sitting here since March last year So you can go and click and go directly to go it and see what's happening with this one And maybe deciding to I don't know close or abandon it or something So this is probably interesting staff for learning per repository What kind of let's say jobs you still have pending from the code review point of view Of course, you can also filter by who is submitting or which organization is submitting or stuff like that so that you can Zero on the kind of information you may want For issues I mean for Park Cilla, we have similar information here You have all the tickets in the current state and I'm going to remove the legend so that you can see it better. I'm not going to enlarge it a bit With Baxilla we have some trouble with data retrieval which means that the data is updated only up to November But still you can get the idea of how you can see the structure of all the tickets right now How many of them were closed when you have a ticket sitting for a long time in such and such state and so on Again, you can do you can see the same by you know organizations projects emitters and staff