Cool, well welcome everybody to the next iteration of the UX SIG meeting, small group today. We have our typical items, obviously nobody new today, so we can skip past that and dig right into some updates here. So the first one, oh there we go, hey Jeremy. So the first one on the list here is called welcome screen UI, it's under this title of empty states and we'll see why in just a second here. So I'm going to share a brief design deck and then we'll talk about implementation. Shall I take the minutes, Joe, just the housekeeping notes, that would be great. Sorry about that, I forgot. Yeah, I'll take care of that then. Thank you. You're welcome. All right, so the item we're looking at here is the welcome screen UI in Jenkins. We had talked about this previously, I think, real briefly how we wanted to improve this. So here is what the design currently looks like. There are a couple of different configurations possible in Jenkins, depending on the user's permissions. But here's the current state, you know, grayed out all of the other elements here so we can focus on what matters. And here's the updated design. And to note here that this is very much still a static mock at this point, this is not being implemented yet and Felix can speak more to that shortly but this is very open to feedback at this point still too. So looking at this, some key takeaways here that this, the goal of this is to improve the usability by doing a couple of things, making the style here more consistent with the other components that we've redesigned. And also by providing additional context for the situation. Everyone on this call is familiar with this state. It's not an entirely common state, certainly. It's not even really arguably that confusing. But we have an opportunity here to introduce a formal empty state treatment. And so that's what we're trying to do. And we'll look at some more variations of that, but any questions or thoughts on that before we dig further? We have like an image, not just something to. Oh, sure. Is this, sorry, is this not showing up? No, no, no, I mean, what I'm seeing here is all text. I'm just wondering if, you know, we have a lot of empty real estate, can we just show a pretty picture or something? Gotcha. It's not. It's a pretty common thing to do that with empty states, right? And it offers an opportunity to inject some personality in there. I don't see why not. I personally lean toward keeping things more minimal and not overwhelming, especially since the configuration here could be a little bit, you know, depending on the permissions we might be offering three different options here with external links already. I could explore that if that's something we think would be useful or beneficial. Maybe we could get the Chuck Norris plug-in print still to the non-habit shots first image. That's what I'm not too sure about, but you know, but something agreed, there's an opportunity there. Whether it can be done gracefully in a way that doesn't push the more important detail is here out of the way, I can explore. So let me check into that and provide a mock-up for you in the next segment, actually, we'll talk about it sooner than that Jeremy and maybe like kind of like a line artsy kind of Jenkins figure, you know, like a light gray, just, you know, I don't know, just thinking something subtle, you know, yeah, there's there's an opportunity here. Yeah, I think I think there's probably not much more for me to stay on it right there or for now, except to say that that's worth exploring. So let me check into that. I quite like it. Like it's a lot nicer that I think from the existing one. I was wondering, the one bit that I'm not so sure about is how it's got like create an agent, configure a cloud and create a job. It's kind of like the first one is two different options. And the other bit I'm wondering about is whether CDF an agent or cloud should be as part of creating the first job. Yeah, it's a valid question for sure. My goal here was really just to to update the style of what we currently have. And so to provide those same options. This could be an opportunity to to reconsider those a bit. But I think that is a slightly larger discussion. But what would you suggest there? So one thing, so the first one, it's quite clear that you create an agent or configure a cloud to this one here doesn't really convey that it's one of the first two options. I could say that, yeah. I wouldn't get too hung up in copy text because this is just the same mockup. It will need to go through copy editing process anyway, so. Yeah, this is a good point. Thanks, Felix. It will need to be verified. The copy that we see here will need to be reviewed by the documentation writers to make sure that it's clear and consistent. I do see your point there, Tim. I'm not sure that we want to solve it right now. The goal really, the scope here is just to change the style. Yeah, I think it's a big improvement. That welcome to Team Kansas always bothers me that doesn't feel right. Yeah, ironically, I actually like the bit of personality with welcome to Jenkins personally, but I think it's more important to provide some context here and say what would actually be here and why are you seeing this message? Yeah, great. Yeah, Rungsha. All right, cool. So just to reiterate for my own notification, so, Jeremy, I'm going to take a look at what we could possibly do. There was something more visual and Tim, that's a good point. Let's keep in mind that we're going to have to review the documentation here about the copy, but I think we're not going to probably solve how these relate to one another right now. This is just more really stylistic for the moment. Yeah, even with the we're not going to have so much to say, but whether you can separate the top and bottom section a little bit of the agents and jobs as separate things. Yeah, maybe. OK, I will take this into consideration. And this is something, you know, I mentioned here that this kind of introduces a formal empty state that could be useful throughout the rest of Jenkins. So this is in a way just the start of a new type of treatment, right, that could be implemented in many other places. And we'll actually talk about that pretty in depth in the next meeting. But that's good feedback for for taking into that consideration of how we could have options relate to one another more more intelligently than just a stack of items, perhaps in the future. So just like with the current UI, depending on the users permissions, these options might need to change. So just a different iteration of this is just the option to create a job or an agent or even depending on the sign in state, the options to log in or sign up, again, not trying to introduce anything different in functionality here, just an adjusted style from what currently exists. And I think I may I may be repeating myself, but really important takeaway here is that just like with the rest of this initiative up until now, we are trying to improve these experience through improved style, improved design. So it's really key that the interactive states are as consistent as possible with the other components that we've implemented as well. There's some slight deviation in the treatments here. But this component also exists in a different context within the UI and it gets a different background than say a particular nav item in the side bar. So it does require some different treatment, but using the same color palette, the same text styles, that sort of thing. But somebody going to say something a minute ago. Sorry about that. It might have been made, but it's OK. Sorry about that. And the last item here was just seeing it in context. You can see that it relates back to the other improvements pretty nicely. So we're overall just like with other components, making a more consistent UI piece by piece. Nice. Any anybody else for now? If we can move ahead to the implementation detail discussion. For sure. Yeah. So I was doing some tech analysis of these improvements. And I did find out that this is something that if we approve and go ahead with this design, it will be tough to support the existing translations for the empty states. First of all, the copies change. We cannot do anything about it. But also the way the current translations are set, they are the each line is online. And the hyperlinks are in line within the translation. So what that means is that it's going to be tough to actually be able to implement it without breaking translations, without breaking internationalization for existing localities. I don't know if that's acceptable or if it's not what an alternative could be. So I appreciate any ideas on this one, especially with the theme. Do you think it's only for the welcome screen broken or for everybody who is using that concept? I know it's for the welcome screen. I would guess it's for everything. Okay. They use it as that state. So the translation is just default back to English, if the text is missing. Yes, but I mean, maybe we're for everybody to just see again if we were to a huge English block. I don't know. I mean, I think that's kind of, you know, just the reality of making changes to new elements that, you know, new translations will be required and we have a fallback to English. And the localization teams, if that's sufficiently motivated, it will hopefully come. This is one of the least seen screens by users. It's only seen by the admin when they first install it. Okay. Yeah, I just wanted to mention it then. So if everybody agrees, I can go ahead with a PLC. Yeah, I don't really understand the problem. I mean, I just don't want to break old, like I'm looking at them right now, almost 20 to 30 translations localize. So if it's okay with everybody, yeah, it's okay by me. I will go ahead with it then. And also something that you may have noticed, I mean you, because you may be the most interesting that I think this is an opportunity to sort of introduce some sort of card component here. We will try to make reusable components, not ad hoc stuff. We will try to do reusable stuff that everybody can use later too fast so that Jenkins can finally have some sort of card. And I dreamed big the other day and maybe I have the idea that for people with a more skill of extensions point at night, this could be a listed in this sort of screen, could be a good place for, for example, imagine that maybe the list of call to actions could be an extension point. So that plugins could register another own call to action. For example, the pipeline, create a new pipeline or a cloud agent, create and register your your agent or I don't know if Jenkins could have something. So that's just an idea I wanted to float. I don't know if necessarily that's a good one, but maybe it is sort of the least format could enable us to do it. Yeah, one thing I'm not understanding is the bottom line is this the title or what is the idea of the learn more about distributed builds. So typically you have a title for a card and not a bottom line. So I understand it as a card footer or a content block footer and it's more for the more bottom. Okay, exactly. It would be the equivalent of this item here. So if there's a relevant documentation or external link, it exists in a different place in the anatomy, but it's a card footer essentially. Yeah, I'm not sure if this kind of component will be used by so many plugins because this is the idea of Jenkins is to use everything by code and not by clicking around in the near future, hopefully. So this is something which is more a kind of wizard thing. And I'm not sure if we have so much requirements for providing such wizards. I think a lot of people are using Jenkins configuration as code to set up the whole instance. They don't want to use any UI to configure the Jenkins instance. I think this is more for the first time user day.  And this I think is the good start towards that. And I agree with you that I mean, if you're experienced, you won't be using this. You'll hopefully be using some kind of automation you'll know what you're doing, but... Yeah, to that, I was also wondering then, just for this particular screen, instead of the title, No Jobs Created, I think that's already very specific. I mean, like, okay, we know that this should be where the jobs are listed and it's nothing there. So we want to create a job, but maybe just, you know, let's create a job or let's start building or something like that to be more towards what users can do or want to start doing instead of trying to figure out, you know, jobs, what are jobs? Yeah, you know, these kind of questions, you've got a really first time user, like Jeremy just said, this screen will be mostly used for. Yeah, I think that's really good feedback. Thank you. It depends a lot on how we're thinking of this and this is the first time that we're introducing like this type of card, right? But if it's specifically an empty state treatment, there are different ways of coming at that, but either way, this one does establish how we label these types of states. And I think it could be a title that's more geared toward something a little more actionable, maybe a little more positive, as long as it's specific in explaining why this state exists. So I agree and keep in mind too, this is placeholder text, but let me update the mock with something a little bit more appropriate and we'll see what the docs people have to say on it too. I think that somebody stopped me if we're not ready to move on and that's totally fine, but I think we may be for the next item, normalization of different colors. Yep. Okay. I just wanted to talk about I've been working the past few days. I was looking at the user of different colors, different grays, especially the grayscale on Jenkins. I found, but also about all of the hard-coded colors not currently stored in variables on Jenkins code base. And it's a bit of some sort of overwhelming task, basically. My initial goal was to try to, okay, I'm going to get all the grays fitting into these five colors that we have available in our palette. That's yet not possible because many cases, the design, the existing design of certain components depend on that. For example, the job configuration or the new item list, option list, the new colors don't look right. So that sort of needs a bit of a redesign and that's okay. So that said, I'm going to probably be landing a PR with some sort of normalization of colors or I think it can be a good chance to see how it will affect, sorry, how it could inspire other plugins to do it. Yeah, it was just an update of what's going on and what you can expect. And it will mostly be focused on the grayscale, grayscale and not on all the inline success grays and grays. Can you give a few examples of this? Yeah, let me look at it. Let me look at it and see if I can have something. The basic example of it is if you search the CSS and the Jenkins code, there's like so many different grays and some of them are using the variables and some of them are just using very slight different Yeah, but I mean, is this kind of, I mean, I guess what I'm fishing at is this a is this a problem from a code neatness point of view or is this a user experience problem for the end user that there's so many grays? I mean, I understand that it's obviously not nice to have CSS with part variables, part none and No, it's more of the former. But in the end, it leads to inconsistency. Yeah, sorry, it isn't directly a UX problem too, right? Because it's really important that so each one of those subtle different grays that we have in the palette we've established here with the sake means something and carries connotation. So having that inconsistency does harm the experience, generally speaking, over time. Sorry, sorry to interrupt. Yeah, so one example to continue something I touched was light backgrounds. For example, like we have like stripped rows, like the side panel Hover FX. That's a light gray color, which is a fade, fade, fade. There were really, there were a lot of similar several similar light gray colors that were not the same. Used across Jenkins. So what I'm doing is trying to consolidate all of those into using the palette one, the palette version of it. Also something that's something I was actually, I was able to do something that I skipped and I ignore was, for example, the colors of input elements, form elements, the borders, because I don't know how to do it without making them too similar to the secondary buttons, to the default buttons. And that's something, it's basically something that needs to have proper design attention, so I'm skipping it. It's not, it's less straightforward than I thought. Makes sense. I think, unless you have more to share on that for now, Felix, next item, I believe. Yeah, I think we'll change some design iterations. Okay, so we merged the tables, 1000 tables PR, there were some feedback. Congratulations. So now, thank you. We had some feedback. Feedback is spearheaded by Iuli. I sort of, I implement a few of those items, for example, I created a compact variant of the tables for the, for the, how do we say, the project view, the main view. And I'm wondering if we should, how we should proceed with that feedback or, because to be, I don't know if we should gather more feedback, more opinion on that, because there are many, there are many variants here. So somebody prefers the white header with, with attached tabs, white header with the attached tabs, white gray, light gray header with attached stuff. There are many combinations that I don't think not, not, I don't think everybody, any, everybody's agreeing on one. So, and I'm happy to just go ahead and do any change. So one thing I can do is try to make, to add variants in Jenkins with CSS, like I did with a compact option for the big table. I can add a white header option for the big table or a light, or a light gray header option. So that would allow table users to, sorry, plugin authors slash core developer users to add whatever flavor of table they want. Maybe that's not the best for general UI consistency, but they could have use. I can see how that can be useful. So in general, would this help or any idea of how to act on all of these different feedback? Wouldn't it make more sense that we start to provide more than one theme? So we have one theme. Now we have a dark theme, thanks to Tim. And then maybe we have a theme that has some kind of light borders theme. And we have a theme that is some kind of black header for table. I'm not sure. Hey, to be honest, I'd like to try to touch core changes from things as much as possible. I'm doing everything because the more we support things, the less we can move on and break stuff, basically. And right now everybody knows that dark theme is experimental, but if we just get everything into themes, so themes should be overrides, but we just still need to provide sane defaults. And if everybody prefers, if the consensus is a light white header with attached tabs, yeah, I'm fine with that. I really don't have a strong opinion on that one. But I don't know, creating a theme just for that, who should create it, who should host it? So there are many questions there, as I don't know. Yeah, there could be one path. Again, it's not something I propose for you to do this to Felix, but we have Neo2 theme, which is light theme and it's widely used. So if there was a contributor who would be willing to start migrating Neo2 theme to the new engine provided in the recent weeklies, then it could be a convenient way to have another light theme, because it's over the existing theme, which has some concepts, which could be adopted. Yeah, but what I don't understand is, I think it could be confusing. I mean, Jenkins default is the light theme. Why is there a need for a... Jenkins default is a light version. Dark theme feels a void, which is a dark version of Jenkins. For example, I don't see how it could be useful to spend, for example, just creating a theme and supporting it, because themes need support. Just for a light variation or something that can be done in Jenkins code. I think one of the main bits of those other themes is they fill gaps in the UI or UX experience. It's things like, it's the font, it's the sizing, it's the icons. And the icons are like a major part, because the icons and Jenkins are very dated. And some of it was just kind of giving out like a material UI look as well. But within the context of just a, within the scope of the header treatment of the tables, right? I don't know that that, my two cents anyway, that that justifies pulling that change or that variation into an entire separate theme. That's not to argue against themes in general or anything like that, just that I don't think this particular feedback justifies a whole different theme. I think one solution would be to do what you were suggesting, Felix, and make it customizable in that way. For me, I'm a little more opinionated about the style than, like, Felix, and that you're saying you could go with either one, and we just need to kind of decide, I think, but for me what it ultimately comes back to is which approach or which style, which one of those recommendations is most accessible visually for the most people. And I think in this case, it was the darker one. I'm happy to revisit that and make sure. But that's really what should be our deciding factor, because with these style discussions, it can be highly subjective, right? I have my biases. Someone else might have their biases because they use different tools. So that's all good and well, but it has to be the one that's most legible for the most people ultimately is my two cents on it. Yeah, so yeah, basically what I wanted to go is people, I'm fine with, I encourage having a discussion with and to see if we iterate. The point of iterating, of merging fast and iterating is to continue discussion. I just don't know what the best way to discuss those designs are, or how to gather more feedback or how to react to that feedback. So I'm a bit at a loss there. I welcome many recommendations on how to act on that feedback, because if the feedback there right now is different separate opinions, I don't know if I'm explaining myself. I just don't know how to gather it, or if there's any experience on this before on some sort of similar things.  So, you know, this is a very limited perspective, but we've had similar situations. This just within the UX to SIG, right, when we look back at the header bar. In fact, then it was certainly an issue of, there were some subject, subjective preferences, and it was an issue of compromise a little bit from my side, certainly, and ended up being a much stronger design element in the end. Thanks to the feedback of everyone here. So this may just be, you know, it's no one design, design choice will make everyone happy about it, especially when it's something stylistic like this. So I think this is one of those where we just kind of have to, that's why I try to come from the objective perspective of which one is the best for the most people, even more so than which one do I like better. I guess I'm not entirely sure how to proceed on it either, but Uli and Tim, I guess I would ask, does that sound like an acceptable approach given that we have kind of stylistic differences? What do you think on that idea of let's just go for which one is most visible to more people? Yeah, definitely. We don't need two options. We just need one that's good for most people. Yeah, but how do we obtain the feedback just from the mailing list? Sorry, which feedback in particular? I'm getting turned around a little bit. Yeah, for instance, to go for white colors or black colors on the borders. So I think in pull request, it was most of the people, or half people said it must be black and the other half said it must be white. So I think this is something which is screaming for, we need a theme for that. And we don't need an option that we have one table in this design and another table in another design that makes no sense for me. I think we should toggle all tables in Jenkins with one switch. And this should be part of the theme, I think. It can be done, right? A theme can happen. I know that this is just me speaking personally bandwidth-wise. I can't design additional modifications. I don't have the capacity to do that to support and constantly update a different theme. So that's totally possible. But I think for now, the goal is just to decide which one will be the choice by default, not whether or not that one style justifies a different theme, which it may. Yeah, I think mainly what Joe said is right. I mean, it is a bandwidth issue, I mean. Yeah. And obviously two themes means that you got on pretty much twice as much work to maintain it and test it. Yeah, typically, if we would have used Bootstrap, for instance, as a framework, we have 100 of themes available already. So I think, yeah, we have really a problem writing it on our own. So I think, yeah, it's okay. We don't need to support more than one theme. That is okay for me. So we should use one major theme for Jenkins. That is okay. That was one. And which one? Yeah. Bootstrap wouldn't work because the way Bootstrap is applied wouldn't work here. I can provide you with some variants. Can you send screen captures? You're getting some Docker containers going on if you can start up all or something on the on the main list. Yeah. I can provide you with all of those options. Personally, for example, I find the white header to have poor accessibility. The option is I find difficult on some monitors to see what's a header and what's not. If it doesn't have a contrast in the background color, for example. And I think defaults should take into account accessibility. That said, maybe the dark gray is too much. Maybe a light gray option could work possibly. Yeah. That's more of a maybe that comes in a statistic. Also, something that can warrant a change on header color is if we prefer to go to further iterate on the tabs and move ahead and create a detached tabs version. I want to remind everybody that we did not think there was a possibility or when we work on the designs, we did not consider the possibility of detaching the tabs because I thought it was a community choice or something that was wrong. If we want to iterate on the tabs as well, yeah, fine. I will try to provide you Uli with those variants, containers, branches, whatever we can or maybe just send screen captures and we can get amazingly thread or something going on. I don't know. I don't want to change it on my own. So please go ahead. If everybody else is fine with it, it's okay. I don't want to stop your development right now. No.  And I can just share it. What I want is to see if should we question it, should we change something? If we change which option of tabs attachment and header color is it? Right now we don't have the bandwidth to go through a poll, collect all the people over everything. And that is a hard work. The easy job is just to make the changes and I have those almost ready. So I think I also shared some docker containers with that. Yeah, maybe it's just sufficient to have some screenshots. Yeah, okay. I will get those for you. If you ask Bootstrap theme plugin, think yes. We already have some styles similar to Bootstrap. Bootstrap is also changing continuously. And Bootstrap is more of a lower common denominator that many tools can use. Having Bootstrap just removes many some sort of personality for everything.  Yeah, I don't propose to implement it for the record. I just referenced it as possible option if somebody wants a challenge. Because yeah, you can take themes from Bootstrap. You can basically replace existing templates or similarly how we do in dark themes and potentially get theme plugin, which allows to use any Bootstrap theme. Yeah, most likely it will look like strange, but technically if someone is up for a challenge, it's possible. Yeah, I want to remind you. Yeah, the thing is Bootstrap, it's not a stylistic set of style of opinionated style. It's more of a Bootstrap-ish framework. It's a tool. And that tool does not fit well with the way Jenkins is done. So it's really awkward to integrate it into Jenkins code. Really awkward. And it will have no backwards compatibility options at all for anything. So there's the Bootstrap styles. There's no such thing as Bootstrap styles as a design guideline or something. They are just the default styles of a framework that everybody is supposed to if they want to change. So that said, if anybody wants to create as much themes as they want, the customizability is there. Lots of CSS variables. Everybody can go ahead and change everything. Yeah. Okay. So do we want to talk more about this topic or can we move on? Yeah, one thing from the Jenkins Core maintainer perspective. So we integrated the current implementation of tables and the weekly release. This weekly release, unless something goes wrong, is likely to become the next lcsb line. So it means that current dark headers are going there by default. If there is a decision by the seek to change that due to whatever reason, then we need to know about that. Let's say by the end of August. Because this change can be backported. But in principle, all styles and changes which we integrated into this weekly, most likely they're going into lcs. Yeah. The way you see it is iteration will happen every version. So we can iterate, we can go ahead with, in my opinion, we can go ahead with this. And then maybe for the next LTS or for the something, we can maybe we can try new headers. We can also try new icons. Hopefully we will try the new icons. Maybe a revisited header and breadcrumbs. So iteration can happen across versions. There are some stuff that I don't foresee we will change that will remain static. For example, buttons, hyperlinks, the sidebar. So there are enough elements that are going to be and that I have a high degree of confidence that aren't going to be changed. Yeah. So yeah, my point, I think in circles sometimes, I think we can safely go with this if nobody's against it. And we can iterate on the November release. No problem. Yeah, that's why I liked the LTS because let's say if there is strong negative feedback coming in the community, we still have an option to change it in LTS. Maybe even keep it as is in weekly and keep experimenting there. But if you want to do that, it's really nice to know about it by the end of August. The great thing about this is that these changes can also can be safely applied on the incremental on the releases and be reported. If we are only talking about variable changes, we can change it for a point two or something. Maybe. Yeah. As long as it's only variables. Thanks for pointing that out. I think we have different, within this group, we have different views on the stylistic preference, and that's okay. But since we since we are at a tiny, not a very big one, but a tiny impasse there, I think we having having it in its current state where it's more accessible of the solutions to more people is fine and we can change it in the future if that is correct. It's the right path for me. Sorry, go ahead, Felix. I was just, I was going to say, yes, we move on because we have 15 minutes. Yeah, we have an important topic, future work. Yeah, future work. I just wanted to share something that, yeah. So at the beginning, we, well, within CloudVis, we all together we created this roadmap. With roadmap, I mean, all these set of goals we went up to achieve. Headers, iconography, iconography, we went push down the line. Headers, typography, footers, buttons, tables, hyperlinks, side panels. And so we wanted to focus on core elements that would affect the whole UI. And we believe we are getting there. And we are comfortable ending this first phase of CSS only changes to end the CSS only changes or the CSS based changes after we maybe do the empty state buttons. Maybe we can revisit the header breadcrumbs and the table headers because the header and breadcrumbs need for visiting. And then I would consider this phase finished. I don't know, I cannot think of any more... It's still left as empty state, CSS. Sorry, I just want to get this. Iconography and revisiting header and breadcrumbs and table headers maybe. And I think we are at a great place, especially if we look at our before and after for the Jenkins UI was in January and now those bigger overarching changes. I cannot think of anything else that's better. And then we could start looking into deeper surgery as Jeremy likes to say to more important changes. What do we want to work on? Do we want to focus on forms? Because we have momentum working on forms. Do we want to work on the job history page? So that's sort of sharing. I don't want to start a huge discussion on what to do next. I just wanted to mention that we are meeting the end of what we want to call phase one. And that's okay. I like to have some closure. And to be able to say we are done, we have achieved. Yeah, just by the way, I'm in the process of writing a blog post for the CDF blog, which will be talking a lot about the work that's done so far and trying to get people to join the rest of the effort. So I think it's important that we have a good roadmap of where we want to go to next. Form seems like a logical one given the table to div kind of moves. Shouldn't we include table to divs on the list of spots still left? No, table to divs is a different initiative. I don't want to, we have this goal. I would like the ceases only changes. We have this goal. I don't want to have a scope grip. I just want to be able to have to compartmentalize maybe and say these different sub projects, we are done with them. It's better for everybody to have a scope grip there. Makes perfect sense. Sorry, I'm just watching the clock here. Tim, you added a couple items. Did you want to share a screen for these? Maybe for the dot thing, briefly. Okay, I'll stop sharing here. Yeah, I'm done talking. But how are we going to, I mean, I think it's important that we do try to define what's next because I mean, I think it's important for our first of all, our stakeholders at Cloudbees that pay your salary, that we have a clear, you know, pipeline. This is what we want to do next so they don't reallocate you to some other projects, which is always a danger. And second of all, I mean, I think, you know, we're trying to want to get people excited about this and to join if we have a clear road map. You know, we've done all this work. It's great.  This is what's coming next. Come join us, you know? Yeah, 100%. I just don't think we have time on this call, but 100% agreed. Well, maybe we should put it as the main agenda item for in two weeks where we try to think of, you know, collectively brainstorm. Sure. Collective brainstorm. We can also look at the road map and we can see if we have UX research capability to see what the actual user interviews, to see what the pain points are. There's lots of ways we can decide, but I agree with this topic for the next session. Okay. Let's quickly do a brief demo of the new dot thing release. All right. And so released 005 this morning. The main change in it was aligning with the tables change. So now support. So it works with the latest weekly. And without this change, it didn't look very good. So that's done. And also added the text area handler, which is the drag down and adjusted some texts, adjusted the dark link colors and alerts. I'll just quickly show that. So this is the, this is the new alert used to be quite a light yellow. It still stands out, but kind of experimented a bit. And it was quite difficult to I think it looks quite good. And it's not everybody's gonna like orange, but I mean contrast well with black I think. So we've got success info, warning and danger. Okay. I definitely don't like warnings and error colors, but I guess it's the best thing for warnings because you may want to get rid of them. Yeah. So 100% open if anyone wants to do any experimentation. So the theme and capability for it's now in Jenkins core. So anyone is welcome to fiddle with the colors. They're more, I think they're more readable now than they used to be. But it's something. Improvement. Yeah, I started with this. I think it might be worth, this is nitpicking Tim. So feel free to tell me to not. It might be worth bumping down the brightness on the orange and the blue just a bit so that that white text is a little bit more legible. And it won't look quite as appealing. But this is definitely an improvement from where it was. So good stuff. Yep. Yep. You can certainly give that a try. Cool. So that's, that's the alert. Hold there. Hold there. Making a screenshot. Thank you. Got it. So alerts. So the next bit was the, where should I pick this page? Yeah. Almost there. Yeah. One question about alerts buttons. Do they have colors adjusted to alert colors or are they independent? The buttons haven't been changed at all. They just used the standard. Okay. So basically it will be darker blue buttons on any warning screen. Yeah. It seems same as in Jenkins. Yeah. There is nothing. There are no but alert button variants at all. Yeah. That's why I was asking because after that I may have missed this change. Yeah. So next bit is this little handle that you use to drag down text areas is now themed and matches the rest of the input colors. The dark link colors changed from the blue primary color to the regular text color. It's mostly was done because the blue primary was very light on the timestamp here. It wasn't very legible. But now it's quite a lot easier to read. I've re-based all the changes against the pipeline stage view pull request. I think I must have made a mistake in the red here but apart from that it looks just looking far better. Yeah. Definitely. It would be great if we could get Wow. And as much as the pipeline stage view looks good at all. But that's a different problem. Looks better than in stock. Thank you. True. Yeah. I mean it's used a lot. Yeah. I know it's used a lot. I mean it's something that you know even though we're going away from it would use a little bit of love I think. Yeah. I think is that a texting contrast? Yeah. So that's it. So not very much in there but just mostly paper cuts just trying to improve it. And the JUnit plugin is still open with the for the JUnit results. So I need some review over there as well. And the I think the e-charts and the Bootstrap API plugin are all merged and released. So e-charts work out of the box and I think so warnings MG looks fine now. So yeah, warnings MG was fixed but that wasn't there was no change to the dark theme plugin for that. And the CloudBeast supports plugins also been fixed as well. This has been a few issues closed recently. The question if you don't mind. What changes were made to the core for better support for theme ability or Word only? Because that sound didn't quite follow. In this release or in general? Well in general for the black theme. In general it was changing from CSS, changing from SAS variables to CSS variables so that we could change them at runtime. I've got an upcoming post for the CDF newsletter which I can share with you in case you're wanting to include any of us in your update. Sure, share it and I will read it at least. Yeah. Yeah so basically it was changing from SAS variables to less and overwrite and adding variables where there wasn't. So some places weren't using it. That was some of the gray that we were discussing earlier. Sorry it was less not CSS variables but LESS variables. So moving from less to CSS and in some places CSS needed changing. Bootstrap needed removing from some places. Right so it's kind of just like cleaning up core but to make it easier to make. Yeah core in plugins. The number of plugins have been changed for it as well. For example in CloudBee support plugin the changes are allowed to get rid of custom JavaScript and other bits which complicate the maintenance and it's not the only plugin where you're already able to optimize how your reward works. Yeah. Do you have anything really quick to share about the tables to this? Yeah really quick to share is that the CSS PR has merged for it. So both the CSS and JavaScript changes have been mainlined. The CSS changes haven't been merged back into it yet so it's conflicted but once that's done the diff should be just jelly files and very small CSS and JS changes. Are you still going to go ahead with the follow-up option? Sorry to be a pin option. Feature toggling out? Yeah or should we just try to power through it for the all in August? I'm not sure if I can be bothered doing the feature toggling approach at the moment. I don't have time but possibly just taking a look at some of the other issues and trying to fix them. Yeah I agree. Better use of the time. Yeah I agree with that. If we can, I say if we can unlock that layout breaking by issue we can just match it at the beginning of August in my opinion. Oh yeah yeah yeah I think the only way that I see the fixer is to adjust to change the layout and then change the layout everywhere and then patch the JavaScript because I was able to get it to not break by removing one layer of nesting but then a lot of JavaScript needs to change and God knows what the impact is. Well if it's what it's needed.  It's not, it doesn't break very many of them. Yeah. Okay so I think we are almost over the time. I think we'll don't call it a meeting. Thank you. If there's anything else anybody wants to say. Okay then thank you everybody for attending. I'll see you all in August in two weeks. Enjoy the beach Tim. Yeah exactly. Bye.


