הי, מי name איזה יציגן ברור, טכניקל מרקטינג מיננגר עד גיטלאב. In this video, I will focus on the value you can get from the combination of SCM, CI, and code review delivered as a single application. SCM, CI, CD, and code review are key tools developers use daily to develop applications. In many organizations, those tools come from different vendors, and they use integrations and plugins to make them work together. While those integration usually works, it is not the ideal way to deliver software today, as you will need to switch between tools, make multiple logins, and spend more time to get what you need. This makes it harder to communicate and collaborate. In addition, you need to maintain multiple tools, plugins, and integrations. GitLab solves this challenge as it has a leading SCM and leading CI, CD, both in one application out of the box. In this demo, I will walk you through the seamless flow developers experiencing with GitLab. Once the developer pushes his code to the server, he can immediately see his branches, commits, and the pipeline status for each commit. The developer goal is to push his code to the master branch as soon as possible. Merging code to the master branch is done via the quality and compliance gate. In GitLab, we call this gate a merge request. In this gate, developers request to merge their feature branches into the master branch. To pass this step successfully, several things should be reviewed. They will need to ensure the new code doesn't break anything, doesn't introduce new bugs or any security or compliance risks, and this is why the CI pipeline runs many tests and scans. It would be helpful if reports from all tests and scans will be accessible to developers in one place so they will be able to get all the info they need easily. In GitLab, the merge request is the single source of truth for that. Information such as pipeline status, test results, security, and compliance scans will appear in the merge request. A review app is a live instance made of the developer's branch. This helps to visually review the proposed change. Once they checked all tests and scans, the next step will be a code review. They can open the code review module by clicking the changes tab. This module enables an efficient review process. And this leads me to the pipeline management module. From the merge request, developers can open the pipelines related to their merge request by clicking this link. This saves time as they don't have to context-witch to another application. The other way back also works. From the pipeline graph, they can click to the commit that triggered it or to the merge request that it is related to it. Having the info all together makes it easy to get an overall analysis of how we are doing. The Value Stream Analytics module shows how much time it took to complete each stage of the development lifecycle. With this analytics, you can identify the slowest stages, improve them, and shorten your time to value. Remember, it sounds obvious, but having everything you need available at all times makes for more efficient work. Stay tuned and see you again at my next demos.


Good afternoon and a very warm welcome to this edition of the Thijsig Talks. We are broadcasting again live from the pre-building in the vibrant and lively Spoorzone. Our team of today consists of my co-host, Pieter Spronk, and our technical support team Maarten, Priscila and Florence. And my name is Mirjam Siesling. We are very proud and honored to stage two speakers today, Marijn and Boris. And Pieter will introduce them properly later. Now without further ado, over to Pieter to introduce our first speaker. Pieter, the floor is yours. Thank you, Mirjam. First speaker is Marijn van Wijnaldum, he's an assistant professor at CSEI in the field of computational psychiatry. He previously was the head of the social rodent lab at Heinrich Heine University of Düsseldorf, where he investigated social decision making in animals, probably very small animals. Already during that time, he specialized on recording electrophysiological signals. That was one of those tough words, you know. And also the intriguing ultrasonic vocalizations that are transmitted between rodents during social interaction. He is also famous because he's the founder and president of the Dutch brain Olympiad, the Stichting Herzen Olympiade Nederland, from 2018 onwards. In his current research, he focused on the analysis of neural activity of bigger animals, namely humans, to predict their social behavior. Today he will talk about data science in healthcare. And you have the floor. Thank you very much. Thank you, Pieter and Mirjam, for the introduction. And yes, there is a connotation between rodents, especially rats and healthcare. Of course, it's usually a bad one, but I won't be talking about rats in this talk. Rather, the talk is about data science applications to clinical data, so data collected by GPs or by hospitals in this case. So just to briefly illustrate the thinking behind this field of work, is that the promise of using AI in the healthcare field is that we can arrive at precision medicine, namely identifying which segment of the population works.  A particular list of treatments is worked down in a particular order, based on what generally works for most people and possibly also by their side effect profile. And if the most preferred option doesn't work for a particular person, you just go down the list until you get to one that hopefully does work. Now, ideally, we would rather predict which treatments, either medicine or maybe psychological treatment, for example, psychiatric treatment, which treatment would work for which person so that they don't have to wait for the appropriate healthcare that long. And in order to make those predictions, we would arrive at, look to AI models, machine learning to make those predictions and just arrive at the personalized healthcare. So there's opportunities for AI in healthcare. There's usually large amounts of data that are stored in hospitals and other care facilities. Some of it is well structured, for example, imaging data like CT or MRI scans. There's also the international classification of diseases that provides a taxonomy, sort of this very clear, which patient suffers from which condition.  So trying to figure out which patient is most in need of particular care. And this can be implemented in decision support systems so that you can maximize the benefit of care with limited resources, like staff, but maybe also technical resources. Now, there's also a lot of challenges, of course. A lot of the expert knowledge by clinicians is actually hidden, so not immediately present in tabular data. It might be hidden in unstructured clinical reports or in a translation that has been made by the clinician to go from what they see at the bedside into a classification scheme that is then used in the machine or in the reporting. And that might not accurately capture data. There's possible data ambiguity when data has been entered later in the day, maybe with some hindsight bias. And usually it's pretty difficult to translate findings from one hospital to another, for example, unless the scanning apparatus, for example, is very well and the protocols are very well matched. But this is quite a challenge. So out of sample validity, it's difficult to achieve. I wanted to talk about the weak air collaboration started by EDZ Hospital and Tilburg University under the impact program, which basically brings together clinicians and AI researchers and others to identify areas for collaboration where data science and artificial intelligence might benefit clinical care. And this is one of the sub-fields that is highlighted under the weak air collaboration. What I will be talking about is two projects. One is using artificial intelligence to predict the outcome after trauma for weak air. And if there is still time and data-driven clustering of psychiatric symptoms in a population cohort that was collected in data that was collected by the Rotterdam study and Erasmus MC. And then we also have a shared project to discuss at the end of this talk, this session. So the first project is about predicting self-reported outcomes after trauma. So we know that the mortality after trauma incidents has dropped sharply with the advent of better care. But still there is a large difference in recovery profiles between individual patients. So how well they recover after trauma. And this is captured in subjective quality of life ratings that address both subjective physical revalidation and psychological recovery, basically. And the goal of this project would be to see if we can predict how well a certain patient recovers in order to provide them with information at the beginning of the trajectory, both to set expectations and maybe to inform some shared decision-making. So the data set that we use for this is the Brabant Injury Outcomes Survey and Study, a large data set that's used long-term data collection in collaboration with Trauma Registry and AZP. And there are five follow-up samples after the initial hospitalization in one of the medical centers in Brabant. The measures are self-reported scales, the Euro QOL five-dimension score and health utility index. And there is a depression and anxiety scale as well. On the slide below you can see the co-authors on this project, which is... So this is the description of the study. This is the protocol, so you can see here the five measuring moments, basically, when all of these questionnaires were taken from the participants. And all in all, about somewhere in the neighborhood of one-and-a-half to 2,000 records are retained across the five sampling points. Now, previous approaches looked at predicting the precise values of these self-reported scores with varying success. So R2, R-squared scores range between 36 and 48% overall. And this was on the physical indicators only. And in this approach, what we wanted to do is to see if we can actually detect patterns in all of these variables that were measured at the same time on different intervals after Trauma jointly. So by clustering on the longitudinal data that consists of four plus two outcome measures. So what we want to achieve is to have a limited number of clusters that we can then use as targets for prediction in a supervised machine learning approach to see if we can predict those from baseline measurements and demographic data. So for longitudinal clustering, we used a couple of methods. One of those is KML3D, an extension of K-means clustering. A Bayesian method called HD-classive, a Gaussian mixture model and also a longitudinal out-of-encoder. And here's an example of how to make a decision on what is the optimal number of clusters. So one of the ways to make sure you can do that is looking at the GAP statistic. But also the Bayesian information criterion, BIC, is sometimes used to pick and to this gap. So select the optimal number of clusters for your clustering solution. So here in the bottom, you can see the co-authors that contributed to this paper that has now been submitted. So here are some of the recovery profiles. We see an example here with six clusters and the scores range from, so they take into account a pre-injury baseline. And then you can see recovery over the six measurements, measurement moments basically, with quite some disparity between outcomes between cluster one with the best outcomes. So near complete recovery versus cluster six that has rather poor outcomes. On the right-hand side, we see a profile for HUD's anxiety scores. In this case, lower values are better. So on the left-hand side, we see a group that didn't have much anxiety but actually also reduced their anxiety after injury. And the top right-hand side is a group that had quite severe anxiety and actually didn't improve at all. Over the course of this measurement period. So there's quite some disparity there. So we use supervised classification for cluster membership. And so here are some some example to this ambiguous between different or make a selection between different kinds of models. We looked at models that have relatively high accuracy, also have a high clinical sensibleness and a lone majority baseline. So the groups, the clusters that we find need to be sort of evenly spaced across the sample so that the different clusters are actually meaningful. And especially this meaningfulness was also discussed with the help of clinical experts. So here we see visualization of our approach. We first selected plausible models based on criteria such as the gap statistic and BIC and then applied machine learning metrics for supervised classification. And then we asked the clinical experts whether they thought that the different clusters that came out were actually clinically sensible. What we mean by that is that today conform to known risk factors, for example, for known for subjective recovery profiles. For example, having a hip fracture is considered a really bad or a predictive for bad outcomes in comparison to those people that don't have hip fractures. Now we see here a visualization using these stochastic neighborhoods embeddings. This is kind of a bad example. We see that the clusters are not very well separated at all. And there are also solutions where this was much better. So clinical sensibleness is here explained a little bit more. We can see on the right hand side this arrow showing that between the different clusters, so the different rows in this table, we actually see the percentage of hip fracture change quite a lot. It's going from sort of the best outcomes in cluster one to the worst outcomes in cluster six. And it's also recapitulates an axis on age. For example, we can see that as well. So the mean age is increasing in cluster clusters and the number of comorbidities as well. So this clustering solution actually recapitulates a lot of the known risk factors and therefore was judged to be clinically sensible. So the conclusion here is that we can actually do longitudinal clustering of patients reported outcomes. And we can predict that with reasonable accuracy from initial hospitalization data that includes both demographic data, but also pre-injury health scores. The clinical assessment is essential for sensible clusters. So we really depend on our clinical partners here to pick the best models, basically. And now the challenge is to go towards implementation. So the goal would be to make a dashboard maybe for this visualization that can be used to set expectations for patient recovery, both by the patients and by the clinician, maybe discuss potential interventions if there are risk factors that are predicting a bad outcome. Maybe you want to start with psychological treatments or care or physical therapy early on. And we think that, for example, reporting the probability of ordered cluster membership would be a good way to do that. So give like a probabilistic forecast of where what the expected recovery profile would look like and then basically engage in a discussion with the patient what they think about that. The second project, if I am good for time, I will look at the moderator. Yes, we have another project which also looks at clustering. But in this case, low maternal clustering of psychiatric symptoms in population cohort. So this is based on the Rotterdam study, a project that is called ERGO as well, where a large neighborhood in Rotterdam was evaluated in many ways and there's a lot of information on that. So the problem with classification of psychiatric illness according to DSM is that usually it proceeds by scoring a number of symptoms that are being endorsed by the patient or by the clinician. But to arrive at a similar diagnosis, you can actually have quite disparate groups of symptoms that bring you to the same diagnosis, for example, of major depression. So there's a problem there that people who have the same sort of outcome, clinical outcome, can actually display rather different symptomatology and also symptoms can be shared by diagnosis. So we want to see what would happen if we just look at the population and see how those symptoms that are being assessed co-occur naturally and see if we can find clusters that are maybe a little bit different. So what we did is we took symptoms from three validated scales that have been assessed by the people looking at the Rotterdam study and performed hierarchical cluster analysis. And the summary of this is that actually those items from the different sub-skills do not cluster nicely in their own scale, but rather interleave and mix. So we can see that the similarity between cluster endorsement and between symptom endorsement actually transcends these questionnaire boundaries. So some of the anxiety, sub-skill items cluster better with depression items, etc. Now, when we did that, we arrived at these profiles for different participants. And actually, let me just go to the conclusion here is that we found that when we looked at patients who have a known diagnosis, that those diagnoses actually transcend the boundaries that we can find here generated by data-driven clusters. So the data-driven clusters basically looking at really the co-occurrence of these symptoms in the population really do not match nicely with the boundaries of traditional classification of diagnoses, basically. We can see that here, the red patients are those with anxiety and they are basically all over the place in this cluster space. So the conclusion here is that there might be a need for epidemiologically defined clinical sub-groups. So maybe there are sub-groups to be found in the anxiety and depression cluster that can be defined by their epidemiological profile. And they might actually respond to different treatments, for example. We don't know this, but this comes back to my first slide. Maybe there is a personalized treatment for those sub-groups as well. There are some open issues that we don't know that much about. One of those is, for example, whether these clusters are stable over time. And that relates to our second speaker also, maybe the analysis of these profiles as time series. So stay tuned for that. And I want to thank my collaborators at the hospital and at the Rotterdam Erasmus MC for collaborating here. Thank you. Thank you. No, let me ask a quick question, because I see there's nothing yet in the chat. But if anybody wants to ask a question, please raise your hand or type it in the chat and I will communicate it to Mareen. But I was looking at your first set of your first research. And what I see in there is a lot is about treatments. So you try to find the best treatment for people who start at a certain stage in an accident or in something where they need to be treated. But I also saw that, well, for many of them, so you have to see six clusters and these clusters, they start at a certain point and many of them start at different points. So that means that you can already early make a prediction on where this will go. But for some of them, that wasn't the case, they started at the same point, but only after the third measurement or so. They started to diverge and they turned into different clusters. So does that mean that they started already out with the wrong treatment or what was happening there? So how early can you make such a prediction where it goes and would it still be possible to make adaptations to it? Yeah. So what I didn't show here, but it's kind of interesting, the more data you take in, so that you could start in with the pre-injury data, but then also the first week and maybe the first month, the more data you take in, the better the prediction becomes, obviously. But then it's less useful because you're already down the trajectory somewhere. So the most interesting cases are those clusters where they start off at a similar, reduced recovery profile and then start to diverge, like you mentioned. And so in order to capture that divergence, we actually need to observe the entire time series here. So for a new patient, we don't have that data, but we do now have this supervised model that basically assigns a probability of this person ending up in a relatively well-recovery profile versus maybe a poorer recovery profile using only the data that's already available after the initial hospitalization. So it's in time basically to still make changes.


