The narcissist pretends to move on. It may seem like the narcissist has managed to forget about you overnight. As though they have moved on. As though they're having fun while you're suffering. Maybe they've got a new boyfriend or girlfriend. Maybe they've got a new job.  They try to make it appear as though you're missing out on something. When really, it's just an illusion. It's a deceptive appearance and oppression. And it's designed to give you false ideas and beliefs. It's designed to make you believe it's something that it's not. So that they can get the reaction they want from you. And then feel better about themselves at your expense. They want you to think that all this stuff is happening without you. As though you're missing out. As though they're having a great time and you're not a part of it. And you're left alone, miserable and suffering. Thinking that you're missing out when you're not missing out on anything. It's just an illusion. It may look like they have a new boyfriend or girlfriend. It may look like they're so much happier without you. But it's an illusion. Just as it was when they were with you. People thought that you were happy. People thought that you were having a great time. They didn't see everything that you had to go through. They didn't see what the narcissist was really like. Everything good you experienced with them was just love bombing. It wasn't real. The entire relationship was fake. And even though it may look like there was someone else. It's just the same thing again. They're not really happy. They're not really having a good time. There's no such thing as a relationship with a narcissist. Because from the moment you meet them they're being fake. They're mirroring you and giving you a deceptive appearance. They're not showing you who they really are. So you're not getting to know them. You're not establishing a connection. Because they don't even care about you. A relationship is the way in which two people are connected. But narcissists cannot connect or relate to you or anyone else. Because they're self-absorbed and they lack empathy. They only care about their own needs. Which makes it impossible for them to build a relationship with anyone. Because empathy is one of the most important qualities of a relationship. Without empathy there is no relationship. They were only involved with you. Because they wanted something from you. It made them feel good. And that's all it really was. They might have said they loved you. They might have said they cared about you. They might have told you that they wanted to marry you. Or have children with you. They might have said that you would live together. And go on vacations. But that was just future faking. Those were just false promises. They just used the relationship to make themselves feel good. It was all fake. They mirrored you. And reflected back to you everything that you like. Everything that you're interested in. So that they could get what they wanted from you. It wasn't real. Had any new relationship they're in. It's exactly the same. They don't love the person they're with. They don't care about them. They're just in it because of how it makes them feel. Because of what they're getting out of it. The narcissist pretends that they have moved on. They pretend they're happy without you. They pretend they're in love with someone else. But if you remember your relationship with the narcissist. They never had any love to give to you. It's all fake. It's all a lie. They're just using people. Just as they were using you. They created an identity. From mirroring you. And that's what they then used to attract the next person. They use it to lure people in. So that they can get what they want. But the narcissist isn't giving anything to them. Because they have nothing to give. When the narcissist displays these illusions to you. You may think that you miss them.  But remember it's just an illusion. That's not who they really are. It's fake. Just as it was when they were with you. Remember how they treated you. Remember how they reacted anytime that you tried to confront them. That's who they really are. And that's never going to change. They're always going to be like that. With anyone they're with. They would love for you to think that they've suddenly become everything. That you've always wanted them to be. Or that they're treating someone in a way. That you always wanted them to treat you. But it's just not true.  They're so envious and jealous of you. And that's why they push you away. They only care about getting what they want. And once you've figured them out. Once you've realized what you were dealing with. They're not going to be able to get what they want from you anymore. So they have no choice but to move on to someone else. But they're not really moving on. It's just an illusion. It's designed to make the new person they're with. Think that they're building something significant. And they're also using it to hurt you. And make you think you're missing out. They always have to tell you or show you what they're doing. To try to get you to buy into an illusion.  So they can get narcissistic supply. But really. They're not doing nothing. They're just as bitter and resentful as they always were. Nothing ever changes with them. You could leave and come back in 10 years. And they'd still be doing the same thing. The narcissist pretends they've moved on. They pretend like they're so much happier without you. Because they want to hurt you. They want to make you think that you're missing out on something. But you're not missing out on anything. It's an orchestration. They plan and coordinate the elements of a situation. To produce a desired effect. Because they want to be something significant to you. They want to be something that you might want. They want you to think that there's no other option. When really, their world is so small. Their group of friends or family are not as significant as they have later to believe. They want you to keep thinking about them. Wondering what they're doing or who they're with. So that they can control you. So that they can keep you focusing on them. Rather than focusing on your life. They want to trap you. So that you spend all of your time watching them. Pretending to have fun. Making you think you're missing out. It makes you think they have everything you want. Because they've taken control over your world. When in reality, their world is so small. Their world is insignificant. And the grand scheme of things. But they pull you into their world. They trap you around their people. So that it's all you know. You don't realise that there's so much more waiting for you outside of their world. It's only when you step out of the box that they created for you. That you then see the illusion. That there's nothing for you. Or that the world is against you. When you separate yourself from the narcissist. You will begin to see the bigger picture. You will begin to see what's really going on. When you detach from them. You will see how small their world is. When you're around their family or friends. It feels like you're stuck and you can't get out. But they've just tricked you into thinking that way. Just remember how big the world was. Before you met the narcissist. There were so many different people. So many places to go. So many things to do. None of that has changed. The narcissist illusion. Is that none of that stuff exists anymore. But it still exists outside of the narcissist world. You've just been trapped in their world for so long. That now you see it as more than what it actually is. The narcissist isn't everything.  They want you to think that their world is so big. And they know so many people. So they can keep you under their control. But it isn't. Their world is small and insignificant. It's full of narrow minded sheeple. And outside of their world. There are so many people for you to meet. So many more opportunities. They want to restrict you to the confines of their world. And with their rules. And when you get out of there.  And you travel the world. And see new things.  And you will find that you don't even need them. Thank you for watching. And I'll talk to you soon.


