Okay. Umar, the live stream is up. Yes. So just change the screen. And I'll be on the line tomorrow, but feel free. I mean, you know, speak in French as much as you like. If you need anything, just ping me. And I'll, you know, I'll be here. We effective. Thank you, David. This meter will be in French. Okay, so I'm going to let us I think. We'll have a little pain in the search. Okay, so the live stream. Um, so I'm going to have this. How am I going to say that? It's a meet-up to start a little bit the activities concerning the tradition and the activities of Hyperledger Francophonie, to start all these activities concerning the French language, whether it's about the tradition, whether it's, I don't know, well, the translation of the document or the translation of the website properly said, because the city-hyperledger.org also, at the moment, maybe it's interesting to be able to translate it. So it's in that sense that I launched this initiative. So here I am with some people with whom I launched the initiative, Hyperledger Francophonie, especially Gilles, Gilles Gravier, who is one of the first to take part in this initiative and who supports me since then. I also have the support of my brother, Ido, I.D., rather, who is a French-speaking Englishman, but who used to be there to explain this to me. So hello, I.D., how are you? OK, so I'm just preparing a few slides quite quickly, well, it's not really a slide, it's just that it's going to be more in-house format than in-house format. So I just have to find the link to share on the screen. David? Yes? I'd like to share my screen. You should have access. Is it letting you? Access to some security measures. OK, OK, got it. I'll share the screen. OK, that's that. Yes, so the first thing is just to welcome you guys to this. Ah, pardon. I wish you all the best. And that's what I'm going to say here. And so as I was saying, the communication methods are quite basic. So what you need to know is to use the documents, the logistical documents, whether it's Microsoft Word or LibreOfficeWriter or Google Doc, these are things that more or less everyone can do. The other thing is to have a good level in French, because that's what you need to do. You need to do documentation, but you also need to do something that is of quality. But I think that for most of the people who are there, these prerequisites are here. So I didn't put the other prerequisites, which might be to say that you need to be bilingual, because it's not quite true. And we don't have to speak English to help translate. So I'm explaining myself. Sure, you need to be able to start translating, but there are several mechanisms that we'll see later on, automatic translation. So that's what I call the first steps. So the first step will be an automatic translation by a mechanical machine. And the second step will be a re-selection by human beings or by people who master the Francophone language and who will be able to detect all these errors generated from context, often generated by automated tools, because they don't have the finesse that humans have. So we really don't have to be bilingual to be able to participate in the translation of the documentation. So there are no two points. The two points are to use it in the logistical of text and to have a fairly good level of French, whether it's an orthographic or a grammar. The other thing I wanted to show you is this page that we created in September 2020 with Gilles. So it's a page in the Wiki of the French documentation. And so on that, I'm just going to share the screen so we can see how it's going. So here it is on this page of the Working Group. So as you can see, I put it online by adding the links that I'm going to use throughout this meeting. So the links serve a little bit on the documents that are in English, but that give the steps to be able to start this process of documentation. So I've already opened them here. So it's not worth clicking on it. Maybe David, you can share the link or maybe I can do it somewhere down here. Oh yeah, when you're sharing your screen, the interface goes away. Yeah, if you click at the top, you should be able to see an option. But I can drop for the documentation working group. Yes, just a little discussion. Yeah, I got it. So the link is here. If you want, you can click on it and see at the same time as me. I had already started with an EPAC on the Translucent Initiative, but we haven't been very far. So here are the pages that we're interested in. It's very, very well documented, the translation. So there is a page of the introduction that is here. So the link is here. The links are there, so if you want to see them at the same time as me. So it explains a little bit how the file structure is decomposed. So the structure is here on the hyperledger link, FabricDocAitinen. So this is a notation for internationalization. So here we are on the local doc, which is the FabricDoc source. So here we have the different translations of existing documentation which are the Japanese, the Russian, the Portuguese, etc. So here it's up to us now to do, so that we have the FR underscore FR here to start our activities. So here we learn that the most important files in the source, they are in the source, and that's all that concerns how to create channels, etc., etc., the different elements. So here is the documentation to translate, and it's quite simple. And there are also parties to build, to build this documentation in local to be able to see live the translation that we are doing, how it will be presented on what will be the online version, definitive and accessible for everyone. So on this part here, which gives us the initial process, create a new workgroup, we did that, which is here. So you can, if you already have it, you can edit the wiki and add your name here, it would be nice. To get to what we can, to get to what we can, to have a beginning, a micro community to start and then in the end, to try to enlarge it. So on the first, create a workgroup, it's done. Then there is Hyperledger disposed of a chat, a big chat, which is, well, on Rocket Chat. And on this chat, there is, no, so I just opened it, there is a channel, a channel called Internationalization or Aetinen. So on this channel, we have a lot of messages and eventually we can discuss the elements of tradition. We can also see what the others do and ask for advice. At least that's what I do with some other people who are in the tradition of other languages. I often ask them how to do such or such things. And that's, that helps a lot. In any case, for the beginning, it really helps a lot. Then, then you have to really put yourself, that is to say, make a fork of the documentation against Github. Once again, you don't have to, on the priorities that I mentioned earlier, it's not the point of being, we don't need to have a technical profile. So everything that is Github is accompanied, if you don't master it, it's not absolutely necessary. I'll explain why, in order to participate earlier without having a technical baggage. So that's for the people who really want to do the tradition from scratch, apart from their machines that are quite technical oriented. So there are the elements of committee, of push, of push, of fork, so they are quite good. So there you go. Once we have put this environment on our machine, we will have to start somewhere, the real work of the tradition. So there are also the first topics, that is to say, the first elements that will necessarily have to be translated before our French language is visible here. Before the French language is visible here, because it is useless to display a French language or a tradition, whereas there is not even the minimum, the minimum being the welcome page, because there you go, the welcome page. It has to be translated, otherwise it's useless. Then there is the introduction page of the initiative and the factory. Then there is the page that explains how to contribute, because that's what we have here. It's to contribute, to give back what the open source gives us, to share what we have at least, what we know how to do. Then there is the glossary, which is also important, because there are many people who help to have a point of view, to know what a smart contract is, to have successfully entered the documentation, the real big documentation, there are people who want to know what the consensus is, so all of this, the glossary allows us, as the name indicates, to detail these elements a little bit. Once we have these four basic elements, we can ask what our language can already be validated and displayed on the real document, the online documentation and the hyperlogical address of Doc Ayo factory. From there, we are very successful. We have arrived a little, we have put our first stone, so from there, we can firmly click here and say that I have brought my stone. Then the other thing is the translation tools. We have tools that allow us, I was talking about mechanical translation, so we have Doc Translator and Textra that are there. So I'll show you a little bit how it goes, which helps to make the first step, an automated translation, because we will not translate it very much. And from there, we are live, and we can attack the topics or the subjects that are suggested here. So also the other important thing that I wanted to emphasize is that we are going to start with the release 2.0, well, 2.2 of the factory. Why 2.2? Because currently, with version 1.4, version 2.2 is the stable version, the long-term version supports. That is to say that it is the long-term version in French. And on this version, the 1.4 and the 2.2, on which the hyperledger factory for developers and for network administrators, network administrator, hyperledger factory and hyperledger factory developers. So it is better to attack these documentation knowing that this is what people will most consult. People who, like me, want to try to have these certifications, they will really base on the LTS, because the LTS, as the name suggests, does not change very often. So the documentation, too. It is stable and fixed. And from this base, we can elaborate on version 3, well, 2.3, 2.4, etc. So that's what I had as an introduction. I don't know if Gilles, you have anything you would like to add or if there are any questions before I attack on the demonstration part? Yes, I will make a comment, Omar, not so much on the method, but on the ideas behind it. Contributing to an open source project, it is not just code, indeed. And many people start their contribution to the open source project by translating the documentation. The advantage of the documentation, as this is the case here, is that we really don't need to be technical. As Omar said, it is enough to be able to use a text or a text editor, and then it's good. While there is another aspect of the translation that is not bad, it is to translate user interfaces, which is also done with text editors. It's not much more complicated, but that makes sense. It's less important for a project like Hyperledger Fabric, which is on a server and for which the user interface is generally quite restricted. It's super critical, for example, for a product like LibreOffice, but what we propose here is really something that will rely on elements that are not very technical. You have to understand a little what we are talking about. But you don't need to be a programmer. That's it. Anyone can do it. Very good. That's exactly what I said. So it doesn't really matter. You don't need to be bilingual, you don't need to be a technician, you don't need to be a NAS. That's it. And then, from there, I can... Is there already questions on... No? Okay. So I'm moving on the approach that I would like to propose here. So I would like that once we have a small group of volunteers, it can be two or three people, we have to start somewhere, that we can take an hour a week to meet and start a translation. So starting a translation is quite simple for me. So once we have created the workgroup and all that, we can come here. They are open to start. That's it. So first topic. So with the tools explained here. So we have DocTranslator and TextExtra. So I tested these two automatic translation types. So I'm just going to start this translation of the approach page. No, not in Chinese. I'm going to take the English version. That's it. So the English version in 2.2. And from there, I have two choices. So this first tool is DocTranslator. And the second is TextExtra. So it's a Japanese tool. They have an English version necessarily for a translation tool. That's it. Then I connect. So quite simply I come here. I type on the introduction page. So I can copy all the text that is there. I just copy it here. English, any language, English, French. So from there, I just have to do a little bit of networking because since I copied everything there may be some small elements. There are especially the images that are copied in text format. The links especially of the images. So that's the title. That's a list but we'll see that later. The night is coming. So English for French, we launch the translation. I think it's translated maybe by little. So there I don't know what's going on. There you go. It's translated by little. I don't know why. That's how it works. So there we have a parallel between the English version and the French version. So there we can see that the translation is pretty good. I find myself on what I tested. So a block chain is an immediate translation book without distributed networks so apart from the translation here this is what I call the first step. So we can copy this translation and paste it in a Google Doc not now. So really very quickly there is work that we can do here at this level on certain elements. We can suggest better translations of the group. As I propose, one hour per week where we regroup we can regroup for all on the same document and from there one takes the end the other takes the end it starts at the top the other at the bottom doesn't matter. And we correct it. Here it's more of a collection but a block register for example it's a good French word for example it's a Google suggestion which is false for me for me the translation here is the good term we classify it. These are the things you need to see So there are things for example, what do we do in English? Anti-money laundering anti-blanching of money do we keep them as they are in English or do we translate them in French? These are questions to know the notions of KYC which are also elements of what we do on these elements of course there are some small mistakes So the translation is really something that allows us to have a lot of documents on which we work and once we are satisfied with the results, we export them and we move on to the technical part of insertion inside the original documentation So it's fast There is also this doc translator that we can also try So on the other hand, we can't copy and paste directly we need to create a text file or something else, PDF or whatever but we will have to file it I don't know, maybe it's me who can't find the button to paste but I didn't see a place where we can paste So we just test 3DF So we put it there we register So from there we load a file So as you can see it uses Google Translate which is a little less accurate than the Japanese one to take the document translated in general we also have a starting element to copy it in a shared document to be able to work all on it in parallel So this is the first part which is the translation of Mechanic and after that we will have to re-read it until then do you see everything well for everyone? No questions? So in this case I will go to once we have a raw translation a little re-read, correct and clean for example smart contracts and a chapter obviously we will have to respect the original form but this is not very complicated So once we are there on I have to connect So there I am on the global documentation So there we are on the release 2.2, you have to check that So the first thing we do is we clone this deposit So I clone it under my name and there I have my repo my personalized code of Deeperledger So the second step we are really on the technical part but we can collaborate on Google Doc and someone who has a technical profile can do everything that is integration in the main repo of Deeperledgerfabric So there I will clone my own deposit which is something quite simple but first I have to do one or two operations so I activate my key here then So I clone my deposit and from there the only thing we have to do is to come here and start reading the code So I go inside and everything is already very well written then then so we are on the 2.2 branch so we create our own branch we will say initialization so I am on the initialization so there we say we have to know which language we are so we are quite simple French from France not from Quebec after we have to start once again so code honor we are already we will see what is on your trick and so we say to add this line to the code so we have to do that and modify the extension of the language so there we are on the FRFR and maintainer FRFR so quite simply but it is things that we have done only once, that is to say that once for example I do it and I put it online you no longer need to do it the the FR language is added we will just add what we will add in addition to the translations not the basic elements so there so if we put a if we put a disc on this file we will see that we have added the language in any case we said that we will add in the local file the FRFR file to sign a new translation from there we also have a new file called DocMaintainer which will regroup all the people who participate in the translation so that's maybe some elements of the knowledge that can be very interesting to show your involvement in this open source movement in the give back as we say in French and so that's the first part so I'm not going to do everything from beginning to end because I already tested it so I'm just going to cheat a little and copy it's behind and copy the elements that I already created so I already created a FRFR file I copied it in local doc and so what gives rather a vision of what we have so we added the FRFR file which actually contains it's not very complicated I just copied the content of the English file because it's the language of reference so I copied English to French but all the content in any case it still remains of the English elements you have to go again and once the base the elements of the base are put in place then we're going to replace as the translations so we're going to arrive like that then we have a suggestion to copy the Brazilian Portuguese to the Spanish-Mexican for example the customized personalized the rhythm to specify to specify to specify what it does etc so here we are so I already did that so the French translation project the perimeter of the initial commuter so here I put my name and obviously we're going to have something that will increase Gilles I can add you you're in mute so I was saying don't hesitate okay cool so I'm going to add your name so if it's just Gilles it's Gilles.Gravier.Weepro.com if you want my mail weepro or it's Gilles.Gravier.org okay the one that corresponds to my github Gilles.Gravier.org perfect so that's what we're doing and then here we are haha so here it gives us a base of the initial contributors and so now what we need is obviously the standard principle a guide art, a guide commuter blah blah blah blah so since it's the first time I've added absolutely everything and here I made a guide commuter type m so here you have to be very careful my back is a little bit dead and I don't like to fall in this trap so I've been a guide for a long time but I didn't know that so this is the first time that I meet him but he's vital because if you make a commuter that you didn't put that it won't be merged in the main repo that is to say this is my field DOC only accept the contribution of the developers who signed an NDA or CLA to say that the code that I give I follow the owner and I know my right to use Hyperledger to do what he wants so it's really a lot of things that the commuter doesn't use especially the developers the agreement of the developer that this code is to him that he doesn't use it and that he has the right to give it to the project so that was what we came and on the interface we hung it on a case and it was quite hard so the people of the guide I'll just do that guide help and we'll see here so here the shooting is somewhere somewhere that's it so here it is it's really a kind of quick signature to say what I give and to me origin so if you need more information you can just do a guide help and read the documentation so if you don't put it it won't work once you have done your push and once we're going to do a merge request so very very important so once we put the S to sign our commit we put our message as an initial commit so it's done and from there we can make our push but once again the push stays on our branch on our local depot because here we have we have copied our I've already checked on which branch we are we'll just do that and replace by initialization so here that's it the push is well done so what we just did is so fork the depot that's the basic element that is to say we click here we fork the depot, that is to say we get a copy on which we can intervene because we can't just come on this main depot because that's it and so we approach this depot by making a copy and once we have done the copy the copy we do this work all that I just did is not to redo because once we have created the FRFR file we don't need to recreate it it doesn't make any sense so we'll just go to the FRFR file to take the elements for example so once we are there we'll just go for example to take a network test to open it and start to translate it so I just we copy that we translate it automatically here and if we have two or three people we share it in a Google Doc and all that for maybe an hour or 30 minutes and once we are happy with the result we come back here and we paste the content and we put the markdown balises that we come with so if the markdown balises it's a markup language it's a balising language a little simpler than HTML so it's a title of level 2 so it's a title of level 2 it's this kind of thing so it's a title of level 2 so if we put a a simple 10 it's a title of level 1 so it's this kind of thing so to make lists we draw non-ordinated lists so markdown simple so that's all I said I don't know absolutely nothing so once we put our code I'm looking for my navigator here perfect what is this who tells me to visit this thing so what does he tell us so there's nothing to compare so maybe there's a merge and a branch so I'm just going to change the branch so all of this it looks a little complicated but it's not there are graphic tools to do that I like to use my terminal that's it once we have that we can start merging work so here it doesn't merge but it's a pull for quest so here it detects that there are changes that are made there's a difference on the original FabricDocs and comparatively on my repertoire so from there we can create the pull for quest to ask for what my work is merged with what is on the main branch so here with a reminder it's a reminder that he says what's in what's in what I want to bring and once we have made the merge request the validator looks if everything is okay everything is in place and from the right there should be no problem to merge what we just did so here it is there's only that and even that it's really put in place after once everything has been put in place it becomes easier and easier because as I always say what is done is no more to do so from there I think I just was there and you put your hand for the most important part it's to ask everyone finally everyone those who are there those who are ready to participate in this embarked adventure and so it's all for me so thank you for your participation so I'll tell you how to say it so I now it's up to you so I'm starting I nominate you I nominate you I nominate you I nominate you and all the rest here on YouTube you're welcome but anyway the planning is really on there one hour per week and then we decide together the collective hour and day and then those who can be there will be there and we all work together to try to put more visibility to the French documentation because that's something that's missing a lot because since I manage a Francophone community there are a lot of elements that go or activities that people on which people can't to which people can't participate and on which they can't come because it's in English and it's a bit of a shame because on a technology like the blockchain really I would really like that our young brothers and everyone can have at least a documentation at least tutorials in French at least sessions or workshops in French to be at the same level as their English brothers because the language barrier of the language exists on the other side English-speaking people don't often see it they mostly see, for example we talk a lot of diversity we talk about men, we talk about women we talk about racial minorities but often we don't talk about linguistic minorities if I can say because the French language is beautiful and everything is done today in English in Chinese we try to write even the French themselves they write in English because they know that everyone now we have to say that there are people who exist in Francophonie and we have to think about trying to join us to you there is no more just regular meetings to make progress yes so I really like the part of each one of you and that's it so meet on the wiki so there is no emergency the wiki I put it back for those who were not there and so from there you just realize and you sign you say that you want to be but I will try to do it so that's it but you can put a mute and discuss there is no constraint you can open the microphones there we are on the science chilling out Kevin we don't hear it doesn't work it will be better it works thank you hello good evening and thank you for the presentation I just had a question a little detail about the TIRES that you have to add to each committee please and it's every time that we make a committee that needs to put the TIRES yes so each committee must have the problem I had is that I made a committee with the TIRES a committee without forgetting the TIRES and another committee with the TIRES so he said to go to the committee of the environment to modify to put the S to be able to merge all these problems so it's very very boring once we forget if you forget it on the last committee it's okay you can just do a guide committee and it will simply change you but if you forget a whole pile there it's a little more sure so okay thank you for the precision I didn't know about the TIRES neither did I and it's quite interesting thank you Serenia Sen who has already created the Sien so I imagine he's talking about the UNIX Foundation to access the Wiki thank you Seren so I have to go back following the link of the Wiki we connect and we have to send it to the identifiers when you add us somewhere if I want to participate how is it going so once you are wait let me see Wiki sorry to make you repeat no no not at all with pleasure so once that once I have your ping so I put the links on which I was so once you have created account identify and arrive on this space there you have the possibility of editing because it's a Wiki everyone can modify you modify there and then there so you modify it you come there you make a tabulation and you put email that's it so ideally you can say what you did here and click here to update me and modify it, that is to say that everyone receives your email otherwise I will see it because I am subscribed to this page so I will see what you do before what happens here so that's it and once I in the end of the week I send an email, create a small group and then we start the activities as simple as that ok thank you thank you so that's it I do not know if maybe Gilles you want to make do you still want to dispense of your sages speak to click listen no I think that I have already made the remark that I wanted at the beginning in addition I have a video conference that starts there in a minute that will be especially thank you very much Umar to have put the call today and then there to see the first contributions it's a good opportunity to contribute to a project which makes sense, thank you thank you very much and I leave you here to join my other video see you soon and the others too so I go to see because I do not want to waste your time David is here no he is not but anyway it's not so I want to thank you all for coming because after there was only the link of Zoom so I apologize for the advance and I would like to thank my brother ID from Nigeria he is very supportive of what we are doing here in Senegal and in all the other chapter of Hippology so I would like to very very very thank you very warm thank you to ID I I just want to see that there is a link on YouTube there is a question that just asked me I will share with you Simon Deve who says thank you do you see my screen so there is Simon Deve who says thank you for this initiative how can we develop you I am not sure to know what you want to say maybe you want to say develop on Hyperledger Fabric well develop and develop Fabric it is very complicated to read the documentation and I do not know to participate in the workshops to try to find a mentor it is a bit like all the technologies that exist you just have to launch and then you have to know the terminal in any case if we want to develop as a network as a network manager to know Docker because it is especially what is initialization and blockchain network development on Docker containers and that's it and then you have to have JavaScript if you are a JavaScript developer write the names if you are a Java developer if you are a Java developer if you are a Java developer you can contact me my ID my handle that's it so that was all for me thank you again for coming thank you for your participation see you next time guys see you see you thanks a lot


