So I'll tell my uncle that's locked up down there. Man, uncle, I got a song in school with you. I'm trying to get this song clear. He said, well, he signed to my law on me on Top Dog. He called Top Dog on the phone. I'm on the phone with my uncle in Top Dog. Hey, you know who this son is? It's this evil Al son. What? Oh yeah, you need the song cleared?   I'm going to stretch the breath. Yeah, we on boss talk one-on-one, one-on-one. Yeah, we going to talk. So he connected me with Jeter, who's next to Ross. So I already had the relationship. So he connected you with Jeter. I had a song with Schoolboy Q, with Kendrick Neymar. So the Schoolboy Q's from my hood, right? Fado's Hoover, but he's signed to Top Dog, which is from Bounty Hood. Niggas in Guards, right? He signed to Top Dog. So I had a song with Schoolboy Q. Schoolboy Q from my hood, I couldn't get the song cleared. So I talked to my uncle that's locked up. I don't know if they're from there. I mean, I got a song with Schoolboy Q. I'm trying to get this song cleared. He said, what? He signed to my law on me on Top Dog. He called Top Dog on the phone. I'm on the phone with my uncle in Top Dog. Hey, you know who this son is? It's this evil Al son. What? Oh yeah, you need the song cleared?   I'm going to stretch the breath. I did the song play like. He's out from the grave. He's speaking from the grave right now. I swear to God. He's speaking from the grave right now. I did the song play like a year. I couldn't get the song cleared. I couldn't get in touch with Top Dog. They two way up there. I'm like, man, I'm trying to get this over the top. So my uncle like, why you didn't tell me? I said, man, I swear to the next day, my song got cleared. Shout out to Bolo, man, from Bostalk 101 for calling them shots, nigga. Yeah, yeah, yeah.   He's the person that I look up to because he come from my community.   So I was signed to a label called Legacy Records during the time. So I already had the connection with Ross. All I need them to do is like, hey, man, listen, I got a situation with Ross. I said, just put up this money for this and we're going to shoot the video. I'm going to his house.  We're going to the promise man. We're about to shoot it to there.  Yeah. Oh yeah, I had the relationship.  No, you did. You know what I'm saying? You know what I'm saying?  Yeah, so I had. So when you get to Ross house, what is it like?  Now, have you seen the movie? Have you all seen the movie? Willy Wonka and the Chocolate Factory? Yeah. Every day. This thing got like a hundred room. I swear to God, yeah.  Like, I'm like, God damn. You know what I'm saying? It was like, it was like that, bro. I swear to God, I was like, I was trapped in Willy Wonka and the Chocolate Factory, bro.   Yo, this thing had a room with every old video game there ever is. And he probably had been in the room, some of the rooms. He can't be gone in all the rooms, man. He always had old video games, not the new ones. The old ones. The old ones. The old ones, collector's items. That's good. Yes, every old one. That's hard. Every, bro, every one, bro. I heard he got a lot of art in there too. I talked to a guy. Bro, he had like a hundred and some rooms, bro. I don't, I didn't get to look at the art, nigga. It was too, it was too hard. It's like, bro, like, bro, like seriously, bro. And then I'm like, then, you know, it's just like, yeah, the bowling alley in there. I'm getting dressed in the house. I'm like, I'm just like, nigga, it's so much. But I looked at the video, which of course it ain't came out yet. But I looked at the video, dope video. I can't wait till it come out. But it looked like the girls was there.   How do you think, like, did he just tell you that we want to set up right here and do it on? Who picked, where y'all said it on? Jeter. Jeter in that whole act, like he already been there before. We gonna go right here, and we gonna be in here, and we want to do it right here. It really take a nigga to act like he know what he doing. You really don't know what you're doing. I'm walking in the house saying I want to set up right here. This is gonna be perfect. It might not be perfect to you.  And bring the girls right here. I think I'm gonna say that nigga's y'all. Yeah, man. It's all about your heart, man. It is.