All right, so release testing. First of all, thank you very much for a wonderful team. Alireza, Brian Cameron, Jennifer, John Shilton, and Lila. So first a brief overview of how we do release testing. It changes every cycle, every release cycle, but roughly we have the same process. So we test against usegalaxy.org and we use local instances whenever necessary. We have a formal detailed release testing plan which outlines a formal protocol which specifies what we test, how we test, how we determine whether or not an issue is indeed an item of concern, how we open issues, how we verify that something has stemmed as a result of the current release and not something which has been around for ages. This helps us keep on track with testing everything which we initially planned. We communicate via MATE Matrix channel for release testing. The channel is public, so this is a link in the slides. Please feel free to join anyone who is interested. The channel is more or less inactive between releases but during the release testing cycle it's quite active. The primary goal of the release testing team, well, there are really two goals. The one is the goal of the manual testing. The other one is whatever automated testing activities we come up with and we have one this time. The goal of manual testing is essentially test everything we can, we can stray off the happy path, try to do whatever a user might accidentally do and discover bugs which are not discoverable by or very, which are very difficult to discover by automated means. So we discover these bugs and whenever we find one we open an issue on GitHub. And of course at the end we summarize the result and present them to the community. The scope is for manual testing, we focus on two areas, requirements-based testing and scenario-based testing. So for requirements-based testing we use the highlights for the release notes. These are the key items which make the current release. This is what we put forward, this is what we advertise. So this is our highest priority. We try to make sure that the items which describe the release actually work as described. Pool requests, we use pool requests which contain manual instructions for manual testing as well as pool requests which are labeled as UIUX. It's a curated list. So we select out of this master list the tests, the PRs which are actually testable and which makes sense to be tested manually. This is our well loosely based requirements-based testing. Then we have the tutorials, the tutorials, GTN tutorials. We use them as scenario-based testing. So we use them as sets of paths a user might take when using Galaxy in the wild. So these are the paths we take and these are the paths we try to leave in creatively trying to break Galaxy. The timeline was usually one week. Usually the week right after freezing we have three to five, four to five team members and it takes about a week, two, three, four, five days. And a special thanks goes to volunteer testers. Thank you Volskan, by the way, this time help was most appreciated. What was manually tested? So the release notes highlights, these are the areas we paid special attention to. So tool search feature, tool search and advanced search updates, the history drag and drop, tool form improvements, theming support which is not enabled by default on usegalaxy.org. So we tested that using our local setup, global drag and drop, et cetera, et cetera. We tested, first of all as a disclaimer, we never are able to test all the items which are on the list of items to test. That said, the proportion of items tested is really a function of what we decided to put on the list because we degenerate the lists. So this time we had a list of 64 PRs with manual testing instructions and 65 PRs which had the UI UX label and which were curated manually as to be most likely a reasonable subset to test manually. So out of them, we tested 49 out of 64 and 17 out of 65. The GTN tutorials, well, we've covered 21 tutorials and again, it's not about the quantity of the tutorials, it's just suggested scenarios which we follow. Opened issues. So the next slide will give more details about how many issues and what types of issues were opened. This is a rough overview of them and this screenshot includes not only issues opened by the team but also issues opened by the volunteers who took part in the testing. Again, thank you for that. And now moving on to Ali Reza. So hi everyone and thanks, John. So I'm going to give you some information about how's the opened issues and how the portion of each. In total, we have 37 opened issue from different areas, terranium, galaxy and tools and mostly for the galaxy. And next slide please. Yeah, so if we want to compare them by their technical category, we have mostly more than 80% opened issues for the UIUX area and API in the following and tools and accessibility. It means that we have to focus more and more on the UIUX bugs and fix them in the future. So next slide please. So if we want to categorize the opened issue by their area, the most important area was the history and then the workflows and tools and et cetera. The history is the main key of the galaxy and mostly have the most issues for them and then for the workflows because we made great changes to the workflow during this release and because of that, we found numerous bugs related to workflows. If I want to give you some examples about how these issues are important to us. In the next slides, we are showing some examples. For example, we found an issue by using drag and drop and multi-view history together because as you saw in the previous slides, we have two great feature in this release that's the multi-storey view and the global drag and drop but we found them have some conflicts when we are in a multi-storey view and we want to use a global drag and drop together. That's one of the important issue we found in the UIUX area for example and in the next issue. Next example issue was related to the workflow editor because as we were testing it, we found for example, we cannot connect some of the steps together or in a correct way or in the next example, it's again related to the workflows, the data for the workflows are not seen. I mean, for the input and outputs, if we want to filter the history items by the input and outputs for imported histories and it's not available and we should address this issue by for example, disable this filter or explain the user why it's not available for imported history because they are based on the jobs. And last but not least example here was about the new data types, page renders an empty table this makes, maybe it makes the user confusing about what's going on with this data type page and so on. Okay, that's from my side. Thanks, thank you Alireza. So a few observations and thoughts about these bugs, Brian? Yeah, I just, I'll go over a couple of things that during my camera on that I noticed while of course there's some new additions to the UI and one of the things I spent some time doing is kind of going over some of the older tutorials that a lot of like first time Galaxy users might use. Just off the get go, I noticed that there were some of the screenshots were outdated in most cases this isn't vital, but if you're sort of like new to Galaxy, I might be confusing when you're trying to follow things step, sorry, follow things step by step. Among them I noticed some of the icons look differently and as far as like where they're at, for example, the refresh history button, how you edit your history name, before you just go in there and click and type what you wanna name it. Now you actually click the edit button and edit the name plus other attributes. So again, generally minor things, but for new users it'd be good to have more recent pictures which the tutorial owners went ahead and updated these images. So now everything looks the way it does in the new releases. Next slide please. One, I found a couple of cool new additions and to be honest with you, one of them was this new, the second run tool. Well, for one now it says run tool before you says execute and I think it's more sort of like direct for users know what you're doing here, but also there's an additional way to run a tool before there was just the one at the bottom. So you have to scroll through all the different tool options and then run it. Now you can just do it right at the top. Now this is really useful if you're just trying to rerun a job exactly the way it was before or perhaps only changed like an initial setting like your initial input file and just do it quickly. Some of the tools we have on here have like loads of options and settings. So it's really neat to just like quickly rerun something. So A plus on that whoever developed that. Next slide please. I also spent some time with the interactive tools particularly Jupyter lab, which is really neat to have. We're actually a working good bid with one form of this tool here in the Blankenberg group. We're trying to import Kiskit which is a software stack used for one computing using Jupyter lab. But I did notice a couple of things. One of them was it, and again I don't know if some of these issues are sort of like on the service side a problem with main or perhaps on the release itself or perhaps on the tool itself. But I did notice that you can't save the notebook back into your Galaxy history and you're also unable to import history items. You could give it the command saying get and then your dataset number from your history but it didn't actually import it. Can't really see the resolutions, not that great. So I apologize for that. But what happens is after you give it the command to get a history item, it doesn't import it. It just says import and then backslash whatever number you gave it. So I found that out. And then I also, one thing that I also found is that like notebooks won't stop running. They're actually still running right now. Even after you kill the interactive tool it still shows up in your history as running. As you can see here on the image on the left. Again, I don't know if this is an issue on the server itself. Things are a little bit bogged down and running slowly but it's just something worth noting I suppose and now certain things though like if you use matplotlib in the notebook and you generated graph and save it as a PNG file that was able to be saved and sent back into your history, no problem. So that was successful. Next slide please. So the new history layout. So I got a, I guess a couple of points on this. To be honest, I found it to be a little bit more difficult and less intuitive, particularly when you're showing multiple histories. You have to sort of like an extra step that you have to take and your current history isn't automatically shown.  So this sort of like adds an extra step and it just didn't really seem too intuitive. Like you open, you show your history side by side and then nothing shows up and then you have to start picking what you wanna see rather than just showing everything all at once and your current history at the front. I feel like, and then this is just my opinion, man. I feel like how it was in 2205 was a little bit more intuitive. So I also, like Alizarra mentioned earlier, I had issues dragging and dropping history items. So in this setup, when I show them side by side and I tried to drag an item from an old history into the current one, the icon or against the screen would show drop here but like I would drop it and then it actually wouldn't happen. So it wasn't actually copying the datasets using the drag and drop feature. So that's kind of what I have to say on the history side of things. But yeah, next slide, I think that's fine. Yeah, that's it. Thank you, Brian. And John is going to talk about deployment testing. Super exciting stuff. John, are you there? I see him drawing. Oh, sorry, sorry, sorry. Yeah, I'm technical difficulties. I drew on the screen as I turned on my microphone for some reason. All right. So one thing we did this release cycle was sort of make some progress on a task that we've talked about for, for as long as I've been on the project and that's deployment testing. So the idea with deployment testing is that most of our tasks we run in CI as a result of pull requests and deployment testing as the sort of the act of running tests against the running server. And so in this case, I was using usegalty.org. And so it's running our existing tests against usegalty.org. In theory, in the future, we can sort of develop tests specifically for our public servers and that'd be great. But for right now, it's mostly about running the tests we already have, the ones that make sense. And so that includes a lot of our API tests and a lot of our end-to-end tests which are currently implemented in Selenium. Yeah, and so the idea here is to run those tests and see how the deployed Galaxy is working. Hopefully, I'm sure this will be a valuable resource for other people deploying Galaxy. Now there's, we have, you know, hundreds, not thousands of tests and there's some serious limitations to what we could do with deployment testing. So like a lot of our tests depend on like highly specific Galaxy configurations, right? So we have two whole like sections of integration tests and all of our unit tests, for instance, that don't make sense to run against usegalty.org because it's just not in the right configuration. And so of the appropriate tests, you know, a lot of them are sort of currently factored in such a way that we wouldn't wanna run them on main because they require an admin key or they assume you got a new history. Every time you start a new test or they do a login of a new user, but there's a bunch of tests that do run and I did get running against usegalty.org and then I have a note that might turn into a GitHub issue but, you know, there's a bunch of things we can do with the existing tests to make them more compatible. And hopefully this will sort of, this process will make it so in the future as we're reviewing PRs and such, we can sort of, you know, think about tests in terms of how we could, you know, get the most bang for a buck out of them when we're running them against main. Yeah, do you wanna head to the next page? Yeah, this is just a little, I did a GitHub action. So these tests, you know, you have to go in and launch them. They don't happen against every PR. So if you click actions and deployment tests, it's probably only something repository owners can do, but if you've got a clone of Galaxy, you can certainly just modify that file and run it against whatever server out of your own branch. And then up here, you've got this little dropdown for how GitHub actions lets you parameterize your tests. So right now you can run either API or Selenium tests or all of them. Yeah, and I've got a few different servers plugged in there. And then you can select what branch of code the test is coming from. That's the GitHub option at the top that GitHub provides. And then like within the action, which set of tests you're cloning out. So usually both of these are just going to be devs. But yeah, so that's where that's going. Right now the output is just a pie test, you know, you just got to scroll through and look at pie tests and figure out which tests are failing and to do the debugging. Hopefully in future releases, we will improve that and we can, you know, use stuff like the HTML plugin and we'll make this process better documented and easier, but this is just that sort of initial experiment and getting the plumbing down. Next page. Yeah, so that's what we've accomplished. In the last couple of releases, we did a better job of like annotating which tests require admin users or new, too many new histories trying to main that sort of thing. And but then this release, we got the GitHub action down and we built a list of useful tests that I think will basically run against main in the future. We caught one of the issues that was the manual team already caught and that's the zip files, not downloading for collections. So the tests, you would expect these tests would be things since they were run on PRs that for the most part, you wouldn't expect a lot of failures. But even this sort of first initial pass caught something and that has to do with the fact that how we were served that zip file is very dependent on Galaxy's proxy configuration, the backend configuration and those things can vary. Those things are very different between main and the test environment. So over the next couple of releases, hopefully for the next release, I'm gonna sort of continue this process. So hopefully I can run the release testing before the release and then after the release is deployed so we can sort of start looking for regressions. And Bobby mentioned improving the reporting and the testing and documentation. And then as we're sort of growing the number of tests, I think it's gonna be another key thing. So improving the existing tests and growing the number of tests that we do run against main, I think will be helpful. And then past that as we've sort of solidified the process and it gets better, we need to develop a plan, I think for, not we don't need to, but I mean, I think it'd be nice to develop a plan for integrating this into part of the deployment process. So if we can, even before the manual testers get involved, if we've run all the automated tests and found a bunch of bugs that we can fix or found no bugs, then it's easier to sort of hand that off and say, we think that this is at least in a state where we think that golden path or the main path works. And so hopefully that will just ease the process and make things more stable. Thank you, John. This won't just ease the process, this solves like 50% of the problem that we keep going over about manual testing. We keep saying that, hey, we need to automate this one way or another. And finally, thanks to John, we're actually doing it. Well, John is actually doing things. So a few notes on the release testing process itself. So we try to learn each time. So the lessons learned this time is we won't plan to start in mid-December. Merry Christmas and everything doesn't work well with release testing at the same time. We're not gonna start on January 1st either. January 2nd is out, so we'll do better with that. We will try to form the team in advance, well in advance, two, three, four months in advance. And of course we'll stay flexible. So if something unexpected comes up, we'll find a replacement, not to worry. But I suppose it will be much easier both for the release testing process and most importantly for the people who are doing the release testing to plan ahead and to know that, okay, that will be a week, roughly three months away when I will be one of the people responsible for making sure the release works. So these are the changes for the planning process. We try to look back each time we plan a new release testing cycle. We try to learn from previous experiences.  First of all, we introduced the release testing label on GitHub last release to make sure things did not get left behind and lost. So it worked. It works pretty well. At the beginning of the release testing cycle, we checked there were only two issues still left which had the release testing tag from the past release. One of them was already closed. One of them is still open. It's sort of like a wish list kind of item. So I wouldn't say it's a problem. So in that regard, we're doing pretty well. So we are going to leave the release testing 23.0 label on GitHub and hopefully next release testing cycle. There will be very few, if any, issues tagged with that label. Implemented works well. So this is not specifically from the previous release cycle. This is a combination of recommendations and feedbacks from all the previous work cycles. So one of the types of feedback we got was always we need a more structured testing plan. So each time we make it more and more structured, this always helps. It helped this time, I think. We open issues aggressively. That means that we don't try to fix the problems we find because again, as practice shows, when you do that, you get stuck on an issue. It takes you down the garden path and you miss opening 10, 20, 30 other issues. So we do that. We keep trying to reduce the list of PRs to relevant PRs, relevant to manual testing and relevant. We try to keep the list limited to the PRs, which actually are worth spending time on. And in that regards, what John just went over with deployment testing is going to hugely help this particular problem. And of course we prioritize release nodes because these are the key features which must just work. Still need to address still too many items to test. So again, we try to manually curate the list of items to test it's still too much to be handled by a team. And it's not a problem of the size of the team because if we add twice the number of people, there will be still too many items to test. And if we spend a very little time on each item, we can test them all, but the quality of course will go down. So the key here is to still keep narrowing down the item, the list of items to test to those items which are definitely not automated, not automatable. So those items which do require human attention. Oftentimes it's not clear how to test an item. What this means is that sometimes a feature will be not available on usegalaxy.org for whatever reason. We resort to local instances. Sometimes the instructions are not clear and I'll get to it. Sometimes it requires admin access. Sometimes it's a backend issue or requires a change in configuration. So we need to address those better than we currently do. And finally, we cannot do side-by-side testing of select items when we want to compare whether or not the item that the bug or the issue indeed occurs on the previous release. We've discussed this forever. It's not easy to implement, but if we finally get to setting up tests alongside main with a similar setup within reason, that would be nice. Then we could resort to running stuff on test when we need to double check what's going on on the previous release. How the community can help. So first of all, manual testing instructions. They are used for two things. One, we use them to automatically generate the list of PRs which are worth testing. The list of PRs is very long. So that checkbox, which we added about a year ago helps a ton. And also they are used to conduct the actual testing. So first of all, if you think that your addition, your new feature or your fix needs to be or could benefit from being manually tested during the release testing cycle, do check that box. Otherwise, there is no way it's going to be manually tested. The process of selection is automated. And another point, if the box is checked, please, please, please include the instructions and make them clear. One of the observations from a previous release testing cycle was that many of those instructions were written by experts, by domain experts, for domain experts. So they have to be clear so that any member of the testing team who may be a developer who is who works in the front end or a developer who uses only, I don't know, the back end. And it's not familiar with this or that particular item which is described in the PR. Maybe it's a user. I hope we'll eventually get diversified teams, tester's teams, where there will be both developers and maybe admins and users. So these instructions need to be clear and very specific. So again, we have a lot of PRs to test and the clear set of instructions helps very, very much. And a few more points. So release notes. Release notes is a chore. It takes a lot of time to write them. They, it's not easy to generate them automatically. We can work without them. So what we do is we look at all the PRs which have been tagged with the highlight label. And based on these PRs, we make a list of key features which probably will make it into the release notes and which probably deserve our primary attention. That said, if we have an actual description, actually an actual text describing each feature, that simplifies the work of the release team tremendously because then the testers can actually focus on figuring out how to test a given feature and not spend time doing galaxy code base archeology, looking for relevant PRs and issues trying to figure out what exactly that feature is supposed to do. So if, and again, there is no easy answer to this question. Generating writing the release notes takes a lot of time. So maybe we can figure out a way so that other teams can help with this. But if we can have those release notes before we start testing, I think the testers will be able to test more and well, we'll be able to be more productive. So that would help. Let's see, improving list of items for manual testing. Differentiate between user-facing and admin-facing items. Again, some of the items are definitely UI UX related and can be tested against usegalaxy.org. Some of them require backend access. Some of them require admin access. So maybe it makes sense to put some more thought into specific labels we could use to tag all the PRs which need to be manually tested. I don't have any answers or specific suggestions at the moment, but maybe this is something we could think how to improve. And another point, Cameron made this suggestion and I don't know how workable is that, but it sounds pretty neat. So I wanted to share it with the community. So can we generate a component dependency graph for the UI so we can, well, automatically see which features should be tested when a particular component has been updated, especially for abstract components that expose a variety of use cases like the form text.view. I don't know how feasible that is. My guess not feasible at all because the mapping itself between view components, the set of view components and the set of things that should be viewed by a user or an admin, we don't have that mapping, I think. And that would be a challenge, but the idea is neat. So I wanted to throw it out. And that's it for us. So again, thank you for the team and thank you to the team and thank you for bearing with us and questions, what can we do better? Thanks so much for that presentation, John. And thanks so much for the release testing team. Do you want me to stop sharing?  One thing you noted in the things that are going well is that having a good structure for the release testing is really beneficial. Can you describe a little bit about what that structure looks like? Yes. Yeah. In fact, how about I share the screen real quick if you don't mind and I will show something. So let's see. So we have a release testing plan and the release testing plan outlines all the steps of the release testing phase, what goes into it and how we do things. So we have a summary of tasks, which explain what we do and why we do that. And then say we have this GTN tutorial scenario-based testing. So it explains why we call it scenario-based testing. We have a section here which explains when to open an issue and when not to open an issue. I remember when we started with this approach about two years ago, we would open issues for absolutely everything. And as a result, we spend hours upon hours upon hours testing one given tutorial and finding all the possible faults, literally going as far as the background color on the screenshot is outdated. So it might be confusing because the current color combination on Galaxy has changed. And that took 99, like 90% of our time. So because of that, we tried to map out, well, what is an issue and what maybe is not an issue. So these kind of examples, straight away from the happy path again, we tried to make sure that the testers keep that in mind that following the tutorial basically is duplicating what a script can do. And maybe we don't have all the scripts we want, but still it's an automatable task.  So we map it out here. Then we have release notes, requirements based testing. And again, it's loosely based requirements based because we don't have a preset list of requirements which must work, but well, a list of PRs and highlights is as close to as good as it gets. So we explain how to handle those. Then we go over about how to record bugs. And actually this release testing plan is a little less detailed than the previous one. We've sort of trimmed it down. So it doesn't look as boring as scary, but it still provides this set of steps we try to follow. So that's how we do it. And that's only for manual testing. So we also have the automated testing component and that's a different story. Awesome. And I assume there's like a sheet with all the specific tutorials and that gets broken down by the group of testers. Yes, we have a, let me, let me again show it so that the community knows how we handle this. We have a Google Drive, a folder on Google Drive, which has several documents and the most probably the one which is the most important is this Google Sheet. Just a moment, I'm trying to get rid of Zoom there. So we have a Google Sheet which lists the highlights which we are testing with all kind of relevant data, opposite each highlight. We have a list of PRs, which has the description of the PR, the status of the PR, the labels. So that whenever a tester assigns a PR to themselves, they know what that PR is about, what areas of galaxies it deals with. We have a list of tutorials and this list we treat as a list of suggested tutorials. So if someone wants to use a different tutorial, for example, for science tutorials, we used to have specific science tutorials. Now we just have any science tutorial as long as there are three. Then we have a list of open dishes. This is where we post stuff which we open and whenever we can link it to a given PR, which is currently in process, which is fixing the issue. We do that. We also have semi-structured notes. We have structured notes here for each open dish here. And in addition to that, we have a Google Doc, actually two Google Docs with notes, which we use for discussing stuff which does not logically fit into the release testing channel, for example, or the end slides. So that's how we discuss. That's how we keep track of what's being done. Thanks. Any other questions or comments? So this was really great. Thanks for doing all this. I guess if the plan is to start arranging the groups about three months before is now the time to start the next group. Yes. Awesome. We have a spreadsheet. So the selection of candidates, potential testers is semi-random and we tried to keep it. It's a super useful task. It can be fun. It's also a chore. We all have our favorite coding projects we are working on, which are super important. And this is more fun than sitting and testing the next PR in a list of 100 to test. So we're trying to be fair and we have a spreadsheet which lists all the release testing cycles starting with 2009, I believe, and all the names of people who have been testing each cycle. So when the next release testing cycle comes up, we look at that spreadsheet and try to find who has not been a tester yet. And if I think the next release is actually the first time when we have to roll over and someone will do release testing again, because we have so many team members. So once everyone has done release testing, then we go to the pool of those who have done release testing years ago and we do a random selection. And then based on availability, we adjust. And then just from a coordination standpoint, for the release and the testing and the deployment, is the plan to have that out before the GCC? Yes. Okay. That's going to be a couple of busy months, I guess, right? Yep. Yes. Awesome. Thanks a lot. I guess normal questions. Thank you again. One more comment maybe. You mentioned something about kind of adding specific tags about what needs to be tested manually, or guess what's more user facing versus what is more admin facing. Is there like a particular process to go about adding a certain label? Does that kind of depend on folks adopting those labels? How can we kind of move that into reality? Well, I suppose first we need to give it a thought then the committers agree that a new label indeed makes sense.  So we try to be very careful about when adding a label. Then we add a label and there is no formal process about introducing the label to the community and having community adopt that label. But since in this case, we would be using them to tag PRs, which should be tested manually during the release testing phase, I believe we would need to somehow convey to the community of contributors so that they start using these tags. And I don't see this as multiple labels. I'm thinking one or two to differentiate between needs to be tested. And this is user facing versus needs to be testing admin facing or maybe needs to be manually testing. But hey, this is backend related. An example of that would be I can think of our recent work on changing the migration system. Lots of manual testing steps there and that was an important manual testing tasks specifically during release testing to ensure that there were no regression bugs, but that's not user facing. That's not even admin facing. So that's 100% backend. I mean, we found this while deploying. So it was 100% admin. It happened to be okay. I suppose you're right. I suppose, yes, I suppose that would be 100% admin facing. Maybe I'm wrong. Maybe there are no pure backend items which would require manual testing. I mean backend which I'm not admin facing. With a lot of the bugs found being UI UX. Do we need to invest more time in integration testing? So, I mean, we only have Selenium. It's what's the feeling on that? Would it help to have more tests that extend beyond testing components in isolation? As John pointed out during his talk on deployment testing, if we can automate the happy path, that would be super. I'd like to do a retrospective and sort of categorize the issues that we did create from this down the road and think about how, obviously, yeah, I mean, more testing is always good, right? But I wonder if, so just quickly glancing at this. I don't think a lot of the UI UX type issues that we did find. That's not something we would see in testing, right? Most of these. Global drag and drop which turned out to be a regression issue and that happened not when it was merged, but after a different feature was merged on top of it. That could be automated. That type of thing could be automated, I think. Yeah. Would you definitely catch a few? I mean, generally, a lot of these are more look and feel kind of, you know, stuff that we'd catch that way. I mean, the goal, the holy grail is when the happy path is completely automated. Like, and the testers, the manual testing is only used for discovering stuff which is not scripted, not scriptable. Yeah. I mean, presumably the tutorials are all potentially scriptable right now. We don't have the resources to get there, but if they each had a tour and we figured out different ways to automate that, et cetera, et cetera. One could imagine someday getting there and then hopefully the manual testing would be just like A-B testing on main. We give Jen and a couple of power users access to, but yeah, we're obviously a ways off from that. I mean, it's for the bugs that I fixed for the release. I mean, they were all in the work for editor and I think all of them resulted in me adding, I think mostly integration tests, selenium tests. So I think the answer is probably at least half of them can be fixed with integration tests. But yeah, I mean, I agree with you. We should go back and see which ones can be caught.  You can always have more and more tests, but then you don't know which tests you need until something breaks and then you're like, oh, I can add a test for that some of the time. Yeah, but I mean, I think there's a pattern in which that the component works fine just not with the data that's coming in. And if our default way to write tests is only component tests, it's bound to cause some problems. Yeah, I agreed there. We can definitely do better. Yeah, so yeah, John, you mentioned that. That was the thing I wanted to follow up on. Where the time is best spent, right? So if you spend most of, you know, X percent of your time on PR, sort of retesting PRs and Y percent of your time just testing the tutorials, where are the issues actually coming from? Are you seeing the most value in retesting PRs or in the more broad tests? That would be a question to Ali Reza and Brian. What do you guys think? Did you repeat that? Yes. So tutorials versus retesting PRs versus going over release note highlights. Where do you think you spent most of your time and where do you think it would be more useful to focus your time? I mean, I ended up spending most of my time in tutorials just because I wanted to go at it as like a first-time Galaxy user and then see if you've rendered any problems there. But I mean, I'd say all would be equally useful. I mean, having the highlights was good just because it's good to have a sense of like, okay, what is actually most important here? Because, you know, like you were discussing, there's definitely like a lot of items every time we do release that they need to be looked at and perhaps not enough time or enough hands or eyes. So I would say a combination of tutorials and then maybe highlights and then just having like the most relevant PRs within those highlights, I suppose. Because it was, at one point it was kind of like, felt a little scattered like, okay, what exactly, what should I focus on here? I've got three different types of like, you know, approaches or issues to look at, I suppose. And so, yeah, that'd be my kick on it. Jen, I just noticed you're also Nicole. I'm sorry. If you have anything to, you know, to comment on, please, please just interject. And as far as I remember the tutorials, as soon as you start treating them in my experience from, there we go, as soon as you start treating them as the item you are testing, you start dedicating all your time to it. But as long as you treat them as a suggested path and you start trying to break Galaxy using that path, then it's much more valuable in my opinion. Because in the first case, well, basically are doing what's, what a script can do for you. Yeah. Following on that, I mean, I guess what I was thinking forward to was if we can get more of this per topic testing done during the release, you know, if you're, if you're looking at a specific PR and you want to make sure it's well tested, how we can, you know, really shift some of the burden of testing those individual PRs to out of the end of the release cycle testing and then have the sort of more end-to-end topic-based testing be you guys real focus. Or maybe that's not a good idea. That's kind of what I was trying to dig into. It's an idea. I don't have an immediate response, not because it's not feasible, might be. I mean, I mean, you are, you are thinking about the, the, the main issue of release testing, which, which is the core concern, how do we distribute our time more efficiently? Yeah. Exactly. You said you had, you know, in one of the earlier slides, you know, there's 2000 things you wanted to test. You can only do half of them or whatever. Right. If we can, right. If we can somehow help out or not help out necessarily, but, you know, if we can do more of the individual testing, you know, we can, you know, highlight or PR testing during the release cycle somehow. That might help. Maybe the labels. Assigned to PRs at the time of merge, even though, I know Maria's pointed out that they're not available to it. It's only for maintainers. But if when we approve a PR or merge a PR, you know, this PR was merged with, without a kind area. And then of course, Nikola will add it about half a second later. So maybe that's what we could do. Tag a PR if it needs to be manually tested. If we can tell that it's manually tested, of course, should be manually tested. Do you have a specific board? I mean, could you make a list of like five PRs? Where you think that would be the case? Because the pskr should all come with tests. Right. We don't want to duplicate automated tests. But the global drag and drop, for example, that was broken after another feature was merged in. So global drag and drop would be probably something. The submitter would expect needs to be tested manually when it's added to the release or adding a label would help that. But again, I mean, this can be integration tested. I don't. I think as reviewers, we should probably pay a little more attention to these. I mean, I feel bad asking sentry tests from people that usually don't code in Python. We need some solution there. I think. Yeah, I mean, to address that, we talked about 23.1 potentially including the playwright stuff. So, I don't know, maybe that's something to consider. Well, keeping an eye on the time, I think it's been a really awesome discussion. And unfortunately having to cut it off a little bit, but again, thank you so much to the release testing team for all the time that you've put into helping to smooth out the release. And for your presentation today really appreciate it. Our next community call is going to be on March 2nd. And there we'll have the PIs present the 2023 roadmap. So that's going to take in some of the feedback from this working group progress meeting that'll happen on the 23rd of February. So stay tuned for that. But thanks everybody for calling in today. Thank you. Thanks everyone.