Imagine an influenza epidemic spreads through a population rapidly at a rate that depends on two factors. So when it comes to infectious disease, whether it's the common cold, the common flu, the coronavirus, whatever, when it comes to the spread of disease, there's sort of two factors to determine how quickly this disease will spread. The more people that have the flu, the more rapidly it spreads. So the more people that are infected, the more opportunity there is to spread from those who are infected. But also, the more uninfected people there are, the more rapidly it spreads. So if you have a lot of people who are infected and a lot of people who are not infected, then there is great opportunity for the sick people to spread the disease to those who are not sick. If you have a lot of people who are uninfected but like hardly anyone has the disease, then there's not an opportunity to spread because the vector transmission, there's only a few of those. But on the other hand, if you have like a zombie apocalypse where everyone except for Will Smith is a zombie, right, then there's not a lot of opportunity for the zombie disease to spread anymore because there's only one guy hiding out that can get infected, right? So for massive spread, we need to have a lot of sick people and a lot of healthy people. It's sort of like this combination. And so because of these two factors playing together, the logistic model actually is a very good model to measure growth right here because the logistic model has two horizontal asymptotes built into its formula. And so the graph would look something, something like you see right here where at first it looks like it grows really slowly because you although have tons of healthy people, you have very few sick people. So the opportunity to spread is very small. Then sort of in the middle, you're going to see this like explosion of spread, where there's enough sick people and healthy people that start spreading around. But then eventually the opportunity to spread might die off over time. That is to say there's no more uninfected people. Maybe that is you hit some type of like herd immunity. So the opportunity to spread kind of is done with. And so logistic model is a really, really good way of measuring the spread of a communicable disease here. So let's remind ourselves the formula, right? So the amount, the amount here, let's say a people that currently have the disease is going to look like C over 1 plus, whoops, 1 plus a times e to the negative KT here, where C is the carrying capacity. It's the maximum population. You can't have more people sick than the people who are in the population. And then K is the rate in which it spreads. So that'll depend on the disease, right? Some diseases might be more infectious than others. And so that depends disease to disease to disease. So with this flu strand, we'll see some data to talk about how quickly it spreads in just a second. All right. And then this number A here, this is going to look like the carrying capacity minus the initial population. We'll call that A sub zero divided by A sub zero. So this is our relative elbow room. So dependent on how much room do we have to spread at the very beginning of this exercise? Okay. So let's, let's look at some specific numbers. So for this, for this, this flu strain, right? Let's say that at time equals zero at the start of this thing, there's one person infected. So A naught equals one. And the initial population of just like a small town is 1000. So we might actually think this is like a school. So, you know, we could change this to be like one person has the Corona virus at the local elementary school of 1000 kids or something like that. That's kind of big for an elementary school, maybe like a high school, whatever. So you have one person infected at the beginning of 1000 students total. So let's say that's how things start off with this logistic growth. And so for a specific, for this specific virus, let's say that it spreads at a rate of 60%. So 0.6030. Let's say that it's, that's the growth. And I'm not saying this is for the Corona virus, this is just for a fictitious strain of the flu. So if these were the parameters for our growth, what would the formula be? Well, we'd see that A equals the carrying capacity of 1000.  I should say infected. And so I'm not, I'm not necessarily worried about like those who are currently infected, just those who were infected. So you have 1000 as the total plus A. Well, A here, you're going to take, you're going to take 1000 minus one, which is going to give you 999 over one. So this gives you 999 e to the negative 0.6030 t. So this right here is going to be the function that we use to model the spread of this flu for our community here. And again, we can see there's a school or small town, whatever. We just have some community where these things will kind of spread amongst each other. So we might ask the question. All right. So we have one infected. So we have case zero right here. So how many, how many say infections after 10 days? How long does it take? After 10 days, how many people will be infected? I didn't write down the number. Try that again. After 10 days, there you go. That's a complete sentence now. And so what we need to do is we need to basically compute what is A of 10, right? So what's A of 10? This, this growth rate I should mention was per day attached to the rate always needs to be a time stamp of some kind. So it was growing logistically at 60% per day. So A of 10, we're going to take 1000, which is carrying capacity over one plus 999 the initial elbow room times e to the negative 0.6030 times 10, right? Which times it's something by 10 moves the decimal place by one. So that's pretty easy to do without our calculator. Negative 0. I guess we moved it by one. So we're going to get 6.03 right there. Now after that moment, there's really not much more we can do without using a calculator. So feel free to consult your calculator at that moment, plug the thing in there. And you're going to end up with approximately, approximately 293.85. So, you know, this has got to be a person, right? These were counting people here. So we're right up to the nearest person 294. This is just a model after all. It's not going to be perfect, but we would anticipate that after 10 days, there'll be 294 cases of this flu throughout the school. Right? There's going to be 294 people that were infected by that. So 10 days is not necessarily a long time, right? If we think about the school, they only meet Monday through Friday, right? That's basically in two weeks. We're going to have almost 300 people infected by this strain on the flu virus. Okay. We could ask then, at the rate in which this thing spreads, you know, predict, predict when, you know, we'll reach, predict when, let's say, predict when 90% are infected. Okay. So what we're trying to figure out here is when is 90% of the population going to be infected? Well, since there are 1000 people total, 90% of that is going to be 900. So we have to solve the equation. Solve the equation 900 equals 1000 over 1 plus 999 e to the, I'm just going to say negative t right here. We have to solve for t. And this is the trickiest part of using a logistic function, but at the same time, the process is exactly the same. The arithmetic's never going to be changed. You could actually pay attention to what we're going to do right here. So think of this number on the left as a fraction. We're going to cross multiply and we end up with 900 times 1 plus 999 e to the negative kt is equal to 1000. We divide both sides by 900 and we end up with 1 plus 999 e to the negative kt equals 100. If we subtract 900 from both sides, excuse me, we divided by 900. So it's be 1000 divided by 900. So we end up with 10 ninths right there. Now we're going to subtract, we're just going to subtract one from both sides. So you can take away 9 ninths away from it. And you end up with 999, so many 9s here, e to the negative kt equals 1 ninth, like so. So we're going to divide by 999, 999, 999. Okay, and now we're not multiplying, we're dividing by 999. So that right there is going to give us e to the negative kt is equal to 1 over 9 times 999. For which that's going to be 8991 in the denominator here. Take the natural log of both sides to get rid of the base e. Take the base e, natural log right there, base e. So we end up with negative kt is equal to negative the natural log of 8991. For which then to finish, we need to divide both sides by negative k. And we see that the answer is going to be t equals negative the natural log of 8991 over negative k, right? Which then makes it a double negative. So you get the natural log of 8991 over k, which remember was 0.6030. In which case then we want to estimate this thing and then put that in your calculator. You're going to get about 15.0978. So in about 15 days, right, 15 days, which for our hypothetical school right here, that's three business weeks, right? So about three weeks, you expect 90% from one case to 90% of everyone has the disease after that. So remember that because we're dealing with a virus, we cannot predict with certainty the number of people infected, right? This is just a model. The model only approximates the number of people infected and will not give us the exact or actual values. These are just estimates. But when someone studies infectious disease, like for example, the coronavirus COVID-19, it spread in the year 2020. Admittedly, the models they use are much more sophisticated when we're doing this example. But this can give you an idea of how one can make predictions about case counts and deaths and things like this. That we can use the parameters, we use the statistics and function models to make predictions about how these things are going to go. And sometimes the predictions are very bad. And that's because it's based upon assumptions, right? Our assumption here was that the disease spreads fast when there's a lot of people infected and a lot of people unaffected. That's sort of an assumption. There could be difference assumptions about the disease, which would affect things. And like I said, real-life problems get much more complicated and the assumptions become much more critical. And so bad assumptions can lead to bad models. But the best mathematical models out there, we can see that they have the good data. They have good assumptions and therefore the predictions turned out to be very accurate in the end.


