That's the way with that. I mean the most watch man and cable news. It's actually a really I think that's away with it. If there's a Tucker and Lori Ingram and then tell see Gappard Well, listen, but I think that's an incredibly relevant question Yeah, and I think DOJ in the same way that it is setting up a task force to investigate oligarchs should look into people who are Russian propagandists and shilling for Putin That's being if you are a foreign asset of toy dictator, it should be investigated Welcome back and thanks for watching. No, what you just saw there was not a less attractive Miss Piggy It was Democrat state media propagandist Anna Devarro And she's trying to explain why it's a good idea to use the force of government against journalists who are saying things They don't like hmm sounds familiar now come with me down an aneurysm inducing mental meltdown as we watch the spew Go down a very dark road of rationalizations to justify horrendous actions only to obliviously out themselves as the very thing They claim to be against but first take 30 seconds to hear about this free coin offer for my viewers Bloomberg financial news has said the stock market lost over a trillion dollars so far this year You heard that right a trillion dollars Facebook has fallen out of the top 10 tech stocks and all the markets have the jitters like you people are worried Really worried except those with gold and silver as their backup plan They know that with the precious metals ira they'll be fine and for the month of march with a qualified ira above 20k You'll get a three ounce silver american virtue coin or a five ounce america the beautiful silver coin for anything over 50k Call<PHONE_NUMBER> now to find out more or visit noblegoldenvestments.com You can also find the link in the description or pinned comment. Make sure to tell them drone tech sent you oxnews's host tucker callson is apparently a big hit in russia right now The website mother jones posted elite kremlin war memo Instructing russian state media to play tucker callson clips as much as possible And tulsi gabbert is being accused of spreading russian false flag propaganda This is exactly what i've always been talking about when i say the left is dangerous because they're capable of rationalizing anything First of all i'd be skeptical of this leaked memo because it could easily be disinformation Used to sow discord in the u.s. Just like the steel dossier But beyond that who cares if they're watching tucker in russia back when bush was president and the war on terror was in full swing There were those who accused anybody questioning those wars of being traders or aligned with the terrorists the media and democrats at the time Fiercely opposed this behavior with hillary clinton famously screeching I am sick and tired of people who say that if you debate and you disagree with this administration Somehow you're not patriotic and we should stand up and say What she said was correct and continues to be correct today back then there were terrorist propaganda videos out That actually used clips from msnbc and cnn accusing bush of being a dictator and guilty of war crimes Or regurgitating islamic terrorist arguments about the us and oil and i remember at the time neither cnn or msnbc Would run any pro iraq war victory ads and we were actually in that war unlike russia's invasion of ukraine There's absolutely nothing wrong with tucker asking any of these questions and the over the top reaction to it should raise eyebrows Back in 2014 cnn asked if showing isis videos was okay because it was just spreading terrorist propaganda And this is what they concluded not showing the video at all However risk sanitizing the grim reality of the world So most media outlets tried to strike a balance media figures also tried to demonstrate some self awareness When dealing with the issue no way to avoid leading the show with isis butchery and yet maddeningly that also seems like what isis wants How is the city different from what tucker is doing now? Raising questions that need to be asked and again I just want to make sure everyone's clear that i might no means pro putin are trying to excuse his war Obviously he's the bad guy and he launched this war on ukraine and ukraine has every right to defend themselves And i think they should get some support from us But i also think that the tough questions need to be asked And i think it's really weird when you have members of the media and members of political party outright asking For journalists to be arrested especially when most of these people went out of their minds when trump even criticized them The fox board of directors should really step in if they call themselves patriots and they you know It's not enough to be posting flans about ukraine. The question is what is in it for someone like tucker crawlson, right? Is it money who's paying him that money? Um, i'm not making any allegations, but it's just it doesn't make sense that he would Do this kind of thing. I mean he also says that the united states helped encourage the russian invasion Ah, so we're back to the russian collusion secret russian agent conspiracy theories What do you mean? It doesn't make sense that he would do this kind of thing He's a journalist his job is to ask these questions and while i do think putin is responsible for the war he started There is this i think the one Place where the greatest consternation would be caused in the short term for admission Having nothing to do with the merit and preparedness of the country to come in Would be to admit baltic states now in terms of nato russian us russian relations And if there was ever anything that was going to tip the balance were to be tipped In terms of a vigorous and hostile reaction. I don't mean military In russia it would be that so tucker asking if america had a hand in instigating this war Is not outside the bounds of normalcy especially with bine being the president that this all happened under For the second time no less. I hope he's planning to move to moscow Because he's not going to be welcome here for much longer, but I think that's an incredibly relevant question And I think doj in the same way that it is Setting up a task force to investigate oligarchs should look into people who are russian propagandists and shilling for putin That's being if you are a foreign asset To a dictator it should be investigated.  There was this lady stalking me. I thought she wanted a selfie No, she wanted to insult me for uh, not for loathing trump But I don't think that should happen to you and I don't think that should happen to chris. I don't think it should happen to me okay, well, um Don, I also don't think there should be hurricanes or there should be Uh, covid but crap happens. Okay, but yeah, this is just straight up scary conspiratorial stuff She's peddling here and finally we arrive at the moment of self-ownage Which should have led to an epiphany But won't they used to arrest people for doing stuff like this If they thought you were Uh colluding with a russian agent if they thought you were putting out information or taking information And handing over to russia. They used to actually investigate stuff like this and I guess now You know, there seems to be no bars Concern also is do the russian people don't know it I know this weekend and correct me if i'm wrong. I think instagram was taken down in russia They really are they almost have a digital curtain now over all information coming out of russia and You literally want a digital curtain over all information coming out of our country It just they don't have the self-awareness to see that they're everything that they claim to be against I mean, they are literally calling to use the exact same tactics that putin has used against his people Hey, literally want the government to investigate and arrest not just journalists But anybody apparently who questions this war between russia and ukraine and or america's involvement in it They want to use the exact same tactics that putin uses And yet they continue to accuse us of all the things that they are guilty of all right I think a part of my brain just exploded so I better end it here But as always, thank you for watching if you enjoyed it Please hit that like button share and subscribe then leave a comment to let us all know what you think