Next up on our last lightning round session for the day is Rosella Tesh, who's right here in Nebraska, on the other side of the state of Nebraska, where I am in Shadron, Shadron Public Library, and she's going to talk about this cool collection they have inside their small library. Go ahead, Rosella. Okay, so thank you for having me and welcome to everybody. I will start talking about our location. We are located in northwestern Nebraska and Shadron, it's the city of which we are the public library. The population of Shadron is 3,800. We are the biggest community in a radium of 50 miles.  There are two prevalent ethnic groups in our community, the white and the native American. Some time relationship between the two have been a little bit rocky. We border with the South Dakota and with the Pine Ridge Reservation, which is the reservation of the Lakota Nation. Okay, a little bit about our library. It's known as CPL. Shadron Public Library was founded in 1913. It's a Carnegie building with 5,500 square feet of space divided onto levels. So, we are really tiny. We have a collection for the total of 36,000 items and an early circulation of 55,265. So, Tiny Library, its name and its history, the collection is called IP&A and stands for Indigenous People of North America. The content is books divided in fiction and biographies, CDs, which are musical CDs of a contemporary and traditional Native American music and DVDs. They are feature films and documentaries made by Native American artists. The name was a little bit of a name that we serendipitously found. We already had a certain amount of books and other items in a particular section of the library on the subject of Native American cultures. And we didn't know what to call it. And one day I read an article that was talking about Indigenous People of North American cultures. And so, I thought to that it's exactly what we should call our collection. And so, we began with that. So, here it's a photo of the collection, the book part. It's located close to very beautiful windows, so there is lots of light.  The structure of the collection is as follows. So, as I said, we have non-fiction items and they are classified with the Dewey Decimal System. Fiction, biographies, periodicals, and I should say newspapers, music, the CDs, the DVDs. Also, we have a section that are young adult non-fiction, young adult fiction, junior non-fiction, junior fiction and junior biography. So, how all of this came to happen? Here you have another photo of the collection and you can see a little bit better the reading area. Around 2010, we started to group together items of Native American interest. A little bit was due to the ability to find them in the collection a little bit easier when we were looking forward for patterns. And a little bit was while we were cleaning and reorganizing our bookshelves, those books were popping up. And we started to see that in collecting them in the same place, they were starting to give the idea of culture inside a culture that needed to be honored. It was like if the books were talking to us, the material was talking to us. Sorry, I went a little bit too... Okay, fast. Sorry about that. Okay, now, okay. And so, we start to classify under IP&A in 2011. In 2012, we started to add musical CDs. That was due to the influence of one of our staff and she was, she is Native American. And we were talking about the beauty of many of the songs and the music. And so, we decided that it could be something that our patterns would be interested to. In 2013, we have the movies. After the CDs, we thought, oh, well, we should try to find movies and documentaries. And we discovered a new world of cinematography. Very, very interesting, very beautiful, soul searching movies. In 2014, well, we had the movies and another natural growth and development from this collection was why we don't present those movies to the bigger public. And we decided to make a movie festival. The movie festival has gone on for 40 years. And it's called Trading Stories because the aim of this festival is to have people of different cultures to sit down and trade their stories, the different aspects of their culture to confront, compare, and share. In 2016, we started to add the periodicals and the newspapers for our patrons. And in 2018, we did the Young Adult and Junior IP&M collections. Okay, some statistics. Here you can see on the photo, Mr. Michael Murphy is a Native American artist who plays flute. One of the things that flew out of this collection is to offer other programs like dancing, art shows and craft, and also concerts of Native American music. So this little tiny collection has 739 items. The value is $10,771. And the circulation, the total circulation since 2011 has been $3,700. So why to do this collection? Why to go to the travel? First of all, to honor a culture historically important to our city. And here I want to say also that we decide to honor also the culture of the white settlers preparing and implementing a local history collection. So we have a balance for the cultures. Provide a wider, deeper understanding of Native American cultures, of course, promote better relationships between the two ethnic groups, support people to search about their roots, and ties to risk to use and stay at the library longer, and to have an ease of material search and retrieval. Gifts of IP&A. This collection has given lots of things to the library and to the library staff, not only the people that we have been able to meet, to meet through the concerts, through the movie festivals, very interesting artistic people, but also, like I said, the better understanding of the Native American cultures, donations. Many people in the community have donated beautiful, very beautiful, very interesting books to enlarge our IP&A collection. Artwork. Here you have a photo on the side of one of the prints that were donated to the library. Previous to that, our artwork was basically made of discolored prints from an old grant that was providing arts to the library. We have now a beautiful, vibrant piece of art. Also, we have received items like a donation of a drum, several bowls, cashewnuts, and so on. The Trading Story Movie Festival has been one of the products of the collection, and it has brought people to the library that otherwise we would have never seen. Publicity for the library, and I will talk a little bit more about this in a minute, and more patterns. Native American patterns, we are seldom at the library before we start our IP&A collection. We have now a big wide use by the communities in Pine Ridge that come here to do grocery, to do errands, and then stop at the library. They feel comfortable, they feel that their values and culture are respected, and so they come and they use the library, they use the computers, they spend time in the reading room. I wanted to talk a little bit about the publicity. In 2014, one of the opinionists of the Rapid City Journal came to the library because of the Movie Festival. He was very enthusiastic about the movies that he saw, but also he was really impressed by the IP&A collection. When he returned to Rapid City, which is the main city, or biggest city in our region, he went to several library, public libraries, and college libraries around the area to see if anybody else had this type of collection, and to his surprise, he didn't find any. So in this part of the country, we are really unique. For us it was very important to have our work recognized. I think also was a little bit of free publicity, and so we were very excited about that. So what we hope for the future, of course, we want to have more space for the collection, more events, and here on the side you can see an image of a dance building at the Movie Festival. We want also to try to collect artifacts. Unfortunately, from this corner of Nebraska, lots of historical artifacts like piddled work, photography, it's living. Every time there is a change of hands of property from a generation to another, or when people die and don't have anybody to take over their states, stuff is dispersed through auctions, and then it leaves the state. And so we would like to have the capability and the possibility to add those artifacts or some of those artifacts to our collection so to be able to preserve a little bit of history of our corner of Nebraska. And this is it. Okay, all right. Great. Excuse me. Thank you very much, Rosella. Thank you so much for sharing about that really great collection. Next time I'm out in western Nebraska, I'll have to stop by and take a look at it. All right. Thank you. Thank you for loving us.


