All right. So welcome, everyone. This is a session about Drupal.org, obviously, about how it is changing and how it has been changing over the past few months. And we really have three very, very different topics to cover. So Josh and I will go through all of us really quickly, and then Ryan will talk about Composer, because that's what everyone here for, right? Okay. Is here anyone who cares about content? Thank you. You are my favorite people. So I will give a very brief overview of the content-related changes, which are all part of sort of the larger content restructure initiative we have going on on the website. Firstly to give you some background, last year we developed the overall content strategy for Drupal.org, which sort of includes recommendations on a number of new content types and also on better ways to structure content on the site. So for more information, I won't talk much about that, but you can go follow those links. The first one is my session at DrupalCon Barcelona. We also had the same session at DrupalCon Los Angeles, and the second link is issue which has like 20 child issues with all the details you will ever want to know. So this year we are focusing on implementing those recommendations, which came out of last year's project. So essentially what we are doing, we are restructuring all of the content on this huge website into a new structure, into new groupings called sections, they are based on different types of user activity happening. And behind the scenes, those sections are actually organic groups, which gives us various perks, such as flexibility to have different user roles and different permissions in different sections. For example, some sections could be more editorial content, so only specific people can be able to edit it, and no one else can. Also we'll be able to display a single piece of content in multiple sections if we want to, and perhaps we might even use different themes for sections, which sounds crazy. So at first we wanted to test our assumptions and ideas on some place, which is less visible and has very little traffic, so no one could see it. And so the first section created was about Drupal.org itself, it is sort of a meta information about the website, various guides, and it primarily is aimed at people who develop Drupal.org or contribute to Drupal.org in some way. And the content is mostly produced by our internal team. So that section worked pretty well. And then the next one, and the first sort of highly visible one, we created was about, which is general information about Drupal and also various promotional materials. So to create this section, we actually audited all the content in the old about Drupal area, which used like book content type previously. We rewrote most of it, and we recreated it using the new content types we now have. The third section created was Drupal 8, and this one was created from scratch specifically for Drupal 8 launch last November, which was a fun few weeks. All the content was written from scratch by our communications team with a lot of help, review and feedback from core people, core committers. And for this section, we went one step further. Not only it has a unique content, it is also designed to look completely different from anything else on the website. So to make this happen, we actually created a separate theme, which is only used in this particular area of the site. Again, this is something organic groups let us do fairly easily, maybe. Yes, no problem. So another thing we did in the last few months, we introduced a new way of communicating information on Drupal.org. Right now, we have topical blocks in some of those top-level sections I was talking about. For example, this is a Drupal blog. It is located inside of about section. And we will see more and more of those coming up in the future. Around the same time, we also introduced possibility to follow individual pieces of content. For example, you can follow a post in a blog and you will receive email notifications for all the new comments. And this is also possible for forum topics, case studies, and book pages, I think. In the future, we also plan to add ability to follow the blog itself. So you will receive notifications not only for comments, but for the actual new posts where email or where your dashboard, which will be really cool. Along with those content changes, we will be also introducing visual changes on the site. And all of them are part of the new design system for the site we are developing right now. You already can see some of them in the header area, in the Drupal 8 area. And more of them will be coming soon. And by the way, I have those links at the bottom, many slides. Each of them is like a very long blog post about this topic. So if you want to know more, you can always read more, because we write a lot about what we do. So speaking of features which are coming soon, the next big thing we are working on is a major redesign and improvement of documentation. In fact, we have a whole session about documentation in this very room at 3.45. So if you want to know everything about documentation ever, you should come. And with that, I will let Josh talk about issue credits. All right. It's also going to be a workout. The good news is I can talk loud enough that the microphone could probably pick it up. All right, there we go. So we're going to talk a bit about issue credits at the marketplace as well. I feel like Tatiana is messing with me, because I didn't have to slide in here. I have to click there. Okay. All right. So to start off with, I've gone into a lot of detail to explain a lot of this in a blog post that we did earlier this year. It's the guide to issue credits and the Drupal.org marketplace. How we capture those issue credits is kind of an interesting process. If we go back and talk about how it all started, it was a conversation that Dries kind of opened up. And I can actually remember sitting with him around a table at DrupalCon Austin, and he was talking about this idea of doing commit credits and how we could do a better job of tying commit credits back to organizations that are contributing to Drupal. And if you saw the Amsterdam keynote later that year, he talked a little bit about this idea of the commons, the common good that comes out of a public project, an open source project like Drupal, and how if we can figure out a way to get people engaged with the idea that giving back to it is of actual benefit, then we're going to get greater participation by a wider range of companies. And I really wish I'd actually kept the napkin that we were playing with when kind of drawing out what some of this stuff would look like because it was a great initial conversation. And initially it was going to be something really simple like, here's the shorthand for it. That started falling apart whenever we started looking at, well, how do you save that shorthand into the database? Because if one person says that they work for the Drupal association and another person says they work for the DA, they mean the same thing, but they're using two different words. Or maybe just adding Inc or LLC to the end of a company name actually makes the idea of doing it based on text formatting and parsing kind of fall apart. And we don't really want to push people to this idea that they have to know short names or that they have to have a special number that they contribute to organizations. We're like, we can probably figure this out with software. It's kind of what we do. So we basically started with this simpler idea before we released the full issue credit concept. And that was, well, what if just every project could say, here are the organizations that are supporting this module theme, whatever it may be. So we added a very simple field there. If you are a business owner and you're actively contributing to a module and you have a maintainer on a module, you should absolutely ask them to put a little information about the organization and how that organization is contributing back. It's usually time for their developers. It might be money related to contractors. There's a lot of different ways that organizations can actually make a module more successful by giving it some resources to make sure that it has the time for support and maintenance and ongoing improvements. The next step after that was, OK, where do we do, and by the way, shout out to the Bear King. Brendan, he's on my team, we call him the Bear King. There's a story behind it, but I'm not going to go into it. So we said, OK, well, if we really want people to track how they're contributing, the best way to do it is to put it at the point closest to contribution. So in the case of issue credits, what it really comes down to is when you're contributing in the issue queue, there's a comment. Maybe you're uploading a file, maybe you're posting a review, maybe you're submitting a patch. All of these things are at the point of contribution, and we added this very simple interface that basically says, hey, you can attribute this contribution as a user to an organization. Now I will say, in order for you to associate it to that organization, you're going to have to take the step of creating an organization profile. So if your company doesn't already have an organization profile you want to contribute, then you need to create one. There's some spam prevention measures in place that require someone creating an organization profile to have been confirmed, which is one of the tools we use in our community to basically highlight people that are real humans and that are doing something that's helpful for the community. So if you post to an issue queue, it's your first time doing it. It's something helpful, likely someone who's been around for a while is going to come in, hit the confirm button, and then you would be able to add an organization page or case study or some of these other content types that we have some little gates on. After that attribution has occurred, the kind of next step falls to the maintainer, and this is basically at the bottom of any given issue. There's this little widget that lets you see who's participated in that issue and how they've participated. Maybe they've uploaded a bunch of files, maybe they've made a lot of comments. The maintainer of that project can look at that issue and say, this was valuable contribution. This person deserves credit, and they basically check a box. It remembers that they checked the box. So at any point that they're participating in it, they can save a little bit more metadata. And they keep working along in that issue until the point that it closes. And at the point that it closes, it tallies as a credit in a couple different places. So the steps, again, if you're going to do this, you have to start with the create an organization profile. To do that, you just go to the marketplace. There's a nice little add your listing button there. Click on that. You're able to go through that process. The users, if they want to be able to add an employer that's just kind of always there in their little form, they need to add that organization to their profile. And to do that, it's just part of opening up your personal user profile, going to your current work, adding a reference to the company that you work for. Right now, we're doing an exact text match is what causes that to appear. Eventually, that's going to shift to organic groups as well. So there can be a little bit more maintenance and management by the organization owner as to who actually belongs to the organization. We do occasionally get requests to remove somebody who's moved on to another organization or who no longer works for that organization. I should also add one of the cool things with this process. It doesn't have to be a company. One of the biggest non-company contributors is the Drupal Ukraine community. Tatiana's giving a shout out there. They created an organization to denote the work that they were doing that they felt was for their community. So it's kind of a cool way to do it. I would also encourage if you're helping to organize a Drupal camp, have them create a Drupal camp organization and attribute that as your customer or as the organization you belong to as a part of the issue queues whenever you're working at that camp. And we can start seeing the kind of growth of contribution in that particular location. It'd be a powerful way to use issue credit. So if somebody has a camp, I highly recommend you do it. If you're in the contribution sprints this Friday, attribute the credits to the Drupal Association. Say, hey, this is related to DrupalCon, that sort of thing. As a customer, not as an employee. That'd be weird.  So again, the credits are awarded by the maintainers. So that's one of our fail safes in this. It's really hard to game the system. I've seen it happen once in one year. And that person did it accidentally. They were actually legitimately wanting to participate, but they were just doing it the wrong way. It's a very successful system so far without a lot of abuse. We only display the last 90 days of issue credits on an org profile or on the marketplace listing or even on an individual's profile. And we have a reason for that. Participation is ephemeral. It has a shelf life. If we only did total credits, then the really big organizations who can throw a lot of money at it would just stay at the top at all times. And so by making it a 90-day swing, what we've actually seen is some of these really powerful stories of, like say, Fauci, which I mentioned in the keynote introduction this morning, who once they found out about it, they started truly contributing back to Drupal.org, making sure that their staff knew how to do it. And they rose from obscurity in the organization pages alphabetized at the time, letter F doesn't get you very far in a community as big as ours. They're all the way up to number four. I could say the same thing about Value Bound, which is another organization that's done some amazing work in getting their people to actively say, hey, this is who I'm working for. Those are both relatively large companies. I've also seen companies that just have an incredible spirit of contribution, like say, MD systems. MD systems is currently number one.   They're just always on top of it. They also have Berter, who frankly is a machine, I think. Not literally, I've met him. He's a nice guy, but I think he might be cyborg. So those last 90 days, it gives that ability for people to move up and down in scale to show up in the top 50 organizations that are contributing back. We've never done a listing of users by issue credits that we do have this data and I do occasionally pull it and put out thank yous to people who are doing a particular high amount of contribution back. That we never really wanted to create the grand leader board. Though I have been tempted with the 90 day concept because it would pop around and people would go up and down and you'd be able to see like, hey, they had a lot of time to contribute back or they had an awesome customer who let them do a whole lot of extra work that they got contributed back. They'd be kind of interesting to see that stuff, but I understand some of the hesitations there. Lots of, oops, again, lots of really fascinating ways to do that contribution. I mentioned the last 90 days. One of the things, I would love a little bit of UI help in this particular area because I don't feel like we've quite got this nailed down to what it needs to look like to really highlight organizations quite the right way. But what you see is how many issues they've contributed in the last four months. You see the projects that it was contributed to. You see the issue count. Dries was just telling a great story in the board meeting a few minutes ago about how there was a company in India that came up to him and said, hey, we really want to contribute more, can you teach us how? And he was like, well, why are you wanting to get involved? And he goes, well, the reality is we just lost a couple of projects to companies that have these contribution profiles where they've got all this credit on their profile and they're getting the business and we're not because they're able to show they know Drupal. And I thought that, wow, that's really fascinating and it's within a year of releasing this we're already beginning to see it kind of impact how companies are able to sell themselves as being Drupal experts. And so this is kind of a powerful way of doing it. I think this is also really important to that kind of Drupal resume sort of thing. GitHub may have your current streak, not the most healthy way to measure your contribution stats sometimes, but GitHub has current streak. We have the, hey, these people really know this stuff. Look at the types of projects that they've contributed to, which is really powerful. For those of you who haven't seen it, this is what the marketplace looks like right now. It's ordered first by issue credits, second by, first by issue credits, second by whether or not they're a supporting partner of the organization and what level that is. So if you're giving money back to basically fund Drupal.org, it's not giving money to the DA so we can go have fun. It's literally empowering us to do things like build tools for collaboration and contribution. It's giving us the ability to do things like release the composer endpoints that Ryan's about to talk about. These supporting partner sponsorship programs are really key because as a nonprofit, we actually don't make any money off of building these tools. So without a business model behind it, we're encouraging contribution to help strengthen the community and through that we get the benefit of being able to do it more and that's pretty awesome. So help us by giving feedback. There's a couple of issues out there right now about different ways of contributing. I would love to hear more from people about things that they see that are key ways of doing it. We're going to do some updates to the organization content type and I actually have an issue out there right now that's going to remove some of the roadblocks to getting listed. It's one of those processes where right now there's a community review process as to whether or not you show up in the list at all. I actually believe we should remove that because if you haven't done any contributions and you're relegated to alphabetical, you fall on, frankly, the third or fourth page of the marketplace right now. So there's no reason for us to prevent people from showing up on page four. I think there's some questions we can ask about organizations that will help us better identify customers, people who are actually using Drupal for their business rather than selling Drupal services as a business, which is what we're primarily good at right now. And I also think it will give us a way to better track volunteer organizations such as the Drupal Ukraine community or, for example, a Drupal camp or a local user group. I would love to be able to track more about how those particular organizations contribute and give back and what they do. So please help us on those issues. If you search the Drupal org queue on Drupal.org, it'll give you an opportunity to weigh in and provide feedback. So that is it. And now we're going to talk about the composer Fakade. The Fakade. It's facade. Sorry, I just realized that it's missing the little curl under the sea, which is really hard to type into Google Docs. Like everywhere else, it's a lot easier to hold down a key. What buttons is the magic one? All right. I'm just going to start with a real high level overview of composer. Just in case not everybody in the room is familiar with it. So composer is a tool for dependency management, PHP. It allows you to declared libraries your project depends on and it will manage and install and update them for you. And how we want to use it, how it helps Drupal, is it'll allow core, core is using it now to pull in libraries from packages and other things. It let us get off the island in ways that we didn't have to invent every single piece of code that Drupal is going to be dependent upon. And soon it'll allow contrib developers to also use those non-Drupal libraries in their modules. And the facade allows us to have site construction using Drupal modules and themes that are proudly invented here. So that's kind of it in a nutshell. So the composer facade, what is it? It's an officially supported service from the Drupal network infrastructure that provides the metadata the composer can use to declare dependencies on Drupal modules and themes. So it's essentially serving as a replacement for a community built tool that's packages.drupalcomposer.org. How many of you are familiar with that? Using, okay great, we've got a lot of folks in here who know that. They were all just waiting for you. Does the transitions work this way too? Okay cool. So just another real high level of how the ecosystem sort of works. You've got a composer repository which the default is packages.org or if you're using Drupal Composer or packages.drupalcomposer.org. And then you've got code somewhere else like GitHub or Bitbucket. Normally a developer posts new code and it triggers a hook to go update all the metadata on packages.org so that the information about which version it is and what its dependencies are located on packages. And then from the command line a user is able to say I want to require, say, Guzzle, HTTP as a library into my project. They can say composer require Guzzle. Composer is going to connect to that packages repository, download all the metadata for Guzzle, parse it apart, figure out what its dependencies are and figure out what else Guzzle needs. And along with everything else in your project figure, determine what it needs to download then it'll go and get all the different components that it needs from GitHub or Bitbucket or wherever else they're stored, whether it's a Git checkout or a tar ball. And so the Composer facade that Drupal.org is supporting is essentially the same thing except we've got our Drupal.org project database and our Git repos since everything's stored on Drupal.org and it's going to act as the metadata repository for all of the Drupal projects and modules and themes. And so, of course, you add new commits. It updates the facade. You want to add, say, the token module to your project. You say composer require Drupal token. And then the Composer command line interface is going to hit the Composer facade, get all the metadata and download stuff from Drupal.org. So it works essentially the same way and if you're using all of this, we'll be part of how it would work in the future. It'll be pulling stuff from packages. It'll be pulling stuff from our facade to build your entire site. So this is kind of my favorite side. Like why did we do this? Why did we build this? Why didn't we just use packages? Why didn't, you know, there's a lot of questions surrounding that. And so one of the main ones is, you know, there's a big difference in the data model between packages which have a one-to-one relationship between I need this package and it's in this Git repository. And so a package and a Git repository are essentially the same thing and you depend upon that package. But Drupal has projects and it has modules inside of those projects. Sometimes the modules and the projects are the same thing like, say, the rules module. You have the rules project and the rules module inside of it and it's equivalent. Sometimes you have things like the features extra module which there's no features extra module. It's just a project but within it there are separate sub modules that are not named the same way. So in order to support these sub modules and have dependencies on these sub modules if you only need one part of a module we needed to find a way to translate our data model into something that mapped one-to-one with what packages would do. So we also wanted to have comprehensive support for all D7 and D8 modules out of the gate. So there was some talk of, well, we can organically move it forward but that requires everyone to submit their own Composer JSON and it would require packages to come and parse that and it would be kind of a slow process before modules would be available. And we were like, well, we have all the metadata that we need without the Composer JSON so we can do this on our side without requiring a slow process. We can have it out of the gates. Another issue that we were facing is the one of semantic versioning. Contrib doesn't have semantic versioning right now but Composer really needs semantic versioning. It's a valuable way that you can have a dependency on a module and updates can happen to that module and you know that if it's a patch level release it probably should not break any APIs and you should be able to just upgrade to it to get your security releases or get bug fixes and if there's new APIs you should be able to depend on those. And our version mapping didn't map very cleanly to what Composer wanted because we have our human readable versions because we have different platforms. We've got 7, we've got Drupal 8 and it's really useful for us to say, well, this is the 7x module or this is the 8x module but it has the same 2.0 branch and they have our feature complete between the two things but that didn't map very well to Composer's concept of here's a package and it does this thing with the platform you're working on. Additionally, there's usage data that takes place. Whenever someone uses Composer it updates the endpoint and says, ham, downloading this and so we use that usage data whenever people download modules whenever there's update stats all of that feeds into what are the top 40 modules? What are the modules that are important? What are the modules that we need to make sure get upgraded to Drupal 9 and we don't want to lose access to any of that usage data we wanted that to keep coming back to Drupal.org. Finally, additionally, project discovery. We didn't want there to be multiple places for people to find where to find modules go to packages and look for Drupal modules go to Drupal.org and look for Drupal modules and the information might get out of sync. We wanted it all to be in one place on Drupal.org itself. Additionally, we have a distributed infrastructure. We're talking to someone recently about they were using the packages DrupalComposer.org and also packages and those only exist in one place globally right now and people in Asia have a real hard time with the latency of trying to resolve all their dependencies because it adds an extra 500 milliseconds and there's a lot of HTTP requests that take place and so this allowed us to build this and put it behind our fast CDN gates because we already had the infrastructure in place for the CDN and so it's already distributed and I've already heard reports from some people that it's like it sped them up considerably. All right, so speaking of versions this is just kind of a map of how we decided to map our current versions to the existing versions and it's relatively simple. For the ComposerJSON files and then the metadata we're just dropping our notion of platform and we're adding an additional zero in for a patch level thing. So a 7.34 beta 2 becomes 3.4.0 and what this will allow us to do is we'll be able to add an additional patch level version to contrib without having to remove the 7.x on Drupal.org we can still have the human readable notion of like well this is a 7 module, this is an 8 module but the machine readable version fits with pure semantic versioning. So one thing that we have to kind of note is that Drupal historically is supported unstable as a type of not quite ready release and the rest of the world supports alpha, beta, RC and full releases and so unstable and alpha are essentially the same thing so we're kind of wanting to deprecate unstable as a type of release. Ah, yes, that's coming right here. So how to use our endpoint? So we've got full documentation on Drupal.org at that link and if you want to add this to your composer JSON it's packages.drupal.org slash 8 and packages.drupal.org slash 7 and we're offering two separate endpoints so that the semantic versioning works so that there isn't any confusion between your modules like which one is it trying to download. It's actually getting the metadata for either the Drupal 8 module version or the Drupal 7 module version. And this is just what the JSON looks like inside. It's a new composer repository it'll try that one first and then if it can't find it it'll go to packages. There it is. So using our endpoint from composer once you have that in your project you should be able to say a composer require a Drupal in the module name and then the version constraint that you need for that module if you want to lock it down to whatever versions and that should add Drupal modules to your project. Additionally we've implemented a couple of features oh wait, I'm sorry there's a couple of other composer features that are also supported like if you do a composer search it's going to hit our search API and hit our solar servers and then it's going to go to all of the other stuff that composer can understand and then composer browse works as well so if you're just like I want to go straight to the project page you can just type composer browse Drupal slash token. I remember one of the things I'd like to point out is like when you're doing a composer require Drupal slash module name that could be the project name or it could be the sub module which is called the API module which is a mutual credit API the project is called mutual underscore credit but you can require either of those and it's a and composer it's a meta package so it basically says oh this is a sub module we're going to go up one level higher and download the full package because again this is that translation between our we have a Git repository that holds multiple modules but you might only want to express dependencies so I'm not sure what best practices are just going to reveal whether or not it's better to try and say composer require Drupal slash project name or whether it's going to end up being better to say composer require Drupal slash individual module name that'll probably be more like they're both supported but we'll find out whether one or the other is probably better so if you're a project maintainer and you want to add a requirement on another module my project requires token I need at least the 1.0 version of token for Drupal 8 and so this is what you would add to your composer JSON in your module one thing to note is you will need to have this here but you also want to still express your dependencies in the info.yaml file because core is still going to look at info.yaml to see what's your dependencies and what's your dependency constraints and so you probably want to have these match now the composer facade is actually going to look at the composer JSON and whether or not you have and what you have in your info file and it's going to join that information together and it's going to for the requires it's going to use what's in the info file because since Drupal needs that it's going to default to that but for all other data fields it's going to default to what's in the composer JSON so if you've got projects on packages DrupalComposer.org you should be able to just drop the major version requirements that either the 8 or the 7 and then add a 0 at the end of those version numbers so if you had 8.1.0 it becomes 1.0.0 and then you want to change the URL to hours instead of the packages DrupalComposer so what's missing what's next what else do we need to make this just fully supported to make it a really nice clean thing we want a subtree split of DrupalCore because there's core well there's Drupal the project but then there's core which is the code base and often times you don't want the same front controller you don't want to use the HT access you're on engine X and you don't need all the stuff that it comes with so you want to use just the core of Drupal and maybe you have a project that's not even going to be running Drupal but you just want to have access to a whole lot of the Drupal libraries so you can include DrupalCore so we want to get a subtree split of that going and additionally want to have a subtree split of the Drupal components so there's several components in the in Drupal 8 that have a ComposerJSON associated with them that you should be able to use completely independently from Drupal and a good example of that is in DrupalCI we're using the plugin architecture from Drupal 8 and right now we can't pull in that plugin architecture we're literally copying and pasting it every once in a while to get that into our project and so we're you know, we want to use it on DrupalCI we like to add distributions and install profiles as a thing to support so that you can say Composer require an install profile as a baseline to start with a lot of essentially a distribution works like a meta package in that sort of that sort of realm but we don't have that baked in yet patches right now there isn't a real good way to add patches to Composer they're not out of the box there's a module that Cameron a Drupal community member has written that allows you to add patches to make Composer work a little bit more like Drushmake that's I think that's built into Webflow, Florian's Drupal project scaffold setup we want to switch DrupalCI over to using Composer for its dependency management right now DrupalCI has a problem that we're running off of project dependencies and project dependency is having a hard time figuring out dev versions and whether or not there's specific versions so especially right now in the Drupal release cycle when people are working on contrib modules and well my contrib module depends on the alpha version of token or a dev version of token it's hard for people to test specific and exact versions and so we want to switch DrupalCI over to using Composer to figure out which dependencies it needs to download and and that would you know as soon as we have that it'll make it a lot easier for people to test exactly what they want. There are still some version issues in some Composer JSONs Path Auto is one that comes to mind where they have put dependencies on other modules in their Composer JSON using the packages.drupalcomposer.org versioning scheme so there's like dependencies on 8.1. So we should open a few issues if we see Composer JSONs that have that I can probably just automatically do that or something but we'll want to migrate those over to using the official one versioning. There's still some complications when using dev versions because the Composer facade does not provide a dist tarball for the dev versions because we don't have a tarball. So if you're using prefer dist then you want to download all the tarballs unless it's a dev version then you want to get a clone of it and lock it at that hash. That way your Composer lock file actually has well I had that dev version that dev version works and it doesn't become a moving target. So we removed dist from the file and so there is a there is a I meant to put this in the slide. Florian has something called Composer Deploy that works kind of like Git Deploy does and it pulls information out of the metadata that we're providing to which dev version you've downloaded so it can be added to the info file. So that's another thing. Does anybody have any questions on everything I've talked about so far? Oh, oh, sorry. It's totally changed where and how does that like stay the same, contrast or stuff that other types of games? It's sort of a limitation of the way Composer works. There's installers that are plugins to Composer itself and so when we provide the metadata we say this is a Drupal module and it'll put it in the I believe it sites all modules directory but there's I don't that's something that still needs to be solved is to figure out how to like say you had a multi site and you wanted it to go to different places that's still sort of an issue of like no it does not, it won't put in the vendor folder it knows it's a Drupal module and it'll put in the Drupal module location. And you can specify in your Composer JSON where things go as well. It the namespace was locked down so nobody else can add anything to it and there wasn't a whole lot of modules I mean, yeah, we should go and make sure it gets cleaned up so that people don't end up with the wrong version, you know, but it seems like a lot of those are like the Drupal console is on there and Drush is on there but those also kind of kind of fall outside of the realm of modules and themes as well, so but yeah, we can definitely look on packages to make sure it's not too polluted with multiple versions of the same thing Yeah, I think I'm not sure I understand I'm not sure I understand Yeah, full projects are listed in there and depending on which version constraints you put on there it depends on which version you'll get of it No, it won't do sandboxes right now Thanks Yeah Do you want to start with that? I'll start with it Yeah, yeah Yeah Absolutely I've actually been doing a lot of research on this. I consider the first two years of having a dedicated technical team for Drupal.org that are paid staff working on it full time as kind of a lesson in fire hose discovery and pointing a fire hose at you and just flooding you with lots and lots of information Early early on when I came on and started building up the team I was getting a lot of when are you going to move to GitHub? When is that going to happen? To give a bit of context the great Git migration where we moved off of Subversion that was a two year project It took I don't know why I said Subversion Sorry The The examples I can't give an example with Subversion WordPress is still on Subversion They take pull requests from GitHub but they run their own Subversion infrastructure because migrating off of it would be a huge endeavor The Linux Foundation still uses Git and a patch based workflow with CLI tools and email They use patches and they email them back and forth to each other Really big projects, it's difficult to do one of these migrations That's not to say it shouldn't be done In fact, I really do believe that there are GitHub integrations we should do But as Dries mentioned the other day whenever it came up in the keynote question to him it would mean having to refactor quite a few things like issue credits Everything I showed you in issue credits requires that we're using comments on issues in order for us to even provide that information about the community Could we come up with some sort of deal with GitHub where we can build in some sort of integration and do some automatic things? Maybe That's definitely some stuff to look at but those are big projects That great Git migration off of CVS to Did you like how I reiterated that? To your project, you're talking about a year of discussion a good six months of a few people moving it forward a little bit and then a good solid six months of let's throw some contractor time at this and get it over the finish line That typical two year project for the community has always been the norm Something like Composer Frankly, it would have taken that long for us to deploy a Composer endpoint if we had done it the old way Having dedicated people working full time on it and having them interact with core maintainers and with key contrib maintainers that are already in that space was helpful GitHub is infinitesimally bigger It would replace about four services out of 20 or so collaboration services that we use Those four services though have 16 integration points that would have to be refactored 12 of them would absolutely be critical to kind of how we do our workflow So it's not a thing to take on lightly even though we'd love to do it and I think what we'll probably end up doing honestly is we'll end up coming with some sort of contrib interaction where you can more easily clone your contrib-based GitHub project and you can pull it into the Drupal.org repository so that we can have all the project browsing and Composer facade and everything else I think there's something there that's a nice middle ground compromise And then Ryan also has done some great presentations on the possibility of taking the way we do core and even some of the bigger contrib projects and moving it to like a more pull request-like workflow that matched the Drupal community a little bit more And those are some great ideas that I think we should still continue to explore But the race isn't over yet GitHub's big, I want their contributors I absolutely because of JavaScript and everything else I think it's going to be necessary but we're going to have to figure out a way to do it while still retaining some of what makes Drupal Drupal Absolutely Actually an interesting workaround from a training perspective that I think would be interesting for some mentors to do is when they're teaching people how to create patches Most people don't know this but for every pull request you create on GitHub there's a special hidden URL where you just add dot patch to it and you've got your patch file just upload that to Drupal.org and you've just fixed the process of them understanding how to create it There's some workarounds we can do in the meantime and I know they're workarounds and they're irritating and not as smooth but they're really necessary because of all these great tools we do have like Drupal CI now the composer in points all of the project browsing stuff are usage stats like all of these things depend on our Git repose and so whatever we come up with we're going to have to keep part of that there's no cost savings or like mind share savings of not spending the time thinking about it by moving over to GitHub because it's actually harder than what we have right now it's just not easy it's not it's definitely not easier to contribute to so we're trying to figure out that middle ground and that compromise What's that? I was going to let him talk but I was just going to mention that we came up with some ideas a while back for issue work spaces and just other priorities have pushed it off the road map and we're not sure where it lands yet but there is architecture and design for how we can improve it on Drupal at work if we don't do a wholesale move to GitHub or it's another option on the table it's something yeah I gave it he was wearing fancier clothes then come on I got big foot you were wearing plaid pants come on you might be surprised you might be surprised on page one of the marketplace right now there are no less than five companies that have fewer than ten people it's issue credits over it's really it's primarily comments if you do a patch or a comment if you're participating in the issue you have an opportunity for each issue to have one credit so you might have a larger company three people participating in an issue and three people will get credits but that larger company is only going to get one issue credit so that actually does help with the percentages based thing there is a skew to a couple companies that have just an incredible amount of resources that they're pushing towards it and that definitely keeps them in the top ten but if you're talking about the top 25 there's a company that I saw in the top 25 within the last six months that had three people it takes about 30 issue credits to show up on the first page now that may change as more people get used to it and start using it and whatnot I think the challenge then will be figure out ways to segment the marketplace so that people who are looking for a Drupal shop are picking the right size Drupal shop for their project and being able to identify that and that's more kind of UI around how we do that listing rather than what are the top contributors because if we start doing it by percentages we skew it in a different way and I just want to add it's difficult because a lot of larger companies will also like their front desk staff will sign up for an account on Drupal.org be a part of their be a part of their company and buy tickets for their employees for DrupalCon and that's their only activity but then it starts to be like percentage of whom you might end up with a lot of people who aren't going to be getting issue credits but they still have accounts on Drupal.org and maybe they're just reading documentation accounts or a company with a lot of juniors versus a lot of seniors so it's hard to figure out how do you percentage of which type of contributors yeah there's an issue on Drupal.org I'll add it to the slide deck so I can make sure that people can get to it so when we post our slides afterwards you can add that to the session you'll be able to see where that's at but there is an issue where I've kind of talked about all the different types of contribution that we know about whether or not we currently collect the information whether or not we currently display the information or whether or not it would be possible to display the information at some time and it's a huge list we're talking about 100 different contribution activities that you could be doing everything from contributing documentation to running a camp to being a sprint mentor to speaking at a camp, speaking at a con like all of these things there's a lot of really powerful contributions because if you're looking at Drupal 8 and getting it released it was the most important thing to do we're still in that phase right now with Drupal 8 module upgrades I don't think we're out of that phase yet but I think as we add more things to the profiles and we make a richer picture of contribution we're absolutely going to be looking for some of these edge cases that aren't really edge cases they're the stress cases that Sarah was talking about this morning they're the opportunity to really highlight the importance in the community and highlight people who are doing great things but frankly if we just have subjective information on their profile they're never going to show up anywhere we have to figure out a way to make that data objective and then we can truly show it and highlight them I just want to add one more thing I just find it fascinating when I see signs in places and it says drilling holes on lecterns is prohibited there must have been a lot of hole drilling for them to require that thank you everybody I can't think of a better way to end the presentation than that