With the Taxonomy Research and Information Network, which deals with organisms or something, I'm not, it's obviously not my area, so I'm not quite sure. But he's here to talk to us about lonely data versus link data with a FOSWIKI. So I'll hand it over to Paul. Thank you. There we go. So I was just wondering if I could start with a question. How many in the audience here actually know about linked data, the semantic web? You guys have, okay, and you're sort of using it to bind your data with, make your data reusable and that sort of thing? That's a lot harder. So where I work is for the Plant Biodiversity Research Center in Canberra by CSRO. And I work for something called TRIN, the Taxonomic Research Information Network. And I'll just, this is our team, so I'm not the only guy, of course. There's three of us employed full time. The other guys have day jobs, unfortunately. So we're like the geeks within TRIN. The other guys do real science. Well, I should say that we're just sort of trying to develop IT systems to help support science, make science more usable, because there's quite a lot of research done. And the focus for the scientist is, as you would have heard Adam and others say before, the focus is on getting a paper out, getting citations, and that is the concern of the scientist. Sadly, a lot of really useful data that could be highly valuable later on, it doesn't go into the paper, and that's often a bit unfortunate. So especially with taxonomy, there's a real shortage of taxonomists, and these are sort of biodiversity researchers who are focused on the classification, on the evolution of organisms. And this is very useful, like if you're trying to grind up sea sponges to find new cancer cures and things, it's useful to know how organisms are related to each other in terms of their evolution. And so with there being very few taxonomists, we need to make sure they don't waste their time. And so TRIN embarked on this project to accelerate biodiversity research and try and make all the data as seamless and reusable as possible. So at Hubris, this means that we have to use open source software because taxonomists, many of them, not being a very lucrative field of research, there's not a whole lot of funding apart from the taxonomist position usually. So we have to make sure the software that we use and recommend and also develop has to be free and open source. We also have to use existing open standards, and that's a bit more difficult than it sounds because there's just simply so many of them. And when somebody is faced with the task of trying to take a data set and make it reusable in a linked data fashion, it's just simply overwhelming, trying to pick RDF ontologies and vocabularies and to really come up with your own data model that will make sense to someone else. And as Adam said, CSV is usually the best because it doesn't carry any of this model baggage with it. So you've just got columns and headings. That can be a problem. We have all of these systems and activities going on. Everyone's collecting data in all of these formats, CSV access, everyone knows the problem. So a lot of time is wasted transcribing stuff from one platform to the next, one part of the workflow to the next. Our focus has actually been to use FOSWiki, which is a collaboration platform. It's a little bit more than a wiki. It's more of an application development environment in a sense. So we've got that version control access controls. That's why we chose FOSWiki. So we've got data capture in the field on PDAs, data capture from laboratories, especially with genetic work. There's a lot of data generated there. The big problem comes when you get to the end of a workflow and you've got a data set and you need to annotate it and mark it up for use. It might even be for publication or field guide. And so you've got this list of hundreds or thousands of types of species names with various attributes that you've generated. The very first problem we come up against is that the idea of the evolution of plants and animals is changing. So for instance, I had one person working on something and it was the first 10 hits out, just the first 10 records of their data set. And in the first five minutes, I'd found out that this species and genus name here had actually changed completely. It was no longer in the same family or order, also we called it. In fact, apart from a few ranks down from Plantae, it had basically completely changed its position in the taxonomy. So it's very important when scientists say, oh, I found an interesting compound in this plant, or this is an interesting gene in this plant, it's very important that they know that they're all researching and talking about the same critter. So apart from identification and classification, the naming is a pretty fuzzy handle to work with. If the name changes, if its classification changes, that changes the name as well. So to try and automate this, we really want to avoid copy-paste madness. So copy-paste madness is where you've gone to the name authority and you've copy-pasted the taxonomy and the name and the authority and all the other attributes about the critter into your own data set. So you're sort of importing this stuff, but you're really just duplicating it. You're making redundant information. So really, we think that the way this is the linked data part, the data should just be the link. If you have a standard identifier authority for the things that you have in your database, and this can be genes like in GenBank or in the case of taxonomy, we have the apnea and AFT, that's the Australian Plant Name Index, the Australian Formal Directory and a few others as well, which are coming online, if you use their persistent HDP URIs, then that is all you need to store in your database. You can cache and pull in all the other properties about the taxonomy and the name and the authority and not have to worry about keeping that in sync. So six months later, if the project takes 12 months, you can go back and query every single taxon and say, has the name change, is this still a current concept? Is this still a currently accepted concept? What is its current classification? And you can update or at least flag for review a lot of things in your database that would otherwise require a human to sit down and manually have a look. Okay, this is a species name, find it in the literature, find it in the database, that wastes a lot of time, and it's something really easy to solve. This is an example snippet, a bit more nuts and bolts side of the semantic web, linked data, this is an XMLRTF fragment. As you can see, it's got a whole bunch of junk in it. I'm just showing the links. So you can think of linked data as actually a graph. It's a massive entity relationship sort of network of things. So this thing is actually the response from a gisterous coniculatum, and it's showing us that it has a name, obviously. It has literature references from where it was mentioned. It also says it's an accepted concept for several names. When we say accepted concept, that's according to the Australian Plant Census. Linked data makes glorious graphs. Well, this is not to scale, it's quite a simplification, but in order to determine the classification of an object, it's a little bit tricky. So the user actually finds this URI. These are research scientists, not ordinary Wikipedia users, so we're allowed to give them a bit of ugly skunk work stuff. So they do actually have to determine the URI of the thing that they know that they are talking about. And once they've put that into the wiki, it goes off and finds each node. It walks the graph and determines and reverse-engineers the classification. So we have these child-tax-on relationships. So this is like, this is the species, that's the genus, that's the family. And so we avoid the copy-paste madness. So being on top of computers and make them do what you want, that actually hasn't happened for me today. So I'm going to have to show you the previous version as of a month ago. I had been working very hard to make this ready for today, but I'm afraid it's not going to be able to show you that. So this is on our live wiki at the moment. This is the taxon that I've picked for this demonstration. So the HDP URI for this taxon has actually been recorded here, and if this was the current version, it would show you the case attributes from the name server. Now because we've expressed this tax on using a standard identifier that hopefully all other researchers will refer to that common ID, it's like a globally unique identifier. If everybody refers to that creator using that globally unique ID, then we can really easily find all other related information to that globally unique identifier. Now the ultimate plan is to experiment with exporting our wiki data into freebase. I don't know if you guys have heard of that, but I don't really have time to talk about it, but it will automatically try to align nodes and find relationships between nodes and automatically discover related information through indirect means as well. So not just direct alignments of nodes, but through indirect links as well. So because I'm using a standard identifier, there are two web services that know and understand the same IDs I do. So all I've done there is we have an ALA info link here and there's another web service that will understand the same globally unique identifier that I've used and because I've done that, the user can very easily find maps and related information pulled from all over the web. So this is like a distribution map for this critter or plant actually. That's a sort of heat map thing going on there. And of course, this is the originating name authority with all the extra boring stuff about the name. And so that's all. Any questions? Yes. Need to need to get a mic up to our questioners because we're recording these talks and we want to be able to hear the questioners asking their questions. I'm interested to find out how the URI is actually constructed so that it's easy to find. Yes, easy to find, very good point. Why don't I go to a taxon that I know won't have the URI associated? So they're very picky actually. They don't want to accidentally just go to the same name that they've randomly found somewhere. They want to use the correct name with the correct author citation to really anchor the concept that they're referring to. So in taxonomy, we refer to taxon concepts. So I'll find one that doesn't, if I wasn't a programmer, the plant names would absorb into my brain a lot easier. Let's try this one. Now, I must admit I've started doing a UI and that's also not ready today to pick the name. There's several different versions of the globe. I say globally unique, but actually, there's two main versions. There's an LSI, can I have a show of hands? Who's heard of LSIDs? One, excellent. That's more than I was expecting. LSIDs are a URIM, if you know what that is. A uniform resource name. And this one has been populated.  It's made a lie of me. Okay, I'll just do it manually. So I'm going to go to this search facility. The wiki has a link. So you get taken here automatically with the name already filled out. And so I can mistype this name actually. We'll see what that comes back with. And they get a list of taxon concepts that exist in the APNI database. So when they're consolidating research facts about a taxon, usually the author of the original research will cite the taxonomy that they used for that critter. So come on, Telstra. All right. Okay, so they basically just copy, paste one of these links on the accepted. So we're just trying to stick to APC accepted concepts at the moment. So if they decide that they want to make a wiki page about this genera, then they can inspect the link. And it's just basically copy pasting. This web service will actually do content negotiation. So if I put this into the wiki, the back end actually does use a library called RDFtri and that's a Pearl library. And it will content negotiate the RDF representation of that same resource. So for example, if I go to RDF on the end here, that's not using HTTP, but just a different URL. So I can get the exact same information in a computer readable format. So you're basically copy pasting links. That's the long-winded, I'm sorry that was so long-winded that answer. Okay. Right, do we have any more questions? Yes. Are there many similarities with this and document object identifiers, the things that nature, for example uses? Yes, DOIs are an excellent success story of URNs. And sadly at the moment, we just haven't had the resources to implement DOI negotiation. We have a very manual copy paste bibliography system at the moment. So yes, they are very similar, especially LSIDs. So an LSID is actually much more similar to a DOI than HTTP or ISO, it's the same concept. More questions? Okay, well if there are no more questions, everybody please thank Paul for his talk. Thank you.