Lesson 292, a happy outcome to all things is sure. God's promises make no exceptions, and he guarantees that only joy can be the final outcome found for everything. Yet it is up to us when this is reached, how long we let an alien will appear to be opposing his. And while we think this will is real, we will not find the end he has appointed as the outcome of all problems we perceive, all trials we see, and every situation that we meet. Yet is the ending certain, for God's will is done in earth and heaven. We will seek, and we will find, according to his will, which guarantees that our will is done. We thank you, Father, for your guarantee of only happy outcomes in the end. Help us not interfere, and so delay the happy endings you have promised us for every problem that we can perceive. For every trial we think we still must meet. Amen.


Thanks very much indeed and thanks very much to the Institute and to all involved for the very kind invitation to speak a few words Here today. I'm always tempted after Peter Sutherland speaks to Simply say I agree and have nothing further to add An approach that was beloved of a now long retired Supreme Court judge who was beloved for exactly that reason by every law student I knew But if I do that they certainly won't invite me back again So I suppose I'd better say something and I read with great interest your paper and agreed with with Nearly everything you had to say in it Peter one particular point that your mention of Refusals of treaties often on the basis of arguments like neutrality taxation or moral issues that have absolutely no substance Rang very true for me. I do remember Sitting down in April I think 2008 which was around the time of the first Lisbon treaty and writing down the arguments that were being considered and the Striking feature about most of them was that they had absolutely nothing to do with the treaty and Farmers were arguing about the stance of the government in the WTO talks and unions were talking about reversing a particularly controversial decision Relating to collective bargaining and hospital committees were trying to stop closures of hospitals the usual arguments about neutrality It came out a completely fake argument about corporate taxation somehow took root and then the argument about a commission Membership that actually had already been decided in the knees treaty without anyone seeming to get to to worked up about it the arguments Over the fiscal treaty struck me as being much more closely related To the substance of the treaty and yet I agree that they too frequently diverged From reality and completely and utterly factually Incorrect arguments about the economic argument of that treaty which in reality was very limited We're constantly made and for all for me all of this involves a kind of call for Realism in relation to things and I think we we need to be realistic not just about our membership of the European Union But about the advantages and disadvantages of the legal mechanism of a referendum as a decision-making tool And of course referendums do have advantages that the big advantage of a referendum is its finality And there's no arguing with the results of when it comes to a really big decision like entry into the Union or matters like that, there's no You know, they are a useful tool, but the disadvantages of them are that the arguments deployed in them are frequently ill-informed They're plagued by propagandistic measures like referring to a treaty as the austerity treaty whether it is or not And they can be affected by attitudes to the government and and furthermore There is the issue that they're also affected by the extent of the individuals knowledge about the issue in question in other words people who don't know and we have research confirming this really do tend to vote no and You know participation rates also can vary very wildly as well. So there are advantages. There are disadvantages I know I stress the disadvantages there but There are advantages. What I would say is that we need to avoid deifying referendums at the end of the day and I think that was a danger and perhaps that Perhaps wasn't The Supreme Court particularly in McKenna number two might not have been alert enough to I think it was Bismarck who said that those who love sausages and respect the law should never watch either being made and You know, perhaps the Supreme Court decision in McKenna number two Seemed to be made somewhat In blessed ignorance of the reality that if you exclude government finance from referendums Well, then private finance will flood in to fill the vacuum and I'm not sure one perhaps point of descent I'm not absolutely sure about the conclusion that we could reasonably and have avoided Referendums on the basis of the essential scope or objectives test in in karate I've been asked that question and I've asked myself that question quite frequently. There's a good discussion of it in Kelly's and Irish and Constitution in which the authors and now judge Hogan and and Jerry White conclude that maybe the referendum on the nice treaty was avoidable under the karate criteria But they're less sure about the others For example, the Lisbon treaty involved setting up a new European Union and a new legally speaking at least so I'm not sure if that could have been done without Without a referendum authorization. I suppose the whole point for me about the karate is sketch essential scopes or objectives test Is ultimately that it is so ambiguous and it's effectively as wide as the gate So we don't know how wide our narrow the essential scope of object our objectives of particular Treaties are and although like Peter Sutherland I'd be more inclined to give the concept a wide rather than a narrow interpretation because after all if you vote for a kitten I suppose you shouldn't be too surprised to wake up in the morning and find that it has grown into a cat and But the only way and you get to find out About such matters is when the courts get to pronounce on it on the essential scope or objectives of a treaty And of course the courts never actually get to pronounce on that because no attorney general and no government would ever risk getting it wrong In other words risk mere parliamentary Ratification of a treaty that might go beyond the essential scope or objectives of existing treaties An attorney general and who advises in favor of a referendum and Will never be found out as having been wrong as having made a mistake and attorney general who advises a referendum is not required It might be and in the results I think that the karate test that's really applied is not does this treaty go beyond the essential scope or objectives of existing Treaties the real test that's been applied is is there any reasonable possibility at all that this treaty might go beyond the essential scope or Objectives of existing treaties and that test is always met and therefore we almost always get Referentums how do we get out of this danger of unnecessary referentums? Well, I think as was mentioned by Peter Alan Shatter's suggestion Which I think might have been modeled on an equivalent procedure that exists in European Union law Preliminary references to the Supreme Court on the legality of Ireland's adherence Or ratification of a treaty would eliminate any danger of superfluous referentums Of course to get that preliminary reference you'd actually require a referendum in the first place and would an amendment like that actually pass Answer to that. I don't know and there's a very large body of opinion that there is no such thing as a superfluous Referendum, so maybe it wouldn't pass. Maybe it would I don't know. I think it would be a good idea to have it personally myself, though and going back over the Substance of what Peter had to say I think Ireland has had for a long time a worrying triumvirate of Decisions the the Crotty decision the McKenna number two decision and the Coughlin decision I think it's fair enough to say that all decisions were controversial enough when made probably in descending orders of magnitude But particularly in legal circles, I think I find that is increasingly less the case and the Crotty case was significant Of course for a number of reasons a number of reasons in relation to its decision in relation to standing and because it elaborated the scope It's a necessitated clause in article 29 for and establishing essentially as irrelevance in cases of treaty amendments Because it elaborated the scope of the constitutional authorization to join European Organizations with Chief Justice Finley's famous for formulation that interpreting that as only allowing access to existing treaties would be too narrow existing Interpreting as allowing access to to any further treaty amendments would be would be interpreting it too widely and coming up with the essential scope Our objectives test as well And but the real reason why Crotty of course was controversial was its approach and to sovereignty And interpreting this is simply being the right to say yes or no to matters And the problem is as Peter Sutherland has indicated it's impossible I think to believe that even such a rigorous test As seems to have been established in Crotty was actually violated by title three of the single that European Act And it's full of what some would be relatively called weasel words And in other words diplomatically diplomatic formulations designed to ensure that no real obligation to do anything at all exists And so it's in other words It's a wish list of rubber formulations Mandating little more than fireside chats about foreign policy and so I think it's fair to say That the Crotty test really was a hair trigger approach and to sovereignty and if the essential scope or objective Test was exceeded then it was likely that the sovereignty test was going to be impossible To escape that's especially since the area of foreign policy is Interpreted on at times is being so wide and of course It's important to remember that the Crotty test doesn't just apply in the area of foreign policy and it talks about Decision holders giving away their power if you like being custodians of the power to decide but but not being entitled to hand them over But that obligation applies to the legislature and it applies to the executive and as well Now of course the immediate damage of the Crotty case in this regard was was done away with by the referendum That's that passed the single European Act afterwards or approved it and then successive referendums If you like approving successive European treaties, but it remains a very real and consideration the Crotty case It was real it's real in relation to treaties which are not European treaties and of course that was the case with the fiscal treaty and of course the big point about the fiscal treaty Is that it didn't need to be ratified by every member state and it's likely In my view in the future that recourse may be had to treaties of this kind again in the future because European Union treaties Need to be ratified by everyone and it's eminently possible that in order to escape If you like that requirement of unanimity and that there will be future treaties there will be treaties in the future in other words, which the The validity of which will rest squarely and on the Crotty sovereignty test at the end of the day So it's a very relevant test indeed interestingly in the subsequent mid-Ymsey test, which was a challenge to the Challenge to the anglo-irish agreement which should have been condemned if Crotty pure Crotty was applied And the Supreme Court ran a mile from it and distinguished it in a very unconvincing fashion as well And I find it interestingly as well that in the latest judgment the Pringle case the Supreme Court Distinguished it as well again very very unconvincingly. I find the interpretation of Mr. Justice Hardiman and his interpretation if you like of the In that regard of the Crotty test a more convincing one, although I prefer the outcome of the majority's decision In that particular particular case. It's just I don't believe the distinction They drove it they drew in the case between the ESM treaty and Title three of the SEA The McKenna number two case what I suppose I should say Basically in relation to the McKenna number two case and the Coughlin case is that I agree and really happen to a great deal Further to add in relation to them I suppose my essential concern would differ somewhat from Peter Sutherland's in relation to the McKenna case This is the one relating to expenditure and in referendums and I suppose I share the difficulty Fail to see where the Supreme Court got its justification for this very radical definition of democracy that it came up with this was very real and judicial Legislation and I think of a rather unwise kind But where I would differ from Peter Sutherland a little bit or perhaps I wouldn't differ It's just that he didn't mention this and is that my view of the McKenna case is that it has effectively privatized Referendum financing because the government which is after all democratically elected is Prohibited from spending any money in a referendum even though it has a very real interest in the result Whereas private parties and we've seen this happen in successive referendums in Ireland can come in and spend vast quantities of money in the same Referendum I find that deeply worrying So that's the the the McKenna case and then and the Coughlin case The interesting thing for me about the Coughlin case was that the Coughlin case involved an eminently reasonable rule and attempt to balance Equality and and Representativity and at the end of the day this was condemned by the Supreme Court again I think very on on wisely. I can't put the matter any better I think than mr. Justice Barrington did in the Coughlin case when he said that the people are the ultimate sovereign But there is no constitutional device that will ensure that their ultimate decision will be infallible or even that it will be prudent Just or wise the most we can hope for in relation to any sovereign including the sovereign people is that before making its decision It will be well informed and well advised in this context to play down or neutralize the role of political leaders in favor of committed amateurs Would be to say the least on wise and so I think that would be the main concern that I would have About those So a fairly hefty step if you like away from majoritarian parliamentary democracy and into the area of direct democracy which could have absolutely You know unthinkable consequences in the long term for this for this country. We'll have to wait and see now last word I know I've probably overgone the amount of time That's that's a lot of to me but a very quick word about the recent decisions Pringle and McChrystal and Daugherty I think the most amazing thing about the Pringle case and the McChrystal case for me Is that the state actually made no argument in either of these two cases that crotty a crotty in relation to sovereignty and B McKenna had actually been wrongly decided and The McChrystal case in particular was more or less straightforward application I've no query about the application of the Supreme Court as a McKenna number two judgment in the McChrystal case They were right the question wasn't whether and that test If you like if the government's behavior and could have been approved under that particular test I don't think it could the question was whether that test was the appropriate one in the first place and that argument Unfortunately was never even made before the Supreme Court and the result of that is worth stuck with it In relation to the Pringle case I found that an interesting case again the crotty case was questioned by neither side In the ruling and I think that's that's very interesting But interestingly the majority and the minority the one man majority consisting or the one judge majority Consisting of judge Hardiman took very different views of what the sovereignty test and actually established and I Think mr. Justice Hardiman took a more traditional view of what it is established But a mr. Justice Clark instead focused on the breadth of the decision In other words that I beg your pardon the breadth of title three of the single European Act and that that was the objectionable feature to it in other words that the European single the European stability mechanism treaty quite narrowly focused and I know I am simplifying here to a certain extent, but that the Title three of the single European Act was much broader Measure affecting foreign policy as a whole and that was the distinction between them So for mr. Justice Clark and if you're reading the judgments the judgments of Justice O'Donnell and Mr Justice Clark are by far the most interesting ones there and the new test established by mr. Justice Clark at page 28 So there you don't even have to read the whole thing and the new test was to distinguish between an exercise Insovereignty on the one hand, which he felt that the ESM treaty was and whether there was and he felt that there had been this in in relation to the single European Act title three such a Significant narrowing of future policy options that it can properly be said that there has been a transfer of Transfer or pooling of sovereignty my problem with this particular test. I actually think it's much wiser judgment than the initial judgments in the in the karate test But the problem is it is also a very difficult test to apply and at the end of the day Where is the borderline between the two of these? So I think if you like the uncertainty that we have been left with In relation to such matters and as a result of the karate case is going to survive And I think we are going to see plenty more referendums. Thank you very much indeed