Hey guys, welcome back to our channel. My name is Andrea with Food and Mentory Adventures in Food and I am here today with a very small Costco haul. I wanted to show you all what I picked up. This small amount of stuff cost me $149 and some change so let me jump right in. Grab some of these whole cashews for my husband. He loves these things and then I grabbed us some of the super extra large peanuts from Kirkland. These are the kind that are extra crunchy and we both like them a lot. Their Kleenex is on sale. Just the flat boxes, not the not the little cubes, but they were on sale for 450 off and I think these were $14 and some change. My husband wanted some avocados and you get six in here and they are huge. I can't even get my hand around them. I think they were $2.99 maybe? I think and then I grabbed us some of these ham and cheese pockets. I have bought these before and we both really like them a lot. You can pop them in the microwave but I prefer to pop mine in the air fryer and they are really good. It's like a flaky croissant and then there is Swiss and ham on the inside. It's absolutely delicious. I grabbed some broccoli florets and then I grabbed this salad kit for the first time. What I like about it is that it's a two pack so on the front you've got well on the front but you know on one side you've got to split. That's what I'm trying to say. It's split into two so you don't have to worry about it going bad when you open it. But you get cabbage, romaine, croutons, parmesan, asiago and romano cheese, kale and carrots with the creamy Italian dressing and it sounded pretty good to me. I needed some more shrimp and this was I think 20 bucks for two pounds of the raw Argentine red shrimp. Howard needed some vitamins and these were also on sale for 450 off and I don't remember how much they were and he also needed some vitamin D. I needed some heavy whipping cream and this was I think like way too much. Five dollars for the small thing of heavy whipping cream. My son Harrison has allergies so he has been getting this Zyrtec for as long as I can remember and he just turned three and then I also got some Zyrtec for Howard and I because we all have allergies. So this is everything that I picked up on my quick fill-in haul from Costco. I hope you all enjoyed it. If you did please give us a thumbs up and if you have not subscribed to our channel we'd certainly love to have you. Thanks so much for watching and we'll see you all next time.


