Made this visible to the public. Currently this is still in draft, but I welcome your comments.

Related: T14306: Implement MediaWiki Help Repository (fetching Help: pages from MediaWiki.org or Meta, similar to file description pages from Commons).

In T117550#1792253, @Legoktm wrote:

Related: T14306: Implement MediaWiki Help Repository (fetching Help: pages from MediaWiki.org or Meta, similar to file description pages from Commons).

Thanks, I knew something like that was out there.

I'm new to phabricator, so sorry if I'm doin it rong:

Related things to consider:

• https://www.mediawiki.org/wiki/Extension:Data_Transfer
• https://www.mediawiki.org/wiki/Help:Export
• https://www.mediawiki.org/wiki/Help:Import
• https://www.mediawiki.org/wiki/Category:Data_extraction_extensions
• https://www.mediawiki.org/wiki/Category:Import_extensions

HTH,

DanBolser writes:

I'm new to phabricator, so sorry if I'm doin it rong:

This works for me. I've spec'd out a bit of how I think this should be
implemented. I'll add that later today.

• https://www.mediawiki.org/wiki/Extension:Data_Transfer
• https://www.mediawiki.org/wiki/Category:Data_extraction_extensions
• https://www.mediawiki.org/wiki/Category:Import_extensions

This feature should be in core. Help pages, for example, should be
available at installation time.

• https://www.mediawiki.org/wiki/Help:Export
• https://www.mediawiki.org/wiki/Help:Import

These tools are there and can definitely be used, but there needs to be
a way to automate all this.

Yup, I'm wondering what we can take from those existing tools, or even if
some could be obsoleted by this project (perhaps a way to get contribution
would be to contact each of the authors of those tools).

DanBolser writes:

I'm wondering what we can take from those existing tools, or even if
some could be obsoleted by this project (perhaps a way to get
contribution would be to contact each of the authors of those tools).

I see.

In that vein, I thought that one thing we could do is use some of the
tools from the Collection extension to create and/or manage bundles.
Make the core functionality minimal but installing the Collection
extension would give you a really nice set of tools for managing bundles.

Hi,

A few notes from our perspective:

• Bundling should include (a selection of) wiki pages from all namespaces and images/files, but perhaps also other resources, e.g. logo.
• One should be able to manually (from a special page) make a selection and start the bundling, like now with Special:Export
• It should also be possible to select&bundle automatically, i.e. from a script or command line
• There should also be an "unbundling" option, to deploy bundled content, again both manually from a special page and automatically from a script or command line
• The automatic process is useful for transferring content and resources from an editor instance to a public instance of a wiki, where the public instance serves an approved subset of the pages in the editor instance
• The manual process is useful for deployment of content and resources in a dev/test/staging/production environment. In many situations, security directives prohibit automatic deployment in a production environment.

I agree that most of the program code has already been written, we just need to assemble it.

Another use case from the support desk just now: a standard template library

Not sure how to reply there, so I'll add my thoughts here... Does the "Include templates" option on Special:Export recursively get all templates?

In T117550#1802102, @DanBolser wrote:

Does the "Include templates" option on Special:Export recursively get all templates?

Yes, it does.

I said I would write up my ideas for this, but I haven't gotten around to it. So, here we go.

I thought about using the extension collection and then, just now, looked at the Gather project. I think there is the opportunity to build on one or both of these projects. for this. Obviously, this is my muddled thoughts, but it gives me something to aim for and get feedback on.

• Table for bundle names

table: bundle
col: name varchar(255)
col: id int

• Table to list pages in a bundle with revisions

table: bundle_contents
col: sourcewiki -- null or interwiki id
col: page -- points to title
col: revid -- specifies specific revision of title, fallback to current if id is not specified

• API offers list of bundles on the wiki
  • File pages mean bundle file and page description.
  • MW Help pages are first bundle instance
• action=listbundles

returns

[ { bundle: "name", id: int }, ... ]

• action=getbundle&id=???

returns

{ url: URL-to-post, request: 'request data to sends' }

• CLI creates artifact to put under $IP/bundle

• getBundle.php --list URL

List the bundles available from the wiki at URL.

• getBundle.php --fetch=NAME URL

Get the NAME bundle from the wiki at URL, put it under $IP/bundles as compressed xml

• getBundle.php --fetch=NAME --install URL

Get the NAME bundle from the wiki at URL, install into this wiki

After seeing @Legoktm's talk on shadow namespaces, there is some overlap, but I just ran into Template:Ping needed by Flow. I think this could be a baby step.