Transcripción
Extracto de la transcripción automática del vídeo realizada por YouTube.
all right I'm gonna get started and if people come in then they'll find us even meet us halfway through welcome everybody this is my talk about taking the plunge and becoming a contributor my name is alex ross i'm a senior architect at nbcuniversal
and on the various channels on the internet I'm blean or glean 18 so you can find me an old all the various places I tend to talk really loud so if it gets too loud because of the speakers let me know and I'll move the mic I can't tell how that
it is back there or if you can't hear me at all so basically before I got started contributing I was doing what most people are doing and using Drupal and getting what I can out of it not doing anything to kind of contribute back to the community i was
using bunch of modules i was using a base theme i was doing all these things I would you know search around when I had questions or problems but I was never doing anything kind of to get back so like most people it started when I found a bug right that's
usually the first place that people end up contributing and you know I submitted a bug report I tried to fix it that didn't go so well I talked to a couple people in the community and you know eventually I got to the point where I was able to get some
help and get some guidance from some of the community community members who around at the time and I finally got a fix in place and I submitted a patch and it was accepted into Drupal core and I was very exciting and actually this is the comment from that
original post so I don't know if you can read it but I was very excited about my first patch getting in and web chick was threatening to go get jell-o and feathers and then whistles innocently so yeah this was about four five four years ago and since then
I've become the maintainer of about a dozen modules on drupal.org I've contributed patches back to core into a bunch of controls and written documentation I've submitted bugs I've submitted feature requests I've answered questions I've
been a mentor of Don trainings I've started kind of Mentor e-type activities at the local drupal user group in New York so I've done all of these things and I figured this was a good opportunity to talk about those things and talk about how you can
kind of get back to Drupal community and and get involved so I'm going to get started with how you can contribute so these are some of the ways is not all the ways but they're most of them that you can actually give back to Drupal community and become
a more active member become a contributor and I'm going to be going over each of you is in pretty good detail some of them are much easier to explain and talk about than others but it doesn't necessarily mean they're easier to do but as we go through
you'll see what I'm talking about so the most common way that people think of when they're talking about contributing to Drupal is just by you know writing a bit of code making a patch fixing a bug creating a new feature submitting that patch back
to the control module or to juba org so we're going to talk about that we're actually gonna do it by the end of the presentation writing and maintaining your own control some contribs I'll and very easy to maintain some of them are panels right
huge complex beasts that require you know 10 people to kind of really get together and deal with so we're going to talk about how you can actually go about contributing your module and your code back to core back to the community rather we're going
to talk about how to review patches right if you come across a patch that hey it's been useful for you talk about that go back on the issue and say hey I use this patch it worked for me or I use this patch and it totally screwed up everything and you should
never use it both of those pieces of information are equally important to the person who's either maintaining the module or the core maintainer if the patch works that's great information if it doesn't work that means that there's more work
to be done but now we have another Pinot another data point to work off of mentoring someone right this is a great way to contribute to the community on friday and i'll talk about this a little more there's a whole big sprint for for newbies and people
who are just getting started contributing and there will be a whole bunch of people in don't know what color t-shirt is yet because I picked it up but in a hour yellow t-shirt who will be there mentoring others and helping you get started as a contributor
in one way or another triaging issues all right not the most sexy of contribution as you can you can do here but very very important there are hundreds of new issues on drupal.org every day and some of them are duplicates some of them are triplicates somewhere
there mark you know are totally in the wrong project and just need to be moved some of them need to be confirmed and so on so we're going to talk about that submitting a bug report in a feature request right how do we actually do that properly and by properly
I don't mean what form do you go to I mean there are kind of right ways and wrong ways I'll talk about for example why it's not a good idea to submit a bug report by saying wow your code is broken you guys suck why haven't you fixed it yet
right things of that nature and then something is as straightforward as summarizing an issue hugely important there's been an initiative for a couple year and a half now to start going through and summarizing issues on drupal.org especially for core some
of those issues can get really long and nasty to try and figure out and try and groc so just you know contributing that way can be a great way to get started and then finally writing documentation everybody always talks about document everything document everything
and that's true we want to document everything but there are again you know different ways of doing that within the Drupal community and each of them are valid in their own way and we're going to talk about kind of how how you can go about contributing
by writing documentation so that's what we're going to talk about we're going to start with writing documentation you basically go in order of ease of explanation not an ease of doing which I mentioned before so writing documentation the first
thing I like to remind people whatever form your documentation takes and wherever you're writing it and we'll talk about those always assume that whatever code you're writing documentation for is or whatever whatever process you're writing
documentation for assume you're going to need to do it again in about two years when you're drunk if you assume those things right then you will always write good documentation because you will always need to you know you'll always kind of picture
it as as though you're going through this again for the first time because nobody can look at code two years later when they're drunk and understand what in the world they were doing with it without good documentation so on drupal.org there's a
good amount of documentation up there and we're gonna go take a look at that and actually you know play around with it a little bit if you're following along with documentation on drupal.org and you see something wrong fix it right there right then
if you see something needs clarification fix it right there right then if you get into the habit of doing that over time if everybody gets in the habit of doing that over time the documentation on drupal.org and in other places which we'll talk about is
going to get better and better so another point that I like to bring up if there's no documentation already for the thing you were doing whatever that thing is write it down as you go right if you can take out an old fashioned pen and piece of paper believe
it or not they still work but write it down as you go these are the steps I took this is what I clicked on this is what I this is the wrong path I went down right those are good for parenthetical saying don't do this even though you may think you should
all that is really good information and if you can add it to the documentation that's going to be hugely helpful to the next person that comes along and don't forget that next person might be you in two years when you're drunk so let's do that
real quick I don't know if the internet is working right now so I have Eclipse have a back-up plan if it isn't did it uh where'd that link go and won't let me click on my link oh well um so I'll bring up my backup plan here so documentation
there are a couple ways to document what's going on there's documentation in code right if you're actually sitting in writing code document your code right wherever you're doing it there's documentation on drupal.org which is what we're
going to talk about mostly right now and there's documentation that can happen in your in your blog right on your personal site where ever so documentation on drupal.org if you come here close that there's documentation link right up at the top bring
through a page just like this and if you click around one of the areas that the documentation breaks it down into and you might be in all likelihood you'll get to one of these pages based on a google search anyway but if you get to one of these pages for
example working with nodes and content types right and you see something that is incorrect right you as long as you log in to juba org you can edit it right away right here there is no requirement to you know that permission to edit the documentation all you
need is drupal.org account that's it so log in head into here say hey this documentation is only appropriate for Drupal 7 or it's a beginner or all this good stuff and then there's the actual documentation at the bottom very often as I'm going
through a process i have this page open in another tab and i just go through and i write my documentation hugely important ok so that is documentation i'm going to keep going so the next thing i want to talk about is summarizing issues all right like i
said there's been an initiative for for a little while now for summarizing issues again all you need to do this is a drupal.org account so it's that there's a pretty low barrier to entry in terms of getting involved when you're summarizing
an issue we want to summarize everything in that issue right this is a deceptively simple process you know people think Oh summarizing issue i have two free minutes i can go and summarize that issue it almost never takes that long it almost always takes you
know half an hour or longer because what you need to do is really understand you know the entirety of the issue and if the issue is at a point where it means summary chances are there's a lot going on so let's take a quick look at at an example of
why this is really useful there was an issue in 2008 that I remembered very vividly and I'm going to bring that up this issue if i scroll down long enough has i'm not gonna go down it has about 600 it's 500 comments and it was about it is it is
a really really horrible annoying ie ie bug I know naive ugh where you can't have more than 31 style sheets on a page it'll just ignore the 32nd and on like you won't tell you won't throw an error just ignores it and suddenly you add one more
module and your entire explodes for no good reason so we needed to figure out a way to deal with it I'm not gonna go into the details of how we did but looking through these comments if you were to come into this conversation on I don't know let's
say January 6 2010 and someone was going to say to you hey what's going on that issue do you know how to fix the problem there is no way you would be able to figure out what in the world was going on and if we scroll all the way back up and I'm not
going to scroll I will use my little magic scroll bar here um all that's really in here is hey IE breaks when you add you know 31 more than 31 style sheets here's a link to Microsoft that's it right so grokking this issue 2 in it this is why I
remember it so it took me like a day and a half to really understand that the the path people were taking because a lot of people were arguing back and forth so an issue summary right this is why they're so important it would be it was nearly impossible
to figure out what's going on here so here's an example of a more recent issue from last year end of last year where they did go through and and I don't know whether this was the person who initially open the issue or this is someone who went back
and did it but they actually went through and they did an issue summary for this and just to give you an idea of how much easier this makes life what's the problem okay when you use the ckeditor in Drupal 8 there's no accessible way to move around
the buttons that's really the issue and here's some screenshots that show hey look no toolbar I can't move around the button that's a problem for accessibility what's the proposed resolution hey we need a drag-and-drop click you are the
drag-and-drop click you I should be driven from an HTML form which underlies it so that you know someone using accessibility software can can take advantage of the form instead of the actual drag name dropping okay there's a proposed resolution what tasks
are remaining determined solid implementation and so on so the key points here are raining tasks up where we have the problem proposed resolution remaining tasks whether there's any user interface changes or API changes and then the original post we always
like to keep the original post so that when the person who really posted it comes back later and says ah this wasn't the issue i was talking about we can refer back and figure out what went on there so hugely important to do these and I don't know
if this is the right one yes there is even a node on drupal.org which has a template for these issues summaries yes sure it's definitely until the question was this is relevant for clothes tickets I would argue that in the perfect world it would already
[ ... ]
Nota: se han omitido las otras 7.175 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.