what to do about all this to start with each person who has to deal with these horrors on their screens in their ears and in their eyes every day has to first protect their own selves their their own bodies from the assault of all of that information which actually is simply feeding a vampirical need to tune into human suffering one has to keep it at a minimum one needs to be informed i understand that keep it at a minimum first deal with the suffering that's happening in yourself that is what a spiritual seeker does they first find the truth within themselves because that strengthens them and when it strengthens them they can handle that assault


Thank you very much for coming. I am absolutely astonished at the turn out So thank you very very much for taking the time to come and join us at this first Drupal ACT meet-up in over a year It's been a while. I'll admit from the outset that I don't live in Canberra. I live in Melbourne. I Know but I'm not from Sydney Sorry So I have a lot of clients in Canberra, so I was very interested in seeing this event took place again and that the Canberra community was meeting up And I got the idea to get involved with this when I met with two people Who I work with that were both doing the same thing but totally disconnected from each other And I just thought you guys need a venue where you can meet and talk about all the cool stuff that you're doing So I want to say huge thanks to Annex for hosting and thanks to Marge for all of the help that she's done on the ground I've just been directing And so tonight I'm going to do sort of a preview demonstration of the talk that I'm giving a Drupal con pride in the next three weeks And then make them walls going to give us an update on gov CMS and then We'll see where the evening takes us. I would also like at some point There is no camera. I'm sorry. There's a camera here If you're waving you're waving here And we're looking to probably do this every month or two months moving forward obviously with triple south coming up If you haven't heard Drupal South is coming up in Brisbane on the 19th to 21st of October So grab your tickets for that. They're still relatively cheap at this point early bird pricing and all of that and So, yeah, early November. We're thinking about doing a panel. We don't know what the panel would be about But if you have any suggestions, please let us know and then early December. We're thinking about just going somewhere for drinks so without further ado, I will Share my screen and we'll get stuck into This presentation. I'll have a little bit of liquid courage I Had a little bit of an incentive like Part of quite this is good for me is that I had to have it ready early The interesting test will be as if it's anything like this by the time it makes it to cross who's it I know? Everyone here So Yeah, my name is Michael Richardson. I run a managed triple platform as a service provider called iron star We provide managed triple hosting for state, federal and local government as well as enterprise clients in payment processing aviation And another sector that I'm totally blanking on but they're a very valuable client Tonight I'm going to be talking about how business managers and project leaders can gain confidence in their site security as a bit of a Survey who here would describe themselves as non-technical when it comes to dribble Okay This talk who here would describe themselves as a decision maker who is non-technical when it comes to dribble All right, this talk is for you Everyone else You are my guinea pigs because I'm sure all of you who are technically oriented and come from technical backgrounds have to Encourage and guide non-technical decision makers in making technical decisions about your Drupal site and This talk and this experience is really it's based on an experience that I had about three years ago where I failed to Correctly and effectively educate a non-technical decision maker on the merits of dribble and specifically dribble's security capabilities I was asked by a client that we work with to get involved in a Client of theirs. So this is an agency their client had about 12 sites that were hosted somewhere else and those sites were having performance issues No one knew what was going on and they asked us if we could get involved do a bit of assessment provide a report to the client With a set of recommendations pretty standard stuff Pretty quickly after getting in there We found that they've been hacked and that someone had put a crypto miner on both of their web servers and we're just Generating Bitcoin or Ethereum or whatever it was And no one was aware We provided we cleaned everything up. We did what we had to do and then we provided a report to The chief marketing officer of that company and her takeaway from that conversation was dribble is insecure And I don't know where in that conversation I went wrong, but I could not get back from that deduction that she had made I tried very hard to explain that dribble was not insecure her Implementation of dribble was insecure, but at the end of the day the entire organization Re-platformed all 12 of their sites on two wordpress so So that was just failure to failure really But in my work I very often almost daily talk to long technical decision makers who are responsible for very technical Decisions, and I have a lot of empathy for them in that situation because they don't come from computer science background They don't come from a programming background. They haven't built triple sites. They haven't hosted triple sites I mean if they're responsible for sites that generate in some cases millions and millions of dollars That are essential to the organizations that they work for and they get asked to make these decisions that they don't have any real understanding of but nonetheless, they are responsible and they are accountable so That's I've gone through all of that and skip that slide so we'll move past that So yeah, this talk is about some of the things that you should be asking your teams about to secure your dribble sites We're gonna talk about this from a cost-benefit point of view not everybody has an unlimited security budget If you have an unlimited security budget, please see me later on this evening. I have some stuff I want to talk to you about But really not there is no security solution that everybody should have It's all risk and benefit and choosing what fits you But there is a lot of stuff that you can do to your triple site that will make it very secure That I find in my experience a lot of organizations and a lot of teams aren't doing and this stuff is free or cheap and most of the time very very So we'll start by talking about the easy wins These are the things that are free and that are very very simple to do and that very few Drupal sites actually seem to have And the first one is security heads using the security kick module I would imagine most of the technical hands that we saw earlier Would be familiar with security kit and security headers But for those of you who aren't a header is something that your web server sends as a metadata to anybody who's requesting any object So when a user visits your site, they get a bunch of headers The headers provide instructions to the browser and security headers in particular provide security instructions To explain I want you to always talk to me with SSL I want you to do this to avoid cross-site request forgery or cross-site scripting click-jacking all of that sort of stuff Security headers are free. The security kit module is free. It is all very very easy to set up and it does work it provides quite a lot of effective control against these sort of Manipulation of users in real time against your with the browser that they're using against your site So we should be asking the question all about technical things Do we have security kit? Are we doing are we sending security headers with our site? And I will be configuring them correctly to do things like put a quick check in the cross-site request forgery The next thing that is on the I'm sorry There is a flight called security headers calm Which you can plug in any domain name into and it will give you a report and a grading on that site And I encourage you grab your phone if you want to plug in the websites or Website or sites that you're responsible for and have a look and you don't have to tell anyone the score you can keep it to yourself But it will give you this site will give you really really great guidance on okay You're missing these headers. Here's why you should have them here's more information about how you should implement them so highly recommend checking that out and The next thing which is going to feel like a no-brainer and surely everyone's patching everything all the time But in my experience no There is a security release for Drupal every month more or less It's it is a time thing every month. They may not necessarily be something every month, but they generally is There are the security patches for modules and I tend to find that things either fall into one or two camps Or three really the third being everyone's patching, which is fantastic The second is the agency or Contractor a consultant that takes care of the site isn't able to convince the customer that they should be paying for the time required To do the patching so patching comes about when there's a security vulnerability and everybody's panicking or Patching comes about only like there is a conscious effort that we will patch our website But that update doesn't really apply to us We'll wait and see what happens next month next month comes around that update doesn't really apply to us either We'll just keep waiting until there's one that applies to us and then six months later There's a massive vulnerability everyone's exposed and you've got six months of patches to apply and one of them breaks your site So what should have been a 20-minute patch? Cycle turns into two three four five days and for that entire period of time that site is exposed So very strongly encouraged non-technical decision makers to be talking to their team about how often they patch How automated those patches are and if they're patching not just the Drupal core But also the Drupal modules that they're using as well patching should be boring. It should be routine So that when you really have to do it in a hurry, there's no surprises The next thing that we should be looking at these content delivery networks This is an area that used to be very very expensive content delivery networks or CDNs are a distributed network of servers that Receive requests on behalf of your web servers, and if they have a locally caged copy, they will deliver it Sorry if users in pride for example And they request content and something that we host and there's a CDN node near them They'll get a copy of that content closer to that has a lot of benefits the first being that it significantly reduces the load on your Web server, which will help you reduce your hosting costs. I'm not terribly excited about that, but it's something that clients like the next is If there is an attack a denial of service attack on your website that network is going to absorb Most of that attack depending on the type of attacks. Sorry a CDN Generally, you can get the free. I've got a little bit of an analysis here on four of the largest providers being cloud player falsely AWS is Cloudfront and Azure's CDN product They have varying degrees of complexity, but there are many many more choices than this. This is a very commoditized Product offering which is great for anyone who's delivering a website because most of you can get a CDN For nothing or for very very little relative to the cost of the actual hosting and the cost that you spend maintaining the site every month The next thing on the list of things that are free and easy to do is Two-factor authentication. I see very very few sites with two-factor authentication Most if not all users are now really familiar with two-factor off. They've got it in their phones They've got it on their company accounts. They've got it pretty much everywhere. So the learning curve is gone And two-factor authentication is probably the most silver bullet of all things that you could find When it came to preventing an attack on your website if somebody gets the username and password for one of your users It's a whole other kettle of fish to get the two-factor authentication code can be done can be bypassed. However Two-factor off with Drupal. There's a few different modules that do it. They do it in different ways You can find the one that fits you best. They are free. They are easy So you should be asking your team. Do we have two-factor authentication on our websites? The last thing in terms of free and easy, which is another thing that we don't see often enough is email security records This is probably the slide that I had the hardest difficulty with not getting too technical But if you think back to the security headers and the fact that they instruct browsers What to do when they access your site security email? Sorry email security records do the same thing that between mail servers They tell mail service how to be sure that someone that's pretending to send email as you is actually you is from a server That you trust and even more importantly or just as important What to do if they get an email that is pretending and fails that test You effectively want to know if someone's trying to send phishing attempts as you And the D mark record is a way to do that and finally the MTA STS record there Will tell mail servers how to interact with your mail servers using SSL so that you encrypt connections over email Again, this is something that we see very very rarely all this stuff is free It's somewhat more complicated to implement but not very difficult at all And certainly something that whoever takes care of your domain name and your email you should be talking to about this So that's it for the the quick and easy stuff And if you went through and you implemented all of those things I think you would have a more secure Drupal site than probably 80% of the Drupal installations that I've ever sent And all that stuff is free Except maybe the CDN The next up we're going to talk about is the work while endeavors if you've done all of that stuff And you're in a really good place and you want to think about okay I'm I'm more exposed than most applications or I'm more worried about risk than most people What are the next things that I can do as an add-on to your content delivery network that you've gone and successfully deployed You can look at a web application file It works similarly to the CDN and that it receives requests from all over the world And it analyzes them before it sends them on to your web server and it looks for malicious patterns in those requests It can be programmed to be aware of specific Drupal security threats when major Drupal vulnerabilities have come out in the past a lot of the CDN slash WAP providers have Put in rule sets even before the Drupal patch is available or just as it's available So that even if you haven't patched your site if you're behind this web application firewall of this WAP You've got a lot of that protection on all that control So we should be asking our teams. Do we have a WAP? Are we programming specific rules that are unique to our organization and our own risks? And do we monitor WAP alerts? If something is attacking us, are we going to know about it? The next thing and I promise this is not a plug Or at least it's a it's a generic plug for everybody The next thing is specialist Drupal hosting in six years working with Drupal. I have seen seven websites of seven servers that have been hacked and They've all been either self-hosted or hosted by a provider that wasn't a Drupal specialist It's very very very easy to host a Drupal website and that's part of the wonder of Drupal But that's also part of the risk of Drupal because it's very easy to think right I've got a Drupal server my site's being hosted everything's okay. I'll walk away But there are specific nuances to the implementation that you need to be aware of and I would encourage you to ask your team does our host actually understand Drupal and If we have major exploits or if we have problems with scale can our host help us do that? If you're looking for something that's a bit more turnkey and a bit Easier to access especially on a tight budget then platform that SH and Pantheon have very very good products at that price point They're very powerful tools And I would certainly recommend them and if you're looking for something more specialized Especially if you're looking for something that's compliant with federal government frameworks like the ISM then amazing Einstein and Acquia are also very very good choices, but Sorry and go CMS But I kind of forget everyone here is already familiar with that But if you're if you're self-hosting or you're hosting with someone who isn't a Drupal specialist You need to be asking them those questions. Are you equipped to take care of Drupal? The next thing along the line in terms of medium effort stuff is single sign-on I'm gonna go out on a limb here and bet that everybody in this room has Authentication to their workplace using something like Azure AD or off-door or Google Workspace or something like that almost certainly Azure AD But if you have more than one user and more than one Drupal site single sign-on is something that you should definitely be talking to your teams about If I see a lot of sites where someone's rolled onto a project worked on it for a few months Rolled off the project maybe even left the organization But no one has an awareness of who has access to what and how tightly controlled their accesses They may have admin rights when they're just a content editor And this can go on for months or years if that person's username and password But they reused for the Drupal site gets leaked from another database Suddenly you're exposed and you wouldn't even know about it single sign-on is a really easy way to give people access to sites and remove it And generally if somebody leaves an organization, you know about it in like you're at least removing and may log in for their email So you should be picking back on that authentication process Slightly more effort to configure Cost depends on whether or not you've already got a single sign-on framework like Azure AD or off-door If you do then the cost should be effectively nothing aside from a couple of days cells And then finally it will talk about a couple of things that you can do To build a culture that's focused on Security so you've done the stuff. It's really really easy. You've done the stuff It's a little bit difficult and cost a little bit of money. Where do you go from there? and the answers to that is far more complicated than I'll go into here because there is probably a hundred things that you can do to Build a enterprise grade government grade very very high security website But I want to talk about a few things really quickly and the first is automated security scans If you're if you've built and deployed a Drupal website that is secure today It may not necessarily be secure in three months or six months There may be a component that you're using in your website Or even a dependency in your website that has a dependency that has a dependency that has a dependency That becomes vulnerable at some point in six months time And if you're not automatically patching that stuff and you're not monitoring that stuff You won't know but that vulnerability exists in your site so one thing that you can talk to your team about doing is Setting up a daily automated security scan that orders your code base for no one vulnerabilities I've got an example here. I didn't have a Drupal app that I could use as an example But this is a Node.js app And this is static application security scanning from GitLab GitHub and pretty much everybody has something in this space But this will look at dependencies and find vulnerabilities in your code and let you know about it And you can set this up so that it runs daily and you can get an alert that tells you hey That site that was perfectly fine yesterday isn't okay anymore and we need to look into it The other option or the additional option I should say is dynamic application security scanning which will log into your website instead of analyzing your code and analyzes it When it's lying in runtime will log in it will scan around. I'm not aware of anything yet. That's a very Drupal aware In terms of testing specifically for Drupal runtime vulnerabilities But there are a lot like intruder.io that I've used here to have a PHP awareness, so there's still a lot of value there So that's another area that's really worth looking at So we should be asking our team. Are we scanning our code for vulnerabilities? How does that thing take place? And again, how do we get notified if it picks something up? Are we going to be aware of? The next thing on the list is workstation security This is one that we've just gone through a very very very long process with And we are still going through the process with it's I think it's more difficult than service security But it's also often overlooked if you read about a data spill Someone an organization has a list of their customers exposed or a copy of their database exposed very very often in their stories You'll hear about a laptop that was left behind somewhere Wasn't secured and just had a copy of the production database. So this slide on the next one address that The first is workstation security making sure all your users have encryption turned on making sure all your users Connect through a secure net secure VPN all your users have any device all that sort of stuff Is a lot of work? But if you've got secure service the next thing you need to be looking at is secure workstations and finally Sanitization of database exports this isn't this is free. So it doesn't really fit in this part of the discussion, but It's something that I think has slightly less value compared to the stuff that came earlier I wouldn't have this before I had the other stuff But you can set up scripts that will when a developer copies their production database to their works Station or to another environment it will scramble the user data That is copied things like emails usernames everything else So that if that database was stolen from that employees laptop or lost somewhere else the data is effectively useless Might be slightly useful to a competitor, but to someone who's just looking to data my personal information. It's pointless So that is a free tool that is well worth looking into So a quick summary Again, if you don't have everything here that is effort minimal Then I would suggest that's the very first thing you should be looking at won't cost you very much at all if anything And then you can work further down that list to just gradually Improve the security of your site over time security is something that you must evolve with a site that is secure today We're not necessarily being secure a year from now And that's not a Drupal thing. That's we all know that that's that's technology and that software and all CMS is evolved like that So Thank you very much If anyone has any questions, I'll take it otherwise. I did mention I'm doing this talk at fraud If you can't see that which I wouldn't blame you if you can't Ionstar.io slash GCISS is a survey for this presentation.  I appreciate this may not have been terribly exciting for 90% of the room, but again, you don't have to go through this whole this the same thing of Providing technical recommendations to non-technical decision-making So if you feel like there's more that can be done here to make this more effective for that room In Prague, that's hopefully going to be a far less technical audience then please let me know otherwise. Thank you very much question How do you go about for the Vincent people they need to do patching regularly because that's a common problem, right? Mate if I knew the answer It's it's a very hard sell especially to the audience that is Will patch when we need to will patch when it's relevant And that is so far only something it's only a option that I've learned that I've seen learnt the hard way where There is that critical patch and it can't go out for a few days and okay. Well, that's pretty bad but I think It's Again, if it's easy and it's done routinely it's not a challenge to sell it so I would talk about automation I Would talk about Getting a routine for it and doing it you know to that routine and never breaking that rule I can see you when we get them sort of in a managed service or all similar. Yes, because I mean they pay for it, right? So it's easy, but I Think everyone has that problem. Yeah, everyone. I work with definitely Talk about it in terms of insurance. Yes, it's like if you enjoy your car And you're ensuring your house patching is ensuring your service or your website or your whatever it is Yeah, and the same way that you well hopefully you wouldn't drive away without ensuring your car You should do the same thing to your website That's how I can be as people We have a raised hand on meat Let's see if I can work that out. Oh Thank you guys. My name is Joseph. I'm from a department of finance. I'm a developer and Thank you for your presentation. I think it is a really awesome and they're really good to pass the triple security to our community So one quick thought is that regarding to the non-tech person From my past experience is like personally I'm strongly recommend that sort of like a Drupal Adversary team or Drupal security advisory ketchup can be happened weekly As we know that Drupal team has a calendar basically has a routine release of Drupal core security updates and Drupal country module security updates In a in the in the calendar So that I think I strongly recommend that the non-tech person has a Like the routine ketchup with the technical person because we do understand that there's a gap there, right? So maybe the the technical person like developer. We all we all know that tomorrow We are going to have a critical something Drupal Like the module needs to be update However, we need to like to put it into a catch up with the non-tech person and Present such information in a non-tech way So that this communication can be smooth this and then we can put this For example like a Drupal security updates happened and the non-tech person can and understand us So this isn't my point. Thank you. That's a really great point. Everyone could everyone hear that? Okay. Yeah, great Okay. Yeah, that is a really really good point time the security meeting to the Drupal security advisories And then you've got a lot of extra context for the conversation. Thank you. Any other questions? I Will be interested what tools if you say tools to use for sanitize the database What kind of tools just the the drush Sanitized command or SQL sanitize command. It's built into drush So you can you can and you can program it to be a bit more aware of your specific data structure And the columns that you want it to to scramble when it does an export So it's all yeah, it's all just built into drush I don't know if there's other tools that do it or other ways to do it, but that's the one Yes mtk on skipper where you can use this customize what they want to sanitize Okay, cool All right, thanks everyone. Um, we'll take like five minutes You can all get some refreshments stretch your legs and then uh, and then we'll hear from Nathan who's going to give us an update on God see you max So yeah, we'll be back at uh, let's say seven ten Nathan. Is that all right? All right, fantastic. Thanks everyone


