Blog Post:42 - Revision history

Mark Hershberger at 18:37, 13 February 2017

2017-02-13T18:37:50Z

← Older revision		Revision as of 14:37, 13 February 2017
Line 2:		Line 2:
	\|title=Impressions from the Jerusalem Hackathon 2016		\|title=Impressions from the Jerusalem Hackathon 2016
	\|tags=Hackathon,		\|tags=Hackathon,
	~~\|people=Mark Hershberger,~~
	\|author=Markus Glaser		\|author=Markus Glaser
	}}		}}

Markus Glaser at 10:41, 23 June 2016

2016-06-23T10:41:47Z

← Older revision		Revision as of 06:41, 23 June 2016
Line 7:		Line 7:
	This year’s [[mw:Wikimedia_Hackathon_2016\|European Hackathon]] took place in Jerusalem, Israel (well, this is not exactly Europe, but only encyclopaedists would insist here). [[meta:Wikimedia_Israel\|Wikimedia Israel]] gave us a very sweet welcome, thanks for that!		This year’s [[mw:Wikimedia_Hackathon_2016\|European Hackathon]] took place in Jerusalem, Israel (well, this is not exactly Europe, but only encyclopaedists would insist here). [[meta:Wikimedia_Israel\|Wikimedia Israel]] gave us a very sweet welcome, thanks for that!

	The main focus of the hackathon was working on the community wishlist and several projects could be completed. I want to share a story of a not completed task, though. So before the conference, I picked a task for myself which was to add an expiry date to watchlist items. This, so it seemed, was reasonably challenging, but not impossible to do when you are at a place where all the MediaWiki hackers are. Add a table column, a few user interface items and some logic to expire and remove watchlist entries. However, when looking at the [https://phabricator.wikimedia.org/T100508 Phabricator ticket]], there was a list of 25 blocking tasks which had to be resolved before. Why was that? It turned out that watchlist code is one of the oldest code areas in MediaWiki and no one had touched it for years (except for some necessary adoptions). The watchlist code seems to be spread all over the place and has to be refactored in several ways. The good news is, a team of core developers took on the task and it will be way easier to work on the watchlist in the future. There are several takeaways from this.		The main focus of the hackathon was working on the community wishlist and several projects could be completed. I want to share a story of a not completed task, though. So before the conference, I picked a task for myself which was to add an expiry date to watchlist items. This, so it seemed, was reasonably challenging, but not impossible to do when you are at a place where all the MediaWiki hackers are. Add a table column, a few user interface items and some logic to expire and remove watchlist entries. However, when looking at the [https://phabricator.wikimedia.org/T100508 Phabricator ticket], there was a list of 25 blocking tasks which had to be resolved before. Why was that? It turned out that watchlist code is one of the oldest code areas in MediaWiki and no one had touched it for years (except for some necessary adoptions). The watchlist code seems to be spread all over the place and has to be refactored in several ways. The good news is, a team of core developers took on the task and it will be way easier to work on the watchlist in the future. There are several takeaways from this.
	* First, never misunderestimate the complexity of code. Even seemingly simple tasks can become a refactoring hell.		* First, never misunderestimate the complexity of code. Even seemingly simple tasks can become a refactoring hell.
	* Second, it is not always the experts who trigger a reduction of technical debt. Had the community not voted this task very high, probably the old watchlist code would sit there for another few years.		* Second, it is not always the experts who trigger a reduction of technical debt. Had the community not voted this task very high, probably the old watchlist code would sit there for another few years.

Markus Glaser: Created page with "{{Blog Post |title=Impressions from the Jerusalem Hackathon 2016 |tags=Hackathon, |people=Mark Hershberger, |author=Markus Glaser }} This year’s mw:Wikimedia_Hackathon_201..."

2016-06-23T10:41:05Z

Created page with "{{Blog Post |title=Impressions from the Jerusalem Hackathon 2016 |tags=Hackathon, |people=Mark Hershberger, |author=Markus Glaser }} This year’s mw:Wikimedia_Hackathon_201..."

New page

{{Blog Post
|title=Impressions from the Jerusalem Hackathon 2016
|tags=Hackathon,
|people=Mark Hershberger,
|author=Markus Glaser
}}
This year’s [[mw:Wikimedia_Hackathon_2016|European Hackathon]] took place in Jerusalem, Israel (well, this is not exactly Europe, but only encyclopaedists would insist here). [[meta:Wikimedia_Israel|Wikimedia Israel]] gave us a very sweet welcome, thanks for that!

The main focus of the hackathon was working on the community wishlist and several projects could be completed. I want to share a story of a not completed task, though. So before the conference, I picked a task for myself which was to add an expiry date to watchlist items. This, so it seemed, was reasonably challenging, but not impossible to do when you are at a place where all the MediaWiki hackers are. Add a table column, a few user interface items and some logic to expire and remove watchlist entries. However, when looking at the [https://phabricator.wikimedia.org/T100508 Phabricator ticket]], there was a list of 25 blocking tasks which had to be resolved before. Why was that? It turned out that watchlist code is one of the oldest code areas in MediaWiki and no one had touched it for years (except for some necessary adoptions). The watchlist code seems to be spread all over the place and has to be refactored in several ways. The good news is, a team of core developers took on the task and it will be way easier to work on the watchlist in the future. There are several takeaways from this.
* First, never misunderestimate the complexity of code. Even seemingly simple tasks can become a refactoring hell.
* Second, it is not always the experts who trigger a reduction of technical debt. Had the community not voted this task very high, probably the old watchlist code would sit there for another few years.
* Third, a hacky solution might have been possible. However, this is not the way to go unless we want to have even more bad code in the software.I am very delighted to see that the Foundation team has tackled the task even though it is more time consuming than initially thought.
It is a good attitude in our movement to take community wishes very serious.

So instead, I ended up translating some [[mw:How_to_become_a_MediaWiki_hacker/de|entry pages for developers]] into German and hope, this helps someone to get started and find their way into MediaWiki hacking. In that course, Manuel Schneider and I also worked on a [[mw:Template:Developing_extensions|navigation for extension developers]], which should provide them with easy access to all the necessary material about extension development. This is not finished yet, and we appreciate your input on what's important for MediaWiki developers.

Special thanks go out to [[meta:User:Maor_X|Maor Malul]], who took us to the best Kurdish restaurant in Jerusalem and showed us around his very lovely neighbourhood, including the synagogue.