Everybody forced here ripping 2022 three and two baseball first off the line and hobby six bucks makes her number four random team style And again, this is for first off the line boxes in two hobby boxes Good luck everybody. Let's get started not gonna recap this one. This is a super quick break But good luck results link is in chat You can always find the results on the website. So two hobby boxes first You Blake ended up with so many Pokemon yesterday I Had a pitching machine. So I gave him so many coins or some of the tickets all right Frank Thomas White Sox 89 of 99 Philly is rookie huns Krause 3 of 99 and A sultans Babe Ruth Yankees the Sultan of SWAT actually 55 to 150 Colossus of Clout Rookie Quad patch Matt brash one out of three Look at the Mariners patches there some partial logos on a few of them There you go. I'm sweet one there And rookie Jersey Auto Tigers Spencer Torkelson 7 of 49 Good first box One more hobby box. That's actually the first live auto. I've seen of that player personally All right got Braves Greg Maddox 7 of 25 a Prospects Clial Watson 7 of 15 Marlins And full count Cedric Mullins 350 31 of 50 sorry 31 of 50 Orioles rookie jumbo Jersey Aaron Ashby Brewers 83 of 99 and With green ink a day one auto jack lighter one of one Wow a live jack lighter one Rangers whoo who has the Rangers in this? Oh, man, Luke s Probably wasn't too too stoked to get the Rangers that is filthy. Oh my goodness. That's the first live lighter I pulled it's a one-on-one That's awesome That's that is filthy. All right for first off the line boxes gonna be top-to-top that lighter What is it? I don't know. It's a green ink. I don't hate it. I'm just confused by it Mariners rookie Matt brash number 47 of 99 red prospects Nick York Red Sox 6 out of 6 doing very well in the fall league Arizona fall team And wonder full count 41 of 50 raised rookie patch cards, so red patch card wait bogs Three color red socks jumbo swatch one of six sick bogsy That's awesome and a red socks red rookie patch auto jaren diran Four of five Congrats to Alvin M with the Red Sox great box there photo prospects cold winds 79 99 Rangers red pudger Rodriguez one of six Rangers and Perez Royals 45 of 150 full count five-way relics Steve Carlton Cardinals six of six and Nike swoosh laundry tag auto five of five Alec Manoa blue jay sweet one blue jays give me one second It was asked me about something rather break All right cool cool back to the last two boxes here two more photos guys Thanks for filling up the baseball breaks tonight. We've got a couple of basketball and a few football breaks including the Including the week nine. It's was it with 35 bucks or 25 bucks? 30 bucks regular season football makes your guys 2017 immaculate 2018 prism 2021 flawless 2019 and T plus more mosaics select Prism yeah guys you're gonna want to check it out breaking tonight. It's at 20 to go. It's a third of the way full Mets Max Scherzer 88 of 99 red Cleveland Jram one of six Jose Ramirez and a Johnny Mice for the Johnny Mice is Giants right New York Giants This is New York No, not Johnny Manziel Johnny Mice dude What good athletes it is Giants, right? Played way before Yeah, John This is Giants unique. Let me see if I find the checklist. That's orange. I'm assuming that Giants I'll go to the checklist Should be he was with the Giants the longest I think Let's see Mice Base parallel insert so full count is Giants Yes, that is Giants Johnny Mice actually only a Giants in this product.  I'll get a picture of that for sure and Jackson Job nice prospect one of three Four-way patch auto tigers. Oh my god, man. What a break We've been hot enough in any baseball breaks tonight actually.  We got Astros Bregman 85 out of 99 Red Ladolo Reds rookie six of six and Berlander two World Series of Berlander five out of fifty actually had a good start this World Series though future first ballot Berlander Was that two World Series and MVP you saw Young's yeah, that dude's got to be the best picture of the generation I would think I was decorated Patch car Dodger's trade Turner Is that a Dodger? What patch is that game warrant three of six? That's got to be a Nationals patch, right? I guess it could be Has this weird like stitching here. I'm don't know I don't know it's game one though cool and Dodgers and that's sick dual auto plus one signatures Padres Fernando Tate's junior in CJ Abrams four of five What a break good stuff You got more baseball coming up


