have some of cool features to enable us to do so. So we'll be doing a lot of demos tonight because we just have like 30, 40 minutes, really hope. So OK, what we want to aim tonight is first, of course, we want to get our applications up and running in AWS, accessible from the rest of the world. And of course, we want to have some kind of configuration injections or what we say as environment variables injection using code build. Because yeah, I want to do as much as work inside AWS because in terms of speed, so we don't bust a lot of work into another third party solutions. And I use code deploy for deployment to AWS. So it will eliminate a lot of headaches here. And if we still have enough time, probably we have we will demos a little bit about the automatic rollback. So if somehow our deployment have failures or our code deploy have a cool mechanism named automatic rollbacks, very cool. And also the last, as a bonus, we're playing a little bit with AWS Lambda to send notifications about our deployment status. Is it successful or not? Keep us updated, right? OK. So this is what we possibly do with deployment in AWS. Yeah, we have a repository in GitHub. And it's very, very simple and straightforward. I'm pretty sure you guys have familiar with this pipeline. We have a git. First we clone the latest version of our software. And then we inject some configurations and firmware for everything and decide if this code should be deployed to the which environment is it development or staging or production or so. And we do some tests. If passed, then we perform the deployment. And each stage will be a trigger AWS Lambda to do something. We ask them to do like send notification to Slack, which is very important. So we always update what's happening in the background and we can also trigger something for the third party applications, like for example, if you are using Sentry. So Sentry have a feature of the name Release. So we can actually send notification to Sentry if, hey, I've released a new version. So please mark something in your application. And one of the most important thing is we want to keep all of our deployment and build activities always recorded in our database. So we have these records, every deployment, every pipeline run, every build, every deployment, everything who run the deployment, how the result and how much time it takes. We want to record everything so we can analyze it. So it's all now in Yoji, we are on the journey into these complex things. However, I don't think that tonight we can demo all of this. So we try to do a lot of simple things. Like I mentioned earlier that we will first we clone the latest version of our source code base and do some configuration injections. If everything is OK, then do the code deploy, do the deployment, do the easy to instances. And if we have some enough time, we will trigger some endless link of options to us like notifications. Hopefully we can do all of this. So first, this is tools for you to have a little bit of experience with code pipeline. Sorry, yeah, code pipeline. OK, good. Code deploy. Ah, perfect. All right. Code pipeline is actually not rocket science tools. Code pipeline is actually a wrapper. So it do nothing but link all the solutions. For example, we have a code build to build applications to get the artifact. And we pass some of the job to the third party solutions like Jenkins and everything. And finally, we do deployment and everything. So this code pipeline wrap it up. So this is some of what you can get from code pipeline. I want to work you through one by one with this. I'm sure this is not a very fancy thing. You guys are familiar with it. And this is what it visualized. So actually, the main point is on every stage, code pipeline has output which is stored in Amazon S3 storage bucket. Then basically, the output from the stage will become the input from the next stage. So the output from the first stage which is source could be called by any stage. So it's not sequential. It's not always sequential process. But the output from this could be called by all the stages as long as it's inside the same pipeline process. OK. As it's called deploy, it's very cool tools. So the deployment, we can always monitor what's happening now. And the most of the cool features of this tools is it can be, it supports blue-green deployments. It's very cool. So let's say we have 10 or 12 or 100 instances. So it supports completely zero time in every deployment. So if we are emphasizing the CI, CD, like a DevOps spirit that we have to continuous deployment, continuous deployment, I can imagine that we have, for example, four development states. For example, we have two or three servers there. So we perform three or four or seven times of deployment per day. So imagine if our system will be done. We experience downtime for a couple of seconds, just a couple of seconds on every downtime. For every deployment, it would be a lot of downtime per day. So we don't want that. The deploy came to rescue. All right. That's it for my presentation, because now time for demo. Now, first of all, of course, we need to make sure that this is my personal account. I've prepared one instance for this demo purpose. All right. So I start the instance. One thing in NWS is some part of this process that we have to wait. There's some process of deferred we have to wait a couple of minutes, like spawn new instance or do deployment process and everything, some kind of not. We have to wait. Anyway, if you have a question, just along the way, raise your hand or make some noise or attract my attention, it's OK. While we're waiting, I guess sometimes it can be so frustrating. All right. OK, let's try to do as I said, if this is running. Let's do it in a 2.2. Make the font be there. Sorry? Onmaker font being there. All right. Sorry, sorry. Yep, yep, yep. Let me try. Ah. Big enough. OK. Cool. All right. OK, we are hooked. So we, whoosh, it's OK. Let it be, oh no. All right. All right, seems our instance is ready. The most important thing when we prepare in this instance is this, if we want to use code deploy, we have to make sure that our instance have enough permission to do that. So a specific permission will be just this instance have to have enough permission to pull data from S3. That's it. S3 packet, no other permissions needed. All right. Our instance is fine. Then let's see our code base. All right. OK. OK. So we're using this. I've prepared some very, very simple applications. So oops. So this kind of Hello World application, so just for demo purposes, cannot expect too much. OK. This is to return the JSONs with message. Hello World, let's test it first. OK. Test, test, all right. What is it? So let me check. Let me try in my local host. Is it working fine? OK, cool. So this is too small. Sorry. Beep, beep, beep, beep, beep. Now, OK, this is what we add. What our simple application will do? What is it? OK. OK. Cool. OK, thank you, Baidu. So this is what we want to deploy this application. It's very simple. This JSON file to print Hello World. All right. So let's test. OK, never mind. All right. So it's already on my public repository here. That's it, OK. Oh, cell phone. OK, sorry, sorry. All right. That's all right, it's better. OK, test, test, are you hearing me now? Can you hear me? No problem? Yeah, I'm hearing you. All right. You can switch off. How to switch this off? OK, it's OK, fine. All right. Let's yell a little bit. All right, this is my public repository. So actually, this is all. Oh, so, oops, how to make it bigger. Beep, beep, beep, beep, beep, beep. All right. OK, so it's on my public repository. So what we are going to do is every time we merge or push something in the master, then we want to our pipeline somehow trigger and do the deployment in the end of the pipeline, right? So this is the spirits of the continuous deployment. So without any manual activities involved, right? For doing that, of course, first, we will need our deployer. We call code deploy. Let's prepare our code deploy. Oops, see. Applications are probably I'll just delete this and start it over again. What, how to delete this? The name application and it's here. All right. All right. So previously, I've spawned an instance. Let's see. In the tag, we have two tags. The one that we have to put more attention is to deployment group. This is, we can actually edit and put everything there, right? So we have a deployment group. Tag with the value is development. For example, this is our development environment. And let's get back to code deploy. Get started. Install. Skip all through, right? OK, application will be Alex here, demo. It's on on-premise, easy to our on-premises. We have two options there. There's a AWS Lambda, which we are going to use today. And deployment group. OK. So this is the difference between the application name and deployment group name was the application name is actually the code base. So this is what were our code source and everything. And the deployment group name could be our environment. Like, for example, development staging, production, and everything. So this is actually all the informant came from the same code base, right? So for example, let's see. Deployment group name Alex here, death, right? OK, this is another cool part is in place deployment. It means we deploy the application into our predefined easy to instance. So there is no any easy to spawn or creations or things. So actually, it's deployed to the existing easy to. While blue-green deployment is the first step what code deploy we do is just they will copy the entire infrastructure into the new one. So the current running infrastructure we'll access, we'll handle traffic is to be and all the deployment happened in this new informant. So after everything is OK, after this, we make sure that this is OK. Run well, there is no error, of course, and everything. Then the code deploy will switch the traffic from the old to the new. And after wait for a while, if we make sure that everything is OK, then the old infrastructure will be teared down. This is very cool. It's completely zero town time, all right? So this is how we choose to which easy to instances we want to deploy our applications. So this is our text. Actually, if you remember, we want to deploy to all the instances easy to instances with the tag name of the tag. The key is development group, and the value is development. So this code deploy will search into our entire easy to instances with the we have this tag, right? OK, hope so. So it detects there is one active instances. It's very cool. This is our instances. This is our instance. And this is only if we activate a load balancing, which we don't have it. And this is just a strategy. So for example, we have two or three instances there. Actually, code deploy offers by default, there are three methods like, oh, we want to deploy all at once, like three of our instances, all deployed at once, with consequences with the town time, because we do all the same time, all half. If we have four, there's two switch off and deployment. So this is not zero town time. Or one by one. This will take more time. Because imagine if we have 10 or 20 instances they have, they will deploy one by one. Because we just have one instances, there is no much difference. All right. Oh, this is code deploy, right? OK, that's a great one. OK, cool. We have now a code deploy active. And how to trigger the deployment? Actually, this code deploy could be pull the data from either S3 bucket or GitHub. But unfortunately, tonight we don't have enough time to demo it one by one. So let's just go to the code pipeline and put this code deploy inside that, right? OK. All right. Oh, no pipeline. Let's get started. Let's create it straight away. Elixir pipeline, right? Source will be GitHub. OK, so I want to connect to my GitHub account. Elixir demo, right? It's auto-detects, very cool. OK, OK. So we want to, after we change this push or merge into my master branch, it will trigger this pipeline, right? So use MAU to check where the code is changed. Build, no build at a time. This is the moment of truth, OK. Diplom provider, we choose AWS code deploy, right? I believe SMM is auto-detect. So our deployment group, OK, cool. Oops, right? Rule name, it actually, if we just create a rule, it will automatically create the rule who needed by this code pipeline, right? Next step, we'll take a look a little bit. OK, seems good. OK, that's great. That's just great. All right, actually, this is OK. So how to trigger this pipeline? Actually, there are two ways for now. First is, like we said earlier, we push something or we put something or merge something into our master branch. Or the second is just to push this release change button. But enough because here, we just pull for source change through. After we create this pipeline, so it's automatically triggered somehow. This is very cool. So let's wait, actually, right? OK, actually, this is auto-naming. So actually, we can eventually change this stage name later. OK, now it looks like our deployment. OK, this deployment will fail because, OK, will fail because for code deploy to be deployed to all the easy-to-instances, we need some code. First, we need this app. Too small, OK. We have to put this script in our root directory of our applications. So code deploy will know the sequence how what you should do in our target easy-to-instances. So first, let's just put this file into our root directory. New file, right? Save, up, right? And for install, we will use this script install. So this is a very simple way to get Elixir dependency and do all necessary installments. Let's just put in the proper, what is it? Install, all right? And based on these scripts, we need to start. OK, this is how we start our Elixir applications. Instead of we type it manually, I've prepared it. All right. I know we probably have several ways to install two-start applications, but let's use this way. What is it? .knit is at the moment, save, install, upspec, good, script, good, all right, script install start. OK, cool. Seems that we have all of the knit. OK, let's see if it's failed. Now, we have all the knit. Let's do good, .knit.m, code deploy, great, all right, come on. OK, let's see if this automatically trigger our pipeline and successfully deploy it, it's coming, it's coming, please, OK, not yet, oh, not yet. Come on. Come on. Any questions? While we're waiting, maybe take a couple of seconds now. How do you guys deploy your application to AWS? Using this kind of solutions or so? No, no productions, usage? And where is the confirmation? OK, OK, meanwhile, it's automatic trigger. Oh, thank god. OK, code formation is actually designed for another purpose, like a proficient, solve the entire, our infrastructure in AWS. So it's not, I don't know if we can, actually, we can integrate between this pipeline and code formations. But yes, we have to check. But for my, I think it will be, it will take a little bit more times to prepare the entire new spawn, the new EC2 instances and do all deployment and make sure all things are OK. And I think you'll do all the applications. I don't know, but still, we have to check. This is for my assumptions. It will probably take a bit longer time. All right, yeah, OK. To the previous person. OK, OK. Good idea, sir. Yes, thank you very much. OK, so, OK. How often do you set up this code pipeline? How often? How often? You mean how often I update this pipeline? How often do you set up the pipeline? Actually, we set it once and we can do it forever. Oops, another failure. Why? We can check. All right, so, few logs. Cool. You have to remove this first. So, let's see your app. OK, that's, yeah. This is what I'm talking to you previously, that code pipeline and code deploy. Another cool thing is the logs are if failures happen, we can just know immediately. And actually, we know what happened, all right? So, we can just push retry. Let's check on the deployment part. OK, so it's in progress. The deployment, wow, it's all instances. OK, it's kind of succeed. All right, let's check. All right, it's kind of our deployment success. Let's see. OK, moment of truth. Let's see. It's there on our EC2 instances. OK, OK, actually, do not celebrate yet, but we want to test our theory if we change something in our code base and we push it to the master branch and it automatically triggers the pipeline. Otherwise, this will be useless, right? OK, so let's change something. It's somewhere around here and here. OK, so we can name, for example, oh, what is it? Let's say this Singapore, all right? OK, we add one key value in our JSON. And OK, oops, OK, push. Oh, all right, without any manual interventions, it must be automatically triggered the pipeline and deployment, hopefully. All right, let's get back to our pipeline. Takes a couple of seconds. OK, any other questions? Yes, please, sir. So what happens now is that I want to check whether during the deployment everything is compiled from the scratch that all the dependencies are get once again or whether it reduces the previous directories. So I'll ask you because, for example, in my case, if I delete the dependencies in the new directory and I want to deploy everything, it takes around 10 minutes, right? Because it means to fetch all the checks, all the dependencies in compile and compile the application. Why if I use the dependencies from the previous deployment to take around 10 minutes, I want to check how it works in this case? OK, thank you. It's perfect questions. Actually, for this kind of solutions, we do a lot of things again and over again. It's easy to instances. However, we can, OK. So basically, it used the previous dependency and all the file necessary. But of course, we can do something like mix clean or something. So if actually we try, we make a change on our code base, which involving this kind of dependency and everything, it will try to reinstall the dependency accordingly. So actually, by default, it will use the previous dependencies. Otherwise, we install things or we change things related to these dependencies. So let's take a couple of minutes. So please.   Let's try. Let's see if it already changed. Oh, thank god. OK, that's actually it. So now, every time we make change and push it in master branch, it's automatically triggered the pipeline and do the necessary deployment. And I don't know, it's already 8 plus. We now finish. Actually, we can take the Q&A while I'm working and wait for another, right? Actually, one extra. How about you guys? You want to keep it going? Oh, is it waiting? OK, here. Actually, it's OK, it's OK. Let's not make him waiting. Actually, I have two more topics. One is how to inject the configurations by the code build. And the second will be the AWS Lambda to send notifications and do some other tasks. But unfortunately, our time is not sufficient. So I'm just sorry. But of course, we can have another discussion and a lot of conversation after this stage. And of course, you can find me in any other channel with andika.coordinator.com. You can, it's in Pasadonesa, I'm sorry. But in the bottom of this page, I have all of my identity. So ping me any time. I have my email. My email is andika. This is very simple. And anika.coordinator.com. So we can start cool discussions and conversation over there. And I think we have your LinkedIn profile. Super cool. Yes, LinkedIn will be fine. And thank you. Yeah, cool. Thank you very much. We just break break with you for five minutes. Really? All right. So we've got our speaker who's going to speak about.


