Welcome, everyone. I hope you're having a good conference so far. It's a little bit of a marathon, the first part of Monday, getting into the swing of things, going to the Dries Note, seeing all the sessions, getting your schedule together. But I do hope it's going well. You are here today at the Drupal.org Accelerating Contribution Panel. So hopefully that's where you intended to be. There's still time to run for the doors. But we're gonna be talking about what we do at the Drupal Association and together with partners to support the community in building Drupal. The tools that you use to collaborate on Drupal.org, the infrastructure behind the scenes. And we're also here to answer questions, talk about possible future features, talk about kind of what's behind in going into these things. So to kick things off, here are some of the faces that you're seeing on stage. I guess you probably want to see mine as well. And the top row is members of the staff of the Drupal Association engineering team. The bottom row are either sort of volunteers or partners who help us with infrastructure, security, and things like that. So we're really grateful to be with you here today. I think I'll hand the mic down the row or we'll share mics down to do some brief introductions. So I'm Pestinette. You've seen me all over Drupal.org, Drupal Slack. Today I'm the CTO here for the Drupal Association. So mostly what I try and do is block and tackle so these folks can actually get things done. Hi, Neil Traum. I do development for Drupal.org, architecture planning, and yeah, bit of everything. Hi, I'm Brendan, Beeman on Drupal.org. I build things, break things, fix things for Drupal.org and subsites. I'm Alex Moreno. I just joined the Drupal Association a couple of weeks ago. So very exciting to be in my first Drupal con North America. And I will talk about me and what I'm going to be doing in the next years. Hi all, I'm Fran Garcia. I work as well with engineering team. I've been helping a lot migrating some of the sites from D7 to D10, as well as helping out with Drupal.org features, yeah, broken things. And as well with the GitLab acceleration which you will listen to in a little bit. Hi, I'm Norton or Narayan Norton. I am the lead systems engineer for Drupal.org. I was here when we upgraded Drupal.org from four, seven to five, but for some reason I'm still here. Right now focusing on modernizing our infrastructure and moving to Kubernetes and split between the cloud and OSL. Awesome, I do want to do a few thank yous. So Narayan is also the CTO at Tag1 Consulting who are our infrastructure partners in supporting all of the back end of Drupal.org in making this work. We also host at the Oregon State University open source lab, which is a place that we and many other open source projects have been at since the very early days of open source projects realizing they had to get out of someone's dorm room and maybe do something slightly more professional. So many thank yous to them. I want to talk a little bit about what the Drupal Association invests in engineering resources. When you become a member, when your company becomes a supporting partner, when you sponsor DrupalCon, when you buy a ticket, a lot of that money goes to directly support this team and our operations and support. We have close to $500,000 in direct costs. We get more than half a million dollars in in kind trade for services we could otherwise not afford salaries for personnel. More or less 50% of the net revenue of the Drupal Association goes just to pure engineering programs, Drupal.org support infrastructure and this team. So your support goes a really long way in making what we do possible and in turn making Drupal possible. So let's talk about Drupal Acceleration in particular. And as you saw in the keynote and as you've been hearing a little bit throughout the conference so far, the Drupal Association is trying to take a greater role in accelerating innovation in the project and Alex with his third week on the job is gonna talk a little bit about where we're going with that. Yeah, so I'll keep it sweet and short. As I said, I just joined the Drupal Association so the only update I really have about this is, hello, my name is Alex Moreno. I've been working in the industry for more than 15 years and I've been doing so many roles between small and big and huge and enterprise companies. So I think I have a little bit of context and experience on what we need to do here. And at some point, a few weeks out, I became jobless and something, first I got very scared, but something amazing happened that some people at the age contacted me. It's like they show me the strategic plan for the next few years. I thought to my goodness, this is huge, right? I will be crazy enough not to accept this and at the same time I will be crazy enough to accept it. As you know in here, so I accepted the role. Some of the things I'm going to be doing is trying to talk to all the actors in the industry, trying to find what we need to do to keep Drupal as it is. Drupal has been innovative for 20 years and we need to keep Drupal that way otherwise we are not going to survive, right? So that's going to be mostly my role. There are going to be things like project coordination, find where we need to put investment from the DA on which projects and in general trying to enable individuals and organizations to try to make Drupal, try to accelerate Drupal. And if you do have thoughts, questions, suggestions about the way that we enable contribution and these sorts of things, please do come up during the Q&A portion and share those with us. And if you have ideas about what we can do to improve things like issues with three years in there or things like, you are more than welcome to come up Dr. Me. Please. Awesome. And speaking of contribution enablement, one of the big things for the Drupal Association the last several years has been trying to provide incentives for organizations themselves to create a contribution culture. So if you are building a business on Drupal, there is a sort of enlightened self-interest that, hey, maybe you should give back to that open source project but there's also now sort of concrete benefits to doing that. The marketplace on Drupal.org is built on the contribution credit system. If you're a contributor, you've seen this before. The maintainer of any project, whether it's core, contrib, theme, whatever it might be, can find any issue that you might have contributed to and said, yes, you helped us solve this and when that issue is closed, that can be factored into the organization you work for and their position in our marketplace and in our community we're trying to create a flywheel of energy and investment to increase that. Brendan's been working on some tools related to this to help the organization owner. So if you're one of those people who owns a business that either contributes now or is interested in contributing, he's built a few features to support you. Yeah, so I should preface this, the right image is work in progress. Currently, the owner tools are visible to organizational authors and it gives you a window into where you stand as far as your contribution and on the right, it's just a much more fleshed out. It's basically most of the things that go into determining marketplace rank, gives you an idea of how you're doing in the ecosystem of contribution. Yeah, not super exciting because it's not super public facing but I'm hoping it will help organizations work with us to have a better understanding of how they can help contribute going forward. And part of the increasing transparency we're trying to create is if we want to point to some specific initiative and say this is strategic for Drupal, we wanna be able to go to an organization and say here's how you can contribute to that, here's the concrete benefit that that contribution will have and here's how you keep track without having to have a one-on-one conversation with an engineer or a salesperson on the Drupal Association staff because we want that contribution enablement to be scalable. Correct. Brendan's also done some work to support those of you out there who organized local and grassroots community events. Hopefully you're familiar with this feature but Brendan, why don't you walk us through it? Sure, yeah, we built the community events system. Oh shoot, I don't know, two years ago now. And since then have gone through a few iterations, adding features, fixing some things. We're now recognizing sponsorships of organizations on, or sponsorships of events on org profiles. We can export event data, just recently, events became a multi-select field, event type became a multi-select field so you can have a contribution camp as you can see. A lot of smaller cleanups too, some big ones hopefully on the way related to time zones, time is hard people. But yeah, just anywhere we can, we're trying to support what we can. Another piece of work that I've been doing is getting Drupal nine, sorry, events.drupal.org onto Drupal nine. We partnered with 611 for the theme migration. Leveraging paragraphs now, it's much easier to use for our content editors and content creators. We no longer measure page load times in full seconds. And now that we have the new D9 infrastructure in place, we can use DDEV and do development locally, which is fantastic, thank you Narayan. Awesome. So the next thing we'll start talking about is how the Drupal association is collaborating with core on certain initiatives. This is something that Neil in particular is kind of in the middle of in a number of different areas. And this was the seed for the Drupal association taking an increasing role in product innovation in Drupal. To do automatic updates or project browser, it was going to become necessary for Drupal.org to provide that data. We serve the updates, so any feature of Drupal that requires updates data requires Drupal.org. And our experience in getting involved in this says, hey, perhaps we should be involved in other ways with product innovation. So I'll turn it over to Neil. Yeah, so if we're doing automatic updates and project browser, we want a stronger security around what your site's running since your site's gonna be writing its own code. So that's supply chain security. There's a project called the update framework, tough from the cloud native computing foundation, I believe, and they designed a standard for software updates, metadata, and downloading the updates themselves to mitigate a number of types of attacks that someone might try. So then we implemented rugged with help from our contractor or consensus enterprises to do automatic signing of targets. Targets are as tough term for just something that's signed. So all the metadata, all the package zip files, everything that composer does. And yeah, we have a proof of concept deployed in a staging environment and we're working towards the next steps. So we need even more metadata, security related, like what's the security release, what's the security advisories, and need that signed as well. And Drupal Core is actually on, it's on packages.org, not packages.drupal.org. So we need a way to sign that even though we don't run packages.org. And yeah, the next steps are testing, finding, fixing edge cases, and third party security audit. Yeah, which is something we're working on and something that takes a lot of funding. As an example, we've been working with the open source technology improvement fund. And they estimate between $85, $115,000 to do a proper audit of the code involved in this package signing, which is an investment we have to make as a project to ensure that the update system is going to be secure. But it is a place where again, we simply can't do that without the support of partners and individuals to make that happen. And certainly if you're interested in the domain of supply chain security and the things involved in this, you can learn more in the auto updates channel in Drupal Slack or you can come talk to us somewhere at the event. We're happy to tell you a little bit more about why we chose this model for Drupal's update system. From here, we're gonna talk a little bit about Drupal.org project endpoints. So Fran, can you explain what this feature is and what it's for? Yeah, sure. So you may have heard about Project Browser. Right now, Project Browser is consuming data from our old unofficial kind of D7 API, which has its own formatting. And it could be ideal for Project Browser to read live data. We decided that rather than spend more time on the D7 site that we would need to migrate at some point, we could start building things on Drupal 10. So that's how we started. We migrated the project's content to get it with the related information, like users and supporting organizations, et cetera. And then we exposed all that data using JSON API as you can see over there in the screenshot. And then based on that JSON API endpoint, we built Project Browser plugin. That's how we are calling them, a source plugin where we can read information from. And then once we created that plugin that allows, actually, Project Browser to show real life data from all the projects that are on Drupal.org. This right now is a little bit of work in progress. So a lot of the ground work has been done, like the migration, exposing data on the JSON API, but we still have some challenges as we do have an old database and we do have a new database. We need to leverage the new infrastructure for it. And then we need to have all those processes running in parallel, both D7 and D10. So this is something that should be coming up soon, but yeah, this is the endpoint that will feed eventually Project Browser. Awesome, and we should talk a little bit as well. Well, did I miss anything, Fran? Yeah, okay, good. We should also talk about Drupal 10 upgrades for Drupal.org. So as some of you probably know, Drupal.org is often one of the last sites to upgrade to the latest version of Drupal because Drupal.org does some unique things that know where the Drupal site does. Most of you out there are probably not serving the updates data for Drupal sites to update with, for example. Most of you are not serving a localization server and multi-lingual in these other sorts of features. So to migrate these things, we rely on the help of the community and on the allocation of time of this internal team when we have that time available. So there's been a variety of progress towards these updates and we'll go through briefly some of these things. First of all, I wanted to thank the community volunteers for localize.drupal.org who basically completed and handed off a Drupal 9, Drupal 10 update of the localize site. Not completed yet, but... Well, are in the progress of doing. Yeah, significant progress. Yeah, yeah, the core translation modules are all in really good shape and there's a few things we have to do, like the theme for Drupal.org is not completely migrated and things like that. I'll go back to the slide briefly. So as Brendan mentioned earlier, events.drupal.org is complete. API.drupal.org is sort of waiting for deployment on the appropriate infrastructure. We've been hard focused on the secure signing problem that we've talked about before and that takes priority over these migrations but these are in the queue ready to go localized.drupal.org and then www.drupal.org starting with the project browser endpoints that Fran just talked about and then other features like contribution features that we're gonna be talking about in the GitLab acceleration portion. Yeah, and should say for www.drupal.org we'll end up running both in parallel for a while. So if you update a project on drupal.org you'll be updating on Drupal 7 and then that'll migrate to Drupal 10 and get to the project browser endpoint JSON API and we'll keep shifting more and more things towards the 10 or 11 column. So from there, what's left before we actually start deploying these sites? I think I'll hand it to Neil again here to talk about a few of these features and then also to Ryan to talk about kind of getting production ready for some of these things. Yeah, so all these sites have single sign-on with each other in Drupal 7 and before that we had a project called Bakery for managing the cookies for single sign-on but we're moving towards key cloak so there'll be different customizations around that to authenticate a single sign-on and also enable social sign-on and third parties to be able to authenticate against your login with your Drupal.org ID. So a lot of that migration's ready for review and it's been waiting on time to deploy. The theme, the people working on Localize did a lot of work on Blue Cheese, which is our theme. So that's in a good spot and Blue Cheese is actually mostly CSS that we really avoid PHP code in the theme so hopefully we can maintain the two branches of that and parallel and merge from one to the other as we can't put everything on pause and start updating, concentrate on updating sites because people keep asking for features. So Narayan, could you speak a little bit to the infrastructure that backs the Drupal 10 sites and in particular how it compares to what existed before for Drupal 7? Yeah, so what we've been doing for quite a while now is kind of chewing through some tech debt and this is our first opportunity to kind of build from scratch something that we actually want to run and is using technology that is well understood and often used these days and not like Jenkins running puppet. So we built that for first events and API and we're using those as tests. Events is up on it, is running on Corentes. With the cluster deployed via Pulumi we use Rancher for the developer experience and then consistent deployments via Argos CD. Events and API are pretty good first test cases because they didn't require live migration. The project browser endpoints and Drupal.org itself will require live migration so that's where we're gonna have to actually connect our old database cluster or make our old database cluster connectable from this new infrastructure which means having a VPN endpoint from the OSL into an AWS VPC so that's the next part of this. Our old database cluster is old like capital OLD. So it's something that we want to have an actual live migration from because just dumping it out and restoring it to a new version is gonna be troublesome. It's always troublesome for Drupal.org because of our international user base. So yeah, so basically what I was talking about right there. The next step is the DB upgrade. We have been focused on tough signing which is what we were talking about earlier where we were taking the work from the rugged project which is the PHP implementation of the tough protocol and making it deployable in a modern best practices way. And building out containers that we want to run long term and are actually maintainable to run long term. That has gone very well and we have that running and staging. We'll probably pivot to production fairly soon to have a production-ish endpoint for testing and then we'll go to the project browser and a lot of this will be fairly set. The one exciting thing on the list here is Tecton which is a CI CD system where you can define the pipelines and tasks that are associated with a site right next to the site in the deployment manifest so that developers are more able to contribute and define exactly the tasks and pipelines they want running alongside the site. A lot of people don't understand that like Drupal.org is not just to the site. We have a Jenkins instance that is truly terrifying of just all the various tasks and pipelines to build packages and clear caches and aggressively unclear caches and having all of that defined in code right next to the actual site that can be cleanly deployed in between environments and even locally for testing is gonna be a huge step forward for us. Awesome, thank you. So now we wanna talk a little bit about the GitLab Acceleration Initiative and in particular the very specific tools that you use on a regular basis to contribute to Drupal. So this is how you get the work done when building Drupal and making the project better. So we've made a lot of steps in this direction. You've also probably seen these updates in a variety of Drupal cons. So it's an involved process and a careful process because we need to ensure that we don't disrupt the release cycle of Drupal by suddenly pulling the rug out from under all the tools and at the same time we wanna ensure that when we move to a new tool set we preserve some of the key innovations of the Drupal project like the credit system. No other project has this way of incentivizing individuals and organizations or even just measuring the sponsored versus purely volunteer contributions to a project. So this has been really important to the work that we're doing. So Neil, can you talk through some of the goals and kind of the outline of what we're doing here? Yeah, so yeah, the overall goal is not just to use GitLab, it's to make contribution to the Drupal project easier and GitLab happens to be a big part of that. And yeah, more standard tools, you know, more around get, you don't have to, well, you have to learn to get instead of the learning of patching and deaf and everything. And yeah, preserve the collaborative nature of Drupal. The kind of unique thing about the Drupal project is we have contribution times and encourage people to, widely encourage people to contribute back to the project and any single issues, especially core issues are handed off among, you know, three, four, five, seven people. So since this is making contribution easier, a single sign-on is kind of part of that initiative umbrella. And we're also working on simplifying Drupal.org. So Drupal.org, we used to have the database of all the commits that you made. We don't have that anymore, so there's one last thing to migrate to past Drupal 7. That's the solution for a lot of the, or some of the migration things. It's easier to not migrate it. And GitLab CI, that's available today. Anyone can put a GitLab CI.yaml file in their project and use GitLab CI. We'll talk a little bit more about that, I believe. And Fran has been working on prototyping how issue collaboration is gonna work and issue credit once we're, and also the migration towards GitLab. So yeah, the next kind of things you'll see next are GitLab CI, contribution credit. That's something you will be able to switch independently of the, you know, before we start moving issues, you'll see the contribution credit move off of the old Drupal.org onto a Drupal 10 hosted system. And same with issue collaboration. We're keeping mostly the same issue fork process, but the UI for that will be on Drupal 10. So as Neil said, today, as of today, any user who wants to switch to using GitLab CI for your project, if you're a project maintainer, that's available now. Up until this date, we have been in a sort of limited test window with about 20 contributed projects who volunteered to opt in. And we've done a lot of work to sort of get this ready. So GitLab CI needed to be, and still needs to be, sort of feature complete with Drupal CI. We needed to work with Core and Contrib for both current sort of modern Drupal and legacy Drupal 7. And for Contrib testing in modern Drupal, that's available today. It's enabled for every project on Drupal.org. There is a template that we are providing that you can find by going first to the source code link on the main page of your project, going to the ad file UI in the repository browser, typing in the name.gitlab.ci.yaml. You'll be presented a list of templates and the one right at the top, template.gitlab.ci, automatically configures GitLab CI for you, following all the patterns that you're used to from Drupal CI. So it uses include files to set up variables to let us centrally manage and keep track of what's the next supported version of Drupal or what was the last security release or what's the minimum supported version of PHP. Those are all preset variables that we'll update over time as they change without you having to manually commit a change to this file to keep track and keep on top of it. As I said, we're updating that template for you. You'll see the include files when you're browsing the template when you first save it. But for most users, especially if you're a project maintainer who is not super well-versed in testing or CI, you should be able to save that template, commit it to your project and not have to do anything further to have sort of the standard level of testing that you've been used to with Drupal CI. And a lot of work from the community and ourselves on staff went into making that possible. But the advantage of this is you now have all the flexibility and customizability of GitLab CI pipelines. You can override these variables to say you want to target a different version of PHP, a different version of core. You can change the template workflows. Anything that you might be used to from GitHub in terms of GitHub actions can be replicated in CI pipelines. So there's kind of an unlimited horizon of how you can customize CI. And I think we may see some significant innovations in sort of new tools being adopted, new types of testing, because you're no longer relying on Drupal Association to centrally provide that configuration. We do provide a central base configuration, but any project can update and override it. So next steps is we're optimizing core testing in particular. You may not know this, but today every Drupal CI test of Drupal Core runs on a 32 processor, 64 gigabytes RAM spot instance in AWS. Everything is mounted into a RAM disk. We're not reading directly from a disk. We are highly paralyzed these tests, and it still takes an hour and 20 minutes to run. There is a lot of work that goes into trying to get the core test suite to come back quickly, as quickly as we can. Right now we're working with some folks on the core team to replicate all of the work that made core tests run that quickly. On GitLab CI right now, their last attempt, I think they've gotten better in the day since I wrote this slide. The last attempt was still running in about three hours because a lot of the tricks we had used in Drupal CI to really optimize and paralyze those tests wasn't quite ready. Another way to think of it is every core test costs about a dollar from the Drupal Association infrastructure, and we run easily 10,000 in a month. I also mentioned Drupal 7 testing, and you might be thinking, oh, God, why? But the truth is we are continuing to support Drupal 7 through the end. It still has security support. There'll be another session today talking about the end of life, so we must continue to support it, make sure that we're not holding back keeping Drupal CI around just because it's our only way to test 7. So we will be working on an option that basically skips the composer steps involved, allows people who are still maintaining their Drupal 7 versions to continue testing that. So now let's talk about contribution credit and then issues, so I think I'm back to you, Fran. Thank you, Tim. So yes, he said previously we are not trying at first to reinvent anything. We are trying to get what we do have now as we can see there into a new system. So right now if we want to attribute contribution when working on issues, so you can say whether you are volunteering or whether you are working for a certain organization or customer, and then at the end of the issue, before fixing the maintainer will select which users are credited for the work on the issue. So that is what it is now, and this is how it will look like in the new system. As you know, we will talk about this in a bit. Issues we migrate from Drupal.org to GitLab, but the credit's won because we have a very unique way to grant credit to people. So right now, because we have the two systems running in parallel, both issues on Drupal.org and issues on git.drupalcode.org. So this is kind of how the new system will look like. You will just have a source link where the contribution credit comes from. We will have related information that may or may not have activity like merge requests linked to that issue. And then we will again bring a list of users whether they are contributing, which companies they were working for. We will even bring the kind of activity like how many comments did they do in all those in the issue and in the related merge requests, or even if they gave emoji reactions to the MR. So this is how the previous screen is how it will look to everybody. The new screen is how it will look for a maintainer. So by default, we are not granting the credit. We are giving the maintainer as much information as we possibly can to have them make the right decision. In this case, the UI will be pretty simple. It's just check boxes. You will just select which users you want to credit. You click on Save and that's about it. Certain other things like crediting other people. We will still remain. We do have now in the current system. And for example, users that are brought that way will be automatically credited. But yeah, we have that kind of difference between how a normal user will see it and how the maintainer will see. But we are keeping feature parity with what we do have now. And one of the things about this system is it's now sort of decoupled from the source of the activity, right? So that activity is an issue, a merge request, one that happened on Drupal.org in D7 or a new one that happens on git.drupalcode.org when we've migrated those issues to GitLab. Yeah, definitely. It's as decoupled as it gets. I mean, we do have three systems talking to one another. We have the D7 issues, the GitLab issues, and the D10 and Drupal.org endpoint. And those three systems are talking together. Yeah, yeah, APIs. So speaking of issues going to GitLab, why don't you keep going and tell us like what you've built in prototype so far to actually move us over there? Yeah, certain. So yeah, as we already mentioned, we are trying to keep what we already have. But in the new system, a big part of it is to migrate issues from Drupal.org to git.drupalcode.org. Here is just an example of how a current issue will look in the new system. I actually did a quick demo for the TrisNode last year in Prague, where we show how the issues go from drupal.org to GitLab. That's how they will look like. So parting from that basis, we migrate all the metadata as labels, so things like the status, the priority, category, version, component. We be labels in the new system, as we can see in there. You can go ahead. And then, yeah, I did talk about this as well in the past. We have Kanban boards that we can just configure. And we can even automate certain things, like applying certain labels or removing certain labels. But yeah, this is going to be the new way of managing issues. And I think I can see a real value for folks. For example, on the accessibility teams who want to see needs review issues or RTBC issues in core tagged for accessibility on a board where they can drag those around more easily rather than just a bunch of sort of saved searches. Also, we've been talking about it a few times. So issues by default, the way we work on them, they are collaborative. So it is as well, we do have a very custom way of dealing with forks, with who has access to those forks. We try to make an issue open to everybody to work on. So they just need to request access. I mean, if they have access to the parent kind of project, they have access straight away. But what happens if I'm just a contributor that I want to help into a project that I don't maintain? So this collaborative approach is very special for us, from the community. Again, that's something that we currently have on Drupal 7. We can create a fork. We can create MRs. We can request access. So we are trying to do exactly the same in the new systems. So from GitLab issue, we will have a bot post some automatic messages. One will be about contribution records, which I just spoke before. And the other will be about managing forks, merge requests, access. And if we go ahead, we can see how that link looks like in the new system. And we can see how the new page starts to look. Basically, we will have the issue linked. All the forks that are attached to that issue, we will be able to create new forks from the UI. If we need to, we will be able to request access to create MRs. I have to say here that when possible, we are trying to leverage GitLab UI. So for example, to create MR button, you can see there is a GitLab icon. And that's just because you will be directed in there and you will create the MR from there. So that's kind of educating the users on how to use the new system. Yeah, that means that they could create MR directly from there if they learn. Once everything is done, then we can also see all the merge requests that are linked to the issue. And of course, we have a link to the contribution record. So we are trying to go back and forth between the different systems. And yeah, basically all these features is what we do have right now on this seven, but built in the new D10 system. And there's a few ways that you can help with this process. So there is a meta issue for the entire GitLab Acceleration Initiative that covers GitLab CI, Contribution Credit, and the issue migration. There's a channel in Drupal Slack called Pound GitLab where you can join the bi-weekly initiative meetings, test things out, try things out that we're doing. It's really important that you help test these things as they become available. So if you are of the old school, for example, and you're still primarily using patches on your project, we really encourage you to start using merge requests now. Patches will be deprecated. GitLab's model is not built to do patches. It can't run CI tests on patches. When we've fully moved over, patches will not be a standard way to contribute anymore. It will all be in merge requests. And so, you know, that's something to move forward on. And also, as I said, GitLab CI as of today is available for every project on Drupal.org. So in the contrib space on Wednesday, you can spend some time setting that up. And there will be folks from those sort of 20 test projects that first helped us figure this all out available to help you. And perhaps once you've got it figured out, you can help someone next to you get their project running on GitLab CI. So with that, we have about 10 minutes left. And I believe we're ready for question and answer. So if you would like to ask us any questions about Drupal.org, about GitLab, or about kind of the history of keeping Drupal running behind the scenes, feel free to come up to the mic. Ask any of those questions. And if you don't have any questions, well, thank you very much for 10 minutes back. But I'll give it a minute or two for anyone to jump up. Hi, thanks everyone for the talk and all the hard work. It's amazing to see the GitLab CI stuff go live for everyone. I'm curious for that work, is there a possibility, or even maybe there is a way already, for contributors and maintainers to run tests locally when they're working on their work to identically replicate what GitLab CI is going to run when you push up your... Yeah, GitLab has some tooling for exactly that. I don't remember what they name it or how they brand it offhand, but they have run GitLab CI locally. Yeah. And so as far as... As far as we know, that should be possible today and that might be a great thing to try out Wednesday in the contrib room and let us know if perhaps we've overlooked a config feature that might be necessary to support it. But as far as I'm aware, that may be possible right now. Awesome, thank you. Any other questions, thoughts, feedback, special requests? Well, if not, thank you very much for your time and attention. Thank you especially for your support of this very small team, trying to do a lot of things with the Drupal.org infrastructure and trying to enable you to move faster in your contributions. There's also a lot that we have kind of learned and explored supporting a project of this scale. So again, if you wanna find us later and chat a little bit about CI for an enormous project or Pulumi and Rancher and a bunch of keywords that I maybe have not heard of, I'm sure you can ask us those questions as well. Oh, and it looks like we do have another one. Yes. Do you need the volunteer help to get this project to go back? The question was, can volunteers contribute to getting sort of any of these different sorts of projects done? GitLab in particular maybe comes to mind. Yeah, depending on people's expertise and what they are interested in doing, there are ways that you can help. There were, like I said, there were about 20 volunteers who first migrated their projects on an opt-in basis to GitLab CI to help us figure that out. There may be other sorts of things like that. So again, I'd look out a little bit for a table on Wednesday and then in general, in terms of supporting Drupal.org on a volunteer basis, Neil, maybe you had some comments on that. Yeah, so I, with GitLab CI, those templates are brand new. There's gonna be a couple rough edges. So helping improve the templates themselves also will be key and really that's something we hope the community can run with and we don't need to be responsible for maintaining those templates ourselves along with the containers they're backed up by. Yeah, we can't move everything to kind of standard containers since Drupal supports a lot of things, a lot of environments to run on. And yeah, for general, like Drupal site building, we have dev sites so that's available and yeah, there's opportunities depending on what you're interested in. To go into that in a little bit more detail, if for example you wanted to, you had a great idea for a feature, actually an example of a contribution that we did have that came from the community was the ability to set your pronouns on your Drupal.org profile. A community member requested in the Drupal.org issue queue to have a development site made available. They built that feature and they sent it back to us and said, hey, can you review this and deploy it if it's ready to improve Drupal.org? May I ask a follow up? Yes, please. Okay, that was in built for Drupal 7, right? It was that particular feature. And is there any opportunity to do volunteer work to in Drupal 10 for Drupal.org? Let's see. So, you know, the localize, the people that are on that slide, they're all doing that. And yeah, api.drupal.org, I don't know, probably needs more time. The API module itself, I mean api.drupal.org, it's 99% one country module, 1% us doing some site building. So, there is a huge opportunity in there. There's a lot of testing people are opening new issues that people are actually submitting new patches. There is even an install script for you to like have a API site running locally. And then you can test it with pretty much any contrib module available. And then, yeah, you are free to submit any issues. I will most likely get the notifications or any of us will review and yeah, be able to, yeah, allow you to do it. Yeah, and for Drupal.org itself, we do have a repository with the code base on Drupal 10 or nine somewhere, but it's not, we haven't had time to look at it lately. So, I don't know, last time you touched that, but yeah, it's not quite inactive development yet, but it's moving in that direction. I would stick with the subsites and the GitLab work for the moment for areas to contribute and we'll continue to post issues with the plans and places where people can become more involved. I'm a big fan of the tugboat support that's rolled out on Drupal.org. Yes, true. For projects and I feel like not enough projects and maintainers, many don't even realize that that's available. I'm curious about ways that we could highlight that or even I was thinking about it when you were showing how the GitLab CI template and how that's configured to be added through the GitLab UI, is it, are we open to the possibility of things like that of allowing like the ability to add a tugboat template in that way? You know, that's a great question. There is a project, Drupal.org slash project slash GitLab templates and right now the main template it has is a GitLab CI template, but there are absolutely other third party tools that need a CI, that just need a YAML file to get them configured like tugboat and like others. I personally would be open to, yeah, someone opening a merger quest saying hey, we'd like to help people use this third party tool, that third party tool. There's also some integrations built directly into GitLab that at some point we might enable. There's a Gitpod integration. I don't know if it does everything we need to do the full Drupal pod experience that some folks are used to yet, but I think that's something we should work on. Great, thanks. Awesome, any final questions? Feel like every time I start it, someone jumps up to the mic, so that's why I gotta ask again. No, but again, thank you very much. We really appreciate your support. We appreciate your interest in this kind of very behind the curtains, very technical kind of content. And understanding that what it does is it feeds the ability of you and everyone out here at DrupalCon and around the world to actually make these contributions to Drupal to try and make those innovations we talked about and Dries' main stage really happened. So we appreciate just that this moment in the very bright spotlights to tell you a little bit about what happens behind the scenes, and we appreciate your support. So you'll see anybody on here on stage around throughout the conference, again especially on Wednesday during the contribution day. Feel free to say hi, ask us more. We're happy to go into details. And thank you again and enjoy the conference.


