Page MenuHomePhabricator

track resource usage by article placeholder extension
Closed, DeclinedPublic

Description

Attempt to measure the cost of resources of the article placeholder extension (cost in terms of development, maintenance, etc).

Event Timeline

Esc3300 created this task.Sep 5 2016, 3:03 PM
Restricted Application added a project: Wikidata. · View Herald TranscriptSep 5 2016, 3:03 PM
Restricted Application added a subscriber: Aklapper. · View Herald Transcript
Lydia_Pintscher closed this task as Declined.Sep 9 2016, 6:29 PM
Lydia_Pintscher added a subscriber: Lydia_Pintscher.

I am sorry but not without a clearer explanation and for which purpose and why specifically this one.

There are several requests to evaluate various aspects of this extension: T144589 T142955 T144592
As this seems to take a fairly large part of development time, it would be good to have a full picture.

If the same is done for all activities, all the better. I think it would be good to compare it to support for lists and infoboxes on clients.

There are several requests to evaluate various aspects of this extension: T144589 T142955 T144592
As this seems to take a fairly large part of development time, it would be good to have a full picture.

That is a wrong impression. It is just that we are specifically careful with the ArticlePlaceholder as we are walking in unknown territory a lot of times. Also more tickets get filed for it because the people working on it prefer that. It skews the picture.

If the same is done for all activities, all the better. I think it would be good to compare it to support for lists and infoboxes on clients.

It wouldn't be a meaningful comparison because quite a few things we have done and are doing for one are useful for the other.

hoo moved this task from Incoming to Done on the ArticlePlaceholder board.Dec 13 2016, 10:07 AM