Serious trouble for Macketze Macketze is allegedly facing legal woes after she pulled a no-show at an event in her home province of Limpopo. According to the promoters, they paid her label, on Mike R-70,000 for her to perform but end up not showing at the all-white party in December 2021. Pale The Events management lawyers served Macketze's record label with an R-159,000 letter of demand in May. Macketze has not said anything regarding this allegation but many of her fans want her to make things clear. Recently, Macketze had to cancel some of her shows following an injury she sustained while performing on stage. The 26-year-old is famous for some of her music and her energetic performances on stage. Macketze took to her Facebook to share the news of how she bumped her head onto a speaker while performing.


The dot product is a very specific instance of what's known as an inner product. The inner product emerges from a mathematician's inclination to generalize a concept. There are several useful features of the dot product that we want to preserve when we generalize it, and so we define an inner product as follows. Let V be a vector space where U, V, and W are all vectors in V. Suppose this inner product, U, V, assigns each pair of vectors U and V to a scalar and satisfies the following properties. Again, a quick observation, there are only so many symbols, and here we're recycling these symbols that we use to indicate vectors, but this time what we mean by this set of symbols is the inner product of the vectors U and V. So what does the inner product do? First of all, we want the inner product of any vector with itself to be zero if and only if the vector is itself the zero vector. Next, we want the inner product of any vector with itself to be greater than or equal to zero for all vectors. These first two requirements are usually bundled as a single requirement. Next, we want the inner product of U and V to be the conjugate of the inner product of V and U. Fourth, we want the inner product of U with the vector sum V plus W to be the sum of the inner product of U and V with the inner product of U and W. Finally, for any scalar C, the inner product of U and the scalar multiple C, V is going to be C times the inner product of U and V. If all of these things hold, then the function U, V is an inner product and our vector space V is an inner product space. So we claimed that the inner product is a generalization of the dot product, but let's make sure that the dot product is actually an inner product. So we'll check our first two requirements. If I have some vector V, then the dot product of V with itself is going to be V1 squared plus V2 squared and so on, and that is always going to be greater than or equal to zero. Moreover, the only way this can possibly ever be zero is for all of the VIs to be zero. And that's only true for the zero vector. So that satisfies our first two requirements. Next, we want to prove that the inner product of U and V is going to be the conjugate of the inner product of V and U. And one way we can do this is we can start with the inner product of U and V and see if we can build a bridge to the conjugate of the inner product of V and U. So we can write down the dot product of U and V and we'll work a step back from the end and write down the conjugate of the dot product of V and U. Since these are vectors in Rn, all of our components are going to be real numbers and so the conjugate of a sum of products of real numbers is just going to be the same sum of the products of real numbers. And again, since the components are real numbers, I know that the product of two real numbers is commutative. So V1, U1 is the same as U1, V1, U2, V2 is the same as V2, U2, and so on. And so I have a bridge from the inner product of U and V to the conjugate of the inner product of V and U. The next thing I want to show is that the inner product of U with the sum V plus W is the same as the inner product of U and V plus the inner product of U and W. So again, we'll set down our starting point, we'll set down our ending point, and try to work towards the middle. So I know the vector U has components U1 through Un and the vector V plus W has components V1 plus W1, V2 plus W2, and so on to Vn plus Wn. And when I form the dot product, I will find the sum of the component-wise products. And we'll expand that out a little bit. On the other hand, let's take a step backwards from our ending point. This inner product of U and V, since we're working with the dot product, is going to be the sum of the component-wise products of U and V. And likewise, the inner product of U and W will be the sum of the component-wise products of U and W. And we see that if we rearrange the terms in our sum, we'll get the previous line. And that connects the starting point to the ending point, and we can conclude that the dot product satisfies the fourth of the requirements necessary to be an inner product. And finally, we'll check that last requirement that the inner product of U with a scalar multiple of the second factor is the scalar multiple of the inner product of U and V. So I'll set down my starting point, set down my ending point, and see if I can work towards the middle. So the dot product of U with a scalar multiple of V is going to be C U1V1 plus C U2V2 and so on. Meanwhile, C times the inner product of U and V, that's our dot product, is going to be C times U1V1 plus U2V2 and so on. And if we expand, we'll see the two are the same. So the dot product satisfies all of the requirements for being an inner product, and that means our vectors in Rn with the dot product form an inner product space. So who cares? Well, one of the advantages to inner product spaces is that we can determine quite a bit of information from a very small amount. For example, suppose V is an inner product space, and I know one inner product, namely the inner product of the vector A and the vector B. Given this single inner product, can I find other inner products? Since V is an inner product space, we know the inner product of C U and V is equal to... Well, actually, we don't know what happens when the first vector is multiplied by a scalar. So all that we know is the inner product of C U and V is the inner product of C U and V. And because of this, we have to try something else. So because V is an inner product space, we know that the inner product of U and V is the conjugate of the inner product of V and U. And so that tells me that the inner product of B and A is the conjugate of the inner product of A and B. Well I know the inner product of A and B, it's five, and the conjugate of five is just five, and so that means I know the inner product of B and A. And the natural question to ask is, is this relevant? And the important answer is, who knows? But it's a fact, and facts are often useful. Looking at our question, we want to know something about the inner product of 3A. And now that A is the second component of our inner product, we can actually find this using our last rule. So I can find the inner product of B with 3A is 3 times the inner product of B with A. And so that tells me that that inner product is 3 times 5 is equal to 15. And we now have the right vectors B and 3A, but they're in the wrong places. But one of the properties of an inner product is that if we switch the order, we'll get the conjugate. And so this means that the inner product of 3A and B is the conjugate of the inner product of B and 3A. And we already know what that is. And that gives us the inner product of 3A and B.


