Talk:Project Open CSP

About this board

Elitre (WMF) (talkcontribs)

The Tech Department at Wikimedia Foundation [1] invites you to a special event on February 09, 2023, at 1600 UTC [2].

Richard Evans, Electronics & Data Systems Engineer At NASA Glenn Research Center [3], will be presenting on how MediaWiki is being used within NASA to help manage the testing of very large spacecraft to prove they can survive the harsh conditions of launch, orbit, and re-entry.

The management platform is built from MediaWiki and several key extensions that provide workflow support. This evolving platform plans to incorporate the extensions that form the MediaWiki-powered Open CSP platform [4]. This talk will explain the architecture and benefits of the NASA platform and motivate the need for Open CSP.

We’ll also be recording the event to share with those who can’t make it. You can join the event through YouTube [5].

Looking forward to seeing you there,

--on behalf of the Tech Department, Wikimedia Foundation.

(For follow-ups, please reach out to






Reply to "Upcoming event ;)"

2022-01-05 Meeting Notes

Revansx (talkcontribs)


  1. Status of WS Extensions
      1. Verbal review of WS extensions
      2. discuss where the code lives
      3. use bots as part of oCSP?
  2. oCSP architecture and guiding principles


  1. [rich] update mw.o/PoCSP with a table of supported extension
  2. [rich] indicate in table the community status of said extensions
  3. [rich] oCSP architecture model and bot overview presentation
Reply to "2022-01-05 Meeting Notes"

Wiki Content Synch Methods

Revansx (talkcontribs)

List of various ways that content synch can be implemented

  1. Namespaces - all edits in a custom namespace are published to other wikis in real-time using interwiki tables and scary transclusions
  2. Hooks - use a "hook" extension that does sync "on save"
  3. Server Scripts - cron jobs + pywikibot/mwclient
  4. Extensions - extensions like Page Exchange/Page Importer
Nischayn22 (talkcontribs)

Have you checked out the Sync extension?

Revansx (talkcontribs)

yes, but it's been a while. When I last checked it, it wasn't possible to use Sync on private wikis that use PluggableAuth for authentication and authorization. Has that changed? Is there a way to use Sync such that allows local accounts to bypass PluggableAuth?


Reply to "Wiki Content Synch Methods"

Wiki Content Synch Definitions

Revansx (talkcontribs)


  • Intra-organizational wiki content - wiki content that is synchronized "within" different wikis in the organization.
  • Inter-organizational wiki content - wiki content that is synchronized to wikis that are external to the organization.
Reply to "Wiki Content Synch Definitions"

Wiki Content Synch and Synchronization Timeframes

Revansx (talkcontribs)

There are three different content sync time frames that should be addressed in enterprise wiki farms:

  1. Synchronous - real-time - edits made to pages in a source wiki wiki are published immediately to a set of target wikis in the organization
  2. Periodic - defined intervals - updates to content in a source wiki is published to a set of target wikis in the organization at defined intervals
  3. Episodic - user initiated - edits made to pages in a source wiki are published to a set of target wikis in the organization manually by authorized users
Reply to "Wiki Content Synch and Synchronization Timeframes"

Wiki Content Synch and Artifact Repositories

Revansx (talkcontribs)

Because enterprise wikis have requirements to maintain autonomy within the enterprise infrastructure, any wiki content sync that seeks to sync with external wikis should be implemented in such a way that they work with local artifact repositories like Apache's Archiva (or jfrog's Artifactory). This would not necessarily be required for intra-organizational content sharing

Reply to "Wiki Content Synch and Artifact Repositories"

The need for a "standard methods" authority in the MW community

Revansx (talkcontribs)

It seems clear that it is outside of the scope of the WMF to establish and recommend standard methods for wiki admins to implement wiki-functionality that is not needed by WMF projects, but it does seem appropriate for a non-profit organization like "MWStakeholders" to take this on by adding a statement in their charter [1] to evaluate and document community approved methods of doing non-MWF (i.e. Enterprise) tasks (like content sync'ing in private wikis, org charts, etc..)


Reply to "The need for a "standard methods" authority in the MW community"
There are no older topics