Hi, I'm Jay Schmelzer, the Director of Program Management on the .NET team. In this video, I'm going to provide an overview of .NET 2015 and related updates and Visual Studio 2015 Update 1. First, let's talk about the way we approach our investments in the .NET framework. It really centers around three primary pillars. The first is ensuring that we're providing a .NET application platform that meets the needs of the applications you've been developing and the direction that you need to take those going forward. As well as providing a platform upon which you can build the next application that you're being asked to create. We're also ensuring that we do this in a way that is open, transparent, and collaborative with the application development ecosystem. Finally, I want to ensure that we're creating a platform that not only can be used to build great applications for Windows, but any application deployed to any platform. We talk about .NET 2015, but we're really talking about two framework profiles. The .NET Framework 4.6, or I typically refer to as the full framework. This is the version of the .NET that we've been working with, and you've been building applications on for years. Provides everything you need for building applications from desktop applications through high-scale web services. A little over a year ago, we introduced .NET Core, an optimized framework designed for today's modern application types. Across all of this, we have a set of common investments. Investments in things like the runtime, the compilers, and core library packages that extend the experience and apply to all types of applications. Let's drill into each of those areas, starting with the common layer across all. Let's talk a little bit about the compilers in the runtime. In the runtime, one of the big areas of investments in .NET 4.6 was around the new 64-bit JIT compiler. Provides increased performance of applications, and the opportunity for us to create new and interesting libraries, for example, support for SIMD. In the language space, we invested in a faster compiler, we've invested in creating a set of language features that smooth the overall language usage and programming experience. We don't have big paradigm-shifting features like async or link in this release. Instead, we focused on the things that just make your life easier as a developer. Things like string interpolation or the name of capability. In Visual Studio, we focused a lot on continuing to have the best debugging experience in the world. We used to call it the Cadillac of IDEs. I think now we'd probably refer to that as the Tesla of IDEs, and really expanding that experience so that you can take advantage of modern language capabilities like lambdas and link while working in the debugger. Finally, in the core compiler space, we have the new Roslin compiler, the re-implementation of the C-Sharp and VB.NET compilers, that exposes the intimate details that the compiler has of your application to tool vendors, allowing tool vendors like ourselves with Visual Studio, and the ecosystem to create richer and more immersive experiences for your application developers. A couple of great examples of where this comes into play are around code analysis. We're now able to move beyond just static code analysis and get into semantic understandings of what your application is doing. Providing even richer set of tools for ensuring you're building the best applications you can. For library and framework authors, we have what we refer to as code-aware frameworks. The ability to include a compiler extension with that library that gives an interactive experience for using the library, using the framework in the way it was intended, and flagging uses that may be not as optimal, including the ability to offer fixes to the developer right within the IDE. If we move up a little bit and talk about the application types that sit on top of these runtimes, we see that there's a number of different things we have. First, we have a couple of great desktop UI presentation stacks. Windows Forms is a great UI platform for building Windows desktop applications. It's actually probably one of the most complete platforms we have. It's a great set of experiences across the design time, the runtime, and the third-party ecosystem for supporting great desktop applications. The team is focused on the fundamentals in this stack, really spending our energy on ensuring that we're providing the best performance, work on the most current hardware platforms, and addressing the key bugs that US customers have told us about. WPF is another great desktop presentation technology stack. We continue to invest heavily here in performance as well as modern hardware. So doing investments around high DPI resolutions, improve touch support, and so forth. We also, in Visual Studio 2015, really made a lot of investments around the tooling experience for WPF. In this case, took a lot of the great experiences that we created for Windows Universal projects and the diagnostic tools and made them available for WPF developers as well. We also took technologies and approaches we used in the web design stack and applied them to WPF, doing things like allowing the application and the surface of the application to be used as the designer as the navigation tool for figuring out where these UI elements were coming from. Of course, the Windows Universal platform, or the Universal Windows platform, really allowing us to create a single runtime, a single design API surface that can work across the full family of Windows devices, from small embedded Windows devices to phones, all the way up through large wall-mounted displays, Xboxes, and so forth. As part of this, we've brought to market the .NET native experience. .NET native is a compiler technology that allows us to extend the .NET compiler tool chain. So rather than stopping with the intermediate language, we now hook up the back-end C++ compiler and produce a native binary as a result. This is the same C++ back-end compiler that you would use if you were a C++ developer. So you get the optimizations of a C++ application with the productivity of a C-sharp and .NET developer experience. Of course, it is a heterogeneous world up there, especially in devices, and we want to make sure that .NET developers are able to use those skills to build native iOS and Android applications, taking advantage of their existing C-sharp and .NET skill set. We do this with a great partnership we have with the folks at Xamarin. They enable you to extend those skills to build native iOS and Android applications, while also having the opportunity to do reuse of code across those specific implementations. So it's the best of both worlds. You get 100% access to the platform APIs specific to iOS or Android, but you can share a lot of the common code that exists across all those implementations. And of course, for the web developer, there's ASP.NET 5. This is the new re-envisioning of the ASP.NET web stack to create, designing it for more modular use, designing specifically around new modern cloud workloads, giving you the ability to create a application that consumes only the components of the framework that you actually need, giving you smaller deployment sizes, which result in higher density on the servers you're deploying to. We've dramatically improved the tooling experience to continue to ensure you have the most productive experience when building web applications with Visual Studio and ASP.NET. Now let's talk a little about .NET Core. .NET Core is really there to move .NET beyond Windows. Historically, when you think of .NET, you think about it as a platform for building great Windows applications. With .NET Core, we're breaking that. We're changing the mold there. And we're making .NET be a technology that can be used by any developer building any app on any platform. We're doing it through a few core design principles. Specifically, we've designed a .NET Core to be modular from the beginning. It's all package-based. Rather than thinking about assemblies, you think about packages. You allow Nougat, our package manager, to ensure you have the right packages available and the right dependencies that your application requires. We also designed .NET Core with specific workloads in mind, specifically modern workloads. So things like universal Windows platform, ability to work across devices, as well as the modern ASP.NET web workload. And .NET Core is the implementation of .NET that we've implemented entirely in the open, working in GitHub, and supports cross-platform. So the ability to build an ASP.NET application and deploy it to a Linux environment or build it on a Mac. When we think about .NET open source, it's not just about the source being open. It's about how we go about building the software. It's about how the approach we take to designing the product. We've done a number of things over the last year. We've really started to see increased maturity in the team, in the way they work. So we see everything from the early design ideas around the next version of the C-Sharp language being posted out on GitHub and having conversations with you as the community of developers about the direction we're taking the language. We see every pull request that's made, whether it's from a Microsoft engineer or a non-Microsoft engineer, go through the same open code review process in the public. So everyone is learning from the best practices that we have. The contributions and the reactions we've seen here have been tremendous. We've seen everything from a big portion of the Mac platform abstraction layer for the common language runtime to fixes to error message strings coming from the community and everything in between. We've also seen this way we work have an influence on the way we work with other platforms. Couple weeks back, we saw the first merge request going into Linux kernel that referenced the Microsoft Core CLR project as one of the justifications for making a change to the Linux kernel. That's just a tremendous example of the kinds of new collaborations happening across our industry. To give you more of a feel for it, let's take a look at what the new .NET Core experience looks like for someone trying to develop an application on a Mac. In this demo, we'll take a look at building an ASP.NET 5 application on .NET Core on a Mac. Now I've already gone through the steps to install both ASP.NET 5 and .NET Core. So I have a set of commands that are now available to me as part of this experience. One of them is the .NET version manager. So I can say DNVM list. And what I see are a list of the versions of .NET Core and ASP.NET that I have available on this machine. Here's how you can start seeing that side-by-side support that we now have with the .NET Core implementation. In this case, beta 8 is the active installation on my machine and that's the one that we'll use by default for any commands. To create an application, I can take advantage of the ASP.NET extension to Yeoman and just say yo ASP.NET, which will launch Yeoman and our ASP.NET generators. We'll choose the basic web application, give it a name, call it hello connect. And that will now scaffold out the basic files we need for our ASP.NET application. So let's go change directories to that. We can take a quick look and we see that it's generated the basic set of views, controllers and project files that you would expect for an ASP.NET 5 application. Next thing we need to do is just restore the packages used for this application. In this case, we'll probably grab a lot of them out of the cache. So again, look at the project file and it's done that. The last thing we need to do is we'll just launch this application by typing DNX web. What this is going to do is launch a lightweight cross-platform ASP.NET host we have called Kestrel. Now that is up, we'll switch over to our browser and we'll just go to local host. And here we see our ASP.NET 5 application on .NET Core running locally on my Mac. That was a quick summary of the areas investment in .NET 2015. Hopefully it gave you some insight into the kinds of scenarios we're going after and the things we're thinking about. This is a collaboration. So I encourage you to get connected with us. Work with us on GitHub. Work with us in the code, track the issues, comment on the designs. Follow us on social media via Twitter or just engage reading and commenting on the blog. Whatever mechanism is best for you, get involved, get connected. Thanks a lot for watching.


