Last modified: 2014-07-24 13:13:36 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T67849, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 65849 - Review and deploy Petition extension to wikimediafoundation.org
Review and deploy Petition extension to wikimediafoundation.org
Status: RESOLVED FIXED
Product: Wikimedia
Classification: Unclassified
Extension setup (Other open bugs)
wmf-deployment
All All
: High normal (vote)
: ---
Assigned To: Nobody - You can work on this!
:
Depends on: 65850 65851
Blocks: 31235
  Show dependency treegraph
 
Reported: 2014-05-28 12:34 UTC by Peter Coombe
Modified: 2014-07-24 13:13 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Peter Coombe 2014-05-28 12:34:09 UTC
This extension will be used for a petition to encourage mobile operators to join Wikipedia Zero. It only needs to be deployed on wikimediafoundation.org, not any other sites.

Would like to get this deployed as soon as possible, since we are aiming to launch the petition in June. The code has had some review already, but still needs a formal security and performance review.

mediawiki.org: https://www.mediawiki.org/wiki/Extension:Petition
bugzilla: https://bugzilla.wikimedia.org/buglist.cgi?component=Petition
gerrit: https://gerrit.wikimedia.org/r/#/admin/projects/mediawiki/extensions/Petition
Comment 1 Greg Grossmeier 2014-05-28 15:30:25 UTC
== Checklist ==
=== Done ===
# Create Extension: mediawiki.org page for developers and people who will install or configure the extension.
# Request a component in [[Bugzilla]].
# Get the extension code in [[Gerrit]].

=== Not Done ===
(in-progress, see dependent bugs)
# Request (and respond to) a performance review
# Request (and respond to) a security review
Comment 2 Greg Grossmeier 2014-05-28 17:29:52 UTC
(In reply to Peter Coombe from comment #0)
> Would like to get this deployed as soon as possible, since we are aiming to
> launch the petition in June. The code has had some review already, but still
> needs a formal security and performance review.

Do you have a target date? In 3 days or in 33 days? Somewhere in between? :)
Comment 3 Chad H. 2014-05-28 17:36:10 UTC
Two things jumped out at me skimming this that need fixing.

1) Since you're disabling the parser cache we end up doing a select count(*) on every render of the page. This probably isn't ok and needs some sort of caching (stash the count in memcached for some short period of time maybe?)

2) Using $wgRequest in a parser function callback won't always work as you expect. Pages can be rendered in many contexts, not just from a web request (eg: command line jobs).

A clever way to get around (2) would be to make it an IncludableSpecialPage instead of a parser function (you can use $par for the existing title param). Then you could call the SpecialPage's getRequest() method and just embed the special page in a non-special one if you need.
Comment 4 Peter Coombe 2014-05-29 10:06:21 UTC
Greg: We don't have a particular date (lots of other variables) but it would be good to have the extension deployed by the middle of June.

Chad: Thanks for the feedback, I'll look into these.
Comment 5 Peter Coombe 2014-06-13 00:15:19 UTC
Okay, change of plan: we're now intending to launch the campaign the week of July 7th. Which gives a bit more time for changes, and aim to deploy late June.
Comment 6 Peter Coombe 2014-07-10 21:28:55 UTC
Obviously this was delayed again, but we're hoping to launch next week.

As suggested by Chad, I changed from using a tag to an includable special page (https://gerrit.wikimedia.org/r/#/c/142561/). The signature count can also be stored in memcached now (https://gerrit.wikimedia.org/r/#/c/144174/)

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links