Insects are amazing animals, a new form of livestock that could be produced in a much more efficient way. Insects can also be an excellent source of micronutrients like iron and zinc. We rear the crickets and we provide them with two forms of iron that we can distinguish later on. We're going to feed that to volunteers and we're going to see how the iron is being taken up in their blood. If insects prove to be a sustainable source of protein plus micronutrients like iron and zinc then promoting insects as the sustainable protein sources of the future can re-provide people that have no access to meat with a new, sustainable source of both animal proteins as well as levels of iron and zinc to see that an idea that we came up with here in Wageningen University is being taken up and is spreading over the world is really a highlight that is amazing to see.


Hey there, today I'm going to go over adding your availability and requesting time off in the When I Work mobile app. Setting your availability is how you can let your manager know when you prefer to work and when you're unavailable to work. Request time off when you need to take time off work that can be paid, unpaid, sick, or holiday time off. Note that the ability to add availability preferences and request time off are based on your workplace settings, so you may have different options available. Let's get started. Go ahead and log in to the When I Work mobile app using your email and password. Tap more than tap availability. Tap the plus next to the date you want to set availability for. From here, choose you are unavailable to work or you prefer to work. Toggle all day on if the preference is all day or pick a set time if it's not. Toggle repeats on if you want the preference to repeat then set the cadence details. Finally, add a note that adds context to the availability preference. When you're all done, tap save to finish. Now if you want to take time off, tap time off request on the dashboard, then tap the plus. Select a type then enter the date range you need as well as a message you want to send to your manager. Tap done to send it. Note that your workplace may require time off request to be approved, so keep an eye on that status. That's it. Check out our Help Center for more videos and articles on how to use When I Work at help.wheniwork.com