Today's session is going to be about, well, Drupal 8 and Purse 2 for best practices, whatever that is. Before we begin, I'm Branislav. I'm a Drupal guy. I was actually a doctor guy before I became a Drupal guy. I studied medicine and I had substantial IT knowledge, but they changed. So now I have hair and everything, and I became a developer guy with substantial medical knowledge. So it's a change. I lived until seven months ago in a beautiful city of Panksevo in Serbia, close to capital. But now I live in Rheinbach in Germany, close to ex-capital. So I changed. I work for a company called Union Betriebsgambira. We are working for, well, for a major German political party and we are doing IT, internet printing and publishing. So yes, a lot of changes. And the thing is, this session is going to be a lot about change management and how to embrace changes, but keep your identity, you know, the ways you are doing. And of course, in Drupal 8. Now Drupal 8 gave us, well, new core, new APIs, 200 new features, new paradigms of coding, object oriented coding, proudly built somewhere else, and of course, big. So it yells out with the old. It yells with, you know, we need revolution. We need to forget everything we knew and start all over again. And I really hated the concept because, well, I learned Drupal for 10 years and I don't want to forget everything. I want to, you know, start building on top of Drupal 7 and Drupal 7 practices and just learn something new. And it is really difficult because of this force, seeing force to change and to embrace totally new thing. So let's start with goals. You know, we need to focus on goals because goals didn't change. And our goal is actually to do as least as possible to build as best product as possible for, well, and, yeah, enjoy it. So, and in order to do that, well, we have good software design. And that problem was more or less already fixed. We have, we know what to do. We know that we need to build software that is good quality software that can be easily maintained, easily upgraded, easily reused and deployed. And, well, programmers invented design patterns. And that's awesome. That more or less solves their problems because, you know, you have patterns. You know how to solve some general problems using some general patterns and that's it. But it doesn't really work with Drupal because, and especially site building. Because we are working with visual programming with settings and not really typing stuff. So that can be a little bit impractical for site building. So we invented best practices. Now, they are similar to design patterns only suggestions how to solve some problems. But, well, design patterns are unique for every programming language, every framework. And best practices is kind of framework and version specific, meaning whenever you change a framework you're working on, you need to review your best practices or even redo them, start from scratch. And, of course, version specific, which we know in process of immigration from Drupal 7 to Drupal 8. And, yeah, they're also task specific, meaning that, you know, you don't have that much design patterns in the world. But we do have a lot of best practices depending on what we really try to achieve. So I don't want to talk about, you know, whether to use node access or rabbit hole to solve a problem, that's too focused on a special task. I want to talk about general stuff. And, of course, we don't have any literature on best practices. We don't have any repository of best practices, and that's really a problem. We really don't know what is a best practice to solve a problem and what is not. Finally, we're not really sure if best practices exist. Are they the best? Are they better practices? Should we just stop searching for better practices if, well, yeah, current ones are the best? So our first problem or the biggest global problem we have is, well, problem with deployment. But not any deployment because we don't care about code deployment. That problem was solved with Git. We care about config deployment. Now, config deployment was generally a problem with Drupal, and there are still a lot of companies who do manual deployment. Are there people who are doing manual deployment here? Don't be shy. I'm doing manual deployment also. So unfortunately, we do a lot of manual deployment these days, even though it's 21st century and we have all those beautiful tools. So we invented something that will prevent us from having to do stuff multiple times and reduce margin of error. And, well, first thing I could think of, we created was hook update and process. Who is using that? A lot of people, awesome. So I don't have to talk about it too much. So we just, you know, use some custom module and just any time we want to deploy something, we write a new hook update 10, push it, pull it. But it's time consuming, and, well, we don't have too much time. Another thing we invented was features. And who uses features here? Okay, who doesn't use features? Okay, features are awesome. So they helped a lot. Now we are able to visually pack stuff together and just create modules out of it and just add it to Git. And we know who did it, if somebody breaks something, we know precisely who broke something. So it's good. However, it's not so good. Due to limitations of Drupal core and overall user unfriendliness, we have problem with auto increment indexes in Drupal 7. To be precise, for example, using blocks and putting blocks into features, you cannot do that without features extra.  Who hates features extra? Okay, so, yeah, that doesn't work really. And you know, come on, re-create, revert, what's that? I had a lot of problems trying to explain what is re-created, what is revert to people who are, well, who are good developers, they're not really from Drupal world. That's crazy. And finally, this is a big problem. When you disable a feature, it is going to delete every setting inside that's, well, deployed using that feature. So you can use, lose a lot of content by disabling feature. And finally, there is a big problem if people are using features for something, but then overriding features in live, they end up with this screen. And this is a nightmare. This is a nightmare. And you know, when you start working on a new project and you see something like this, and you're not really sure where to start, what to do. So first thing you can do is like create a group called delete me. And all the things that you don't need, just put it there. Because you must not uninstall it. Or even worse, you cannot uninstall it because it is like circling dependent from something other. So it's a mess. And that mess happens like this. So if you have thing called, well, you created an article. An article has node containing body, which is a field base and field instance. And then you created another content type called listening, which is actually also having body as, well, field and field instance. So listening is dependent on article. No, just imagine you want to create a list of listings in the article because client wanted that. So you're going to have entity reference to listing nodes. And then you have circular dependency. And this is a nightmare to disable because, well, you cannot disable it. Well, not without too much troubling. So we created, again, some best practices. And one of the practices is we can force our features not to be dependent one on another by, for example, creating unique fields for every single node or content type. And that works. It results with a lot of tables and it's also a mess to maintain. Who uses this approach? Not so many people. Okay, so we have another approach. Another approach is a little bit better or leery. So we're going to do the opposite. We're going to create feature for every single field we have. And then we can create dependencies, well, for every single node, which also has a feature. Then we result with, you know, we have a lot of features, but everything is unidirectionally dependent of each other. So we can create views and those views will be dependent on nodes and nodes will going to be dependent on fields and everything is going to work okay-ish, but we are going to end up with a million of feature modules. Who does this? Okay. So it solves our problems. But do we have to think about this? Because now we have configuration management or short CMI. I don't know who invented CMI's configuration management. It's like occurring from initiative, but still we still use CMI and I use it as well, even it's wrong. So CMI allows you to do the stuff into database, export YAML files and then just add those YAML files in Git, add those YAML files, well, push them and then import them. Who uses CMI already? Wow, awesome! So and of course we have Drush and Drush helps us a lot with config export and config import and finally we don't have problem with revert features and whatever. So it's awesome. It's great. But let's talk about practices. What is good practice here or bad practice? For example, do not like the location of exported files, which is, well, in files folder. Again, this is totally logical because that's the only folder that is supposed to be writable by a purchaser or so, it's okay. But this is in some development environment. I want this to be somewhere where Git can pick up those files and just manipulate with them. So there's a fix for that, of course. In settings PHP, config directories, array sync item just can be changed to something anything and after Drush config export everything is going to be working perfectly. So we end up with a lot of files and Drupal took care of security so it added HT access, which is awesome. And now we can see hundreds of files with various settings. Those hundreds files can easily become 1,000 files in complicated projects, which could be a problem. So my initial idea when I saw this bunch of files is can I create a lot of directories and just categorize those files so that I can use them afterwards? No, I cannot, of course. It won't work. So if we want to categorize all those features, we are going to use features module again. But it got seriously updated and totally rewritten and now it is built on top of config management, which is awesome because now we are not using features to deploy any configuration or anything, so that's all by Drupal. We are only bundling configuration into various bundles or various modules. Now due to the fact that modules are being shipped with their own sets of config and that's the features are using messily. And that config is being imported into active configuration of Drupal on install. Drupal cannot really detect the changes on already installed modules, so features are taking care of that. Of course, features are exporting and importing changes. They are auto-packaging, which is the same they did before, so it's like normal. And they are doing namespacing and namespacing is really awesome. So it solves the big problem of creating a feature which already has a module with a similar name on Drupal.org and then who had that problem with name collisions of country modules and features? Anyone? Yeah, so you create a feature called blog and you're in problem because, yeah. So namespacing solves that. And of course the best thing with features is it's a dev module. You're going to enable it only in development environment. You don't need it on live server or on production environment. However, you still have problem with dependencies.  Nevertheless, good thing is if you disable a feature, you're not going to lose your content because all the settings you created are going to remain that. And that's huge advantage. That's something unbelievable. So as a conclusion, features should be only used to bundle configuration. You don't have to use it for deployment and that's awesome. And okay, so you manage to deploy your site and you start working on that.  So how to save ourselves when you have discrepancy between your local environments and your live environments and you want to keep changes in live environments. Well, the easiest thing you can do is, of course, to export settings in live environment added to Git, push them to the repository and pull them back in your locals. That works. Sometimes you have a problem where you want to keep both changes in local and remote environment. And for that, there is a thing called Drush Config Merge. Now I first heard about it six months ago and I still haven't tried it. But I read a lot about it and it uses Git to merge local changes and remote changes keep them all. Does anybody know anything about this? No? You should try it. I should try it. Somebody should try it. And talk about it. And well, this is my favorite, you know, just forbid config changes in live and that's, there's a module for that called configuration read-only mode. Just, you know, forbid it. Goodbye. Problem solved. Now, our installation profile is that. There's this thing we invented in Drupal 7 to create an installation profile during our web development process and then just all the modules, all the config, all the stuff we created just to put in an installation profile. So once we are done, once we want to deploy the site, we are going just to, well, push everything and install using that installation profile and we are done. Who uses this strategy here? Installation profiles. Not a lot of people. Okay. So it's an interesting strategy. It's awesome. It's easy to test and maintain and everything's good. But do we really need them due to the fact that we could possibly do something like this? We could build a site in our local environment, export files, push them, do minimal installation and then import config. Did anybody try this? How did it end? For me, it ended like this. So it turned out config management helped with continuous deployment but not with initial deployment due to the fact that once you install the site, you get site UUID. Once you install the site another time, you get another UUID. And that discrepancy just kills the kitten. So as a way around this, you can just do minimal installation, deploy files, push the database, just deploy the database and then you're going to have the same UUID and then you're going to just push files. Or you can use installation profiles. And we're back at the installation profile, same thing we used in Drupal 7. So you can just create installation profile. And really installation profiles in Drupal 8 are not that different from installation profiles in Drupal 7. So, well, directory is the same. Info files became Info YAML files. Install files are the same. Profile files, same. We're not packing features, well, or configuration into features directory. They're not modules anymore. We can just add all the configuration to config install. And modules are in the same place, things are in the same place. When you look at Info files and Info YAML files, it is really difficult to find the difference even though it's different syntax. So, same. And the only interesting thing is, okay, this setting files or YAML files that are being placed in some magical config slash install folder, and they just simply work. So one can really be attracted by this and try to do something like, okay, I'm going to build the entire website. I'm going to export my settings into some directory somewhere. I'm going to copy all the settings into installation profile. And I'm going to, well, install a new site with those settings. Did anybody try that? Did it work? Nope. I hate it. So it didn't work. And turned out, again, these files were built to do continuous deployment, not to do installations. So if you want to do installations, either you're going to cherry pick YAML files in order not to break the entire installation, or you're going to use features. So next, noble practice in Drupal 7 world is Drush Unsuck. Does anybody know what Unsuck is?  Drupal 7, that is. So, and nobody uses an overlay, I guess, I hope.   And of course, Drupal websites without C tools, use libraries, they're not really useful. So you want to do all that. But in Drupal 7, Drupal 8, you already have all of this. So the only thing I could find, as my standard Unsuck practice is just enable admin toolbar, toolbar which allows me to have this wonderful drop-down. So give them a try if you haven't already. Which ends up with all the old practices, and they're kind of the same. We have a new practice, totally new practice in Drupal 8, which is like Drupal 7 as well. So we have Composer. And Composer is de facto standard for, well, all the modern PHP applications today. It handles dependencies, it provides you with autoloader, it keeps the codes updated with Composer update, and it feels really good to use it. It's a shell thing, and it's really good. But the question is, is it Drupal friendly? Is it ready to be used in production environment? So let's start with basic stuff. So setting up a project. So with Drush, you would just use Drush DL, Drupal, and then install it. With Composer, syntax is a little bit different, but nothing too complicated. So sounds okay for now. There is this problem of performance. It turned out Drush is 10 times faster than Composer. So Composer with warm caches, totally full, everything up to date, needs 31 seconds to deploy, well, working core, and well, Drush needs only 12 seconds. Things can get really nasty with cold caches for Composer, then it's more than two minutes. So performance-wise, it's not so good. You need to set up Composer. You need to prepare the entire environment and everything to use it. So first thing you need to do is you need to use Drupal repository, and there's a command for that. Then you need to make sure that all the stuff you download are going to be in Drupal directories, not in slash vendor. So you're going to have to install this library custom installer and then add some settings into Composer.json file, which is not a big problem.  Then you're in problem with patches, you know, if it ignores, and, okay, I'm going to talk about it later. So once you're done, you can get a module relatively easy. Composer require, I believe this is an error. It should be Drupal slash admin toolbar, so, yeah. But otherwise, and it's okay. Once you're done with it, just enable the module and it's going to work. Developers might like only to avoid this Composer thing and just just enable and it is going to download and install. So it is not really good. Well, the best performance thing ever. And I said patching. So you're pulling a module, you need to apply patch. If that module is not going to be part of your Git, then you need to apply that patch in production as well. So there is a way to set up Composer to apply patches, but it is not by default supported. So what you need to do, you need to add this library Composer patches and you need to then in this patches file, add, well, connect patches to patch files to, well, modules installed. It's a lot of setups. So somebody was smart and gave us Drupal Composer, which is, well, starting point for you to bootstrap all your Composer projects. It already supports patching. It's already supports custom directories, scuff folding.  So just touch with it and it is going to work. So with all of these things built in, if you are using Droshmake workflow, Composer can really help you and replace Droshmake workflow in a way that is going to be readable to other PHP developers. However, there is this big question. Can I sell this to my boss? So I probably can sell Composer to your developers, but managers are a little bit different. So they are going to ask me about return of investment. They are going to ask me about, okay, so 131 seconds against 12 seconds. That's kind of bad. So I still have not the entire answer. I know that with Composer you can save a lot of time on deployment. So for example, platform s age already included this entire Composer build into their workflow. So once you push all the changes, well, in Composer file and only in Composer file, it is going to install all the required modules. It is going to install all the dependencies for you. It is going to apply patches for you. So it is going to be, well, it is going to do a lot of wonderful stuff for you. And I hope this process can, well, save enough time or provide that return of investment your managers require, hopefully. And to conclude, I started this session as, well, story about best practices. But the question is, do they exist? And I don't really think they exist. So I would really like to call them current practices. And why current practices? Because they always need to be questioned. They always need to be refined. So when you have some idea, it should be documented. It should be time-tested, rethought again. It should be shared with other people, again refined with them. So other people should question and refine those ideas. And it is a circular process which returns back to another questioning of practices. And hopefully that will provide us better software and better working paradigms. Thank you. Questions? Yeah? If you're using Composer, how would you, can you go to the microphone? I can repeat. So the question was, if you're using Composer, how can you add your custom modules to it? Basically you don't. You don't. You just push it in, get in, continue with that. Unless you're happy to share it with other people. And then there is a process for that, of course. Which includes publishing it to the Drupal org. It doesn't work. I can repeat. Does it work for Multicite Composer? Does it work for Multicite Composer? I have no idea. It should be working. I mean, why not? But because Composer only handles files and dependencies. And they are shared between Multicites. So I don't see the reason why not. So the question that was asked earlier is, we're currently architecting it so that we have a site repo that has a module in the themes directory and then the composer JSON. And so then what we do is run a post script after you do your Composer build, that sim links those folders where they need to go for Drupal. I'm not going to repeat that. It's too much. But if you want to use the microphone or, but yeah. Anybody else? Yes? Ladies first. I believe last change was really good and it was in September 22nd on Drupal org. So and it's really full of new stuff and it's good. But I suggest you to take a look at this. Oh, wait a minute. Okay. So this Drupal Composer thing or platform message example Drupal 8. Because it's basically everything you need to know about Composer. It just squeezed in and with it, you're just we just clone this and you're ready to go. No problem. Yeah. Any questions? Yeah. Okay. So the question was, what's the best way to handle situations where you have multiple environments and you want various configuration to be in various environment? So I have no idea. I guess, well, that's really interesting question. I guess you would have to use features and just decide where to enable those features and where not in which environments. So I guess, but it's a good thing to think about in terms of how to create this best practice for that or recommended practice for that. Yep. Yep. I can try to answer what question about Dev and if you want to not to deploy Devol for example, there is a Drush CEX to export, but you can use skip modules and you can give names of modules that you don't want to export so that it's not in your git. You don't have the problem with config that you don't want to have in production and another problem is with config that you want to be different in production or in Dev and you can use, I don't remember exactly, but you can write it in files, some like you can override the config that is in database with config that is in files like in settings and things like this so that even if in your form, in your config form, you see like CSS is a CSS packaging, compressing is on, actually it's not on your Dev because this config that you see in the form, it's overridden by a file. That's it. But there is a little problem with Drush CEX skip modules because it skip some modules but not always the config that depends on that modules and I'm currently working in a patch of Drush to do this and I'm not the only one, but it's still a little problem. Thank you. Well, it's, I'm only thinking about how to automate all of this so that's kind of next question. Okay. So you still need manual power, human power to decide what is going to which environment but it would be interesting to think about how to automate the process. Other questions, comments, rotten tomatoes. So the question was, if I heard correctly, isn't it possible to just disable modules with some settings in various environments? Oh, that actually could work. But then you cannot really, you cannot really, hmm. So if you'd like to have various settings, local settings in various, that could actually be interesting to try. I have no idea. But yeah. Anyone else? Okay. Thank you very much. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you. Thank you.