I am welcome to the session. Let us discuss the following question. The question says, where function f from x to y be an invertible function? Show that f has unique inverse. First of all, let us understand that if we are given a function f from a to b, such that it is invertible, then there exists a function g from b to a, such that g of f is equal to identity function on set a, and f of g is equal to identity function on set b, then j is called the inverse of f and is denoted by f inverse. This is the key idea to solve the given question. Let us now start the solution. We are given that function f from x to y is an invertible function. Now since f is an invertible function, so there exists a function g from y to x, such that g of f is equal to identity function on x for all x belonging to set x, f of g y is equal to identity function on y for all y belonging to set y. Also, f is one-one and all-two functions, since it is invertible. So, it must be one-one and all-two functions. So, we can write function f one-one. Let us assume that g-one and g-two are two inverses of f. f is the function f, and for all y belonging to set y, f for g and y is equal to identity function on y is equal to f for g-two y. We know function f is one-one and all-two functions, so the identity function of y is unique for g-one function f, which is possible only when g-one y is equal to g-two y. So, therefore, we get, it implies, function f has unique inverse. This completes the session. Hope you understood the session. Take care and goodbye.


I'm Dr Paul Belford and I'm the Chief Executive of the Claude Paris Archaeological Trust. We are one of four Welsh archaeological trusts who together provide a complete archaeological service across the whole country. We operate regionally and have a national perspective and we have deep roots in our local communities. Today I'll talk about how our regional archaeology services have worked for nearly 50 years in Wales. I'll highlight our successes and identify some of the challenges we face in the future. First the Welsh archaeological trusts are charities. This means we are independent organisations that are independently regulated. This status gives us flexibility that's not always enjoyed by public sector colleagues and unlike private sector bodies we must deliver public benefit.  It contains a huge diversity of landscapes, people and identities. Welsh language is central to cultural identity in North and West Wales, but different Welsh identities are equally powerful in Anglophone South East Wales. Population density also varies widely across different parts of the country. This affects demand and delivery of services. Finally the Welsh archaeological trusts are resilient. We have survived several significant structural shifts, devolution, local authority reorganisation and of course historic environment legislation. The Welsh trusts provide a comprehensive package of archaeological services for the people of Wales. This includes advice, investigation, management and education. The historic environment record in Wales is a statutory obligation placed on Welsh ministers and the Welsh HER is publicly accessible online through the Archwilio portal. Using the HER the Welsh archaeological trusts provide planning advice to all 25 local authorities in Wales including the three national parks. Across Wales we process around 9,000 applications every year although the intensity of this work varies across our regions and this work supports the Welsh Government's sustainable development goals. Our regional heritage management teams help conserve and protect schedule monuments, designated landscapes and non-designated assets and we deliver strategic input here too such as recent agri-environment and climate change policy work. We also provide advice and support to the public and local groups and on top of this we deliver a wide range of bespoke education and outreach programmes. Finally there is our commercial contracting work which builds skills expertise and knowledge to further enhance archaeological understanding in Wales and beyond. The work of the Welsh archaeological trusts is delivered using a combination of public and private funding. The HER planning advice and heritage management projects are publicly funded. About two-thirds of this comes from CADU Welsh Government with a balance from service agreements with local authorities and other public bodies and our commercial income supports our charitable objects of education and public benefit too. We work in close cooperation, collaboration and partnership with our government funded counterparts with other NGOs and with international project partners. The continuous development, evolution and refinement of the Welsh system is a huge achievement but the future is not without some challenges. Funding is an obvious worry although the level of CADU grant aid has been maintained in recent years its value has been eroded by inflation. Demand for our services is always increasing and so we need to work harder to develop new income streams. Another issue is demographics expertise and experience is vested in a small number of individuals. The trusts themselves are also relatively small organisations and this has the potential to limit individual career opportunities and can sometimes act as a deterrent innovation. A related issue is trying to make archaeology in Wales align better with the identities and values of future generations. Finally there is the question of advocacy. The four trusts are certainly champions for archaeology in Wales but our voices could be louder beyond Wales and when addressing global issues like climate change beyond archaeology too. I spoke earlier about the resilience of the Welsh archaeological trusts and this resilience is as much about adaptability and flexibility in the face of changing circumstances as it is about consistency and excellence. I feel confident that the system in Wales will continue to survive and prosper in the future. We've already begun to think about how to address some of the challenges we face whilst continuing to deliver excellent public service and public benefit. The Welsh model provides superb value for the public purse and indeed adds significant value across a wide range of activities. Wales sets a good example which could be adopted or adapted for other parts of the UK. Thank you for listening and please don't hesitate to get in touch if you want to find out more.