We're back at GTC 2024 in San Jose. This is theCUBE and Scott Bills is here. He's the Vice President at Dell Professional Services. Scott, thanks for making some time. Yeah, thank you for having me. So you're welcome. I mean, services, we always say, rubber meets the road with services. That's where actually the business value is realized. It reduces risks for customers. But wow, we're talking about a whole new era here, right? And of course services, you go with the flow, right? If the customer says, hey, this is what we want. You guys figure out how to deliver it. You're obviously doing a lot of infrastructure. You've got a big ecosystem, but as I say, we're entering a new era now. So how are you guys, you know, first of all, what do you think of the show? And then let's get into how you guys are accommodating this AI world. Yeah, I love the show. Love the energy. Love the announcement we had with the Dell AI factory, which our services is gonna obviously help support from a Dell standpoint. Really what we're looking to do from a services point of view and how we're thinking about the space is that we want to help customers from day zero to day two plus on their AI transformation journey. So that starts with helping them understand what are the use cases? What's the strategy? How do you assess readiness? How do you prepare the organization for AI? Then how do you think about data readiness, prepare the data, engineer the data, ingest the data, scale that. How do you stand up the infrastructure, the software, the hardware, deploy the models, optimize, and then scale over time? So our goal with Dell and Dell Professional Services is to really help our customer through that end-to-end journey but also meet the customers where they're at. So if we do have a customer, for example, who has addressed the use cases, figured out the strategy, we can help them with the data or we can help them with performance optimization. It's meeting them where they're at and working with them with the AI factory to provide a real easy button for AI enterprises. Let's unpack that AI factory a little bit. So we saw Michael Dell at the keynote, right up front, he had a little bit of an entourage with him, which was awesome. And then Jensen gave an unbelievable shout-out. He said, something to be effective, there's no better company in the world than building end-to-end AI systems than Dell. It was like floor-drop moment. It was Michael Dell, he was ready to take the orders in a good way, good tongue-in-cheek joke, but he's ready to take the orders. So that was quite amazing. But what is the AI factory? What's that partnership like? How can we expect it to unfold? Yeah, it's really an end-to-end solution for enterprises to really provide them that easy button for AI. So it brings the breadth of Dell infrastructure and hardware, so compute, storage, networking, workstations, add devices, laptops, plus NVIDIA AI infrastructure and their software stacks, including the new MIM microservices software that they'll be bringing to market. Plus our combination of Dell and NVIDIA professional services as well to provide a real turnkey solution for enterprises to help them address their biggest challenges. They're most complex issues around adopting AI use cases and driving those into operations and production. Let's talk about what's happening in the field, what customers are asking you for.  You know, tech spending is what it is.  Everybody talks about it on their earnings calls. Our data with our partner ETR shows that about 44% of customers tell us that they're funding AI, gen AI specifically, by taking from other budgets. Okay, so it's not just like, here's a checkbook, go. CFOs are being very careful. Two thirds of the customers expect their gen AI ROI inside of 12 months. Not to put pressure on you. So we know there's a lot of experimentation going on. What are you seeing in the field? How are you thinking about that, helping them get that ROI? What are you seeing? It's really that upfront process of identifying the use cases, prioritizing them, and really understanding where the business value is from AI. So it's understanding how do you apply it, how do you integrate it into your business processes, applications, and how do you make it real? So it's really that first step of understanding how AI drives value. As you're thinking about POCs, as you're thinking about use cases and driving that into production, it's having that upfront lens that assesses that upfront and prioritizes based on that.  I don't think we've ever seen one like this, but we've seen waves. So we know what a wave looks like and feels like, and a lot of times it's like, hey, we got to do something in AI, or we got to do something in X, and that's sort of what's happening now. The boss says, hey, what's your AI strategy? I don't really have a good one. So what is that starting conversation like? You start with the data, you say you start with the use case, but it's like, what are they asking you? What are customers asking you? How do I drive more productivity? I'm sure they're asking, how is Dell using AI internally? How are others in our industry using it? So are you seeing any patterns that are emerging? A lot of the large enterprises are very, very similar to the experience that we're seeing with Dell, which is they have hundreds of use cases they've identified across the organization, and the challenge is really where to get started. Where is the biggest opportunity to bang for the buck? How do you think about clusters of common use cases? How do you think about the patterns? How do you think about architecture from a solution standpoint, and a data strategy to support that as well, aligned with those clusters and use cases, but it's really around figuring out where the best opportunity is, just because in most organizations they're finding hundreds of potential applications for AI. Yeah, so in gymnastics they have the ratings, right? And there's the execution, and then there's the degree of difficulty, maybe figure skating, kind of the same thing, right? So I would imagine there's a similar analogy here, is if you've got really good data, and it's clean data, and it's high fidelity, and it's sort of low risk data, well that's going to be easier, but it may not deliver the business value. So where are people starting? Are they starting to get some quick wins in singles just to get some muscle memory going, or are they going after those big productivity hits? Quick singles I would characterize it as, and they're also focusing more on internal use cases, so functional optimization, things like content generation, software development, sales, support, services, things like that, where it's a lower risk environment internally, before they start to pursue AI use cases that may be more externally customer focused or customer facing, where there may be some more execution risk, or the impact of execution risk might be higher. So software development will be coding, is this correct? So that's got to be a big use case. Yeah, absolutely. What are the early returns saying in terms of the productivity improvements that people are seeing with developers? Yeah, it's significant, so it definitely is worth the investment that we're seeing in terms of the AI tools, the solutions to go drive that, the use cases, so the early impacts for software development from what we've seen is strong, it's positive. And then, what's the state of data? I mean it's, on the one hand I feel like the big data era and Hadoop and all that stuff has sort of really got us thinking about how to get our data as states in order, but at the same time, so much more data was created with cloud and mobile and social, and we just became inundated, it was almost really quite difficult to keep up, and then sort of Hadoop didn't get us where we needed to go, so we sort of pivoted, started to develop pretty sophisticated data pipelines, which probably helped. A lot of that's focused on analytics. I still got the transactions over here, my analytics over there. I've got different data types structured and unstructured, so it's a real challenge, but what are you seeing in your customer base in terms of the state of data? I'm sure it's a wide spectrum, but are we in good shape or do we have to fix our data state before we can get that AI ROI? Fix that data, state is generally what we're seeing, and I think the key goes back to what we were saying before, which is to understand what your data strategy should be and how you should be managing data and leveraging data, you need to understand what the use cases are going to be, and I think most organizations, rather than figuring out what data should look like on a use case-by-UK basis, are going to have to develop a more comprehensive strategy for thinking about data across use cases and AI adoption more generally within the organization. Scott, how about the, we've put forth, you know, my gosh, a year ago now, the power law of gen AI, where you got some big, big models, big size of models, but then you've got a long tail, smaller models, very specific domain, domain specificity within, you know, let's say, I think great use case would be financial services or healthcare, virtually any industry actually, so what are you seeing in terms of that, sort of sovereign AI, private AI, sort of on-prem AI, if you will? A lot more experimentation with the domain-specific AI or LLMs, foundational models, versus organizations looking to build and train their own models. You know, I think when we were looking back six months ago, there was a sense that people would be building and training their own models internally, and what we're finding is that there's more gravitation to the smaller, more domain-specific, kind of smaller parameter models than, you know, developing models from scratch on their own and training models. Are people leaning into Retrieval Augmented Generation? Are they looking to you to help them develop that? Absolutely. And how are they going about it? Are they trying to do it out of the box? Are they kind of cobbling it together on their own? Well, that's one of the exciting things we announced this week as well, in addition to the AI factory, is the RAG solution that we have developed jointly with NVIDIA and Dell, Common Architecture, and then we do have a set of services around that as well to help customers rapidly operationalize, implement, and deploy their first set of RAG use cases using a common framework, Common Architecture. So what would that entail? Would I take, basically, a corpus of data, make sure it's clean, put it inside of a Dell object store and get the vector database piece of my choice? I mean, you may have opinions, but I presume you're saying to customers, I kind of know Dell, use whatever you want, you know? And if you want an opinion, we'll give you one. But, okay, so it's sort of open. I can choose my core database, my vector database, and go. And then, essentially, you start getting an LLM or a RAG out of the box, is that right? Yeah, that's correct. And then you start working it and she's human. Help them to deploy the vector database, the embeddings, figure out what the specific use case would be, what the model should be, and then, yeah, get them implemented and help them operationalize that and start to see the initial results and train that over time as well. What about the broader ecosystem? I mean, Dell's a product company, but you've got services that are accelerants. You also have relationships. Dell has relationships with GSIs. You have relationships with software companies. What's the ecosystem look like? How is that reshaping for AI? Yeah, we're developing the specific strategy for working with GSIs and their customers and how they're specifically around vertical use cases and leveraging their industry-specific expertise. We're also heavily relying on the ISV community to bring technical expertise, IP and leadership in specific use cases as well. So we're working with the broader partner community in a number of different ways, both from a go-to-market standpoint, but then also delivery standpoint as well. Dell's service is a secret weapon, Scott. Thanks so much for spending some time on theCUBE. Yeah, thank you very much. Enjoyed it. You're welcome. Okay, we're here covering the AI era, GTC 2024, Dave Vellante and John Furrier. We'll be right back right after this short break. You're watching theCUBE.


T F N N headline news update Everyone buzzle trapping on this Tuesday August the 24th, and we're looking at the Dow up 85 at 35,420 200 points away just under 200 points away from an all-time high of 35,631 this is going to be a very interesting week because look at the V shape pattern here We've seen these V shape patterns rally to new recovery high then turn down a little bit and then Spike to another high. So will this be a catch up for the Dow as the SNP Went to a new high yesterday hasn't made that today, but it did go yesterday And now you've got that four four eight oh point two six high of the August 16th slumping down to the forty three sixty seven level just four days ago running to a new all-time high yesterday and that high was forty four eighty nine, I think yeah forty four eighty nine point eighty eight today's highs forty four point eighty nine thirty one Listen a point away from an all-time high. Look at the QQQ First of all key support for the Dow now is at thirty five thousand key support for the SNP will be at forty four I would put it at forty four Forty eight and for the QQQ which has made an all-time high the game today Little doji candle so far, but it's only 30 minutes into the trading day we're looking at up fifty four cents at three seventy three point seventy eight and That is very good action. This is that alternative counsel We've got an east-dash C and suggest that there should be maybe a little bit of a pullback There may be one more high and then we're going to have to check to see what happens next Let's go to the IWM which has been playing catch up catch up again today It's up forty eight cents at two twenty point ten. It's really stuck in this range Let me just join another arch formation here because that's what I think we're looking at and over a period of a week Or so we could see it back at test in the two seventeen two fifteen areas at two twenty one right now or two twenty actually Point twenty up sixty one cents now. We're going to go to the let's go to the gold Gold is doing very nicely. It's up four almost five points from yesterday's really big move up So this is saying that gold is participating in the rally for more importantly We're looking at areas like crude oil which is coming off a low off the two hundred period moving average And the TLT is pulled back. I'm sorry Yeah, pull back so that yields are just bouncing a little bit is a lot to talk about as soon as I get back


