 Si viene de manera de las novedades en inglés, tengamos una cuenta de que está un poco sobre el modo climático, el primer maledad tiene el punto de la exenidad y es por eso que es la aplicación. Es una buena idea, pero es que eso es una de las novedades mejores en inglés para que pueda garantizar lo bien. Y bueno, os cuento, Sprilax es desarrollador margen, trabaja con Joe, y Sport Comiter, discurriplines, aplicadías, vamos a quitarlo de todo. Y como lo suficiente, además el producto es musical, y toca el piano, porque no se puede ser bueno en todo. Bueno, nos pasan a ver, las amizas. Gracias. Hola, buenas, y este es todo que puedo decir en español. So, I'm going to speak about contributing to WordPress Core, and I will explain some of the, what you need to be aware of, when you are interested in contributing to WordPress Core, which is the software WordPress itself. And I will do that in form of basically telling a bit of how I, my own story or how I got to do that, and what I learned across the way so that if you are interested in that, you hopefully have an easier path and have some of the, you know what to expect basically. So, before we start with that, there's just a few quotes by other core contributors, and how, why is this beneficial? Why can this be beneficial for you? Contributing to core, or generally contributing to any area of WordPress, can really, it can boost your career, it can give you job opportunities, but it also can give you an environment of people that you work with, even if you're, for example, if you're a freelancer, you might be working by yourself a lot, but then contributing, you make lots of new connections with other people who you can collaborate with, which is a very valuable experience. But then also, and you can make friends from all over the world, like at WordCamp, like this, you can meet them, and it just has given me really a lot, and also there are some other ideas from other people here. So, it actually, for me personally, it all started at WordCamp Europe 2015. If you were around in the WordPress community, you might know that it was right here in Sevilla. So, it was my very first WordCamp, I was at WordCamp Europe in Sevilla 2015, and so Sevilla tiene un lugar especial en mi corazón. And I went to the contributor today, and we have a contributor today tomorrow here as well. So, because I'm a developer, I just thought, yeah, okay, I try to contribute to the WordPress core, and it was a core table, I was sitting somewhere there, there's an arrow, and I was, the core table was led by Konstantin Obeland, who was the lead of the release, which was WordPress 4.3 at the time, and there was the task to test the heck out of the site icon feature. If you remember, there was a feature in WordPress which introduced the icon to have on the page, and that was the major part of this release. It was only about testing and testing and testing and finding one small bug and fixing it, and I did find one small bug and fixed it. It was just like ten lines of code or five lines of code, but by the end of the day, it was committed, and I got my first props, so this is my username, and I was like woohoo, I have got props and contributing to WordPress, which also had my, that means, now your name is in the list of people who contributed to WordPress, which was like wow, that's amazing, is it? So I was really excited about that, so I was so excited that I went back to the hotel later and I worked on another thing already, but it was a very great experience starting, so I really recommend that you, if you're interested in that, you should try and tend to contribute today at the WordCamp, like tomorrow. You can also try doing, starting this at home, it's definitely possible, but you have to be really motivated, you have to look everything up yourself, but in a contributor day, there are experienced people who can help you and answer your questions and immediately they have great feedback and they can also provide you good tasks to work on that are easier to get into. So after this, I contributed a little occasionally and usually at WordCamps and other contributor days, so this is a picture of WordCamp Berlin in 2015, so it was mostly still WordPress, WordCamp related, I did not contribute in my free time at home at this point, but then at some point I opened an issue, a ticket at WordPress does not use GitHub, as you might know, it use like an old system called track and that was the first ticket I had opened, it was just a small bug, it doesn't really matter, so I got a very welcoming response, first welcome to track, that was really nice, but then the ticket was closed. And the good thing is, I got a very elaborate response, why it was closed, so I guess I could understand, but sometimes you don't have made that experience, sometimes you just see like this is closed and why there is no response, that can easily happen and that was, it happened to me too, it's a very important, you have to be aware that this can happen and you have to ask why, if you're really confused why this was closed, you should not just be frustrated and stop, you can comment again even on the closed ticket, can you give me a reason why this was closed? Sometimes the people who on the other side they are of course very busy like we all are and sometimes you tend to forget to give an elaborate response, which is of course not good, but it happens, so we need to follow up, it's very important that you follow up and some things can easily be frustrating but don't just get frustrated. But then there were also very rewarding parts, so at some point I wrote a very simple class and the class was introduced into WordPress Core and I was like whoa, now I introduced a class into WordPress Core, it was very simple, but it was very motivating, so of course you have both sides as always and there are a few things you have to keep in mind when you want to prevent frustration as much as possible so a lot of contributing to WordPress is not writing code, it's discussing how to approach a problem, how to solve a problem or if you have an idea of something that should be in WordPress, you have to ask yourself is this really something that will benefit the majority of users or is this only something that will benefit me and a few people, you have to learn the WordPress philosophies, what the project goals are, what the project stands for, for example it is very focused on the user, it is not as much focused on the developer which is sometimes a shame for me but it's the way it is and to some degree it also makes sense and really communicate, communicate is very important ask questions if you don't understand why something was decided the way it was decided and if you still disagree sometimes it really just helps stepping back and coming back later maybe you have changed your mind, maybe you haven't, but then you have definitely the initial level of really being angry or frustrated has gone away after a bit there is a great article that on the web that I will have the slides online later so you can actually click on them or you can Google that it's a great article by Andronation which is pretty much what I'm speaking about here what values are what traits are valuable as a core contributor yes and like I said they always follow up and really important it is do not take anything personal who you are chatting to on the ticket or on Slack they probably don't know you especially when you knew so why would they be mean to you there is no sense in it but sometimes you think that is really rude to close my ticket or reject my patch but it doesn't make sense there is always some argument behind that and that's why you should follow up and try to not be frustrated which is of course easier said than done but you get the chase and there was also a great talk about that at a WordCamp US a couple years ago which I can really recommend to watch as well on WordPress TV so WordCamp US 2015 was for me the next big step I attended that and there was I was working for a big multi-site client and I had seen a talk about multi-site by John James Jacobi JTrip you might know him from he's a body press one of the creators of body press and so I talked to him at the WordCamp and then at some point he said this team is really small so if you're interested in it just go and contribute to it and I was like ok so a few days later I went on Slack I didn't really do anything but I just read some of the chats there and saw what they were talking about and I generally followed a little bit what was going on so at some point I was working on a ticket where I didn't get any response after a while so then I actually decided to join a meeting they have a weekly meeting and first I just said I want to help and then I also said please give me feedback on this ticket I have been waiting for a couple of weeks so the first response I got was this and the second response was this so the gist was that this is a very old ticket it's really complicated and nobody wants to touch it because it's so hard to solve and by the way the ticket is still open as of today 2 años ago and nothing has been done ever since and if I had known that back then that it would be open today I would have quit but I learned to step back and see there are other priorities for the project then fixing this ticket I wanted to work on and sometimes this happens and in that case you can either be really persistent and you want to you can basically say you can you can basically say that that I want to just do it myself you can you can own the ticket and everything that resolves around it and move it forward but that of course is very ambitious undertaking or you can just step back so for me my mindset at this point is it will have its time, I don't know when it's definitely a valid point and problem in WordPress and at some point somebody will be like okay now we need to fix it and I will be happy but you have to learn to step back and yeah that happens there's a great YouTube short film it's ridiculous it's again about following up you always have to follow up and be persistent when contributing when you don't get a response when you get a negative response and you don't know why always ask and ask and communicate and discuss and follow up don't just open a ticket and then never look at it again and hope that somebody will fix it this short film movie who never met so something else I really got out of going into the multi-site meetings is that I found my focus since then I've mostly contributed to the multi-site part of WordPress which has been really valuable not specific that it's multi-site but just finding a focus because as we know you can be an expert in every area you have to specialize so I built more and more expertise and multi-site over the time and then the other advantage you have is that you only deal with a few people there if you contribute to 20 areas of WordPress core you deal with 20 people and it's really hard to make an impression to make an impact to have somebody of these people know you because of course you're splitting all your available time across 20 different parts almost all your efforts into one there's just one or two people who lead this component and if you make an impact with them they can really elevate to the next level because the leaders of the components usually already have they're more known in the community and of course sometimes it's bad that you always have to build trust in order to move bigger efforts forward but that's how we work I guess so you need to invest invest invest and at some point you will get it back but then it's going to be really beneficial it's a long term process that can take a couple months or maybe a years it's usually not a good idea to focus on a very old ticket that what I learned too that ticket was really complicated and bad so at some WordCamp later in 2016 I heard that there were components all these parts in WordPress where you find also a list on makewordpress.org and there was a call for them and I was like ok I looked through all the components and I saw there's this post thumbnails featured image it's also called component it is the smallest component of WordPress core there were only 5 open tickets and there was no maintainer it's just the smallest component I will ask if I can be a maintainer of it and I did and that was ok I became a maintainer but looking back it kind of didn't make sense because I didn't care about post thumbnails at all so it was important that so what I learned is generally you have to make a step you have to go out of your comfort zone if you want to move forward you have to make an effort you can ask can I become a component maintainer of the rest API component or the post component or any part of WordPress and this is what can move you forward you have to make the effort of course sometimes people will recommend like hey this person should become a component maintainer but most of the time it's going to be you that has to move themselves forward so when you do that do that better than me because it's the smallest component the rest API for example is a big component but if you're interested in the rest API you should pick the rest API as your component just because that's your expertise it doesn't make sense to do something else just because it's small don't think you can't handle that because it's too big you just have to go and learn and grow with it so as a component maintainer now it's a little later in the process you're now on the receiving on the other end where you have to make new contributors feel welcome and try to ensure that they don't get frustrated so you're basically now on the other side a little bit and it's very important especially as a component maintainer not only to have you always have to see it in the full picture you have to manage the tickets that come in and of course really important you have to focus on other people's tickets that is a general thing don't just move forward your own tickets that will not bring you further far on the long term of course also you now have capabilities to milestone tickets to say like this trick ticket should be part of WordPress 5.0 for example but if you do that do it reasonably not like I open a ticket and I immediately put it in 5.0 that shouldn't work like that yeah the most important part as a component maintainer is that you now have to make new people feel welcome because really everyone and be aware that everyone who is a core contributor they want new people to help because we need more people to help always so WordCamp Europe 2016 at that WordCamp I personally I finally met where I had been contributing collaborating with before and it was really great to meet the people in person to get to know the people behind just the names and avatars and it was also very productive to talk about some of the issues in person and last but not least you make friends from all over the world and have been with them and hang out with them in person and that's just amazing to get that out of here so I'm gonna skip a little bit timing wise so I was in the time I was working on my thesis at the university so what I did eventually is I contributed much to WordPress core because I didn't want to work on my thesis and the final day before I had to hand it in I got the message on Slack, like out of the blue wow I can be a core committer that was completely overwhelming for me but yeah I couldn't sleep that night anyway because I had to give my thesis in the next day and then I got this and it was over I could not sleep now forever so at that night I stayed up and then I read through the core contributor handbook because I'm a German and I need rules for everything and yeah so it was really exciting for me that I thought I was not at that level but I got core commit and that's really what happens you just you always underestimate yourself and you just have to be more vocal get out of your comfort zone and things will also come back to you and so you will get something out of it so at the next work camp I did my first commit and especially after being a committer I learned a few additional things that are also really valuable if you're not you always have to consider edge cases because it's so badly written the whole thing if you change something here something can break somewhere there and you have to become familiar over time with how it works and if you're getting immune to it you have to trust the more experienced contributors if they say like here there's something that breaks they have that knowledge built that knowledge over a long time and really always be precise communicate that's the most important part and so afterwards I was traveling for a bit to attend other work camps projects and more parts of WorkPress core at some point like we started having a PHP group in WorkPress where we want to move forward people finally get into more PHP versions so that WorkPress can become more secure and most important what I found out at some point there was that I have to be reasonable you have to be reasonable at the time because at some point I picked up too many tasks and I was doing that it's still in my free time and I I was doing that still in my free time so I had to manage it a little better so what can happen because I was contributing so much earlier this year I became part of team Yoast so I got this fancy avatar and they now part time sponsor me for so now I can do what I did before but I can do it confidently and put more time in it than I did before and that can happen to you by contributing but not only to core even to all the other areas people get to know who you are maybe even if they have never met you they know of you and you can get your opportunities like that so companies there are many companies that are looking for people to sponsor in that area so that's it for my story at this point I'm really interested where the next part of my journey will take me but I'm really interested to hear some of your stories if you are interested in doing so what your experiences will be and I'm happy to talk about this further I will be here today and tomorrow and happy to answer questions and I hope to meet many people of the Spanish community and I hope to stop I've been able to take some of the pain points away that you might have in the future or that you already ran into and here's just a quick summary of everything and that's it for me thank you questions it was really interesting and the questions about the Slack meeting how it works the Slack meetings so the questions how the Slack communities are managed so there are local Slack so I'm sure there's a Spanish Slack team but then there's also an international Slack team and the international Slack team is where for example CORE could discussions take place there are many teams for example there's a CORE multisite team and CORE REST API and you can just go in there and on the website makeworkpress.org there's a makeworkpress.org slash meetings it will have a list of all the weekly meetings of all teams when they are and it's really if you're interested in one specific area the best thing you can do is just attend one of these meetings and you don't even have to say something you can just say hi in the beginning of every meeting everyone just does the emoji the wave and you can just you see what they are talking about and then you can figure out what's important for the moment and if you're comfortable doing that at some point you can just say I want to help how can I help this kind of meeting this kind of meeting that you have and talk to the people about the special meetings that you have in the CORE or design ok ok y básicamente normalmente se prepara una pequeña agenda antes de la reunión que se suele circular que un post en en el mail entonces eso se articula los días antes cuando llega siempre hay un líder que es un poco lo que va a funcionar de esa agenda se empieza a hablar de los temas normalmente se intenta e intenta cerrar temas y normalmente las reuniones durante una hora de relojo, osea empiezan a hablar en culto y ahora en culto acaban y luego se hace una recuperación en toda información de la meeting y se completa un post con detalles entonces suele hacer un resumen de donde venimos, a donde vamos y que es lo que se va a intentar hacer casi ok gracias