DrupalCon Portland 2013

Cómo organizar bien los sprints y la formación

Andrea Soper, Jess, Addison Berry, Cathy Theys  · 


PDF (pincha para descargar)



Extracto de la transcripción automática del vídeo realizada por YouTube.

so welcome as Kathy was saying this is the session about sprinting and mentoring and that lot if you have questions please write them down or tweet them so that you remember them and ask them at the end of the session because we are going to be kind of switching

between and we don't want to like interrupt the flow our goals today are to introduce the contribution training resources and all the things happening at the events to get you ready for for the sprints and give you the recent resources to plan a contribution

sprint or training in your own user group or company or drupal events our slides and handout are linked from our session page at portland 2003 drupal.org / node / 2433 the urls and resources that we mentioned during the talk are linked from there so you don't

have to write them down you can just go to there and check it out and then there are also some other resources if you have one of the postcards that you can pick up at our booth you there will be a QR code on the back that you can that will take you to some

more resources as well so um I'm Andrea I've been working in Drupal or a lot a few years since 2006 and have been working in core and ink or mentoring since Denver which would be a year or so ago and so my name is Jess I'm xjm on drupal.org uh

and I sort of started the core contribution mentoring program I'm also one of the four members on the views in Drupal core initiative team word for Cole leads and finally I also work in the office of the CTO at aquia this is very recently my job title

is code and communities strategist and what that means is that I basically breezes my boss and I work on course stuff so it's actually a full-time job for me now I Madison berry add one son on the interwebs I'm the director of education at lolla bod

and I've been doing a lot of drupal stuff for a long time but obviously the director of education my focus is on sort of training and education and so I've been very involved with the Drupal ladder and the core mentoring stuff in terms of trying to

provide underlying training for everybody so that they feel comfortable and confident with with what it is that they're trying to get into so yeah that sounds good hi I'm Kathy phase I'm yes CT on drupal.org and I work for compress which is based

in Hamburg Germany and I do community contribution as part of my job and then I blog about community contribution and I'm a regular mentor in the weekly Cora mentoring IRC sessions that are every week and I also organized the global sprint weekend that

was in March so so between us we've led a nine sprints in the last year and Kathy lette organized the global sprint as she was saying which and then if you look around the room some of you have picked up your shirts these are the people who will be mentoring

on Friday as well if you are signed up and you have don't have a shirt yet you should go to the men touring booths and pick it up so today jess is going to tell us a little bit in a soon about the case for core contribution and Addison will talk about

the some contribution solutions and cathy is going to tell us a little bit more about planning of sprints and I will tell you what to expect in the in the sprint this friday and then when that's done well we'll do our questions which we do ask that

you wait till the end that we're excuse me that you wait till the end so the we can continue our flow and pace and all that sort of thing which I'm clearly having trouble with if there are only three things that you get out of the next hour we hope

that you will feel confident with finding and using resources and the tools to help you plan a successful sprint it needs to be like maybe how to find the people and how to find the people that you might need to to help you along the way we also think that

it would be good if you remember to plan to deal with development development environment issues which almost always happen when you have a sprint we don't expect you actually to know how to to set up a devstack on every single different development environment

but we do expect for you to maybe collaborate and anticipate a problem and have potential solutions and we can try to give you some advice on those things and we would also hope that you would learn to prepare task list in advance so that when people and we're

going to go into this a lot more later but it it really does help to have reviewed the tasks and be able to help people to choose something that is more suitable to their abilities but first let's talk about some basics so we're all on the same page

what is a sprint actually does anyone have like any kind of things that they think a sprint is all about anyone stand up jump up it down no okay running fast way running fast yes run fast is my favorite what do you see up there zoom okay so so it's prince

is yes it's running fast but it's also when we when we all get together and in a coding context this when we all get together and we especially it like an event like this it's the only time when some of these people can get together in one place

and work on things and so a lot of things get done at once so it goes fast and that's I think why it's called a syringe so but what are what does friend is is it as a focused contribution event where people who write code and work on code and write