Hello, this unit builds upon the unit on ambiguity, whereas the context of use usually selects one of the meanings of an ambiguous expression. In cases of vagueness, the context can add information that clarifies the meaning of the vague expression. In fact, there are various types of vagueness and they will all be discussed in this unit. Thus, the programme of the virtual session is clear. We will first look at the various types of vagueness and will then provide and put to test several criteria that distinguish vagueness from ambiguity. Use the question sheet for guidance. The hyperlinks and video links in it may help a lot. The mastery worksheet is a dynamic multiple choice test that shouldn't be problematic at all after going through the virtual session. Well, and the practical provides you with data as usual, data to identify types of vagueness and to differentiate between ambiguity and vagueness. So, good luck with this unit.


Hey, Bolo buddies. Thanks for watching. Okay, this is going to be a quick how to cross post using list perfectly video if you guys like what you see I do have coupon code when you go to sign up for list perfectly You just type in Bolo buddies under the coupon code and you will get 30% off your first month I'm gonna show you if you just go with the first plan You have to list items individually and then I'm gonna show you how to cross post in bulk Which is the second tier and I'll show you guys the pricing After I do the demonstration But I chose the second tier because bulk cross posting is amazing. So let's get started All right, let me get my screen share up and also at the end of the video I want to show you how to add the extension up to your toolbar. I think it's called Because I know some people struggle with that So I went to my cats meow items. That's why that's all you're gonna see I bought a bunch of cats meow items at a garage sale, and I recently just listed them all I have some of them cross posted But not all of them here is a little trick or tip that I have When you are cross posting from eBay to other sites I go to the custom skew and I'm gonna add this one From eBay and I'm gonna take it over to Mercari and Poshmark. So I put in those MC and PM and that tells me when that item sells I need to remove it from Mercari and Poshmark Let me just confirm that I've yes got my screen share up. So I'm gonna Change that one.  I think it's called I should have You're gonna go boom boom and you're gonna hit copy Okay, now just wait until you see how the bulk cross posting works. I'm gonna show you that next So there is definitely a benefit to getting the business plan at the $49 because I feel it is much much quicker So this second one's loading and it does load to both platforms.  I'm telling you it's it's such an easy little cool that a lot of people don't use So, okay, so those three So I picked three more and I'm gonna hit this button and then I'm gonna click click click and then I'm gonna hit this button again and Then I'm gonna share they're already highlighted because I already clicked on them to Mercari and Posh and I'm gonna hit copy Now it's gonna pull up all six tabs because I had three items and they're each going to Mercari and Poshmark so a lot of times I'll do Between 10 and 20 at a time and while they're loading I'll get on my phone and I'll send offers to watchers on eBay or offers to watchers on Poshmark or all reduced prices on Mercari or send offers, you know what I mean? So kind of while they're loading I multitask But after they're done loading wait until you see how easy this is It's amazing. This is such a time saver That's my favorite thing about list perfectly is how much time it saves me so These are loading and it looks like it might be done So if you go back to eBay, if it says copy, then it's done. If it says processing you have to wait okay, so We are good to go So I'm gonna go up here to the first item and this one is going over to Mercari and it says vintage cats meow village and it says Metremora, whatever that is It's whatever it says on the back and you just have to either Like take something out of the title like that didn't have the whole ending here because there's not enough Characters on Mercari. So I'm gonna put in vintage I'm gonna have all these typos because I'm trying to do this for you guys and I'm gonna put cats meow and I'm gonna put village as my Key words and then home decor accents. It's already got it kind of plugged in as the category It's in good condition. I'm gonna put in my zip code. I'm gonna do free shipping I recommend free shipping on Mercari. Just build it into your price so on eBay I had it at $13 and The buyer pays shipping so because I'm gonna do free shipping I'm gonna change this to 17 and I'm gonna hit list. So now that item is ready to go and then I'm gonna close that tab because it's on Mercari and now I'm at Poshmark and I'm gonna do the same thing And you have a few more characters on Poshmark. So you just kind of adjust that title This is gonna be under home accents decor I just do one size no tags Zero and I'm just gonna Poshmark takes 20% so I'm gonna up that to $15 and I'm going to Share it and there it is. It's listed. So I'm gonna go through all of the ones I think I did five total and I'm just gonna show you how quickly I can do this then we're gonna look at the plans And I can explain to you what I was talking about the differences and the pricing and having the bulk and the Not having the bulk listing.  It's just so fast And you don't have it just saves you even more time. So it's worth the extra I think it's $20 difference a month to get the the second tier in my opinion So it depends how much you're how much you're listing, you know what I mean? Let's do 17 because they are kind of heavy And people can make offers and all of that stuff so And these cats meows They are a great item to pick up if you can get them cheap I picked them up at a garage sale And I paid $30 and I'm much quicker at this when I'm not talking I picked them up at a garage sale. It was like three boxes full for $30. So I got a Great deal on these and Yeah, I I listed them. I think I've sold like between Six and eight. I can't remember exactly. I've sold quite a few So I'm pretty excited about that some of them are bread and butter Some of them will go for a little more but overall, you know, they're bread and butter items But I've got like 30 cents in each one and I've got over a hundred listings. So it will add up quickly And I have so many that people can put them together and buy more than one Okay, so I've got what four or five more to do here So I'm going to do those real quick and then again, I'm going to take you guys to the pricing Maybe I shouldn't have done so many but I just want to show you how How fast it is And I have been I was the person that cross posted everything manually before there was something like this And I will tell you it is a pain and I'm sure a lot of you guys are if you're watching this and haven't signed up yet You are doing the same thing and it is a pain This is just amazing amazing. I love it. So this is a tavern. So I'm going to use that And that's vintage cats now home decor super easy you guys And Ship on my own. This one's a little heavier. I'm going to put 20 on it I just I just sold one I think for 16 and I think that one sold on ebay So that was cool I think it was a kentucky one also So they have different um Different things on the back. There's like lineal trains. I have some of those listed. Those are cool um I'm just kind of adjusting my price based on the platform What the fees are if i'm going to do price drops if I have free shipping and all of that good stuff And mercari has a special offer going on right now where if you sign up, I think you get is it $30 Can't remember But I have a sign up code if you guys are not signed up to mercari Definitely check that out in the description of the video And if you use my code, that would be amazing because I get credit and I think you get $30 right now Don't quote me on that. It was 10, but I think they have something special going on. I'll see if I can't Check that one's a heavy one if I can't check my phone here in a minute Okay, I got one more guys and then we're going to get into pricing So I just close it out and then I know it's finished um All right so decor accents And you'll get more familiar with the different sites and how they work the more you use them I'm also selling on grailed and um etsy, but for this video I'm just going to do poshmark and mercari because those two platforms I pretty much cross post everything to Uh poshmark now allows toys, which is fantastic. Oops. I forgot hit list Okay, so all of those items are cross posted Let me see if I can look up that mercari thing here for you guys real quick So if you're not selling on mercari, they have a special offer going on it says um Give 50 get 30 Or no, I'm sorry get 50 give 30 share your link to people who aren't on mercari yet We'll give you 10 off their Wait, we'll give them $10 off their first order plus 20 when they make their first $100 selling on mercari And then I'll get 10 when they make their first purchase and another 40 when they make their first hundred dollars So that's really awesome. So if you guys use my link, I'd be so happy All right, the link to mercari is down in the description. Okay, so let's go over to list perfectly here and Here is the pricing plan. So on the simple plan You guys I clicked on the one item And then I sent it over and then I had to click on the other one manually and send it over So that this is the simple plan Okay, and there's other things that the simple business and pro how they differ But this is the game changer for me and why I chose or I don't know they didn't have bulk pro cross posting when I started but um If I would have been on the simple plan and they would have added the bulk cross posting I would have went to the business plan, but I was already on the business plan so With the business plan you get to do the bulk cross posting which is where I clicked on the three And sent all of them over at the same time, which Is well worth the $20 difference So there are the the different plans and if I'll post a link down in the description of the video to list perfectly And then when you sign up you can just put in Bolo buddies at the coupon area and that will give you 30 off your first month Now what I want to show you guys is How you add the extension once you are signed up? So i'm going to go over here and i'm going to delete this from chrome So i'm removing it from my toolbar and Let me see here I'm already logged in. I do believe yes So you're going to go to once you sign up and log in you're going to go to get the latest version And you're going to go to current version and you're going to hit download now And that is going to you're going to hit add to chrome And then you're going to see that it is right here Okay It's right there So once you do that it is going to update on ebay And you're going to have all of these little Circles They're going to show up. So that's all you have to do now. It says log in to list perfectly I'd click on that and log in again I'm not going to do that right now because I'd have to put in my Password and my email and all of that stuff. So basically Um, there's your extension Here's your little dots and you're ready to go So What do you guys think? Let me know in the comments. I'm going to keep this video short and sweet again my coupon code Um Four lists perfectly as bolo buddies if you put that in you will get 30 off your first month of list perfectly It is an affiliate. Um Basically, I get a small commission when you guys sign up using my coupon code, which is fantastic And if you guys have any questions, I have a facebook group, uh, bolo buddies It's linked down below in the description if you guys have any questions. I'm happy to help Oh my goodness Oh So sorry can't I'm not even going to edit that out. It is what it is So I am happy to help If you guys have any questions, so just join my bolo buddies facebook group again the links down below I'm also on instagram. So check that out as always. Thanks for watching And if you're new to the channel, most of my videos are about Bolo's items to be on the lookout for items you can buy low and sell high So if you want to learn about items like that, which if you're a reseller, I'm sure you do Definitely go check out my other videos. Be sure to like comment subscribe and share and as always. Thanks for watching


the five golden rules of trading. I've got some rules. The first one is of course you all know it, the broker says it, only investment you can afford to lose. Rule number two is about risk. So you should risk a small portion of your account per trade. You have to remember that all trades should have the same effect or weight on our account. The third rule, which I call the technical edge, the fourth rule, which is our second edge is going to be through risk management by only targeting at least double what we are risking. And you have to remember that it's not how many times you win. It's how much you make when you win versus how much you lose when you are wrong. Rule number five is about emotion stability. So if you are not feeling well, don't trade. If you have something going on in your life like exams and college, problems at work and so on, simply take the week off. That's a privilege we have in trading.