Okay, we're back. We're live. It's Wednesday, 10 o'clock, rock. I'm Jay Fidel, think tech, and we're doing today research in Manoa with Andrea Gabrielli, graduate student at the Hawaii Institute of Geophysics and Planetology in the School of Ocean and Earth Science and Technology at UH Manoa. But today he's not there. Today he's in San Francisco. He's at the meeting of the American Geophysical Union, which is a big deal. So we want to talk to him. We want to get a handle on what's going on in that meeting in San Francisco and learn, as he learns, what's going on in the field of geophysics. Welcome to the show. It's nice to see your smile and face, Andrea. Thank you very much, Jay. Good morning, everyone. Nice to be here. Nice to talk to you from San Francisco. So, Andrea, tell us what the Geophysical Union is. When was it organized? Who is involved in it and what does it do with these meetings? With pleasure. So basically, the American Geophysical Union meeting is that the American Geophysical Union is the largest organization in the earth science in the entire world. It was founded in 1919. And it grew exponentially from having just 20 members, 20 attendees were present in their first meeting, which was in 1920, here in San Francisco. And right now, last year, for example, we had more than 24,000 people attending from more than 110 different countries. That's major. When you compare that, say, with the IUCN that happened here in Honolulu last summer, we had 10,000. This is more than twice as many as one of the biggest conferences we here in Honolulu ever had at the convention center. Right. This is, this union is basically, it spans from so many different fields in the geoscience. We're talking from earthquakes and volcanic activity, but even drought, hydrology, atmospheric sciences and planetary science. And not only universities are here present with their research and their faculty people, but also some federal agencies such as NASA and Google, but also the FLIR and other companies that are interested in sharing their products, their research, their future plans with the science community here in San Francisco. So it's not, it's not only the academic community. Absolutely. Industry. Industry and federal agencies and universities. So it's really, really a large and extended meeting with so many different events and things going on every day. Usually, I was talking to some friends of mine here who are also in San Francisco. And usually, everybody starts around eight o'clock in the morning with some breakfast and talks with colleagues. And then we're off into the most corner center, which gets his name from one of the former mayors of San Francisco. And we're right in downtown. So attending conferences and lectures. And then we have a huge poster hall. So I believe we also have a picture of that. Yeah, let's take a look at some pictures now, Andrea. Okay, this is the picture of the poster hall. And there must be hundreds just within our view, maybe thousands even altogether. Describe what happens here in this poster hall. So basically, these, the AGU meeting is organized in sessions. So every discipline, such as, for example, planetary science has different sessions. So one session specific about lunar geology, or, for example, exploration of the outer solar system, or even Mars and other planets impact craters, for example. And so it's organized in sessions so that people can attend the sessions or they are most interested in. So here, for example, you can see in these pictures, this is the poster hall. We have thousands of posters, thousands of people presenting their research. So what usually happens is that you have a program of all the sessions and all the people who are presenting there. And you can get a number. So you can, it's really well organized. So you can walk directly to the session and then you can talk to the people who are presenting. That's very good. That's very good. And this is the poster hall. So it's organized in such a way that a poster is hanged over there in place around in the morning about eight AM in the morning. And then the people usually leave a sign next to the poster saying, I will be here between this time and this time so people can go and talk. Sure. Everybody wins. Everybody wins. Absolutely. And so and so this is a poster session. But then there are also other kind of sessions which are presentations. So usually, usually there are presentations. So there are talks which are 15 minutes long. Yeah, we're looking now at a photo of a talk with a huge big TV screen. Somebody is presenting on something. So can you describe this photo for us? This is the NASA booth. So you can see this is NASA. These are NASA scientists presenting about the most recent missions. So you can see it is really well attended. Because AGU with all these talks and all these different agencies present is a fantastic place to get to know more people and even start new collaborations, showing new ideas and having more projects. Well, let me ask you about that. And, Andrea, you know, when you go, you said you had some friends in San Francisco, but do you have friends at the conference? Do you have colleagues that you already know that you plan to look up that you have met by by agreement at the conference? Absolutely. In fact, for example, the Hawaii Institute of Geophysics and Planetology, which is the Institute I work at, is basically present with 20 plus events, I mean, with which include basically talks at sessions and also posters. So I was one of the first who presented here because I was on Monday morning. So I believe we have a picture of me, I think standing next to you. So just to show how it looks like, I mean, these posters. So the posters are actually quite big. They are one of the very big posters compared to other conferences. But so I was one of the first who presented here in San Francisco. But some of my colleagues that were also present that will be talking on Thursday. So, for example, my supervisor, Professor Robert Wright, is going to talk on Thursday morning about a new thermal hyperspectral imaging camera, which we developed. And we're still working on this. So I presented some results for some inversion algorithm, so some software to basically retrieve SO2 gas, another pollute chemical substances in the atmosphere and retrieve quantities. So how much gas is in the atmosphere? That was that your poster? That's my poster. So we presented some of these results. And but for example, other topics that will be covered are impact craters. For example, Pete Moghini's Mark presented on Monday morning, he gave a talk and he explained some impact craters on Mars, some very some in geological terms that these are craters that are fairly recent on Mars. So he was looking at the deposits and all that. And then we and then we have some also some old friends who joined us from Europe. So there are people who were who were at the Hawaii Institute of Geophysics. But then they moved on to other places such as Los Alamos National Laboratory here in the US or the European Space Agency. And so it's also a great a great way to talk to people who they're not here anymore. So it's also join old friends and share experiences and results and all that. You talked about finding ways to collaborate. And I'm always interested in that. So you're sitting there in the in the great hall, maybe the great hall of posters and schmoozing with somebody. And then you have an idea. And he says, yeah, that's a great idea. And then you say, why don't we work on it together? Is that what happens? Absolutely. Because usually, for example, I'm going to give you an example. While I was standing presenting my poster, there was this guy from the the State University in New York. And and he came and he was very interested because he had seen before some work by Paul Lucy, who is a professor here at the University of Hawaii. And so he is very interested in these hyperspectral imaging sensors. So what is doing now, the University of New York is trying to build some new sensors. And they are interested in the work we're doing because they would like, they would like to use our, for example, the the software to retrieve gases that I that I and John Porter, who is also a researcher at the HIGP developed. But the interesting thing is that one of the applications of this technology is that we you can use, we can you can use it to detect gases such as we're doing, but you can also use it to detect camouflage targets or identify rocks or other materials from the distances. And that is what they're interested in. So they are interested in a slightly different subject, but the technique that they're trying to develop is very similar. And so this is why we started to talk what the way we're doing it the way they are doing it. And so it's just excellent to share ideas. But you don't hold back. You tell them everything you're doing, they tell you everything they're doing. This is a completely candid conversation. Nobody is being particularly cautious about it. You share. Isn't that what happens? Well, you have to be a little cautious, because especially if the results are not published, of course, because if there is a paper which is published, then you can refer them to the to the paper.  And and for example, what we did on Monday night, we had we had a dinner with all of the people who are currently aware in the past at the University of Hawaii at the School of Ocean and Earth Science and Technology. And so this was an excellent way to meet again, colleagues and former people and former collaborators. But then also AGU organizes also events for the broader community. So yesterday, we had a gathering with all the volcanology, all the all the or the volcanology presence at the Marriott here in downtown in San Francisco. And now and that was also an excellent way, especially in front of, you know, food and some drinks. Well, you need to go to a conference like this, you need to take a break and here at Think Tech, we need to take a break too. So we take a break. We'll be right back with Andrea Gabrieli. We'll be right back. Hi, I'm Stacy Hayashi with a Think Tech Hawaii show, Stacy to the rescue highlighting some of Hawaii's issues. We can catch it at Think Tech Hawaii on Mondays at 11 a.m. Aloha. See you then. I'm Ethan Ellen, host of likeable science here on Think Tech Hawaii. Every Friday afternoon at 2 p.m. You'll have a chance to come and listen and learn from scientists around the world. Scientists who talk about their work in meaningful, easy to understand ways. They'll come to appreciate science as a wonderful way of thinking, way of knowing about the world. You'll learn interesting facts, interesting ideas, you'll be stimulated to think more. Please come join us every Friday afternoon at 2 p.m. here on Think Tech Hawaii for likeable science with me, your host Ethan Allen. You're watching Think Tech Hawaii, exploring the world we live in, recognizing the changes around us and looking into the future of our lives together in these islands. Great content for Hawaii from Think Tech. We're back. We've taken our break. We're back with Andrea Gabrieli, who joins us by Skype from the meeting of the American Geophysical Union in San Francisco, California. And, you know, talking about breaks, Andrea went to a meeting of Google. And we have a photo of that. And, Andrea, perhaps you could explain what was going on in your meeting with Google. Absolutely, James. So this, here we have, we are inside the Google San Francisco headquarters. And so Google was present at the American Geophysical Union meeting with the booth and also some events, some workshops to train the scientists about some products that Google has developed for Earth science data and data processing, particularly from satellites. So here you can see one of these events. We are in one of Google's conference room here in San Francisco. The location is like 20 minutes walk from the most corner center. That's where there is the American Geophysical Union meeting. So it's quite convenient. You can easily get there and you go there. So basically Google was interested in the American Geophysical Union, particularly because of their Earth Engine platform. So the Earth Engine platform is a platform that Google developed for processing of images, and particularly satellite data. So this is an extension of Google Earth, yeah? And it's sort of an extension of Google Earth, but it's much more powerful because you can pay, it's a platform. So basically you can code, you can write your own programs, you can write your own processing tools and algorithms. And for example, you can process Landsat data in a very effective way. So Landsat is a satellite by NASA, which takes images of the Earth. And so you can use these images to monitor a variety of things such as natural hazards or processing which are happening on the Earth. What strikes me is that Google is, I didn't know that Google was into science. I didn't know that Google taught scientists. I didn't know that Google followed the Geophysical Union meeting and that it wanted to be part of the whole scientific advance in this area. Does that surprise you? Well, this is what really Google is about because Google is, they have products for the people, for the public, but it's really a research organization, it's a private company, it's a research organization. And one of the Google people who was there to meet the scientists at the American Geophysical Union was telling me that the AGU is their favorite part of the year because they can basically, they develop these tools for the science, for the scientific community. But in this time of the year is great for them because they can actually talk to the scientists to get feedback about their product. So how, is our product useful to you? What kind of changes you would like to see in the program and things like that? So it's absolutely, it's absolutely amazing, these kinds of, as I said, the kind of collaborations that start in this kind of meetings, and particularly this American Geophysical Union meeting. Well, let's go to the next photograph. I'm really getting excited about the depth and breadth of this meeting. It goes everywhere. What's this now? This looks like another hall. Oh, no, the next, this picture is basically the Moscone Center here in San Francisco. This is the location of the conference. So I took this picture just to show how it looks like. And you can see, and actually the interesting thing is that I took these pictures around 8 p.m. I was leaving, I was going for dinner with some colleagues and friends. But what's interesting in that is that you can see there, even 8 p.m., there are still people going in and out of the location of the conference because, I mean, as I said, these are really, really full, full days. As I said, they start 8 a.m. in the morning and they just continue with meeting dinners and even at night. That's great. We can learn from them in conferences here to take advantage of the fact that people are together and that there's possibilities of collaboration and to squeeze that lemon for everything you can get out of it. And it's amazing because, as I said, there are more than 110 countries that are represented here. So it's particularly, I mean, as I said, the extent of this conference is just great. Yeah. Okay, we've got one more photo. Let's look at that. The last picture is, since we were mentioning the importance of the fact that not only universities are present, but also external exhibitors, such as, as I said, Google and NASA, but even companies that actually build sensors. So sensors that scientists might use. So here we're looking at the exhibit hall. So that's basically the place where all the external exhibitors were present. And also, since this conference is also well attended by students, even undergraduate students, who come and because they're interested in science and would like to learn more about graduate programs at universities. So what's the, there's a reference in this photo to the 2019 AGU fall meeting. What is that? Does it happen every, what, three years or two years or what? No, no, no, no, this, that's just a sign that it's changing over time. Basically was telling that the locations of the next AGU for, for, for, for next year. It happens and that's a good question. So yeah, it happens every year, every year, and usually the first meet, usually it's held here in San Francisco, but there's going to be some renovations on of the most corner center. So basically next year 2017 is going to be in Louisiana, in New Orleans. Are you going? Probably I will be going, yes. And, and, and two thousand, and then 2018 will be Washington DC, so it will be in the capital, and then 2019 it will be back in San Francisco. So that sign is basically saying that in 2019 it will be back in San Francisco. One other thing about the industry there and the exhibit hall that you, that you were talking about, is this an opportunity for suppliers, maybe sensor manufacturers, what have you, to make deals with universities, with researchers? Is it an opportunity for you to make deals with them, either to help them develop their equipment or to buy their equipment for your work? Absolutely, that's exactly what the exhibit, the external exhibit hall is all about. So the, the, the, the agencies such as NASA and Google are interested in sharing their plans so that scientists can engage with them in projects. But companies such as, for example, Fleur, who develops infrared sensors, is there to try and make deals with universities and scientists to try and sell their products to people who might be interested in, for some research. And also, and also universities are there to try and make deals with, with, with these companies because they can tell them, the researchers can tell them face to face in person with, with really direct conversation, what they need, what they're interested in, and, and, and so, and so that's excellent for, for, for, for everybody. Now one other thing, and I wanted to ask you before we, we conclude, and that is what, what caught your attention in this, what has caught your attention in this conference, Andrea? What have you learned? Who have you met that leaves a lasting impression for you? Well, my research at the Hawaii Institute of Geophysics and Planetology is mostly about developing sensors for remote sensing and monitoring gases and are, and aerosols in the atmosphere. So I was particularly intrigued and amazed by the fact that a very important professor such as Terry Gerlach came to my poster, for example, and he had very good comments for the work that my, that this group which is led by Robert Wright is, is, is carrying out. So he was particularly interested in these inversion algorithms that, that we are developing because one of the main things is that these inversion algorithms are based on differences between the temperature brightness or between radians that we can measure, but the approach we are, we are introducing is basically having a single point measurements which, which can really tell the concentration of the gases. So people were very interested about this work and, and, and also something that I learned, the, the, the most, the, well I attended this, this Google workshop. So this tool that they developed for processing satellite data is, is particularly, is, is great. And that's, and that's exactly what, what we will eventually be doing because the, the sensors we're developing, now we are just testing them here on the ground on detecting gases, but eventually the goal will be to develop a space platform with these, with these satellites. So once we will do that in the future then the key would be looking down from space and then we might be, end up using these tools that Google is developing. So that's great, great. That was absolutely, absolutely great.   That really makes it worthwhile. It sounds like it's been very productive for you and I, I must say I'm, I'm very impressed with the fact that 20 people have, have, have joined you at the conference this year. And I, I think Hawaii and HIGP and SOEST, they are leaders in this area and they play a role at conferences like this. Thank you so much. Andrea Gabrielli, graduate student at Hawaii Institute of Geophysics and Planetology in the School of Ocean and Earth Science and Technology at the University reporting live from the American Geophysical Union meeting in San Francisco. Thank you so much, Andrea. My pleasure Jay, my pleasure. See you when you're back.