documentation and these sorts of things get together in one place is it generally very fun event I really very much enjoy it and Ruiz a lot taller than I am and so I'm going to talk a bit about the case for core contribution or the problems that were actually

trying to solve here and I'd like to start by telling the story of how I actually got involved with Drupal core because I faced some challenges that I think a lot of new contributors do so two years ago I was trying to upgrade the tax on tea access control

module to Drupal 7 and I hadn't ever looked at triple seven when I started but with some help I was able to get about eighty percent of the way through it before I got stuck on this one thing so I talked to some people in IRC and we eventually came to

the conclusion that we needed a new alder Hulk and core hook field widget form altar in case anyone is curious so we're like okay we're going to do this we're gonna file a court issue asking for this hook so we filed the issue and I kid you not

two hours later son had created a patch adding the hook decor in the posted on the issue two hours later I came back from lunch and it was there but the problem was that it was failing tests and I knew that there was a bug in the patch but I had no idea how

to fix it so by this point my port of TAC was about two weeks late actually for a contract that I had and I started asking you know what can I do to help this patch came in faster I can't fix it myself so what can I trade and people suggested that I should

just work on other core issues so this was two years ago and my reaction to that was kind of so I'm not a core developer I don't know what you expect me to do I don't know anything about this stuff now his fate would have it there were actually

two things that happened that same week first is that checks every note checks while the Hungarian guy very passionate contributor um he asked an IRC for someone to update a patch just removing one blank line that he'd added by accident and so I thought

huh okay this is a core issue and I know how to do that so I'm gonna do that so i did it i downloaded the patch up light it made this one small change and the upload a new patch and it was such a tiny ridiculously simple thing Jax could have of course

fix it himself in like 30 seconds flat but instead he gave me the opportunity to take that first step and cross that line in my head the second thing that happened that same week is that the issue summary functionality was deployed on drupal.org for anyone

who's not familiar the main post of a drupal.org issue that the top part before all the comments is it issue summary and it can be edited so the idea is that anyone who's looking at the issue can collaborate to update it describe what's been discussed

and describe the issues current status so instead of having to read fifty or hundred comments to figure out what's going on you just read the summary by this point my port of like I think I mentioned that there was two weeks behind schedule after after

a couple of weeks it was actually rtb seat someone else fixed it for me after I started doing some of this work and then it was actually just stuck near the end of a big backlog of other our TBC issues in summer 2011 there were just two core committers at

the time and they it's a lot of work to come in all these patches so I figured that if I could write issue summaries for those issues save the core promoters time when they reviewed them then they'd be able to get to my issue faster so I started writing

issue summaries I took one issue every day read the whole thing research things in it that I didn't understand and then tried to write a concise up-to-date summary and a lot of things actually happened as a result of me writing those summaries beyond even

helping my patch gettin faster the first was that every now and then I come across makes you that I actually knew how to fix and thanks to the confidence that checks had given me I was able to just create patches for those issues myself another thing that

happened is I actually figured out there were a lot of other dripless in a similar situation to me who had an interest in contributing to these issues these core issues but had no idea where to start and issue summary seemed like a fairly approachable thing

so I started encouraging other people throughout issue summaries for issues as well and that was one of the seeds for the core contribution mentoring program and finally completely by accident I taught myself about core by reading an issue every single day

and researching it and then trying to explain it to other people I learned a lot I started writing on a tests for core bugs and fixing more of those bugs myself I started reviewing other people's code and it was such an entirely different experience from

working on a contributed module instead of just hacking away on things until they worked I actually learned how to do them in the right ways so that's why I think the core is the best way to learn you learn a lot about Drupal first of all and you interact

with more people and get more feedback than you do in contributing other people at the same time and finally you also get this ownership in Drupal and this empowerment to solve the problems that you encounter in your job and your client work in your volunteer

[ ... ]

Nota: se han omitido las otras 5.453 palabras de la transcripción completa para cumplir con las normas de «uso razonable» de YouTube.