 Good morning Fortunately that cut into the time that I'm supposed to have already so we're gonna make this really quick. No I'll be speaking for about 20 minutes I'm left some time at the end for question and answer hopefully And mostly I just want to thank you all for coming Like you I'm here to have discussions. I'm here to participate and Hopefully even build some stuff What I wanted to try to do with my time today is really communicate a little bit about what we're doing At what committee of foundation and what we're doing with the product and the technology teams what we've done What we're going to do next and really how to engage with us So there's a lot to celebrate. I think About what we've done in the last year There's a number of initiatives that we've done That involved a lot of people that were multi-year efforts that Involved a lot of people that pays benefits for everything that we're trying to build and do the single user logon was a Was a many year effort Just like the HTTPS was this year. They came to fruition and They are both things that went pretty well coming off of the multi-year effort the hip-hop virtual machine is also something that we did this year which greatly helped reduce the The reading too much off my slides already The editing experience in the load time by 50 percent We also decreased the pain times on Page load times by reducing them by 40 percent. This was done by the performance team performance is really important It's it's where we all benefit. It's where our users benefit the most and it's An area that we want to see improve and expand this year as well The page view definition that was rewritten this year was also very important the analytics team helped redefine making the page view definition go from a Sample log into a unsampled log which gives us a much more accurate description of what's going on across our site Training that a into an API has allowed many teams to start using that for development Which is a very good thing as well. The analytics team has done a number of dashboards with the different teams and enabled the more awareness through the extending the event logging the Objective revision I have to say or as the revision evaluation service is really the machine learning service that helps us Get much better quality across our entire Set of software. This is something I hope to see expand into a lot of the different features as we develop over the next year And then the release team did a great job Really getting every everybody on fabricator this year as product teams. That's the best way to engage with us and You'll see a little bit further. We have that's the primary way to actually engage with us The research team has done a dramatic amount of work this year One thing that I'd like to call out is the new editor retention Initiative that was done through tea house the reason why I bring that up is because I think it has a lot of potential and it It's highlighted here But I think these are the types of things that we have to do to move product further by engaging with our users more directly the There was also a number of design research initiatives that were done this year that really really really Help how we're developing our software through a be testing through surveys and that paid a lot of dividends to To the visual editor work that went on this year Research has also done a lot to open our data sets and provide a lot more information for people to gather and to understand What's going on? Rest Base was rolled this year. There was a lot of improvements that that came from that work Both in the save times editor switching and the reduction of our overall html load API performance in general has been An initiative where we are looking much closer at the performance and the analysis of our APIs and the simplification and the documentation around them The improved reliability of wick media labs was an issue done by the operations team There were some issues earlier in the year that I think they recovered and have done a much better job of actually improving the lab service Visual editor continues to expand a lot of features were included this year including the math extension improving upon the quick loader and The incorporation of the graph editing That mean the graph extension There's a lot to be a lot more is going to be done or this year But we really have started to expand now that we're in English wick media The content translation tool resulted in over 40,000 new translated articles this year This is another thing that is providing a lot of new opportunities for us to engage more users Echo notification enhancements We're I like them personally. I'm using them a lot and we're gonna have the ability to do cross wiki notifications very soon Parceler improvements around html size and performance were also done a flow beta was Released the graph extension itself has gone through a lot of iterations and now there's dynamic graphs Which year has been working on that show a lot of promise search completion Suggestor is working on improving the relevancy of How people actually discover all the contents across the site the map tile service and the wiki data query service Went into limited production and this was an opportunity for us to work with operations to really explore How to expand things out of labs in a more bare metal way and there's probably too many highlights There's I'm there's a lot that I'm missing But I want to I want to try to make sure that we celebrate the things that we are doing in the progress that we are making We've reduced page load time in mobile web. There's been a lot of Android and iOS additions this year The tab browsing and the link previews as well as the map service showing up in Android are all great things iOS with share a fact and improve search as well as a read more section all have opportunities to Be showcased in desktop as well and that team is continuing to explore those The banner history feature that was entered into central notice allows for better understanding and testing of how banners perform and then last but not least the community wishlist survey That was introduced late in November has provided a better engagement opportunity for the community tech team to Directly interact with our community to find the the primary things that we want to do to actually increase and improve our admin tools I'll talk more about that later So what are we doing next in 2016? These are just a few things Being here going through our annual planning The constant feedback loop with individual teams will expand and improve upon everything that we're trying to do over the next year we're Mobile editing and mobile speed improvements are at the top of our list These are things that we absolutely must do in order to try to improve our overall software API efficiency and understanding and performance are also key on our list to actually improve Cross-wiki features such as notifications and search being able to explain What we can see and where we can see it data and feedback tools such as quick survey and some of the data API's that we're going to be able to continue to improve upon and bringing our res translation graphs Maps wiki data query service UI consistency and making sure these types of things actually get built into more and more features The engagement and prioritization Component of this is really us as a foundation doing a better job of Making it clear what we're working on why we're working on it and when we're going to be working on it One of those things that I brought up earlier was a community wishlist survey. We had over a hundred community Suggestions but fourth these are the top ten There's gonna be a discussion tomorrow. I believe We're at the session where we'll go more in depth about how that worked and where we're going to go with it I think that this is a good example of how we're we're trying to do a better job of actually Engaging with people getting the right things and building the right things So working with foundation teams The primary way to work with us is really through our team fabricator boards making suggestions Engaging in the discussions that are ongoing constantly just like we did for the developer summit are the primary way that we would like you to engage with us at this point Participating in planning really comes from engaging in the team wiki pages the mailing lists the talk pages IRC and our fabricator boards Monitoring the progress of our goals and our projects comes from going to our we have set up our goal pages on media wiki and we're trying to do a much better job of putting those up early and Announcing them on our mailing lists and engaging people On a more regular cadence so that there is more warning and there's more participation in discussion that can occur We've also started initiative around product showcases this year We're actually trying to show the work that we're developing so that you have a much more visible way to interact with us and then lastly we've also created a product hub where you can see the status you can see metrics and outcomes as we perform and There's a number of jump points within there to go to all of these pages for each product team Really more communication is the whole key. We want more blogs We want to continue to work with developer relations and community liaisons to To talk about the things that we're developing We're looking at our development process and we also are trying to engage by saying when we're running user tests What surveys are running the results that come from them and have a discussion around our strategy? the teams at the foundation are broken into technology groups and Into a product group and it's I just provided these really as jump points to be able to go deeper into those particular areas And teams that you can work with and lastly I just wanted to share some of the milestones that we have currently going forward the goals are for This current quarter are posted through January and March on media wiki You can engage with each of the teams and ask them directly how How they came up with it what the rationale was around it? But we want like I said earlier to do a better job of doing an earlier cadence on these sorts of things so we want to try to have our planning and drafts for The following quarter for April through June done in February and March and ideally we want to get to a nine to twelve month Roadmap where you're gonna have a much longer window to actually engage with us The planning and review for a lot of the work that we're doing at the foundation is Going to be happening around the annual plan for 2016 2017 from now until June And I highly encourage you to engage with us So I want to keep it relatively short and provide an opportunity for questions and answers but I wanted to make sure that we had a a Broad picture of kind of where we've gone where we're going this event the annual plan and ongoing conversation is directly with the teams as they develop their goals is the best way to engage with us right now and So thank you for today. Thank you for the discussions that we're going to have and I look forward to participating with all of you Thank you And I one of the things I would love to celebrate is the as is back on the community wish list side of things we've a lot of folks put in a lot of work here and I want to make sure that everybody knows the people because Like one of the things that we're hoping happens here at the summit is that you talk to these people about What the community wish list items were so? Danny We're yes, so Danny horn here and I'll Danny. I'm if you don't mind me putting you on the spot I'm gonna let you introduce the rest of the team. Hi everybody. I'm Danny. I'm the product manager for the community tech team We also have Ryan Calderi our technical lead Niharika coley and Francis oh good. Oh, she's over there. There's Francis Yeah, we would absolutely love to talk to everybody about We're basically starting 10 huge projects at the same time. There's a lot of conversations we need to have so that will be great I will talk to y'all soon Great yeah, I think a lot of the projects that you see here. These are all things that that I know We've you know, we've been talking about a lot of these things for a long time and talking but not really like having a good concrete plan for them and so I love the fact that the Community team has been working on actually figuring out How we move forward on these things and starting with you know the first step on these this this year I mean 10 projects. That's a huge amount of work for a very small team to do but with With the the help of everybody here We can get it done and that's and not just everybody here But everybody in the world that is a programmer like we want to get those folks Kim That's also something that's gonna be highlighted at the hackathon as well, right? Opportunities to work on this list so So anybody want to comment on any of these projects like there'd be a good start like is there is there anything that strikes? Anybody here is like like oh my god. We if we do one thing. This is the one thing we have to do Yeah, okay, right I think for number Five there's an option. We could just enable and underlying library So it's just a simple matter of configuration. There's a global you said it's fine so Yeah, I think that that having that so at this point there's starting to be people I breaking with with with our plan here by holding the microphone and and and being microphone guy and Letting people sort of sit in their seats and do this so if you can line up at the microphones on either side and we'll and and we will Take people in order that in their order in line so yes, I Guess I kind of had an unfair advantage because I was sitting literally right in front of the microphone, but Considering the broad scope of the product department. What would you say is the underlying mission of the product department? Or in more operational terms, how do you decide what to work on on what not to work on? so each individual audience right now is Definitely has the responsibility to take in a number of different feedback loops to figure out their prioritization as a larger product department we're doing We're doing some strategy development as part of the annual planning where we're gonna open it up and now have active discussions around it This is it's new which relatively new I started just technically two months ago But I've been at the foundation longer than that We're really trying to drive People to the teams themselves because they're closest to what's going on They understand the audiences and so like I said try to work through their fabricator boards Try to work with their mailing lists try to work with their conversations as they build their goals and their planning All right, so on the community wishlist survey. I just want to comment I think it's all about number three central global repository for templates Yeah, he said it's all about number three Okay, good Talking to it. Yeah So that's better So yes, I just wanted to add that you know many years ago We set up commons for central repository for images and it made it hugely easier To reuse things between projects and between languages And it's really really really been missing for templates modules and gadgets It creates an extra complication from authors and maintainers and there's no good localization and so there's been a lot of difficulty in terms of making these materials actually available for use on What is now several hundred separate weekies? So in my opinion that is the most important thing we can possibly do and I think a lot of people will get benefit from it Thanks. I'll jump in real quick there to say that About four years ago team and I wrote some code that did that for gadgets and never finished it It is my understanding the community tech team has already begun picking that up and polishing it and doing things to it. Cool To that I would add Another indication of how important that is is I think nine out of ten of these can be implemented using a gadget Which is not necessarily advisable, but It kind of illustrates how important having like a central maintainable repository for that would be Thanks If you're interested in talking about number three, I have an RFC called Shatter namespaces that would take care of templates and Lua modules I'm gonna schedule in for an unconference slot if you want to talk about that. All right, that's 20 minutes Thank you