to the third and the last day of the workshop. And we are happy to have Lukas Miller and he will tell us about anomalies, high geometry, and functorial field series. One second, and thanks for the introduction. Thanks to the organizers for giving me the opportunity to talk about my work. So I'm going to talk about anomalies and then I try to talk a bit about the corresponding metamatics and study it and a lot of these things have already appeared in the previous talks with the secretary, where it was mostly about anomalies, theories, and actually true to a certain kind of geometry that I expected. Actually, for example, which were most of my own work actually guys and then this part of the study they really simply found and all these things are basically kids. But I will start with some physical integration and anything which is my own work in this part of the space from the workshop. And so yesterday we have seen and then we have seen anomalies in the past secret description. And in my work, I will focus on the California description. So how can you see the mental level of space spaces and all spaces? So I will start with some physical integration. So it's like I have a drawing along here to keep the space, not if there's time to keep the space. And then to set up our front view theory, I will usually need some elementary structures on a map and to be concrete, I will also show here I will show all the general stories like on the right, I will talk about the kind where I'm on and your case, please. So we have a total description. This happens if the dimension of n has a part, so it's more secret to one or one to the two. And then it appears to be as very long to discuss the method, which I was just going to show you in a moment. On the other hand, I guess here, this is a connection on the principle of lambda for the key, the key. And furthermore, I'm patient of the space brush. Because is your microphone on? It's supposed to be on. How's the sound? Okay. So is it better now? Someone should respond. Is there a microphone on? Right. Well, we have to see someone.  We have to do some testing. Is it better? Can you try? I can turn this off. This is supposed to be muted. And is it better now? It's not configured testing, but there are problems. Are we using the same setup? Okay. I don't know. I mean, if you can hear me now, I will just continue. People seem to hear you through that microphone. Okay. Sorry about that. So where was I? Yeah. This is somehow the geometric background structure we need to define a carriage theory on a time slice. And over here, we just have a manifold M and then some type of geometric structure which lives in the space F of M. And then what we get, what we have first, we have the one particle, this one has some H. And here, this H is going to be given by the square integral sections of the spinobundle and sort with the vector bundle which is induced from the principle bundle of this representation rule. So these are sections, square integral sections of this bundle. And then this is like the one particle here by space. And then what one wants to do is second quantization. And for this one needs to pick a polarization of the red space. So decomposition into positive and negative. So H plus and H minus. And then one can define the second quantization space on M as the exterior algebra which just can roll with the exterior algebra on H minus. And here, so if the, let's assume for the moment that there's no zero modes from the geocorporator, then we just take S H plus or the space span by eigenvectors with positive eigenvalues and H minus being the space span with eigenvalues. And if there are zero modes, you can for the moment you can just put them into H plus, point to H minus and the resulting torque space is going to be isomorphic, but non-canonical. But since we are just at one point in F, this is not such a big deal. The problem appears now if we study the following, we try to understand what happens if we vary these three but spaces over as F of M. So we want to understand the dependence. And this is the place where the unnormally happens. So it's like somehow that we cannot define this fork space globally or continuously in this space based on the space of years. So what we can try to do is we can have a F of M with some patches, Ui and Uj, and then we hope that we can pick some polarizations over these patches so that we can smoothly define these three but spaces. So then we will get a Zi of M defined on this open patch and we get a Zj, which is defined over the other open patch here. And as an example, what one can do with the tiger gate series. So for example, if I have my patch and then the spectrum of the DRock operator does something like this. I could, like for example, in the I patch, I could say this is the I and then this bit here would be J. So and then I just take H plus everything above this element, which is not in the spectrum and here I take everything below the element which is not in the spectrum. But maybe, I mean, there's no reason why I can do this consistently over all of F of M. I mean, there's a reasonable hope to be able to do this locally, but globally there might be no reason for this to work. And this is exactly where the anomaly comes from. So it's like the fact that we are not able to pick these polarizations consistently. So now let's assume that I can at least relate the polarizations as something kind of dimension. So I assume H, J, H, I plus some finite dimension of vector space. And I mean, this is what happens here, right? The finite dimension of vector space are just all modes between these two valence and then H minus I will be H minus J plus some vector space. And now I can consider the form spaces. And from the definition, we see more or less directly that this space is not equal to the other one in this case, but we have a canonical isomorphism which goes to the IM, if it depends on the determinant of W of J. The determinant is just a top exterior problem. And then this has happened like over UIJ and if UIJ is noncontractable, this might define a non-trivial line bundle. But we could even make it, I mean, if we assume that we have a good cover, this we could trivialize this, but the thing is that this trivialization is non-canonical. This relate on again, this is where the problem lies somewhere. And then here on the Kyrie-Gates theory side, I mean, WIJ is just the eigenspaces with eigenvalues between like theta and I and J. And now we can ask what happens on triplet intersections. So if I go, look at the triplet intersection UIJ case, what I will find is that, I mean, I can start with the I, this is isomorphic to the J, can do the determinant of WIJ. I can also directly go to the K, and I need to handle the determinant of WIK. And here I can now go to the J, a DK, and then I handle with two determinants. And I turn out that there's a canonical map here, which is also from one terminal with some psi IJK. This is a map from the determinant IJ, handle with JK, determinant for WIK. This is the psi IJ as well as this. And now somehow here you can just pay this out, but this will give you a similar structure. And now this is somehow really where the anomaly happens, is that we cannot trivialize these things and these things at the same time. So there's somehow no globally well-defined Hilbert space on FM in general, but it's only defined locally.  So let me now try to motivate the corresponding mathematical structures. So we see what I really want to highlight for the moment these two bits. And I want to convince you that you think of these things as line bundles, but where the coefficients are not complex numbers, but actually vector spaces. So you see here, like I have at the intersection of two things I give a vector bundle. For a line bundle here, I would give, if I have a line bundle, I would give some transition function from UIJ to C4. But here I give a vector bundle, which is a smooth space, which is a map from UIJ to vector spaces, but the smooth family of vector spaces. And then down here, I have the usual co-cycle condition, Fij, Fjk, this is Fik. But since these are vector bundles, there's a notion of map between them. So I don't want to have the co-cycle condition as an equality, but I want to have it as an isomorphism. So I have an isomorphism here, which implements the co-cycle condition and then there's a compatibility condition on quadruple overlaps, which I'm not going to mention. I'm not going to spell out, but you can figure it out by just looking at the example, opening any textbook. And so this structure motivated it like a category for a line bundle, or these things are also known as jobs. So this is the structure we'll get. So we have the space of fields. Move to the other side. Yeah, so we have the space of fields, S of M, and then we have this higher geometric structure of a job sitting over it. And now if you look what this lead does, this behaves like a section because it defines like something on all the independent patches, which then transforms, if I go from one patch to the other one by the transition functions, now just we implement these things by the most items again. So we have our job sitting over S of M and then we have behavior space. This may define as a section of this job. And the non-periodity of the job is similar to the presence of an unknown. Okay, let me mention what happens in the Kyber case. So we take now only the only very, so we restrict the space to the space of connections on a fixed bundle. This is an affine space over one forms on M with values in G. And then I have a job over here and this thing is called the index job. So this has been studied by Kari Mikkelson and Rory in connection to anomalies and the Fibar trace is again a section here. And now the anomaly is the non-periodity of the job but one really needs to be careful because this is a contractable space. So you probably know that our line bond is over contractable space at trivial but the same is true for jobs. So the job as it's own is trivial and the anomaly really comes from the fact that there's more structure, right? There's the group of gauge transformations acting here. And this job, the job here becomes equally variant with respect to this action and really the anomaly is a non-periodity of the equally I want. And this is the second point I want to make in this introduction is somehow. These things are higher geometric objects but it's important to also treat this thing as a higher geometric object which has internal symmetries. So here you see if it's that difficult just treat it as a space and do not consider the gauge transformations it's really there's no anomaly. And the anomaly comes from the non-equivariance from the non-equivariance or from this thing being not equivariant each other. Okay. And then there's another technical problem one might worry about is that these things are infinite dimension but both I mean this space doesn't generate infinite dimension in this one as well. So now I'm the next bitch I want to talk about is just like a mathematical framework somehow which allows us to make these objects precise and talk about them and study them. This is, both I know the name higher geometry which I will just talk to of my talk. So let me start with a definition of a generalized space space. It's a pre-sheath F on the side of many folds which takes values in infinity group for it or simplification sets or topological spaces. And this is similar to what we have seen and then treats talk as a model in the geometric structure we put on a border category. But for the moment here we allow more than just look at if you move and we also know all maps of the truth with many folds and then we also denote by H as a category of generalized spaces. Let me give you some examples. So how does this framework come on quotes most of geometry you probably know. The first example has to fix a manifold X. So this is a manifold that can even be a fishy manifold or some other infinite dimension type of manifold. And then we can form a generalized space it just goes from many folds up to these two sets but this sits in infinity group. So these are just the group which has no higher morphisms and what does this do? It just sends a manifold M to the collection of C infinity so smooth functions from M into X. And this summer should be the general picture one has in mind for these objects. So instead of describing the space F what we really describe is what it means to have a smooth family of points and F parameterized by manifold M. And this is somehow a convenient way of modeling all types of higher spaces. Let me also give you two more examples which have some higher structures which are relevant to what is going to come. So for the first one is BG with a connection this sends a manifold M to the group void of G bundled on M with connection. And then the other example is related to the fact that we want to also study the geometric structure on a fixed manifold. So I fix some manifold X and then I want to have like a space which describes certain geometric structures on X and usually you do that by a parameterized geometric structures on fiber one with typical fiber X. Let me just use an example which are matrix on a fixed X so they send M to set a fiber wise matrix on M cross X of the projection to X. I should also say putting in many folds here is not, it's a bit too big because in general these things satisfy descent so they are already determined by knowing them on the contractivist space so one could also replace this with the category of Cartesian spaces also. So you're using a sheet condition in general, right? I did, I said yeah, it's a sheet. This should be a sheet, yeah. So it satisfies the version of descent and this allows you to work with sheets on Cartesian spaces which is a bit smaller but at some point these many folds they really have to go to deputation so we will stick to it for the moment because we are not going to do anything too technical anyways. So now. Lukas? Yeah, yeah. Would you need the bundles M times X to be non-trivial if you want to have a sheaf? I don't think so. I'm not 100% sure, I was confused about that when I was preparing the talk as well but I think it's, I mean these are just, I mean what I want to, I just something like that's from M into metric on G, metric on X but I want to write this and I could put like some many folds and fill it in as a many-fold structure on this and then I could use an assumption to rewrite it as much like this. And the projection should be to M or to X? Oh, the projection should be to X, right? Yeah. So I wasn't, I'm not 100% sure but I thought, I think this is okay because somehow I do not allow our morphisms of X so nothing happens like, if I would also somehow include a few morphisms of X then I would need bundles because then I can like locally glue using this different morphisms of X and they should not. Okay, okay, thank you. I mean if someone disagrees, they should let me know. Okay, so now I'm like, I don't want to call this a definition but now somehow higher geometry is just you do ordinary geometry but you replace many folds with general spaces but we can do, we define what a smooth higher loop is. So smooth higher loop is an element in H. What I should say is the loop object in an H but I'm just going to give you an informal definition so it's an object in here which comes with a multiplication because from G plus G to D and it has a unit which is a map from the constant G to D and these things now need to satisfy so there's a lot of coherence data which encodes that this thing is associative and this is a unit and furthermore this needs, this multiplication needs to be in multiple which way you can more or less use the same definitions one uses usually and then I'm not going to give you all the details because in H it's also quite complicated but quite often the things we have actually factors who sense or the factors who group or it's an in there it's easier to say what these objects are. Let me give you two examples. The first one is just I take a lead loop and then I take G underline so I take consider this as a smooth as a generalized space and this is a smooth group. So this is one example and then the second example which is relevant to define jobs I call line but you could also call this P C cross and this then the manifold M to the two point of line bundled on M and here I only take a vertebrate loop for instance. So it's to a space M to a manifold M it assigns a scoop world of line bundles and the multiplication in this case is given by taking the terms of product of line bundles and all line bundles I'm just a bit of respect to this operation. Okay. And now there's, now we have groups and now there's a similar definition to the usuricate of a principle bundle. So the definition is due to Nikolaus, Stevenson and Schweigel and I'm again, I'm not going to give you the details or any precise definitions but it's similar to what you would expect. So it's a generalized space which comes in with a map down to your original space which has an action of G such that the quotient of the principle bundle by this action is X and then the job X and H line. So this is like a really bad, okay, let me write B to cross bundle and you see if you know I mentioned something like a co-cycle description for this then on double intersections you will actually assign line bundles and on triple intersections you will need to assign either more for something. So this is somehow a good mathematical framework to make the things we had we have seen before pre-sets and also this X as I alluded to here can be infinite dimension but this is not a big problem for the framework to have at least on a theoretical level, okay? And then we do one example. So I can look, I take a manifold X which has an action of a legal and I can define this quotient straight and this, so I'm only going to say to you what it does locally. So if I evaluate this on a patch I don't know if it comes in contact with it or something local, I get the infinity function from you interact, acted on with the infinity function of you into G and then the global behavior can be constructed by gluing these things together just using the descent construction. If you do this on a global manifold and this would not be a sheet but you can chiefly find this description and then let me put this here because I have a job on this space then this is equivalent to having a G equilibrium job on X. And this is exactly what we have seen in the beginning. If you had this job at the space here which actually is the quotient stack so I have a space that has an action of the group and then if I want to have a job on this as a higher geometric object I actually need to give an equilibrium job on here and this is exactly what happened in that one. Now I will switch topics a bit and move towards factorial field theories and the goal is somehow to at least sketch how this modern description of anomalies in terms of factorial field theories actually matches this older description and what type of mathematical productions one expects for these things to match up and should also say there are a lot of things which are open in my opinion. So this is three and actually three and the new thing compared to some of the previous talks is that my field theories will actually be smoothed. So we define field theories as the final goal from a modern category equipped with geometric structures. Now this F is slightly different to the F's over here. It only needs to be defined on families of n dimensional manifolds and local difium offerings between them. So it does not need to be defined on all manifolds. So for example, n is two, one might want to consider spinar structures which are double covers of SO2 which do not exist in another dimension. So this would then be something which is really specific for dimension two. But otherwise this F was really similar to what we have seen before and also this appeared yesterday. Then it's a factor from this vector spaces. But now the new thing is that this is actually the symmetric one order. That's what we had before but it's also supposed to be smooth. Metric one order. And then I mean, depending on what we want, this is really a smooth infinity category but this moves one category so we can work with one category. And let me explain what this word smooth means here. So we just applied the same strategy as we did in the case of generalized spaces to make something smooth. We just consider it as a chief on manifold of. So the smooth category is a factor from the opposite of manifold two categories. Automatic one order categories or symmetric one order category. And then what do I mean by the smooth category of vector spaces? This is just sense to the category of vector boundaries on M plus the vector on M is sort of a smooth family of vector spaces. And the definition of this border smooth border category is a bit more complicated. I should also, by the way, mention some names. So this idea of smooth field series goes back to Stoltz and Heichner. But then recently there have been besides definitions in the framework of smooth infinity and categories by gradient path law and also a bit in the case of smooth two categories by Ludovic and Stoltz. But I'm not going to give you a precise definition. I'm just going to give you a step. So I need to define all these categories here. Evaluate on a manifold. You allow in the dimension of vector spaces. Let me not mention that there. I thought that's where you should, but then you should also worry about topology. So I would like, like it depends on what you want to do. But generally you should, yeah. And maybe you also don't want to have like vector space. You don't want to have something like a sheet of vector space. Depends on the example you have on mind. Then you need to worry about what type of topology you have at space. So, but that's also not, yeah. I would like to be agnostic about that. But let me sketch this category to the object. I mean, so this is just a parametrized version of the ordinary board, isn't it? That's what you've seen before. An object is a fiber bundle of N minus one dimensional manifold or maybe germs of N minus one dimensional manifold and N dimensional manifold which are equipped with fiber-wise F structures. So this just means that every fiber has something in it. So for example, it's something like the fiber-wise metrics we had been seeing before, but fiber-wise orientations and then the morphisms are given by co-borderance of these things. So I have a vector bundle of, I have a fiber bundle of manifold, I have a different fiber bundle of N minus one dimensional manifold and then I have a fiber bundle of co-borderance over. Over N and this is equipped with a geometric structure. So this is one type and then they are, which one might need to add by hand or in the framework. They just want to highlight them. It's basically the automorphisms of the symmetries of Y. So for example, if F contains the bundle, then these automorphisms would contain fiber-wise gauge transformation. So these are automorphisms in the photogenic ethical. Where's the other area? Ah, okay, thanks. Now smooth field theory is such a funcal, but what does it explicitly, like if I have such a Z and I evaluate it on a type of smooth framework of co-borderance over S, what does it give me? Is first of all, does it give me two vector bundles over S and then it will give me a linear map between them. So it will give me a fiber-wise linear map between them, which corresponds to the co-borderance. Okay, now an example of which is actually a theory to David Evans' part and path map and then more modern version or more modern proof is due to Ludwig and Stoffel. They also, their formulations are slightly different and that looks a bit different. But the theory is that if I look at this one-dimensional border of the particle with, but here the structure are mapped into a target space X, then smooth field theory is like this. I prefer them to vector bundles of this connection. I find out that they need to be finite dimensions. And how does this work? So an object in here is a map from a point to X which will be mapped to the side over X or more generally an object in here is like a family of points and X which will be mapped to the full vector bundle. And then a morphism in here as a co-border, so it's like something like this, which comes with a map to X. And this will be mapped to the parallel structure in the X to the Y. And these are all of these sweet theories. Now, I want to explain how I normally describe this. And we already have seen that yesterday's by using a relative series of boundary theories but to capture the Hamiltonian part I mentioned before, I need to extend once. So I will just define extended field series by putting n minus two here and the two back there. Let me explain what the smooth category of two vector spaces is. So two vector, and I just tell you what it does locally on like a contract in this space. And then you can again extend it using a sheaf property. This is now two categories. So this thing will be a smooth two category. The borders in category will also be a smooth two category where we just allow now, updates are n minus two dimensional vector by a fiber bond with morphisms are the same and two morphisms are like fiber bonded of the fiber bond of cobalt in between cobalt. I mean, if I think explicitly, it's not that easy. This is like a picture I want to have in mind. In this category locally, I guess there's objects algebra bundles. These are bundles of algebras on you. And then the morphisms are binot two bundles and the two morphisms are just fiber-wise linear maps of bi-multi-bundles. This is a local description and then the global description happens by gluing the algebra bundles together and bi-multi-bundles. And this has recently been studied by Crystal, Ludwig and Weidoff, so I should mention that as well. And then such a smooth theory once extended with an assignment algebra bundle, yeah. So these things then on the level of object, these things with the algebra bundles, these things will become binot two bundles.  So the interpretation here that they are actually described by field series. The anomaly itself is a field series, but it's inverted, so it lands like in the two line bundles that are the morphisms between them. And then if I want to describe and the anomaly theory with anomalies, the relative field theory, and they can be described by either relative field series or twisted field series. For this, I take this A and I restrict it to its value of N minus one and minus two and I allow that the things which are symmetries of the geometry structure. And I think yesterday, this was called a categorified field series or something like that. And then I have something here, two line bundles, and I have a trivial one and I have the restriction of it. So I can restrict my area to this category and then a relative field theory is defined as a natural transformation sitting on this. And this is, so it's a metric model that's lux, but the lux does not is with respect to the symmetric monoid structure, but it's with respect to the coherent isomorphism for the two naturalities of the lux, the metric monoid of two transformations. And it also needs to be smooth. So everything to work in families over many fours and these lux transformations, they have been defined quite generally by Schoenbauer and Johnson's flight for infinity and categories. And now I want to somehow connect this description of a field theory to what I mentioned before and the point here is this description somehow considered all allowed manifolds at the same time. So we study really quantum field series, not just on the fixed space or space time manifold, but on all series we can put it on. And this definitely contains more information and they even situations where we think might be trivial on the independent manifolds but the interplay is non-trivial. This is more generally, but how do we go back to the more practical description? For this we fix some space at some space with an n minus two dimensional manifold. And then we want to somehow take this anomaly field theory and restrict it to the space time. And the way of doing this is called or the world of dimensional reduction. So I consider this category and I'll look at geometric structures on sigma as my geometric structure on the two one zero borders in category. But I can map this into the n minus two border in category and how does this work? So I take an object in here or manifold in here and this comes with a geometric structure. It is an element in S of sigma evaluated on S. So this means that somehow S parameterized to a family of geometric structures on sigma. So this is also something which we will leave the contained in this redefining this structure on sigma cross S. So then I just map this to S for sigma equipped with this geometric structure that's seen as living in here. And I can use this to take this field theory and restrict it to this border in category and I can also restrict these relative fields. So I get relative fields on this type of border in categories. And now the connection to previous description is the following connector, which is definitely not due to myself, but I'm also not sure which name to put it. And it's, I would also say it's probably in the way I formulated it's wrong, but it should be morally true. So like it will be true in certain cases and then if one finds the right interpretation of the words, it will be true in general. And I will say a bit more about what this failure is in the topological case in a few minutes. As I have, which is impossible, it goes to two vector spaces and the statement is that these things are equivalent to terms sigma with the dimension. This is some of what one expects if the two descriptions of anomalies in physics, like the two mathematically ways of describing anomalies in physics. If they match up, then these two things also match up. And furthermore, the relative field series is equivalent to the section. One should probably put some additional adjectives on the field, like reflection, all the, or unitary or such. So this is like, this is more like a general guiding principle of what should be true. And sometimes it might be too direct or not. And I should also here mention that if you take a target space here, so you take that into a target space, then the connections to jobs on target spaces is ongoing work by Bunker and Weidoff. And they also have already done a lot of work on the non-extended case. So there's like really good hope that these type of field series at least have something to do with jobs. And then I also have not mentioned generalized homology at all.  I mean, they're fun because she's on many folds. So if we look at them, what's the case when we get a chief of spectrum manifold and these are things we can study in differential homology. Let me mention one physical thing one can do with this description. It's just the right boundary for so much. So if I have a manifold M, which has a boundary of six months, and M is now dimension N. So we got out, let me say something else before because you're gonna ask, okay, M is defined on n-dimensional manifold. And this description, I don't need it. And then the version of twisted field series by Stoltz and Feichner, they also just have a twist which is not defined on n-dimensional manifold. But having a theory defined on n-dimensional manifold really gives us additional data. And it's safe for you to study the theory. And the boundary correspondence one example. So the value of the field theory gives me a map form one and I evaluate it on the sigma, two A of sigma. And then I can take the theory A and evaluate it on M because we go back to one and then here I will get an automorphism of the monoidal unit of two vector states. So I will get a vector state for, depending on the family I would get a vector one. So this is, and this is the vector state and this is like the boundary space. And that's one proposition one can prove in this framework or at least in the non smooth framework that our symmetries, the symmetries on this combined system of the theory they act on the boundary space and non-projectively. And usually if one has an anomaly like if I consider this as a stage space the action of the symmetries would be only projected but if on this space I will always get abstractly a non-projective action of the symmetry. And now the last 15 minutes I will discuss a simple toy model. So the first simplification we will make is now that we don't work with smooth objects anymore but we restrict the topological one. And this makes our life, this makes a lot of things easier and let me mention how the topological world is connected to the smooth world so I can take my general best spaces. This is a sheath on many foods. So I can evaluate at a point and then I get a topological space or I get an infinity group or which I can model as a topological space and this has a left edge toy which will tend to topological space somehow makes it constantly as a constant, as a constant generalized space. And the same as to smooth infinity categories. So I can take one and evaluate it at a point or just take the infinity category or topological category make it constantly into a smooth category. And then somehow I say, my board doesn't categorize topological or the geometric structure as topological as board NF is equivalent to taking this constant thing on like a topological category just to put all this category F. And then you think it's a junction we can actually rewrite a fear theory on here as like a just a funnel between categories out of the sense. Okay, and then this gave also the definition of the job just to become simpler. So if I look at the flat job, in all jobs with the flat, this is just so that we have a connection on see all those days. This is equivalent to having a local system on T with values in two line bundles. And these are really now and brought to this back here because this is not a smooth category anymore. This is just an ordinary two category. And such a function is called a local system. Okay, now in this case, in the topological case, we can use the corpore doesn't hypothesis to study. To study the conjecture here and what does it tell us? It tells us essentially if I look at the series almost borders in category that say with maps into a target space. So this is equivalent for local system on T with values in for the end of it. And in here, I have the trivia ones which are given by just two line calls. This is in here and the job like this local system in here or the job would be the thing which comes from these type of things. And then yet also clear what goes wrong with the conjecture over here is my with my geometry structure includes an orientation that somehow more than that such a local system because it's twisted by the OIN action on the category of the fully doable objects. So this was a lot of abstract stuff. Now I want to do something extremely simple which are not something where one can do a lot of things explicit, I should say. So we've and these are these discrete gauge series. So we fix the finite group D and then we want to build a gauge series in dimension N out of this. I should also say these have first been studied by Dicap had written and a lot of things I'm going to tell you are based on a paper by Friedland Krim. These have been studied in the Nazis. But somehow you can study this framework in this case where you can make some precise techniques. I want to explain. And then the action is given by an enter. I want to build an N dimensional gauge theory versus finite structure. So the action is given by an N co-cycle in D D with values in D one. And now there are two theories one can define the first one as the classical one. So this is defined on co-ordered which are oriented and dimensional problem. This talk I just extend down to N minus two but the series can be defined as something fully extended. And this goes, this is invertible. This goes to two fact. And now this is not smooth. This is really just I do both bi-mortals and bi-mortals. Or if you want, same, I think the linear category is linear found those and natural transformations between them. And what this does, I take an oriented manifold which comes with a map to BD. This map does describe my D bundle on X and I should assign to it a number. So the number I assign to it, I take this co-cycle here I put it back and I integrate it over X. And then, yeah, okay. Let me mention also what is the, there should be a line bundle assigned to N minus one dimension manifold. I'm directly telling you what happens on N minus two dimension manifold. So to this I should assign by this construction. I should somehow assign to it a job on the field. So I should assign to it a job on D bundle on sigma. That was true. And this is the transgression. It's classified by the transgression to sigma for makeup. So this is the category just has one object, one algorithm of this and then a map. So this is something like a KZ two space. Then the map into it is just described by a two-pointer. So I need to give you a two-pointer cycle on this space. And this can be done using transgression. I have maps on sigma and two-pointer. And for sigma, this maps by a variation to be D and by a projection down. So this is the same as print of the D bundle on sigma. This maps to one on sigma. And then the transgression of omega two sigma is defined as a full-back on the evaluation map. And then I integrate, I push it forward by integrating with the sigma. Okay, and this is a line bundle which is classic if you assign to a vector space. Okay, and then there's the quantum version, which is now just given by thumbing over here. So what we want to perform usually is a parsnetic work. In this case, we can actually do that. So it's one of the, that's what makes this VK series from there. And that's the final position function as the pars integral over bundles, or D bundles on X, and then I take the action, which is from this thing. And then this integrals that they're only finite in many bundles with a discrete structure group on a compact manifold. This is just a sum. And then one needs to put in some normal notation factors. Thumb over isomorphism classes of D bundles on X. I desire my G series on it. And I decide by the automorphism. Number of elements in the automorphism group and this group. And then this also needs to assign vector spaces to n minus one dimensional manifold and two vector spaces to higher, to n minus two dimensional manifold. And this does happen. So let me again only do the n minus two dimensional thing. This is given by taking sections of the D bundles on X. And this classic, if you really find the job over this space and I take sections of this. This is my, this will be a linear category. And this is what the series assigns to it. Now, last few minutes, actually talk can talk about on the on the on the symmetries. Do you think I'm going to say have been studied the physics literature by Kapustin and Swarbring. And then some awesome thing I say about boundary series have been studied in a paper by Witten and then a paper by Wang Wen and Witten. So in a symmetry. Now it's another kind of G, which should act on my theory and it acts classically by acting on the field. So I want to have an action on the stack of D bundles. This is represented by BD. So I can describe this as a map from G, the automorphism with BD. And as a hierarchy, this is the automorphism of D. And then D acts on this by conjugation.  I thought this is my action.  So this is again equivalent to fixing an extension. And this G hat somehow tells me how D gate field and G gate fields combine. So they are there some are not independent. If I want to put it on background, I want to go to which I have a G gate field. This is sometimes called fractional notation of symmetry and physics, or that's at least how I understand the term. Okay. And then this is not just an action. I want this to be a symmetry of the classical field theory. So the condition is that the omega is just its point for, I mean this action induces me an action of G on the collection of n dimensional Gs. And I do one extended ones. And then, but still this fixed point is actually data. So I need to say how it's a fixed point. And if I want to fully extended ones, then there would be more data. But in particular, they could also be never been another. Because then the theory would be fully local. And we can use the co-border in my process to have it to that confidence. But this implies. That if I look at the digraphic theory to the quantized version, then this lives to G. This is now fun to which goes to the category of G presentation. Now to host anomaly appears. The background fields are just orientations. And I want to enlarge them. I want to move orientations and background fields for the symmetry. So I also want to have the bandwidth that's background fields. And now, let me first mention a situation where you can do that. So if find an omega hat. And the cycle on the PDG. Which pulls back to omega. And then I can gauge the symmetry. So I want, which means I want to define the theory defined with these background structures. And what do I do? I take the field theory. For omega hat. And then if I have a group of morphogen like this. If I have a group of morphogen like this, I can push forward. So I push this field theory forward along with. This is defined from your PhD on G. And in the front of your framework, this has been explicitly defined by which I go to focus. Okay, in this case, this. So in this situation, there's no anomaly. The last thing I want to say is about the situation where one has an anomaly. So I can look at a really similar. And then I find an omega hat. Which pulls back to two omega, but it's not close. And then the close thing is the pullback of something close. So theta. In. Okay. In this case, this omega itself will not define a field theory ahead, because it's not close. But what it will define for me is the natural transformation from the identity to. Now the statement is that one can actually perform a relative version of this push forward. So I can take this theory and omega. And I can push it forward. And this is something which goes from one. And this defines the relative for me. This then so this is 40 relative to this invertebrate theory describing the anomaly. The job describing the anomaly is just a transgression of theta to the base of bundled. And this is something which is much more explicit on how the space and space spaces look. That's in my paper with Richard. And then one last thing is one has an anomaly. This is not a big problem in physics, but what I cannot do is cage. So I cannot now some over G bundled. And this is also what happens here because I cannot. Because this is not the pullback of the theory. So I cannot perform a push forward to the point, which would be the quantization. Okay, that's everything I wanted to say. Thank you for your attention. So I suppose.