good morning guys happy saturday it is a great day because it's saturday i just wanted to tell you the weather because the weather here has been so nice right now i'm in like the winter garden area but overall it's like this over central florida but it's 70 degrees out oh my gosh i can't even i'm listening to my podcast obviously imposter syndrome are you worthy of the life you dream about and obviously it's by tori de simon love her i am at cycle bar like normal gonna take ethans class at the 915 this location is just so much closer it's only like 24 minutes it's under half an hour to get here so it's just amazing before this video starts it's just gonna be like a typical like weekend vlog vibes just pretty casual but i did want to address like what i'm going to be doing like while i'm in school for money and it's basically just going to be youtube and instagram i do make a little like some pennies on instagram it's not a lot so don't get your mind twisted um but i'm gonna be doing social media so i want to thank you guys so much for clicking on this video it really really helps me out it'll help me pay for my health insurance that i'm gonna be paying for pretty soon so thank you for being here and thank you for your time means the world to me literally and i also obviously have savings and stuff but yeah i just wanted to like tell you guys so fully transparent all the links in the description box if i do put links down there if you click on them i do get a kickback from that if you purchase anything so again thank you so much if you want to check out anything in the description box that also helps me out as well kind of just wanted to be fully transparent with you and you know i guess i'm going to act like this is my full-time job because it's gonna be my full-time job for a bit anyway i'm gonna get ready to go in to class now i am really excited because i'm going to be trying this really fun um starbucks drink it's very fall vibes and i got it from tara henderson so so it is a grand day well i'll tell you later because i'm gonna go in now this is the drink i don't know if you guys can see that but i'm gonna try that one today and then maybe next week i will try my cousin's girlfriend's drink that she wanted me to try because it's also a chai tea and you guys know i love chai also i'm gonna go to public's later because i obviously can't be going to starbucks because that shit is expensive and i just can't be doing that so what i'm going to do so what i'm gonna do is like make my own starbucks drink so basically starbucks as you know sells like jugs of just like coffee so i'm going to get a jug of their like coffee the big kind i don't i don't know and then i'm just gonna buy my own almond milk and then like i get the vanilla flavored almond milk and then bam like every morning i can just pour the thing pour the milk pour the coffee pour the milk and then we'll be on our merry way at i don't know really early in the morning six a.m so number one i don't have to like make a stop which is good and number two it's a lot cheaper it's a lot cheaper than like going to starbucks i have control of the almond milk so honestly i think it's just a win win win and then maybe like once a week like saturdays or like yeah probably saturday so on saturdays i'll probably treat myself to an actual like starbucks drink where they make it and it'll be like a more specialized drink not just iced coffee but i think that's what i'm gonna do because that shit is expensive so now i'm gonna get ready to go inside okay so my hair hair looking crazy as we already all know this drink is so expensive okay this is eight dollars i will not be getting this soon but i wanted to try it because it just looks so good so here's the label yeah if you want a screenshot that go ahead but it is just a gondae iced chai tea latte with pumpkin cold foam and a double shot of espresso so it's like a dirty chai pumpkin drink which i'm excited about so i'm gonna try it this better be worth the money it would suck if it was bad okay okay that is really really good if you like chai if you like espresso and if you like pumpkin all three things that i adore yeah this is a really really good drink this is definitely going to be on my favorites list for the fall i haven't really been drinking my fall my typical fall drink um number one because of the cost number two i don't know it's just like i feel like my taste buds have changed so this is definitely a win try this if you get the opportunity to because it's really really good i'm on my way home finally i took a little detour and i went to oldie i got the coffee they don't sell pepsi products which i find to be extremely interesting because they were all out of publics and valvary loves her die pepsi kind of like i like the coffee so unfortunately she didn't get it but she can check tomorrow i'm gonna go home shower and eat and i'm gonna try to get a video up today that's a goal if it's not today then it'll be tomorrow i need to get on my upload schedule a lot better i don't know what i'm gonna do really i don't know if i'm gonna keep it to like the two videos or three videos i'm gonna probably try to do three a week um but i don't know again don't hold me to that because i want it to still be good like i don't want to feel like i'm just gonna post just to post i don't know but i got the ice coffee i'm really happy um oldie was actually like really nice like it looks new and i don't know it was easy to find the coffee so i'm excited to try that i'll probably end up trying it tomorrow rather than today because like i already had like espresso and stuff i don't really need another coffee today um so i'll probably end up trying it tomorrow morning which will be fun and using like the almond milk that i bought the vanilla flavored so i'll show you guys i'm gonna get back to the house and i'll do a little haul okay so i'm gonna do the little haul this is the only thing i got at oldie because they had it in stock and it's the starbucks iced coffee medium roast unsweetened smooth and balanced so i'm just gonna get like these to like put in the reusable cups and then this is the almond breeze almond milk it's gonna be like the coffee so i can like save some money this is like this costs how much the drink costs like the 16 fluid ounce this is like five six bucks for 48 fluid ounces next up i got some lettuce because i needed some stuff to eat for lunch tomatoes green peppers and cucumbers and then i got toastitos it was buy one get one free so i had to get these because i don't know if you guys get on kicks like i do but like when i am on a kick on something like i need to eat it eat it eat it until i get sick of it it was good that these were on sorry well valor's going to the store tomorrow when i'm on a kick of something i just need to eat to eat it and it was good that toastitos were on sale because i want a toastito kick right now so that's what i got at the store all right guys so i'm finally helping sherry just took a little bit but we are this is stuff for my room why is this a living room alex's dance silhouettes my fish pillow what's this i don't know all right guys so i'm gonna go through this box this is in our storage unit um we close it now so there's like not exist but i'm gonna go through this if i find anything interesting or stuff that i want to throw away but like want to keep a memory of i will just vlog it so it'll be in this video this is always fun because this is like my dance notebook so it just has like notes and stuff which is kind of funny dan don don costumes i don't know but there's just a bunch of like random things okay i do want to vlog this because this is a wrap that we made for i don't know having good technique or something but we practiced this in the car on the way to dance and it was really fun okay so we made a lot of progress i will show you in just a minute but first i want to unbox my lamp and i will link this down below it's from amazon it was like 60 bucks super cute will match my room really really well also guys sorry about the lighting and stuff but i still haven't showered because we have just been like on the grind this entire day we have not stopped but we've come a long way haven't we sherry my camera battery always loves to die during timelapses so i just want to show you guys my lamp i thought it was going to be a little bit brighter but at least it works it works for now and it's really going to be in this corner but obviously there's boxes so that's not going to be happening i need to well this is both garbage but i need to do that little unbagging it's for phabletics a little working with them and yeah so basically it cleared out all the bags when i get a dresser again i'm gonna deal with that but we made progress up here with all the stuff like keepsake memorabilia up there so i have all of that stuff and then i still have a little bit more room for some storage things that i just want to keep up there and yeah coming along coming along in the room i'm very grateful and i love how it's turning out so far i'll show you guys the downstairs now okay and this is the downstairs we've cleared out all the boxes over there and got this little cabinet looking semi normal um we do have to have some teapots on the bottom there but overall we are looking good our kitchen is looking good we've been done with the kitchen for a while we just need to like put some stuff away this is donation this is stuff for over here so we have to get that nailed into the wall and then we can complete like empty these boxes how you feeling sherry she's exhausted yeah my back is pretty rough right now good morning it is sunday decided to put on the robe but i've been waiting to make this coffee since the time i've like discovered it sherry sipping on her hot coffee now i've just discovered i don't like hot coffee it'll probably be like 40 degrees and i'll probably still drink ice coffee i don't know maybe i'll get a warm drink if i'm just too cold but it's just always so hot that like i don't know when it's cool enough to drink and then i always burn my lips burn my tongue i don't know i've just come to the inclusion that i just don't drink hot coffee maybe hot chocolate but that's at home so i'm gonna use this cup and this straw i don't really want the lid so it's just gonna be like this and i'm not gonna make it like i don't want like this much coffee like it's gonna be like a grande and it's gonna be like huge so what if i can take this thing off one eternity later it's now what i wanted it to be a plain cup so i can see how my drink is looking this kitchen is just so more aesthetic to look at like when i'm making things even though it's messy over there but you see you can't see the mess over there because i'm feeling like this and just like cuts it out okay i know i'm getting sidetracked so first things first got the ice got the fixings and now okay doesn't like coffee so i'm gonna like put it to there okay well i guess i am making the full cup because like that wasn't very good judgment on my part i'm gonna shake this because i don't want it to look you know expired okay okay the moment of truth let's try it it tastes like my drink like i'm not gonna lie i think i put a little too much almond milk a plus now i understand why these were all sold out at public's because if you make yourself like this much it kind of goes fast but it's fine i'm not planning on um giving myself so much ice and like products i just wanted to try it today and see if it was actually worth it and it is an a plus so if you guys want to make your own at home like these two ingredients work out really well okay also too i want to unpack this because i'm gonna try to shoot this today i'm not sure but there's my new phabletics i'm so excited ooh these are so cool i love shorts too these are them i like it because it's like snake pattern but like it's like discreet let me see like look at that are they cute oh right isn't that cool yes these are my favorite phabletics bras okay this hands down is one of my favorites because i love these bras i have the plain black version that's this design and it's like such good support and everything a plus a plus and now i'm gonna get started editing my vlog to like post it today because i didn't edit yesterday because we were working on the cabinet over here as you guys know so i'm gonna do that and sip on my coffee i got to sleep in today thank you sherry and hopefully today we'll have a good productive relaxing day okay so we are on our way to dinner we're going to the town traveling tonight kind of a little nice family dinner look at sherry back there okay so i got a little Caesar salad my fries should be out soon he's just going to get it i think i don't know but Valerie got her usual little lobster tail looking great over there and then sherry got stuff shrimp so it's a beautiful evening downtown it's perfect weather too okay so that is going to be it for this video i hope you guys enjoyed this little weekend vlog i plan on vlogging tomorrow the first day of school i don't know how it's gonna turn out but i'm gonna try my best and we'll see so anyway if you guys enjoyed this make sure give it a thumbs up don't forget to subscribe and i'll see you guys in my next video bye


