Hi all!
This is a Final Call for Comments on the RFC on Content Model Storage [1][2]. If no new and serious objections are raised within a week, the Architecture Committee will approve this RFC and drive its implementation.
The RFC on Content Model Storage was originally approved in 2015, but was then postponed in favor of another RFC, which proposes to create a separate content meta-data table [3] as part of the move towards multi-content revisions (MCR) [4].
However, MCR in turn got stuck on database performance concerns. So we now propose to go ahead with implementing the original RFC. The idea is to assign a number to every content model (and content format), and then use these numbers to refer to the models and formats in the database, instead of repeating the same string millions of times (which is my fault btw, sorry about that).
Since the original RFC was already approved, and the situation does not seem to have changed since then, we see no need for another round of discussions. If nobody raises any new and serious objections within a week, this should be good to go.
Cheers, Daniel
[1] https://phabricator.wikimedia.org/T105652 [2] https://www.mediawiki.org/wiki/Requests_for_comment/Content_model_storage [3] https://phabricator.wikimedia.org/T142980 [4] https://www.mediawiki.org/wiki/Multi-Content_Revisions/Content_Meta-Data#Dat...
Hi all!
Again sorry for dropping the ball on ArchCom reporting, things should be back to normal by next week.
This final call regarding Content Model Storage has passed without any new concerns being raised.
The RFC is thus approved as proposed, and implementation can go forward.
Implementation work and deployment schedule should be coordinated with the imminent work on Multi-Content-Revisions. If you are going to work on Content Model Storage, please talk to me first.
Thanks, Daniel
Am 14.12.2016 um 12:29 schrieb Daniel Kinzler:
Hi all!
This is a Final Call for Comments on the RFC on Content Model Storage [1][2]. If no new and serious objections are raised within a week, the Architecture Committee will approve this RFC and drive its implementation.
The RFC on Content Model Storage was originally approved in 2015, but was then postponed in favor of another RFC, which proposes to create a separate content meta-data table [3] as part of the move towards multi-content revisions (MCR) [4].
However, MCR in turn got stuck on database performance concerns. So we now propose to go ahead with implementing the original RFC. The idea is to assign a number to every content model (and content format), and then use these numbers to refer to the models and formats in the database, instead of repeating the same string millions of times (which is my fault btw, sorry about that).
Since the original RFC was already approved, and the situation does not seem to have changed since then, we see no need for another round of discussions. If nobody raises any new and serious objections within a week, this should be good to go.
Cheers, Daniel
[1] https://phabricator.wikimedia.org/T105652 [2] https://www.mediawiki.org/wiki/Requests_for_comment/Content_model_storage [3] https://phabricator.wikimedia.org/T142980 [4] https://www.mediawiki.org/wiki/Multi-Content_Revisions/Content_Meta-Data#Dat...
wikitech-l@lists.wikimedia.org