Have a dream of a life of romantic adventure? Want to get away from it all? We offer you escape. Escape, designed to free you from the four walls of today for a half hour of high adventure. We're on a remote island in the war-torn Pacific. A paradise of tropic splendor. Where sounds of battle are far behind. While walking slowly toward you, our arms stretched out to you is the most beautiful girl in the world whose embrace could mean your death. Listen now, as Escape brings you Millard Kaufman's exciting story, The Island. The problem was, what could I do with Robert Lacey? Do you happen to have a dream book handy with all the charts and categories precisely arranged in alphabetical order? Well in it you'll find a dream for loneliness about girls in soft summery dresses. You'll find a dream for hunger, two-pound steak perhaps smothered all over with lamb chops. There are dreams for the traveler of the hometown far away and long ago. But find me a dream of a place you've never seen. A place that doesn't exist. A wake or asleep that was Lacey's dream. Corporal Robert Lacey, second battalion, fourth Marines.  May it was, 1945, in a little wood down Okinawa. I guess I got it. Where are we anyhow? A couple of three mines behind Jack Blines. Oh, fine. You worry too much, pal. Even for a guy on his first patrol. Well, I've been thinking of it as my last. Relax like me and you'll live forever. Nothing. Just a screamin', Mimi. Got a kind of a tail adjustment that cuffs the wind sort of screams. Jack uses it to scare us. Well, they sure succeeded. You scare easy, pal. Sure. Sure, I'm a pushover for that shreklikite stuff. Shreklikite? What kind of jive is that? Well, it means terror, fightfulness. German-German's got a whole arsenal of terror weapons. Japs have got a few themselves. What do you say we sack in, huh? Sack in here? As good as the next place.  It's three miles behind Jack Blines. You've got no chance of gettin' back tonight.  First watcher, I'm gonna sack in. You goin' to sleep? I just sit here and dream a while. You're sure pickin' a fine time for it. Hey, did I ever tell you about my island? Yeah, yeah, you told me. You must've told me 50 or 60 times in the past month. All right, so I'll tell you again. Now, this island, it's a sort of a special place, you see. There's no rain, no jungle rot, no war. Just a quiet, cozy spot where a man can lay down under a banyan tree and live off the fat of the land. Oh, there is no such place. Now, on this island, a man would never go hungry. All you gotta do is fish a little with the natives.  Not like a nips. And all the dames are beautiful. You know, something Lacey, you read to me. I'm fixin' to go as soon as I can find it. I'm never going back stateside. I'm gonna lay down under that little banyan tree, and I'm gonna rest for a while. I let him rave on. What else could I do? Argue with him? There I was, three miles deep in enemy lines with a stranger. His eyes narrowed in a thousand-yard stare. It's a rush of words like a nervous twitch. He raved on about a place that doesn't exist with big men and beautiful women. And then I found myself listening, sort of hypnotized. And I learned something about corporal Lacey and what combat wariness means. He'd foraged too long among the rotten, bomb-scarred pebbles of the Pacific. He'd seen too much death, too many crack-ups. He was himself half-cracked and slightly dead, barely held together by the taut and twisted wires of his dream. So what could I do? Argue with him? There'll be cattle on the island, too. I'm gonna find me a beautiful girl and... Yeah, yeah, I'm listening. Look, Taburi out there coming toward us. Where? Four. Three men in them. They're heading right for us. What's the matter? You flip or something? They're not chaps. The men are too big. It's funny, the woman with them, though. Maybe his eyes were better than mine, but how could I trust that brain he has all fasted with dreaming?  The dame is beautiful. Only I'd listened to Lacey then. If only I'd known, but chaps are no chaps. I was taking no chances. I raised my rifle and...  I'm gonna see if she's hurt bad. Come on. Lacey, Lacey, don't go. You know the chaps. Don't worry about me. Let go of me. Listen, you get yourself killed. Not me, Taburi. I live to spit in your grave. Now, let go of me. I just hope you know what you're doing. I don't want to get involved in any of your cockamani dreams, you know. Dreams? It's no dream, Taburi. You'll find out. Okay, Lacey, so where is she? It's funny. She must be around here somewhere. Maybe... Wait a minute. What's that? It came from over there. Come on. There she is. She's scared of us. Lady? It's all right, lady. Why?  She's bluffing.  You see, we got bandages, adhesive tape, penicillin. She don't get what you're talking about. She gets the idea. That's right, lady. This won't hurt a bit. You just got nicked a little, that's all. Is it just a flesh wound? Oh, she trusts you. Yeah, she trusts me more than you do. Didn't I tell you she was beautiful? You told me a lot of things. How about the men? She was with the big men.  Not Japs. And a pig's eye, not Japs. There you see. Well, then what were they? They were... Who are you? What are you? What's your name? Name, please go away. Now you've scared her again. Look, Taki, it's all right. Everything's going to be all right. You just come with us, huh? No. I go home. Must go home. So go home. Scram, lady. Lose yourself. Oh, no, you don't. Let her go. Let her go back to her rice paddy, will you? You still don't catch Tabore. She ain't from Okanama. She's from that island I was telling you about. She must see. She must see. She must see. She must see. She must see. She must see. She must see. All right, then what are you doing here? Do not know. The Japanese bring us in canoe. She's crazier than you are. Who ever...  Taki, where is your island, huh? Where is Yagachi? In...in China Sea. Yeah? A half day from Okinawa by canoe. Canoe. Well, what's it like, Taki, huh? Well, what's your island like? Listen, never mind the island. Let's find that canoe. Come on, don't you see where the canoe... we can get back to our lines by water. Yeah, I think you got something there. You...Taki, can you find the canoe? I think I can. Come on, let's go. She led us on through the wood. A lopsided moon came up in its rays, filled it through the clouds and down through the jagged trees. In the moonlight, she was like one of those porcelain figurines, delicate with a peculiar tint to her skin, unlike anything I'd ever seen before. It was like the shade of waxed ivory, ancient ivory. Her hair was long and black, drawn tight over her head. She was straight and slim. She walked with dignity. She was beautiful. As beautiful as a dream, Lacey's dream. But dreams don't come true, not like this, yet... Here she was just the way he described. And the three men. And the island that... I couldn't figure it out because just then I didn't have time. Lacey, listen to that. Yeah, come on. Taki led us down a slope to the water. There were canoes. And leaning against a prowl were two sentries. While they were safe, they thought three miles behind their lines snug as two bugs in a mosquito net. So safe they didn't know what hit them. Who knew, huh? All right, push off, Taburi. You take your bow. Sit down, Tom. You know what I think? I think we're going to make it. Okay, Taburi. We can take it easy now. I'm not taking it easy. It'll cross our perimeter. How are you going to tell at night? Maybe you think I got neon signs, huh? Well, maybe we'll see a landmark or something. Distances can fool you at night. We're labelled to paddle right into a platoon of nips. Okay, what do we do, Lacey? We'll stand by the morning and head for our convoy. We'll ride a shore in style in an LST. I don't know. I think it'll be better if we... Whatever you think you're outvoted, two stripes to one. What, are you pulling rank, Corporal? Well, why not, Knucklehead? This ship's got one skipper, and I'm it. Oh, you're like a... Now, look, if I want any stuff out of you, I'll knock it out of you. Now, morning, you don't follow up this detail. So what was I going to do? Argu with him? Start a private firefight in the middle of the China Sea? I was getting a little combat worry myself, but Lacey, he was all charged up Lying on the narrow deck of the canoe, I could hear Lacey, and the more I heard, the more confused I got. It's not like other islands. Is it, Taki? It's different, Yokashi. I wish I could tell you how. I know. It's pretty, huh? It's very pretty, but... Is the fishing good? Good. And we have pigs. Cows? Good cows. I knew it, I knew it. Cows and pigs. And Lacey, getting all this hopped up about them. Well, that was the last thing I remembered. I guess I fell asleep, and then suddenly it was daylight. Tabori! Hey, look, Tabori! What? Look over there, what do you see, huh? An island? Just an island? Not just an island? That's my island! What's so special about it? Well, look at it! It's surrounded by mist, just like I said. Oh, tell it to the troops. Let me get back to Okinawa. Look, Tabori, stand by for a ram. We ain't going back to Okinawa. Ain't no way to... I don't want any more trouble from you, Tabori. Well, then don't make any, or I'll... Hey, what? Looking for your rifle? Well, don't bother, because I got it right here. Now you get for it. You're crazy! Go on, move, Tabori. You're flirting with a purple heart. All right, now lean on that paddle. That's right. We're heading for Yagachi. The coral beach at Yagachi about four hours later. It was a lovely island with terraced hills and patches of tilled soil checkering the greenery. Well, Sien's believing that, Tabori. I wouldn't believe it. So close to Okinawa. Where are your people, Taki? Wrong way over here. But you must not come. You go back now. Oh, no, I'm sticking around. How about you, Tabori? I came this far. I'll sweat it out just for last.  What do you mean? Well, that's just a figure of speech, Taki. Let's go. So there I was caught up in Lacy's dream when all the time I should have taken off at high port for Okinawa. I should have known better, but I didn't, and what you don't know can hurt you. Plenty. Hey, look at that cat, Tabori. I could eat her down in the hooves.  The trail snaked upward. There were scarlet flowers and lilies in the swordgrass. All very nice, I suppose, but I was looking for people, the big men of Lacy's dream, the girls all as lovely as the girl beside us. I was tense with expectancy at each bend in the trail, but Lacy's tensions had all vanished. He lost them because he had found Taki. Robert Bracey. No, Taki. My name's Lacy. Now, try it once more. Lacy Taki. L, I can... This is a lily.   Tabori, I'm going to slug you. You're so funny, Lacy, when you're mad. Well, you laugh nice, Taki. It is the first time in five years. It is the first time I am happy. Maybe you were waiting for me to make you happy, like I was waiting for you. What do you mean, Lacy? Well, I... I mean it... Well, here. This is for you. Why you give me flower? Why, Taki? You don't know... I don't know how to say... You do not know me. I know you. I've been dreaming about you for two years. I knew I'd find you. Never forget what you say. I'll never let you forget. Lacy. Lacy, honey. L, I can love. We walked on together up the trail. A tall marine and a slim girl with the ivory skin with a flower in her hand. Now, and then she'd look at the flower and then she'd look at Lacy in a pained expression and cloud her face as though she didn't understand. I didn't either, but I had to find out. Man, what a climb.  Don't worry about me. I'll get by. Well, we got it, Lick. There's the summit. If you... you got it. Down there... Hey, look. Look at him. Be my people. I told you they were big men. How can you tell from this distance? Well, look how broad they are.  Hey, listen. Well, maybe it's what you call a ceremony or something, huh? It is. Well, maybe it's for us. I bet they know we're coming. No, it's for the dead. What happened, you suppose? A war? The war's not here.   It's just gotta happen sooner or later. Never heard it so well, Poit. Why don't you drop dead to boring? Let's go, Taki. Down the mountainside, down to a cape that jutted into the Pacific like a gnarled finger of doom. Far away we saw a village. We headed toward it through a sunless gorge. At the far end was a thatched hut. Looks like it's empty.  You wait here. I'll come back soon with Hetman. He speaks English good. The boring? You, uh...  No, I see. I just want one good look at your big men and beautiful women and their native habitat. And I'm off for Okinawa. He still won't prove, huh? There's something strange about this place. I wanna know what it is. It's just different, like I said. You're all fouled up, Lacy, in a dream. I'm not sure what it's all about, but I gotta find out or it'll drive me crazy the rest of my life. You mean crazy like me? I didn't say that. Since we left Okinawa, you've been giving me a bad time. Let's mute you. Now you just call me crazy. I know what I said. I know what you think. I know what you'll do once you get back to Okinawa. You'll tell the MPs I went over the hill and you'll tell them where I am, they'll come after me. You are crazy.   Lacy, Lacy, stop kiddin' around with that rifle. I ain't kiddin'.  But first, you're gonna see I was right.   Now get back in that corner. Keep him out shut. You the head man? I suppose you could call me that. His name, Hiroshi. What can I do for you? I, uh, stay here with Taki. I'm afraid you cannot. Well, I'll work my way. That is not the point. You cannot... Look, I don't want no arguments out of you. You cannot stay. Well, why? She is a leper. She's so beautiful. Yes, I know my son. But in three years, five years... I tried to tell you, but I did not know how. And then I could not, even if I wanted to, wanted it to one more hour, one more minute. They stood there facing each other. The tall marine and the girl with the ivory skin with the flower still in her hand, the flower already beginning to wilt. Good. Thank you. For the flower. I, I never... Hiroshi, what's this all about? It is quite simple. Two nights ago, the Japanese came to the leper colony. They took more than half my patients to Okinawa, headed toward the American lines. Why? To disrupt your advance. There was no chance of contagion, but, well, my patients do not all look as lovely as Taki. Oh, I see. Shreklikite. Exactly. A weapon of terror. Yeah. Tobori? Yeah, Lacey. I, I guess we better move on. You, you ready, pal? Yeah. It's a long road back to Okinawa. For me, the road back is longer than that.