Hello everyone, welcome to the Jenkins Infrastructure Weekly team meeting. Today we are 30 May 2023. Around the table we got your servitor, Damian du Portal, Erwelemer is off today, Markway, Tester, Stefan, and Bruno, our collaborative destruction of the nodes. Perfect. Let's get started with announcements. The weekly release 2.407 has been released successfully, at least for the packaging part, including the Docker image. So that means, Stefan, you are ready whenever you want on con. You can update weekly on infrasier. It's currently happening. Container images are verified, change log is published. There are a few more items on the checklist to do, but they'll probably be done before the end of this meeting. Cool. Mark, just to double check because we mentioned it one or two weeks ago. So it looks like that creating the tag on the Jenkins CI slash Docker repository was effective and in a few minutes, ten minutes after that, only the new release version was pushed to the Docker hub successfully. Is that correct? Yes. So I created the 2.407 tag in my local repository and then did I get push minus minus tags? Unfortunately, that pushed four tags, not one, because I apparently had some latent tags sitting in my private repository, in my working repository, that were not on the remote. I promptly deleted three of the four tags because they were junk tags that didn't belong there. But I was worried that I might have damaged the build process. But Damien, you said that it had safety checks that it would not attempt to push a tag that was too old. So those safety checks worked. Exactly. The setup of the job on trusted CI, the current setup is, discovers all existing tags. If a tags is removed, then remove it immediately from the build history. And finally, don't build, don't trigger a build for tags older than three days. Which mean if by error someone changes a tag from the past, that's the situation you were in, that won't rebuild and override the existing image. The downside of that setting is that if you want to rebuild a tag for a security reason, you have to manually trigger the build to force the system to trigger it. Otherwise it won't pick it by itself. Thank you. Now that leads to the future topic of we need to append a build number suffix to the end of our tags. Because 2.407, while correct, is actually not giving us the facility to do a rebuild of something if we were to need to do it. Exactly. But that will be the topic of the SIG platform. But of course that's the next step. But now for the infrastructure part today, we have demonstrated that now we are not overriding the existing tags unless we specifically trigger a build and that allows the contributor to have their pull request merge way faster. In fact, that was not a mistake from you. That was a test of the actual working of that feature. That's well done. The difference between a mistake and a test is very slim in that case. Got it. And now that means for infrastructure the next step for us will be to see I propose we wait for tomorrow's LTS and after next week we discuss again the topic of automating the release, the part build docker container made from the release. That could be as simple for today as release CI once finished the packaging or maybe it can start earlier but at the moment in time the weekly release process should be able to create the tag on the repository by itself that would automatically trigger the build on trusted CI that could be a first step to avoid someone having to do it as part of the release process. So I propose we wait for next week for discussing this one. Good for you? Let me take note of that element. Do you have other announcements? Yes, 2.407 is the first release that will warn users of our CentOS 7 container image that the operating system that that container image is delivering will not be supported after November 16 2023. So you may see noise in online forums you may see noise in various places saying we're not going to support CentOS 7 anymore and the correct answer is yes, that is accurate. Beginning mid-November of 2023, the Jenkins project will no longer support CentOS 7. Yeah, it's Red Hat Enterprise Linux 7 is the base but the vast majority of users are probably actually using CentOS, not Red Hat, not Oracle Linux and not Scientific Linux. Nice. Expect. And there will be a blog post Oh, it is today, isn't it Bruno? So I'll publish the blog post. We've got approval and today was the targeted day for it. I was thinking the day was tomorrow but I'll publish that blog post right now. Thanks. I'm excited. It says that will help a lot on a lot of cases. We should add the link of the blog post on that comment. Here? Yes. Please help us, collaborative notes. I'll put it in there because the blog will be published within the next few minutes. Upcoming calendar next weekly, next week 2.408 We have an LTS tomorrow if I'm not mistaken. 2.401.1 So please don't break the infrastructure tomorrow. I haven't seen any adversaries published. So we should not expect public adversaries on the mailing. I don't know about next major events. So is there any announcement or calendar item or can we proceed to the operational tasks? Ok. So then the tasks that we were able to finish we invited a student from the JITSAC project to the Pliggin Hill School Repository and the Associated Team. We had to work on different areas so we weren't sure about the initial need but looks good for Adrien. So I've closed the issue. If there is something missing he will reopen give details and we'll fix it. A user lost their password so as usual that will be worth checking Google indexation of accounts checking say oh but we have more and more gain user that just send that kind of request. So if they search too quickly I guess that's correlated with the uprising of chat GPT and I'm afraid that maybe chat GPT could send people to account I'm not sure how to deal with that no I'm not really interested into doing things with chat GPT so anyone with good idea or knowledge or skills on that part may be my theory is wrong but if that's the case influencing chat GPT to tell them to not open not redirect users to open issues there could be a great great thing. Maybe we should ask chat GPT what to do to not have chat GPT. You can I'm not creating an account there anymore. Thanks Mark for handling that. Thanks Stefan thanks for walking on ensuring that Popeur's Chesh 2 bootstrap 4 removed from all of our controllers with all the involved chaos that we can have between the docker images the puppet manage the manually manage everywhere anything to add on that topic Stefan mais ce n'est pas l'aim de votre question, j'imagine. Non, c'était juste que j'ai oublié quelque chose. Je ne pense pas qu'il y ait un tasque ou un feedback ou un post mortem pour faire ce tasque. Cool, merci pour ça. Je vois que vous avez fermé la machine Azure RM64 virtual. C'est à dire que nous avons effectivement stoppé d'utiliser AWS for Infra-CI.io, including credential and plugin removal. C'est correct? Je pense que j'ai fait tout. Cool, merci. La prochaine étape pour moi, c'est de vérifier l'impact sur le AWS billing. Il doit probablement, plus tard cette semaine, ou le début de l'année, je pense que ce sera un petit jump comparé à l'impact sur le cost d'adaptation, mais je suis sûr que ce sera visible pour cette semaine. Un autre compte, c'est l'issue. Donc, jump. Autolink référence pour Core. Je n'ai aucune idée de ce que c'est. J'assume que c'est quelque chose qui a été fait entre Alex et Team. C'est correct? Oui, c'est correct. Et c'est travaillé bien. Les plugins 15 plus que j'ai maintenues sont maintenant utilisées en Autolinks, et j'ai confirmé qu'ils travaillent. Donc, pour ces plugins qui utilisent Jankin's Jira comme leur bug tracker, cela le fait un peu plus facile. La plupart de notre travail en Jankin Infra n'est pas traquée comme en Jankin's Jira. On a tenté d'utiliser des issues GitHub. Cela ne nous aide pas beaucoup, mais les maintaineurs de plugins comme moi sont bénéfits. Si ils choisissent d'évaluer eux-mêmes. C'est cool. Merci pour l'explanation. J'ai oublié ce que c'était. Maintenant, c'est plus clair avec l'explanation. Clean up and import and manage data monitoring in terraforms. Je vais être la voix de l'arrivée ici. Donc, merci d'arrivée, même si vous n'êtes pas là. Il y a eu plusieurs manières de créer des monitors data. Les monitors sont objectifs dans l'API et l'UI qui permettent de créer des conditions et des thresholds pour alerter quand ces thresholds sont crossés ou quand ces conditions sont mises. Par exemple, quand une machine virtual a un hard drive qui a atteint 80% de usage en termes de disk space, cela a créé un alerte. Cela a créé un alerte warner et si nous avons créé 90% de thresholds, cela a été un alerte de page utility. Nous avons recently started to use properly monitors and we have realised that somewhere as code somewhere created manually, somewhere created magically, so we did a big cleanup on that part. Everything is managed as code from our terraform repositories. Thanks for that big cleanup survey. We removed false positives and there was a hidden task behind based on the feedback from both Erwin and Stefan when we reached a new usage, a new node disk space left I don't remember on which service but we were still having a lot of free disk space and we all realised that it was a full on high nodes. So now thanks for from your actions folks, we have a monitor that not only monitor the free disk space but also the free high node per device that will alert us in the future to avoid blocking a service like that problem did. So nice iteration folks, I'm really proud. And one last issue account name. I need to spend more time on this one. Now jump on the work in progress. So as usual for each of these items, we will see if we continue working on this on the next milestone or if we need to put back on backlog or close it because that can happen. First one migration to the cluster public gates from the former cluster. The goal was to fight against a big error message on AKS that say hey, your network has an IP overlap that create a bunch of troubles and it did. So we are migrating services to the proper clusters. The status is that we migrated a few services during the past milestones including public health core that is now running properly on the new cluster. Here you can see the lists. So we have already migrated to the network. Key clock has been migrated last week without any problem. Incremental Publisher service which is a basically a web book receiver that receives messages from the pipeline library on CIG and Kinsayo that tells it to get the archived artifact and publish it to artifactory in incremental's repository. So that service is quite widely available. So we can migrate to the network. So we can migrate to the network and be careful with it. That has been migrated with 10 minutes downtime after letting everyone know that oh it was. By the way we should think about making it highly available. It's a stateless service so we were able to migrate plugin health coring. Here on state I'm just checking the last messages. Yes, plugin health score was done with also the help of Adrien that was way efficient to have the developer of the application to be there to help us on the probes. So thanks Adrien for that. We were able to remove deleted resources to not consume a lot of data. Just a point we had a former DNS record for javadoc. No it was for wiki. One of the two websites did add the old DNS record pointing to an IP instead of being a C name to the whatever Jenkins IO name. So that broke the service after deleting the resources. So we were able to fix Managers code now so we shouldn't have the issue anymore. And next step is to migrate work is in progress that will be done later today. Rating Jenkins IO which is used on the changelog pages of Jenkins IO when you have these icons that you click to vote and rate the releases. And uplink Jenkins IO which is used for telemetry sending from Jenkins controller all over the world so we can get some statistics. So both of these services are of the same topology. They have a PostgreSQL database on two pod replica running on the cluster. So we are going to migrate both of the same time in a few in one or two hours. I expect starting to work on the critical one held up and get Jenkins IO. But we will decide that with Irvi when it will be back from Jenkins IO we need to be full time for migrating these two critical services. So almost there any question? Ok so we continue working on this obviously until the new cluster and there's all the workloads and we can clean up all the former resources. Next one migrate trusted CI Jenkins IO from AWS to Azure so we worked both Stefan and I on this one Stefan was my rubber duck the world that has been migrated to the new virtual machine successfully. So the next step is to run the effective migration of trusted and see what happen. A few so the proposal date is Thursday first of June we might start tomorrow but as a good and really wise tip from Stefan maybe wait for not doing it a day of LTS even a few hours after because I'm sure the LTS will be done quickly so that's why the proposal for Thursday. Until then the next step will be taint the virtual machines that mean destroying and recreating machine from start to clean up every temple test trace that we might have left on the data disk that won't trash the data already migrated we want because the data disk won't be tainted on the virtual machines and then we will see what will be the next steps there might be some fine tuning afterwards especially on the security groups but now we have reached the same quality level and same rate as what we have on AWS so we should be able to proceed for the next steps so that's all that means during the operation the update center index and the repository permission of data jobs might not be able to run as expected so as a safety measure I will ensure that I will run both of the jobs on the current machine to have something fresh and updated particularly for the air pay and once it's built we stop the controller, do the migration and then try to run them separately most critical is the update center but that should be quick to build and republish and the second one will be the RP most of the issues we should have after that after that migration will be IP openings on different firewalls because it used to be a whole machine so the new IP that will be used by its agents and its controller have changed of course so for instance when we want to push to the update center virtual machine we might need to update the configuration so if you have word issues in publication of plugins update centers, if you see people complaining that their plugins is not up to date on plugin genkin.io starting from Thursday that will be the main reason any question no thanks for the alert do we need to and I assume that there will be some notice to people or will there be any notice to people yes the plan includes most probably that will be sent tomorrow one day before the operation status genkin.io will be updated and an email to the mailing list of genkin.io dev will be sent because that one has quite the impact so better communicating works I prefer letting people know good point thanks for the reminder that's important send email 31 of may one day prior all DNS has been set to with a TTL of 60 seconds for both operation cluster migration entrusted next task install and configure datadog plugin genkin.io so I worked a bit on how to make the datadog plugin installed inside the genkin.io container to communicate in UDP with the datadog agent running on the host machine behind it's mostly a question of setting up the agent to listen on the proper network interface so the container can reach it on the host and by default the agent only listen on localhost which is not available the localhost of a host machine is not available from a container so that's only a set of finding the proper pooped setup for the agent so it's agents.yaml configuration file will be updated to listen on the proper network interface airway told me will be able to continue working on this on the next milestone it did some successful manual test on the machine that have been overridden since then by the agents so it's in a good direction and we should be able to have way more information on the agent.yaml airway was pretty excited about this topic because that could help a lot on the bomb build slowness on the agent.yaml we had a question about adding a repository gitpack so a contributor should be able to build their own their plugin they I haven't had time to look on this one most probably we will act on short term by adding an exception on ACP so the build will instead of ACP train to get on our gifrock repository it will directly bypass ACP for that specific repository we need to help the user as soon as possible so if it's okay for everyone I will keep that issue on the upcoming milestone upgrade to Kubernetes 1.25 I've started reading the changelog we might have issues with the psp and a few depreciation so that need to be reviewed for workfully so I'm still currently trying to evaluate the impact on our clusters the idea will be planning for Kubernetes cluster upgrade next Monday for DOKS and CIK so the two clusters used by CIK because this one doesn't have anything related to high availability load balancer or persistent volume they don't have these free features so that could be easy to start with them. ACP is unreliable we didn't work on this one so that was a time management mistake for this one right now the next steps will be being able to have inbound agent for the Azure VM agent on CI agent Kinsayo I'm keeping this one because I'm sure Stefan and I can work on this later this week Ubuntu 2204 upgrade campaign I spent some time cleaning up two of our machines that are ready to be upgraded these machines are the 203 OSL machines meaning lettuce and edamame the proposal is migrating this one as soon as possible because they don't host any service so better upgrading them the idea is that if the upgrade goes properly that means we can immediately jump to the question Kinsayo which is also a virtual machine updated on OSU OSL why these free machines are special they are virtual machines or Bermuda I'm not sure I think it's virtual machine hosted by the OSU OSL organization which is a University of Oregon the question is if we upgrade in place the distribution and reboot will the kernel work with the virtual machine so if we lose edamame or lettuce that's not a problem and we will ask them and we will know what is required for the upgrade before breaking Puppet Jenkins so you that could be way more annoying Puppet Jenkins ready support Linux container when running Windows virtual machine oh I forgot this one install docker with docker desktop instead of docker c on windows packer images that should be a few lines and Stefan finally RM64 not pull on publicates to start using RM64 pods for the production website workload can you give up a heads up on this one yes I started a PR to define as oh sorry to define the new node pool and the main problem naturally a problem was to find the correct machine to use as a IRM node we worked a lot on disk size and memory and CPU to define the correct one I think we found we found the good one so it should it should go ahead now and maybe we will have to work a little on a new node pool for the Intel one to just rename the node pools and to have something more coherent yep homogeneous is that okay for you to prioritize once the node pool is created successfully because you know with Terraform and Azure we know that sometimes the plan says I should create these resources and when it's time to create them it fails with whatever error and then you have to iterate so once created successfully proposal is then you start working on how could we still Kubernetes to use IRM image for the Java doc and Genix image okay again the goal of that issue is to execute some of our workloads websites mostly static websites on IRM 64 machine instead of Intel so we can decrease the costs per request or the cost absolute cost of these workloads now I'm removing the backlog let's cover the triage and new issues mark I think you can start because I saw you open issue about bum issue bum problems earlier today is that correct yes so so and I think you mentioned something that may help in in your earlier comments I'm not sure so what we see is that attempts to release the Jenkins plugin bill of materials failed over the weekend on three different attempts each attempt failed taking 1,5 to up to nine hours to to attempt to do the run previous releases that had been successful with this configuration took six hours and so there may be some change that has caused things in the last seven or eight days to become slower we will take some actions on the bill of materials side right now we're supporting for release lines 361 375 387 401 we will very soon drop 361 so that should reduce our runtime somewhat right there immediately but there may have been other changes that are worth are worth further consideration in the infrateam right the the problem here may go away just by the changes will make on the bill of materials to reduce but if it doesn't will then need help ok so we still need to look at the logs and see what happen because between the eventually the spot the spot instances eviction rate that could have grown on these instances so we can check this and also yeah I fear that we will still be stuck with the concurrent for resources on CIG and Kinsayo when there is a bomb builds and when the step starts to take absolutely unexpected times for simple steps that should take seconds and that takes minutes I'm sure we are in that kind of locks so yeah for that one we need to focus on the new CIG and Kinsayo instance the first step and the work that we did is doing with the datadog thing we might have datadog helping us on monitoring what is going wrong in that controller great yeah so there are plans already for the bomb to take some actions Tim Jacquem even replied to my that one saying hey we don't even need to wait for the release of 2.401.1 and I think it's a valid a valid statement because 2.361 has no known security vulnerabilities and users should be running 375 or newer actually they should be running by now 387 to decrease time needs to investigate datadog plugin could help ok so I've added this one on the upcoming milestone now we have a request by Gevin for Matomo kit of docker repositories yes he created a repository and we removed it because we didn't add news for Montez on that topic even asking him so he recreated everything we have to edit this and I will take just scan the configuration state of that repository and everything I assume it's the part for replacing google analytics by Matomo which is back on the pipe that should help us not depending because it looks like even Olivier doesn't have access on google analytics so yeah he doesn't have enough permissions to grant me admin to migrate some of the properties these are objects inside the google analytics API as I understand so we will have to wait on july for automatic migration by google analytics themselves but that was a discussion and survey was willing to help to have our own Matomo service I understand that Olivier Verna run Matomo for the past 2 years for update CLI and gave in also on his own so that should be a service to host on our cluster the next step will be we need and I will ask explicitly gave in on here what do we need for running the cluster because there is no reason for hosting and building a docker image if we don't run it somewhere and we need to know the requirement for running Matomo in production so by default I'm adding it to the next milestone assuming that survey express some interest one or two weeks ago when we discuss that topic if I'm mistaken we will remove it and let gave in walk or just say no or move it on backlog that's not top priority but important because gave in is able to spend some time with us now for the bootstrap so better to use that precious time mark you open an issue about Artifactory bandwidth assessment oh I forgot to work on this today oh crap so the idea is after a meeting with Gfrog last week we have two brown out session to do so brown out will be us changing a major setting on the repositories and see the effects both the build on infrastructure and the build from the outside contributor brown out is between black out and I don't know is white out existing so between nominal condition and everything broken the goal is for one hour so we will let chosen know a few days ago that that day during one hour we will change that setting that might have that impact and will most probably break your builds because we want to see how it breaks the first one will be once validated with the one time with the Gits repository to see if we can disable the Maven repo one making it private only for Artifactory that's a repository is used on the virtual repository public that everyone should use we are not absolutely sure but it looks like that some users are directly calling that repository from repo.genkinci.org slash repo slide Maven repo one they should use public they could be two kind of usage for a direct call to that virtual repository the first one is misconfiguration of POM XML or settings XML and that one if it breaks it's ok because that need will need fixing by using public if it's a valid and expected use case and the second case is abusive use case that cost us bandwidth somehow so we need to check if we can disable Maven repo one so we will do a test on Gits and then a brown out of this one to see if it break things is that a good summary mark for the first step yes that is and then the second the second brown out will be removing Maven repo one from even the public virtual repository at all and see the impact but that one will need more details because one thing for sure is that if the abusive use case switch from the direct Maven repo one and they realize they can use public that will just shift the problem from one repo to the other to see why do we have mirror of Maven repo one today that one might need some fine tuning of the ACP though because ACP if they cannot find if it cannot find an artifact then it will need either to fail abruptly and then we fix the POM XML dependency or eventually directly have ACP downloading artifact from Maven repo one instead of our Giffrock repo and caching everything still to keep the caching on an infrastructure so we have to move this one to this week milestone because the goal will be to do the first brown outs this week is still okay for your mark if we talk gets Thursday or Friday yes yeah I think so I would have a preference for Friday if it's okay for you and Friday sounds great so Damien the Friday brown out it's still okay if we just do the J get one we think that's relatively low impact on the Jenkins project overall yes so jig it for Friday and based on the feedback we plan to do the brown out of Maven repo one the direct one next week is that okay for you that yeah that that should be fine Monday or Tuesday next week for the Maven repo one timing proposal discuss during well and it doesn't even have to be that early in the week next week because we won't have an LTS that week we could do it Wednesday oh yes but I would prefer doing the brown out as soon as possible so we can give feedback to Giffrock as soon as possible okay great she gets brown out Friday too yep Friday too brown out Maven Maven repo one brown out four the five of the order six is that okay yes yes that's the same thing Maven repo one we don't have administrative on the Maven repo one we would need more money clearly the dash cash is a suffix that implies that it's a caching of the original Maven repo one external mirror that's the same awarding I use abusive awarding for mentioning that mirror repository so we don't need more triage what do we have find a way to monitor job done from private controller yes that doesn't need triage and it's not the priority there was one that was raised in chat just minutes ago by Gavin Mogan on the 3602 did it already get covered it's matamo yes okay so I hadn't seen it in the notes and so I added it to the notes okay real time check perfect thanks yeah I did it milestone but I forgot to cherry pick to the notes let me add the assess artifactory so find a way to monitor job done for private controller it's a kind of next logical step of the CI Jenkins IO connection to the data.dog plugins that should give way more information to the data.dog about the internals of Jenkins the amount of job failing jobs that could allow us to monitor critical jobs for instance when the bomb takes more than 10 hours we could have a monitor on data.dog letting us know that's a practical example but for some private and sensitive controllers such as trusted CI and release CI as infrastructure officer I refuse to enable the data.dog plugin at that level of detail we can have data.dog plugins sending virtual machine matrix oh that sensitive virtual machine is using a lot of CPU that information is okay sending internals of Jenkins controller that could or could not depending on the accidentally set up by someone unexpected unexpected backup of credential in data.dog is a scenario that could happen that we don't want specifically for update center we don't want an unexpected backup of the update center certificates right so we need to find a way they used to be a proposer by Daniel that might have been an issue or private conversation I can't remember so I've chaired that with survey the idea will be to each of these sensitive jobs that we want to monitor will need a post build step that just write a few selected information the date when it run whatever information that are not sensitive inside I think we have a public bucket with file with json file use for the reports we can write without any risk for the safety of this controller the status of the latest update center build or RPU builds and then build the data.dog monitor that say if after 15 minutes the update center last build successful build then send an alert we can build that kind of 2 step process so that's not top priority but that will be really useful for us to track these jobs and helps developer because we can fix the element before error happen so that's why I propose we don't start working on this we don't have time for this milestone remove triage but that one is interesting to track jetpack we should not have triage anymore it's CIGEN Kinsayo and it's on the new milestone ok I don't see any new issues we are removed pullcredential from Kubernetes cluster so for that one I'm removing triage but not adding to the milestone because we won't have time credential ok so do we have new issues new element you want to speak about and add to the milestone or to triage or I got I got one last item that need to be tracked on a new issue I will take care of opening it and adding it we receive the pull requests from Alex I will sync with Alex for the implementation to see if we have to do it Alex and team are heavily working on weekly CIGEN Kinsayo which is a public instance and a public demonstrator of the new GENKINS design UXUI etc mainly the design language and they want to make anyone being able to have the system read so we can show the UI of the system administration the new UI which is a valid and legit use case thing is that could risk and that would risk people being able to access some encrypted credentials even if the credentials are encrypted that will give them some specific permission we are not completely sure but I'm not really willing to try because we are in a sensitive area giving read access to the system configuration should give you access to G-CASK export as far as I can tell which has an export of the encrypted credentials our credentials could be on some fields I don't know exactly how the permission work but as a matter of safety my proposal is I don't want to block that new thing but before I prefer stop using LDAP authentication for that instance and switch to the local Jenkins user database so we would have an admin and a shared password for the administration so the LDAP binding password there would be no chance to expose that password and the second credential that could be risky is the GitHub app token but as Tim said it's fine to have that risk there because it's a really fine-grained GitHub app so my proposal is to change the configuration of weekly CI so it doesn't use LDAP anymore and it doesn't use any credential on top level unless there will be public credentials for demonstration so then we couldn't have any risk of anyone accessing sensitive credentials here so the real concern the remaining concern seems to be that LDAP binding credential and that the only way to stop using that is to stop using LDAP as the authentication system exactly because on the paper that permission shouldn't expose credential on the paper but once the credential is exposed that's annoying because that's a public instance better and also I want to suggest to Tim and Alex that we could create a dummy agent so that will mean a SSH agent machine running outside Kubernetes that could be a tiny virtual machine somewhere if they need to demonstrate the UI of the nodes pages but that's not for now so yes that's all for me is there anything else you want to add non ok so then I'm gonna stop sharing my screen I'm gonna stop recording and for people watching this recording see you next week bye bye