Today, we will learn how we can use generative adversarial networks, GANs, to produce much more convincing examples when it comes to images. We will talk about ways in which we fall short of producing good probability distributions. We will talk about specialized settings in which GANs are particularly useful, and the many ways that are needed to get GANs to actually work and why that is generally difficult. So let's first talk about the history of the field. It has improved so dramatically. In 2014, the state-of-the-art was simple, grayscale images like this, and that was hard. That was state-of-the-art. And over time, we get to really, really realistic images like these. It's truly impressive to just see that. I should also mention here. This is a great person to follow for you, Ian Goodfellow, who's in Montreal and has been driving the progress of GANs for a very long period of time, and he's a big inspiration for me. Let's also talk a little bit about GANs in the news. Now, like, I just want to get across how important they are. Now, MIT Technology Review did a feature about the GAN father, which is Ian Goodfellow, and they did a nice piece on him. We talked, like, even in the New York Times, you see, Internet companies prepare to fight the deep-fake future. So it's just something that's important in the news, and you may have seen the videos where people put rather funny words into the mouth of our former president. So how do we know how good GANs are? Well, Photoshop now has new GAN filters that allow you to do things like change the facial expressions on someone. And not only that, but Adobe also now provides a tool to do the opposite, to actually prove to the world that you actually took a photograph instead of just taking that photograph. Isn't it funny how in the past, no one would have said you'd need to prove that the photograph is real? If it was obviously real, you would have to prove that you drew something by hand. Now everything has changed. Fake tax is being used for customer reviews. We have Snapchat filters that use GANs, countless more applications. In fact, the promise of GANs being too convincing has gotten so big that deep-fake detection was a challenge on Kaggle with the price money of $1 million. So it's literally the million-dollar question how to detect that something's fake. Now let's briefly put this into a broader context. Now, like, they are discriminative models. This is standard machine learning, standard deep learning. We put in features, maybe an image, and out comes a class. We have dogs on one side and cats on the other side. And we use features to classify that in a way we're interested in the probability distribution, which is the probability of the class given the features that we have. Now there's the other possibility of generative models where we could say, well, I give you some noise here and I give you a class and I ask you to produce the features.  In that case, we are rather interested in the opposite, the probability of the image given the fact that we will tell our systems that this should be a cat. Now, and there's lots of different cats, and ideally a generative model should produce every image that is possible with the corresponding probability, which we sketched here by a Gaussian. Obviously, cats do not fall into neat, simple Gaussian distribution, but the distributions that we have in the world are very complicated. Now, what is the idea of GANs? The idea is we have one generator that draws images. Look, here's a nice image. And the generator will try to produce images that look like the real images. Then that image is shown to the discriminator and the discriminator might say, that's so fake. I don't believe this. This isn't the real image. Now, there's something subtle hidden here, which is the generator might want to produce images, but that's not enough if the generator would always produce the same image. The discriminator could still figure out that that image must be fake, because the discriminator seen so many of those. So it's a really interesting game where the generator shouldn't just produce an image, which is part of it, but it should also produce a distribution of images that matches reality here. Now, let's talk about how it works. So we have a generator. The generator constructs an image. The reward function in a way is to not get caught. The reward function of the generator is that the discriminator cannot distinguish it from the real image. And again, setting the output of the generator is an image, a fake image, that fake image is then handed to the discriminator along with a set of real images, and then the discriminator asks, is this a real image? Now the discriminator's job looks like this. You have a generator handing out a fake image, discriminator gets a fake image and a real image, and so it sees a mix of those, and for every one of them, it has to say, is this real or is this fake? And the reward for the discriminator is not getting caught. Now here's what the model is to be more specific here. The generator G takes as input a vector z. That gives it randomness, and the reason why that's necessary is because there's a real distribution here. And now the discriminator has to tell the difference between fake images here and real images. Now, you can say, at first, if we have a really bad generator, this should be easy. Now, a real image looks very different from, say, white noise. And then through training, the generator draws progressively better images, and then it will be harder. And it forces, in a way, the generator to produce progressively better moralistic images, and the discriminator is to get better and better at figuring out the many ways how a real image might be different to a fake image. And that is, in a way, the crux here, that there are lots of different real images, and that, in a way, a good generative model would understand this manifold of images that is there. Now, what's the discriminator loss function? The loss function for the discriminator is, here we have 1 over m. This is just because we want an average. The log of what the discriminator says for those stimuli that are real. So here, yi, if it's real as 1, so we have this sum that takes the log probability for the samples that are actually real. And then it takes, we have the second sum here, like 1 minus yi is 1 if it's fake, that's 0 otherwise. So this thing here is effectively the sum for the fake ones of log 1 minus d. So basically it means we want to have high probability for the real images and low probability for the fake images. Now, let us build a discriminator. We start with the discriminator, and give it a couple of animal faces, hooray week 3, and some random images. And let's train it so it can distinguish the two. And we will use just a very simple multi-layer perception, and somehow this should be possible. Not like white noise images look very dissimilar to real images.