Welcome everyone. This is the Docs office hours. It's the 21st of September. Let's look at the proposed agenda and Here you'll see Topics so Jonathan, we put you first new migration GitHub issues then October fast and Google season of Docs anything else we should add to the list maybe if I Saw the last meeting we have many people who are working on it. So Maybe if you want to update us about some topics Then a worker and all like a vacation Impact or work okay, I'm not sure what you're referencing so Say you say it again Jonathan for me. So you're thinking status reports or oh I guess I make the top case. I saw another He do it's not our passion. So, oh No, that's okay. That's that's great. No problem. So but we can certainly we can certainly discuss status reports and Project progress because there are a number of topics there like Jenkins 2.2 49.1 Has had many different things going on Jenkins infrastructure HTTPS or update center Etc. So they're quite a number of those. Yeah, I can include those. Oh, that's the wrong place I even put it in the wrong wrong entry. Sorry just a minute But the notes not in history and let's put the notes in current So what I was what I wanted to be sure we went through Jonathan was the topic here The new issues you've created and how we can use those for our work on Hacktoberfest That was for me. That's the crucial one for this particular meeting today Okay We're now at Hacktoberfest is now on the Jumbotron Are you okay if we look at the new issues you've submitted and talk through them, etc? No problem and that started. Okay, great. You scared me when you said no problem, I'm like It's a normal phrase here man before it is it's a perfectly good one, but you hung on the no and scared me for three seconds Sorry Made the wrong intonation, I know yeah a Reminder to wait until the sentence is finished before you freak out All right, so let's let's take a look at And we're now at 89 and I believe Jonathan that these are yes, okay great, so let's How about we take a look at one of them? Is there any one of these that you'd like to Choose as the one that we look at so you can talk us through the technique you're using now No, it's all of them. It's following the same template. So, okay, really similar All right, go ahead Okay, so as I speak in our and Previous meeting and we are using this template to create the issues So the first part the station and central information We have the page to migrate with the link and the hot thing needs to do So for example the proposal or in this case, it's only redirects for the Indicated explanation. So this issue is about the migrates for a plug-in Yeah, I searched the the plug-in that I indicate the Correspondent station So you did that's perfect you did the research and that says yeah This this page with its rather long and verbose name is In fact the plug-in documentation and here is the plug-in page Exactly. So if I compare the content, so if you click on the Go back to issue, please and click on the link in the destination proposal plugins about Jenkins. Yeah, yeah, click on it Okay. Yeah, so this one Yeah, is right here. Yeah. Oh, yeah So it's the same as plug-in. I follow the link on the issue So on the old page original page So and this is just to that exact location very good. Okay So clearly this was intended to be the documentation for that that plug-in and There is not an awful lot of content there. Good. So And the first time now the first the next step now it's but for simple way new tag and good to first I guess And so this yeah, so this one so what it needs is a redirect and the does the teacher I don't remember if the tutorial shows people how to do the redirect. I think it does I Think to I can't remember right now Okay. Alright, so that's So we need to redirect page to migrate and then the answer is redirect to the destination That's elegant and I agree with you. This is a good first issue Good first issue. Yeah Is there a reason to do redirect and not just put the move the content Well, that's that's what's actually quite important here the content here is This block and that's it. Yeah all the rest it says move to the read me and Is a bunch of comments and questions from users that we would not put into the documentation So so the content has already moved actually and that's in this case. Yeah Right and even better the content here is much much more useful than that wiki page Okay, now now something that this particular task could benefit from but not Not in the context of Jenkins.io But this particular plug-in would benefit by having the transformation made to use its to deliver its documentation from GitHub and Then this content that we see here on the page Would appear on the plug-ins Jenkins.io page. It doesn't right now So this this page could be dramatically better automatically if we made if they would merge one change to the palm file on This on this particular plug-in and I suspect there's already a pull request proposing that change No, don't see it. Okay Just my concern is I know that HTML proofer that we use for Cloudby stocks Will not follow a redirect So so an x ref to that page that gets redirected will fail if it checks hmm Well, but so so because I don't think we have much choice there We may not know redirect because wiki is read-only. So this top page Let's go there this page. Whoops This page right here the one that opens when I click the top link is in fact Only readable no one can write to it right therefore. It's not going to help anyone Find the information. They have to search and get lucky that they find this hyperlink, right? Yeah, you are yeah, we need to remember we are using redirect because This page is one of the most accessed page Followed it. So it's important to do the red red right right good point. Yeah, so we've got this We've got this Report that tells us which pages are are actively used and this is this is now up in the list good Yeah Near for one thousandth All right Also a side question So we're updating the terminology in Jenkins now even though the software has not yet been updated We're doing we're doing both right so we intend to both update the documentation and update the software to to address The first yeah first two are the hotspots right now, right and but the others yes We are also doing the other two also Yeah, after our previous meeting I had the section about technologies just as a reminder Yeah Very good I'm concerned that it's going to be confusing if the documentation says I'm doing a controller and the software says it's a master But it may be we just need to live with that Yeah, the the the usual problem has been that the software makes the change and the documentation never catches up I would love for once to have the problem the documentation is ahead of the software Indeed Okay, the following sections about the tutorial and additional information why it's important to migrate the page and then the next day the last one it's about the redirect so when the know we Migrate the content that we need to redirect so I guess it's everything a Voluntary needed to work on Right now now for this specific one because it's just a redirect I think it's safe for me to delete the additional information. Isn't it? Oh It's a it's a it's on you Yeah, I just put there because it's the template. It's the same for every issue So all we should do the we'll have the same Yeah, and my thought was for someone who's seeing this as a first time as the first thing they see I Worry that that they won't Understand that this is just quite a play well, I Get a Concept the way I work on it. So for example when I start to work with you. I Ask questions. I Research I read I watch the previous videos section So if the people need to work and do the same they think they can figure out What that what this test can say to him So I guess if they follow a test to work on it Jenkins No clear for you No way. No, I think it's clear to me. I'm just concerned. I'm not sure I want that level of tests for these first time Particularly because we're coming up in about 10 days We've got Octoberfest starting and for there are many folks many people there who would who will help us and Then quickly drop off because they did something just for the fun of it And we want to get as good results from them as we can so I think I'm I think I'm gonna go ahead and Well so I But For example, what do you right now? You are doing a 3h on the previous issue. I have That's so I guess I guess it's the important work to do. So for example, I go there and Do the research and create the issue and the next step and you read it and mark for example It's good the issue edit on as to remove the The content to your gas is not important for first you show the answer. I I guess it's a good best to follow And I think that makes sense You I you have a good point Jonathan that that having two of us involved in thinking about it We'll probably give us even better than that if we do only just one person working it Exactly, okay That because this the benefit they get a video That shows them. Hey, here's here's how you do this and they they've got very specific instructions Immediately that say you need to do the following redirect Good, okay. Yeah, so for example, maybe for this kind of issue It's a Good thing a recorder a new video explain how to do exactly the redirection Not for example, because this video Relinquished about a page week Migration not only about the redirect Right, right. So it might be better if we had a segment which was just How do you do? How do you do a redirect? For example, go to the next the last session that the issue last session go down, please go go back Oops Yeah, so okay, so yeah, so about the redirection Process it's Instructions are and a redirection be set up by sending PR for this file. Just take a previous samples best samples To me it was enough to this phrase to work maybe for a new commerce maybe not maybe Right help more Well, and in particular because at least for me the syntax of that vhost.conf file Was not immediately obvious. What it's what does it mean? Right and reading through where to put it and why was was more complicated. So yeah, good point Yeah, excellent. That's that's great. Thank you, Jonathan So do we want do we want to take a look at any of the other issues? Were there any in this new set that you submitted that? Oh Just pick one Okay, how about troubleshooting articles page? Oh, okay. This is another one where it's just a redirect Yeah Good, okay, very good Well, well that's encouraging because you've done you've done the triage work to review this original page You as a human being looked at it and said look this makes more sense to go here than here Exactly. So we say a Big start I guess that that is that's wonderful. Okay, so that so then the the task there really is Visit those and say yes, these are good first issues and then label them and if I remember correctly You don't you we haven't yet granted you permission to assign that label So that that assures us a two-step process for now and as we get better at this We may grant you permissions to allow you to do good first issue as well Okay That but I like I like the two-step process. I think that's very healthy for us Excellent, so please any important content and just to go Just wait a moment. Let me find this Go back. Please. Yeah, just a moment at the vote foundation guarantee Okay please click on the migration display information about the nodes Yes, there's one. Okay, so first sample This kind of page we have a problem because the destination The destination click on it Okay, just a minute. Let me get rid of some yes and hold tabs All right now Okay, this one so the destination Yeah, the destination link. Oh, yeah, so this Okay, go ahead This one is is sort of a hotspot for Megan for me Because this should probably now be named well So this one's talking about all sorts of things agent related and there's very little here But there's an awful lot that we need to know about agents And so yeah, so this one is a poster child of a wiki page that has lots of very good Oh, no, this one doesn't have this one's not terribly useful. Okay this this target page needs lots of information on it and has Nothing particularly useful for a typical user this this script Monitor and restart offline agents is is a very specialized unique thing not Not the thing that needs to tell us here are this different types of agents and here's when you use an ephemeral agent and so Exactly, and there is another point to for simple go back to issues. It's just the issues that Okay issues. Did I do this? Oh issues. Yeah, this okay, so you want to go back to issues go back. Yeah Go down more or more Go down or there is another. Yeah Just as let me find them Try to Post initialization script Yeah, that's all there is a problem. I did to go The destination proposal didn't go in the same place. I wish I will correct them But it's about the APR. I send it about the Jenkins agent So the PR wasn't approval yet, and we need to migrate content to there. Oh Okay, I can't I can't be great because the PR was not approved Right. So this one this one this issue has a dependency that we need to get the existing PR in Before this one will make any sense. Okay, so that's that one There's a great way to to say that something like this This PR this issue Needs PR number and Then we we find it See post initialization I have I'll have to let me go look for it really quickly here because what it really needs is exactly the issue that The PR that you've submitted we need to get it merged so that it's there as a precondition So is it yeah, yes, you put the outer as Jonathan Yeah, get your other get Jay Yeah, okay, so so Agents architecture Yeah All right, so 35 11 and that's that's a merged before Work starts on this issue Because you've given us a place to put things with the agent architecture page, but we need to get that merged exactly So elegant all I get asked for some modifications. I already sense that Great, so it's waiting for the next review. Yeah, and all I won't be able to review He's probably offline for at least another week or two potentially a month With other things, but I should be able to help with it So that's that's a that's a good one that knowing that it's we've got another issue that is pending on it Good very good Okay, so this one this one for me. I would not flag as good first issue because it has this dependency Exactly. All right. Yes about issues. Can you go to work targets? I Yeah, click on it With conversion and Google don't okay, so go to issue maker the third Okay, so I I put on the yellow Data pages. I can figure out the nation and sometimes because it's a a development content development guy, so for example So get one. Yes. This is a nice sample Jenkins is hanging on hanging Let's see what you said Jenkins is hanging. I missed that There it is good, okay here this way. All right click click on the page It's a strange concept to be on the documentation so it's so It's not so objective Yes, well and and isn't this isn't this really this one for me is Is a subset of the information. How do you report a bug? Because I think if Jenkins hangs it's a bug and so I would propose that this page Should be redirected to how to report a bug. I Agree, I think the same because it's not so it's not objective content Right, right. Yeah, it is it is very subjective. Yeah, so Yeah, okay, so you can put in front of only redirects. I will create the issue. Oh Okay, great. Okay. Thanks. Let's see. So it's subset of How to report a bug okay, and And that it may be that the content is not in how to report a bug but my guess is This information is probably well, let's see when was it last yeah, here we go look created in 2013 So The page is seven years old and this class of failure Hasn't hasn't been common with Jenkins for a very long time This type of failure. Okay. Good. I put some comments on the Sheets for simple go to Logger configuration Logger configuration. Okay. Good. All right So go to the page to first simple Mike's out here. It's because we already have a page speaking about longer but It's a old page old content too. So I don't know if Logger on Jenkins is handler in the same way. For example, Woodson.model and Java.u2.login Maybe it's not more Useful for new person on Jenkins. How was it can figure out that? And oddly enough, I found this one for me has been well at least I've used the loggers Just very recently and found them be very helpful. But let me let me do a quick Quick show it because I thought we had this that information already on Loggers Yeah, we do. Okay. Good. So so this has a We've got a page already that I think we could redirect that to immediately and this page is actually current So that's a that's a very good one You just found a page that we should redirect and and I think I don't see anything in this page Well, I So, Hannah, I thought I speak about the developer content It's because the last part of us so You can have a link that see Java.login overview. So if you saw that link It's about developer.login and not Jenkins.login property Clicking on it. I guess it's going to Oracle page Right and it's going to a really old last update 2001 so a really long ago How you do logging and I think I think by now they may have replaced it with eight Although I don't know if they've rewrote this. Oh they did so so if we wanted to point someone to To the Oracle docs, but really the the cool thing about the Jenkins logger is it makes the Java logging facilities trivially available for a user of Jenkins. So that the new versions You can set. Okay. So just to redirect you. It's a good issue First issue. Yeah. Yeah, and that one I think would be a good first issue So now in the way to identify that you used only redirects Yeah, that's it. So template two will be prepared to change Very good. So we need to see all yellow meetings. Maybe another time to not take our meeting time What do you'll get? Yeah, but this is this is these are great candidates for for for example The one that you highlighted here in yellow static analysis in pipeline static analysis is quite a popular topic And so having having that correctly redirect will probably be a big help And point it to the warnings ng plug-in Rather than to to this Because I think yeah, in fact, this is early documentation of Warnings ng this is but it's frozen in time now. And so the current documentation for it Is is on the plug-in page There is a plug-in. So after this tactic a pipeline But there's so what there is is there's a plug in there. Yeah, so there is a plug-in page. Oh, I didn't know for Let's see Jenkins Jenkins warnings ng so this plug-in Has has the Has documentation and introductory video All sorts of of great guidance for users and this is the redirect For that page. So yeah, this is this is a really good one that you detected because It should be only a redirect Because much better information is now available from the plug-in site than from that wiki page The next one i'm getting out of memory. Maybe say obviously content tools about the developer I get Yeah, see and I would have thought this would yeah, so this was I would think this is an a An administrator topic, but that we would have had something like this already In on jankins.io. That's Let's see You don't Interesting. Okay. So so that that one looks like See I would have expected it to be somewhere like system administration And be a page here On on diagnosing Jenkins. In fact Meg, didn't you tell me that that there are presentations at devops world on diagnosing Jenkins? There is yes Yeah, but we don't have a topic about diagnosis. So for example, we have another a talk Talk about a common way horse on Jenkins or how handling errors or something like that We didn't we don't have one kind of the destination to put You're you're correct. This would be brand new material. You're absolutely right. This this doesn't seem to exist as As the information that's here is not anywhere on Jenkins.io that I can see So What did you think about a new page a new section or nothing? Yeah, so I I would propose you know, let's tell me what you think I would I would propose making it a A new a new page new page in sysadmin section and something like Now I need to edit it Out of Or maybe we should just call it diagnosing Jenkins errors Oh common errors Even better. Yes. Very good common errors or maybe it's just diagnosing errors Yeah It's a good one because because really it's That gives us a place to put. Hey, what about out of memory? What about of what about?  What about Oh, things got slow and I need to find out why Right. What's your stack trace and how do you read it and right? Yeah, exactly Yeah It's not the directory. Hey, let's do that with Jenkins. It's Java but We will help you to use Jenkins better Right, right exactly. Yeah, and we do have a session on diagnosing diagnosing memory leaks Um, and we have another one on called demystifying debugging screw logging Oh, and now now. Okay. That's a that's an interesting one I think we would be we could be potentially allowed to embed the video recordings of those into these pages I hadn't I haven't checked with cloudbies to see if they're willing to allow us to After the conference is complete embed videos of those into jenkins.io pages, but Maybe let's let me put that as an action item for me to see because We've we've done it before with with video recordings of other conferences Are we allowed to embed? Uh Conference so dev ops world Session recordings In the docs I'm also hoping to put them into the cloudbies training but um Having being able to actually do that mark knows the sad story so And I I see no problem if it shows up in both places actually Right. Yeah, that's great. Okay In the next case if it's not allowed to embed that we can solve the video and replicate samples Like our property content Right Just get the idea from video Create anyone Absolutely Yeah, if someone wanted to To rephrase just that for me feels like a lot of work that I'd rather not do if and And it doesn't help promote their videos either So they may they may actually like that. Hey, we placed it there. So it helps promote the fact that they did this video The one slight problem. I don't know is that They may mention cloudbies in a way that will make the community unhappy Right, so we'd have to review the video to be sure. Yeah and I uh I've seen the demystifying Through logging video and it's excellent But I'm I think that they've done it's pretty much stuff that's applicable to both the open source and cloud bci, but I think there may be more Uh There's definitely something where it talks about a feature you get in cloud bci that's not in there It might aggravate the community. I don't know right valid point Okay Okay, yeah now So go ahead. There is the issue you open. Uh, it's a good sample Building Jenkins is a 100 percent about development So just go there. It's about the check out of the source from Jenkins um and build with maybe Move on So This kind of content that needs to be integrated to Jenkins.io or not because it's the same inside the Readme.jng file And and we've got a maybe only a direct for this page Yeah, so we've got well, we've got um, let's see do we have it Compiling Jenkins from source I thought we had that already on Okay, I don't see it immediately. All right, so that's I thought we had in so for instance We've got a tutorial for plugin development But this is not Jenkins core. This is a plugin that depends on Jenkins core. Good point. Good point. Maybe a new patient tutorial That that could be or or let's see. I thought there was yeah, and I don't see one here that talks about How to build Jenkins so there's Jenkins CLI So so this so it looks to me like this information is not there And and it might justify either a tutorial A second tutorial, which is how to do how to this is this is the more common one, right? Hey plugins most people don't have to build Jenkins But if you want to build Jenkins we might put it maybe in a how-to guide or Yeah, that Yeah, so I suspect we may want to do a how-to guide how to build Jenkins from source Or how do you have Is it possible to break up that how-to guides into subsections? I I think it must be I mean you see the the leading keyword and code I know that I would say it looks obvious I'm thinking the old rule of seven and I'm thinking that list is already getting hard to read Well, and I know I wonder this this concept of how-to guides May actually be generated From data in the documentation That says it's a how-to guide about this topic. And so this this thing might in fact Be already something we couldn't in the in the ruby code that generates this page Do follow your guidance mag and Create Substance or headings And then place the topics under the heading so extensibility security views et cetera Yeah, so basically the developer and documentation so maybe there is no big problem It's so program actually developers can't read I don't I don't mean they're illiterate. I mean that most developers way of getting information is not reading And uh, yeah, yeah, I know With our life mag I've spent most of my career documenting for Developers and I I've actually done tests. I can put any crap at all in a paragraph and ask them to review it And they will see tables. They will see lists. They will see charts And and I can put some absurdity in a paragraph and almost nobody will catch it Yes Yes, I'm sorry. I uh, I guess I didn't turn on uh the microphone. I would Email saying that this meeting had been cancelled. That is why I just Oh, oh, so so that was that I we had cancelled last week's meeting It should still be my apologies. Maybe I made a calendaring error And didn't have it on this week's but I We're definitely back on I'll forward it to you again, blad We only we cancelled last week because nobody came so we didn't cancel before nobody came Well, I think wasn't last week a national holiday. No, it wasn't two weeks ago two weeks ago. Yeah And the last week was in you and I sat and right so so I'll I'll forward you another invite blad that way you've got it Mm-hmm. Thank you well, uh mark we were out Almost in the last minutes of the meeting you you want to go to the next stop Let's do I think we made good progress there Yeah, and the progress we made is a good lead in to the next topic. So let's take it just briefly Okay, so beginning october 1 We have hacktoberfest and hacktoberfest Is an invitation for people to engage with open source communities The incentive is if you contribute four pull requests To an open source community during between october 1 and october 31 Digital ocean will send you a t-shirt That says that you contributed to hacktoberfest And if you wish they'll also Instead of sending you a t-shirt they'll donate by planting trees instead so you can choose either The page here describes places where you can contribute I just submitted the update on this page this morning And boldly included the jankin's website what we're talking about here As one of the featured projects with our list of good first issues As candidates that they should be considering working on But we've only got 11 good first issues and last year I think we we we completed 10 or 15 ish good first issues in the first week or so So so we'll be we should look for more good first issues For for the for the jankins.io website So that was and that was my intent there. We may also do a And a recording session or a media session To highlight how to contribute to documentation Like we did last year. We might we might want to A sometime in october say here's how you can help with jankin's documentation So you will record another video about the how to contribute That's that's what I was thinking is and I thought this time it might be fun Jonathan to have you be one of the presenters and vlad be one of the presenters and me be a presenter And we could rotate through the three of us Saying hey look here's here's this piece of it and here's this piece Maybe jonathan we have you show how to do a redirect or you know Each of us chooses a piece and we consider doing it sometime during october Okay, you'd say good points So we result two issues with the I think Right So vlad would you be willing to be part of that kind of a meet-up to be one of the presenters and I'd be one and jonathan Yes, I would be glad And also tomorrow i'm presenting on the meet-up which was organized by cdf and i'm going to talk about jankins and Well going to engage new commerce to jankins and saying that jankins is well Not so complex as some people think and so you can easily start contributing to jankins This is kind of the message that I would like to deliver And i'm going to talk about Jenkins and docker and also say how it is possible using official jank docker image to Call docker agents inside Um Pipelines declarative pipelines something like this something Tutorial like Which we Still have I guess on jankins.io is still pointing to outdated Jenkins CI blue ocean docker image right We had intention of substituting it with With official docker image So i'm going to present it tomorrow see how is the feedback and In case if they will be no Well Somebody will accept it. Well in this case I may consider updating tutorial as well Excellent. Thank you. That's great If we want first issues have we i'm back to this um terminology change thing Which is way heavy It seems to me that it's Appropriate points and quote unquote because I we need to define that We need a quick page that talks about the the terminology change being made and why it's being made and this sort of stuff and To translate it so that people You know There's going to be a point of time where people are going to have to deal with the fact that some of the docs are going to Say master and some are going to say controllers And you know and this sort of thing and then That's a ton of that's good first. All I have to do is understand how to you know Do a github branch and edit ascii doc and You know, that would be wonderful stuff to have a whole bunch of people You know, we we had enough participation We might be able to uh get get that largely done in octoberfest You know if if we get a large number of sort of naive users who just want to get into it Yeah, so that's that's that's very good That one would need that might lobby us towards the technique that templated issue report that That jonathan has been doing Of we maybe we put that as one of our topics actually converting terminology well, uh but a issue just A converting terminology may be caused to us some problems for for example, uh, imagine if a thousand of pages just receiving prs. We have a dq 200 just update the terminology terms without a review the content and update the content I think yeah Yes, so I was assuming that in order to not get 10,000 tiny little pull requests that just change the word once But we did that we would break we would assign things by sections in the issue list So here I was going to do a quick check just to see I think if we do a get rep minus l master We can identify some pretty quick. Okay, so blogs have actually been converted already as a section and What else has I believe change logs have in in this one, but for instance administration as a section has not been touched and Managing as a section hasn't been touched. So those might be reasonable issues as a group to say convert all of the pipeline references to master convert all of the system administration to master Yeah, it's better. I guess it's better by section I mean for instance security Let's do Minus and even that Yeah, so so the security advisories. I know have been converted because Daniel Beck did those very early but others for instance google summer of code We've got lots of places we could do those conversions and do them as as blocks or groups I guess it's a good issue first good first issue Yes, just a replace content I think so. Yeah, I would think that And and it's a section so it's not so large that they risk being overwhelmed by They made a change and their review and the change they made was flawed and the reviewers rejected it and threw the hopeful request away Right, whereas if you're just on a single section A change is probably a mistake is relatively small And can be corrected without without destroying the entire pull request Right. Okay. So uh for the next meeting Can you open these issues up about sex because you have the content with you Yeah, are you noticing that you have the next bullet issue is terminology change issues also Oh here, let's put it. Yeah, so so let's put it there. Good. So let's do it that way We could put it in the in our video in our meetup session and Proposed sections. So if here's Jonathan, I think this is what you were requesting, right? Is could we just have some proposed sections for it and Put those into the list and then generate issues for them Exactly because as I said today 1st of October it's Next hour Maybe two weeks to register all week. All right Yeah, so so let's say let's go with Actually, and I can do this. I think I can do this separately. I don't need to make everybody here Wait for it. Let me just From mark So I'll just prep them. I'll get it into this document so that we don't go over our ending time and and then Jonathan if you or if you and glad together can can combine to create good first proposed issues for those That would be great or create one and notify me and I I can look at it and we can talk about hey How's the phrasing on this and once we get an initial one, of course then we create many of them Mark have we noted the the thing to look at the how-to the list of how-to guides and see if that could be broken up by into Can everybody know the rule of seven or is that common parlance, but Better format Really, it's raising GitHub issue To better format How-to guides Yeah need headings or some other Form of organization Instead of one giant list Meg do you want to be the one to raise to raise that github issue? I guess I could I've never let me see if I can do that I have not done that, but I should be able to right You absolutely should be able to you just click the green new issue button over there. Okay And it will take you through what type of issue it is and you can describe it. Okay. I will do that Excellent Oh Mark, I just wanted to mention continue this terminology stuff which Meg mentioned I noticed that he was searching for master Uh, my understanding master is kind of outdated term which is going to be replaced by controller Correct. That's right And it looks like there is There are not many sections where controller is mentioned in all the communication. So there will be a lot of kind of change right Yeah, exactly glad you you you got it precisely that That we know we've got many many places where those two transformations have to be made And then we have a white list and black list as well But those need uh, they those have a more involved fix They actually need phrasing work usually to improve the phrasing Any anything else We need to change we need to explain the terminology switch someplace Where is the right place to do that in this set? Do we want it at the beginning of each of these guides? Yeah, I would I would I would prefer personally just a hyperlink because long term we hope people will just Stop being confused by it, right? Right. It's it's an interim piece that needs to go away Right, and we've got uh, if we look for for instance, let's look for Let's pick this and we'll look for a different one. It's Slide omics, I think Nope slide omics No, okay. I've got to find Alex's blog post Alex url blog post Terminology Here we go slide omics Nope, it wasn't him who we've ever Jenkins terminology, sorry Just a minute and on Jenkins terminology up. Oh, this is from markey jackson, right? Okay So so this one is the the introduction to it and then Then it continues with There are actually there's a more recent post on oh, this one is the most recent This one is june where where it was updated and then alex url posted one on the continuous delivery foundation about The next next level of this it is no, no, that's not it. Sorry. I can't find it here trivially That's we can work. It's something to think about as we're looking at stuff during the week Right. Absolutely. And then where do we put links and what do they look like is still an issue, but Yeah, because what I'm thinking is for if people are going to try to make um For pr's that get them a t-shirt That a lot of people might at the beginning do one of these and then be able to go on move on and do something a little More interesting Right, right. That's that's a good point. If your first experience was oh, yeah, that was pretty simple You may say oh, I'll try more of more something more interesting or more challenging And we do include that the instructions about doing this explain the special circle in hell for anybody who does a global search and replace No, although that's a that should probably be in the in the Template that we are intentionally working through these section at a time because It's too much. It's we will reject pull requests that propose to change everything. They're just too large We think it needs more thought. Yes, although, but will you see that and how I did that? I'm not You would see each line that got changed, but if you know, you've got to read them You've got to read them, but to somebody who's never been through these as we all know this somebody who's never been through this as a reader It's like not a big deal. You just do a global search and replace and you're done and Yeah, we we've all We've all seen that one right But uh, yeah Okay, I think we've covered the topics. We've covered a number of topics I propose we call it done for today and we can we can Carry this forward. We'll meet again in a week outstanding Thanks, everybody Thank you. Thank you everybody. Have a good. Oh, um, I won't be here next week All right minutes afterwards. Sorry Jewish holidays All the best to you make enjoy. Thank you. I intend to Take care everybody