Good evening. This is Crime Classics. I am Thomas Highland with another true story of crime. Listen. That's the way Missouri sounded just after the Civil War. Wind through elm trees, wind through long grass, wind blowing up the dust and puffing it down the wagon road. And listen again. Another Missouri sound. Rope. New rope. Freshly purchased at a crossroad store and cut into six equal lengths to support six bodies of approximately equal size by neck. Six bodies. Six Missouri boys in union uniforms. Newly come home from the war. Waylaid by Cole Younger and his brothers who were on a perpetual rampage until they were stopped. So tonight my report to you on the younger brothers, why some of them grew no older. Crime Classics. A series of true crime stories from the records and newspapers of every land from every time. Your host each week, Mr. Thomas Highland, connoisseur of crime, student of violence, teller of murders. Now once again, Mr. Thomas Highland. Before the Civil War, there was a border war.  And the next Saturday night, vice versa. It got so they didn't wait till Saturday night. Every day was bloody day for everybody. The question now arises, why? The answer is simple. A difference of opinion about slavery and they couldn't wait till war was declared.  And one day, through this never-never land of pistol and knife and torch, there walked a young man. His name was Cole Younger. He was leading a horse and buckboard. And when he came to a certain shack by the road, he was at the end of his journey. People around saw he wasn't armed, so they let him through. They saw his face and the look in his eye and they let him through. Learned to knock on a door, sonny. You're Mr. Quantrell, ain't you? I admire politeness in young men. You try and knock on... My dad is dying on a buckboard outside. You come see. I've seen dying, sonny. You come see. All right. He's dead, sonny. I'm sorry. Shout him while he's standing there just talking to him. Just saying why were they on his land? Shot him because he raised his voice to them. Kansans? Jayhawkers from Kansas. North boys. What are you needing, sonny? A bearing for your daddy? A bearing's a private thing, and it's a thing I'll do myself, Mr. Quantrell.  Tonight, maybe. After I bury my daddy, maybe? Soon after that. I'm coming with you. Of course you are. Not right after he buried his daddy, but soon after. Cole Younger had to take an oath before he became a member of Quantrell's Raiders. It was called the Black Oath. The black being the color Quantrell admired most. Since it suggested death and danger. The candidate was placed between four men clothed in black, wearing hideous masks representing the devil. First, these men plattered long, keen swords together. Then pointed one at the candidate's throat, one at his heart, one at his arms, one at his feet, while the oath was spoken. The purpose of war is to kill. I will fight because I want no other occupation. I will tear down, waste, and destroy my enemies. By the powers of darkness here under the black arch of heaven's avenging symbol, I pledge and consecrate my heart, my brain, my body, and my limbs to exterminate Federals, Jayhawkers, and their bettas. And if I fail in my oath, may an unmerciful devil tear up my heart and roast it over flames of sulfur. Well, by the time war came, Cole Younger was two years older. He was Quantrell's first lieutenant. This rise from the ranks because he was a smart lad, a reader of books, a blower up of ammunition trains, a burner down of farm buildings, a pillager of par excellence, a murderer meticulous in that he only shot males and mostly always from the neck up. And the exception to this last was the time in Lawrence, Kansas, in a bar on Christmas Eve. So step up to the bar. That's so billy, drunken friend Billy. You sleep so sound, Billy. And don't you too, Johnny. You sleep because you got no sleep at Shiloh. Tell them how it was at Shiloh, should I? Listen all you all. You step right up and have a drink, courtesy of me and Bill and Johnny and the Union Army. Yang. What you doing around these parks? Send us out here to get us Quantrell. What's your name? Martin Wallace Martin. A sergeant from the stripes on your uniform. And my drunken friend Billy's my corporal. You've seen a lot of killin', ain't you? Didn't you hear? We were at Shiloh. Were you brave at Shiloh? Huh? Brave, like y'all now. What are you talkin' about?   Billy, corporal Billy, wake up. Now you come on, open your eyes, Bill. Can you see this, Bill? Johnny. Yanky, Johnny.  By your shivrin', Johnny. By your shivrin', so. Merry Christmas to one and all. You're young, aren't you? Well, yeah, but what's the idea all you men bustin' in here? Vigilante's. What you won't hear? Cole Young is your brother, isn't he? Yeah. Where is he? He ain't here. Where is he? He's fightin' a war. Shootin' three men down, two of them sleepin' and ain't fightin' a war. Where is he? I told you... Take that! That rope over that rafter. Where's your brother, Johnny? Look, I... I don't know where Cole is. Texas, maybe? Louisiana, maybe? All right, man. You want me to holler. You want me to scream mercy. Well, hang me and see if I do it. All right. All right, Johnny. Yeah, you're, you're fightin' a lip when I put the noose around your neck, but that ain't hollerin' is it, John? And drawin' it tight. You ain't hollerin' either. Or you're hidin' Cole. All right, Pickett, let him down. Loosen the rope a little, John, so you can holler. Or tell me where Cole is. You're right before I tell ya. You're right. Before I tell ya. Regular brother to Cole, ain't you? Try me. I just tried you. The end of a rope? A dozen of you did that one at a time. Pickett! Wait.  I gotta say something. I gotta tell you about Cole. Why, if you were lickin' his boots, you'd be in the right relation to him. He's fightin' for what he knows in himself. For what? For what your brother is and a blood-letter and... Kicker, are you? That's good. That's very fine. Because now you'll kick high ones and low ones and the air all around. Pickett! But they didn't hang him until he was dead. They hung him till just before he was dead and then let him down. And beat him up and left him. But they didn't find out where Cole was and that spunky brother of his knew all the time where Cole was. In the hills, not two miles away. Down the road and through a pass and up a hill and two miles away. Hi, John. They came looking for you, Cole.  Did a thing with a rope. Here. A thing like that and you didn't sail where I did you. I'm comin' along with you, Cole. From now on. That's good. You are listening to Crime Classics and your host, Thomas Highland. Captain Cannelly of CBS Radio's 21st Precinct called to remind us if the station house will be shut down this Friday night while the program moves. Beginning next Wednesday at a somewhat earlier hour on most of these same stations, 21st Precinct will join Crime Classics, Crime Photographer and the rest of your Wednesday stars address dramatic thrillers. Listen for the 21st Precinct a week from tonight at its new time. And now once again, Thomas Highland in the second act of Crime Classics and his report to you on the younger brothers. Why some of them grew no older. On April 9th, 1865, General Lee surrendered and the war was over. A thing happens when a war has ended. A pall hangs over the land and then suddenly there's a maelstrom of activity. Returnings, accountings of gains and of losses, dead battles fought again on saloon tables, lost legs bragged about the blinded eye, the maimed arm, the victory ball and the brain shocked from its moorings and adrift. And finally, the bright young men funneling into the area of sorrows and devastation. To sell, to cheat, to build. Which was Missouri in 1866? Six of them Yankees, Cole. And one shot scared him. All right, man, get him. That don't look like none of them are armed, Cole. Yeah. Who's speaking for these men? I'd be. Who are you? What the six of you doing riding here? I ask you the same question. What's 50 of you doing stopping us? There must be 50 of you. I'm Cole Younger. I've been over there as John Younger. That's my brother, Jim, and Bobby's... They're younger boys, huh? That's right, mister. I hear you believe the war... Yes, you believe like me. That's why you're riding in uniform. Boy, you're not a simple man from what I heard, Younger. You know why we're uniformed? We're riding to Indians. John. Remember, Cole Younger and his brothers hanged six soldiers. You might ask how come Bob and Jim Younger were with Cole and John all of a sudden? Well, they were. After the war, there was a reunion, and the four of them decided to cast lots together, as the saying goes, to join forces, to butter their bread all on one side. Anyhow, for the next ten years, the brothers Younger robbed and killed and burned. John Younger was shot down by a detective in St. Clair and was buried near there. Then, on the 7th of April, 1876, in a shack on the skirts of Northfield, Minnesota. It's them, Cole. All right, Bob, open the door for them. Come on in, boys. Hi, Jesse. Hello, Cole. You met my brother Frank, haven't you? Sure, everybody knows everybody. James, boys, Jesse, and Frank. Cole. Uh-huh.  Don't you worry about it. I ain't worried about nothing, Cole. I just asked you a question. Don't worry, Jesse. They'll do what they gotta do. They'd better. Everything ready? Sure.  Yes, I know. Then we don't have to wait for nothing. For nothing at all. Cole. Uh-huh. A lot of money in that bank. That's good. Me and Frank talking about return for a little while. Going to Mexico. Hey, Sniff. What are you smelling, Cole? Too empty. Just said too empty, that's all. You and me, Jess, Bob and Frank, rest of your weight. Stick up, Mr. who just slide everything you got through the window. Back of the window, Jesse, he's not cheating. Not the silver, Mr. Silver's too heavy to carry. Come on, come on. How you and Frank doing, Bob? Good, good. Let's get out of here. Come on, Bob, Frank. Okay, boys! I just don't gallop till we turn the corner. All of us galloping might disturb that meat in it. What's matter, Cole? Too empty. Like I said. Let the shiver about, Cole, as a meeting. Plan, kind of empty. That's what these streets are... Look there, boys! Run! Run! The bank robbery at Northfield was the turning point. The instant that the townspeople, instead of being at a meeting, had formed a posse and ambushed the outlaws, the bringers of terror became fugitives. The younger brothers had never turned tail and run before, nor had the James boys. But some loop in time, some coordinates of chance, conspired that they retreated at exactly the same moment. At darkness they lost their pursuers, but they kept riding. It was not until almost midnight that they found a hiding place. Ah, Jean, Bob. Hurt. Lucky we got away, ain't we, Cole? We haven't done it yet. Jim hurt bad. Ain't riding no more. Dying? Baby. Cole. Yeah? Jess is fuming. I walked over in the clear a minute ago. Him and his brother was teasing with Jim. Take us a walk, huh? Hi, Jess. He's looking at your brother here. Marvelous. Oh? How is he staying alive? I'd bother a new son. Well, I'll tell you, Cole. Yeah. Yeah, it is. Jessy. You're talking at me, Bob Younger. Tell my brother, Cole, what you've been saying about Jim. I've been saying, Cole, your brother, Jim, be better off dead. Better for a lot of people. Like who? All of us. So we can get on our horses and start riding. How long you think it's going to take that posse to catch up with us? The truth is, Jessy, I haven't thought about that. Well, not just you think about it. Jim can't ride, Jess. That's what I've been saying. What do you think we ought to do with him? Leave him. Oh? Or shoot him. I'd shoot him. Jess. Uh-huh.   I'll tell you what else I've been thinking. Tell me, Cole. Tell me real fast so you can get it out. Thinking hard would be we drew on each other. Be pretty with me. Want to try? Be pretty with me. Stop, stop it!  That's what happened. You know it. What do you think, Jessy? I think maybe your brother, Bob, is right. But you want to try. Here I am. You get going, Jessy. You're going to stick around for a posse? Maybe. Just you get going. Not because you're saying it. Because I think it's a thing to do. Come on, Frank. Jim, can you hand me a brother? You know, smiling makes me know you can. Now, don't you talk? Coolness to your head. Don't you worry. Nobody's going to leave you. We're going to take care of you, Jim. Get a doctor to you. Somehow they eluded the posse from Northfield and Jim got stronger. There were four of them, Cole Younger and his brothers Jim and Bob, and a man named Charlie Pitts. Across Minnesota they rode and into Iowa. And now there were posse everywhere, some numbering a thousand men. And they couldn't catch the younger brothers. Rewards and promises by bankers and sheriffs and governors. And they couldn't catch the youngers. The brothers, as far as anyone could tell, were headed into Missouri. But no one could catch them. And once... I think I got one of them, Cole. Me too. I think there was only two. You cover me, I'll go make sure. Thought I'd got you before, Sonny. Not my part. Guess me and my brother both got him. You hurt bad? Crazy to try to ambush us, only two of you, son. Reward? What are they offering for us? Thousands, I don't know.  Everybody. They all out after the younger brothers, huh? Everybody. You hurt? Hurt. You didn't deserve better, kid. Two, I'm cold. Like you said, kids. Kids. How old are you, brother Bob? Yeah. It's a long way. Bob, get out! Just keep shooting! And at last they were surrounded. Charlie Pitts was killed almost at once. But the younger brothers held off a hundred men for hours. Finally... Right out! Shot the pizza! And they truly were shot to pieces. Cole had been shot 11 times, with one rifle ball under his right eye. Jim had eight bucks shot and one right shot. And one rifle ball in the body. Plus the shattered jaw bone he'd received at Northfield. And Bob's arm was practically macerated. So they were captured.  Done now. The younger brothers leashed. Finally... They were tried and sentenced to life imprisonment in the penitentiary at Stillwater, Minnesota. Several newspapers tried to get Cole younger story. There was a copy of the letter which he wrote to one of them. Dear sir, without intending the least disrespect, permit me to say, positively I will have nothing to do with writing a history of any kind. As for anything since the war, a true statement would fall flat. I look upon my life since the war is a blank and will never say anything to make it appear otherwise. The world may believe what it pleases. I have nothing to say unless it would be a request using the language of a fellow. Speak of me as I am. Nothing extenuate. Nor set down art in malice. I was a soldier and fought to hurt, but I never molested an uncombatant. Truly yours, Coleman Younger. Bob Younger died in prison in 1889. Jim and Cole were released after 25 years. In 1902, Jim committed suicide in a hotel room in St. Paul over an unrequited love. Cole lived until 1916, a quiet life. He sat on a front porch in Lee's Summit, Missouri, and whittled and rocked, and talked to hardly anyone at all. But he thought a lot. In just a moment, Thomas Highland will tell you about next week's crime classic. The Younger Brothers tonight's crime classic was adapted from the original court reports and newspaper accounts by Morton Fine and David Friedkin. The music was composed by Bernard Herman and conducted by Lud Glaskin, and the program is produced and directed by Elliot Lewis. Thomas Highland is portrayed on radio by Lou Merrill. In tonight's story, Jack Edwards was heard as Cole, Sam Edwards as Bob, and Jimmy Eagles as John Younger. Featured in the cast were Barney Phillips, Clayton Post, Bill Bissell, and Walter Tetley. Bob LeMond speaking. Here again is Thomas Highland. Next week, South Con Can, India, in the spring of 1856. We will concern ourselves with two brothers. Their names were Conak and Supen, and they despised each other. It's listed in my files as How Supen Got the Hook Outside Bombay. Thank you. Good night. Two more familiar CBS radio headliners have moved. This Friday night on most of these stations, where you've been accustomed to hearing stage-struck, the star's address now brings you the new Friday night full-hour Arthur Godfrey digest show, bringing you Arthur and all the little Godfrey's back to nighttime radio with a bang. As for stage-struck, this fine full-hour visit with Broadway shows and Broadway folks will be presented Sundays at the star's address from now on. Thursday nights, Marlene Dietrich stars in Time for Love on the CBS Radio Network.