Hi everybody it's Sam at Mixed Up Craft. Thank you for watching my tutorial today. This week's scrapbook layout is one of me and my besties. There's actually only five of us in this picture. There's two missing so sorry Hayley, sorry Karen. I'll do another page with you in it but these are my oldest school friends. We have a friendship that's spanning nearly 30 years so yeah they're the best ones. The layout I've decided to do I'm using the Stillwater 12x12 Paper Pack by Rosie Studio. This picture was taken on the hoe, the Plymouth Hoe, where we're all from which is right by the sea. So although the scrapbook layout doesn't really look like it's got anything to do with the sea or the water I just wanted something that was kind of just soft I guess is the right word for this. So I'm just taking two pieces of the 12x12 there and I'm cutting them into half inch strips so I want to create a lattice woven kind of background so I am bringing in a white piece of cardstock. I've already cut this down to nine and a half by nine and a quarter again to fit that 10x10 album and I've just brought in some of my watercolor paints here and I'm just mixing up a wash that's going to complement the kind of greens and the pinky tones that are in the papers that I'm using so I've just covered my paper there in white in water and then I'm just you can see here I'm not taking any care at all I'm splashing it around there's a lot of water on there because what I'm going to do is when I heat set it I'm going to move that water which you can see me doing now see how it's dripping down that's the you know I guess that's the water kind of elements that I'm bringing into this scrapbook layout so I'm just heat setting that make sure all that water is completely absorbed it was pretty saturated so you can see here I'm going pretty crazy with my heat gun so now I'm bringing in all those half inch strips and I'm just lying it all out first on my mats I didn't really know how big I wanted it to be I wanted it to cover obviously the size of the photo but I didn't end up using all the strips so what I'm doing is I'm just popping a little bit of glue and then I'm just popping a strip on top then the next one I'm going to pop the glue on top of the strip and then I'm going to feed that underneath that piece of paper and then the next one goes on top and the next one underneath that's what you need to do on that piece that you start off with after that you can see what I'm doing now I'm just weaving all of my paper through so the bottom one is stuck and then all I do is stick the first and the end which you can see there of each one then that I add so I weave it all the way through and then I just glue the first mic I'm doing there and then the last one now this was actually the end so then I go around and I trim all of this and I seal all of the edges um you don't want obviously any of it coming undone and um the effect is really really good I do enjoy doing this one so that's it complete and now I'm just laying it down on that card and obviously you can see it's very big so I go around and I randomly trim all the edges all different lengths just go around every single side and just snip all of those strips until I'm kind of happy that I've got it to the size that I want it to be I do end up trimming it a little bit more so you can see there it's all kind of there but it's not stuck down yet now the picture looked lost so it needed to be framed so I'm just bringing in that pink that I pulled out from the pack earlier and I'm just going to mat that just so I get that nice little one-eighth of an inch kind of border and then just trim that one down to size and it just makes it pop much better and it pulls the pink actually that's in the other strips it brings that all together as well so I end up moving the lattice I'm calling it a lattice woven kind of background and move it around and now I go for the which way yeah no is she going that way that way there go I didn't want to lose the droplets those kind of dripped watercolor bits on the right hand side there so I've got my positioning I've got my picture and then I bring in more rosy studio now I've got some of the still color accessories but I end up using more of the glass house accessories they've got similar tones so they worked really well with this so I'm just going around there just splodging glue just over the main bits really the edges and then just a few bits through the middle get that stuck down again you'll see it really nicely in the pictures it's got lots of detail and it has it's really worked well this one and then I'm just again just making sure all those little edges are all stuck down I don't want them to catch when they're in my album and just make sure that's obviously all nicely stuck down so I end up keeping the picture more down towards the far I guess bottom left hand side I'm popping this on some foam double-sided tape again I like to give it dimension I like it lifted slightly on an angle there and then I'm going to start adding in my embellishments now I ended up not using these they're really nice they're little they're called luxe clips I kept it there for a while but I ended up taking it off these are really nice these are from the glass house collection and I end up using I put some foam on one part the bit that's kind of hanging off just so it's lined up and level with the photo so I bring that one down the bottom right and then I use the green one towards the top left and I do the same thing they've already got they already have their adhesive on them but I just add some foam just to the area that's going to be overhanging from the photo again just to keep it all nicely finished and all level you don't want it kind of sinking in your album over the years so everything's starting to tie together this is more stuff from the this is from still water and the sentiment I pull out there is called laugh dream love together and I just thought that's what we do we've we've gone through a lot the seven of us and we've all still come out of it the other end and life brings us those challenges even every day now so we're always there even though I live miles away from them and miss them dearly we all do stay in touch and yeah best is friends these are some resin flowers and I do stick them down with my heat gun you don't see me do that but they do have adhesive on them but I always whenever I'm working with like plastics I like to use my heat gun then I'm bringing in some of the gold words and I use friends always which is what we are so I thought yeah friends always laugh dream love together and they just all seem to kind of work nicely so I took a while trying to there's loads on there so there was actually quite a few different sentiments that I liked but I thought these two were quite worked well they've got the gold trimmer's well which goes well with gold that's below the flowers they're kind of framed then the title for this layout is besties so that is our facebook group the kind of chat group that we have it's titled besties and it's just the easiest one to to title this scrapbook layout now I do go quite high initially these are from hobby base these letters and I don't ever push them right down so you can see that I brought it down lower and then I just you know really push them onto the paper you can always add some extra glue as well which I may end up going to do because they they don't have the best the best stickiness and because they're going against that lattice and also some of the watercolor it might not be the best surface for them so I may well go back into them but I was just leveling it off with my Tim Holtz ruler and then I bring in my Nuvo drops of course I have to finish my scrapbook layout with Nuvo drops so I use the sunlit meadow I use the bubblegum blush and I use a white blizzard and again you'll pick that up really nicely in the photos you probably can't really see it too much and they always dry better so there you have it a really nice soft scrapbook layout of me and some of my besties I've really enjoyed this one I love that woven lattice technique and hopefully you give it a go I inspire you to try something and if you've enjoyed today's tutorial as always please give me a thumbs up and subscribe to my channel to see more thanks for watching bye


Australia. The young country for you and your children.  Then Australia is the country with great opportunities and a great future. Maybe you want room to move, space to grow. Australia is the country for get up and go people. 700,000 Britons have already gone to Australia. If you simply must know more, see your local TV paper.


The study describes the development of a vaccine against HIV, which addresses the challenges of sequence diversity and immunodominance by focusing on highly conserved regions in hyvend that are poorly immunogenic in macaques vaccinated with full-length end-expressing DNA vaccines. Two versions of plasmids encoding these 12MCE were generated to maximise the inclusion of commonly detected variants, and vaccination of macaques with a combination of these two NFCE DNA-induced robust, durable cellular immune responses with a significant fraction of CD8-plus T cells with cytotoxic phenotype. Boosting with the intact NFDNA vaccine potently augmented pre-existing immunity, increasing magnitude, breadth and cytotoxicity of the cellular responses. The study concludes that NFCE plasmids are capable of inducing durable responses to highly conserved regions of end that are frequently absent after end vaccination or immunologically sub-dominant, making them candidates for use as prophylactic and therapeutic of vaccines. This article was authored by Shindau Hu, Antonio Valentin, Margarita Rosotti and others. We are article.tv, links in the description below.