 Ydych chi JV ac yn ddod â'i dda i gael i'r hyn yn ddod. Rydyn ni'n gwybod y gwerth gwrs ac yn ystafell ar y gyrfa. Ac rydyn ni'n ddiogel eu bod aethau yn mynd i gael i'r hyn yn gwybodaeth ac yn gwybod i'r chyletaeth ar Eiril Rwkem, ar gyfer dda ni'n gwneud eich ddweud eich ddweud eich ddweud eich ddweud eich ddweud, i gael i'r cymdeilig o ddim yn gweithio'n gwybod i'r cymwyngau'n gwybodaeth i'r cymwyngau'n gwybodaeth, Ydych chi'n gwybod i'n gweld i'n rhodod i'n gwybod i'n ffars. Rydw i, mae'n oeddiol i'r ffarsau ymgyrchu ei ddylch chi. Rwy'n ddweud yn ymgyrch i'r ysgolion i'r ysgolion. Rwy'n edrych chi'n gofio'r costerol o'r 100 o flynyddiol, rhaid, ac i'r ystod o'r unrhyw i ddim yn ddiddordeb, ac yn ymgyrch o'r newid i'r ardal gyda unexpected that I'm sort of bringing up with you at any point. And the main thing that I want to start off with saying is thank you so much for being here, because if you care about building open communities, literally by being in this room, I really, really appreciate all of the work that you're doing, so thank you so much. I have a talk that I've given multiple times and if you've heard me speak you've seen this slide before, it usually says, reproducible research on there, there's loads and loads of incentive barriers about why we don't have reproducible research, so we've talked a little bit about them in terms of fare this morning, there's a massive publication bias towards novel findings, people don't want to have to show evidence for the fact that they may have made a mistake along the way, it's not currently considered for promotion or getting grants, requires extra skills. All of these incentive challenges I'm not going to talk about today, felly mae'r ddechrau yn eich bod i gafodd. Mae gennym ddau oedd y llyw i'r ddweud i ddweud i'r ddweudio i'r golygu ar y gymryd y Llywodraeth yn ystyried dros y fwrdd yng ngyfyrdd 2018, wrth bod yn y ddweud o'r ddweudio i'r ddweudio, mae'n ganddwch ar fy ffordd o'r ddwyllgor mwyllwch ymddangosol ac rwyf lewbeth yw myfnod rwyf ei dweud i'r byw sylwag sydd wedi bod ni'n bryd yn dweud gan un o gweithio cyfnod o bobl o'r awr, o gweithio ar gyfer gweithio'r gweithio'r gweithio, o'r gweithio'r gweithio yw hefyd, a'r pwnghwych yn gwych, rwy'n dechrau i ddau yn y pwnghwych, oherwydd mae'r union. I also have a talk, I gave a talk at OHBM this year that the slides are available online and my friend Ross did a superhuman tweet thread of all four talks in the Open Science Symposium, and again, I'm not going to talk about this. But I do think it's really important to recognize that these structural challenges are there. They are always there. So, enghraifftrwyd i'r lleol iawn,ion środig yn wneud yng Nghaerweith Cymru, ond dylai gofyn yn fawr a'r gняf. Felly, yma fel rhai'r ddod ddim, yn gweithio'r gweithio'r gweithio i'r ddod. Mae'r ddod yn wych â rhywwch yn ei rhyn. Dyda yn cael ladechau a ddod ar gyfer y gweithio'r gweithio. ac yn ei fod ar y fusyfod, gallwn yn hynny'n fwy oeddiol ac rwy'n erbyn ei dleifydd. Ac yn rheswedd i'r llais cymdeithasio cyfreithiadol sylfaen i gynnwys.... Cywyddaeth yn gyfan wneud hynny achos ymgyrch iawn ac mae anxmaedau ar gyfer y dyfodol. Ond, yn ystod oherwydd mae'n fwy o beth sy'n hynny hollwgoddau sy'n mynd i'ch arwinelltio cyfrifiad ac yn cyfrifiadau, mae'r hynny'n llais cyfrifiadau yn eu fwy o beth sy'n hwyl i Felly, mae'r rôl 10 o'ch gweithio'r projiect yma, a 10 o'ch projiectau o'r opensor sydd yn ymgyrchol, ac rwy'n gweithio'r cyffredinol yn ymgyrchol. Felly, yma yma, Fy ffondi'r FNCF, a'r gwyllgor yma'r cyfnod, ymgyrchol ymgyrchol, Patrick Park, I'm a project, then I'm leading with my postdoc Georgia, I'm James and Bastion from Autistic and Open Humans. I respectively think that is a really cool project and would love to hear your thoughts about it. The Turing way is my hyper tweeted about project and I had a massive team of people working on that last year. I am Becky Louise, Sarah Petrisha James, Rosie Anna, Alex Martin, Malvika yn ymgyrch chi dweud y cyfnod ar hynny i gyffredinol a gyfnodol, i gymryd hynny i gyd o'r cyfond i'r amser i'r cyfodol, dwi'n gwybod i'r cyffredinol a ddysgol, chymae'r ffordd dros Ysgrifredin ym Mhwylwyr i'r amser i gyfyddiadol. Ymgyrch chi'n ymgyrch chi'n ffwyaf, gyda'n gwneud o'i gwybod i'n cyffredinol. Mae'r cyfodol yma yn ei dweud ymdyn nhw'n cyffredinol of a project from Dirk, Sarah and Danielle and then every single one of these rules is inspired by my relationship with the Mozilla open leadership mentorship scheme and so a huge shout out to Abbie, Chad, Aurelia and obviously the funding from Mozilla for them. So these are our 10 rules. We're going to enjoy them. Let's go. So the first one is to lay out your welcome map and that if you're working on GitHub or on an online forum will probably be your read me file and a read me is a special file on GitHub. You probably already know this but you might not have thought about it. If you call a markdown or an RSE file, read me. It will automatically be rendered underneath your list of files when you go on on GitHub and that is the first thing that anyone will see when they come along to your repository. So that is telling everyone why they should care about being there in this one that Patrick made. We have a table of contents. We have some information about the motivation, the project summary, some information on how to find out more information, a little bit about the philosophy, some of the benefits for public good and for yourself of being involved. There's a couple of nice icons and we tell people how they can get in touch to contribute more and we acknowledge our sponsors and also we tell people how they can acknowledge their academic publications that have supported it. So that is the first thing that anyone is going to see and it's really important that it has some really engaging content about why people should stay in. The number of read me files that are still just the template from the default that's added when you open a GitHub repository is kind of sad. I would like to be taken extremely literally here. I want silence during all coffee breaks and lunches. Nope, I'm joking. What I mean by don't have conversations in the kitchen is that you build up cliques that are completely unintentional but are very, very exclusive and it happens to be the case that a lot of times these are not for easy tasks. You often go and have conversations in the kitchen when you need to think through something really difficult and what that means is that the people who have the deepest knowledge about a project do not share that information online and in an accessible way that allows people to be able to come and join the project in a meaningful way later on. So I want to shout out binder because I think they're doing a really, really fantastic job here. This is their read me file and they have three different badges here that you can go and find out more information about the project management and what they're thinking about at the moment. So they have some issues on GitHub and you can scroll down and see those. Some of them have nice accessible badges that would help you go through and decide which ones you might be able to help with. There's also a Gitter channel which is kind of like an openly available slack so you don't have to download anything, you don't have to be invited, you're able to just kind of come along and chat in there and that's a really nice way of sort of that water cooler kind of having fun and thinking through things and chatting to each other and because Gitter scrolls very, very quickly and you lose information very quickly as you, as lots of people chat, they've recently moved to a platform called Discourse. Discourse is the same platform that Neurostars is based on so it's all exactly the same functionality if you've used Neurostars. There's a few different categories here and you can see for example stuff about community chat, governance, special topics, a meta one. If you go to binder you can see this particular discussion points that they're having there. I've just pulled out this specific example just so that you can see it that Tim is thinking about different user interface tweaks on my binder and he's got a gif in there that demonstrates what he's thinking about and there's a back and forth conversation thinking about how you can make that page less scary, more accessible and more understandable. So you can have conversations when you go to the kitchen around the water cooler and you're chatting with your friends and coming up with ideas but if you can put some effort into capturing the essence of those ideas in a way that people will be able to see how that conversation progressed you make the project a much, much more accessible space to join. Once people are motivated to join, so that's the readme file, they've got excited about it, they can see what sorts of things you're thinking about then you need to give people guidelines on how they can actually contribute and those are your contribution guidelines. So this is the SCONA project and if we go to our contributing guidelines here it talks through, it says a little bit at the beginning that says thank you so much for contributing, we've got sections on share your thoughts, we want to hear from you, we've got a little bit of information on the labels under the issues so we're explaining what the issues are and how we use them and what you might be able to learn from those so we have ones on questions and we have a couple of examples of how you can join in, you can positively join in with those conversations, we have ones that are for no code so if you don't feel confident writing code but you want to come along and help us run the project then those are really great issues to get started with, we have good first bugs or good first issues for folks and we highlight in bold that there are no stupid questions, we have ones that are marked with help wanted, bugs or requests so if people want to ask for something but it doesn't necessarily mean we have to do it and then in the next section we talk about how you make a change on github so one of the things that I personally think is an extremely high barrier to people contributing to open source is how difficult doing a pull request is if you've never done one before there's a huge amount of jargon, there's a very sort of different framework for collaborating and if you're not used to it it's really hard and so our guidelines have an explanation of creating an issue, tell people what you're going to do, make sure that you're not reinventing or redoing work that's already happened elsewhere, fork the repository, make the changes and we actually have a separate file because it got really long of a development guide and that development guide so I'm just pulling up a screen grab here that's another file has information on installing an editable mode that's a different way of installing the project versus if you just wanted to run the code, linting, writing doc strings, building the documentation web pages, tutorials and testing on random seeds and then we have a worked example so we have a little bit of information about what we expect the contributions to the project to conform to and then Ila built up this really fantastic fantastic example that takes us through doc strings and the linting that's expected for those, a little bit of adding a test if you're going to add some new code and we finish all of these by just saying thank you so so much for going through all of this work because as you can see from all of my screenshots there's a lot that goes into contributing to an open source project particularly the first few times so you've done that you've gone through here you can submit a pull request and then we also have a way of recognizing contributors I now use the emoji code but the scona project is a little bit older and so we use the let's all build a hat rack project it's a blog post that I like extremely strongly recommend from Leslie Hawthorne the links are in there and it's a live web page that tells you who has contributed including the folks who have just the clapping hand signal they have not made a commit to the github repository but they've participated in either reviewing code contributing to issues and adding to the discussion so it's a really nice way of acknowledging those that breadth of types of contributions that we can welcome and we let people know how they can ask us questions and we say thank you that's going to come up in it that's going to come up a lot so the fourth rule is to set explicit expectations for the project content and what I mean by that is that this is your roadmap this is where you set a vision for the project and this is where you say what is in scope and what is not in scope for the project because although an open source project is really great and if people know how to do a pull request they could come along and do an awful lot you still have to put a lot of effort into making sure that you are taking that project in a direction that is useful for you useful for the community that you're looking to serve and sustainable so you can't do everything immediately by tomorrow you have to prioritize what you want to talk about and one of the ways in which you can communicate communicate that to your community is through your project roadmap so with Tadana and I just wanted to pull up our read the docs page because it's got our fantastic logo that Dan created we have a we have a bunch of different documentation on that page but one of those is the roadmap and we've got a project vision there and we've got six different milestones which are our metrics of success and we want to include sorry we want to include documentation is really important to the project the fact that we want we can support transparency and reproducible processing we want to make sure that we have a lot of tests in our project um and these all of these have hang on a sec oh yeah I know I know what was going on here sorry um all of these have associated milestones that's why that was supposed to be my cube and so this is a vision in the documentation but the milestones themselves are collections of issues and so you can see that we have these various different milestones the issues can be collected into those and then you'll be able to see a little bit of that vision and how we're doing on those particular issues that we want to move towards being able to achieve that goal so another one another of our milestones is workflow integration with AFNI another is a workflow integration with BIDS one is on having a method extension and improvement so one of the things that we want is to have people add to the project to make it even better not from being inside of the core team and a final ethic is that we want to have a healthy community so this is the sort of work that often the leaders of the project the you know the two three or four founders and a couple of the people that they work with will have these conversations about thinking about what they want to do it's actually something that's kind of useful if you're going to write a grant for example and ask for money you'll probably have to say what your objectives are what your deliverables are but there's an awful lot of open source projects that are run in people's spare time and they often don't put that effort in and the point that I want to try and make is that it's there are selfish reasons to be super super clear about what you're doing the most obvious is if people want to take the project in a direction that you don't want to take it you have a place now where you can say do you know what that doesn't fit in with our roadmap we are interested in hitting these particular goals but hey it's open source you fork it take it do what you want we're super excited for for you to be successful and or if someone comes along and says I want to help this is a great place to help people get sort of aligned with your vision the fifth is um around your code of conduct so it's really important to set expectations for your community interactions and this is where I want to bring in the carpentries they did a huge huge amount of work earlier this year to think about how to build a really safe space um that github repository renders to a website and the code of conduct is front and centre in there um carpentries handbook there is a summary view that says that we're dedicated to providing a welcoming and supportive environment for all people regardless of background or identity um there are sort of a few bullet points and links to the guidelines there's also a much more detailed view that talks you through why it's important to have a code of conduct and more details about the specific code of conduct it's got a section on unexpected behaviour and it's got a section on unacceptable behaviour so instead of just saying hey people be nice and don't touch people uh there are actually very explicit examples of what being nice looks like and what harassment looks like and they also um link out to the consequences of unacceptable behaviour and they keep this updated as people um develop it going forwards associated with this already quite long code of conduct there are very very detailed incident response guidelines so if you are an instructor if you're running an event or if you like me are using this code of conduct for your own community you have a lot of guidelines on how you can make an immediate response to ongoing incidents uh you have checklists for responding to a report and responding to an incident for an immediate response an in-person event or online and communication channel reportings um there's another file there's a lot of documentation here on the incident response procedure and the enforcement guidelines it's got a little bit of information about what will happen and what the terminology that comes that even further down is um it talks through the whole procedure acknowledging the reports um making a first assessment of the incident following up with the reportee and then it's got some suggested resolutions and one of the sentences that I'm sure you can't read in there is saying there are many possible uh resolutions and we're not locked into any of these specifically but there are lots and lots of possible um actions so one of the sort of big misconceptions about codes of conduct is that it's all or nothing that you either pass or fail the discussion and you're either in or out of the community there's actually lots and lots of ways in which you can stimulate a really positive response um going forward there's an appeal process and there's some information about accountability for the organisation um and also on conflicts of interest I I give longer talks about this and I like this slide up there um I put the word um phallus cepsis up there to remind me what it is it means naval gazing and my advice to you if you're looking to run an open and inclusive community is that while you can take the the carpentries code of conduct and all of those materials they're all open source you can reuse them under a cc by license you have to do the work of really thinking about what you want to to reward within your community so it is not possible to just put up a code of conduct and say everything is fine you can say it but things won't actually be fine you have to do the work about thinking about what you want to um encourage I've got four more minutes according to my timer I think it's really important to send regular updates about what's going on for anyone who follows github repositories when there's lots and lots of conversation which is what you would hope from a healthy community there will be loads and loads of notifications and it gets really overwhelming so one of the things that you can do is send summary for example monthly updates this um citizen science project that I'm running with in collaboration with autistica one of our goals is to um co-design it and co-produce it with uh members of the autistic community and an aspect of autism which is not the case for everybody but is um a sort of prevalent challenge that some people have is that big blocks of text and lots and lots of possible options is very confusing and very off-putting and so one of our collaborators has um left this this long comment talking through how ridiculously difficult it was for her to try and actually contribute to this project because there were so many possible ways that it was actually really confusing and all of these links on this website that she didn't know how to use and couldn't install on her iphone etc etc was really difficult and so what I've done is I've responded to that I've added in some suggestions of things that we can do and what I what I was really reflecting on is that I think it's going to be really important when we send out our second newsletter we just sent out the first in august when we send out our second newsletter which we used through tiny letter which is now owned by Mailchimp instead of giving lots and lots of information we're going to focus each month on one specific ask which is much clearer and reduces the amount of information that people are having to process through in order to come and help you for free for your project I think it's super important even though I say that you shouldn't talk in the kitchen it is important to make time for face-to-face interactions and so I'm just shouting out the Turingway in May this year we ran a book dash event a book sprint is usually three to five days five days where you get together and write a book and a book dash is just a one day event these are the wonderful folks who came along to the Manchester one these are the wonderful folks who came along to the London event one of the things that we did the night before is we went out for a nice dinner we chatted to each other we sort of I tried very much to make everyone feel very very important and really appreciated because we did deeply appreciate them coming and we gave some little lightning talks in the evening after dinner just to sort of share some of our cool projects and interesting things that we were that we were doing and and then the next day we opened 38 new issues in the Manchester one was about the same in the London event and added a bunch of information one of the coolest things was that we had an artist who came along to both of these events and so we now have lots of openly CC by available artwork that folks can use on for example the fair principles these are some of the lessons that we learned in here was some just collections within our report of some of the reasons why people really enjoyed those two day long events and there's a pool request open right now it's it's got a couple of approvals so I think it will be merged quite soon where I'm proposing an online collaboration cafe so instead of having folks who can who have to spend 24 hours or a bit more of their time to come physically come to a day long event this is a two hours every two weeks in a zoom call in a in a sort of online like a Skype call where folks can work together they can either shut up and write which is what I did when I was writing up my thesis during when I was in Berkeley or they can go into smaller breakout rooms and be able to collaborate together even if they're not they're not physically located in the same space we want to try and bring the collaboration online in real time and one of the rooms that we'll be working on is to help everybody be mentored through their first pool request so fixing a typo fixing a broken link these are sit two of the most of useful contributions that we can have because they help folks get through that that journey it's going to start it's going to be a soft start because I've been because it's not even merged into the main spec yet but it's going to start next Wednesday I'm really looking forward to it we're going to do these like three different Pomodoro sessions and then have a little space to chat and support each other I think it's super important to explain how decisions are made the bid specification is currently going through a big reorganisation of its governance and so a lot of these what's happening next to the my screenshots for talking through all of the different aspects of thinking through how decisions are made within the bids community there's lots of different groups there's lots of ways of addressing those we have a working document where everyone can comment and leave suggestions and my point with this slide at the end here is that every project has a culture even if you haven't thought about it and so this essay by Joe Freeman from the 1970s it's a feminist essay that talks about the tyranny of structuralistness even if you don't have a governance document even if you haven't written everything down you do still have decisions being made at all times it's just that they're likely to have been made from a clique of people who were where it's it's non-transparent how those decisions are being made I'm coming to the end I know I'm going a little bit over time um I went to the last session at Mozilla's annual festival um in October Mozilla's annual festival Mozfest is a really really overwhelming space it's a very very participatory three days Dix later is currently pictured in here he does the training for the facilitators but he led a session and I just was going to rock up because it was the end of the three days and I thought it'd be kind of fun to support my friend and actually it was really really emotionally draining because what we were talking about was the life cycle of a project and so in the design that his group has been working on there is a preconception stage there is a conception stage there is birth there is infancy there is the youth and then it becomes a mature project and then there is the death of the project and I think a lot of us think about getting started and there's quite a lot of people thinking about sustainability right now but I don't hear very many people thinking about the graceful death the end of a lovely project that did a great job but is not a high priority for the team members anymore what does it mean how do you archive that how do you make it so that it can still be accessed even though folks don't need to aren't currently working and developing on it and maybe you don't know someone else will come along and there'll be a rebirth afterwards I'm going to finish by saying that the most important rule actually the most important rule is just to show great great appreciation for everyone who's coming along whether they're paid or whether they're not paid and I think that the Mozilla Open leadership programme does this these are printouts of postcards that are handwritten and sent to all of the participants and all of the mentors they are coordinated by Abby who's based in Toronto as you can see and she sends out stickers and those handwritten notes and I just have these these four little screenshots of members of the community being really excited to receive those in the mail and this is a picture of my wall at at work at the Turing Institute in London and a note that I got and a little pin that I was given and it means so much and most of the time I receive messages of not having done things things are late things haven't worked they're not as good as they should be why haven't you and to be able to look up and be able to see some positive notes and encouragement it's really good and that matters both online and offline so those are my 10 rules I've way over time so I'll stop these are the links the slides are all up online the DOI is down at the bottom of those slides you can't see them because of the colouring but obviously if you download then you'll have access to all of those different 10 projects that I showed you I want to thank all of the members of my lab and just acknowledge that I used a lot of photos from Unsplash and the Noun project in making this talk thanks so much