<https://phabricator.wikimedia.org/T93613>. Besides my work on UI
Standardization I'll also continue to work on the skin. I think Blueprint
should be on that list.
On Thu, Jul 23, 2015 at 6:25 PM, Adam Baso <abaso(a)wikimedia.org> wrote:
Would you please share this on the list?
On Thursday, July 23, 2015, Volker Eckl <veckl(a)wikimedia.org> wrote:
> Hi Adam,
> there are currently plans on deploying skin Blueprint on mediawiki.org
> <https://phabricator.wikimedia.org/T93613>. Besides my work on UI
> Standardization I'll also continue to work on Blueprint. Although UI
> Standardization is a "special case", formally we belong to Reading and
> therefore I think Blueprint should be on that list.
> On Mon, Jul 20, 2015 at 10:58 PM, Adam Baso <abaso(a)wikimedia.org>
>> Hi all -
>> I've been reviewing a list of extensions with Reading Engineering and
>> Reading Infrastructure leads - props to James Forrester for promoting this
>> discussion. Here's a list of extensions we believe currently falls under
>> Reading for triage (n.b., not all extensions will get active development
>> Presuming no major issues with this, I think we should move the page
>> to mw:Reading/Extension_Responsibility.
>> One important outstanding question:
>> Is MultimediaViewer appropriate for Reading given its
>> consumption-oriented nature? Or is this actually better suited to Editing
>> (where there exists a team named Multimedia)?
>> Some other notes:
>> * For skins with low utilization, we in time probably should
>> coordinate handover to interested community members (or discuss with
>> community members practical approaches for EOL).
>> * Regarding the Nostalgia skin, we believe it's only used on
, so maintenance would
>> be updating for breaking skin changes or security issues only.
>> * JsonConfig, ZeroBanner, ZeroPortal - we'll need to examine this more
>> closely. Yuri (who has deepest PHP knowledge on extensions) is now over in
>> Discovery, Jeff (JS & Lua) is in Reading, and now I'm managing instead
>> writing lots of code.
>> * Collection probably belongs in Services
>> Mobile-l mailing list
Mobile-l mailing list