Change Details

== Session title Developer Wishlist == Main topic [[https://www.mediawiki.org/wiki/Wikimedia Developer Summit/2017/How to manage our technical debt|How to manage our technical debt]], [[https://www.mediawiki.org/wiki/Wikimedia Developer Summit/2017/How to grow our technical community|How to grow our technical community]] == Type of activity unconference session == Description === 1. The problem Developers are people too! Just like readers and editors, a poor user experience can drive them away and make them spend their time on some other project instead, while a great user experience can allow them to work more focused and more effectively. Developer experience (DX) affects everything from the slope of the learning curve to volunteer and staff retention to work efficiency. Despite the importance, DX does not get much "official" attention; the continuous integration infrastructure has an owner but most other related functionality (such as documentation and consistent interfaces, logging and error reporting, debugger and development environment integration) is improved on an ad hoc basis. That tends to result in prioritization reflecting the needs of the people doing that ad hoc work; even if they want to focus on what is going to have the highest impact, they don't have the resources to figure out what that is. Wikimedia tool/feature development for experienced editors used to suffer from the same problem, and the [[https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey|Community Wishlist]] proved to be an effective tool to get around that problem. Maybe that success is something that can be copied; should we try to create a Developer Wishlist that can be used to direct attention to the important platform-level issues the same way the Community Wishlist directs attention to the important feature-level issues? === 2. Expected outcome Agreement about a Developer Wishlist being a worthy goal, and a process for creating it. Or agreement that this is a silly idea and should not pursued. === 3. Current status of the discussion === 4. Links == Proposed by @Tgr == Interested attendees (sign up below) == # @Qgil # Add your name here

== Session title Developer Wishlist == Main topic [[https://www.mediawiki.org/wiki/Wikimedia Developer Summit/2017/How to manage our technical debt|How to manage our technical debt]], [[https://www.mediawiki.org/wiki/Wikimedia Developer Summit/2017/How to grow our technical community|How to grow our technical community]] == Type of activity unconference session == Description === 1. The problem Developers are people too! Just like readers and editors, a poor user experience can drive them away and make them spend their time on some other project instead, while a great user experience can allow them to work more focused and more effectively. Developer experience (DX) affects everything from the slope of the learning curve to volunteer and staff retention to work efficiency. Despite the importance, DX does not get much "official" attention; the continuous integration infrastructure has an owner but most other related functionality (such as documentation and consistent interfaces, logging and error reporting, debugger and development environment integration) is improved on an ad hoc basis. That tends to result in prioritization reflecting the needs of the people doing that ad hoc work; even if they want to focus on what is going to have the highest impact, they don't have the resources to figure out what that is. Wikimedia tool/feature development for experienced editors used to suffer from the same problem, and the [[https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey|Community Wishlist]] proved to be an effective tool to get around that problem. Maybe that success is something that can be copied; should we try to create a Developer Wishlist that can be used to direct attention to the important platform-level issues the same way the Community Wishlist directs attention to the important feature-level issues? === 2. Expected outcome Agreement about a Developer Wishlist being a worthy goal, and a process for creating it. Or agreement that this is a silly idea and should not pursued. === 3. Current status of the discussion === 4. Links == Proposed by @Tgr == Interested attendees (sign up below) == # @Qgil # Add your name here Etherpad: https://etherpad.wikimedia.org/p/wikidev17-devwishlist

== Session title Developer Wishlist == Main topic [[https://www.mediawiki.org/wiki/Wikimedia Developer Summit/2017/How to manage our technical debt|How to manage our technical debt]], [[https://www.mediawiki.org/wiki/Wikimedia Developer Summit/2017/How to grow our technical community|How to grow our technical community]] == Type of activity unconference session == Description === 1. The problem Developers are people too! Just like readers and editors, a poor user experience can drive them away and make them spend their time on some other project instead, while a great user experience can allow them to work more focused and more effectively. Developer experience (DX) affects everything from the slope of the learning curve to volunteer and staff retention to work efficiency. Despite the importance, DX does not get much "official" attention; the continuous integration infrastructure has an owner but most other related functionality (such as documentation and consistent interfaces, logging and error reporting, debugger and development environment integration) is improved on an ad hoc basis. That tends to result in prioritization reflecting the needs of the people doing that ad hoc work; even if they want to focus on what is going to have the highest impact, they don't have the resources to figure out what that is. Wikimedia tool/feature development for experienced editors used to suffer from the same problem, and the [[https://meta.wikimedia.org/wiki/2015_Community_Wishlist_Survey|Community Wishlist]] proved to be an effective tool to get around that problem. Maybe that success is something that can be copied; should we try to create a Developer Wishlist that can be used to direct attention to the important platform-level issues the same way the Community Wishlist directs attention to the important feature-level issues? === 2. Expected outcome Agreement about a Developer Wishlist being a worthy goal, and a process for creating it. Or agreement that this is a silly idea and should not pursued. === 3. Current status of the discussion === 4. Links == Proposed by @Tgr == Interested attendees (sign up below) == # @Qgil # Add your name here Etherpad: https://etherpad.wikimedia.org/p/wikidev17-devwishlist