Happy birthday to you. Happy birthday to you. Happy birthday dear Michael. Happy birthday to you. Best birthday present ever is going to get solar. That's right guys. Today we're going down to AM Solar.  There was like four companies who agreed to provide all of the solar, which makes my life a lot easier and better. It makes my life happy because it's going to be fun to wire it. It's going to be great top of line stuff.  I don't know if you guys met him before, but super rad guy and was the catalyst of putting all this stuff together with these different companies. So we have four ZAMP 170 panels and then we have a whole packing list full of stuff. So do you want to explain what we got here? Yeah, so basically we broke the system down into several components. Solar charging, battery bank, alternator charging, AC input and AC output and DC output. And we try and keep everything organized so you can see which parts go with what. Some of the major components are the solar panels, which were provided by ZAMP. They're 170 watt panels. Victron provided a 2000 volt amp inverter charger system and it's very generous of them. They also provided the solar charge controller and several other smaller components. And Lifeline is contributing two 400 amp hour AGM batteries. So starting from the roof, we got your four panels there. They go into the combiner box here, then to a master switch, then to the charge controller, then to a breaker. We've got your lugs, your heat shrink, your cable management, mounts for the panels, sealant to seal the mounting feet and the combiner box. So that's everything you need there. Next box, let's see, we're going to do battery bank. Putting two 6 volt batteries in parallel, I mean sorry, in series. So you've got your cables to do all that and to connect to this shunt here. This is the battery cable, this thick stuff right here. You also get contributed by Victron, a battery monitor that talks to your phone via Bluetooth. I had that one on the last one and those are amazing because you could just open the phone and see where you are. So easy to use with the Bluetooth communication too. Instead of having to remember which sequence of buttons you push, you just talk to it on your phone like you do any other thing. And if you guys remember when I was in Texas, I had a little issue with the alternator. How I knew that was I checked the battery monitor and I noticed I wasn't getting a current from the battery combiner. So I went back to O'Reilly, swapped out an alternator and parking lot and didn't get stranded on the side of the road. So for a couple hundred bucks, it's highly worth it. And this is the DC output section of your kit. A lot of people don't do this, but I find it's really helpful adding a battery protect, which is a small device that interrupts the flow of current from your battery to your DC loads. And it keeps you from over-discharging your battery. So here it is right here. This one's a Victron BP65. And we also applied a switch to turn off all your loads. Six position DC fuse block, cables, breaker to keep your current from getting too high. And just to make it easy for you, we threw in an outlet, which is dual USB and normal 12 volt. So that takes up one of the positions. You still have five other positions for bands and lights or whatever you want on there. I'm really excited for this device here, this piece of equipment. If you guys remember, I stopped by here frantically because I accidentally drained my AGM battery past 12-2 or 50%. And so I had to buy another $700-800 in batteries. So that is not some of the stuff you get what you pay for. When you get quality stuff like this, it will save you in the end. Dean, the schoolie, is dealing with some issues right now because he used some products that weren't top-notch. And he might actually have to call you and order like three grand and stuff. Like it's not fun to repurchase stuff. I'm sure you have some stories about that too. Yeah, I've killed batteries. I've killed charge. Yeah, it's not fun. The money you spend is worth it when you're doing solar. Don't buy the cheap stuff. That badge had actually a panel with one of the cells burnt out. Same thing with Dean, the schoolie had one that burnt out. And yeah, I mean you can definitely go the cheap route, but just know that something might fry and mess up everything just because of one small cheap part. Yeah, we warranty our system so we try to make everything as idiot-proof as possible. Like we don't let people screw it up. Well, I'm sure if there was a way in the beginning I could have screwed it up. Alright, let's check out this alternator charging kit. So the key piece in this is the Victron Syrix battery combiner. This allows for 230 amps to flow from your starter battery or alternator to your house battery. And it comes with a system which is a boost.  Yep, those come in handy. The last one I had was a 50 amp, so this bigger one is going to be even better. And for sure I'm going to have to upgrade my alternator because that's a lot of current. That's more than my alternator puts out.   This is like class A type stuff here. I'm just excited to wire it because it's all like, you don't have to figure out what parts you need. It's like all right here and it's just, yeah, there's not much thought that goes into it. By the way, AM Solar is doing schooly kits. So if you want to see what quality components they're using, head on over to the website. Are we still doing the Jax 5 and the Jax 10? Yep, those promotions are about... 5 or 10% off for you guys on everything under the sun, right? All your products? Yeah, the Jax 5 works on everything. The Jax 10 works on select components. Cool. So the AC input, your vehicle's going to be able to charge on shore power on a standard 15 or 30 amp connection. Going over all this, we include the inlet. We're going to have a shore power cord for you. This is the device that regulates the MultiPlus inverter from Victron. You've got your sub panels. You've got your breakers, your fuses, communication cables, master switch. We even gave you an AC outlet so you could see how everything works for one of the circuits and then you could just add whatever circuits you want with easily sourced, you know, residential wiring. Excellent. Looks like you've got everything you need.  Dude, hi 5. Thank you for helping me set this up. Huge shout out to Victron. You guys are amazing. Lifeline, thank you for the batteries. Zamp, thank you for the panels. And I don't know, did I miss anything? AM Solar. AM Solar, I think you guys are ready. If you guys are curious how a proper school-y system kit, what it looks like, what you should have in your kit, head on over to the site. There's also diagrams and things like that. Happy birthday. Yeah, this is... You get to play with all this stuff. I get to fire all this stuff. It's very exciting. Sweet. So, we're actually using the handicap door. Yeah, we'll take the whole pallet, dude. We are transferring batteries. Oh, you can lift that thing up, too. Yeah, there you go. We're transferring batteries. We've got all the gear in here. This is insane. I feel so blessed to be the recipient of so much high-quality stuff. So, yeah, these are 116 pounds each. Look at that. So, these are 6 volt, 400 amp-hour batteries. So, thank you, Lifeline. Thank you, Victron. Thank you, Zamp and thank you, AM Solar. Holy moly. Wow, this is unreal.  How much do these things weigh? 120 a piece? These things literally weigh as much as me. Alright, let's fire away. Let's get this thing lifted, huh? Nice. Oh, like a chair. I'll take the stairs.  We just filled up the bus with so much stuff. Unbelievable. I am blown away by the generosity of everyone, and those are massive batteries, dude. They weigh more than meat, no they don't. They're probably 30 pounds less than me. Yeah, that's crazy. So, I guess what happened was, Victron saw the video that we did when I installed a battery monitor and then got a hold of the guys here. And almost the same time I was selling my bus, I received an email saying, hey, you know, we're thinking about doing some stuff with this and that.  Oh, no way, let's do something together. So, this is how it all happened. Serendipity is all I can say. We got cruise control in this bad boy. Alright, so on the topic of quality components, I perhaps mentioned my buddy Dean had some issues, the schoolie with his solar system, Mitch over at AM Solar was on the phone with him for 45 minutes. And also, Dean sent me a message and was like, oh my god, thank you so much. He's awesome, he was on the phone with me for almost an hour, blah, blah, blah. And I didn't know details. Mitch just texted me from AM Solar and he said, it turns out his cheap charge controller not only blew up his stereo, was cooking his batteries at 16 volts. For everybody who doesn't know, that's more voltage than batteries require. And apparently, Dean put his head down next to the batteries and they were hissing, hissing. Like some kind of serpentine slippery snake, like sssss. So anyways, just another example of what can happen when you get the cheap stuff. But also what can happen when you get good things from good people. They'll get on the phone with you and troubleshoot for like an hour. So yeah, high quality and great customer support. And I'm super curious what Dean is going to do now. Oh, holy guacamole. You know what I mean? Hey, birthday boy! How's it going? We made it back, back of the pad, got all the stuff inside. Man, I'm exhausted from driving. Are you exhausted? I'm just happy there's no leaks or anything. The thing ran like a champ. It did. It did? Yeah, we took it down, it was like two hours each way. So maybe 200 miles plus today. Tomorrow, we're going to work on the plates. We are going to get new headlights. I'm going to pick them up on the organ side, because they were like 300 bucks or 250 bucks, I forget. I saved on sales tax, state sales tax. So it's worth it. So we're going to get rid of these hideous, terrible, dangerous headlights. And we're going to replace them, yet again, with the GE Nighthawk, which are fantastic. No, that's not sponsored, but I'm choosing to get them again because they are phenomenal. And the price went down, I think, 100 bucks from the previous time I bought them about a year and a half ago. So that's great. And then otherwise, we're going to load this thing up full of stuff and get ready to leave in two days. So tomorrow is basically our last day before we hit the road. Head east through Idaho, Montana, hot springs, mountains, maybe glacier, maybe not, because it might be full of snow. It's probably still full of snow. And then on up into Canada. So thanks for watching. We'll see you guys on the next video.