Hi, I'm William. Now, in GitLab 13.9, you can configure your GitLab runners to leverage GPUs in the Docker executor. Why is this great? It means that for those of you running computational workloads that can benefit from having a GPU, such as machine learning pipelines, now you can configure a dedicated runner to execute those jobs using a GPU. Let's consider this example. Here I have my project where I have been working on experiments and visualizing data. Now I want to retrain the model, changing some epochs in the main script. For that, I can use the Web IDE and let's change the epochs from 10 to 15. As you can see here, I'm using TensorFlow. Let's commit the changes. Add some commit message. Meaningful one. All right, now that I have committed the changes, let's take a look at the pipeline. As you can see, we have different stages from validation, training, testing and reporting. Only during the job called train model is when we are using our runner enabled with GPU. Let's take a look at that job. As you can see here, the job is starting and we are using GitLab Runner 13.9 with Docker executor. In the log, now we can see how the epochs start to execute. Now we know that we are using the GPU, as you can see in the text that we have created here, where we are using a dedicated runner with GPU enabled for this job. Okay, it's done. It finished training the model. Now if we check the next job, the reporting one, we can see that it is using one of the shared runners. We don't have the GPU tag because for this job, it is not necessary to have a GPU enabled machine. Okay, that was it. More information about how to enable GitLab runners with GPUs in the video description. Stay tuned and let's continue learning at GitLab.