So you got some friends coming over to the house and you want to show them something unique and special maybe they never had before, check this out.  Take some olive oil, get the oil down in between the leaves, get the other side. Now you take these straight out to the grill. Let them fire up, it happens quick. It's been about 45 seconds.  A minute and 15 seconds. That's all we wanted to do was get that nice char on them just like that.   Now you need some dandos original, that's the green top and now we're taking it to the next level with dandos cheesening, that's the cream top. Give it a shake. Give it a pour, stir it up. Grilled lettuce is phenomenal. So is that dressing, give it a try. Let me know what you think. We'll see you next time. Keep sprinkling.


Hello everyone, this is the GSOC Jenkins Dockerbase Quick Start meeting. We are on the 14th of August 2023 and today we have Ashutosh with us and Berviento, who may have some internet problems. So we are on the week 23, I guess, and we have lots of things left to do but quite a few things have been done or are about to be done. So what I had from last week was about keeping a list of the plugins up to date thanks to a GitHub action or something. We also wanted to give the users... We wanted that the users use pre-built images and not build on their machines anymore for two main reasons, which are speed and tested platform.  And we also had a proxy warning configuration to remove only for GitHub, which was not working. Let's start, if you don't mind. So as for the node tutorial, we used to have a problem with the port 3000, which was hard coding the pipeline, but I think you have already sorted this out. Ashutosh, am I right? Yes, yes. I think it was sorted a week before. Yeah. Me too. Last week. And as for automation, there was another work item, which was about using the real job and not only the simple job, and I don't know what you did for... I can't remember what you did for the node tutorial in regards to the automation part. Oh, I think you did it. You added an ID to the input so that you could, with a call command, say abort or proceed. Yeah, you did it. Done also. So the pull request I've seen closed last week were browser to preview. Come on, come on. Looks like my internet is slow also today. Let me make it a little bit bigger. Ouch. Okay, thank you. So I had added a configuration for Gitpod a few weeks ago, but sometimes it worked. Sometimes it didn't work, and we didn't know why. And you found a workaround, which is the use of open preview instead of open browser, and it seems to work, at least for me and for you. I don't know if you have tested that, but it seems to work, which is pretty handy. That's why, yeah, cool. That's why it got moved last week. Well done on this one. This will prove useful because people won't have to click anywhere. It will just open the tab. At home, it's a tab. Is it a tab also for you or a new window? It's like half a window inside the code editor itself, but it has the button to make it full screen in another tab. Right alongside it. Then there was another one. I really wanted this one to get done is update Jenkins plugins because I was getting bored with doing that by hand. So the goal there was to find a way to update the plugin automatically. So the one I just clicked on is not the one I was referring to. This is one of the manual PR that I did to update the list of plugins, which is not what we are looking for. More on that a few minutes from now. Then we had use prebuilt images instead of building them locally. So the week before you had produced a PR that creates Docker images and push them to Docker hub. Okay, there it is. Oh, okay. That's for the next, my bad. Let's go back to prebuilt images. So now that we build and push images to Docker hub, we want the end user to use them instead of building on their own machine. So you did this one use prebuilt images instead of building them locally and seems to work so well done. And thanks for the review. Today we still have a few open PRs. So the first one is very old for Docker hub repository until last week we had hard coded in the, what is it? GitHub action. The name of your repo within the Docker hub registry. Yeah, that's a correct name. And so now I guess you have declared a new system variable. How is it called in GitHub? I've added the environment period. I think it's environment. So that now I've seen that you can use the variable directly and it will build and push to your repo, which is defined within the variable.  So Docker hub username and it's defined somewhere within the settings of the website of the other repo. There is an environment variable defined, which is called Docker username. Fine. So I guess this one is ready to merge. Yes, it's working for me. Right. Now I checked it. I haven't checked on that part, but it should work. Okay. Fine with me. The goal there is one day to migrate your repo to the Jenkins CI organization and just have to change one variable and we will be good to go. Then there's another one which is adding an updating read me. I think it's about the second persona and I could be wrong, but I think it is. Yeah, that's it. So as I've said a few minutes ago, we want the end user to use pre-built images and not build them by themselves. But the thing is if we have an end user that wants to know more about Docker and Jenkins who also may have a platform which hasn't been tested yet, for example, ARM 32-bit or RISC-5, PPC-64LE, whatever, we don't want to restrict these users. So we wanted to have a part of the read me that would explain how to build and execute the images built locally. And I think I gave a review earlier. You made the changes I had asked for, I think. Yep. So I think we are ready to go. Then we have this one which is not ready at all. I've read the summary of the last Docks Office Hour you will participate in. And you had an interesting, at least to me, discussion with Mark and maybe Meg, I can't remember, about this last tutorial. And it looks like we can't get rid of the Blue Ocean set of plugins yet to go to the end of these tutorials. So you put them back into the plugins.txt. You are right. Yes, for this tutorial, since it uses Blue Ocean too much, I've added the Blue Ocean to the plugin.txt list. Yes, I'm afraid we have to. But it works without Docker and Docker since it's similar to the Node tutorial, so using the same agent works fine. Yes, I read that. And that was a good surprise for me because I was afraid we would have to use Docker and Docker. So yes, that's cool. We went up to the end of this set of tutorials without Docker and Docker, which is a good thing. So not ready to merge. I think we will still have to discuss and maybe also with the next Docks Office Hours. We'll see. We should maybe make another demo show them that it's working without Docker and Docker and see if they find what they were expecting. But that's cool. We are progressing. Thank you. Ah, the one I was looking for, the plugin up to date. As I told earlier, I'm kind of bored with that. I don't want to do the plugin updates by hand anymore. I have supplied a few bits and bobs, you know, some hints to get you started. But I think you did something much better. And frankly, I haven't seen PR yet created by that maybe because it's not on the main branch. I don't know. Yes, I forgot to change the time to check, but it should create this tonight at midnight because I've used it. So it works on every branch and with different name for the branch. It uses the time, date and time for the branch. So I believe you, of course. But better safe than sorry. It should work without being merged, right? Yes. So I don't know which midnight is it. Is it the US midnight UTC something? Thinking lit. I should, it will be okay if I push it right now to check if it's working or not. Wait a second. Yeah. Go ahead. So would you like to share your screen or? Okay. Sorry. I'll share it. It's almost an excess thing. Live coding. That's cool. It looks like you are way more fluent with Git than a few weeks ago. That's a nice thing to see. Yeah. I want to learn GH now. I haven't used it much before. I used Mark in the meeting using it and it looks way better to use that. Mark is mastering GH and Git like nobody else. Yes, it's a joy to see him operating Git and GH. Wow. That's quite something. And it's a powerful tool Git and GH on top of it. It's a joy to use. I made some really cool things thanks to GH in Git of action, for example, or even in Jenkins 5. That's a nice tool. I love it. So we have something running. So Kodasi, we don't care. Okay, image, plugin to date. Oh, plugins, update, file, test. Failed. Oh. Okay. Okay.  The demo gods were not with us today. So we'll let you work some more on this one. Yeah. Wait a second. I just think it will work. Okay. Go ahead. If you feel like the small modification could make it. Fingers crossed. See the steam. What is it too small? No, no. For me, it's okay. Read it. Layers. Layers. Layers. Okay. So the agent has started. What about Jenkins itself? Jenkins is ready. Last LTS. Fine. Yes. See, sometimes happen. So origin main is not a commit and a branch cannot be created from it. Okay. So there is still some work to do. Sorry about that. Yeah. Stop saying this thing. Yeah. That's okay. Let me share mine. Nice try anyhow. So the last one was removing reverse proxy warning on it. But I've seen you've done something with YQ. I think. Yes. I have updated the report. Yes. You are. Yep. So I think it's ready to merge. Now we still have 14 items, not all of them are for last week, this week and next week. So we'll focus only on the ones for this milestone and the previous one. Yeah. So keep the plugin list up to date when building the Docker image. So it will not happen when building the Docker image. We all got that. It's every day at midnight. And it will work in a day or two. Yeah. The next one, we've already merged this one. Oh, we haven't figured out yet how to configure correctly, depend about. Because I haven't seen any PR for depend about yet. I guess it's not working yet for whatever reason. I know last week we clicked on several links, buttons, whatever it did not do anything. And I guess nothing has changed on your side. No, not yet. Okay. But I would really want to see if this one done because it will keep the project way more secure, I would say. I may be naive thinking it's just updating dependencies will make it more secure, but you get the idea. And frankly, that's something that don't want to do by hand anymore. We have tools to do that. So let's try to make it work. Then we have the end to end multi branch pipeline project creation. So you've discussed that with Morgan mega thing last week. Would you have anything to share regarding that. So, Mark was also agreeing that we should keep blue ocean for at least one of the tutorial. Since it's easy to understand for beginners to and also when I first use Jenkins, I used it with blue ocean. So I like blue ocean. And I first used it was simple to understand. Yeah, it's a very nice tool. The only problem is that it's deprecated or about to be deprecated and that's why it's a problem but if Mark and make agree that we should use it and go for it. Sorry, I interrupted you what were you about to say. Yes, so other than this. That will don't don't need docker and docker for this. And so, yes, I had another issue while creating the PR for this. And it's documentation it says that it has to use multi branch pipeline so in one of the pipeline. It should create. Output in port 5,000 but instead it's creating that in port 3,000 instead. So like there are two tutorials, two things, two times when it creates a react website output one on port 3,000 and one on port 5,000 according to the documentation but it's creating both on 3000 for some reason. I don't know in the tutorial. It's something the wrong with tutorial and I don't know right now. I don't know either. I will have a look. I don't know I can't remember and it's kind of complex the way they start with docker and so on so maybe there is a definition of the port 5,000 somewhere. I don't know. We'll find out. I am trying to find out right now. I'll let you know if I find out anything other than that. I asked Mark how should we how it will go by integrating this into Jenkins. So he said he wants to wants us to me to create. PRs on the Jenkins.io separately for each tutorial. But I'm not sure how it will go that first maybe first we'll need to be touching with the infra team to discuss. It should be first go with the documentation. Okay, so only documentation for the time being. Yes, and I also wanted to know like like you mentioned before like it's not production ready yet and how it can get production ready or what we need to do for that. That's a good question. To be honest, I don't know yet how we should do that. We've got lots of security alerts that maybe we should get rid of before calling that production ready. You know of the alerts we have in the security tab in your GitHub repo. We have to have the automation of the Jenkins plugin update. We have to have the automation of the update of the Dockerfiles. All of this has to be automated before even trying to call that production ready. And then I guess we should have a discussion with Damian de Porto and the other people from the infra team to know what they are expecting before integrating that into the Jenkins.io organization. Frankly calling that production ready as it's only a tutorial for end users is a bit stretchy. So yes, I guess the thing we should do we have a clear discussion with people from the infra team to know what are their expectations. What are the prerequisites? What do we need to have something that they could integrate into their infra? Okay, I got it. First of all, let's do documentation PRs. What bothers me with that is, okay, we'll modify the documentation, but we should modify the documentation while referring to your own GitHub repo. Yes, that's that's what I'm going to do. Yes, it's a chicken and egg problem. Yeah, I won't be able to make it to dox office hours this week. So I don't know if you will be able to go into one of them, but maybe you could ask questions to mark and whoever will be there. So we know how we should start. Should we start with the egg or with the hand chicken to the existing repo? Whatever, I think I have this play problem and the requirements. I never clicked on the O but there is no whatever. Okay, anything else about this last dox office hours of this tutorial? I don't think this is it. Okay, do you have anything, any feedback? Okay, thank you. Yep, whatever. Okay, so we still have more than two weeks to go before the end of the month. Yes, we're only on the 15th tomorrow. I was trying to think straight in my head, being in PTO is not easy. You know, I even don't know which day we are. Of course, we are on the 14th today. Need to sleep, whatever. So I don't know when you are supposed to be done with that project at the end of August. I think because we have to make an evaluation for the beginning of September, am I right? According to the GSOP timeline, coding period ends at 28th of August. After that, it's mentors evaluation. So I think what Jean-Marc said last week is still valid, relevant. So we'd like to have a document that tells us what needs to be done to be part of Jenkins CI. So you've already gone to last dox office hours. We know more now because Marc said he wanted to have some PRs for the documentation, but we still don't know if we should refer to the existing Ashutosh repo. So maybe you should write down somewhere that we still have some questions. Then we should have a discussion with the infra team knowing what are their prerequisites and expectations. So all of that should be documented because we may not have enough time to be part of the Jenkins CI organization by the end of the GSOP project. So at least let's document that. This one can be more or less removed. Yeah. Okay. So yeah, definitely that's what we should focus on once we have finished the technical part. We don't have that many work items left. Some of them could take quite a lot of time we'll see, but it would be nice to have them done by the 28th of August and then have a document that lists the things that we'll have to do later on to be part of the Jenkins CI organization. Of course, it's your repo. Maybe you'll find sometimes you're in there after GSOC to continue working on it just tiny little bit. Of course, not 20 hours a week. I'd like you to be there when it will be part of the Jenkins CI organization and see that your documentation is in Jenkins IO website. I think that would be a freaking nice milestone project done. Yeah, I contributed. It does work. And of course, we would like to keep you as a contributor or regular contributor for Jenkins, but you don't have to. We would love to have you after GSOC ends. And we've got to ask you guys another thing like for the next year or a year after that I'd like to become a mentor like you guys are. So, like, like, not you guys, like you are to experience like, like some of the like he contributed one year, then he became the mentor next year. Chris did that. Yeah. Yes. And so how, how much knowledge do you think I would need to become a mentor? Should I next year should I again participate as contributor then become a mentor? That's a tough question. Frankly, I don't think I know that much, but I became a mentor nonetheless. I think it's not knowledge. It's more about experience and maybe confidence. But even if you don't know, you know that if you search, you will find out or you will find somebody that who knows what it's all about things like that. It's not about global knowledge. Frankly, I don't know that much.  But I won't evaluate myself. I won't say I'm a good mentor. The level of knowledge I have, the level of experience I have does not make me a good mentor. I have no idea. Bevin too. What do you think? No, no, I was not asking for your approval. Not at all. Not that. I wanted to know what do you think is needed to become a mentor? Is it experience? Is it knowledge? Is it something else? I think it's fundamental for Jenkins and also some knowledge about Jenkins. Yes, some knowledge and maybe the whole knowledge of what Jenkins is, how it works and so on. Because frankly, there are lots of dark places in Jenkins haven't been into. There are lots of things I discover on a daily basis on Jenkins. It's a huge project. It's an old project. So you can't know everything. Even Mark does not know everything. I don't think one person, even Basil Crow, doesn't know everything in Jenkins. So you should know more about Jenkins, of course. But I'm not even sure one mentor should know lots of things about Jenkins. He should know what it is, how it works, some things about the network, maybe Java, of course, or Docker. But I'm not sure you have to be an expert in Jenkins to become a mentor, frankly. I think the main motivation would be the desire to share, to grow, to learn. That should be enough. If you're curious and ready to spend some time, I think that should be enough, more or less. We'll see. We still have not one year, but we still have a few months for you to decide if you'd like to become another GISA contributor or a mentor. We'll see. I think, yeah. And frankly, if you continue working on open source, even if it's not Jenkins, you will learn lots of things. Hopefully you'll find welcoming community. All of the open source communities are not that welcoming. So sometimes they don't want to spend time to explain to newcomers how things work and so on. So it's sometimes difficult to get some knowledge to grow within some communities. But of course, Jenkins is kind of welcoming community. I think it's quite healthy and benevolent. So if you'd like to stay with us until next GISA, please do so. Try to do some PRs here and there or to finish or contribute to this project even more. Hector, our first will be coming soon. I'll be part of that. Yes. And if you'd like, if you have some ideas that you think you won't have time to implement before the end of GISA, don't hesitate to create new issues, work items, and then maybe in September, label them with good first issue, October 1st and so on, so that anybody could come and try to help. I know it's not yet part of the Jenkins CI, so I don't know how this would be welcome. But I'd like that we integrate your repo into the Jenkins CI organization before October 1st, so that people would contribute to Jenkins CI through your integrated repo. That would be really cool. And you could be starting to contribute as some kind of mentor because it's your project, you know. And I think this would be a nice experience.  That would be nice if you know it before GISA. We'll see. Yes. Thank you very much. Cool. Pito doesn't mean anything. Whatever. Is there anything you'd like to talk about before we wrap it up? We haven't discussed, I don't think we have discussed the goals for this week, other than the OpenPRs. Are there any other goals? I think there was one. Really? I thought I had to put all the ones for week 31, 32 and 33. Let me go ahead and check if you have something to share. I haven't seen. Go ahead. Yeah, this one. Use dependent board and update CLL to keep. Okay, this one is integrated. It was listed, in fact. Yes, but we haven't discussed it. You're right. This one could take quite a lot of time, unfortunately. Depend about, I don't know. We've already discussed that. We have clicked on the links with thoughts were valid and nothing happened. So I don't know if we should open an issue at GitHub or get some help in a way on another. I don't get it. It works on my fork. Why would it work on you? I think we are doing something obvious that we are missing something obvious. Yes, so I don't know how to open support. I'm going to have a discord. Gitter or something. Okay, so yeah, this one, first of all, trying to get dependable to work. I don't know how much time it will take. I don't know if we have something to do or if a bug in GitHub will see. As for update CLI, that's a whole other subject and it's kind of a difficult tool. It's not an old tool and the documentation is not that good. Sorry, Olivier. Olivier Verna is the main contributor, is the creator of update CLI. It's a fantastic tool, but the documentation is not as good as the tool itself. I know it's also my fault as everybody else because if the documentation is not that good, once you have understood what is going on, you should make a PR and make better documentation and I had a few problems with update CLI and I haven't done any PR yet regarding that. I've only created some issues, no PRs. Yes, it's not an easy one. Olivier used to work for the Jenkins project. He was part of the infra team a few years ago. He's a very nice guy, but that's not the problem. You could give a try at update CLI. I may have done a PR that I have closed, I think, regarding update CLI, though we may find something that you could begin to work with. Let me check. So in the issues... No, it was a pull request, my bad. Okay, EPR, update CLI. It's better when it's correctly written. Okay, it was just a reference to update CLI, my bad. Let's go back to the repo and have a look at my fork. Do we have a branch that works on that? More or less? Or not? We'd find that. Okay, I don't have it. I did win it. That's a bad thing. So Dependabot is a must-have. Update CLI is a nice-to-have thing. You would have to invest quite a lot of time before having just a tiny bit of update working. That's the way update CLI works. You have to spend quite a lot of time, the first time, in order to gain some knowledge. And then, when you feel more confident, the subsequent updates go way more smoothly. So it's not mandatory. It's not urgent. It's a nice-to-have if you have time, too. Okay, and if you're looking for examples, I've made quite a few ones for the Jenkins IO website. It's been merged a few weeks from now. So you will find the PR, or you will find it's a directory called a DTI, in which you will find all the definitions. The thing is YAML, which is not that handy, but anyway, it's YAML. And you define in the YAML, sorry, you define one YAML per tool you want to update. For example, if you're looking for Node, you will create a Node.YAML, in which you will say, okay, I will try to find in GitHub, for example, the last version of Node. Then I will try to find the latest version of Alpine, for example, if you want to use a Node Alpine Docker image. And then when you have created that version of latest Node and latest Alpine Docker image available, then you will try to find the files where it is referenced, and then you will make the update. Lots of regular expressions and YAML. Yeah, it's definitely a challenge. But you got that, of course. So do it if you want to, if you have time to, if you're interested in learning a new tool to update. Dependable already makes quite a few updates that work for us. It's able to update the Dockerfiles, which is our main source of code. That should be more or less enough. Update CLI is a bonus. Fine with it. And the last one was find a way to auto make the fork and clone part of the tutorials. I think you copied right away the config.xml in the test you do for the various Jenkins tutorials, Node, Python, and so on. It's hard coded in the Action file. Okay, Wari? Yes, it's hard coded with some variables for the links. Yep. But maybe, I say maybe, so this one is not monetary either. We should try to clone or get the file directly from a GitHub repo. The thing is the official tutorial repo is not finished, of course, because the end user has to do the work all by himself. So we don't have a working Jenkins file in the official sample repose. I don't know if we should use yours, for example, which had the definitive one. I don't know. It's more of a discussion, you know, you don't have to do this part. And the title is not that good anymore because that was written at the time where we were thinking that maybe we should fork and clone locally because the end user shouldn't do that. And that's not the case anymore. We decided a few weeks ago that no, the end users should be able to fork from GitHub and then clone locally. We don't have to do that for them. It's just that maybe we should reuse some of the scripts that were written at that time to fork and clone locally or not, just for the testing part. Once again, not mandatory. And that's all that I had. Did you see anything else that you wanted to do this week? No, I don't think so. That's it. Okay. Anything regarding school agenda or is there a day when you won't be available this week or? This week shouldn't be, it should be normal. I may get exams in September, late September or, but they don't last much. It's like three days. They take all the exams and it's in the morning usually. So Jenkins meeting office office hours meeting within evening for me. So it won't be a issue. Okay. You said end of September. End of the September. Yes. So, yeah, Jesus will be over. So that shouldn't be a problem. It's more for the presentation. We haven't decided yet. Yes. That's the subject we should discuss next week. Yes, of course. Yes. Thank you for reminding me of that. I had forgotten. Okay. Anything else? No, that's it. Okay. Thanks a lot for your work and your time. So I think we'll wrap it up. I'll try to pause the video from 24 to 48 hours on YouTube and modify the existing community Jenkins.io. I think that's the best thread regarding this project. So best of luck for the issues you will have to solve this week. And we did to get in touch via. Gitter element or our shared document. Once again, thanks a lot and have a good week. Bye bye. Thank you. Thank you.