Another person on Facebook on our Facebook page Todd Voss said if you could combine Zelda with any other series Which one would you do? Assassin's Creed hands down. I knew you were gonna say that Well, why Assassin's Creed? I It would appeal I when I play games I am very much a graphics person and visually and I just think Assassin's Creed and Zelda would meld together visually because I've seen a Lot of fan art combining link with the main character from Assassin's Creed Tingle the setting You know if they just gave it a medieval setting and had some Zelda characters in there I think it would be a great crossover game and I think the reason a lot of people like that is a crossover game is The climbing and the way that you can explore the cities in the world in Assassin's Creed a lot of people want to be able to do that in Zelda you be able to scale mountains and Climb tall buildings, which there aren't really a lot of tall buildings in Zelda But they could make there be some tall buildings in Zelda if that makes sense So it would be really cool if they if they kind of went that route I know that some people will own or not assassin's Creed. I'm like this isn't about making Zelda an annualized franchise At one point Assassin's Creed was actually considered one of the best games out there Assassin's Creed 2 is received extremely well so You know if you kind of look at what Assassin's Creed used to be and you combine it with some Zelda I think that could be an interesting mix I'm gonna kind of throw a you know a bit of a curve ball out there I would almost like to see Zelda smashed with Super Mario RPG Wow, I never thought of that. Oh, yeah, like it's like Super Mario RPG is such a unique game And you know it's changed a bit over the years and they tried introducing it into the paper jam and paper Mario stuff But ignoring all that just that the original Super Mario RPG game It really took Mario in a drastic. It was one of the one of the first games to take Mario in a really drastic different direction And you know, I know people like Ozelda is not an RPG.  They might be able to do it with but I a Super Mario RPG level game I Don't know. I just imagining all the different Zelda characters you could have and I'm leveling up and you know the the turn-based combat it could be That'd be interesting to see a turn-based Zelda game Exactly, I mean I even thought about you know, maybe a bit of fighter emblem on top of that You know a little bit of that that grid based strategy game But yeah, I don't know it's just something that I always thought would be really really cool You know, obviously I wouldn't make it a mainline game. It would just be kind of its own side game, but Yeah, why not? I mean if they can do Triforce Heroes The third multiplayer Zelda game and have it be as different as it is from the series I don't know why you can't you know try a turn-based game Why not right? I mean and I think it would work in the timeline I don't think gameplay style matters But even if they just make it a non-canon sort of spin-off game like Hyrule Warriors, I'd be totally okay with that Yeah, exactly. It's just something different. You know like I like Assassin's Creed because it's kind of a almost an expansion on what Zelda already does and Just you know, there's a lot of cool things in Assassin's Creed that would mix well I know some of it was over the Assassin's Creed combat is really easy Zelda's combat is really easy. So you're not really Preaching to the choir at all Yeah, but but you know, I don't know those are just some ideas we have You know what what ideas do you guys have you know go down in the comments type it up? What games would you like to see Zelda kind of crossover and do that's a really good question