Hi, I'm Alan Footman. I'm a sports tour operator from Cape Town. My family and I have been living in the southern suburbs for 21 years. What we love about the neighbourhood is it's very family orientated. Lots of things for the kids to do, especially here where we are next to the farm, where folk can walk the dog, go for runs and enjoy the fresh air. In the southern suburbs we're lucky enough to have some of the top schools in the country because after that we have the University of Caton, one of the most famous universities in the world. Newlands is a great suburb. All the sporting amenities, Newlands, rugby ground, cricket ground, etc. Down the road to Claremont, lots of shopping centres for the kids and for the mothers to do their shopping. Fantastic pubs and restaurants around like Forries, Springbok Bar. Bishop's Court is full of beautiful upmarket homes. Kirstenbosch Gardens, National Botanical Gardens right next door. What attracted us to Constantia is the large open spaces. I've always wanted to be a farmer and now I'm living next to Pro Constantia Wine Estate, the oldest wine farm in the country where you have fantastic wines, great restaurants, got the best of both worlds. My family and I have loved every moment of living in Constantia. We couldn't be happier and this is our neighbourhood.


Well, after a great regular season, the BHS baseball team earned the top season section 8 3a that kick us off tomorrow evening at BSU expectations. High for the Jacks that compiled a 16 and 4 record in the first part of their season, but now the slate is wiped clean for the playoffs and the journey to get to the state tournament begins. That search tomorrow in their postseason opener, hosting a Detroit Lakes team. They beat twice just a week ago, outscoring them 32 to 6. As long as the Jacks keep winning, they will keep having home field advantage until a possible sectional championship again. If you've enjoyed this segment of Lakeland news, please consider making a tax deductible contribution to Lakeland Public Television.