It was a good game. I enjoyed the game, but congrats to Philadelphia Eagles for not covering but getting a win It was definitely a better game. I think then we expected everyone's thinking I go, okay This is gonna be it's gonna be a disaster But the Texans did what they could in the first half to they're gonna have time tied and then they turn the bowl over a few Times and you know you're screwed like they had to kind of play a perfect second half I feel like to keep this close and have a chance to win Dougie Mills makes a I Didn't expect him to make that pick the CJ DJ one Kind of jumped up in the pocket as he was getting hit and flying it down there through it That was like a panic that like that's not what Dougie Mills is You know that that didn't look like a standard Dougie Mills type play But maybe pep and he went into game thinking hey, we got we got to make the most every you know Hey, we're playing against a very good offense. We got to make the most of it It felt like he forced it that felt like the first like rookie mistake We've ever seen him making his young career here Philadelphia Eagles team is awesome. I enjoy them a lot


We evaluated PocketParker in a couple of different ways. One of the first things that we did is we built a system simulator. And that allowed us to experiment with different parameter settings and with also with different types of parking lots because we wanted to evaluate the effectiveness of our modeling approach when faced with parking lots with different features. So we actually looked at five different types of parking lots. So for example, the fast fill parking lot is a type of lot that suddenly experiences very high arrival rates and so it fills very quickly and then some point later in the day everybody kind of leaves at once and the lot empties rapidly. And this might be associated with a place of work where employees have pretty set hours. On the other hand, this low churn lot over here, this lot actually never fills and there's constant inputs and outputs to that lot. So we suspected that the low churn lot and the high churn lot were going to be the most challenging for our approach. Partly because the low churn lot makes it very difficult to estimate the monitored fraction because we never see a full zero to capacity swing in the capacity of the lot. On the other hand, a lot that never fills like this low churn lot may not be a good candidate for our technique anyway because if it's never full, you'll never have a hard time finding the spot. So we looked at the relationship and this is a graph showing as the monitored fraction increases for the different types of lot, whether it's a high churn lot or a fast fill lot, the accuracy increases. And there's a little bit of weirdness here towards zero because in certain cases zero essentially will overestimate the amount of time the lot is free and that can also, that can improve the accuracy a little bit under certain conditions. But in general what we see is this nice trend where at some point, you know, without having to monitor a really high number of drivers, maybe only 20%, I still get pretty reasonable accuracy. And what this is computed over is we ask the model questions about whether or not the lot has a spot available in it or not at that moment and we compare it with the ground truth maintained by the simulator. So 90% correct predictions means that 90% of the time when we asked the model whether there was a spot available, it gave us the right answer, either that there was not a spot available or if there was not or there was if there was. But, you know, we're systems people and so we are not satisfied with simulation results. We want to look at how things work in the real world. And so we deployed Pocket Parker, we built an app out of it. We experimented with a number of different features of the app in terms of the activity recognition and other things and there's results in the paper describing those. And we deployed this app for 45 days in several parking lots surrounding our building. There were 105 people that eventually used the app at some point during that time and the events that we studied fell into a four-day period where we did some camera instrumentation of the lot. So here are 217 parking events that we recorded during this four-day interval and the reason why we chose four days out of that longer interval was because we actually needed to ground truth the system. So this may be hard to see but this is a picture showing that we added some cameras on the building and then a couple of graduate students looked through, I think these cameras are pictures every minute and they looked through the lots to determine whether or not there were spots available and they did this for thousands of images. So this was a fairly labor intensive process to ground truth the system. And what we found was that the system could actually be fairly accurate. So on the fourth day you can see here that we have a correct prediction rate of about 94%. And in this case we break down the errors in terms of false negative meaning that there was an opportunity to have a parking spot and we missed it because the system claimed that there were no spots in the lot and also what we call waste or false positives and these may be a little bit more problematic because what this will mean is that some will actually go to the lot, look for a spot even if there's not a spot available. But on several days, not sure exactly what happened on day one but on the third three days of the study we had between 81 and 94% accuracy which we think is quite good. The monitor fraction was computed in the same way that we would do normally using swings of the lot and given the number of users that were using the system, the capacity of these lots and the positions of those users in terms of what they do with the school we think that those monitor fractions are pretty reasonable actually. And this work got picked up in a couple of places. This paper was published at Ubicom 2014. MIT Tech Review did a little write up of the project and since then we've actually been contacted repeatedly by companies that have been looking to commercialize this. I think that this idea would actually work very well in practice. I think the biggest trick though, and this is a challenge that many of these types of crowdsourcing systems face is getting up to a higher monitored fraction. So if we could get this in the half of the phones out there in the world then the modeling and the prediction challenges start to go away. And so I think there's actually a really interesting lesson in here for people that are building crowdsourcing systems because there's this sort of virtuous cycle where as you get more users in many cases for a system like this that's relying on crowdsensing the system gets more accurate. But how do you convince people to use a system until it is accurate? And so I think there's interesting challenges for the mobile systems community to look at and also in the IOT spaces. We start to have more sensors out there in the world. How can we somehow give apps a boost so that they can get over that initial curve and how also can we detect which apps are actually going to succeed in certain cases certain approaches may not work even if they're widely deployed. And so it can be hard to tell the difference at the beginning but telling the difference at the beginning is really critical because we want to support the apps that are going to work when they're really deployed and not the ones that won't. So overall we were fairly happy with the performance of Pocket Barker. We think this is a simple system as the accelerometers and the GPS on these smartphones have gotten better and as smartphones have seen wider adoption a system like this should actually become way more practical.