Hello. So you know we are being recorded at this time. Yes. You make me a co host. Yes. What somebody else here she disappeared. Hello. Hello. This group is not the best at attending on time. There we go. Just need one more for a quorum. Okay. Well, then it won't be with us, but I haven't heard from anybody else. So. Anybody have Brits number. Yep. I just texted her. Okay. I texted Shoshana and Sarah. Great. The woman named Mary. I'm on and. I'm letting you speak if you want to say something, Mary. Hi, sorry. I don't use zoom a lot. I can't hear you. I'll see you unless you become a panelist, but we can hear you. Okay. Cool. Yeah, I haven't been to meetings before I was just kind of interested. Partly because I live near McClellan, which is. Has had a lot of trees cut down recently. And. I'm curious about getting trees planted there. Planting some trees there. I don't want to talk about that. While we wait for the quorum to have an official meeting. Sure. Mary. Where on McClellan do you live? If you don't mind. If you don't want to say it's fine. Just to also reiterate that this is being recorded. And we'll be able to see seen. On the town website. After Friday. Okay. Yeah, that's fine. I'm not sure how to, I'm happy to enable my video. I just, I'm not used to things where I need to. Be a panelist or something. Okay. Okay. I actually don't live on McClellan. I live on a little street that's right off of McClellan. Oh yeah. Yeah. Okay. Yeah, we have, there was a lot of trees. Private trees came down on McClellan and some of the town. Evergreens that were. Between the sidewalk and the road came down as well. We do. We do plan on replanting. On McClellan street. I don't know if there's any room in the public way there. Except for trees on. I guess that would be the north side of McClellan street. There is some room in the setback. Almost in the right away to plant. I think we planted. One, two, three, three trees, four trees there last fall. But there's more to do. Yeah. So. Will that be part of like a, a public tree planting thing like there was last Saturday? Hopefully. Probably be something we do in the fall. On the clown street. That's probably one of the things we'll discuss. Briefly this evening is the next. Next location. Cool. Do you know anything about why all the trees were taken down? I don't know. I don't know. I don't know. I don't know what it is. So. The white pine that were between the sidewalk and the road. We're taking down because they. Really had outgrown their location. And that. And we're. Sort of. Trapped. They couldn't really grow any bigger. And because of the way they had been. Were all these multiple leaders. For branch attachment points. The trees were just sort of self-destructing. So. They've been on my radar for a long time to do something with, and the town decided to repave. The sidewalk on film street. Which was. Pretty bad around these trees in particular. So we took the opportunity there to hold a tree hearing to. And so. So we took the opportunity to walk in and we plant. There were a number of trees taking down. Large. Norris Bruce that were on private property. That the owner took them. And they were. That was a large section of. Kind of the open space over there. Yeah, I think we saw some being taken down.  So it was kind of striking. Yes. I'm not sure if my video is on currently or not, but.  We can see you on this would be to make you a panelist, which I'm happy to do. Okay. Yeah. If you wouldn't mind trying that again, I'm happy to enable that. And we now have a quorum. Although Julian has disappeared from view, but. There you are, Mary. Julie and I still here. So. We officially have a quorum. We can start the meeting. We were just. Filling in Miriam for those for, I guess, the Sarah who came late. Lives on near McClellan street. And so she was asking about those trees. So welcome. The agenda. We're not sharing anymore, but. First thing is just, are there any public comments besides what I said? So you have someone with you, Mary. Oh, yes. This is my partner. Okay. Anything you want to say or. Nothing that she hasn't already covered. Okay. And if you want to put your email address in the chat, I will add you to our mailing list. Cool. Thanks. If we'll see if that works. All right. So approval of the March minutes. Board member committee members. Everyone good. Ellen. Okay. So minutes are approved. Ours. We collect volunteer hours. And then that goes into our three city USA application at the end of the year. Sarah. Four. Julian. Nine. Ellen. Four. Four. And I think I did about 10. Yeah. Okay. Can I ask you a question that just occurred to me? Yes. So on the, when we do the second side of tree plantings, do you keep track of the number of people that volunteered? How long they volunteered for on those plantings? I estimate that. Yeah. Okay. So I'll probably add. Or half a dozen people. I'd say add 12 more. Hours. 10, 10. Because it's not all of them stayed that long. It's not all of them. It's not all of them. It's not all of them. Members of the committee column. So when we do the other day. Volunteer, they also break down. Like youth. Hours. And they count those separately from. Adult hours. So if we can. If there's a way to track. Youth. Separate from adult. Okay. Okay. I'm not sure. I'm not sure. I'm not sure. I'm not sure an adult. Yep. I am 18 until this June. Yeah.  That's fine. Moving on. Let's see what's on the agenda. The chairs report, I guess is next. Greenfield tree committee has a tree nursery. And they're having an open house this Saturday. Yeah. Henry, I'm sorry. Can I interrupt? Is anyone taking minutes? Thank you. No one is because I get you want to do that, please? Sure. It's going to take me a minute to get a document open. So. Okay. Yeah. Well, I'll make these announcements. Whether they get in the minutes is not as important. So Greenfield, they have a tree nursery, which we had years ago. They have a tree nursery, but there's this quite extensive. They have about 150 trees. They're growing out for the town. And they're having an open house from noon to two Saturday. You can show up there giving out free trees and you can see the operation. And then if you want to help out from one to four, there's a work day and that'll continue on Sunday, the work day. So it might be good. I'm working this weekend. I can't come, but I can't go there. But if anyone wants to do that, I can do that. I can't go there. I can't go there. I can't go there. I can't go there. I can't go back since we're talking about doing a tree nursery again at some point. When it, I'm sorry. I missed the date. When are they doing that? This Saturday, the 15th. Yeah. And the work day is the 15th and 16th. And then. Julian, you probably know more about this, but I got an email about the. That is correct. I can also confirm. That they're working on the solar survey and getting a good amount of responses. On that. So that's an update. Great. Okay. How are you going to attend those meetings or. I am. I believe both of them are out of the school day. So I believe I can attend both those meetings and. I'm just thinking they also are going to be planning for the sustainability fast. Great. And that's what we need to do also. Yes. If that's on our agenda. The other thing is I sent Scott. All the information about. All the activities we're doing this month. And we got a nice column in the paper. That along with Brits. Let it to the editor was nice. Although she said that as a private citizen, she didn't mention she was a member of the committee. So. And then we heard from a group on. Through our email. The art called. It's a company called orange theory fitness and Hadley. And they wanted to encourage their members to come help out. So they may show up at one of our plantings. But they didn't show up this time. So I don't know. The only other thing I have. I don't know. I don't know. Besides what's on the agenda is I went to. The South Amherst high school former high school campus. And I did a lot of the pruning of the fruit trees there. We have an orchard. At the former South Amherst high school, which was an elementary school before that across the common from the library. And those trees are for anybody to pick fruit. So we planted those. Seven or eight years ago. And then we planted the fruit trees. And then we planted the fruit trees. Anyway, the trees look good. And hopefully we've got more fruit this year. That's all I have. Julian, do you want to do the vice chair report? Sure. So two updates were about the. ECAC and the solar bylaw working group. Just noting those two meetings. Another update I was going to share was that I. I have a lot of friends who are interested in the sustainability fast coming back this year and hearing from us and working with that. And then. I've also talked to some folks on. Greenwich and Long Meadow who were interested in getting more trees there. So that is a potential. Location. We obviously have. McClellan and. Fearing as well. Yeah, and Woodside. Yeah. Yeah. Okay. No, we did. We did Woodside. Do you mean orchard? Yeah, I guess so. Yeah. Yeah. Bad area. All right. Good. Alan tree warden's report. Sure. We had a nice, Henry.   And it's an opportunity for the students. In this urban forestry class UMass to come out and kind of see what's going on in the community, how. How the tree committee works. How the tree warden works. Some of the. Issues, you know. Running a urban forestry program and trying to keep trees alive and healthy. And then we went to the county park. And then we walked. From there. Crossing over East pleasant street. To all the new buildings that are going up and then down Kellogg. We're currently doing the sidewalk renovation there. And we discussed some of the. Zone protections. Things we're doing to protect the big oak trees on Kellogg. It's something I've done for. It's been a lot of fun. It's been a lot of fun. Even when I was a volunteer tree warden in town. And it's, it's always been a lot of fun. It was really good to have Henry and Julian there to talk about the community. Fit nicely. Tonight is the house move from sunset. Remember the tree hearing for the development taking place on the corner of fearing sunset. The last house is being moved. And it's going. Down sunset out onto Massachusetts Avenue. Down North pleasant street through the roundabout Danny's pleasant street and straight down towards rest streets. Across from Shea Street. And that's where the new house. House's new home will be. So there has been some pruning going on by contractor. By law. We cannot stop a house from moving down the street. So we have to do a lot of pruning. And I think it's a great way to get the law on the book. The public way. Essentially says, if someone wants to move a house, nothing can stop it. So. We obviously work with the movers and that it was actually big help. They actually pruned a lot of trees. That had poor clearance over the roads. So. And they did a pretty good job pruning overall. So. So. College street. From. South pleasant street. Where North end road comes up. Meets. Self pleasant. And then turns into college street. It goes down. Towards the substation. So from South pleasant street to the substation. Every source is going to be undergrounding. All new. Conduit system for. There's one tree left on that side of the road in the grass belt. It's in Norway maple. And I will be. Posting a tree hearing for that tree to come down. There is also talk. Of undergrounding utility lines. On the other side of the street. Sort of on the Valentine hall side of college street. If that happens, this is a once in a lifetime opportunity. To complete a completely new. Streetscape. From the center of town by the common all the way down to. The substation. So. The, the underground, the utility. Kind of it going underground this. Spring after I was college. Homecoming. Graduation. So that's for new power cables. It's not for the existing power cables and told. So the other power cables on the far other side of the street. They're not part of this current phase of the project, but there's talk of doing that. So I have to post this hearing next month. So we'll have a site visit schedule. For next month's tree here. Committee meeting. See. I think that's it. Thank you. Thank you. Sarah, you want to do a treasure report. No update. You didn't check. I'm wondering, did the $25 check get deposited? I, I'm not sure. Allen. Allen. Are you talking to me? Did the $25 check that I dropped off at your place? I did receive it. And I gave it to. Sarah in the office to deposit. So. Great. So Sarah, if you could keep an eye out for that, it'd be great. I'd say that there's going to be a. This is not a tree planting, but we can talk about it now. We need to do a vote for unless we already did. I don't remember. To spend money. For tree planting. Till July 1st. When the new. Budget hits. Did we do a authorization for every month? We did. We did something that was kind of in perpetuity, but I don't know the lengths. That it would be active for. Okay. I haven't been told. So I. The trees that we planted. 16 trees. The best quote came from Emerson nursery. It was $3,252 for the 16 trees. 18 trees. I'm sorry. 18 trees. Probably saw smoke coming on my head. Add that column up. Yes. So it was $3,252. For 18 trees. So. Is that going on our expense or in your expense? That's on the tree fund. Expense. The new. Go ahead. I'm sorry. What were those trees purchased for? The second Saturday tree plan. I just did the math. It appears they were about $180, $190. Yes. So. Okay. So that's coming out of our budget. We'll have to look up whether that. Was covered, but maybe we should just say. Do we approve that expense? Oh, in favor. You could do a vote. Okay. Make a motion and do. I propose that we budget that we agree to spend $3,200 for the trees that we already spent and bought. 3252. The 18 trees that were already planted. All in favor. Passes unanimously. And then should we do that for next month or. If you. If you don't think the past. I. I do feel like we have had one. In the past. I wonder if I don't know. It said for the seas. I think it was for the season. Was it for. I don't remember the wording on that. So if it was just for one year of planting. Was it a calendar year or was it a planting season? I don't remember us having a termination on it. But I think the wording was something like that. During the planting season. Which. Applies for. Every year. That we do planting, you know, to the, I think the idea was to exclude expenses for buying trees during the winter months when we're not planting. And during the month that we take off on the top. So I can check the wording, but I believe. We are. I don't remember us having a termination on it, but I think the wording was something like during the planting season. So I wonder if. I don't remember us having a termination on it. So I don't remember, but I think I'll name. The. The termination is the year of the save. We already, we kind of covered it. Okay. In perpetuity. Yes. If you can check on that for next meeting. We can either update it or. That's that. Okay. Okay. Great. Thank you. Okay. What's next? Social media report. Anything. Julian. dog digging a hole for Bennett but that is about it. And did that get the huge response that he was expecting? People liked it here and there but only five or six I think. All right. Okay so presentation discussions the Mary Maple Love Letters exhibit I think that was Brit or was that Ellen not you so okay. Arbor month plans we pretty much planned out we have Arbor day Alan wanted to shoot me to share something it's going to be a whole event around the big tree at strong street let me see if I can find that flyer. There it is this is going to be in conjunction with Amherst College and with the Amherst Storkle Society and the Amherst Library Jones Library. So I will share this and you can see let's see if I can find it here. All right everyone see that. Yes. Okay so it's it's pretty exciting it's going to be a talk by Alan and then this this guest speaker is going to talk about big trees and then it's going to be a tree walk on Amherst College after that and then back to the library for a children's book reading and then planting the new sycamore. So Sean and I had a quick meeting a zoom meeting the other day with Jones Library. They're going to have a children's book reading and a craft event based on trees that the teen lounge group is going to participate in and then from there we're going to go over to the Amherst History Museum and use a tree planting of the the new sycamore tree. The new time our this lecture with Dr. Kevin Smith from US Forest Service. I think I've said this before but just to repeat it. He gives a very entertaining I believe entertaining presentation that's you know science based on tree biology you know the difference between a mature you know old big tree and younger trees they really do respond differently to the environment around them and they they grow their energy supply system is very different than young trees it's interesting he's very entertaining so if you want to learn you know about how big trees work this is an excellent opportunity I hope to get mass certified arborist ISA credits any other kind of professional landscape nurse admin association those kinds of credits I want to see how many you can get to encourage people who work with or around or plan buildings around old trees to go to this so they can learn something about preserving big trees. Amherst College Amherst College will be hosting a walk and discussing their big trees on campus and their tree planting program on campus as well and they will be planting a tree great and that's on April 28th which is the last Friday of April so I expect to be at it and whoever else wants to join me that'd be great and I will forward this piece of paper to Scott Merzbeck so we can get more information in the paper and Julian and if you can talk to Shashana make sure it gets out on all our social media yeah I just want to preference this that this is a draft so this is not it's not a final a final version I haven't your proof this or anything this is literally finished it this afternoon and wanted to show it to the committee so the schedule is right but it's not a final draft for press release but you want to start you know okay sending it out there it's fine as long as you realize look at it make any corrections that should be made grammatically here okay yeah I can do that and where I can wait I'll do that and I'll make sure Bennett puts out a special newsletter mentioning this and the the link that's in this the coal assembly room link that's not for that was that's an internal link that wasn't intended to go out public it just shows the room where the presentation is taking place okay yeah I noticed that all right good any comments on this no okay great good so I will stop sharing and be able to see all you guys again just quickly at the so the sustainability festival is next we really need to have a schedule who's going to be working when the setup I'll get the the canopy that I got last year or whenever we last had an event and then we'll need people to staff the booth and we're giving out the paw paw seedlings and the tulip tree seedlings if you have them Alan yes I do great okay so I think that'll be popular and we need to also publicize that we're giving these out so Julian if you can meet with Shashana and really try to make a big push on that on getting the seedlings or on getting the word out oh yes absolutely absolutely and maybe we'll just pass around by email a sign-up sheet for when people can come help out rather than do that now with only four of us here all right and Miriam and partner whose name I forgot I'm sorry um you're both welcome to join us and staff the booth or just hang out and see what we're doing so yeah great okay um back to the agenda okay individual tree requests we'll table that for now uh town tree tour that's really we decided to do it in the fall so Alan at some point you and I should get back together and figure that out again but okay second Saturday plantings we had a great planting this month it was great and a lot of neighborhood help and it was fun Alan yeah I mean they have Blue Hills Dana very uh they're very active they have a very active email chain you know in their neighborhood so it's I've had a lot of email follow-up about how to maintain the tree not to care of it you know they're all public tree trees they're all planted in the public way but there's they still want to help help them protect them so I will continue to encourage them give them the information they need we will be watering them as well um so uh orchard just desperately needs trees sweet you have two more trees there that might need to come down one definitely um and I think we have some stumps left to grind but I mean that's that's an option Greenwich and Long Meadow believe it or not most of those would actually be private trees they'd be setback plantings um the right way there is not um conducive for tree planting in the grass area because of all the utilities everything is um there's sidewalk on one side and it's too narrow to plant trees and then on the other side all the utilities run underground in the grass belt so we can't can't plant in it so they'd all be setback which can be done it's a little more complicated so which are we doing in May are we going to do uh orchard street or do we have something else in mind yeah yeah I mean we could do orchard and uh hop back over to amity street or something like that there's a few more locations on amity street that might I could use trees um I could also talk to um embers college and get some permission to do summer northampton road they may have pulled back some of the construction project by May um so we could actually plant some of the stuff on northampton road in May that would be great I know we've done a planting on McClellan so that's all set but what about going on thuring ab the fairy ab is another one desperately needs trees they've lost a lot um tough side you know the side with the power lines you know there's no sidewalk over there but there's you know we can't plant under the power lines they're very successfully with any sizable tree without going on private property um and the sidewalk side there's no there's no room you know in the public waiting plant just a narrow grass belt I do want to plant there it's a little more challenging than orchard I think I think orchard and northampton road would be because it connects to one another you know um would be a good a good place to go so I'll start I'll start working on that talking to embers college and see where we could plant trees you know on their property they own most of the property and from like orchard up to the center um those are all embers college properties yeah all right why don't we um plan that for the May planting I may not be here for that planting so hopefully the rest of you will all come out it's on May 13th for the day all right um so it's a town budget line item I was supposed to write a let it to the editor and I have not done that I will try to get that done I've just not been writing lately but I will try to write that so I apologize um UMass interns that's also Brit so we'll postpone that tree nursery nothing much to say right now I think that's a longer term project but I'd really be great if some of you can go show up at the um the greenfield tree nursery if you need the location I can I posted it on Facebook um but if you need the location contact me that's the Saturday um and then is the old stuff anything new on the town tree nurse tree inventory on no update on that I um I spent most of my time working on the embers history tree that part of the grant getting everything buttoned up so I can get it all build out and get everything accomplished so um June 1st is deadline for submitting all the application for reimbursement for the grant um and I'm trying to pull together slowly that the inventory information so which may may I'm just going to have to hit the inventory really hard um so and when uh when is the work going to be done on the tree on the big uh second one yeah probably uh last week of April first week of May somewhere around there looks like it'd be interesting if how that affects the April 28th date shouldn't shouldn't interfere either way okay all right uh that's good I mean we're getting we're making through some of these some of these things are on the agenda and they take forever but the history museum grant and all the work is actually happening it's very exciting um next thing on the agenda state state level initiatives and I haven't done anything about that lately um I am still in touch with Joe Comerford and Mindy Dom and I will continue to stay connected with them significant tree ordinance Sarah anything new on that you can shake your head if oh okay and I I'm sorry for the minutes um Alan the you said a June 1st deadline to submit reimbursements that's for that's for the dcr grants we got for the immerse history museum tree work the heritage tree grant we got for that and then we also got a dcr grant to update our inventory um and develop a management plan urban forestry management okay thank you yes I see your email Mary and I will add that great thank you all right um the only other thing is um the solar action committee we talked about that unless Julian you have anything more to add about that no okay I think we're more or less done with the agenda unless anyone has anything else um let me just look at it one more time make sure I just bleed it no all right so there's no topics uh not reasonably anticipated by the chair so I think we can end the meeting before you do Alan let me just grab this email address I could um I'll just add that um if anybody knows of somebody I've already talked with Julian who is looking for gainful employment over the summer month we um are trying to attract seasonal employees for the summer um we still have a vacant position full-time position in our division um that we just haven't been able to fill for the past uh five months six months so can't find people to work crazy yeah um question about that uh on the form it said under it said are you under over 18 I clicked under but I'll be over 18 when I begin work will that be an issue no that won't be okay great awesome and you guys are pretty short staff basically what I'm hearing well we're short staffed by one person one full-time employee yeah so how how old do you need to be for the summer work uh we strive for someone to be 18 um we have taken people who are 17 I'm told in the past um it's these are basic seasonal labor jobs my son is 16 so probably too young I was hoping to apply last year when I was 16 but I felt I was a little young so okay um yeah did they just reach back out to me for an interview uh I didn't get an email or anything so is that all that work so yeah well you should get an automated email that your application has been received um and then it gets this it'll get sent to um if you're depending on which boxes you check it'll get sent to DPW and then um all the divisions in DPW will look at it if you selected any particular division like tree and grounds um then I'll get a you'll get sent to me directly otherwise it gets dumped into a pool and we we comb through them got it it didn't have a space for me to set anything specifically which was okay so I don't know but you'll probably eventually see it you've seen it yet I'll look for it I'll log in to the for the system and see if I may have gotten an automated email I did not check so I will look for that okay all right um I got your email addresses and I think we can end the meeting awesome thanks everybody and thanks everybody I'll send an email around about signing up to take shifts at the Stain Building Festival and I will see everyone there that's probably the next yep media event yeah thank you everyone bye bye thank you bye bye you


