Change Details

**Type of activity:** Pre-scheduled session **Main topic:** https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Handling_wiki_content_beyond_plaintext == The problem == Multi-Content-Revisions (MCR) (T107595) have been proposed as a way to move structured information and meta-data out of wikitext, and to better integrate information currently stored on subpages or similar. During the RFC discussion, it however became clear that the intended use cases are not sufficiently defined and documented. See the comments on T107595 for discussions; most of them revolve around use cases. == Expected outcome == A set of use cases for MCR, with priorities and requirements for each use case. Some sort of commitment by WMF to work on MCR, or at least support the development. Alternatively, we may discover that MCR does not fit the intended use cases well enough after all, and needs to be re-considered. == Current status of the discussion == The MCR proposal is extensively documented and there has been quite a bit of discussion about it since the last DevSummit. Once of the most problematic points in the discussion has been the fact that we have many potential use cases, but we do not have much detail on these. == Links == * https://www.mediawiki.org/wiki/Multi-Content_Revisions#Use_Cases

**Type of activity:** Pre-scheduled session **Main topic:** https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Handling_wiki_content_beyond_plaintext == The problem == Multi-Content-Revisions (MCR) (T107595) have been proposed as a way to move structured information and meta-data out of wikitext, and to better integrate information currently stored on subpages or similar. During the RFC discussion, it however became clear that the intended use cases are not sufficiently defined and documented. == Expected outcome == A set of use cases for MCR, with priorities and requirements for each use case. Some sort of commitment by WMF to work on MCR, or at least support the development. Alternatively, we may discover that MCR does not fit the intended use cases well enough after all, and needs to be re-considered. == Current status of the discussion == The MCR proposal is extensively documented and there has been quite a bit of discussion about it since the last DevSummit. Once of the most problematic points in the discussion has been the fact that we have many potential use cases, but we do not have much detail on these. See the comments on T107595 for discussions; most of them revolve around use cases. == Links == * https://www.mediawiki.org/wiki/Multi-Content_Revisions#Use_Cases

**Type of activity:** Pre-scheduled session **Main topic:** https://www.mediawiki.org/wiki/Wikimedia_Developer_Summit/2017/Handling_wiki_content_beyond_plaintext == The problem == Multi-Content-Revisions (MCR) (T107595) have been proposed as a way to move structured information and meta-data out of wikitext, and to better integrate information currently stored on subpages or similar. During the RFC discussion, it however became clear that the intended use cases are not sufficiently defined and documented. See the comments on T107595 for discussions; most of them revolve around use cases. == Expected outcome == A set of use cases for MCR, with priorities and requirements for each use case. Some sort of commitment by WMF to work on MCR, or at least support the development. Alternatively, we may discover that MCR does not fit the intended use cases well enough after all, and needs to be re-considered. == Current status of the discussion == The MCR proposal is extensively documented and there has been quite a bit of discussion about it since the last DevSummit. Once of the most problematic points in the discussion has been the fact that we have many potential use cases, but we do not have much detail on these. See the comments on T107595 for discussions; most of them revolve around use cases. == Links == * https://www.mediawiki.org/wiki/Multi-Content_Revisions#Use_Cases