This Wednesday, 2100-21:30 UTC, let's have a thirty-minute RfC review
meeting to check on a few proposals to consolidate, and whether a few
authors have done their next steps from the last few months. (If people
want to answer these questions onlist/onwiki that's fine too.)

https://www.mediawiki.org/wiki/Architecture_meetings/RFC_review_2014-03-12

I have some open questions:

   1. Configuration (database) RfCs:
original<https://www.mediawiki.org/wiki/Requests_for_comment/Configuration_database>,
   RFC 
2<https://www.mediawiki.org/wiki/Requests_for_comment/Configuration_database_2>,
   and JSON 
onwiki<https://www.mediawiki.org/wiki/Requests_for_comment/Json_Config_pages_in_wiki>.
Shall we ask authors to consolidate by a certain date?
   2. URL 
shortener<https://www.mediawiki.org/wiki/Requests_for_comment/URL_shortener>(and
URL
   Shortener 
Service<https://www.mediawiki.org/wiki/Requests_for_comment/URL_shortener_service_for_Wikimedia>,
   probably to be consolidated). Do we have the implementation details Tim
   wanted?
   3. Assert <https://www.mediawiki.org/wiki/Requests_for_comment/Assert>.
   Any particular enthusiasm or next steps here?
   4. Linker 
refactor<https://www.mediawiki.org/wiki/Requests_for_comment/Linker_refactor>.
   Any initial comments? (onwiki comments welcome also)
   5. your RfC here?

I recently updated lots of entries in the
https://www.mediawiki.org/wiki/Requests_for_comment table so please check
those out and comment on those where appropriate, and suggest RfCs to cover
on Wednesday.

We'll talk in #wikimedia-office on Freenode, at 2100 UTC on March 12:

http://www.worldtimebuddy.com/?qm=1&lid=2950159,100,524901,5128581&h=5128581&date=2014-3-12&sln=17-17.5

Moscow: 1am Thursday 13 March
Berlin: 22:00 12 March
New York: 5pm March 12
San Francisco: 2pm March 12

Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
_______________________________________________
Wikitech-l mailing list
[email protected]
https://lists.wikimedia.org/mailman/listinfo/wikitech-l

Reply via email to