Sunflower MediaWiki: Difference between revisions

From MWStake
Jump to navigation Jump to search
Line 5: Line 5:
==Objectives==
==Objectives==
By providing an "essential MediaWiki" for administrators around the world, several goals are to be achieved:
By providing an "essential MediaWiki" for administrators around the world, several goals are to be achieved:
#To promote the awareness and dissemination of MediaWiki, extensions, bundles, communities and service providers.
#To promote the awareness and distribution of MediaWiki, extensions, bundles, communities and service providers.
#Create a collaborative project for third-party users and developers (non-profit and for-profit) to improve stability:
#Create a collaborative project for third-party users and developers (non-profit and for-profit) to improve stability:
##Organizing the maintenance of the included extensions
##Organizing the maintenance of the included extensions

Revision as of 11:16, 7 November 2019

Sunflower MediaWiki is a new multi-purpose MediaWiki distribution.

(This is a draft)

Objectives

By providing an "essential MediaWiki" for administrators around the world, several goals are to be achieved:

  1. To promote the awareness and distribution of MediaWiki, extensions, bundles, communities and service providers.
  2. Create a collaborative project for third-party users and developers (non-profit and for-profit) to improve stability:
    1. Organizing the maintenance of the included extensions
    2. Sharpening awareness of the basic functions with which new functions must cooperate
    3. Providing a basis for the technical developments of various projects: Meza, Semantic MediaWiki, BlueSpice MediaWiki, Language Bundle and many more
    4. Development of programming standards and agreement on technologies and architectures

Target group

  • Admins and developers who run MediaWikis in a professional environment
  • Cloud Service Providers

Distribution

A first proposal for extensions that are delivered with Sunflower

Extensions by MediaWiki Extensions by Sunflower MediaWiki Skins by MediaWiki Skins by Sunflower MediaWiki
  • CategoryTree
  • Cite
  • CiteThisPage
  • CodeEditor
  • ConfirmEdit
  • Gadgets
  • ImageMap
  • InputBox
  • Interwiki
  • LocalisationUpdate
  • MultimediaViewer
  • Nuke
  • OATHAuth
  • PageImages
  • ParserFunctions
  • PdfHandler
  • Poem
  • Renameuser
  • ReplaceText
  • Scribunto
  • SpamBlacklist
  • SyntaxHighlight_GeSHi
  • TextExtracts
  • TitleBlacklist
  • WikiEditor
  • Arrays
  • Auth_remoteuser
  • CirrusSearch
  • ConfirmAccount
  • CommentStreams
  • Data Transfer
  • DisplayTitle
  • DynamicPageList
  • Echo
  • ExternalData
  • Email Authorization
  • FlaggedRevs
  • GraphViz
  • googleAnalytics
  • Header Tabs
  • Hit Counter
  • JSBreadCrumbs
  • LDAPProvider
  • LDAPAuthentication2
  • LDAPAuthorization
  • LDAPGroups
  • LDAPUserInfo
  • Lockdown
  • Maps
  • Math
  • Mermaid
  • Mpdf
  • MsCalendar
  • MsUpload
  • MultimediaViewer
  • MyVariables
  • OpenID Connect
  • Page Forms
  • Pipe Escape
  • PluggableAuth
  • Popups
  • SimpleSAMLphp
  • Tabs
  • TemplateData
  • TemplateStyles
  • TitleIcon
  • UploadWizard
  • UrlGetParameters
  • UserFunctions
  • UserMerge
  • Variables
  • VisualEditor
  • Widgets
  • YouTube
  • Cargo
  • Semantic MediaWiki
  • Semantic Result Formats
  • Semantic Scribunto
  • MonoBook
  • Timeless
  • Vector
  • Chameleon 2.0
  • Erudite
  • Foreground
  • Metrolook

It also comes with a "best practice default configuration" for all of these extensions/skins.

Technical details

  • The distribution is build using composer and published as "tarball" and "docker image" (may include Parsoid and ElasticSearch).

Release and distribution

  • Approach: The releases of Sunflower will / can be delivered by Hallo Welt! for the MediaWiki Stakeholders. MWStakeholders offer an automatically provisioned (?) rolling release on a public download portal: http://sunflowermediawiki.org/
  • There will be only one edition, where different sets of extensions can be enabled

Branding

A branding of one's own is time-consuming but necessary in order to create a project that is attractive and open to all stakeholders (from Wikimedia to Nichework, Meza to SMW) and builds bridges here.

Open questions

  • Distribution:
    • Adding Semantic / Cargo? BlueSpice Foundation? Basix extensions for extension families
  • Decision making and responsiblities
    • Release Board: Who will attend?
  • Roadmap?