So I was trying to stay out of all this recent Gabby Hannah drama, but I actually got a really, really good mental health question. So let's do this. What is up, everybody? This is Chris from the Rewired Soul, where we talk about the problem, but focus on the solution. And if you're new to my channel, my channel is all about mental health. And what I like to do is pull different topics from the YouTube community to try to teach you how to improve your mental and emotional well-being. So if you're into that stuff, make sure you subscribe and ring that notification bell. So yeah, for those of you who are not familiar with me, I am not a drama channel, all right? So something that I'm always doing is I'm trying to find that, that thine line between like, is this drama or do I have a mental health topic that I can pull into this situation? And I had a lot of requests, a lot of requests to talk about the Gabby Hannah situation with the makeup brushes. I think that's called Kinza Cosmetics. I had quite a few people ask me if I think she's gaslighting. But yeah, like, in this video, this is not to be any shade at Gabby Hannah. Most of my videos that I make, I don't ever, ever, ever expect a YouTuber to see it. Gabby mentioned that she does watch my channel, so she might see this. So there will be some tough love, but I don't have any strong opinions on Gabby Hannah. But I know her audience is feeling certain types of ways with what's going on.  So this is something that we need to talk about. So to catch you up to speed on what's been going on with Gabby Hannah and Kinza Cosmetics, Tana Mojo was involved in this. Basically, Gabby Hannah and Tana Mojo both promoted Kinza Cosmetics and it was supposed to be like the brushes are free and all you do is pay for the shipping. So it's like $10. But what happened was a lot of people ordered the brushes and they didn't get them for like months. All right. And I watched a bunch of the drama channels talk about this and everything. So if you want to go get like more of the tea on this, like go for it, right? But it was taking people months to get it. So people started calling out Tana, started calling out Gabby for scamming their audience.  So people started receiving their brushes, right? And Gabby stayed pretty silent. I don't even think Tana's responded to it yet, but anyways, Gabby did a get ready with me and she addressed it. All right. And this is what got some more backlash. All right. So I watched Gabby's video and I watched some videos using clips of Gabby's video. And Gabby was basically saying, which I completely agree with, but I can see the other side of it. What Gabby was saying was, you know, these brushes, they're, you know, you pay $10 for 10 brushes or a dollar a brush, like don't expect the quality to be top quality, right? And I'm like, yeah, I get that. Like, for example, for example, like I manage my expectations. Like when I go to like Walmart, for example, okay, I do not expect excellent customer service. All right. It's freaking Walmart. When I go to like McDonald's, right? I don't expect amazing food and awesome customer service. Okay. So like, I just want to put that out there. But what people are talking about with Gabby Hannah is one of the major issues was that these brushes were marketed as having an $80 or $90 value. And then they were being sold for $10, but other people did have to pay more for shipping. So people were a little bit upset that she didn't address that. So I have a really good question about black and white thinking and borderline personality disorder, which I'm going to address in the second half of this video. But first, I want to talk about gaslighting. So those of you who don't know what gaslighting is, it is, it's a form of emotional abuse and where, where one person tries to make you question your own sanity, right? Like, for example, when I made a video about Jake Paul, where Jake Paul's like, I'm not taking advantage of kids. You guys are just haters, right? Like, that's making you question like, Oh, am I just really a hater? So people are saying that Gabby Hannah is gaslighting people by saying they're upset about the quality of the brushes, but people are really upset about how long it took or how they were marketed at a higher value. So is Gabby gaslighting people? I don't know. I honestly, I, I don't know. But, you know, I guess it's possible. I'm not inside Gabby Hannah's brain. And any of you who watch my channel, I hope, I hope you know, like I never try to accuse or anything like that without like really blatant evidence. Like it's like, okay, this person is doing this, right? Now I will say this. Gabby maybe should have done some more research, maybe, you know, try to rectify the situation a little bit more. I don't know, maybe, but I'm going to talk a little bit more about that with a black, black and white thinking. All right. But I can understand, like I'm empathetic to both sides in this situation. I can't understand why some people do feel they were manipulated or gaslighted, right? So this next question, which made me decide to make this video actually came from our Facebook group. So those of you who don't know, we have a mental health support group on Facebook as well as on discord. It is always linked down to the description. A ton of you send me DMs, emails, all sorts of tweets. And like the best thing you can do is get involved with the support group. All right. I don't have all the answers. I do not have all the answers. The best thing you can do is get involved with these support groups. So this post I'm about to read you. Our support groups, we have rules and guidelines in there. They're meant to be 1000% confidential, but in situations like this, I asked the person who posted this and I said, are you okay if I address this in a video? And she said yes. So that's why I'm doing it. So just so you know, if you join the groups, I'm not like taking things and making videos about it unless I get your permission. All right. So anyways, this post said, Hey guys, I want to talk about something here that's been bothering me. Mostly this is just for Chris. I'd like to ask that everyone please be calm and respectful in the comments. So about the Gabby Hannah, Hannah scam thing. I am someone who struggles with borderline personality disorder. So black and white thinking is a huge problem for me. I love Gabby and she has done so much for me this year with helping me understand my own mental health and inspiring me to make music of my own as I go through my journey. I see a lot of myself in her and seeing her succeed and the amazing message she spreads has inspired me. She genuinely is one of my favorite people on the internet right now, but I'm having a hard time because of the way she addressed the issue with Kenza cosmetics. Less was less than graceful and the whole situation was just so bad to begin with. I'm disappointed in her and my BPD is so confused because I love her to pieces, but she did something really dumb. I guess what I'm saying is I'd appreciate if Chris could give me and others some guidance in a video or post addressing the issue and how to acknowledge slash hold someone accountable for their wrongdoings while still being able to love them. Thanks guys. And like I said, please be nice. I'm not asking for people to send hate Gabby's way or to argue about the her character like with all of Chris's videos. This is this is about a larger issue. Thank you all and God bless. So yeah, this this made me want to make this video. So those of you who are not familiar with borderline personality disorder or what black and white thinking is black and white thinking is something a lot a lot of people struggle with even if they don't have borderline personality disorder. You see it all the time how people just switch from one side to the other.  Somebody is either all good or all bad.  It's hard for them to look at this and say, okay, maybe you just did one bad thing, but the whole of you is not bad. So that is what she's asking in this post. She loves Gabby Gabby's helped her a lot with her mental health, but Gabby did this thing that upset her. So for somebody like her with borderline personality disorder, not Gabby, but the person who posted this, they're struggling with their brain is trying to categorize Gabby in the negative side of black and white thinking is trying to say she's a bad person. You can't trust her because people with borderline personality disorder, one of their symptoms is a fear of abandonment, right? So there comes a lot of trust issues and all of that. So this is why sometimes people with borderline personality disorder, they wait for you to screw up and then they push you away, okay? Because sometimes they self sabotage. Now, although I've never been diagnosed with borderline personality disorder, black and white thinking is something that I've struggled with. So I just want to kind of talk about what I do and the methods that I use, because this is something that I can definitely relate to with YouTubers. I can definitely relate to this with YouTubers. There are YouTubers who I absolutely love and they might do one tweet or they might say one thing in a video, right? And I'm just like, oh, I'm done with them. I'm done. Unsubscribe, done. Bye, right? And that's crazy. That's crazy. So one of my tips for dealing with black and white thinking is empathy, right? So ask yourself, ask yourself, how would I feel? How would I feel if somebody just completely, completely shut me off because of this one thing that I did, right? I have to ask myself that. It wouldn't be fair to me, okay? Or would I want somebody to give me another chance? You know what I mean? So like the post said, like we definitely have to keep people accountable. And I think, I think Gabby is seeing the backlash and hopefully learning from it. But also if Gabby does see this video or if any other YouTube creators see this video, I hope you understand that some people in your audience are struggling with things like black and white thinking. And when we make videos to address certain topics, we really have to think about that. We have to think about how our audience who might have mental health issues is struggling with these things, right? Because we see it in the opposite direction too. So one thing that black and white thinking can do too is make you like irrationally loyal to somebody, right? We saw it with like Logan Paul. When Logan Paul did his idiocy in Japan, you saw people just sticking up for him no matter what. So black and white thinking can do that for you too. You can be just like just irrationally loyal, okay? So it's about finding balance. The other thing that I recommend, and this is something that I do in a writing exercise or I actually, you know, a lot of times I do it in my head now, but you can take out a pen and paper, you write down what is true and what is false, right? What are the true things that your brain's telling you?  So in this Gabby Hannah situation, right? Like what is true about Gabby Hannah? So based on this post, and this is just kind of like a rough way that you would write this down, Gabby Hannah has inspired me. Gabby Hannah has been a great advocate for mental health. Gabby Hannah has helped me, you know, overcome some of my fears.  She's always been an awful person. She hates everybody. You know what I mean?   You can say, okay, maybe these things in this column aren't necessarily true.  My mom doesn't care about me, but I had to write down like my mom has always been there for me. My mom came to the hospital.  My mom helped me get sober. So on this side of the column, when my brain is telling me my mom doesn't love me, like I have evidence to prove the opposite of that. All right? So something with borderline personality disorder or black and white thinking in general is trying to rely on the evidence rather than your emotions. All right? And that will greatly, greatly help you. So is Gabby a good person? Is she a terrible person? I don't know, man. Like I've recently been following Gabby. She seems all right.  She talks about them. She addresses them. I've been reading some of your comments and I don't know where they're coming from. You know, a lot of people do feel manipulated or gaslit by Gabby. I don't know, man. I've been following her for a few weeks now. But if this is something that you struggle with, even if you're not a Gabby Hannah fan, if you're struggling with this with other YouTubers, try to take some of these suggestions. Okay? Even when you're on Twitter and you see this news come out of somebody doing this or somebody doing that, like check in with your own black and white thinking and saying, like, why am I putting this person in an all good or all bad category? Like something that is an insane expectation of all of us is thinking that other people have the potential of being perfect and never making a mistake. The same thing is with ourselves. Some of us are way too hard on ourselves because we hold ourselves to an insane expectation that we're never going to make a mistake. Right? We can have that black and white thinking of ourselves too. We look at ourselves as all good or all bad. Like I'm a great person who has done some pretty terrible things. You know what I mean? So I try to empathize with other people and that's why I'm a very forgiving person. That's why I don't think anybody's a hopeless cause because I have done terrible things in my past and I've worked really hard to get where I am today. All right? But anyways, let me know down in the comments below.  Even if it's not with the Gabby Hannah situation, like I would love to hear a story about how maybe a YouTuber did something and you just like completely switched your views of them. All right? Like anything like that. Like let me know down in the comments. Let's have a conversation. Okay? But anyways, that's all I got for you with this video. If you like this video, please give it a thumbs up. If you're new, make sure you subscribe and ring that notification bell. So I make a ton of videos and a huge thank you to everybody supporting the channel over on Patreon and we have a Patreon Q&A coming up. A lot of you send me requests. I don't always get to them, but if you want to for sure have me answer your questions, sign up for Patreon right there for as little as a dollar a month. All right? Thanks again for watching. I'll see you next time.