Okay, so I did a video like last year about a travel PA and we were just talking about you know What it's like to be a travel PA and is is it even a thing? Um, and so I introduced you guys to locum tenants if you didn't know about it But uh, I had a question that was asked and it was asking kind of a similar question to being a travel PA Um, but essentially wanting to know kind of what do we have time to do? Okay, in your PA life as you're working like do you even have time to travel? So that is what we're going to be getting into in this video What's up you guys the donna welcome back to my channel So I had a question posed by Jalen Jackson and says hey, thanks for the video I never found information online and this is giving me the motivation. I need it I was wondering what if I really enjoy my staff job But want to travel often do PAs get the time off to do those such things Or is it better to just become a traveling PA rather than take the risk of not doing what I really what I enjoy Thanks, Jalen all right, so thank you so much for this question and Honestly, like it comes right at like a really good time because that is kind of the space that I'm in right now so I first want to apologize to you guys because I haven't put out like my second video in the past couple weeks in terms of my Live sessions because I've been working a lot of extra shifts now With that being said I'm going to like make some concessions. So Tomorrow I will be doing a live because I'll be working. I'll pick up another shift on Tuesday So I'll do a live tomorrow and then I will do a live again on Wednesday night Wednesday night, maybe Thursday night, uh, but just you know, stay tuned to the channel So go ahead and subscribe and uh and and hit the notification bell So you can know exactly when a new video is coming out But it will be on one of those days just because I've been Doing a lot more And so with that being said Jalen like to answer your question Yes, you know PAs do have the time to do that, but it all depends on your schedule And so now I told you guys before like there are various different types of PA schedules and just schedules in general In the healthcare space so you can work three twelves. You can work four tens. You can work five eights You can work three twenty fours in a fourteen day period. You can work four twenty fours in a fourteen day period You can work a nine to five So it's really up to you. There are lots of options But the ones that lend the most to travel are like your three twelves Your your three twenty fours your four twenty fours And I mean, you know, if you're just doing like a little weekend trip here and there Then, you know, your four eights might work as well now for me I do three twenty fours for the most part sometimes I'll pick up an extra shift like I've been doing Um or an extra two shifts, but I still have like seven days off or six days off like in a long stretch Where I might work like a sunday and then a Tuesday and a thursday if I want to work back to back to back And then I don't come back to work until like the following not this the upcoming sunday, but the sunday after that Um Or you can spread it out and I work sunday thursday sunday And then I get that whole week off and then I'll come back again until the sunday So it works out really well for me right now Um and it worked out really well when you know COVID had hit hard because I was homeschooling my kids And so I needed to be there to actually like teach them So I would work sundays and thursdays and I would have pretty much all week to do like homeschool with my children um and then we'd also just take random trips because They're being homeschooled so I can teach them anywhere and if I'm off for like Days on hand and my husband works from home like it just worked out really well So yes, you absolutely can do that. It's all a matter of you finding what works for you So like right now I'm about to go on like a little mini vacation for the next two weeks Um, and I'm excited about it And I'm working a couple extra shifts as well because I'm gonna be planning another vacation in april Um, and I plan on going somewhere in june and in july and august So this is like, you know, I I want I want to live my best life, you know, I worked hard I went to school. I studied a lot. I spent a lot of money Um to live this life right to be able to enjoy traveling enjoy experiencing new things but at the same time still loving what I do as a pa um and helping people in some of their toughest moments as a trauma pa so Yes, you absolutely can do it. Um, again just find what shift work Works best for you. Um, I think it's you know, like these 24 hour shifts are kind of few and far between So even if you can do like three 12s, that will work as well I think that will give you enough time to kind of have like mini stacations or, you know, a longer weekend Where you can travel and visit friends and visit other countries and, you know, do your thing All right, so I hope this answered your question If you have any other questions for me, you already know what to do leave your questions in the comment section below Join me on tomorrow And then again on once day or Tuesday for a live and I will be talking about one of the schools that you Asked me to review and I'll keep you posted on if I changed the date But I will make videos. I put videos out typically every Sunday and Tuesday. Okay, so join me back You can always subscribe and like this video Follow me on instagram and on the pa and on instagram and get that see university. Thank you guys so much for watching I will talk to you guys next time