First of two summary & "what's up now" posts.
TitleValue:
https://www.mediawiki.org/wiki/Architecture_Summit_2014/TitleValue Next
steps: Nik is leading the discussion, Daniel will help with the process to
identify desired service interfaces, and we're discussing it in the RFC
review this Friday (tomorrow).
Architectural guidelines and process:
https://www.mediawiki.org/wiki/Architecture_Summit_2014/Architectural_value…
aiding Brion in improving
https://www.mediawiki.org/wiki/Architecture_guidelines , and the architects
are going to try to delegate more decisions (e.g., "such-and-so is our
delegate for making a Yes, No, or Revise-And-Resubmit decision on this
particular RFC").
In
https://www.mediawiki.org/wiki/Talk:Architecture_Summit_2014/Storage_servic…
collected the two different sets of notes that (evidently) different
people took on the same session. This includes notes on API versioning,
Data Store, PHP REST service, and Storage Service.
The API: Yuri and Brad will look into shimming old versions and will lead
discussions on API key/Useragent stuff onlist and onwiki, and have already
started updating
https://www.mediawiki.org/wiki/Requests_for_comment/API_roadmap .
Data Store: Brion and Tim so far like the idea, and Aaron Schulz recommends
adding getMulti options. We accepted
https://www.mediawiki.org/wiki/Requests_for_comment/DataStore but did not
implement it yet.
PHP REST service: we agreed to approve the interface, with an initial
implementation using DataStore key-value as a backend.
https://www.mediawiki.org/wiki/Requests_for_comment/PHP_Virtual_REST_Servic…
and implementation is in progress.
Storage service: Gabriel is refining
https://www.mediawiki.org/wiki/Requests_for_comment/Storage_service and
refining the Rashomon prototype, and will present it for consideration when
ready.
HTML Templating: there's a working group whose first aim is, as Brion puts
it,
https://www.mediawiki.org/wiki/Architecture_Summit_2014/HTML_templating&quo…
investigate existing work in VE & co to get a better idea of the
widget/template distinction and how we can make sure low-level crud doesn't
get done by default" (quoting from notes). Ryan Kaldari, Chris Steipp,
Gabriel Wicke, Owen Davis, and Jon Robson and others are working on this
and I believe Gabriel will have an update in the next few days.
More to come.
Sumana Harihareswara
Engineering Community Manager
Wikimedia Foundation
On Tue, Jan 28, 2014 at 10:20 AM, Rob Lanphier <robla(a)wikimedia.org> wrote:
On Tue, Jan 28, 2014 at 1:28 AM, Federico Leva (Nemo)
<nemowiki(a)gmail.com
wrote:
Can/should notes about specific RfC be copied
into the respective talk
pages? Some of them include DocumentMode bits that can be part of the RfC
text itself, but not many. In particular I'd like to see updates to <
https://www.mediawiki.org/wiki/Requests_for_comment/
Performance_standards_for_new_features> but the etherpad notes don't
help. It's useful if every attendee incrementally updates the main RfC
texts with a fresh memory of the discussions.
Yup, it'd be really useful to have all of the notes as close to the
relevant RFCs as possible, and any help you can provide in prodding the
attendees to update their respective RFCs would be greatly appreciated.
:-)
Rob
_______________________________________________
Wikitech-l mailing list
Wikitech-l(a)lists.wikimedia.org
https://lists.wikimedia.org/mailman/listinfo/wikitech-l