Thanks! I added it to my subpage and assigned it to Reading Design. Assuming comments on this thread taper off soon, I'll figure out how to get this stuff added into https://www.mediawiki.org/wiki/Developers/Maintainers . I think in the Maintainers column we'll want to be generic and point to the particular team if someone isn't actively maintaining it, but otherwise point to a person who we know to be actively developing *plus* the particular team.

-Adam

On Thu, Jul 23, 2015 at 9:31 AM, Volker Eckl <veckl@wikimedia.org> wrote:
There are currently plans on deploying skin Blueprint on mediawiki.org. Besides my work on UI Standardization I'll also continue to work on the skin. I think Blueprint should be on that list.

Best,
Volker

On Thu, Jul 23, 2015 at 6:25 PM, Adam Baso <abaso@wikimedia.org> wrote:
Would you please share this on the list?

On Thursday, July 23, 2015, Volker Eckl <veckl@wikimedia.org> wrote:
Hi Adam,
there are currently plans on deploying skin Blueprint on mediawiki.org. 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.


Best,
Volker

On Mon, Jul 20, 2015 at 10:58 PM, Adam Baso <abaso@wikimedia.org> wrote:
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 support).


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 https://nostalgia.wikipedia.org/wiki/HomePage, 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 of writing lots of code.

* Collection probably belongs in Services



_______________________________________________
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l




_______________________________________________
Mobile-l mailing list
Mobile-l@lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/mobile-l