Last modified: 2014-08-25 18:08:58 UTC
I'd like to enable TwitterCard extension and see if there is any appreciable effect on inbound traffic before and after it is enabled, I propose a 1 month test period.
"foundation wikis" is undefined.
Nemo, "Project wikis?" basically the first 3 rows at http://www.wikimedia.org/ if there is a better term please let me know so I can write more clearly in the future.
Those are the content projects, but ok, basically all wikis (for the sake of this component).
(the dependency is reversed, the items from the other bug need to be address first, notably perf and security reviews)
Greg, it depends on the perf and security review, not the deployment of the extension right?
(In reply to Jared Zimmerman (WMF) from comment #2) > Nemo, "Project wikis?" basically the first 3 rows at > http://www.wikimedia.org/ if there is a better term please let me know so I > can write more clearly in the future. See these 3 pages, for various group-names, and why "foundation wikis" was confusing. :) [[m:Complete list of Wikimedia projects]] [[m:Wikimedia projects]] [[m:Table of Wikimedia projects#Projects without language subdomains]]
(In reply to Jared Zimmerman (WMF) from comment #5) > Greg, it depends on the perf and security review, not the deployment of the > extension right? To test it requires deploying it, even if just for one month :) The details of what the 1 month test entails should be outlined including the goals and rubric that will be used to judge the test. Otherwise it's not a test :) So, for the avoidance of doubt: 1) Get all of the checklist items done in bug 62811#c42 2) The last one is slightly different in this case because a 1 month test run is being suggested 3) Communicate the goal of the test and the rubric (I suggest getting explicit CL support on this, it's potentially not a slam dunk/easy thing) 4) Run the test 5) Assess via the rubric for removal/keeping (sidenote: is this going to be a new model of deploying extensions? We have the "standard way", the BetaFeatures way, and now an explicit 1 month test phase method? Let's sit down and talk about that.)
@Greg I proposed the 1 month test period for a few reasons, Beta Features doesn't really make sense because it has no user facing effect on the site itself. The second reason is the questions about "does the community want this" is always a long conversation, if we know it makes a difference in traffic that will be a data point to weigh with everything else, if it doesn't then we'll know that we don't necessarily need to prioritize and spend as much time on community consultation for a feature that doesn't really gain us much. To your general point about standards, they sure are great, if people actually use them.
There's one problem with this plan: page HTML is cached for 1 month, so TC will come into full power only when you're proposing to disable it, and then it will take another month for the cards to disapear. This also means that whatever effect it will give will kick in slowly, making the analysis harder.
good point Max, lets just roll it out then ;)
Adding an extra blocker. It's from me, so you know what it is about :)
@luis, I can think of 2 options, I don't know how possible either are… 1. modify the image, add a footer which contains the basic licensing req. as a watermark 2. modify the request for the description text only when pulled from twitter and include the licensing info in the description sent to twitter.