Standing in a field of corpses, Russian mercenary boss Yevgeny Prigazin on Friday published an expletive-ridden video personally blaming top defense chiefs for losses suffered by his Wagner group fighters in Ukraine. Prigazin's tirade reignited and escalated a long-running feud with defense minister Sergei Shoigu and chief of general staff Valerie Jarazimov, whom he has repeatedly accused of starving his forces of ammunition. Prigazin appeared next to dozens of bloodied corpses that he said were those of Wagner fighters. We have a 70% shortage of ammunition. Shoigu. Jarazimov. Where is the ammunition? He yelled into the camera. Prigazin, whose Wagner group has spearheaded Russia's months-long assault on the east Ukrainian city of Bakhmut, began publicly feuding with defense chiefs last year, accusing them of incompetence and of deliberately depriving Wagner of ammunition out of personal animosity towards him.


It feels really great with your photo in a magazine obviously and it's good to know a lot of people apply and when you come out as among the top 30 among so many so it feels great obviously and honoured. It doesn't matter where you come from in advertising but advertising always welcomes you with open arms. All you have to be is just be passionate, hard working and most of all just be patient because this industry takes a lot of time for your work to get out. So just be patient and make sure you can gulp half a bottle down before even starting your night.


On April 8th, the whole world will stop and look up to experience a once-in-a-lifetime event together, the Total Solar Eclipse. We're answering your top questions. Check out our special YouTube playlist and visit purdue.university.com forward slash solar dash eclipse to get your Total Solar Eclipse event tickets.


