Talk:Writing an extension for deployment

"use the "shell" keyword so that people with shell access can find the request;" - I thought people were only supposed to add shell when there's something for a shell user to do (so after it is reviewed, not before like these instructions say). Bawolff (talk) 16:58, 22 April 2012 (UTC)
 * Good point. Fixed. Sumana Harihareswara, Wikimedia Foundation Engineering Community Manager (talk) 03:57, 25 April 2012 (UTC)

Support
ECT no longer has resources (20% time) to support extensions on an ongoing basis. The doc should be updated to reflect how deployed extensions will be supported on an ongoing basis.


 * Commitment from a deployer or a engineering team to support and, if necessary, review and push changes
 * If user facing or noticeable by user commitment from product and design for the same.

Tychay (talk) 04:21, 4 October 2013 (UTC)
 * Perhaps you can draft something for review? --MZMcBride (talk) 16:28, 5 October 2013 (UTC)

Post-deploy support plan
One thing that I think is missing from this checklist is a discussion of what happens after the extension is approved and deployed to the wiki(s). Who is responsible for fixing bugs, responding to feature requests, keeping up with MediaWiki API changes, etc.?

I don't know the answer, but I know enough to ask the question. :) --BDavis (WMF) (talk) 23:04, 1 November 2013 (UTC)
 * Good points. +1
 * (It should probably also be added to Developers/Maintainers)
 * Also during deployment, what are the requirements (or even recommendations) for announcements? Eg. When a new extension gets launched, it should probably be mentioned in Tech/News at a minimum, and probably on the wikitech-ambassadors mailing list, and perhaps on the English w:WP:VPT and/or Signpost. Quiddity (WMF) (talk) 19:12, 4 November 2014 (UTC)

example site
I would like to have at least one site as an example, to check if an extension is working.

All the best from Dschermennie --Bernd M. 07:10, 21 May 2014 (UTC)