Studies have shown that our cells don't just communicate with each other chemically, the pharmaceutical world, they're based on chemistry. You put a chemical on your body, it gets absorbed and it affects the chemistry of your cells and then they do different things, right? But cells also change the way they work or change the way what they do through electromagnetic signals. And they did lots of studies about that, about how sending an electromagnetic signal to the cells actually change how fast they regenerate or how fast they create energy or how fast they eliminate waste. Isn't that profound? You don't need chemical reactions, you can actually speak in the language of your cells because your cells and your DNA actually communicate to each other through electromagnetic frequency.


Hello people of the internet, my name is Johnny and welcome to Rejected Custom Night 2. I had no clue that this was just going to drop out of nowhere because that is in fact exactly what it did. It just kind of dropped out of nowhere. I saw a trailer for it and then like, it was either the same day or like the very next day, the creator just released it. So here we are with Rejected Custom Night 2 and it appears that we have new characters. Though like, I'll be honest, I don't quite remember the roster for the first game. So we have a whole new group of characters. Well actually I do see some returning faces. Like these Phantoms, the Endoskeletons, Golden Freddy was here. These two withers were here. Pretty sure Funtime, oh yeah, maybe Funtime Freddy. I don't know. Basically we have more characters to choose from. This is Neon Bonnie from freaking FNAF VR. And this is Withered Bonbon from FNAF VR as well. Oh my god, we got the Ad Gang, we've got Egg Baby. Swivel Hands up here, I see you. Frostbear is now a part of the main roster. Originally I think he was part of Prize King's roster but he's on the full roster now. I don't know what we're doing, I'll be honest. 2000, we could try and get 2000. Though we do have new challenges here. Well the challenge is active. To edit it or reset it. You can do custom. Nice, alright so again I'm not entirely sure what we want to do. We could just try and go for our own high score. I think we can do that. Alright so Freddy, Golden Freddy, yeah. So he's easy, we'll put him up to a solid 20. Ooh Endo has a new interesting mechanic. He will appear in the office randomly with dramatic music playing.   I randomly appear in the office, put on the mask, yep yep yep. I think we'll start off with maybe 1000 points and then we'll go from there. Alright that's the same as the first game when her face appears on the arcade machine. You want to click that. Also, 50-20 mode. I did try that for a little bit, that was just to test the recording of the game and see how well the game works. Because if you remember last time for the first game, it crashed quite a bit. But 50-20 mode thankfully did not crash my computer just yet. So let's hope this game is a lot more stable. I'm pretty sure Pan stands just like the original Trash and the Gang. Ooh sound sensitive, I don't know about that. When you hear him commit bonbon, go get him, close the left door, get ready for surprise. Alright yeah so that's fine. We'll start off with these bros. Actually what do we need for 2000? We should get the first office in this video alright. We're going to start off with these guys. This all looks the same. Yep everything looks the same. Yeah okay, so it seems like everything is the same. I think they changed flashlight to Z. I think in the first game it might have been, oh there's Vanny. Alright so I think this first night should be Y, create a Y. This first night should be a little bit chill. Why is Springtrap's decapitated head right there? That is kind of creepy. But yeah I do like this office. I do really really like this office. It's much better than just much better. No. Ooh they attack fast. Alright. Alright so that's kind of weird. FunTime 40 doesn't, like when you hear him speak you can close the door and that'll get rid of bonbon immediately. You don't have to wait for his dialogue to end. That is interesting because that's how it is in CIS location customer. You have to wait for his dialogue to end and then you close the door. That's interesting. But back to what I was saying earlier. I do like this office much more than the previous games. One, because that one was just ultimate customer in office with a little bit of Photoshop editing here and there. I'll be honest you know creator. Ooh I see Phantom Chica. I don't mean to roast you there. I'm sorry but I like this office a lot better. This looks amazing. I'll say that. Alright so, ooh. I don't know if I want to go into the cameras. Actually I gotta remember who I have on. I've got some masked people. The Phantom Chica. FunTime Freddy of course. And who else? God. Yeah right there. And I open it back up and I'm fine. Nice. Okay so, FunTime Freddy not a problem. It's already 2am. It looks like it's going off of the same... Do you mind? FunTime Freddy? It looks like it's going off of the same time cycle as Ultimate Custom Night. The last rejected Custom Night. I'm pretty sure has its own time pattern. And it seems like Pan stand comes up every time you close the monitor. Though I'm not sure if that's actually his mechanic. He might just show up randomly and I've just gotten lucky. Lucky. But yeah. I mean, yeah. It looks like every time you flip down... Yeah. Every time you flip down the monitor... Oh man!  I was talking about Pan stand. Golden Freddy. You didn't have to sneak up on me like that. I might try and spruce things up a bit. When he tells you a story toning on the heater is the only way to stop him. Alright. We're trying to go for 2,000 right off the bat. So, let's look through a few people. Spawn and block your screen for some time. That's perfectly fine. I'm trying to remember who else was here. Oh wait, where's Dark Springtrap? Because he was pretty easy. I think maybe Dark Springtrap will spin. We'll move from the roster. Button. Play some on the screen and click it. Or press Z to mute his call if you don't want your noise. Oh! You can press Z to mute the call? Wait, really? That will be placed somewhere on screen and click it. Or Z. Yeah, I think you just press Z was the thing. My mic's blocking his icon. So I think I just press Z to mute the phone call. That's a little weird because Z is also the flashlight that can mess you up in a lot of cases. Especially if there's some sort of like Nightmare Balloon Boy character in this game. But, um, yeah. Alright, so the final two people I have on are Phantom Foxy, who will sometimes appear in your office after closing the monitor. Flash your light on him to avoid his jump scare. That's pretty easy. And then we also have an adventure of Freddy. He's just like Old Man Consequences. So this is 2K. We should be able to do it. Hopefully. Alright, so Z is getting on a phoney. So, yeah. Okay, here we are. So Candy Canada's right there. And I will say, he's looking kind of depresso-expresso. He's very... He's very... What's the word I'm looking for? New War? I don't think that's right. But yeah, we'll go with New War. So, Phone Guy, who probably should change that button. Creator, if you end up watching this. I will tell you a story. I forget what I do. A heater. A heater.  Okay. Probably should have looked at that. Uh, C. Yeah, very easy. Old Man Consequences style. Um, yeah. Should probably change the mute call button to something other than Z. Just my recommendation, because Z is also the flashlight. And if you have someone like Balloon Boy, I don't know if you have someone like that. Balloon Boy. But if you do, then I would highly suggest changing that button. But if you don't, then maybe it's alright. I'm not entirely sure. Alright, so minute past 1 am. One minute mark right now. And I'm chica just in time for that one minute mark. Uh, catch that again. Pretty chill night. I'll be honest. Uh, pretty chill night. I don't think people start attacking until I flip up the monitor. I don't think I need to worry about my heat either. It's at 120. Uh, and once my temperature does go below 50%, I'm sorry, not my temperature, my power, once it goes below 50%, I will get the adventure, no, adventure endo? I can't remember if there was adventure endo or just regular endo. It might have been the adventure version. But I will get those guys covering my screen just for a little bit. Okay, so, Hito is number three. I just wanted to, uh, make sure on that, because that is also the same button as regular custom night. I think, fricking me, I literally just played it today and I cannot remember. Um, which by the way guys, if you did not see my speed run of, well, speed run of ultimate custom night, it wasn't really a speed run of ultimate custom night. It was more just a speed run of a category in custom night. Uh, go away, Funtime Freddy. Basically, uh, let me tell you a story, right? Why would, waiting, let me tell you a story. Just like, uh, Candy Cadet, let me tell you a story. Get out of here. So, I originally, for an April Fool's video, was going to do me speed running FNAF, and then I thought, no, you can't actually speed run FNAF. Um, that pearl did not look like it was on the plus sign, but, all on its slide. Yeah, originally I was like, well, technically, the whole point of it being an April Fool's joke, was the fact that you can't actually speed run FNAF because it has a set timer in the game.  So, I actually looked it up to see if anyone had speed run. Speed run? That doesn't sound right. Okay, no, no phantom foxy. Yeah, I looked it up to see if anyone had done speed runs on FNAF, and it turns out there is some speed runs out there on FNAF. In fact, on this website called speedrun.com, there is a whole series of speed runs dedicated to the FNAF series, and all the way up to Freddy and Space 2. Every single game out there, including Ultimate Custom Night, Help Wanted, FNAF World, all the games. So, I thought, hey, why don't I damble? Hold on. Why don't I dip my toes into the speed running, into the wondrous world of speed running, and give it a shot? And so I did. I picked out a challenge. Excuse me, Mark.  No! Final few seconds, hopefully we can do it. Anyways, yeah, so I picked a challenge that I wanted to do. Oh, I understand. You have to hit it on the plus sign. It will allow you to hit it. Sorry, I didn't think that he went away. Anyways, it will allow you to hit it, but you have to hit it on the plus sign. Back to my story. I picked out a challenge. It was, how fast can you get Fredbear and Ultimate Custom Night? I did that. I did a few attempts at that. I got 8.6 seconds. And once the people at speedrun.com will review that footage, I will be number-throated on that leaderboard. But here's the night done. Fredbear was about to send Bonbon after me as well. How many times have we danced to this specific theme tune across so many different games? Oh, we actually got another 100 because... Do we have it in the bear? That's a thumbnail. Now that's a thumbnail right there. That's a thumbnail. Now that's a thumbnail right there. Ah. Brick. Brick. Bunny now? Can I see the bunny? No. Ah, shucks. Uh, who did they add by the way? Um, I don't know if it'll let me see, no. No, they took them off. Damn. Guess I'll never know who they added. Anyways, as I was saying, just for a quick little second here, I hopefully you guys enjoyed that speedrun video. I know it's a little bit different. As of the recording of this video, it's gotten pretty good reaction to it, and I do plan on doing a bit more speedruns in the future. They're not going to count as actual videos, which is why technically you're getting two videos today. The speedrun and also this proper video. So they're not going to count as normal videos. I'm just going to throw them out there just because I think it's enjoyable. I've never...  And once I found out that there was a finesse speedrun community, I was like, hey, I want to at least give this a try. So hopefully, you guys don't mind that I'm doing this. It doesn't affect videos, so hopefully it doesn't offend you guys too much. Anyways, let's check out this new office. Um, 5K will probably be another video. We can attempt maybe 3K if we want to give it a shot. So let me have a quick look through and add or sometimes cover your screen plus enter. Okay, that's perfectly fine. Sometimes appear in your office, go to the prize counter. Ooh. I'm good. I'm good. Uh, she'll stay in the restroom camera. No, I don't really want to have any camera characters. Um, that's kind of what I did with the first game as well. One of them will sometimes appear on the forward desk in your office after closing the monitor. Flashlight to avoid the jump scare. Alright, seems pretty simple. What about you guys? Will appear in your office purchase the no, no, no, no, no, no. Alright, so, monochrome toys will appear in the office. If a Fredo appears, don't click on it. Seems pretty self-explanatory. Don't let your mouse link over them for too long. Pretty good. Um, stand in the gaming room. Nope, nope, nope. Be behind you more sound. Make him angry. We'll try out you. Okay, so here is 3K. Let's give it a shot. Yeah. Sure. I don't know how well this is going to go, but we're going for it. Alright, load in game. Thank you. Oh, this is interesting. Where is...  Ooh, hello. Where's, uh, Security Puppet? Now I will tell you a story. A story about the kind man. I want to know what Security Puppet looks like. Boom. Just so I know, like, what surface area I'm walking with, you know? Ooh. Oh, it literally covers the entire screen. The ad literally covers the entire screen.   Did I miss that? We're going to find out? Yeah, I did. Yep. Monochrome toe, toy? Is there a hot key to the mask? Because I feel like... Mmm. Wow, that's a pretty delayed mask. Like, look at that. A story about the kind man. I mean, I guess it could be worse, but like... Wow. Like, I feel like I was... Did I miss that? Damn. That's actually a little bit tricky. That you can click it anytime, you know? This mask, I don't know. I feel like it needs a bit more walk, but then again, maybe if there's a hot key for it that I don't know about, boom. Okay, that showed up for, like, literally one-tenth of a second, but alright. I will tell you a story. A story about the kind man.  Fun time, buddy. Just affecting close and only. I'm just not used to that, so that is kind of my fault, but, you know, whatever. I am legitimately enjoying this game. It is a huge step up from the, from the last one. Also, that ad man covers the entire screen.  That's not really a complaint. I'm just, just... Wow. Then again, the ultimate custom I wanted to fill up the entire screen. Maybe it's just the darkness. Maybe it's just the darkness behind the ad. Sorry, I had to concentrate there. I couldn't see that. All right. So, yeah. I really, really am enjoying this. It is a huge, it is a huge step up from the last game. And I'm just, I'm enjoying this a whole lot. I wonder if there's more sequence in this game. Autochrome toy. Hey, hey, hey. Sorry.  Oh, got it.  I want him to come back. Anyways. Yeah. Oh, hey. I got you. Correction. I got you, Phantom Foxy, so I don't know what you're complaining about. You. Nice. 74%. 4AM. I wish Ultimate Custom I had the hard key for it. Bunk for muting phone guy. That would make the game so much easier than you wouldn't have to worry about Nightmarion so much. This office is definitely something. I'll tell you that. Definitely something. I do have. Wow. That is a big security puppet. I do have a complaint about this office though. Developer, if you do happen to watch this video, pay extra close attention.  Pay extra close attention because this is really important and I feel like you definitely need to change this in the next patch for the game. There's not enough Toy Freddy's. There was nowhere near enough Toy Freddy's in this office. You know? It's just I feel like this is the Toy Freddy themed office. I feel like there should be a bit more because you know it's just a little bit here, a little bit there, a little bit down there. It's just, I feel like there should be a little bit more Toy Freddy, you know?  New cutscene? Wow. Great, how many times I mentioned this last time but how many times have we danced to that song? Good question. Hey, a dedicated fan out there go back and count all the times we have danced to that song. All right, so no new office, no new cutscene for 3K, but it is definitely better than 2K. That is how it works.  Oh, it's green! 20 seconds! Can we take 20 seconds?  I don't know who I died from. Maybe a secret character. Maybe there's a secret roster I don't know about. Great. Great. Great. Next attempt, here we go. Right, so I think thanks. Thanks. Thanks. Thanks. Thanks. Dude, I'm booping on your snoot! Maybe you want your hand back! Nope. Huh, interesting. What is... 15 seconds! What does... What do you want? Sometimes, see it to touch bonbon on your desk. When you see it, you have to find a way bonbon on someone in the office. Oh, I need to click the button on his torso. Wait, what? Oh, that's just easy. Why do I have to look for the arm when I can just look for with a bonbon themselves? Anyways, alright. Last try. I know I said 30 seconds, but... Boom. Thanks, man. Woo! Hey, what? Anchors. Anchors. Someone calling me, but... Chipper, you have gotten a lot scarier than I remember. What do you do? Two slots will sometimes be on the top left corner. Press X to stop the... See, the slots match. You can... Oh, wow. That is actually a really difficult mechanic. There better not be more than like two possibilities, you know, life and death, because... Wow, that's a really fuckin' difficult thing. Boom. Got that. I don't know what I do with... Excuse you, man. Do I have to click? I... Click you. Oh, Chica. Click. Click. That actually got me. All right. What do I do? Like, slowly materialize and let's hold the camera. Oh. Disappear again when it's low. If you materialize all the way, it jumps here. Oh. My temperature is too high. I thought I turned the fan off. All right. Let's try. Let's try. Let's try. Let's try. Let's try. Seriously. Dude. Oh, I...  I turned the fan off. I was like, I turned the fan off while I get killed. Yeah, yeah, yeah. Woo! Dude.  What do I have to do with him again? X and C. I don't like how some of the things are the same things. Some of the buttons are the same buttons, you know? Anyways, final try. I promise. Like I said last time, final try. Uh, no, keep that on. Okay, bye. Now I will tell you a story. A story about a current man. Oh, hit it. Hit it. Hit it. Yeah, no, that was the final try because we have not been getting any higher time. So, thanks for watching this episode on rejected customer 2. And I'll see you all on the flip side. Goodbye.


