 Welcome to the Jenkins user experience special interest group. It's May the 26th reminder that we abide by the Jenkins code of conduct. So let's work through the agenda so you noted status of the student project for pull request viewing and you've added bootstrap five inside each arts. Any other. Oh, let's see. And I would like to put one on a replacement for Mark weight as scribe slash meeting launcher. Okay, any other topics we need to put on the list. Yeah, I would put one. So collaboration is open source design. We can discuss it. Mark. Did I capture that well enough. Yeah. Okay. Yeah, just a second. I struggle with finding the right meeting Google Docs. Oh, yeah, the US secret still references the old doc in the calendar. So I reported it last week, but it hasn't been updated. That is the document that I can't edit. So yes, I need to fix that. Let me. I think my past attempts to fix it in that Google count in the calendar entry have all failed. I don't know what I'm doing wrong, but it just fix it for you, but please send me in because I don't know where you bet. Yes, here's the link. I'll just paste it into the chat for Here is that. Thanks. Sorry about that. I tried to fix it last week and was unable. Okay. So any any other topics we need to add to the agenda. Okay, then let's take on first topic really and status of the student project. We are currently implementing the first portlets. So the student already provided a pull request for my warnings plugin and a pull request for the code coverage API plugin. Both portlets are not yet ready, but they are already in review process. So I think in one of the next meetings, we can present them in a demo again here. And currently, I can present a pull request. I'm not sure if that makes sense. So I think it would be much nicer if we can see them in the real system. So if that's fine for you are just the heads up that we are working on the portlets and we need some more time to finish some to integrate them into some plugins. And it takes two or in four weeks we are ready to present again. So we have the portlets in the running system and Simon already started a topic in the developer mailing list to gather some feedback from others. But I think we will obtain the most feedback if we deploy it in a Jenkins instance as Alex suggested already. It takes only some time until we get some more feedback. So are there any questions on this topic? When you say deployment on a Jenkins instance, is it on one that you or your students are managing or something else? Actually, the demo could be done on one of our instances. Yes, of course. But I think Oleg mentioned that we can deploy it to our CI. Jenkins if it's stable enough so one can see the results there. Okay. Don't hesitate to mention it if I can help on that topic as part of the Jenkins infra team or team here. Don't hesitate to mention us and at least just let us know so if there is any instability that was not forcing, that can happen. That's not a problem. It's just important that we share the info. So now I have it, I will share it inside the team as well. Don't hesitate to tell us if you need anything on that topic. Great. Thank you Oleg. Thanks very much. So that sounds very promising. So Simon's work you said was in warnings NG and in code coverage. Both those I believe are installed on ci.jenkins.io. So it would just be an upgrade of those plugins and we would get his capability. I assume the plan would be to release the capability and a general availability release of the plugins. Is that correct? Yeah, that's the plan. Yeah, so then then we would get that get that automatically that's great or we would get that as a result of upgrading the plugins. Wonderful. Well, the only thing which is not yet available is the part of the dashboard plugin which we need to install as something that so the plugin that is showing all the results. This is not yet installed. The warning plugin installed, the code coverage plugin is installed, the forensics API is installed, so everything else is there. But the view is not there. Speaking of that, where do we stand with ci.jenkins.io as code? Because once we have it fully automated, we would be able to quickly experiment, maybe even to deploy preview environments. We go all in. I know that Damian was looking on that, but I'm not sure what's the background status. So I'm currently, as for today, writing an email to start the discussion on the info mailing list to explain the plan. The idea, what we discussed first privately for a good reason is that it was just brainstorming. So now we're switching the brainstorming and writing the plan publicly. The status is we want to focus on managing only the agents as code for now. The reason is because if we start to do a big bang update from the current status for that instance configuration to full config as code, that will be nightmare and breaking. We want to do first tiny iterations that we deliver, which means to answer the topic here. The plugin management as code is not forcing for now, at least not for the upcoming three weeks, because that will be too much work on one side. We first want to have something and the agent is the proposed priority. However, that's a proposed plan that can be changed. So don't hesitate to raise your voice following my email later today. That means manual and install and uninstall to put things clearly. Yes, the problem is manual install. The problem is evaluating the purpose of these plugins need configuration, right? Well, they are configured in the user profiles at the moment. So any logged in user can do something. You anticipate my next question, but that's the point. We will have to define. Yeah, that's not the topic right now, but we will have to discuss before installation, where is the plugin storing its configuration on the file system. So we are sure that in any case we can know what is happening and how to roll back if needed. Currently, it's only stored in the browser. No, sorry. I don't know, forget it. Sorry. That was our first plan, but in the last meeting, I think Tim suggested that we store it in the user profile and the Jenkins user profile. So it's now in the Janker user profile. Yes, Janker user profiles can be technically managed as code. Practically, it's almost impossible to manage them as code from JCAS plugin. Okay. So what it means that any user would have to basically manually go to the profile page and configure it. So that's why I was bringing up whether we could have defaults or whether we could have views, because for example, you can imagine that there is a view like the dashboard view plugin. And yeah, there you can just put some default layouts, default reports, so that any user visiting this page can go this, let's say, analytics tab or, well, I know that they are saying dangerous words. But yeah, for example, not analytics, but yeah. So just a view which can be configured and whatever. So, well, I'm just creating ideas and probably I should do that in GitHub issues, but yeah. Thanks for hearing me out. Yeah, I think we need to spend some more thoughts on this configuration, especially for such a big instance as our instance. Okay. Any other questions here. So that one really the, the status of ci.jenkins.io configuration is code was really sort of a part of the discussion around that okay got it. Next topic then the new version of the each arts plugin. And still is in progress, but I already showed last week or last for two weeks ago, that I'm trying to make the train charts configurable. So maybe I can share my screen. I can't share it. Mark, can you give me the rights. So, what we currently have on the top page here is the trend charts and currently the trend charts are just for starting from the top and going down. Yeah, there are a lot of trend charts here because this is my demonstration instance. Maybe you don't have so many a trend charts. So, up to now these trend charts are not configurable that means all what you see is hard coded somewhere in in the server side. And what I know, what I'm now adding is a configuration button for all of these trend charts. For instance, here the forensics trend where you can see the commits in there you can have a trend chart that shows the others the commits modified files and then we have here a configuration button. And if you press this button you now get a configuration dialogue. And in this dialogue you can, for instance, change the chart type. This is something that a plug in must support of course, but here my plug in can show up to four different trend charts. For instance, I can show the total number of files in my project. And then you can say okay how many bills you would like to consider to show. And yeah, how many days you want to look into the past, and then you can save this dialogue. And then the trend chart here immediately changes and you see a new trend chart with some new options. I integrated this kind of configuration for the forensics plug in for the warnings plug in so for instance in the warnings plug in. You can configure also some different trend charts you can see the new and fixed issues for instance if you are clicking this and say okay let's say I want to see the last 25 bills in my trend chart, and you save. Then you see not the totals anymore you see the number of new warnings and the number of fixed warnings so this is maybe somehow useful for teams to show different trend charts for different plugins. So of course the configuration requires that a plug in offers different trend charts, but using the e-charts library these trend charts are really easy to implement. So for instance Tim already created the test result trend chart also with e-charts. And here you also can configure the trend chart currently we have no different trend charts just one trend chart, but at least you can now change the number of bills you would like to see in it, for instance. So this is something I'm currently adding in the e-charts plug in it's running with bootstrap five. So all these trends are rendered on the client side only that there is no connection to the server currently. And yeah, this is something which I want to even extend so for instance that we can create a different sizes of the charts, etc. And in the end maybe we can also use this dashboard where we can drag and drop those trend charts, but this is something you know which needs some further exploration. So this is my plan currently for the e-charts plugin. And one thing which I would like to have a little bit of feedback is about the configuration. So currently the configuration of such a trend chart is split into two different parts. The first part is some plug in specific part for instance here you can choose which trend chart you would like to show. And then we have some kind of let's say general configuration where you see if the domain access should be a build number, or if we should show days, or if we should consider maybe let's say 20 bills, or how many days we should look into the past. And I'm wondering if I should make the general configuration global for all charts. That means if I change it here, then all other charts will be updated as well. Or if it makes more sense to have a configuration per chart. So this is something I'm hoping to get a little bit of feedback in the next weeks to see in which direction I should implement it. So any questions on this new idea here on the job page. I think it looks great. I'm not sure where you would place the control for a global setting. So for me just the placement on the UI lobbies for keep it local to each chart, but but that's I guess a design thing and I am not a designer. Yeah, currently you see when you open the dialogue, you have it in every dialogue in the lower part. So one question is if I change a value here. It changes only currently one chart and the question is if it should change the other charts as well. So, I think it would make sense because from the meaning of the parameters from the width or from the number of bills it would. It would make sense to have it the same value for every trend chart, but I'm not really sure. The tools like Grafana works work exactly like that by default. So it makes sense to follow this behavior. And yeah, whoever wants analytics that they will likely want to just eventually have various your controls like you can just select a time frame, etc. And then zoom in. So if you're familiar with Grafana UX, yeah, eventually we could have something similar. Well, no hope, but yeah, maybe more navigation UI for analytics reports. That we can just turn from the best and follow the example. Okay, so what I also thought about is currently you have a configure button for every chart. And maybe it would make sense to have some kind of, yeah, this dialogue is a little bit old school here. One button that configures the whole dialogue here, for instance, which trend charts should be shown on a user basis or how is the order of the trend charts and things like that. This would make sense in my opinion as well. So currently this is hard coded on the Jenkins side. But maybe I'm not really interested in the last successful artifacts. So I want to hide it as a user and I want to show these trends charts on the left and on the right. So this would be possible with the same dashboard few kind, which is Simon proposing. So maybe, yeah, we can try to use such a framework as well here on that page. And then we need a global configuration where we can add portlets on this page, etc. If that makes sense, I don't know. I think that makes sense to me that sounds wonderful. I'm still not sure that that could be why the topic maybe don't seem to ask over mailing list or so to have feedbacks. I mean, that means a wider audience on my side to be quite transparent. I'm not really at ease by using metrics inside Jenkins UI. I've tend to avoid as much as possible to go to the Jenkins UI. So I don't have any use case that could help here on my side to really take decisions. So I'm sorry, I cannot help but I think a lot of users are doing and have the same leaders the one you have. So that that's why, why don't you think that question could be really interesting and get you valuable feedback. Yeah, I'm a I'm a heavy user of of metrics inside Jenkins. So, yeah, I, I think there are a number like me who are using the metrics, the warnings and the code coverage API views. Yeah, I think it's the best thing to release a small iteration and let the users talk about the feature. And then we will see how we can improve it. Okay. So, if there are no other questions, I think we can continue with the next topic. Okay, and I stop sharing again. So, next was next topic was from Oleg feedback on using Jenkins funds. Yeah. So, well, I'm trying to somehow keep working with community excited and post those things, sometimes questionable things from time to time. And yeah, encourage everyone to do the same so that we can repost more people from the Jenkins account. So one thing I raised is actually about using funds, because we have some funds, and all effects outfunding, you see other threats and the developers may increase. And yeah, just asked in public okey, so how should we spend them and he is to dance and design your improvements. From 45 for votes. Again, don't consider it as a kind of official polling results or official decision but well it's curious data to get anyway. So, yeah, what I'm bringing up to the team with that. So, if you have any ideas in mind we have things like the effects outfunding effects mentorship, so we can find either official paid mentorship or official and paid mentorship. We can have an opportunity to define our own programs because some effects mentorship is, let's say, will some of course as a service, to some extent. So, we can organize various events. And, for example, maybe for this. If there are some programs you would like to run, you can do it through this program. Money is something we can discuss and yeah, I have another topic below which is also related to money and outreach, so you can proceed and listen to the comments. But yeah. Highlight. Yeah, your design improvements is highly ranked. Like, I would surprise anyone by telling someone about Jenkins. We have money and we use some of them. I think that that matches my hopes. So I like that a lot. Thanks for doing the poll. A great way to ask the question. Yeah, this is a good idea if we need some designers for instance for icons or something like that. This would be a really good idea to have someone paid for it to draw it because as a developer normally it's not so easy to create a good looking icon. For instance. Oleg, you had the next topic as well on collaboration with open source design. Yeah. So, a few weeks ago like we discussed the governance meeting I was invited to join open source design nice student committee meetings. Well, it was a group of 10 people use different backgrounds, etc. But open source design is a well known initiative focusing on open source design. Specifically on user experience out for design work. They have multiple tracks, one of them is related to just one specific proper design best practices. And they have a listing of projects. So I added the link below. So they have a list of projects which are specifically focused on user experience design. And well, yeah, I'm planning the official low welcome from the Jenkins project but I think it would be nice to just have us listed there. So if you're sick, maybe you'll allow to bring some contributions, maybe not, but definitely doesn't hurt to be a list of that. And you also was thinking about adding some ideas to the Jenkins to the job sport. So if you go to open design jobs to the link. There are multiple types of ideas, including once which are just artists so basically feel free to contribute and we will have shaped that sense some swag. For example, and there is also but you need to pay to put paid ideas. For example, the paid ideas are supposed to be largely paid. So let's say some bonds like $50 or $100, what do they consider as paid. So for that, they offered me to send a message to the discourse about how it will be posted because they would be also interested in this small bonuses. Like freedom sponsors and other things work. But yeah, at the moment, they don't have approached for that. But yeah, what I am thinking about it if you have some ideas. I'm still yet to create the Jenkins through logo, and they may have a few other requests. So we invited to post these opportunities on this board. People visiting them they also the post opportunities in the social media so that it would help to find someone you meet Mark. The idea is we would, we would post this jobs board here is actually for tasks that might be done or bigger picture things it's not just for. Design a logo looks very much a task and whereas design contributors is looking for people so both those are allowed here and now you said that and we could fund so there's a paid option as well that we could we could use then to Incent. Yeah, but well it depends on what exactly we do so it's not like we can throw money in there we didn't have much money, but we have some. So we could put them to use. Basically, how it could work here we can just use this job board, you could just maybe create a separate repository for issues or use Jenkins IO is artwork label, like we do now. So that we could also promote it on our side. But yeah, I believe that we could come up with so many ideas there. You just need people to write them down. Actually, it's actually a Google form. But once you submit a Google form they have magic which converts a Google form to pull requests. And while I am curious to know more about this magic because it would be useful for some Jenkins use cases. But basically we can also submit a pull request against their website directly. This information. It's not documented but yeah they confirm that possible. Excellent. So it's and like Google form is this button. Yeah, so yeah, well maybe it's not even a Google form. But yeah they have this form you fill it in and then once you create that magic happens and there is a pull request submitted. Nice. Elegant. That's really elegant. Okay. Yeah, it could be a good implementation for some of our use cases theory. Yeah, maybe it could be some combination of GitHub actions. So it could be other kind of automation like integration without chatbot. I don't know. But it's definitely possible to create something like that. And for some use cases might be useful. Yeah, that looks really so so the next steps then would be form submits pull requests. I go ahead or like next steps. Basically what to encourage you to do if you have any ideas, etc. I already start the Google doc where basically put a brain dump of ideas where you could use artwork. For example, yeah, like Jenkins for log logotype for the contributor summit in June, the ship has sailed but in principle, it's been good to have a logger. So, for example, I put idea of a special logo for a different client plugin. So ideas like that. And if you have something in mind. So I can totally imagine that you will forget plugin for Jenkins we might use a logo. Why not. If you have such ideas, if you can formalize them maybe maybe somehow have this brain dump and convert them to ideas and post them. So the next meeting is on the next week, I intend to send a traditional from myself through the discourse. I also intend to post some jobs request. This is my action items from the previous meeting. The meeting is monthly so yeah by the end of the month makes sense to actually do action items. No guarantees at all but just sharing the context. So and that that document, could we link to that. I haven't published it. Oh, okay, got it. Okay, so my work. If someone is willing to contribute I can make it public. If nobody's interested. Got it. Thanks. Yes, maybe it's a question for me because yeah, I should definitely send the summary to the mailing list maybe even to the developer mailing please. Use the meditation for others to contribute. But yeah, right now that's what we have. Maybe I will build a flow. Excellent. Thank you. Anything else on open source design I don't think so. So we also shared some expertise in terms of organizing events. They actually looking into what they could do with their budgets and how they could put, because they have small budget based on donations. And they are wondering how they could use it efficiently. So we shared some experiences, maybe eventually do a joint event. But it's rather hand waving to this point. I'm not sure what they will have been like, but in technique, technically it's reasonable. So and when you say a combined event it might be something like a open source design event focused on the Jenkins project or why not. We already had your UX hack done last year is some offerings to work on design. But we didn't have much traction for this activity, but we, if we engage with a vital community like open source design. I think it could be a win win. If we provide quite a diverse set of tasks and not drawing 100 versions of Jenkins for meetups. So you can go out of the box like sending requests for icons because we have iconography reward pending in the project. So such requests could be definitely done. For example, plug in logo types, etc, which could be a bit more different. For example, for the tone I offer that we use pick on puppy but pick on puppy dressed like a partner in pick on colors. It might be completely terrible. Or another idea in my brain dump was to just have Jenkins logo, but again, we stick to on puppy. Not to pick on puppy on a plate, of course, would suggest something different, but maybe a new type of logo. But yeah, so yeah, things like that. And if you're interested and want to get creative, I think it meant a lot to such a particular interest. Excellent. Thank you. Okay, let's see you had mentioned you ex SIG logo. Well, next on the agenda was me replacement for me as scribe and meeting launcher. So I'm donating a kidney beginning the surgery is June nine. So our next meeting I won't be available. Do we have a volunteer. Yep. I'm volunteering to take over the next one. Excellent. And given that volunteer thank you very much I will send the request to the advocacy and outreach SIG to request permission request permission for the CDF Jenkins zoom account to Damien. Any objections. All right Damien you are you are you're chosen by acclimation congratulations. I will just double check the, just the task list to be sure I don't forget anything. That means that I have to to start the call to take the notes drive the call itself. Is there are there other tasks that are expected that I should take over that. So Oleg would we expect that he would upload the recording to YouTube or is that something that would be a different permission do we need is that something someone else would do. Well, there are multiple options because one of the things you can just record to the cloud. Somebody can repost of it. Or you can. Yeah, you can get YouTube permissions. Documenting how to get permissions. But we are quite relaxed to have something 14 content managers or so. So the top did the job based on the recent people in his organization policy changes. But yeah it's documented. So please refer to job 13. And there is a process explaining how to get YouTube permissions if you want. 13. Yeah. I'm currently checking the 13 and adding the link. Does that mean that I need a YouTube account or something. I think you just need your Gmail account. I believe you have a Gmail address. Yeah okay I might need to create a new one then only for that, because I don't want to have a personal account on YouTube so okay I will take care of creating one. Yeah I'm one of 2008 persons. Good for you. That's great. Not it. Okay. All right. Oleg last topic. You exit logo. Yeah. So I'm just reviving all the logger. Sorry all topic because the current situation if you go to your sick page. And if you try to post it on Twitter and whatever you get to this icon of two persons. And it looks pretty better especially in open graph. So yeah my question to the team is, yeah, originally we discussed for the, we would like to have another logo job, brookie. Has great support types. Jeremy Hartley has great sample heads but we have never selected anything. So I just bring it up to the team, especially taking open source design, etc. is that maybe it's time to actually have something as a logo. So in the worst case possible to just get something like, let's say, well, Jenkins Margaret as a logo, or the logo, also Jenkins meet up, please do not Google that. But yeah, putting it as your sick logo would be hilarious. Yeah, well, it belongs to memcans, but in general, I would be happy to see that. So, yeah, I'm just bringing this question so if somebody drives that maybe we can find this ticket is a logger, even if it's existing image, because it's better than the current situation when you have no one as you're sick. Could you, I missed what what you had said, what does it currently look like it's a, it's something. Yeah, you have a. So you go to the exit. So there is square look resolution logo of two persons. So it goes to open graph as well and well square logos don't look well enough graph at all. It's a special low resolution so when you link to this page, for example, if you're, so what I do in Twitter, if you're concerned about Jenkins user experience you I feel free to contribute we have user experience page link. And then this logo counts. This week. So, yeah, that's my key just why I want this logo to be replaced. Yeah, because if you want to contribute us everything doesn't really help and it will be between. Yeah, so it could be to reuse it could be any one of these kinds of logos here in the artwork that would certainly be better than that low resolution square image. I think I understand what you're saying now this this image as an open graph image is looks really poor. Do you mind guiding us how to see. I have no idea what open graph is to be quite honest so I've just opened the open graph page on Google right now. They have no idea what it's about, but is it possible to show it here and the recording. I'll show you an example just a second. Right now. Yeah, so I was going to show you so I opened the page and I look for og colon annotations and there's this one og colon image, and this shows me the page that is used for it. So if I open that it should show us the oops, except I don't want to see the source. So when I do that it shows that's the an open graph is this standard that I think started with Twitter or like did you want to share your screen to show it. No I don't, but I'll put a link just a second so that you can share it. Okay, great. Yes, sorry for exploiting you but yeah I have some sensitive documents open now and they don't want to forget. Yeah that'd be great. So, yeah. Okay, so how we do it. In, for example, meetups, etc. So you have a Google Doc. If you open the agenda, I put the link there. Oh, you put it in the agenda. Okay, sorry, thanks. Yeah. So then you can see. It's basically our dump presentation, which is slightly quickly growing a bit too big. So basically open graphs are standard size images. This standard size images slightly depend on what you use but it's basically 1629 usually. And here we have just long, long Google Slides where you put all meetup open graphs. Content and yet a good thing about that, why I use Google Slides. Well actually you can just create the image PNG or whatever in any editor, but here you can create the machine Google Slides and then download a particular site and PNG and you get it automatically. So that's why I used that. So basically these are the images and if bigger page has metadata, LinkedIn, Twitter, etc. they show this image by default. Oh, that's the preview image stuff that we have sometimes. Okay. Oh, okay. I was feeling to understand the, the consumption part. Okay, thanks. And there is also a description for pages which is also goes through open graph metadata, which was used for some pages but yeah the images are quite sensitive especially for Twitter. Because yeah in Twitter, you either post a link and then open graph picks up and the entire image becomes a link, or you can just attach the image but in this case this image won't be a hyper. So yes, so tweaks apply, but it's better to use open graph. Okay. Thanks. It's clear. Yeah, and yeah I found the image I really want to our York seek adopt and to use this images log until our goal is achieved. Yeah, this one. So yeah. Well it's rather a joke, but yeah, I would definitely put it as a log if I was a basic leader. Well, maybe pretty fight version, but you know, the painting. That's a classic yes beautiful okay. I vote for the for the HTTP. Well, actually, I'm about to Google asking somebody to create a more pretty fight version because this one just stop Jenkins had on the page so we somebody creates something let's say more well integrated. I think it would be hilarious. So I don't recognize the image is this isn't the screen by this is a different screen. Okay, all right. So yeah, because although it was from Oslo, so they decided that it would be a great logo for us. Excellent. All right, anything else on that topic. Okay, any other topics we need to cover today. All right, let's call an in for today thanks very much I'll post the recording later today. So that it's available. Thanks everyone. Thanks. Bye bye.