We're covering 50 tech tips from the LSMTAP community here today. These tech tips were brought together mostly from the email listserv and from suggestions from the community. There is a handout in the GoToWebinar area that allows you to download the tech tips, and it has links to all of the different tech tips in there. A tech tip handout will be available in the follow-up email after this. It will be put on the LSMTAP blog, and it will be distributed to the email list. So a quick introduction. My name is Sarth Rao. I'm working with Northwest Justice Project on LSMTAP. This presentation is made possible by a grant from the Services Corporation to Northwest Justice Project. We're doing a series of different webinars this month, and casual roundtable discussions with the community, and we hope that you make it out to those. We've got the next three listed at the end of the presentation here. There we go. First and second tech tip is if you are looking for anything currently with regards to technology, definitely search for whatever the company is, plus COVID, and see if they have particular offers to the community. A lot of different tech companies have either decided to give away their products, extend trials, or make other offerings. Three of those are on this slide, which is Adobe Sign has added a 90-day trial for new users through May 31st. One password we're going to be talking about later, PandaDocs has a free option now available with unlimited signing and unlimited documents as part of that. It's the best deal that I've seen so far on electronic signatures. We are doing an entire webinar next week on electronic signatures. We are looking for individuals that have experience with different particular programs and are willing to join that to talk for about five minutes about what they do for electronic signatures or electronic scanning. It's been one of the two most popular topics people have been looking for in the community. First area that we're looking at here is video. Since many things have been moved to video, one of the biggest questions that we've gotten is what options are out there, especially on the secure or even open. Source side of things you did see is a completely open source, fully encrypted, free conferencing solution that is out there. It is very easy to set up a conference call or a video conference with many people. You head over to the website, you type in a meeting name, and it automatically gives you a dialing code, pin number, and the ability to add a password to it and be secure from there. I do have one minor warning with this, is that you want to use a unique room name, because when you type in a room name, if that room name happens to be tests, as I did the first time doing it, you're dropped into the test room. So double check to make sure there's no other participants in your room. Then add a password right away and then share that information with other individuals so that they can enter into that. If you would like it to be even more secure, you can host it yourself. There's a very easy tutorial over on GitHub. It is built on a Linux stack. It does not look that difficult to install. You definitely need an IT experienced person, but it takes the secure platform that they've already got put together. It puts it entirely in your control. The cost estimates that people have given me with regards to using this range from 20 to about $100 a month, depending on how often and how large you're using it. Although I wasn't anybody who's hosting it themselves, none of those cost estimates work from very small or very low use organizations. Articles that we found out there do say that you could host it for around $20 to $40 a month, depending on what your web program looks like. So hosting yourself is not free, but it does give you the added security that the video is no longer going through a third party in any way. Zoom has been in the news a lot with regards to security, and Zoom has done two major security updates in the last 10 days. The one that we're focusing on here is adding the security panel to Zoom. It's very user-friendly. It has the little shield icon down at the bottom. It allows you to control whether people can rename themselves, to lock the meeting, to enable a waiting room. Some of these features appeared to be only for the pro version earlier and have been added across the board. There are articles over on Zoom's website where they've been talking about the larger security issues that have come forward and they've made some changes on those. We will probably publish an article with some updates there, although this is moving so quickly. It's almost easier to check out some of the security professionals at Zoom's site directly. We've had a lot of discussion about this on the listsurf, both with concerns and then with the follow-ups. If you have any questions about Zoom, a lot of the community is using it, and the LSNTAP listsurf is a great place to get some more information about how individuals are using it. Discord, I'm bringing up another easy way to do audio chat. One of the features that I really like about it, besides the fact that it is free and very easy to add password controls, lock particular chat channels, is that they just added noise suppressant on April 10th, which helps cut out some of the background noise that's there. And a lot of individuals working from home do end up with some background noise, and mics themselves also, a lot of the time individuals do not have higher quality mics. So the sound quality with regards to their free chat has been improving significantly recently. The last one with regards to video, they've got here is much more on the casual side. It is Marco Polo. One of the important things not to lose sight of here is those social connections when we're all working remotely. Marco Polo is not a video chat. It is video messaging. You record a short message and send it over to someone else. It does have a very good reputation. It's extremely easy to use. If you're looking for a way to casually connect with friends that doesn't require their immediate attention, but still has the depth of video, Marco Polo is a very good app for doing that. Video capture has also been something that has come up a lot, especially when individuals are trying to do remote work and put together work processes or share them with a team. Loom is a Chrome plugin that is free for the Chrome plugin version and allows you to record your camera, record the screen, or record screen and camera along with microphone audio. It is extremely easy to use, very low weight, and has a wonderful price point of free. They do have a full version that is a desktop version that adds a bunch of other features, but if all you're trying to do is record your screen, audio, and camera, this is a great way to go about doing it. Number nine and 10 here is Open Broadcast Studio 2 Facebook. So this is screen capture plus webcam, or you can have multiple videos, and Facebook Live now supports having a feed stream go to it. So several different programs have been providing services, especially educational services via Facebook, and the best that I've seen out there definitely added more than just a talking head webcam. So they took the traditional slides or information that you're providing to the public and added with OBS, the resources, links, information, visuals, even court forms to show people. It really ups the production value at a cost of free on the software side. OBS is, I would put it at a two out of five for complicated. It's not very complicated at all to use about 30 minutes or so. You can set it up and there's some great walkthroughs online. The tip sheet includes a setting up OBS with Facebook Stream specific article to show you how to do that. I strongly recommend that for live streams. Our next topic area is collaboration. This is the area that we have the most overall suggestions for tools, although a lot of them were the same tool. There's definitely one tool that people really love in this current environment. The first tip that we've got here is Slack. And we're adding this partially because of the brand new integration that has shown up with a box. Box is an online storage and system similar to Dropbox or OneDrive. It has very good security features. It integrates with some of the case management systems in the private sector and is one of the best online ways to share files out there. Slack has just added integration. They've also upped their feature set recently of the free version, archives, 10,000 messages, your 10,000 most reach, your paid versions. Your archives increased significantly. I believe you've been to unlimited. But on the paid version, they've also added team voice and team video. So if you're looking for somewhere to track and keep things together, we're also providing that to video to voice at a low cost. Slack is definitely one of those options currently. And the integration with Box adds a very nice security with regards to file sharing. Number 13 here, this was the most suggested tip when we crowdsource these from the community. A large number of organizations are using Microsoft Teams. I think we can do a half hour or hour webinar on Microsoft Teams. Although other organizations have done those and we've got some links in the education materials to basic 101, 102 of Teams and the feature sets that are out there. This has many of the same similar features that Slack does, but integrates with your entire Microsoft environment, chat channels, and have the ability to cut down on the need for massive email. One of the most impressive things that I've seen about using Teams is the way that some people will move over to creating online conversations instead of mass emailing. The search functionality is much better and it has wonderful integration, creating those separate channels for chat, strongly recommended. And both with regards to Slack and Teams, I recommend having a water cooler, informal discussion chat area because that is another important way to keep people engaged and to provide a little bit of stress relief in this current time. On the project management side, Confod flow has come up more than once. It is a free, easy to use, agile kind of project management system that allows you to keep track of tasks. It has what you need to do, what you're working on currently, the progress and completion of it. You can assign tasks to individuals or to multiple people. There's comments with regards to each task. This is a very similar system to Trello, which was another one that was suggested, another very strong free project management system. There are advanced features beyond the free model, but the functionality of both Trello and Confod flow is very strong, very easy to use, does not require any tech background to set up. Excellent project management, very lightweight. On the more complicated project management side of things, there was the suggestion of Monday. Monday allows for many more options, setting up priority, time estimates, directly attaching files, and a little bit easier interface for looking at what's going on. Dividing your staff into different teams is also an option directly in Monday. It does have a deeper learning curve in Confod flow, but it has a significantly larger feature set as part of it. I've seen firms use this to create a different board for each case and then assign different case members or legal assistance, different pieces of that, and then use this for check-ins on a weekly stand-up meeting. Having those type of meetings where people can both view the online project management system and have video chat definitely helps with the engagement and ability for people to follow along as opposed to video only. Next section we're looking at is learning online. This is both for staff and then also for the public more generally. TechSoup, which hopefully everybody here is familiar with, has amazing resources online for discounts with regards to software, which most of us know about. Something that I was not aware of until it was suggested by the community is that they also have a non-profit response track in their educational area called TechSoup courses that includes about eight different courses for helping non-profits move online and doing remote work. It is all available for free to the public. Two of those modules is a Teams 101 and a Teams 102 tutorial that are part of it, which is super timely considering what we're talking about. Quality content, easy to follow, targeted really at the non-profit community. Definitely recommend always checking out TechSoup, but in particular the TechSoup courses which are available for free at this point and have a specific one for what we're going through currently. Pluralsight.com was one that was suggested by the community that I had not heard of. It is a website with about 7,000 plus of videos organized in how to courses. The content is extremely high quality, well produced. It covers a diameter of different areas, but there's many that are on the practical tech outreach, business, analytics side of things, type of trainings that they normally charge a significant amount for. They're free through April. For example, this UX strategy fundamentals course that I spent a little time looking at in the research was very well produced, very easy to follow. I strongly recommend checking it out if you're looking for high quality courses. It's nice that they are all vetted.  This is one of the classic suggestions that we're giving out here. TechLearning.com, although they go by TechEd Learning, is an old school classic blog that covers the intersection of technology and learning. These blog posts are short, simple to the point, less than 1500 words, very, very useful. In particular, the second that I logged on, I saw an article on how to teach for how paying free, the suggestions in it actually inspired some of the suggestions later on when we go to working from home technology, but just creating a workspace that is ergonomic and helpful in this time. They're just very, very practical. They've done a pretty good job also of categorizing and sharing some of the other free offerings that are out there with regards to technology and online technology and learning tools. The target audience for this website is definitely educators. It's not necessarily legal services, but there is a lot of useful stuff that comes out of this site that is generally applicable, and it's just very easy to read with solid use of visuals and play language throughout it. Next one here, I didn't know about it until last week when I attended an online meetup over family law. One of the firms that I've worked with had a physical meetup, and meetup has added features to put all of the meetups online within their event. You can make anything online as the location, and you can add a direct link to your registration or video conference, things for this. Meetup is still actively being used. I know several organizations have used it for outreach, especially if there's something that's done on a regular basis quarterly or annually. It is probably the second easiest way to provide events outside of Facebook events, but it is the easiest for reaching an online community that is different than a particular page's friends network, because people actively search there. I love their support of doing events online. They've made it easy. The family law that I attended last week was extremely popular. I'm attending another online meetup with regards to COVID and family law specific to Washington state this Thursday. Just, and it came to me through the meetup as a suggestion, so I definitely recommend this for reaching out to a different community that your Facebook page may already have or your social media. That section we're going to look at here is home office suggestion. This is one of the biggest areas that has shown up in informal or water cooler talks is how do you stay comfortable, take care of your health, and put together a good work environment. One of the biggest suggestions, and I went out and fixed this after my first week at home, is finding a chair that is comfortable, something that has armrests, the height's adjustable so that you can get proper post-sharing keyboard, back support depending on your back. The one suggestion that's that almost everyone had that I talked to that is difficult in this period is to try to tear out if possible. The exchange policies are very good for online sites currently. Some of these stores most don't let you come in in very small numbers and check them out in that order and I have one set directly, but it will make a huge difference in your work life. Individuals I know who have picked up chairs recently normally been spending about the 75 to 225 range. You can spend as much as you want on something like this, but they return on investment for one's health. It is worth finding something that you are comfortable in during this time period. Another suggestion, this one came off of the LSN Teflis directly, what is considered noise cancelling headphones, especially if you're working in a louder environment. It will help you a lot with focus. Noise cancelling headphones typically run about $60 to about 400. The biggest difference is the sound quality of the audio and I have definitely used some of the less expensive, the middle ones there are a Sennheiser that is about $70. The noise cancelling is great and the music sound is actually pretty good for the price. It is not a high base, high audio file, even though it is from Sennheiser, but it is high quality and works in that functional way. I've heard very good things about Apple beats noise cancelling, also which are around about $10 to $1.20. The more time you're spending on online conferences, the more that I definitely recommend looking into these and I appreciate the suggestion from the listener. I never thought that I would suggest buying a home shutter to anyone and we've got several law offices here in Washington state that still practice in areas where you are printing and mailing in. Electronic filing is not everywhere. Fortunately a lot of courts are looking at electronic filing right now but as I've got remote interns and staff getting someone age better so that they can't destroy things that they printed out that they're planning on mailing in is worth considering. I had some bad experiences with those that are at the six to eight sheet range. The ten sheet has worked really well. I hope that we move to an area where electronic filing is always an option and we don't need to make this type of a suggestion in the future but many counties still have mail-in as a primary filing or difficult electronic filing systems. The next suggestion here is a docking station. If you're using a laptop in your home environment, laptop keyboards can tend to be a little small, less comfortable. A docking station often provides you with extra ports for USB in case you need an external keyboard, an external mouse. They often let you hook up to a larger video or use your laptop with dual screens. Some laptops have very limited storage. There's two ways to deal with one is off-site storage which I definitely recommend on a firm level but this could be a way to also do personal storage for extra items that are there. Ethernet port. Many laptops do not have direct ethernet ports anymore and an ethernet port can be put through a docking station and then the power to support everything is running off of it. The cost range on these ranges from $50-$60 to as much as you want to pay to get it really about the features that you need. Do you need that extra USB with a second monitor to be useful? The storage, second monitor, or higher quality monitors are some of the more expensive features. The basic ones will definitely work for just getting those extra ports and creating a more usable workspace also. One of the most entertaining suggestions that we got from the elicent app email list service was phone books. I had no idea what they're talking about. I followed up and what they were really talking about was foot rests. They also recommended old law school books as something to make sure that your feet are at a level straight place and that you're comfortable. Adjustable foot rests do cost a little more than free phone books but are much easier to use and cost a lot less than legal textbooks from law school. Make sure that you've got an IT procedure in place that encourages or requires individuals if they're using personal devices at home to create a work specific profile. If the computer is shared by others, this just segregates most of the items that they would have access to in the tip sheet. We've got a how to set up second accounts on Windows and on Mac. In both cases, it takes about three minutes and no tech experiences needed but just having that segregation for files and with a lockout when you walk away, especially if you're in a shared space with roommates or other family members, it just helps protect the confidentiality and security for the individuals that you're serving. One of the more practical suggestions that we got was the written doorbell. Working from home, I've definitely experienced, especially since I live in a house with several different people. The number of deliveries that we get is very large. The doorbell rings often realizing if it's a package being dropped off or if you can continue to just work and not worry about it. It's very, very useful. This was mentioned at the beginning and is well worth checking out. They have removed their trial limits. It's a password management program that is very popular. It is used across many different platforms. They securely store your passwords on their server and the key for encryption is stored on your device. They have a master password that is used for accessing the plug-in and getting access to all your passwords. Most importantly, they've got team sharing options that allow you to easily share passwords. One password I checked out this last week after it was suggested by someone on the list. It is easy to use and I was happy using it. For signatures, we're doing an entire webinar on scanning and digital signatures next week, which is why we don't have a huge number of suggestions here. This is one that came up as a question from last week's webinar. Someone wanted us to look into the security background of it with regards to some new rules that were being passed in Oregon state. What I liked about this particular sign program was it was the fastest and easiest to sign your first document. The sign-up procedure basically walks you through your first document that you're signing and they do 10 free signatures per month. Their $7 option has unlimited documents. This is nowhere near as feature-rich as DocuSign or some of the other leaders in the industry, but it is extremely easy to use and extremely well priced for online documents. They've got a whole page relating to their compliance with GDPR rules and how they treat your client information. I would definitely check that out and whatever your state local rules are. The Oregon rule was very interesting in that it was very broad and it allowed you to add a process that verifies that that signature was actually made by the right person. If you emailed out a link, they sent it back. There's some concern that that email could have been intercepted or somebody else could have signed it. The Oregon rule added that if you do a check-in with the person to verify that they signed it, that would count for authentication. Each jurisdiction has different rules around e-signatures. I'm still aware of one jurisdiction that requires a separate rules declaration for it, but most of the jurisdictions are looking at ways to make e-signatures easier and cutting down on some of the barriers of access there while still providing authenticity specifically. The next one that we've got here, this piece of technology, RingCentral could have been in many different sections. Several people recommended this from the LSF tab listserv. If you have larger questions about RingCentral, definitely feel free to email me or get on the listserv and ask about it. The reason that we're putting this in this area is that RingCentral has great internal fax features. Another question then has come up several times on the listserv in the last two weeks has been what are people using at a discussion over e-faxes? RingCentral has that built in. They do have a longer trial period that has been created with regards to COVID-19, and specifically they have an NPO page that includes some consulting to get things set up as part of that free offering. So if you've been considering RingCentral it is definitely worth checking out and there are lots of people in the community that can help you out. For individuals that don't want to put together an entire communication system and they need to do a few hundred faxes, at most red fax is a very easy to use lightweight online fax system that uses their service to take your documents and send it to the destination or to take the documents that are coming in and send them to your email. I tried setting it up and it was very easy to set up the cost point. I believe it was 500 documents or so for about $5 a month. Initially, so for lower volume this is an easy way to deal with just a few faxes a month from an external perspective instead of a larger communication tool. A quick break here for some suggestions with regards to staying sane during this time period. Two books that I strongly recommend since we're spending so much time on our computers and so much time on our phones are The Attention Merchants, The Epic Scramble to Get Inside Our Heads by Tim Wu, NYU professor. It explains a lot of the psychology and economics behind how cell phones are grabbing our attention and using random reward schedules and psychology to create this co-dependence. As all of us are moving to a more digital environment at this time it's a very good read and on the more practical side of dealing with technology and the innovative with technology is Cal Newport's Digital Minimalism. It sounds a little odd in this time period when everything is going online but it has wonderful suggestions about thinking about your use of technology and a strategic manner and choosing which tools take up your time. His idea of a short term, courage and then re-introduction is not possible at this current time period given how much work related stuff we have to do through technology but he very consciously talks about your choices and making sure that you find time that is outside of that digital space that's trying to grab your attention. One of the reasons that we added those two books was this wonderful suggestion that came from the Aliccer called Daywise that allows you to control your notifications. One of the things that cell phones are really bad at because it doesn't help them grab your attention is allowing you to control your notifications. I often spend time trying to hunt down a single setting to get one thing changed on my phone to get back by time and Daywise does a wonderful job of shutting down those alerts and those noises and allowing you to filter instead of just shutting everything off you can choose some messages to have a high level of importance to them and you can choose other messages that it saves the notifications until after or it saves the notifications until 8 a.m. the next morning because you are at off time and those are non-emergency work related. I highly recommend checking it out so that you can take more control over your time in this extremely online digital age. Our next suggestions are a little more on the techie side. The eval lists serve and the community ranges from individuals who have a little bit of interest in technology to those that are IT professionals. Next few suggestions are a little more on the IT professional side. Having a system that allows you to take over remote users computers while doing IT support is absolutely essential in this current time period. We've got two different suggestions that came from the listserv. First is connect wise remote control for your user's computer. There is a free version for one user that is easy to use. The full version is $19 a month. It is just very, very useful when troubleshooting computers. They have a lot more extra features on there and it's a much broader program but it is rather easy to use from a technologist's perspective. The additional suggestion that we've got here is remote access through Splashtop. Another easy to use multiple different devices easy to set up for remote access. We'll have links to both of those in the tip sheet document. Check them out and compare them if you're looking for a way to do IT remotely more efficiently. In the same category we've got an education system which is Microsoft Learn which is entirely free. Any of the technologies you're looking at to set up or if you just want to improve your skills and work on certificates, those are there. They range from getting started using something like Power BI which is applicable to a larger non-tech community, individuals that are doing business analytics. It's a great tool. Most of their tutorials are a little more advanced. They're targeted at techies which is why it ended up in the IT section. Any of their what is series or their beginner is useful for anybody using a new product. What is Microsoft 365 is only 11 minutes and it gives a nice introduction. If you're moving from Microsoft on-premise in this time period to Microsoft 365 definitely recommend checking it out and taking ideas or tips from it and adding it to staff. One of the more techie suggestions that we got was Microsoft Direct Access. Direct access to put it in simple terms is basically a leveled up easier to use virtual private network. But instead of connecting to a single user you connect to an authenticated machine so that it is always on and it is what they call a seedless but I would say more behind the seeds less in the way of the user. It's for domain joined Windows clients. The setup of it is very easy and it's free with Windows server. So if you're looking for an enterprise wide alternative to VPNs and you're in a Windows environment I've heard at least two very good reviews from the community and looking through and researching this tip. The community is very supportive of it. They're very very positive reviews. Another thing, another area where you can get help off the listserv if this is the direction that you decide to go. So our next area here is security and backups. On the security side there's been about a $50 million investment recently and single from one of the founders of WhatsApp of all things. And I believe a non-profit that he has but part of that investment is improving the security which it's already one of if not Vivo secure messaging platform out there. But they're also spending some time improving usability to make it easier for people to use and more readily adoptable by a larger population. Signal started out being extremely secure but not very usable or very aesthetic. The aesthetics and the usability are definitely improving. It is a product that puts privacy first and foremost at the beginning. They have voice and video calls. They have the ability to send disappearing messages and they have solid approved chat features. Highly recommend checking it out and it is definitely improving on the usability and the security has always been is still top notch. Recommend strongly having an antivirus. Sophos Home is free, has been and is easy to use. I would recommend an antivirus on an enterprise level also that will be covered in our security webinar coming up in May. But make sure if using home devices definitely have an antivirus that is available as part of your checklist. Part of the goal of putting together these tech tips for this webinar is that it should cover broadly most of the major things you need to think about for working remotely and doing legal services remotely. You can use it as a bit of a checklist. Do I have these things? Do I not? Which is why we also included the antivirus even though it is a very basic tip there. A backup system that allows for external backup. Carbonite has been strongly suggested by members of the community and used by organizations. The biggest tip that I have here is test your backup systems. I cannot tell you the number of times that the cost of recovery has skyrocketed because the backup system didn't work correctly or it took a few days to get going or they had to do data recovery with the backup system. Had that happened sadly more than once in the community with clients that I've worked with through LSM TAP. So during this time I know that there's a press on our resources because the mean is growing significantly but carve out a weekend and test some backup systems that you haven't placed or implement a new backup system given a month and then test it. This is going to save you a lot of pain and suffering later when things crash or if you get hit by ramps somewhere or a virus hits having that backup is essential. With regards to backing up your cell phones this question has come up a lot. Gcloud has a free option that is the backup up to 10 gigabytes and lets you choose what to backup. It is very easy to use. It is not by Google. Although when I searched for it on Google a Google ad for Google was the first search result. It was the second link. I'm going to try on my cell phone and very easy to use. 10 gigs does not sound like a lot for your phone but if you exclude your photos and your music it should cover all of your documents all of your essential items there. So choosing what you backup is important when using a tool like this. A practical tip. More than one person who has taken our suggestions of using a strong password system and a password manager have lost their master password and lost access to all of their passwords. This is an old paper system suggested take your master password write it down on a piece of paper put it somewhere nowhere near your desk put it in your closet with photos don't mark what it is just have it there and know where it is. I actually took and took that one password and shared it with or put it somewhere secure and then shared that location of where it was secure with someone else in case I forgot that location it's just essential to know now where I put that was locked up so someone could just get into it but as long as it's away from your computer and not easily found it is more secure at that point password managers are amazing losing your your master password is the absolute worst which is why I've got another suggestion to help with this problem is generate one time passwords that will let you do a recovery or re-inter the system last pass which is one of my favorite password systems will let you generate three one time strong passwords and with that they can only be used to lock in once it notifies you when they are used I take one of them hide it is your location and then I'm taken a trusted calling and said hey if I ever need this you've got it but then I know if it's been used it's not like giving them your actual master password because you get notified and it can only be used once but it is essential for recovery for these disposable passwords the next group of suggestions before I move into suggestions from the community here is how and ways to improve getting the word out to the community during this time period the trans sense legal icon project I strongly recommend the individuals checking out they are free to use under creative comments by non-commercial not derivative license which basically means you can use them as long as you give the creator credit and you don't change them the idea is to have standard visually intuitive icons for the legal world these are very easy to use strongly recommend them for videos and for print publications that you're creating putting on your website also the second thing is if you create a video during this time period to help people out with regards to COVID I've seen a lot of visual programs doing this put those videos up on YouTube don't just take the Zoom meeting video or a plain video and throw it up on your website you will get 10 times more hits by putting them up on YouTube even if you don't currently have a YouTube channel in North West Justice Project I did a do I still have to pay my rent video that came out a week ago it already has 936 views much higher than their average for one week and larger than their subscriber count it is being shared and other people are viewing it I know someone else in the community that created a similar video that was specific to a smaller geographic or to a different geographic region not smaller a different state just put it up on their website they've gotten almost no views at this point you need to go to where the community is and share those awesome new resources you're creating with the community more broadly this is an older suggestion that people asked for specifically some easier suggestions for getting started with new technology the quick start guide in the Creator Academy is great it will get you the basics of a YouTube channel set up in less than an hour short easy to use videos all of these first materials are free strongly recommend checking them out they're not aimed at a nonprofit community specifically but they do have great practical tips on the marketing and outreach side and just set up overall the last suggestion that I'm putting forward or actually these all come from the community is Unsflash for coming up with amazing images for sharing the Unsflash images do not require attribution but I strongly encourage you to attribute the quality of the images is just amazing it is a curated site with beautiful images that can be shared used on your social media it looks a lot like a museum collection or a well curated stock photo site the quality just adds a lot to presentations so now that we went through 47 tech tips in 58 minutes we've still got a little bit a little bit of time here please type into the question box or raise your hand we would love to hear any other suggestions did get three more tips from the community first group me for group text messaging a nice informal way to connect with staff or to put together groups of individuals that want to knowledge share via text messaging second we've got scan bot for a phone scanner that is mac and android we've also got phillips speech live for voice to text with human review or automated the human review aspect is extremely nice for editing work product thank you to everybody on the lsn tapped email list this was these were great suggestions from the community and this could not have been put together without all of your suggestions thank you so much


