Difference between revisions of "Sunflower MediaWiki"

From mwstake
Jump to: navigation, search
m (Objectives)
Line 9: Line 9:
 
#Organize the maintenance of the included extensions
 
#Organize the maintenance of the included extensions
 
#Development of a common basis for different projects: Meza, Semantic MediaWiki, BlueSpice MediaWiki, Language Bundle and many more
 
#Development of a common basis for different projects: Meza, Semantic MediaWiki, BlueSpice MediaWiki, Language Bundle and many more
** Forstering stability
+
## Forstering stability
** Forstering awareness and defining with which basic functions new functions have to work together
+
## Forstering awareness and defining with which basic functions new functions have to work together
** In the best case: Development of programming standards and agreement on technologies and architectures
+
## In the best case: Development of programming standards and agreement on technologies and architectures
  
 
==Target group==
 
==Target group==

Revision as of 10:58, 7 November 2019

Sunflower MediaWiki is a new multi-purpose MediaWiki distribution.

(This is a draft)

Objectives[edit]

  1. Delivery an "essential MediaWiki" for admins around the world
  2. Creation of a joint project and impact point for third-party users (non-profit and for-profit)
  3. Promotion of MediaWiki and additional bundles, communities, service providers
  4. Organize the maintenance of the included extensions
  5. Development of a common basis for different projects: Meza, Semantic MediaWiki, BlueSpice MediaWiki, Language Bundle and many more
    1. Forstering stability
    2. Forstering awareness and defining with which basic functions new functions have to work together
    3. In the best case: Development of programming standards and agreement on technologies and architectures

Target group[edit]

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

Distribution[edit]

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[edit]

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

Release and distribution[edit]

  • 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[edit]

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[edit]

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