FYI :)
---------- Forwarded message ---------- From: Erik Moeller erik@wikimedia.org Date: Wed, Jan 9, 2013 at 4:43 PM Subject: Announcing Patrick Reilly as Site Performance Engineer and Senior Technical Advisor To: Staff All wmfall@lists.wikimedia.org
Hi folks,
it's my pleasure to announce the promotion of Patrick Reilly to the role of Site Performance Engineer and Senior Technical Advisor.
It's been planned for a long time for Patrick to focus on site performance as his next step after his role on the mobile team. On the mobile team, he was responsible for building out the initial MobileFrontend extension, and has been the team's tech lead since then, succeeded in this role by Brion Vibber.
I've decided to also designate Patrick as Senior Technical Advisor. Patrick has been invaluable in the last few weeks in supporting hiring processes, cross-team coordination, and technical evaluations. I will continue to rely on Patrick's expertise and network to support technical coordination across the department. This is one of the near term improvements to increase my bandwidth and capacity as well.
Patrick will report to me. For performance and architecture projects, he'll work directly with engineers working in those areas (Tim, Asher, Aaron, Ori, etc.). I've posted the job description for this role here for reference:
https://wikimediafoundation.org/wiki/Job_openings/Site_Performance_Engineer_...
Please join me in congratulating Patrick.
All best, Erik
-- Erik Möller VP of Engineering and Product Development, Wikimedia Foundation
Support Free Knowledge: https://wikimediafoundation.org/wiki/Donate
Congratulations Patrick! Are you now the right person one should ask decisions/updates to for stale performance/platformeng bugs? https://bugzilla.wikimedia.org/buglist.cgi?keywords=performance%2C%20platformeng&keywords_type=anywords&resolution=---&query_format=advanced&list_id=172284 Or questions such as «which pages are safe to run an update on even on en.wiki, and how frequently; and which would kill it? Or, at what point a wiki is too big to run such updates carelessly?» (http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/65463... ) https://bugzilla.wikimedia.org/show_bug.cgi?id=15434 Thanks, Nemo
Erik wrote:
it's my pleasure to announce the promotion of Patrick Reilly to the role of Site Performance Engineer and Senior Technical Advisor.
It's been planned for a long time for Patrick to focus on site performance as his next step after his role on the mobile team. On the mobile team, he was responsible for building out the initial MobileFrontend extension, and has been the team's tech lead since then, succeeded in this role by Brion Vibber.
I've decided to also designate Patrick as Senior Technical Advisor. Patrick has been invaluable in the last few weeks in supporting hiring processes, cross-team coordination, and technical evaluations. I will continue to rely on Patrick's expertise and network to support technical coordination across the department. This is one of the near term improvements to increase my bandwidth and capacity as well.
Patrick will report to me. For performance and architecture projects, he'll work directly with engineers working in those areas (Tim, Asher, Aaron, Ori, etc.). I've posted the job description for this role here for reference:
https://wikimediafoundation.org/wiki/Job_openings/Site_Performance_Engineer_...
It's been gratifying in the last few years to see our capacity to improve site performance on an architectural level, and to react immediately to site performance crises, improve substantially. I look forward to yet another step in this direction and I have just added https://www.mediawiki.org/wiki/Site_performance to my watchlist. :-) Patrick, can you talk a little about what your first priorities are in this role? Or how the Wikimedia technical community can help?
Right now https://www.mediawiki.org/wiki/Manual:Database_layout/MySQL_Optimization/Tut... and https://www.mediawiki.org/wiki/Manual:Performance_tuning are the resources helping volunteers see how to write and review code -- more guidance in what people need training in would be welcome.
On 01/10/2013 06:51 AM, Federico Leva (Nemo) wrote:
Congratulations Patrick! Are you now the right person one should ask decisions/updates to for stale performance/platformeng bugs? https://bugzilla.wikimedia.org/buglist.cgi?keywords=performance%2C%20platformeng&keywords_type=anywords&resolution=---&query_format=advanced&list_id=172284
Or questions such as «which pages are safe to run an update on even on en.wiki, and how frequently; and which would kill it? Or, at what point a wiki is too big to run such updates carelessly?» (http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/65463... ) https://bugzilla.wikimedia.org/show_bug.cgi?id=15434 Thanks, Nemo
Andre, Nemo has a good question. :-) Basically, who is the product manager for site performance, who can prioritize upcoming work and Bugzilla issues and specify workflows and guidelines as Nemo would like? Can you coordinate with Patrick to figure that out?
On Thu, 2013-01-10 at 09:25 -0500, Sumana Harihareswara wrote:
On 01/10/2013 06:51 AM, Federico Leva (Nemo) wrote:
Congratulations Patrick! Are you now the right person one should ask decisions/updates to for stale performance/platformeng bugs? https://bugzilla.wikimedia.org/buglist.cgi?keywords=performance%2C%20platformeng&keywords_type=anywords&resolution=---&query_format=advanced&list_id=172284
For everybody's info, there are 28 open bug reports (excluding enhancement requests) with the keyword "performance".
Or questions such as «which pages are safe to run an update on even on en.wiki, and how frequently; and which would kill it? Or, at what point a wiki is too big to run such updates carelessly?» (http://article.gmane.org/gmane.science.linguistics.wikipedia.technical/65463... ) https://bugzilla.wikimedia.org/show_bug.cgi?id=15434
Andre, Nemo has a good question. :-) Basically, who is the product manager for site performance, who can prioritize upcoming work and Bugzilla issues and specify workflows and guidelines as Nemo would like? Can you coordinate with Patrick to figure that out?
In my understanding I wouldn't call performance a product (no identifiable codebase, hence also the Bugzilla *keyword* across products) but I see what you mean. :) I'd also love to see the documentation asked for by Nemo, also as it would help to have a bug report seen by the right developer. Let me try to follow up.
andre
wikitech-l@lists.wikimedia.org