So yeah, I actually want to ask a question in the room, especially of the folks who use the issue queue quite often. One of the things that we observe is that people use the issue queue in different ways depending on what they're doing. So one of the questions I wanted to put out there, just as sort of this crazy idea, is what if we had like a YouTube channel where people literally did screen capture of themselves working through issues? That would be awesome. Essentially using a tool like TriMai UI or something like that so that we were getting a sample of a whole bunch of people using the issue queues and walking us through what they see when they use it. I like that a lot. Yeah, so I mean it wouldn't take a huge amount of time if you're on a Mac. You could just use QuickTime Pro to capture the screen capture. But in usability testing, we often do what's called a think aloud study, which is basically you go through what you're doing, what you normally do when you visit a site, but you think aloud and tell us what you're looking at, what you're thinking while you're doing it, why you're making the choices that you're making. And one of the challenges in doing usability testing, for example, in a product like Drupal, is so many of us, especially when we're dealing with the issue queue, are experts. So it's really difficult to recruit people and really get people from all over the world to just show up at a lab one day and walk us through this process. But if everybody took the next time they worked through a bunch of issues and just did a screen capture on QuickTime, I'm sure we could come up with a YouTube channel pretty quickly and say upload it to here and then publicize it and then we have a whole bunch of data on how people are actually using the issue queue in their real lives. That would be excellent. I really like that a lot. I mean I took down a note for us to work through that. So I threw up on the screen real quick. This is what the issue queues look like by default right now. I do have Dredditor installed, so I get a couple little Dredditor features that have been added in, like hide irrelevant issues. So the fact that Dredditor took the time to create a hide irrelevant issues button is kind of significant because a fair number of our users are basically saying that closed issues are irrelevant. So why do we display them in the default view as an example? Recently closed as a label that you can go to makes a lot of sense, but having that be the default view seems a little bit strange. But as everyone can see, it's basically when was it last updated is the default sort. You can sort it by all the other things, but if someone were coming to just see all the open issues for a particular issue queue, and I'm using Drupal.org infrastructure as an example, they go to a default sort. One of the things that we played around with within the team, and as I said, there's plenty of issues out there about make issue queues more agile. We took the concept of the issue queue and said, okay, we have priority, we have status, and we have assigned. So it is much more meaningful by itself than what we currently see. Backlog would be anything unassigned or anything postponed. So basically saying that I'm not working on this right now because I've taken the time to postpone it. And then of course, you'd move everything that was fixed or closed off to another look. Now we only got as far as grouping this on a single view as a thought of kind of throwing it out for us to weigh in on the work. It was interesting when we put this on staging, it kind of fell down and so we haven't gotten back around to dealing with some of the queries that are causing it to not work. But when we put it on staging, what we immediately saw was data from the way that we manage our own queues. So Drupal.org infrastructure, we have several people on staff at Drupal Association who are constantly monitoring this queue. We still, when turning this on, had 140 that would have been considered active issues. The reality is we're not working on 140 things at once. And if any projects as they are, they're kind of kidding themselves. So what are the things that someone are actually working on? This would be really valuable information for anyone coming to a site, I'm sorry, to a project to evaluate it for use. So anything else to add to that Tatiana? Well, we can also show on this. Oh yeah. So this is something done by one of our volunteers. I think it was Luis Naiman who kind of suggested a similar interface just using Kanban style. So you will see he just like dialed up issues. This is what I get for taking over the controls because my computer is completely not set up to present right now. I apologize. And this uses some of those same concept but it uses the need to review, active, needs work. But it also grouped it into little cards as opposed to the table style, the default issue queues. Another one that would be good for this. Does anyone remember the URL for the localize initiative? And I think I have it off the top of my head. Rocket ship. Hey, not bad. Just like everything else in Drupal, I have learned to memorize URLs. So they were playing with this idea of listing everything as to do, to review, to be committed. I think this view has some similarities to like say what you would see in Jira's agile view. But the basic idea of being able to kind of group things into those areas. I do like the color coding in this. Kind of a nice way to address that as well. So in short, I mean all of the conversations about issue queues seem to come back to the question of how do we actually get our work done. Issues themselves in terms of the comment structure. There's probably some improvements we could do in that space as well. But the what is the most important thing and what is being worked on right now isn't something that we really display to our community very well in our projects. And you guys are going to have to help me out here because this has to become a conversation. I would love to hear from those of you who use the issue queues a lot. Kind of what are the things that are pain points? What are the things that you would see we need to change over time? Yeah, so I work a lot with JavaScript and so JavaScript as a component. But usually it's not really the JavaScript component that is assigned because it's a node module that has a problem. So I like the ability to filter on a component and a tag at the same time or a tag at the same time. But I mean that's just a wish list. It's not very important. But it does happen. So I did use Rocket ship to try to sort my own issues as well. Do you know about the user pain rating for bugs? It's basically you have five criteria that you can select and you get a score for your bug. And if a lot of people, you know, encounters this bug, it's going to rate higher than another. And you can, well, triage your issue based on that. So it was kind of successful. But then again, it's only useful for bugs, not for features. So I guess the question is you talked about Kanban, agile, but we don't really have a proper process for developing Drupal. Maybe contrary module do, but not Drupal core. So how could we, if we implement something new, how do we know to writing basically? And one of the things we had thought about for if we're rolling this out, we wouldn't roll it out and just replace the existing issue view. Because if we rolled it out and just replaced everything, then there'd be wailing and gnashing of teeth and very upset people. But what we could do, and we kind of tried to show this a little bit on this agile view that we threw up on one of the redesign sites. If we released it with the path that included beta, and then we interlinked it with the existing issue queue and said here, try beta and give us feedback. We could essentially allow for that feedback loop that said, oh, is this working? And we could also track statistics and see our analytics and over time we would see whether or not people were using the new queues more than the old queues. And at some point there could be a transition over and instead of having the beta path be the primary path, we have a path that includes the word old. And as we know, people would stop using it because no one wants to use the thing that's path as old. And so about issues, WebChick did some statistics on issues like the time an issue is open, that kind of thing. So is there a plan to publish statistics on issues that say, for example, how long the average issue stays open? Or how many people are involved in issues, overall, those kind of stuff? Some of it is published right now, it's drupal.org slash stats, and it's just a Google spreadsheet which we populate by running queries against database, basically. But there is some stuff there already, like how often issues gets response or comment not by its author, which is important. But then again, I mean, stats like how many time an issue gets from need review to need work, or from RTBC to need work, which is probably more important. Like those kind of things would help us, well, work better, because we know that do we put too much polish on patch, or we get away with doing less perfect patch and still get meaningful review and not spend too much time on it, basically. It's kind of interesting to figure out what is the most valuable metric for getting work done on issues. Right, and then there's the problem of the UX and UI issues that Danny was talking about yesterday. That we don't really, you know, there's no way to really work on those. So what can we do for them to use the issue queue in a better way, or use something else anyway? So it's partially for project maintainers, partially for designers, steamers, all of these people who want to help, but have this perception of, I don't code, how can I help with that? And we talked about the idea of having design maintainers just as much as module maintainers. And for module maintainers, for example, on their project page to have a spot that says how you can help. And literally that's something, you know, any module maintainer can say, I need help. That's the point of open source, is that you're not the only one doing this. So if we have something on the project page that says how you can help, we need help with UI design. Here's a list of all the UI design issues. You can contact me. So it comes to a lot of discussions that I think we've been having over the last year about the state of the issue queue. Is how do we make it relevant for people who aren't the hardcore developers who are in the issue queue all the time? And have figured out the 85 million band-aids for how they find their issues? If you're talking about wish list, then we have discussed yesterday there was a buff for mentors. And one of the main pain points for people organizing Friday's prints is that we actually have the same user interface for different kinds of contributors. And their needs are very different. For example, people who actively participate, they want issues to be split up for groups of their interest, like issues that they're working on, issues that they want to follow, but not necessarily work on. For mentors, it would be nice to see issues of their mentees and things like that. And another thing that was raised yesterday on that buff is that because of the character of the issue queue, it is very different of other types of content presented on Drupal.org. Maybe it does make sense to have it as a separate tool. Maybe having the same single sign-on, of course, but still. Yeah, we actually have talked about the idea of what if we spun off issues. One of the difficulties there would be figuring out how they could still relate back to projects. Because the bulk of what Drupal.org does is it provides the projects and issues. Certainly it has the documentation, but if we're narrowing it down to like four things that Drupal.org does primarily, it's users, projects, and delivering those projects to people. It's issues and it's documentation. So the question of do we spin it off, I think we'd have to weigh that against how much more difficult will it be to tie it back to those other things if we spin it off. I wanted to elaborate on something a bit different because you were talking about making priorities more visible to people who visit like a module or something. And so about making things visible, what are the plans to improve the project page? I don't know like visibility and measurements around the state of projects. Because I mean, it's always been a pain to select a project to do something and people get really, really confused about how to do that and which one to choose and all that kind of stuff. So what are the plans around that? Well, I can tell you that it's been prioritized as one of the things that we're going to focus on for the next year. It's in the user research that we just conducted between Austin and now and the personas that we developed out of that. There were quite a few use cases that basically pointed to the fact that the biggest pain point for someone who is learning Drupal, someone who's skilled at Drupal, someone who's an expert at Drupal, it doesn't really matter, but one of the biggest pain points is finding either the right module or finding a module that they want to come back to. Finding that module that maybe they followed and they want to come back around and be able to see, oh yeah, I wanted to try that, I remember reading about it on a blog post. So the two parts of that would be how should we display those modules in the search interface? What data should we pull out? Because we've got quite a few project page improvements that happen after the Drupal 7 upgrade in terms of adding additional statistics. The question is which of those statistics are the most valuable for someone in selecting a module? If we went purely based on crowdsourcing, we could say this is the module that's most installed because we have that data. That's the order we list them in right now. We don't necessarily, the information architecture of the page doesn't necessarily highlight that is the most important thing and that's why we're sorting them in that order. It's not like it's a big number that people can see as the most important thing. It's one of the things that displays in that. So that'd be something we could look at. Any other thoughts, questions? Like what are the things you guys want to see in the issue queues? Go ahead. I'm liking this, it's like user research to a small room. I would like a page where I can order the issues to work on. So put them in a certain order. So just collect issues I want to work on but not right now. That's kind of cool.  Yeah, for example. Or another method could be a way to pull the issues to your own site so you can order them on your own site. Right now, I tried with the RSS feeds but changed the search labels above. For example, priority version. But the RSS feeds still displayed the 50 last issues instead of what I searched for. Yeah, so the rocket ship module that was shown before. That's what the multilingual is using. Yeah, so you can put your own whatever issue into your own site and do whatever you want with it. I don't know what can you do with that. Alright, so basically the rocket ship, it's going to crawl an issue page that you give him and then save every issue into your own site and then you can do whatever you want with it. No, no, no. As a matter of fact, everything that you see over here, so if I go to click on the issue, this is the Drupal 8 multilingual initiative which is one of the better examples I've seen of it being used. Basically for any of those, you click on it and it takes you straight to Drupal.org and that specific issue. So it's really just a means to view it but not anything else. Again, it takes the tag, the also of the issue and some mid-time formation that you don't get into the RSS feed. Because it's scraping that back off the site. I would love for us not to need to scrape it. I would actually like the issue queues to just work. My question is actually not regarding the issues and problems that we have. We discussed that and there is an issue about how we can achieve something from what we want from the wish list. But at some point we get stuck and we don't know how to proceed without help from the AI people. Well, you can come on Friday and we'll sit next to you and we'll explain you all the things. That's actually a good point. Part of it is asking. There is a block on certain things so we can set up just about anybody to have a development environment and they can begin developing. That doesn't necessarily mean that they will understand all the places where all the specific integrations of that Drupal site. Any time you come and start working on a new project, it's going to take you a while to get up to speed. A lot of these things, it takes a while. You may not be able to make an immediate contribution but if you're really interested in it and you want to spend some time with us, then we can probably get you to the point that you can push it further. That's actually the one that Lewis had done right here. That's exactly the approach he took. He was like, hey, I want to affect this. Got him a dev environment and we started playing with it. The issue that we ran into here is it's a start. We could roll this out as a beta just the same as we rolled the other one out as beta. We're trying to figure out how best to get the feedback. Sure, go ahead. I like all this swim lane type of layouts that you have designed. You also have the one where you saw the active tasks and the backlog. I think that's a really good step but even before that, what is my issue in the issue queue is when I come there and I'm motivated and I want to contribute to some module or to core, when I come there, I would just want to kind of magically see a short list of different issues or options what I could work on. For example, a few weeks ago I was going on a hike. I wanted to buy this hydration pack. I went on a website and they had this really graphical kind of search engine or product selector, if you will. It asked my weight, how long the hike was going to be, what the weather was going to be like. After answering a few simple questions, it just showed me a selection of products that would match my needs. When you come to the issue queue, you could have some kind of issue selector which would be more user-friendly and graphical than just these drop-down filters that we have because I think it would really improve the quality of the search and the user experience. Kind of like issue facets or something like that, being able to do a faceted drill-down of a particular queue. Though, what you're talking about too, asks some questions around what are your preference. Yeah. Do you want to work on backend or front-end or site building or documentation? How much time do you have? Do you want to work on critical or minor issues and stuff like that? This is one of those interesting ones where I think an outside view into it is always valuable because we've been using the issue queues for so long we have a bias. So being able to get that look through a set of eyes that are willing to tweak it and make it something new, I would love to see more comps of what this could look like. Obviously, we might pick apart a little bit whether or not we have that data, but we can always look at whether we can start collecting that data. For instance, you were talking about front-end versus back-end. I'm not sure that people really use issue tags accurately enough to give you that data right now. But the front-end team does. The front-end team does, yeah. That's true. We can map a topic to a set of tags that we know will bring up relevant issues. Sounds like a topic page. It's just some mapping to do. You can say that louder. Sounds like a topic page, right, Boyan? Yeah. Are there any other ideas, more things that you're just dying to see in the issue queues? Please. Like I said, this is great. Getting to hear people actually give us direct feedback. The reason why I came to this session was very curious on how Triple wants to maintain the large size of tickets. There are huge sizes of tickets in some are critical and some are for the wish lists. So I was wondering for a certain module, you have 300, 400 issues. How do you present to the user which tickets are most important? So what I've seen here, the most fun I've seen here is which tickets are fixed. And I was wondering also if you considered to implement gamification to solving of tickets. Some tickets are easy to fix. You can earn points or something like that. And when you see tickets are fixed, you can also see that certain person, user has earned a lot of points for it. I don't know. So that's my question. Have you considered gamification? Yes? I think he definitely covered the idea that commits and tracking contributions which may not actually be a commit. It might be the comment that has the patch that eventually rolls into the commit. But being able to track that and tie that back to a credit system of some sort would be really valuable. What you're saying is the person who actually marks the issue as closed fixed, that could be another metric.  No, you can. That's true. But you can. Makes them fixed. See that's an interesting thing because I think our permissioning system doesn't even really allow for that gamification. Because as soon as we gamify marking issues as fixed, there could be some people who get a whole lot of points really quickly by fixing things that maybe shouldn't be. So we'd have to figure out how to make that. So Neil, you have said points do mean prizes. Oh, okay. Oliver said that. Never mind. All right. So a few things that are sort of swimming around. Again, in terms of gamification, we are talking about how to expand the metrics that we use to count what is actually a contribution. I resist the idea of calling it gamification. So you get points and badges and all of this other stuff, even though there's some of that language being used, because the issue queue is not a place for gamifying, frankly. The issue queue is a place to get work done. So the question is, can I quickly find what I have to do, figure out what I need to do to finish that, and then close this out so I can move on to the next thing? Or is there, and there's a difference between the stuff that I have to do in the couple of hours that I have, and I just want to move through a list of issues. And the stuff that I want to work on when I'm at a sprint, which tends to be bigger, requires more feedback, requires, like, being able to run over to that guy at the next table, or, you know, talk to someone else and say, help me work through this issue. So we have to understand the different types of issues that people work on and find a way to point out, for example, this is something you could do in 20 minutes. This is something that is going to take more work. So that's one area that we need to think of in the content. How do we sort of separate out those larger scale issues from these smaller ones that you can just pick off? And we're trying to do that with the meta header on issues, but it's hard to say that that's effective because we can't really pull that out and say, here are all the big sort of initiative type issues we're working on. I think we were talking earlier, like, the agile workflow, you have epics and you have stories. And that's what we're trying to recreate right now. We have meta, but it doesn't really equal epic because we don't track it that way. We don't see the aggregate. Yeah. And so that's one piece. Then in terms of what you're trying to get at, I think, with gamifying is this idea of motivation and satisfaction and increasing sort of the fun factor of writing code, which is its own other thing. And one thing we can think of is when we actually, so first of all, I think the biggest thing is we need to make it much easier to decide whether an issue is resolved or not. So those issues that should take 10 minutes, they should actually take 10 minutes, not 10 minutes after an hour of reading every comment. And then going in and marking it closed in this area that's entirely separate from everything else related to the issue. So this way of quickly scanning is something we have to try to prioritize. But then a very simple sort of UI issue is make it really easy to say, yes, this is fixed. And then let it disappear or let it like go into a little hidden filter somewhere. So at the end of a two hour session where you pick off maybe 10 or 20 issues, you can look and say, huh, yeah, I got that done today. So when we think about like, you know, so I would think about gamification that way is sort of like creating that satisfaction of a job well done. Like I was productive today, I did what I needed to do to maintain this module and maintain the commitment I made to the community. And then the other thing that I wanted to talk about is actually back to your point about choosing modules for a project. One thing that happens a lot in the design industry with assets, so image assets, font collections, all of these other things is we tend to group things like assets into categories based usually on the project. Like I'm using this set of fonts for this particular project, this light box for my Getty Images account is related to this particular thing. What if we could do that with modules? What if each like developer can flag a module and say yes, this is what I use all the time. Like, but your personal, what I'm saying is like your personal collection of modules. Like you can flag a module and say like I know that I'm going to need, you know, this is back to Drupal 6. I know I'm going to need CCK and views for example. And I'm going to need path auto and fences and like this collection of things that I download for every single project. And maybe in your collections, you can download a tar of all of those modules in one day. Or a make file. Or a make file. So that's another. Well, the gain is, I mean the gain is specifically for this learner to novice.  But when someone's just learning Drupal and they don't know that yet, you have to go to every single project page, download every single tar file and it will take you literally two or three hours just to do a basic site. But people don't know what distributions are and not every distribution has the configuration that you need. And not only that, as people gain mastery with Drupal, they start developing their own custom distribution on the side with a checklist of modules they always download. This is behavior we've seen over and over again. I disagree with you. Because distributions don't help build mastery. Having a collection of modules that is just given to you and say here install this and everything is fine is not helping you learn Drupal. It's helping you say, I need this distribution. But as you learn Drupal and you start flagging modules and saying, yes, okay, this one I've seen is good. I'm going to download it every time and find it useful. That is actually helping you build mastery. It also provides incentives for maintainers. If you know that there's a ton of people who have flagged your module as I use this in my daily work, then that can actually be brought back to the issue queue. You need to pay attention to this module. That can be set up with reminders and that kind of thing. Yes, remind me when this is done. That might not help every maintainer, but it might help the day reads of the world. The other thing we've touched on briefly is almost like a five star rating based thing as well. That ties in with that a little bit, almost being able to flag in common modules that you like. It does get, again, that touch idea of being able to find highest ranked modules and what could be useful for your site for newbies. I think it's interesting how the conversation of issue queues immediately gets us to module search. It always seems to come back up, which goes back to the stuff we saw in user research about module search being so important to so many people. Any more thoughts on issue queues? Like I said, we're filling in because the person who was going to be here didn't make it to Amsterdam. We decided to use it as an opportunity to get feedback on what you guys would like to see, because we have the ability to implement a lot of this stuff now much more quickly than in the past. Say again? I'd like to take a look at the older notes. Anybody else? No, it's alright. I actually kind of like that it's cold in here. It feels good. I've been sitting in a hot room half the day. These Dutch, they keep everything so hot. Is that everywhere, Pohang? Oh, okay. Alright, well going once. Going twice. Hey, thanks. Everyone who made it in here, thanks so much for coming and having the conversation. I appreciate it. I'm moving. Oh, wait, he's coming. Thank you. And now we'll stick around and take notes as well. I think what I am going to do though is go ahead and... I have a question. If you'd like to hear a little bit more about Git, we actually do have a conversation that we are firing up over in the Amsterdam suite where we're going to have one of our engineers who's been spending quite a bit of research time on the conversation of Git versus GitHub and what can we do. I've actually been presenting on it several times when talking about our key initiatives. And if you're curious, please do stop by because it starts at five o'clock and you can listen in. It's a lot of information to present because, believe me, there are a couple of years' worth of research on this at this point. Do you want it on the recording or would you like to just ask it separate? Go ahead. One idea for improvement for maintainers can be echo templates. So they can choose an answer from a list. If they need to... If they put an issue to fix, they can say no. Thank you for all your input. I hope this is fixed now. If not, feel free to reopen. canned responses on issues, yeah. They probably do it with a browser or JavaScript plugin, right? Yeah. It's not really important to me but it can be an idea. All right, cool. Thank you. I appreciate that. Okay, again, thanks everybody for coming in. Appreciate it.


Welcome to Trader's another technical chart with me Patrimonial. We want to look at the Euro dollar here on the four-hour time frame and we've got a 1, 2, 3, 4, 5, 6, 7 swing structure. We've got some nice divergence into this low. What we're looking for now is a break of the trend line resistance that comes in let's say 1, 1575, long positions through there up into 1, 16, 39, pullback. We're ultimately looking for a corrective move to take us up into 1, 17, 50 as the corrective upside objective. As always Trader's, plan the trade, trade the plan and most importantly manage your risk. Until next time, thanks very much.