Evaluation of the written draft by the teacher, by the students themselves, and then post-writing is an important element of planning a writing course. In this regard, who can evaluate the course? Of course teachers, but mostly you might agree with me in your own teaching context if you are teaching in private schools or if you are teaching in government schools. Most of our teachers complain that they don't have time, they lack time to integrate planning, drafting, feedback, editing as a coherent whole in a writing course. So, but there is a vital link as you might have realized throughout these modules, some of the previous modules between revising, feedback, editing, and this vital link can be lost if we don't evaluate what the students have written. So, it's our job as language teachers to use explicit criteria and tell this criteria to the students. The criteria against which their work will be awarded, their work will be graded in other words. Evaluation should focus on the interpretation of the task, to what extent the students have engaged with the task, to what extent they have answered the questions, and to what extent their writing reflects the sense of audience being addressed, and to what extent the materials used are relevant, and to what extent the ideas and their development and organization is coherent and appropriately managed. And what about the format, grammar, structure, spelling, punctuation, capillary clarity. So, these areas of course are broad areas and which cannot be analyzed in one session. We can divide our session and allocate one session to grammar, the other session to spelling, the other session to punctuation, the other period to vocabulary, and this is how this can be divided into weeks, into months, and into semesters. And the purpose is to actually make the judgment criteria or the evaluation criteria in other words, clear and explicit to the students. And of course, we as language teachers, in terms of evaluating and post-writing, we can make the use of numerical grade in terms of, for example, a grade or a plus b plus or b or c plus or c, or the use of marks as well like 80, the range of 90 from 100 to 90 to 80 to 70 to 60. So, this is the numerical figure which we can give. Post-writing means or refers what the students will do with their writing. And I would suggest if we want to own their writing, if we want to acknowledge their writing, we need to give this message to the students. Look, it's important, it will be published. And it will be published in different ways. For example, pasting it on the classroom walls, on the notice board, or you can ask the students, share their writing with other colleagues, with other peers in the classroom, and reading them aloud. So, post-writing is all about transforming texts for stage or displaying them on notice boards. So, the main actually purpose is to recognize what the students write is important, and it's worthwhile, it's not wasted. So, what it will do, although it looks a tiny activity, a very commonplace activity, but it has very rich fruits to offer. For example, it will not only enhance the motivation, but also give a sense of purpose to the students. So, as language teachers, we need to offer a criteria against which students' writing will be analyzed, evaluated, assessed, and graded. And then empower students make them realize what their writing is important, it's not wasted. And it has a worth, it has a value, and it will be displayed in the form of different portfolios, different sort of charts or posters in the classroom, on the notice boards, and in different formats.