Welcome to Eyes on Hawaii on the Think Tech Live streaming network series, broadcasting from our downtown studios at Pioneer Plaza at the core of downtown Honolulu. I'm your host, Carol Cox. Joining me in the studio is Ms. Bridget Hamakwis and Ms. Eileen Ketcheland, actually by Skype. And today we're going to be talking with Ms. Hamakwis and Ms. Ketcheloin about the deal at the Department of Health and the Big Island Dairy. Remember that our talk shows are streamed live on the internet from 12 noon to 5 o'clock PM every weekday. And earlier shows are streamed all night long. All our shows are streamed in livestream.com. If you want to links to our live streams or previous broadcasts which are available on youtube.com or if you want to subscribe to our programs or get on our mailing list and get our program advisories, go to thinktechhawaii.com. If you want to pose a question or comment during one of our shows, please tweet us at Think Tech High, that's Think Tech H.I. Well, thank you for joining me and this is Eyes on Hawaii. We talked last week about the subject of the Big Island Dairy and some of the issues that were going on and the impacts and the environmental impacts that were taking place there. And we had some of those community members, or one community member. And we had Ms. Bridget Hammerquist on with friends of Mahau Ulepu from Kauai. Now we decided to do another story on this because since that story, there was a recent development. The State of Kauai Department of Health fined the Big Island Dairy some $25,000 for some of the alleged violations of the Clean Water Act. And other violations and some compliance issues. So having said all that, let me welcome, I guess, Ms. Bridget Hammerquist and Ms. Eileen Ketzloin. Thank you for joining me. Thank you. Hi, Carol. Nice to be with you. Hello. Yes. Well, you should be all smiles, at least with your hard work and there's nothing to laugh about it. Actually, we should be crying, I guess, when we share with the public what we found and what has been tolerated for these years of contamination, pollution, and the impact on the community. So why don't you introduce yourselves and tell us how you got involved with this briefly and where are we going from here and is this a good thing? Okay, Carol. I'm Bridget Hammerquist and I've served now for three years as a President of Friends of Mahau Ulepu with grassroots community-based organization here on Kauai that has been very concerned about the quality of our drinking water and our ocean and our streams that's been threatened by a proposed industrial dairy similar in size to the Big Island Dairy, O'Kala on the Big Island, and unbeknownst to us that dairy started operating in 2014 and the community there was reporting wastewater through their streams and into their actual villages, into their homes, into their yards as early as June 2014 and prior to that. So within months of Big Island Dairy's commencing operation, they have manure wastewater right in their yards and they complained about odor, they complained about the manure, they complained about the contamination of their drinking water being a risk and the state came out and spent three days inspecting and found waste was actually running from the dairy through their village and out to the ocean. So it confirmed what the people had reported, but then the state didn't do anything about it. So years went by and they had other floods and the state was back there in 2016, still nothing was done and someone from the community just happened to find our website. They found us, we didn't find them. There are a small community, they don't have a website yet, but they were searching and they found ours and they sent us an email and said, you guys are doing a good fight over there, please keep fighting because you don't want in Kauai what we're experiencing on the Big Island. And that's how it started. I emailed the gentleman back and said who are you, what are you talking about, what's happening and then we were told what they've been suffering with and that there was another community meeting happening, not their first, but another and he said, maybe you'd like to come and hear what we're going through and learn more for your fight.  And so that's how the affiliation between what they now call their Kauai Ohana and the Ohana of Ocala formed. And doing this response to this email that you received, we actually travel, I went with you and others to document and to investigate what was transpiring and what took place. And what we found was absolutely nightmarish when you can common sense things that should never be taken place, for example, the spraying of the manure water and onto the area that supposedly were for crops. But we found that, consistent with what the state had found in earlier, that it was running down into the streams and down into the coast and on the cliffs and what have you.  Quite sure it was wrong to be spraying cow manure, laden water into the air and the homes down below. So Eileen, you recall that moment where we both in a hurry, the rush back. Yes, and how we flipped the Yui to get back there because I went on my cell phone and looked up the wind speed. And at the time it was 16, I took a screenshot of it. And 16 mile an hour winds is not a time to be spraying. And this is a cannon type sprayer. So it's spraying a huge stream way up into the air and it was blowing everywhere. And it was brown. And it was brown. You could tell it had manure in it. I mean, it wasn't, there was no issue that it was wastewater. So the bacteria was becoming airborne. And aerosol. And so that brought on a bigger problem because what was happening brings on illnesses and airborne bacteria that is generated potentially breathing in and what have in. People have been reportedly sick and then one they believe without full confirmation yet is that one has become ill and actually is deceased now because of this or some connections to it. We don't have the medical records to show that. But it was consistent with what people are concerned with.  And the snail, the semi snail that was noticed to be increased in population once it's flowing of manure and wastewater down into the community. That's the semi slug. And a lot of the residents over there have noticed that they went from having none to having an abundance of them and having them crawl up the side of their house. And they take, fill in their patios, going in their vegetable gardens and crawling all over their vegetables. Recently, one of the residents sent me a video of her backyard at night. And we found like a two foot square. I counted 11 semi slugs and she has her garden. This was on her garden. Yeah, they've had to stop eating their vegetables, Carol. Not just because of the contaminated water, but because of these semi slugs. And you'll recall, Carol, you videoed one woman who came to the meeting. And that was her first complaint. You know, before the manure came into her yard with one of the floods. She said, I never saw these snails. And now they're everywhere and I can't get rid of them. And then we went online and did some research and found out that 75% of the slugs over there are contaminated with rat lung worm. And it's a parasite. And then we checked with the University of Hawaii campus. There's two researchers in Hilo. And they confirmed that Ocala has a particularly large population of semi slugs. They'd already been out and they were researching around the island to track and find out where they were. And they'd already identified Ocala as a place where there's a specially large concentration of these semi slugs, but they didn't know the people. The researchers didn't realize that that community has suffered several floods with manure, mud, wastewater from the dairy running freely into their yards, under their homes and several places into the homes. And there is a direct connection between waste and these semi slugs. They like manure. They like rat manure. They like any kind of manure. And so they are attracted now to those yards and they're living there in a greater number than ever. Now, we talked about that to some degree. Let's go back to the actual legal action that was taken against the big island dairy by the Department of Health. $25,000 assessed. Do you believe that that is sufficient or do you believe what they're requiring of them now after the fact? And do you think that until they come into compliance, should they be required to reduce their herd or shut down completely? What about those particular points? Well, based on what we've read of what's happened elsewhere in the US, I think they need to either reduce the herd or they need to get wastewater treatment trucks in to reduce their effluent ponds. Because every time the state goes, they describe their effluent ponds as being at nearly capacity. And they talk about this overflow, emergency overflow channel that the dairy never got permission to build. And it's going, as they call it, an emergency spillway channel. And it's going from their largest lagoon, their 2.5 million gallon lagoon, into the Oja Oja Gulch stream, which is one of the places the state now has confirmed they've visibly seen the wastewater running through that gulch into the ocean. And they've tracked it from the dairy running through the gulch on the west side of the property, the Alaia Loa Gulch. So there's no question this dairy is leaking manure wastewater into the streams, the waters of the state, into the waters of the US, the ocean, and on its way through the community of Oja Oja. So they've got to reduce the wastewater volume in those ponds. I see no other solution. Or they've got to migrate the herd out of there and get a more manageable number so they are not overflowing their pond. They don't have a national pollution elimination system permit, which is being required by this violation citation. And if you have more than 699 cows, you're supposed to have one. Well, you're supposed to have one if you discharge. If you discharge. And they've discharged. They've moved that. So they need to thin their herd, and they need to pump out and clean their effluent ponds. And the only way they're going to do it is through honey bucket trucks type thing and getting it off of the property. And take it to wastewater treatment facility. Carol, it's ridiculous. Eileen has a quote here, but their upper effluent pond has a thick batch on the top of it.  It hasn't been drained since 2012 when they bought the place. They found it full. And yet that upper pond, according to the farm manager and the owner, is the first place they're pumping all their wastewater into. Now, how do you pump into something that's already full? You know it's going to overflow. The state's been there twice. And they've seen it overflowing. They've seen the kaka water all over the ground. So this is not a mystery. This is not difficult to assess. But they didn't do anything in 2014 because the community didn't know how to make noise. Carol, people in Cala didn't even know that they could order themselves. They could request DOH lab to come out and test for their water quality. But they didn't talk a lot of do that. And we actually covered the cost for them. When they caught the water test at Carol, it was off the Richter scale with peak of bacteria. So I, the lab called me and said, I didn't know what you guys wanted to do with these results, but I have to tell you, I've got to report it to the state. I said, oh, absolutely. We would want it reported. We don't want to keep a lid on it. We're trying to help them expose what they've been suffering with and what they've been exposed to. Two little children, one year old twins. Yeah, well, here's a situation with this bridge. Okay, down with Salmonella. I mean, can you hear me? You know what? The Department of Health is calling in the parents, saying it was a bad Salmonella. And the parents, they want to know where the parents had the kids. They're looking at the parents as if somehow the parents are responsible for the Salmonella. They called me up on Sunday. They said, what do we say to the Department of Health? I say, you tell the Department of Health to come test that air because the doctor told the husband of the woman who died that she got airborne bacteria and he doesn't know how she contracted it. She became septic and she's 42 and she's dead. Are we gonna have to take a break, Bridget? One year old twins are safe. Hold that thought. We're gonna take a break here shortly. And there's so much to talk about. So what I will say, we'll be back in a short bit and we'll take up this discussion of the Big Island Dairy and the penalties assessed by the Department of Health, state of Hawaii, some $25,000. Is that enough or is that just a drop in the bucket? And should the public be required to police this business when in fact we have a regulatory body in place that allow this to happen? So we'll be back and we'll take a short break. Aloha, my name is Steven Phillip Katz. I'm a licensed marriage and family therapist and I'm the host of Shrink Rap Hawaii where I talk to other shrinks. Did you ever want to get your head shrunk? Well, this is the best place to come to pick one. I've been doing this. We must have 60 shows with a whole bunch of shrinks that you can look at. I'm here on Tuesdays at three o'clock every other Tuesday. I hope you are too. Aloha. Okay, we're back and this is the Carol Cox on Eyes of Hawaii and we're basically talking about the Big Island Dairy and the impacts that it has on the community of Ocala. My guest is Ms. Bridget Hamakwish and Ms. Aileen Ketchelowen from Kauai. Now they had, why are they involved? Well, you see, they were threatened with in the Kauai community, the island of Kauai. There was a proposed dairy there and they were able to legally challenge it and so far beat it back in a sense, but you can just never know. But with all the promises, they had alarms to go off there on Kauai and the alarms were the environmental concerns, the environmental impacts and all of those things. And so this group was quite sharp. Friends of Mahaa Olepu. And let me tell you, they were right folks because the enforcement that we found lacking in Ocala or the Big Island Dairy is absolutely, something is absent, something is missing. So ladies, thank you for joining me again and let's go at it. You had a couple of points that you wanted to talk about. I wanted to go over and read some quotes that came out of the notice of violation that was given to Big Island Dairy from the Department of Health, just last Friday. However, the CNMP drawings for the lagoons specified 7 million gallons capacity, which differs than the 2.5 million gallon volume capacity stated by Big Island Dairy representative. It does not include, as well, an overflow spillway. So the CNMP is their management plan that was submitted to Department of Health and approved. And they were supposed to follow it. And they obviously haven't. 2.5 million gallons versus 7 million gallons that's a long ways. And then the Department of Health goes on to say that the exact as-built drawings of the lower lagoon and overflow spillway were not reviewed as a component of the inspection. And I have a big question, why not? That would tell exactly how many, but they go on to say that Mr. Duff stated that he did not believe the standing water which they saw in the overflow. In the lower lagoon spillway was from the lagoon. But from stormwater runoff from up gradient land caused by recent heavy rainfall. This was inconsistent with the statement made by Big Island Dairy representatives during the opening conferences when they stated that the lagoons do not receive stormwater runoff. Why they don't receive stormwater runoff? I don't know because they are downhill. So they don't get it and another point they're claiming they do get it. Now the CNNP, there was one supposed to be in place already that was before it's opening. At least the one has the 7 million gallon effluent pond. So why was it not in place? They're not following it. They're not following it. So the penalty then is they have to now do a new one. So that's not very promising if they've been allowed to operate knowing they had submitted one and whether completely incomplete, they'd submitted one and yet the state allowed them to operate that way. So I think you're justified in your actions and your aggressiveness toward this issue on your island because as they promise, it will be an aggressive enforcement regulatory body on this, that's the Department of Health and other agencies. And here Big Island Dairy is operating without any of these controls or things that are in place. So what do you say? Three years without adequate regulatory action. I mean even the chief of the wastewater branch was unhappy because nobody told her that was going on and nobody said, you're not there and you know they didn't build it as to the plans that were approved. This is a violation, she said to them. You know Carol, you've got her emails and why they didn't review the As Built Plans we couldn't find when we did our request for documents we couldn't find any As Built Plans with the Department of Health. So I don't think the Dairy ever took back to the Department of Health which they're obligated to do under the law. They're obligated to let the department know if they changed the plans that were approved. It says it right in the regulation, the guideline that they have to let the department know and we can't find that they did let the department know that they built it differently than what was approved. But wouldn't you, if you were- It's not a situation with the upper lagoon. But if you were this Dairy and you could get away with this, I mean whose fault is it? Is it the State Department of Health who has a regulatory and fiduciary responsibility? It's as if we're suggesting that well they didn't they did as much as they could to get away with it. But the bigger question that looms over us all why isn't our regulatory body, the agency on top of this and they're permitting this activities and then just sit back on their thumbs and allow it to develop inexcusable. You know Matt Curano explained to the community they have five people I think he said that work in enforcement for the whole state of Hawaii and their job is to follow up on every complaint for wastewater discharge whether it's from a veterinary hospital whether it's from a power plant whether it's from a county. The only problem is they never do a complete inspection. Like the first time in 2014 they didn't take any water samples when they should have to find out. And right now they should be taking regular water samples because it is polluted. Yeah, but I think they knew what was there in 2014. He didn't have to take samples because Neil Mukai did a good report and he said it smelled like manure, it looked like manure and it was brown water running through the community and he traced it all the way back up to the dairy. And so he actually concluded in his report correctly. But they didn't do anything. No, they didn't take a rate. No, but he sent his findings to Honolulu and the Honolulu staff who are the enforcement. They didn't do anything. He did everything he could on the big island, the DOH representative there. And I think, Carol, you might have met him when we were in O'Connor. Yeah, well, one of the things I'm thinking back as we did that helicopter flight and that flyover. You can see the water in the, I mean putrid water in the canals or in the gullies in the gulches. And then you fly over and we go down in the helicopter and go to the cliffs and here we are seeing stained, the color of cow manure on the face of the rocks on the cliffs. Then to really drive home to point that something is out of whack here, we find, what do we see? A plume. Now, this is a time to get off your duff for the state, $25,000 sounds like a lot of money, but then what is the irreversible impacts on the environment and the people in the community? Is it worth $25,000? And my suggestion to the friends of Mahalapuk, keep fighting and don't drop your guards because one of the basic faults that I see in this whole process is that they say they don't have enough manpower. They don't have enough money. Well, then they need to get out there and tell someone this and they need to be in the legislature asking for more money rather than wait until the public get deprived of their rights for clean air, clean water, clean life, be able to guard and sustain themselves. Instead, they tell us we don't have any money. And that plume that you saw from the air and you've got great pictures of, Carol, of the phytoplankton in the ocean, that's exactly what blooms when you put extra manure into the ocean. Nutrients form what they call eutrophication and all of a sudden these extra algae and phytoplankton develop and it was a huge plume. And remember the pilot said nowhere else on the whole coast of that Tamakua area could you see anything like that except right in front of the Ocala? Well, I don't want to use a term vindicated because I believe you were right in your first action that you took on Kauai to fight this dairy over there because we have the same regulatory body that is handling this. And look what we have, we have plumes. That's what you complain about and are concerned about on Mahalolepu while Peely Ditch stream, right? So these things are coming home to roost these chickens. And it's gonna go down from Mahalapu down to Poipu which is one of the favorite beaches in the world where little kids swim because they have a little kiddie pool. And that little kiddie pool only has water coming in. It doesn't have good circulation. So we just can't have it out at Mahalapu.  Thank you. Anything else on this, this about the upper lagoon? Because there's an older upper lagoon that was in place when they bought in 2012. In 2012. And this is what's in the state report. Yeah. We gotta have one minute so make sure you go and refer it. Vegetative map on the surface of the upper lagoon prevented the facility employees from accessing the lagoon for cleaning. The upper lagoon had not been cleaned since the current owners purchased the facility in 2012. The vegetative map is gonna have to go all the way down. There's no room in there. They're saying there's a million gallon room. At least that's what the dairy was telling us. There's no room. There's vegetation in there. Well, we'll have to take this up again because 30 minutes is not enough to go through this whole thing. But thank you for joining me, but thank you more than that for the fight that you're helping this community and helping the environment and helping all of us. I really appreciate it and publicly declare that. So thank you. Well, thank you, Carol. Alrighty. Thanks. Okay, we're out of time and we'll have to wrap it up. I'm Carol Cox. This is Eyes on Hawaii on the Think Tech Live Streaming Network series. We've been talking with Ms. Bridget Hamakwis and Ms. Aileen Ketzel about interpreting and discussing the NOV issued by the Hawaii State Department of Health on the Big Island. Thanks to you, Ms. Hamakwis and Ms. Ketzel Owen for being here. Thanks to our broadcast engineer, floor manager, and to Jay Fidel, our executive producer who puts it all together.  If you want to be on our email and social media program advisors, click the link on thinktechhawaii.com. If you'd like to be a guest, underwriter or a volunteer, if you want to join us in our downtown studio here in Pioneer Plaza, contact Jay at thinktechhawaii.com. That's J-A-Y at thinktechhawaii.com. If you want the links to our live streams or our previous broadcasts or use stream TV or YouTube.com, just go to thinktechhawaii.com. Go there to our Facebook page and tell us that you like us. We'd love you to like us. And of course, I'll see you next Tuesday for more on Eyes on Hawaii. On Thinktech, I'm Carol Cox. Aloha and thank you.