Let's go over to our man Mr. Teddy cakes that and Teddy folks can be found every trading day at Forex That's trading desk on lock.com. That's Forex that's trading dash unlock.com. Teddy cakes that what's happening, brother? New year's looking forward to seeing how the dollar settles today. Yeah me too. I like it. The dollar's getting destroyed sell it maybe sell it So we need your advice Teddy tell us what's going on I just said to Tommy a little bit. I thought you I thought we were talking about that's on Thursday But I know you're gonna be doing a show on Thursday, which is just fabulous. Okay You're gonna he's gonna be two to three Eastern stand-to-time folks. Teddy's gonna do Dave White show. So we really appreciate that man Hey, we finally get some movement in the dollar, right? So just where do you want to start? Well, I'll tell you what the dollar index is exactly where I want to start cool, you know back in October We were looking we got that one-cell signal and then we had a little bit of a Retracement the dollar seemed to have some strength in November, but December we didn't get a Christmas gift for the US dollar Didn't we know no we didn't and they know I don't think that the market's gonna turn around too much today I don't really can't see a big rally. I mean anything can happen, right? That's gonna happen today So but I'm actually negative the dollar and not too extreme But I can see that the next three to six months maybe even 12 months that the dollar is gonna be under pressure So and I think that that's gonna give a nice little bit of a lift to the Euro a little bit, but not too much I think that's gonna be very oil related. Okay. I think the pound is definitely gonna have a chance at exploding to the upside When you say that the Euro would be oil related. How does that work? Okay Well, if you've noticed that obviously over the course of 2019 oil has had a big rally Yes, hey now the Euro The US dollar is considered the petro dollar globally, okay? Decades but over the past literally 10 years and especially over the last five years You have more and more where the Euro is becoming a petro dollar. Okay for ever reasons whether it's you know Even the Chinese when they buy oil or in other countries. They're not using US dollars. Yeah, so that's a demand for the Euro So now we have the today was really interesting was watching some of the broader indexes where we're at on the year I mean everyone's looking at the US growth being like wow 30% growth. This is amazing. You know, it can't happen again next year Whenever we don't know about what's gonna happen But there's been a very interesting lift in both Europe and in China for the broad-based index for their economies They're up over 20% this year. Yeah, that's it. I was looking at Shanghai Shanghai looks like it's gonna bust top-side the big way Man, I did the not last night the night before man that the that's getting up to the top of the consolidation Yeah, right now. This is all now gentlemen. This is all in the wake of trade wars, too How is it that China is up? 23% over this year in the wake of all these tariff blah blah blah Yeah, and everyone for a year has been saying doom and gloom. It's gonna crush our economy It's gonna crush the Chinese economy and the net result of all this stuff is that Asia's booming China is actually doing well in the wake of this tariff stuff, you know And Europe for some reason too, which they've been screaming recessions for a long time now not necessarily Germany Germany has its issues, but the European Union as a whole even in the midst of Brexit and not Knowing any clarity on what's gonna happen with trade. They're up 20 some percent on the year, right? No, no, there's no doubt man. There's no doubt, you know The these currencies I know we talked about this before but it's pretty amazing like To me that you know the dollar has broken this uptrend that we've been in since February of 2018 I mean that that's 22 months That's that's pretty intense, man And you know we'll we'll see you know if bottom line if it wants to go to the bottom of the trend That would be really intriguing and I and I you know Folks when Teddy was just talking about Europe going higher now This is what does happen if you're thinking about the old our own S&P If the dollar goes lower our S&P can actually go higher on price It doesn't mean that you buy more because it's priced in US dollars. Okay, which gets really intriguing doesn't it Teddy? Do you know what I mean? It's like okay Yeah, so it's intriguing how this works because I was looking at the gold contract yesterday and The gold contract it's only in US dollars that we really haven't broken highs I mean the euro broke the high the The Australian dollar made me forget it's it's way higher You know and so that's intriguing in itself that it's a US dollar itself that hasn't been able to break that is that 2011 high Right. Well now it's funny. You just mentioned the Australian dollar and gold now what let's just say Hypothetically right that right now the economic engine globally just continues on pace for the next three to six months Yes, the Australian dollar if you look at I was looking at the monthly charts before I came on with you guys Yeah, see, you know how things are really shaping up now the Asian trade zone because the tariff wars Which we just talked about had definitely been suffering for a little bit especially Australia because we noticed in 2008 and just like over the past year how they have all their eggs in one basket Okay, but now that we see that China is actually not doing as bad and Australia is starting to spread out their commodities are moving again. So we start to see a spike in the CRB You know, that's gonna start to really accelerate things for the Australian dollar I think you know because right now it looks like they have a really good chance of getting it I mean they're in a rally right now That's evident But I think that you can actually see this momentum Continue and also in that trade zone because it's not gonna come out of the yen It's gonna come out of the New Zealand dollars to come on an Australian dollar and definitely your minor crosses that no one really looks at in Asia You know because the trends got different factors Yeah, no, it's a big deal and what Teddy's talking about folks is Australia is a commodity country So the bottom line is that when commodities take off this takes off like a rocket ship, man There's no doubt and in fact, you know, Teddy what was interesting is that in 2011 when gold was hitting highs Folks had a high time understanding why the Canadian companies Basically still weren't doing that well meaning the gold companies and it had to do with folks is that the Canadian dollar got so strong That's you know, that's the other part of the equation, which you know Did the lead up to the next thing about with this whole commodity thing with mention in Canada If you look at the US dollar Canada, yes It's tanking right now and that's because of the commodity strength And like I said, this is kind of a ripple effect by these different countries where the US dollar the There's milder currency crosses like the Canada and the Australian and New Zealand. They're becoming big bulls Yeah, and if you look at the US dollar Swiss on it's been trading basically between Parity of 04 down to about 98 cents for the past like few years Okay, that's like year and a half two years right and now it's slamming down to this 97 cent area It could be down like literally 92 to 87 cents within the next like eight months to 12 months at the dollar index It's a it's a really big slide It's pretty cool man because that's a lot of opportunity out there for trains I mean, you know when you when you had big turns in the marketplace, right? I mean the bottom line is that it's it's It's not necessarily the very beginning of that You like to trade them, but the fact is that That's where the biggest chunk is that you know if in fact, this is a big turn, which I think it is You can see all those different trades lining up man. I mean, it's like, okay, you know We know that in a bull market you can make mistakes, right? I think you're we're hitting a very big cyclical turn for a lot of markets. Yeah whole sack You know pretty cool, man Well, listen Tommy and I wish you a happy new year great 2020 We look forward to the show on Thursday. So Thursday right here folks. I'm in Teddy cakes that he's gonna be on two to three Right before me. Teddy have a great one. I say for my man. Absolutely. Thank you. Thanks, Teddy. Happy new year