What's up everybody once again, it's Brandon man Sean and today we're going to talk about some shady music industry Practices because artists need to be aware of this stuff and what inspired this video was actually when YB in the mirror Basically set it on Instagram that a label tried to eff him out of his hit single rubbing off the paint because his manager Actually sold the beat of the song to the label the label bought that and they basically tried to strong hold him into Signing a deal with them just because they like hey, we got the rights We own the song technically cuz we own the beat and if you don't come with us Then we're gonna try to put it a stop to it But I've already touched on some of these topics in some of my videos So I wanted to get the homie sir love just to get his perspective on All of these shady practices and inform you guys on a lot of things that that are very real to happen Let's hop into it. Yeah I think it's definitely important for artists to keep their paperwork together a lot of things that artists don't understand in Today's they don't understand the value of what they have and what it can turn into long term You know, you have the long-term check You got the short-term check and the short-term check is always going to be appealing Exactly getting right understand that people in the business is making money So if anyone's ever going to offer you a price for something best be rest assured that they're going to flip it for something That's higher. So if you don't know your value, it's just a jug You know someone come up to you and they got something they're trying to sell it to you for five But you know it's worth five hundred Five sell it for five hundred when really they probably could have sold it to you for three hundred And you still would have bought it and it would have been a more of a fair trade for both parties involved The tricky thing about this scenario is that the the label was or you know The parties involved that had control over the record was then kind of holding the scenario For ransom because at that time period they wanted to do future business with a particular Artist and because they want to do future business with a particular artist They were able to hold the record over his head and say yeah, but we own all of your assets We own everything that makes you hot right now Yeah, unless he goes out and creates other records that are popping or just as hot Which means that he has some type of system or some type of strong fan base where he can replicate the success of that first record Then he's really in a position of weakness in the negotiation Exactly and I mean so one thing That's it could sound kind of scary and crazy to a lot of you guys, but so basically you have a song Let's just say this situation if they might not be buying to beat, but there's a lot of other scenarios where Hey, you might be talking to somebody and they say hey, let's let's let's get this deal going you talk to the label Nothing you say know what now we're not good on that deal. We don't want to sign with you guys And then at that point some people might come up back and say Well, if you don't want to sign how about this because we got this on you We got this on you. We got this on you. We done trademark your name. We got all kind of things where Matter of fact, how well what are some scenarios that you know about specifically? Scenarios that I've seen I can't speak on any one situation Okay, what I can do is say the trademark name thing is definitely real Pretty much it's not hard ball that labels are not out here to get you You know, that's kind of the thought process But all of them are not evil, but you do have different people that have their own incentives A lot of times the person that's going to take advantage of you is the person that's trying to close the deal with the label So a lot of times you go to a particular label and that a and r that works at that label has his own label And he wants to sign you under his label before signing you to the major scenario and in those situations is where The situation can get desperate cassette a and r is already kind of hyped you to the building or he's already kind of presented The project or he's been tasked with bringing the project in he's on a sharp He or she is on a sharp deadline and so they might apply pressure to you and you know, it could be the label No, give me wrong labels labels can fucking right but you know a situation that I've seen is you know You're doing a negotiation with a particular particular company. You're trying to Figure out the best way to bring your project into their building for whatever reason you're not with it And so they turn around and they can do things to take control of the scenario They can trademark your name like you mentioned before you buy an own ownership of your name So that you can no longer use your name unless you come through them You can no longer sign using that name and go anywhere else and anywhere that name is represented They can make you take it down. So if you have mergers, you have something out there things of that nature they can also Go in and buy out your contract if you sign to your manager Like it's not a manager agreement and it's actually a label agreement that you're signed to they can buy Out your contract to your manager and still own rights to you If you've given over your legal rights to your manager or to your production company to anybody like the right to sign for you Then they can buy that person out and that person can sign and put you in a crazier situation Slow that down and break that down because you got a little fast I want to make sure they caught and understand what you're talking about because I know what you're talking about Okay, so you can it's common practice as artists you to give the right To sign for you over to someone else because say you're performing in another country And you have a check that's waiting for you right now in Atlanta You need that check to do whatever you're doing in said country because you're running out of cash And you're not there and the bank is not going to clear those funds unless there's a signature on it So you've given another person the authority granted them the right to sign on your behalf that individual then can sign that check And then clear your funds to allow you to continue doing what you're doing in said country It can get real tricky if that individual signs and commits you to something that you didn't want to commit to Which a lot of times can happen if you don't have to trust normally the people that have those rights or your attorney or your men Or your manager will have those type of Rights and I forgot what it's called The name slips me at this exact moment, but it's it's in a lot of contracts. Yeah It's pretty standard practice, but that can go twist it at any given time You can also see the crazier things like they can Trademark the the logo or the album cover or the artwork or things of that nature So you can't even post the artwork on your streaming platform. You can't make any money off the merch Yeah, you can't you can't do any of that. Um, they can Go back in and it can do all sorts of things. They can go down to the split sheet level It can go down to the record registration level It can go down to dirty ball where they're black balling your record on radio Yeah, it can go I mean there's so many different ways the game can be played to kind of force you to comply if They had, you know negative and malice intentions to you know to acquire you but That's not gonna be the usual practice like they may do one or two things But you're not gonna see a full boatload of bull ish coming your way because Then you're not gonna sign right no one no one wants they don't want to sign you if you bullied and they've like enslaved you They want to sign you and you feel like you're happy most scenarios when the artist gets screwed The artist has no idea they getting screwed, which is the best scenario because the artist is happy They perform their best work and they don't know they're losing the best scenario for the record The best scenario for the record level the best scenario for the artist is just to do your freaking paperwork You know make sure you split sheets are on point make sure you're you've done all your publishing paperwork your PROs Make sure you're registered. Make sure that you've registered your trademark make sure you register your name trademark your name All yours like the paperwork the stuff that people don't want to do that's the stuff that makes you money That's your check right so with that being said I want to just go ahead and get your opinion because I always talk about this from my standpoint But when do you decide that it's actually worth going ahead and doing that paperwork because you got some artists They go through these phases right they say hey, I got this name two years later. They have another name They still haven't blown up when do you decide when it comes to an artist that we need to go ahead and do all of our due diligence Well, if you have it depends so if you're in a scenario some companies have money some companies don't so it depends on for you guys It depends on Where you are financially if you have any type of bread then all this stuff should be done day one out the game if You don't have bread and you're probably Trying to hustle up bread and you're moving money around and you may not get to some of these things you may be trying to decide between the trademark and In marketing your project and you may be looking at a $1,500 tab and you're looking at well shit You know, I got to get this record out in those scenarios You're gambling your game and I've gambled so, you know, I get it, you know Sometimes you got a game. We got a royal dice. You got throw it at the records Just make sure you've done the back end at minimum if you lose your name You can change it like, you know, soldier boy. Look how he spells his name for example, perfect example bow Wow didn't own his name So he had to go from low bow. Wow to just bow. Wow, right? You can survive with you know, not paying for a trade market things of that nature But you can't survive when you lose ownership to your track when you lose rights to your record when you when you lose Things that are are so valuable that you can't get them back. Perfect. Those primary assets. So go ahead and in your opinion If you list obviously everybody knows music right the song What are the next few things that you would personally try to actually go ahead and say? Hey, I need to lock these down if I got the money for it. If I had the money things that I would do I make sure that I'm not sure how the artist is doing it But I would open up a company as artists go ahead and get and you get the EIN Yeah, get the company name all that stuff LLC or INC depending on if you got partnerships And how that structure and taxes and that gives real complicated depending on what route you want to go But either way you're gonna go LLC or you're gonna go EIN You want to make sure you're trademarking all your different names You want to make sure you're trademarking all of the different artwork and things that you're doing throughout You want to copyright everything that you're doing you also and I say everything I'm talking about even the text on the website You want to copy that you want to copyright? All of your records you want to make sure you register all of your records with the PRO You want to make sure you have split sheets on all your records and make sure all those records are signed You also want to make sure that you've done all of your Back-end publishing and things in that nature documents associated with that you probably want to sign with the publisher or a co-publisher or a Sub-publisher or yeah, I do all those pick make a choice in that area.  Okay? Yeah, I got my track. I own my track Two other things where you would say these are the next two things We know it's a full list of things you on your track The very next thing you need to do is do your split sheets. That is very important You want split sheets is probably the most all the money starts with the split sheet I have your split sheets. I have it signed by everyone that's involved I'd have my IPI numbers on that have all the proper information on the split sheets done the right way And then at minimum I would register those records with the PRO and copyright them like You know split sheets copyright and PRO or something that goes together at minimum. I do those things, right? Okay, perfect, and I'll go ahead and cut the video off right there We did float into some other topics that I think are important and I'll put the videos up But I didn't want that in the same video So if you liked this video go ahead and hit that like button and if you like it You might as well share it other than that, you know what to do hit that subscribe button