MWStake - User contributions [en]

Sales deck/Sales Deck Construction

2020-06-03T22:30:29Z

Markus Glaser: /* Slide 5 */

[[File:Deck Outline.png|thumb|450px|Sales Deck background graphics showing the MediaWiki Sunflower.]]
The following is a working copy of the [[Sales deck]] to aid in collaboration. Each header section represents a slide in the deck. The thumbnail to the right is the slide deck background. See below for a working copy of the PowerPoint deck:
* [[:File:Sales Deck.pptx|Sales Deck (PowerPoint)]]

<div class="noautonum">__TOC__</div>

==Slide 1==
<big>'''MediaWiki Stakeholders' Group'''</big>

{{Font color|#2F5597|'''Your wiki, our passion'''}}

==Slide 2==
'''Our Mission'''

The MediaWiki Stakeholders' Group (MWStake) is a MediaWiki user group of:
* MediaWiki Developers
* System Administrators
* Users
* Consultants
* Hosting Providers

We cooperate towards our mission in order to improve the software and advocate the needs of MediaWiki users outside the Wikimedia Foundation (WMF), its projects and the traditional Wikimedia movement.

Thus to ensure MediaWiki becomes and stays the best fit open source wiki for knowledge sharing and documentation.

==Slide 3==
'''Ecosystem and Structure'''

MediaWiki Stakeholders' Group is a recognized Wikimedia Foundation (WMF) affiliation. The WMF was established as a nonprofit in 2003 to give Wikipedia ‘the largest source of human knowledge ever created’ a permanent home. Some Wikipedia numbers (2018):
* Wikipedia remains the only top 10 website that's a non-profit
* Wikipedia surpassed 50 million articles
* Volunteers added 2.5 million new articles
* 250,000+ volunteers contributed to Wikipedia each month
* We maintain Wikipedia with 350+ non-profit staff worldwide
* People visited Wikipedia 15 billion times each month
* AI bots scanned Wikipedia edits 86 million times per month to catch and correct vandalism

The MediaWiki Stakeholders’ Group Corporation was founded in 2019 to complement WMF. MWStake's current members are high profile members of the MediaWiki community. Many Members use or maintain MediaWiki in a professional environment, in corporations, highly visible sites or as advisors.

==Slide 4==
'''Activities'''

Since 2014, MWStake has been caring about the needs of MediaWiki maintainers. We raise the flag in:
* MediaWiki events
** Semantic MediaWiki Conferences
** Enterprise MediaWiki Conferences
** Hackathons
** Developer Summits
* Discussions
* Develop
* Fix bugs
* Work on documentation
* Standardize functionality
* Exchange experience
* Create a network

==Slide 5==
'''Relevancy'''

MediaWiki is widely used. Here’s some statistics and numbers. We co-power:
* 100,000k+ wikis <ref>141,469 unique wikis by 29th September 2019 per https://pingback.wmflabs.org/#unique-wiki-count</ref>
* 132m+ MediaWiki users <ref>132,887,711 users from wikis queried in 2020 by 3rd June per 2020 https://wikistats.wmflabs.org/ ; Total: 344,124,641 users</ref>
* 1,25m+ active users <ref>1,253,904 active users from wikis queried in 2020 by 3rd June 2020 per https://wikistats.wmflabs.org/ ; Total: 4,052,934 active users; Compare to 198,547 on Wikipedias; </ref>
* 500+ MediaWiki developers <ref>515 authors on git by 3rd June 2020 per https://wikimedia.biterg.io/</ref>
* 180m+ pages <ref>181,880,985 pages from wikis queried in 2020 by 3rd June 2020 per https://wikistats.wmflabs.org/ ; Total: 336,268,574</ref>
* 40m+ articles <ref>43,722,664 articles from wikis queried in 2020 by 3rd June 2020 per https://wikistats.wmflabs.org/ ; Total: 59,134,554</ref>
* 13m+ files <ref>13,519,034 files from wikis queried in 2020 by 3rd June 2020 per https://wikistats.wmflabs.org/ ; Total: 28,385,654 </ref>
* 1,2b+ edits <ref>629,813,566 edits from wikis queried in 2020 by 3rd June 2020 per https://wikistats.wmflabs.org/ ; Total: 1,266,649,765. Here, I think we can take the complete figure as these are all valid recorded edits</ref>

==Slide 6==
'''Workboard Topics'''

We validate and focus on the topics the MediaWiki Community and its Members put on the technical agenda:
* Installation (Meza, Composer RfC)
* Integration (LDAP)
* Use cases (Fantastic MediaWikis Track)
* Networking (EMWCon)
* Member projects
* Your project

==Slide 7==
'''Benefits & Incentives'''

Why should you join?
* Influence the direction of the group
* Help select projects
* Meet other MW users
* Exchange of ideas and experience
* Engage with conferences
* Shape the future of MediaWiki

==Slide 8==
[[File:Dues-Notes.png|thumb|450px]]
'''Membership'''

Becoming a Member, stakeholders contribute resources and money specifically to the development of MediaWiki.

Members can influence the features of MediaWiki with their resources.

Members enable MWStake to reach their Mission and Goals.

<br><div style="clear:both;"></div><br>
==References (Non slide)==
<references />

Sales deck/Sales Deck Construction

2020-06-03T22:22:35Z

Markus Glaser:

[[File:Deck Outline.png|thumb|450px|Sales Deck background graphics showing the MediaWiki Sunflower.]]
The following is a working copy of the [[Sales deck]] to aid in collaboration. Each header section represents a slide in the deck. The thumbnail to the right is the slide deck background. See below for a working copy of the PowerPoint deck:
* [[:File:Sales Deck.pptx|Sales Deck (PowerPoint)]]

<div class="noautonum">__TOC__</div>

==Slide 1==
<big>'''MediaWiki Stakeholders' Group'''</big>

{{Font color|#2F5597|'''Your wiki, our passion'''}}

==Slide 2==
'''Our Mission'''

The MediaWiki Stakeholders' Group (MWStake) is a MediaWiki user group of:
* MediaWiki Developers
* System Administrators
* Users
* Consultants
* Hosting Providers

We cooperate towards our mission in order to improve the software and advocate the needs of MediaWiki users outside the Wikimedia Foundation (WMF), its projects and the traditional Wikimedia movement.

Thus to ensure MediaWiki becomes and stays the best fit open source wiki for knowledge sharing and documentation.

==Slide 3==
'''Ecosystem and Structure'''

MediaWiki Stakeholders' Group is a recognized Wikimedia Foundation (WMF) affiliation. The WMF was established as a nonprofit in 2003 to give Wikipedia ‘the largest source of human knowledge ever created’ a permanent home. Some Wikipedia numbers (2018):
* Wikipedia remains the only top 10 website that's a non-profit
* Wikipedia surpassed 50 million articles
* Volunteers added 2.5 million new articles
* 250,000+ volunteers contributed to Wikipedia each month
* We maintain Wikipedia with 350+ non-profit staff worldwide
* People visited Wikipedia 15 billion times each month
* AI bots scanned Wikipedia edits 86 million times per month to catch and correct vandalism

The MediaWiki Stakeholders’ Group Corporation was founded in 2019 to complement WMF. MWStake's current members are high profile members of the MediaWiki community. Many Members use or maintain MediaWiki in a professional environment, in corporations, highly visible sites or as advisors.

==Slide 4==
'''Activities'''

Since 2014, MWStake has been caring about the needs of MediaWiki maintainers. We raise the flag in:
* MediaWiki events
** Semantic MediaWiki Conferences
** Enterprise MediaWiki Conferences
** Hackathons
** Developer Summits
* Discussions
* Develop
* Fix bugs
* Work on documentation
* Standardize functionality
* Exchange experience
* Create a network

==Slide 5==
'''Relevancy'''

MediaWiki is widely used. Here’s some statistics and numbers. We co-power:
* 100,000k+ wikis <ref>141,469 unique wikis by 29th September 2019 per https://pingback.wmflabs.org/#unique-wiki-count</ref>
* 132m+ MediaWiki users <ref>132,887,711 users from wikis queried in 2020 by 3rd June per 2020 https://wikistats.wmflabs.org/ ; Total: 344,124,641 users</ref>
* 1,25m+ active users <ref>1,253,904 active users from wikis queried in 2020 by 3rd June 2020 per https://wikistats.wmflabs.org/ ; Total: 4,052,934 active users; Compare to 198,547 on Wikipedias; </ref>
* [#] MediaWiki community members
* 180m+ pages <ref>181,880,985 pages from wikis queried in 2020 by 3rd June 2020 per https://wikistats.wmflabs.org/ ; Total: 336,268,574</ref>
* 40m+ articles <ref>43,722,664 articles from wikis queried in 2020 by 3rd June 2020 per https://wikistats.wmflabs.org/ ; Total: 59,134,554</ref>
* 13m+ files <ref>13,519,034 files from wikis queried in 2020 by 3rd June 2020 per https://wikistats.wmflabs.org/ ; Total: 28,385,654 </ref>
* 1,2b+ edits <ref>629,813,566 edits from wikis queried in 2020 by 3rd June 2020 per https://wikistats.wmflabs.org/ ; Total: 1,266,649,765. Here, I think we can take the complete figure as these are all valid recorded edits</ref>

==Slide 6==
'''Workboard Topics'''

We validate and focus on the topics the MediaWiki Community and its Members put on the technical agenda:
* Installation (Meza, Composer RfC)
* Integration (LDAP)
* Use cases (Fantastic MediaWikis Track)
* Networking (EMWCon)
* Member projects
* Your project

==Slide 7==
'''Benefits & Incentives'''

Why should you join?
* Influence the direction of the group
* Help select projects
* Meet other MW users
* Exchange of ideas and experience
* Engage with conferences
* Shape the future of MediaWiki

==Slide 8==
[[File:Dues-Notes.png|thumb|450px]]
'''Membership'''

Becoming a Member, stakeholders contribute resources and money specifically to the development of MediaWiki.

Members can influence the features of MediaWiki with their resources.

Members enable MWStake to reach their Mission and Goals.

<br><div style="clear:both;"></div><br>
==References (Non slide)==
<references />

Sales deck/Sales Deck Construction

2020-06-03T21:38:52Z

Markus Glaser: /* Slide 7 */

[[File:Deck Outline.png|thumb|450px|Sales Deck background graphics showing the MediaWiki Sunflower.]]
The following is a working copy of the [[Sales deck]] to aid in collaboration. Each header section represents a slide in the deck. The thumbnail to the right is the slide deck background. See below for a working copy of the PowerPoint deck:
* [[:File:Sales Deck.pptx|Sales Deck (PowerPoint)]]

<div class="noautonum">__TOC__</div>

==Slide 1==
<big>'''MediaWiki Stakeholders' Group'''</big>

{{Font color|#2F5597|'''Your wiki, our passion'''}}

==Slide 2==
'''Our Mission'''

The MediaWiki Stakeholders' Group (MWStake) is a MediaWiki user group of:
* MediaWiki Developers
* System Administrators
* Users
* Consultants
* Hosting Providers

We cooperate towards our mission in order to improve the software and advocate the needs of MediaWiki users outside the Wikimedia Foundation (WMF), its projects and the traditional Wikimedia movement.

Thus to ensure MediaWiki becomes and stays the best fit open source wiki for knowledge sharing and documentation.

==Slide 3==
'''Ecosystem and Structure'''

MediaWiki Stakeholders' Group is a recognized Wikimedia Foundation (WMF) affiliation. The WMF was established as a nonprofit in 2003 to give Wikipedia ‘the largest source of human knowledge ever created’ a permanent home. Some Wikipedia numbers (2018):
* Wikipedia remains the only top 10 website that's a non-profit
* Wikipedia surpassed 50 million articles
* Volunteers added 2.5 million new articles
* 250,000+ volunteers contributed to Wikipedia each month
* We maintain Wikipedia with 350+ non-profit staff worldwide
* People visited Wikipedia 15 billion times each month
* AI bots scanned Wikipedia edits 86 million times per month to catch and correct vandalism

The MediaWiki Stakeholders’ Group Corporation was founded in 2019 to complement WMF. MWStake's current members are high profile members of the MediaWiki community. Many Members use or maintain MediaWiki in a professional environment, in corporations, highly visible sites or as advisors.

==Slide 4==
'''Activities'''

Since 2014, MWStake has been caring about the needs of MediaWiki maintainers. We raise the flag in:
* MediaWiki events
** Semantic MediaWiki Conferences
** Enterprise MediaWiki Conferences
** Hackathons
** Developer Summits
* Discussions
* Develop
* Fix bugs
* Work on documentation
* Standardize functionality
* Exchange experience
* Create a network

==Slide 5==
'''Relevancy'''

MediaWiki is widely used. Here’s some statistics and numbers. We co-power:
* 100,000k+ wikis <ref>141,469 unique wikis by 29th September 2019 per https://pingback.wmflabs.org/#unique-wiki-count</ref>
* [#] MediaWiki users
* [#] MediaWiki community members
* [#] pages
* [#] articles
* [#] pages

==Slide 6==
'''Workboard Topics'''

We validate and focus on the topics the MediaWiki Community and its Members put on the technical agenda:
* Installation (Meza, Composer RfC)
* Integration (LDAP)
* Use cases (Fantastic MediaWikis Track)
* Networking (EMWCon)
* Member projects
* Your project

==Slide 7==
'''Benefits & Incentives'''

Why should you join?
* Influence the direction of the group
* Help select projects
* Meet other MW users
* Exchange of ideas and experience
* Engage with conferences
* Shape the future of MediaWiki

==Slide 8==
[[File:Dues-Notes.png|thumb|450px]]
'''Membership'''

Becoming a Member, stakeholders contribute resources and money specifically to the development of MediaWiki.

Members can influence the features of MediaWiki with their resources.

Members enable MWStake to reach their Mission and Goals.

<br><div style="clear:both;"></div><br>
==References (Non slide)==
<references />

Sales deck

2020-05-18T21:52:46Z

Markus Glaser: Some ideas

Some information about marketing collateral for the MWStake marketing sponsorship campaign.

==Team==
# Eric-Jan
# Markus
# James
# Bryan

==Subjects==
# Awareness raiser
#: ''Why should I read this deck?''
#: You love open source and the power of the engine behind Wikipedia? Us too. We are here to improve your experience.
# Mission statement
#: Claim could be something like "Ensure MediaWiki becomes and stays the best fit open source wiki for knowledge sharing and documentation"
#: See also [[mw:MediaWiki_Stakeholders%27_Group/Mission|our mission]]
# History and Activities
#: ''Proof that we can do it''
#: Since 2014, MWStake has been caring about the needs of MediaWiki maintainers.
#: We raise the flag in MediaWiki events and discussions; develop and standardize functionality; exchange experience; create a network
#: See our annual reports, e.g. [[mw:MediaWiki_Stakeholders%27_Group/Annual_Report_2018|2018]].
# Topics
#: ''What did we focus on?''
#: Installation (Meza, Composer RfC), Integration (LDAP), Use cases (Fantastic MediaWikis Track), Networking (EMWCon)
# Our Team
#: MWStake's current members are high profile members of the MediaWiki community.
#: Many of us use or maintain MediaWiki in a professional environment, in corporations, highly visible sites or as consultants (''find a better word, consultant always has a smell of "I want to make money"'')
# Corporation structure and ecosystem
#: ''Most people will want to hear how we are related to Wikipedia and its ecosystem.''
#: MediaWiki Stakeholders' Group is a recognized Wikimedia affiliation.
# Eco system (MediaWiki community, users)
# Membership
# Benefits

MWStake incorporation

2020-01-27T15:38:44Z

Markus Glaser: Some details

This page documents the project for mwstake incorporation. Members of mwstake decided to incorporate with the two main goals being:
# Bank account for events (EMWCon, etc.)
# Accept grants from the WMF as a non-profit

==To Do==
# Follow [https://meta.wikimedia.org/wiki/Grants:Processing/Rapid/New/Group instructions] to process the grant {{tick}}
# Determine [[MWStake incorporation/Non-profit type|which non-profit type]] to register as {{tick}}
# Work with lawyer to begin incorporation process {{tick}}
# Finalize the [[Bylaws]] {{tick}}
# Describe [[MWStake incorporation/Activities and Operational Information|Activities and Operational Information]] for IRS 1024 Application {{tick}}
# Open a corporate [[MWStake incorporation/bank account|bank account]] and make sure it [https://meta.wikimedia.org/wiki/Grants:Processing/Rapid/New/Organization follows WMF rules] which are similar to the rules for Rapid Grants {{tick}}
# [https://meta.wikimedia.org/wiki/Grants:Project/Rapid/Report Reporting] on the outcome (what worked well, what didn't work well, and what you would do differently next time, etc.). Some [https://meta.wikimedia.org/wiki/Grants:Project/Rapid/Plan/SampleReport sample reports] are available.

==History==
The following are the major milestones to date:
# '''02 August 2018''' - Collected [[{{PAGENAME}}/Individual statements|individual statements]] from MWStake members on what role they felt MWStake should have once incorporated
# '''15 August 2018''' - [https://meta.wikimedia.org/wiki/Grants:Project/Rapid/MW-SG/Legal_fees_for_MediaWiki_Stakeholders%27_Group_incorporation_as_a_non-profit Rapid Grant Proposal] was submitted
# '''15 November 2018''' - The rapid grant was approved and moved to funded
# '''18 December 2018''' - [[{{PAGENAME}}/Board meeting|Board meeting]]
# '''21 November 2019''' - [[Event:97|Board meeting]]
# '''20 January 2020''' - [[Event:100|Board meeting]]

==Board rolls and structure==

{| class="wikitable sortable"
|-
! Name !! Role
|-
| Bryan Hilderbrand || Secretary
|-
| Cindy Cicalese || Member
|-
| Evita Hollis || Treasurer
|-
| James Montalvo || Vice President
|-
| Lex Sulzer || Member
|-
| Mark Hershberger || President
|-
| Markus Glaser || Member
|-
| - || Member (Open position)
|}

===Board member applicant request email===
The following proposed email will be sent out to mailing lists ([https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise Enterprise MediaWiki], [https://sourceforge.net/p/semediawiki/mailman/semediawiki-user/ SMW Users], [https://lists.wikimedia.org/mailman/listinfo/mediawiki-l MediaWiki-l]) in the attempt to fill and open Board Member position.

<pre>
Hi everyone,

The MediaWiki Stakeholders' Group (MWStake) [1][2] is a MediaWiki user group consisting of MediaWiki developers, system administrators, consultants, and hosting providers who cooperate in order to improve the software and advocate the needs of MediaWiki users outside the Wikimedia Foundation (WMF) and its projects. We have recently incorporated as a 501(c)(6), non-profit organization and are looking to fill an open Board Member position. In this position, you will take part in bootstrapping the formal organisation and have a voice in the overall strategy of the group. We expect a workload of one hour per week, including online meetings every three months. If you are interested, please send an email to admin@mwstake.org.

If you would like to learn more, feel free to join our next meeting (February 7th) [3] or chat on Riot [4].

Thank you,
Mark Hershberger
President, MWStake

[1] https://www.mediawiki.org/wiki/MediaWiki_Stakeholders%27_Group
[2] https://mwstake.org/mwstake/wiki/Main_Page
[3] https://mwstake.org/mwstake/wiki/Event:99
[4] https://riot.im/app/#/room/#mwstake-general:matrix.org
</pre>

==Costs==
{| class="wikitable"
|-
! Cost !! Description !! Notes
|-
| $125 || File Articles of Incorporation || rowspan="4" | Part of [[:File:Smoker Gard Invoice 1.pdf|Invoice #1]] (total = $380)
|-
| $85 || Publish Legal advertisement (newspaper)
|-
| $85 || Publish Legal advertisement (legal journal)
|-
| $85 || Corporate minutes book
|-
| $600 || Non-profit filing fee || Check sent to Smoker Gard made out to US Treasury
|- style="border-top-style: double;"
! $980 || colspan="2" style="text-align:left;" | Total
|}

==Subpages==
{{Special:PrefixIndex/{{FULLPAGENAME}}/}}

==Files==
* [[:File:EIN Application and Confirmation.pdf|EIN Application and Confirmation]]
* [[:File:Pennsylvania Dep. of State Bureau of Corps and Charitable Orgs..pdf|Pennsylvania Department of State Bureau of Corporations and Charitable Organizations]]
* [[:File:Smoker Gard Engagement Letter.pdf|Smoker Gard Engagement Letter]]
* [[:File:Smoker Gard Invoice 1.pdf|Smoker Gard Invoice #1]]
* [[:File:Business Resolution Authorization.pdf|Business Resolution Authorization]]
* [[:File:Signed Form 2848.pdf|Form 2848 to tell the IRS that Smoker Gard is our rep]]
* [[:File:Signed Form 1024.pdf|Form 1024 -- Application for Recognition of Exemption Under Section 501(a)]]
* [[:File:Cover.pdf|Copy of cover letter sent to IRS with the Form 1024]]
* [[:File:Smoker Gard Invoice 2.pdf|Smoker Gard Invoice #2]]

==Links==
* https://www.501c3.org/nonprofits-board-directors-board/
* https://www.501c3.org/avoiding-conflicts-of-interest/
* https://www.missionbox.com/article/68/board-officers-and-committees-what-structure-works-best

MWStake incorporation

2020-01-27T15:31:50Z

Markus Glaser: removed a whitespace

This page documents the project for mwstake incorporation. Members of mwstake decided to incorporate with the two main goals being:
# Bank account for events (EMWCon, etc.)
# Accept grants from the WMF as a non-profit

==To Do==
# Follow [https://meta.wikimedia.org/wiki/Grants:Processing/Rapid/New/Group instructions] to process the grant {{tick}}
# Determine [[MWStake incorporation/Non-profit type|which non-profit type]] to register as {{tick}}
# Work with lawyer to begin incorporation process {{tick}}
# Finalize the [[Bylaws]] {{tick}}
# Describe [[MWStake incorporation/Activities and Operational Information|Activities and Operational Information]] for IRS 1024 Application {{tick}}
# Open a corporate [[MWStake incorporation/bank account|bank account]] and make sure it [https://meta.wikimedia.org/wiki/Grants:Processing/Rapid/New/Organization follows WMF rules] which are similar to the rules for Rapid Grants {{tick}}
# [https://meta.wikimedia.org/wiki/Grants:Project/Rapid/Report Reporting] on the outcome (what worked well, what didn't work well, and what you would do differently next time, etc.). Some [https://meta.wikimedia.org/wiki/Grants:Project/Rapid/Plan/SampleReport sample reports] are available.

==History==
The following are the major milestones to date:
# '''02 August 2018''' - Collected [[{{PAGENAME}}/Individual statements|individual statements]] from MWStake members on what role they felt MWStake should have once incorporated
# '''15 August 2018''' - [https://meta.wikimedia.org/wiki/Grants:Project/Rapid/MW-SG/Legal_fees_for_MediaWiki_Stakeholders%27_Group_incorporation_as_a_non-profit Rapid Grant Proposal] was submitted
# '''15 November 2018''' - The rapid grant was approved and moved to funded
# '''18 December 2018''' - [[{{PAGENAME}}/Board meeting|Board meeting]]
# '''21 November 2019''' - [[Event:97|Board meeting]]
# '''20 January 2020''' - [[Event:100|Board meeting]]

==Board rolls and structure==

{| class="wikitable sortable"
|-
! Name !! Role
|-
| Bryan Hilderbrand || Secretary
|-
| Cindy Cicalese || Member
|-
| Evita Hollis || Treasurer
|-
| James Montalvo || Vice President
|-
| Lex Sulzer || Member
|-
| Mark Hershberger || President
|-
| Markus Glaser || Member
|-
| - || Member (Open position)
|}

===Board member applicant request email===
The following proposed email will be sent out to mailing lists ([https://lists.wikimedia.org/mailman/listinfo/mediawiki-enterprise Enterprise MediaWiki], [https://sourceforge.net/p/semediawiki/mailman/semediawiki-user/ SMW Users], [https://lists.wikimedia.org/mailman/listinfo/mediawiki-l MediaWiki-l]) in the attempt to fill and open Board Member position.

<pre>
Hi everyone,

The MediaWiki Stakeholders' Group (MWStake) [1][2] is a MediaWiki user group consisting of MediaWiki developers, system administrators, consultants, and hosting providers who cooperate in order to improve the software and advocate the needs of MediaWiki users outside the Wikimedia Foundation (WMF) and its projects. We have recently incorporated as a 501(c)(6), non-profit organization and are looking to fill an open Board Member position. If you are interested, please send an email to admin@mwstake.org.

If you would like to learn more, feel free to join our next meeting (February 7th) [3] or chat on Riot [4].

Thank you,
Mark Hershberger
President, MWStake

[1] https://www.mediawiki.org/wiki/MediaWiki_Stakeholders%27_Group
[2] https://mwstake.org/mwstake/wiki/Main_Page
[3] https://mwstake.org/mwstake/wiki/Event:99
[4] https://riot.im/app/#/room/#mwstake-general:matrix.org
</pre>

==Costs==
{| class="wikitable"
|-
! Cost !! Description !! Notes
|-
| $125 || File Articles of Incorporation || rowspan="4" | Part of [[:File:Smoker Gard Invoice 1.pdf|Invoice #1]] (total = $380)
|-
| $85 || Publish Legal advertisement (newspaper)
|-
| $85 || Publish Legal advertisement (legal journal)
|-
| $85 || Corporate minutes book
|-
| $600 || Non-profit filing fee || Check sent to Smoker Gard made out to US Treasury
|- style="border-top-style: double;"
! $980 || colspan="2" style="text-align:left;" | Total
|}

==Subpages==
{{Special:PrefixIndex/{{FULLPAGENAME}}/}}

==Files==
* [[:File:EIN Application and Confirmation.pdf|EIN Application and Confirmation]]
* [[:File:Pennsylvania Dep. of State Bureau of Corps and Charitable Orgs..pdf|Pennsylvania Department of State Bureau of Corporations and Charitable Organizations]]
* [[:File:Smoker Gard Engagement Letter.pdf|Smoker Gard Engagement Letter]]
* [[:File:Smoker Gard Invoice 1.pdf|Smoker Gard Invoice #1]]
* [[:File:Business Resolution Authorization.pdf|Business Resolution Authorization]]
* [[:File:Signed Form 2848.pdf|Form 2848 to tell the IRS that Smoker Gard is our rep]]
* [[:File:Signed Form 1024.pdf|Form 1024 -- Application for Recognition of Exemption Under Section 501(a)]]
* [[:File:Cover.pdf|Copy of cover letter sent to IRS with the Form 1024]]
* [[:File:Smoker Gard Invoice 2.pdf|Smoker Gard Invoice #2]]

==Links==
* https://www.501c3.org/nonprofits-board-directors-board/
* https://www.501c3.org/avoiding-conflicts-of-interest/
* https://www.missionbox.com/article/68/board-officers-and-committees-what-structure-works-best

Sunflower MediaWiki

2019-11-14T13:45:07Z

Markus Glaser: Can we maintain it?

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:
#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:
##Organizing the maintenance of the included extensions
##Sharpening awareness of the basic functions with which new functions must cooperate
##Providing a basis for the technical developments of various projects: Meza, Semantic MediaWiki, BlueSpice MediaWiki, Language Bundle and many more
##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

{| class="wikitable sortable"
|+
! |Extension / skin name
! |Maintained
! |Maintainer
!Activated
!MWStake
!Notes
|-
| |'''Extensions'''
|
|
|
|
|
|-
| |[[mw:Extension:Arrays|Arrays]]
|no
|
|
|?
|
|-
| |[[mw:Extension:Auth_remoteuser|Auth_remoteuser]]
|yes
|
|
|yes
|
|-
| |[[mw:Extension:Cargo|Cargo]]
|yes
|Yaron Koren / WikiWorks
|no
|
|
|-
| |[[mw:Extension:CategoryTree|CategoryTree]]
|
|
|
|yes
|bundled with MW
|-
| |[[mw:Extension:CirrusSearch|CirrusSearch]]
|
|
|
|no
|
|-
| |[[mw:Extension:Cite|Cite]]
|
|
|
|no
|
|-
| |[[mw:Extension:CiteThisPage|CiteThisPage]]
|
|
|
|yes
|
|-
| |[[mw:Extension:CodeEditor|CodeEditor]]
|yes
|
|
|yes
|necessary for code edits within the VisualEditor
|-
| |[[mw:Extension:CommentStreams|CommentStreams]]
|yes
|
|
|yes
|
|-
| |[[mw:Extension:ConfirmAccount|ConfirmAccount]]
|yes
|
|
|yes
|
|-
| |[[mw:Extension:ConfirmEdit|ConfirmEdit]]
|yes
|
|
|yes
|
|-
| |[[mw:Extension:DataTransfer|DataTransfer]]
|yes
|Yaron Koren
|
|yes
|
|- |
| |[[mw:Extension:DisplayTitle|DisplayTitle]]
|yes
|
|
|yes
|
|-
| |[[mw:Extension:DynamicPageList|DynamicPageList]]
|yes
|
|
|no
|DynamicPageList3?
|-
| |[[mw:Extension:Echo|Echo]]
|yes?
|
|
|no
|
|-
| |[[mw:Extension:EmailAuthorization|EmailAuthorization]]
|
|
|
|yes
|EmailAuth?
|-
| |[[mw:Extension:ExternalData|ExternalData]]
|
|
|
|no
|
|-
| |[[mw:Extension:FlaggedRevs|FlaggedRevs]]
|yes
|
|
|no
|
|-
| |[[mw:Extension:Gadgets|Gadgets]]
|
|
|
|no
|
|-
| |[[mw:Extension:googleAnalytics|googleAnalytics]]
|
|
|
|yes
|
|-
| |[[mw:Extension:GraphViz|GraphViz]]
|
|
|
|yes
|
|-
| |[[mw:Extension:HeaderTabs|HeaderTabs]]
|
|
|
|yes
|
|-
| |[[mw:Extension:HitCounter|HitCounter]]
|
|
|
|yes
|
|-
| |[[mw:Extension:ImageMap|ImageMap]]
|
|
|
|yes
|
|-
| |[[mw:Extension:InputBox|InputBox]]
|
|
|
|yes
|
|-
| |[[mw:Extension:Interwiki|Interwiki]]
|
|
|
|yes
|
|-
| |[[mw:Extension:JSBreadCrumbs|JSBreadCrumbs]]
|
|
|
|yes
|
|-
| |[[mw:Extension:LDAPAuthentication2|LDAPAuthentication2]]
|
|
|
|yes
|
|-
| |[[mw:Extension:LDAPAuthorization|LDAPAuthorization]]
|
|
|
|yes
|
|-
| |[[mw:Extension:LDAPGroups|LDAPGroups]]
|
|
|
|yes
|
|-
| |[[mw:Extension:LDAPProvider|LDAPProvider]]
|
|
|
|yes
|
|-
| |[[mw:Extension:LDAPUserInfo|LDAPUserInfo]]
|
|
|
|yes
|
|-
| |[[mw:Extension:LocalisationUpdate|LocalisationUpdate]]
|
|
|
|no
|
|-
| |[[mw:Extension:Lockdown|Lockdown]]
|
|
|
|yes
|
|-
| |[[mw:Extension:Maps|Maps]]
|
|
|
|no
|
|-
| |[[mw:Extension:Math|Math]]
|
|
|
|no
|
|-
| |[[mw:Extension:Mermaid|Mermaid]]
|
|
|
|
|
|-
| |[[mw:Extension:Mpdf|Mpdf]]
|
|
|
|
|
|-
| |[[mw:Extension:MsCalendar|MsCalendar]]
|
|
|
|
|
|-
| |[[mw:Extension:MsUpload|MsUpload]]
|
|
|
|
|
|-
| |[[mw:Extension:MultimediaViewer|MultimediaViewer]]
|yes
|Wikimedia Foundation
|
|no
|
|-
| |[[mw:Extension:MyVariables|MyVariables]]
|
|
|
|
|
|-
| |[[mw:Extension:Nuke|Nuke]]
|
|
|
|
|
|-
| |[[mw:Extension:OATHAuth|OATHAuth]]
|yes
|Wikimedia Foundation
|
|
|
|-
| |[[mw:Extension:OpenIDConnect|OpenIDConnect]]
|
|
|
|
|
|-
| |[[mw:Extension:PageForms|PageForms]]
|yes
|Yaron Koren / WikiWorks
|
|
|
|-
| |[[mw:Extension:PageImages|PageImages]]
|
|
|
|
|
|-
| |[[mw:Extension:ParserFunctions|ParserFunctions]]
|
|
|
|
|
|-
| |[[mw:Extension:PdfHandler|PdfHandler]]
|
|
|
|
|
|-
| |[[mw:Extension:PipeEscape|PipeEscape]]
|
|
|
|
|
|-
| |[[mw:Extension:PluggableAuth|PluggableAuth]]
|
|
|
|
|
|-
| |[[mw:Extension:Poem|Poem]]
|
|
|
|
|
|-
| |[[mw:Extension:Popups|Popups]]
|
|
|
|
|
|-
| |[[mw:Extension:Renameuser|Renameuser]]
|
|
|
|
|
|-
| |[[mw:Extension:ReplaceText|ReplaceText]]
|
|
|
|
|
|-
| |[[mw:Extension:Scribunto|Scribunto]]
|
|
|
|
|
|-
| |[[mw:Extension:SemanticMediaWiki|SemanticMediaWiki]]
|yes
|mwjames
|no
|no
|
|-
| |[[mw:Extension:SemanticResultFormats|SemanticResultFormats]]
|
|
|
|no
|
|-
| |[[mw:Extension:SemanticScribunto|SemanticScribunto]]
|
|
|
|no
|
|-
| |[[mw:Extension:SimpleSAMLphp|SimpleSAMLphp]]
|
|
|
|
|
|- ]]
| |[[mw:Extension:SpamBlacklist|SpamBlacklist]]
|
|
|
|
|
|-
| |[[mw:Extension:SyntaxHighlight_GeSHi|SyntaxHighlight_GeSHi]]
|
|
|
|
|
|-
| |[[mw:Extension:Tabs|Tabs]]
|
|
|
|
|
|-
| |[[mw:Extension:TemplateData|TemplateData]]
|
|
|
|
|
|-
| |[[mw:Extension:TemplateStyles|TemplateStyles]]
|
|
|
|
|
|-
| |[[mw:Extension:TextExtracts|TextExtracts]]
|
|
|
|
|
|-
| |[[mw:Extension:TitleBlacklist|TitleBlacklist]]
|
|
|
|
|
|-
| |[[mw:Extension:TitleIcon|TitleIcon]]
|
|
|
|
|
|-
| |[[mw:Extension:UploadWizard|UploadWizard]]
|
|
|
|
|
|-
| |[[mw:Extension:UrlGetParameters|UrlGetParameters]]
|
|
|
|
|
|-
| |[[mw:Extension:UserFunctions|UserFunctions]]
|
|
|
|
|
|-
| |[[mw:Extension:UserMerge|UserMerge]]
|
|
|
|
|
|-
| |[[mw:Extension:Variables|Variables]]
|
|
|
|
|
|-
| |[[mw:Extension:VisualEditor|VisualEditor]]
|yes
|Wikimedia Foundation
|
|no
|
|-
| |[[mw:Extension:Widgets|Widgets]]
|
|
|
|no
|
|-
| |[[mw:Extension:WikiEditor|WikiEditor]]
|
|
|
|no
|
|-
| |[[mw:Extension:YouTube|YouTube]]
|
|
|
|
|
|-
| |'''Skins'''
|
|
|
|
|
|-
| |[[mw:Skin:MonoBook|MonoBook]]
|
|
|
|no
|
|-
| |[[mw:Skin:Timeless|Timeless]]
|
|
|
|no
|
|-
| |[[mw:Skin:Vector|Vector]]
|
|
|
|no
|
|-
| |[[mw:Skin:Chameleon|Chameleon 2.0]]
|yes
|Stephan Gambke
|
|no
|
|-
| |[[mw:Skin:Erudite|Erudite]]
|
|
|
|no
|
|-
| |[[mw:Skin:Foreground|Foreground]]
|
|
|
|no
|
|-
| |[[mw:Skin:Metrolook|Metrolook]]
|
|
|
|no
|
|}

==Technical details==
* The distribution comes with a "best practice default configuration" for all extensions/skins.
* The distribution is build using <code>composer</code> 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:
**Dealing with mutually excluding extensions (like Semantic / Cargo, Google Analytics / Matomo): extensions can be part of the distribution, but they are not activated
*Decision making and responsiblities
**Release Board / Sunflower Consortium: Who will attend?
*Roadmap?
** First release in February 2020?

Sunflower MediaWiki

2019-11-14T13:14:13Z

Markus Glaser: added links to extensions / skins

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:
#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:
##Organizing the maintenance of the included extensions
##Sharpening awareness of the basic functions with which new functions must cooperate
##Providing a basis for the technical developments of various projects: Meza, Semantic MediaWiki, BlueSpice MediaWiki, Language Bundle and many more
##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

{| class="wikitable sortable"
|+
! |Extension / skin name
! |Maintained
! |Maintainer
!Activated
!Notes
|-
| |'''Extensions'''
|
|
|
|
|-
| |[[mw:Extension:Arrays|Arrays]]
|
|
|
|
|-
| |[[mw:Extension:Auth_remoteuser|Auth_remoteuser]]
|
|
|
|
|-
| |[[mw:Extension:Cargo|Cargo]]
|yes
|Yaron Koren / WikiWorks
|no
|
|-
| |[[mw:Extension:CategoryTree|CategoryTree]]
|
|
|
|
|-
| |[[mw:Extension:CirrusSearch|CirrusSearch]]
|
|
|
|
|-
| |[[mw:Extension:Cite|Cite]]
|
|
|
|
|-
| |[[mw:Extension:CiteThisPage|CiteThisPage]]
|
|
|
|
|-
| |[[mw:Extension:CodeEditor|CodeEditor]]
|yes
|
|
|necessary for code edits within the VisualEditor
|-
| |[[mw:Extension:CommentStreams|CommentStreams]]
|
|
|
|
|-
| |[[mw:Extension:ConfirmAccount|ConfirmAccount]]
|
|
|
|
|-
| |[[mw:Extension:ConfirmEdit|ConfirmEdit]]
|
|
|
|
|-
| |[[mw:Extension:DataTransfer|DataTransfer]]
|
|
|
|
|- |
| |[[mw:Extension:DisplayTitle|DisplayTitle]]
|
|
|
|
|-
| |[[mw:Extension:DynamicPageList|DynamicPageList]]
|
|
|
|
|-
| |[[mw:Extension:Echo|Echo]]
|
|
|
|
|-
| |[[mw:Extension:EmailAuthorization|EmailAuthorization]]
|
|
|
|
|-
| |[[mw:Extension:ExternalData|ExternalData]]
|
|
|
|
|-
| |[[mw:Extension:FlaggedRevs|FlaggedRevs]]
|yes
|
|
|
|-
| |[[mw:Extension:Gadgets|Gadgets]]
|
|
|
|
|-
| |[[mw:Extension:googleAnalytics|googleAnalytics]]
|
|
|
|
|-
| |[[mw:Extension:GraphViz|GraphViz]]
|
|
|
|
|-
| |[[mw:Extension:HeaderTabs|HeaderTabs]]
|
|
|
|
|-
| |[[mw:Extension:HitCounter|HitCounter]]
|
|
|
|
|-
| |[[mw:Extension:ImageMap|ImageMap]]
|
|
|
|
|-
| |[[mw:Extension:InputBox|InputBox]]
|
|
|
|
|-
| |[[mw:Extension:Interwiki|Interwiki]]
|
|
|
|
|-
| |[[mw:Extension:JSBreadCrumbs|JSBreadCrumbs]]
|
|
|
|
|-
| |[[mw:Extension:LDAPAuthentication2|LDAPAuthentication2]]
|
|
|
|
|-
| |[[mw:Extension:LDAPAuthorization|LDAPAuthorization]]
|
|
|
|
|-
| |[[mw:Extension:LDAPGroups|LDAPGroups]]
|
|
|
|
|-
| |[[mw:Extension:LDAPProvider|LDAPProvider]]
|
|
|
|
|-
| |[[mw:Extension:LDAPUserInfo|LDAPUserInfo]]
|
|
|
|
|-
| |[[mw:Extension:LocalisationUpdate|LocalisationUpdate]]
|
|
|
|
|-
| |[[mw:Extension:Lockdown|Lockdown]]
|
|
|
|
|-
| |[[mw:Extension:Maps|Maps]]
|
|
|
|
|-
| |[[mw:Extension:Math|Math]]
|
|
|
|
|-
| |[[mw:Extension:Mermaid|Mermaid]]
|
|
|
|
|-
| |[[mw:Extension:Mpdf|Mpdf]]
|
|
|
|
|-
| |[[mw:Extension:MsCalendar|MsCalendar]]
|
|
|
|
|-
| |[[mw:Extension:MsUpload|MsUpload]]
|
|
|
|
|-
| |[[mw:Extension:MultimediaViewer|MultimediaViewer]]
|yes
|Wikimedia Foundation
|
|
|-
| |[[mw:Extension:MyVariables|MyVariables]]
|
|
|
|
|-
| |[[mw:Extension:Nuke|Nuke]]
|
|
|
|
|-
| |[[mw:Extension:OATHAuth|OATHAuth]]
|yes
|Wikimedia Foundation
|
|
|-
| |[[mw:Extension:OpenIDConnect|OpenIDConnect]]
|
|
|
|
|-
| |[[mw:Extension:PageForms|PageForms]]
|yes
|Yaron Koren / WikiWorks
|
|
|-
| |[[mw:Extension:PageImages|PageImages]]
|
|
|
|
|-
| |[[mw:Extension:ParserFunctions|ParserFunctions]]
|
|
|
|
|-
| |[[mw:Extension:PdfHandler|PdfHandler]]
|
|
|
|
|-
| |[[mw:Extension:PipeEscape|PipeEscape]]
|
|
|
|
|-
| |[[mw:Extension:PluggableAuth|PluggableAuth]]
|
|
|
|
|-
| |[[mw:Extension:Poem|Poem]]
|
|
|
|
|-
| |[[mw:Extension:Popups|Popups]]
|
|
|
|
|-
| |[[mw:Extension:Renameuser|Renameuser]]
|
|
|
|
|-
| |[[mw:Extension:ReplaceText|ReplaceText]]
|
|
|
|
|-
| |[[mw:Extension:Scribunto|Scribunto]]
|
|
|
|
|-
| |[[mw:Extension:SemanticMediaWiki|SemanticMediaWiki]]
|yes
|mwjames
|no
|
|-
| |[[mw:Extension:SemanticResultFormats|SemanticResultFormats]]
|
|
|
|
|-
| |[[mw:Extension:SemanticScribunto|SemanticScribunto]]
|
|
|
|
|-
| |[[mw:Extension:SimpleSAMLphp|SimpleSAMLphp]]
|
|
|
|
|- ]]
| |[[mw:Extension:SpamBlacklist|SpamBlacklist]]
|
|
|
|
|-
| |[[mw:Extension:SyntaxHighlight_GeSHi|SyntaxHighlight_GeSHi]]
|
|
|
|
|-
| |[[mw:Extension:Tabs|Tabs]]
|
|
|
|
|-
| |[[mw:Extension:TemplateData|TemplateData]]
|
|
|
|
|-
| |[[mw:Extension:TemplateStyles|TemplateStyles]]
|
|
|
|
|-
| |[[mw:Extension:TextExtracts|TextExtracts]]
|
|
|
|
|-
| |[[mw:Extension:TitleBlacklist|TitleBlacklist]]
|
|
|
|
|-
| |[[mw:Extension:TitleIcon|TitleIcon]]
|
|
|
|
|-
| |[[mw:Extension:UploadWizard|UploadWizard]]
|
|
|
|
|-
| |[[mw:Extension:UrlGetParameters|UrlGetParameters]]
|
|
|
|
|-
| |[[mw:Extension:UserFunctions|UserFunctions]]
|
|
|
|
|-
| |[[mw:Extension:UserMerge|UserMerge]]
|
|
|
|
|-
| |[[mw:Extension:Variables|Variables]]
|
|
|
|
|-
| |[[mw:Extension:VisualEditor|VisualEditor]]
|yes
|Wikimedia Foundation
|
|
|-
| |[[mw:Extension:Widgets|Widgets]]
|
|
|
|
|-
| |[[mw:Extension:WikiEditor|WikiEditor]]
|
|
|
|
|-
| |[[mw:Extension:YouTube|YouTube]]
|
|
|
|
|-
| |'''Skins'''
|
|
|
|
|-
| |[[mw:Skin:MonoBook|MonoBook]]
|
|
|
|
|-
| |[[mw:Skin:Timeless|Timeless]]
|
|
|
|
|-
| |[[mw:Skin:Vector|Vector]]
|
|
|
|
|-
| |[[mw:Skin:Chameleon|Chameleon 2.0]]
|yes
|Stephan Gambke
|
|
|-
| |[[mw:Skin:Erudite|Erudite]]
|
|
|
|
|-
| |[[mw:Skin:Foreground|Foreground]]
|
|
|
|
|-
| |[[mw:Skin:Metrolook|Metrolook]]
|
|
|
|
|}

==Technical details==
* The distribution comes with a "best practice default configuration" for all extensions/skins.
* The distribution is build using <code>composer</code> 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:
**Dealing with mutually excluding extensions (like Semantic / Cargo, Google Analytics / Matomo): extensions can be part of the distribution, but they are not activated
*Decision making and responsiblities
**Release Board / Sunflower Consortium: Who will attend?
*Roadmap?
** First release in February 2020?

Event:95

2019-11-01T15:21:17Z

Markus Glaser:

{{Event
|mwstake-meeting=Yes
|start-date=2019/11/01
|start-hour=15
|start-minute=30
|end-date=2019/11/01
|end-hour=16
|end-minute=30
|url=https://meet.google.com/mdd-ufhn-ksb
}}
==Meeting agenda==
# '''Wait for attendees & chat''' {{Agenda time|5 min}}
# '''Wiki Quickie''' {{Agenda time|15 min}} {{Agenda presenter|Rich E.}} - '''Process & Safety Management (PSM) with MW + SMW'''
#* Discussing an implementation of Hazard & Risk analysis for [https://en.wikipedia.org/wiki/Process_safety_management PSM] to meet ISO & OSHA requirements using MediaWiki + Semantic MediaWiki
# '''Update on EMWCon 2020''' {{Agenda time|10 min}} {{Agenda presenter|Rich E.}}
#* Information about next year's [https://www.mediawiki.org/wiki/EMWCon_Spring_2020 EMWCon Spring 2020 EMWCon] including a new [https://emw-meza.site/emwcon/index.php/Main_Page conference website]
# '''OAuth 2.0 support for MediaWiki and updating the OAuth extension''' {{Agenda time|10 min}} {{Agenda presenter|Dejan Savuljesku}}
#* Hallo Welt! is working with the Wikimedia Foundation to bring OAuth 2.0 support for MediaWiki and updating the OAuth extension
#* Brief [https://developer.okta.com/blog/2019/10/21/illustrated-guide-to-oauth-and-oidc Illustrated Guide] on OAuth
# '''MediaWiki blog''' {{Agenda time|5 min}} {{Agenda presenter|Richard Heigl}}
#* We need articles for the blog and other progress updates
# '''Agenda Item''' {{Agenda time|xx min}} {{Agenda presenter|Presenter}}
# '''Wiki Watercooler''' {{Agenda time|remaining}} {{Agenda presenter|Open Mic}}
#* Present any current issues you are having or things you're working on, ask the group for help/recommendations/suggestions
#* Add any Wiki Watercooler items you may have to the [https://etherpad.wikimedia.org/p/mwstake-2019-11 Etherpad]

==Notes==
Shared notes: https://etherpad.wikimedia.org/p/mwstake-2019-11

==Action board==
{{Actionable board
|Open
|{{PAGENAME}}
|Extension, Conference
|True
|View
|{{PAGENAME}}
}}

Talk:Bylaws

2019-04-26T18:12:06Z

Markus Glaser: /* Toward Consensus */ Markus

The [[Bylaws]] page is modified using the following:
# Making the subsections wiki headers, this allows specific sections (4.3.6, etc.)
#* This makes the TOC more complicated, but is fixed by <code><nowiki><div class="toclimit-2">__TOC__</div></nowiki></code> and changes to [[MediaWiki:Common.css|Common.css]]
#* However, doing this also removes the visibility of section numbering, but is fixed by adding the [https://www.mediawiki.org/wiki/Extension:NumberedHeadings NumberedHeadings] extension and adding <code>__NUMBEREDHEADINGS__</code>
#* This makes the sections different font sizes, but is fixed by changes to [[MediaWiki:Common.css|Common.css]]
# Removing section edit links by using <code><nowiki>__NOEDITSECTION__</nowiki></code>
# Edits on February 14, 2019, by Frank Taylor
#* Inserted commas after "be advised of" in provisions 3.6.1 and 3.6.2.
#* Reversed order of terms "Special Meeting of Members" and "Annual Meeting of Members" in provision 4.6.2.2.
#* Inserted explanations in note 4, note 8, and note 14.
# Edits on February 24, 2019, by Frank Taylor
#* Changed “shall” to “will” in 3.7.2.1, 4.5.2.3.4, and 5.1.1.
#* Changed number of directors from eight to nine in 5.1.1.
#* Added note to 4.5.2.3.4.
# The fee schedule is based on the Linux Foundation (another 501c6) [https://www.linuxfoundation.org/bylaws/#schedulea Bylaws]

== Toward Consensus ==
We need consensus from board members on the Bylaws. This section is for noting that.

===Mark===
My vote: {{aye}} --<span style="color:#d30000">☠</span>[[mw:User:MarkAHershberger|User:MarkAHershberger]]<span style="color:#d30000">☢</span>([[User_talk:MarkAHershberger|talk]])<span style="color:#d30000">☣</span> 14:11, 23 April 2019 (EDT)

===James===
I’m good with the bylaws, except that I think we should have measurable actions we plan to take for section 2.3. Those measurements and action specifics don’t need to be in the bylaws, and probably shouldn’t be, but perhaps should be linked from it. Examples: 2.3.1-commit X patches to MW core, Y of which close out preexisting Phabricator tasks.

2.3.2 is what we were talking about with Ext:Duplicator. We need to formalize what we plan to do with it
:Right, putting the specific things we're working on in the Bylaws wouldn't be appropriate. How about updating the bylaws to point to a specific way to track our current activities? --<span style="color:#d30000">☠</span>[[mw:User:MarkAHershberger|User:MarkAHershberger]]<span style="color:#d30000">☢</span>([[User_talk:MarkAHershberger|talk]])<span style="color:#d30000">☣</span> 14:13, 23 April 2019 (EDT)

===Bryan===
: My vote: {{aye}} --[[User:Bryandamon|Bryandamon]] ([[User talk:Bryandamon|talk]]) 22:25, 23 April 2019 (EDT)

===Cindy===
: My vote: {{aye}} --[[User:Cindy Cicalese|Cindy Cicalese]] ([[User talk:Cindy Cicalese|talk]]) 11:25, 24 April 2019 (EDT)

===Sabine===
: My vote: {{aye}} --[[User:Sabine.melnicki|Sabine.melnicki]] ([[User talk:Sabine.melnicki|talk]]) 10:57, 25 April 2019 (EDT)

===Markus===
: My vote: {{aye}} --[[User:Markus Glaser|Markus Glaser]] ([[User talk:Markus Glaser|talk]]) 14:12, 26 April 2019 (EDT)

Bylaws

2019-04-26T18:09:10Z

Markus Glaser: Fixed typos

<div class="toclimit-2" style="float:right;">__TOC__</div>
__NUMBEREDHEADINGS__
__NOEDITSECTION__
Bylaws of '''MediaWiki Stakeholders' Group''' (MWStake).

==Name, Location, and Applicable Law==
===The name of the corporation will be '''MediaWiki Stakeholders' Group''' (hereinafter "the Corporation").===
===The headquarters will be at '''739 Main Street, Akron Pennsylvania 17501''', which may from time to time be changed by resolution of the board of directors.===

===The Corporation will be governed by the laws of the '''State of Pennsylvania''' and the '''United States of America'''.===

==Vision, Purpose, and Activities==
===The '''Vision''' of the corporation is to '''make MediaWiki the most effective open source knowledge sharing software'''.===
===The '''Purpose''' of the Corporation is to '''preserve and promote MediaWiki as open-source collaboration software for the benefit of all users'''.===
===The Corporation will engage in '''Activities''' to support this purpose:===
==== Contribute to the development of MediaWiki; ====
==== Maintain MediaWiki and its extensions; ====
==== Improve documentation for MediaWiki and its extensions; ====
==== Cooperate and liaison with the Wikimedia Foundation, Inc.; ====
==== Coordinate between MediaWiki developers, operators, and users; ====
==== Promote MediaWiki to the public; ====
==== Act as a patron and coordinator for international gatherings, conferences, hackathons, etc.; ====
==== Advocate on behalf of third-party users of MediaWiki; and ====
==== Foster best practices for MediaWiki and its users. ====
===The Corporation does not contemplate pecuniary gain or profit, incidental or otherwise.===

==General Provisions==
===Effective Date, Savings Clause, Rules of Procedure, and Prohibition of discrimination===
====These Bylaws will become effective upon approval by the Board of Directors.====
====If any part of these Bylaws is determined by a court of law or other competent authority to be void, unenforceable, or otherwise illegal or invalid, the remainder will remain in effect.====
====Robert's Rules of Order will be the parliamentary authority for all matters of procedure not specifically covered by these Bylaws.====
====The Corporation must not discriminate against any person in the selection or employment of personnel, election of Directors, provision or acquisition of goods or services, or in any other way on the basis of race, color, sex, national origin, disabling condition, age, or any other basis prohibited by law.====
===Amendment===
====These Bylaws may be amended, supplemented, or repealed by a two-thirds vote of the Directors or a two-thirds vote of the Ordinary Members.====

====Notice must be given to the Directors at least 30 calendar days before the Board of Directors may consider an amendment, supplement, or repeal of the Charter or these Bylaws.====
====Notice must be given to the Ordinary Members at least 30 calendar days before the Annual Meeting of Members or a Special Meeting of Members may consider an amendment, supplement, or repeal of the Charter or these Bylaws.====

===Contact===
====The Board of Directors must establish by resolution at least one address for the receipt of correspondence to the Corporation via the United States mail, electronic mail, or other reasonable means.====
====The address for the receipt of correspondence will be displayed on mwstake.org ('mwstake' hereafter) or another website accessible to the general public designated by a resolution of the board.====

===Records and Inspection===
====The records of the Corporation must be available for inspection in accordance with the applicable laws as well as the purpose of the Corporation.====
====The Corporation may charge a reasonable fee for copies of its books and records in accordance with the applicable laws.====
====mwstake.org is designated as the primary site on which to display records of the Corporation which may from time to time be changed by resolution of the board of directors.====

===Waiver of Notice===
====Whenever these Bylaws require notice to be given, a waiver of notice may be sent to the Secretary of the Corporation by mail, electronic mail, facsimile transmission, or similar verifiable means with the written or electronic signature of the person or persons entitled to the notice.====
====A waiver of notice will be deemed equivalent to the giving of the notice.====
====A waiver of notice does not have to specify either the business to be transacted at or the purpose of the meeting or other matter for which notice is waived.====
====Attendance at a meeting of the Board of Directors, the Annual Meeting of Members, or a Special Meeting of Members will constitute a waiver of notice of the meeting except where a person attends a meeting for the express purpose of objecting, at the beginning of the meeting, to the transaction of any business because the meeting was not lawfully called or convened.====
===Constructive presence===
====A Director may participate in a meeting of the Board of Directors, the Annual Meeting of Members, or a Special Meeting of Members by means of a conference telephone or online, so long as they can hear, or be advised of, the discussion of business, and other members can hear, or be advised of, the absent member's votes or comments.====

====An Ordinary Member may participate in the Annual Meeting of Members or a Special Meeting of Members by means of a conference telephone or online, so long as they can hear, or be advised of, the discussion of business, and other members can hear, or be advised of, the absent member's votes or comments.====

====Constructive presence will count toward a quorum.====
===Definitions===
====The term "notice" refers to posting to an email distribution list and/or posting on mwstake.====

====Quorum====
=====For meetings of the Board of Directors, the term "quorum" signifies at least five (5) Directors that currently compose the Board of Directors by reason of election or appointment according to these Bylaws. Every act or decision done or made by a majority of the directors present at a meeting duly held at which a quorum is present will be regarded as the act of the Board of Directors.=====

=====For the Annual Meeting of Members and Special Meetings of Members, the term "quorum" signifies greater than fifty percent of the number of individuals who have satisfied the requirements to become Ordinary Members as evidenced by the records of the Corporation.=====
====The term "individual" signifies a natural person.====
====The term "entity" includes a domestic or foreign business corporation, domestic or foreign nonprofit corporation, domestic or foreign unincorporated entity, estate, trust, state, the United States, foreign government, or governmental subdivision.====
====The plural term "Directors" refers to the total number Directors that currently compose the Board of Directors by reason of election or appointment according to these Bylaws.====

==Membership==
===The membership of the Corporation is divided into these classes:===
====Ordinary Members; and====
====Corporate Members.====

===Membership in the Corporation may not be sold, conveyed, or otherwise transferred.===
===Ordinary Members===
====Requirements to Become an Ordinary Member====
=====Only an individual may be an Ordinary Member.=====
=====An Ordinary Member must submit an application for membership via mwstake.org.=====

=====An Ordinary Member must be a user of MediaWiki and participate in the activities of the Corporation.=====
=====An Ordinary Member must pledge to observe the Charter and Bylaws of the Corporation.=====

=====An Ordinary Member must pay the annual membership dues identified by these Bylaws (the "[[Bylaws/Dues|Membership Dues Schedule]]").=====

=====The Board of Directors or its designate must approve the application of an Ordinary Member.=====

====Rights and Privileges of an Ordinary Member:====
=====An Ordinary member is entitled to vote in elections of the Directors of the Corporation and on all matters that properly come before the Annual Meeting of Members or a Special Meeting of Members.=====
===Corporate Members===
====Requirements to Become a Corporate Member====
=====A Corporate Member must pay the annual membership dues identified by these Bylaws (the "[[Bylaws/Dues|Membership Dues Schedule]]").=====

=====An entity may become a Corporate Member in one of two ways:=====
======Submission of an application online via mwstake.org; or======

======Admission by a resolution of the Board of Directors on its own initiative.======
=====To be a Corporate Member, an entity must be represented by an individual who is an Ordinary Member of the Corporation.=====
====Rights and Privileges of Corporate members====
=====Corporate members are allowed to advertise their membership to the group.=====

=====The Board of Directors may by resolution establish such additional rights, privileges and duties corresponding to each class of Corporate Members provided that such rights, privileges, and duties are consistent with the Articles and these Bylaws.=====

====Corporate Members are obligated to observe the Charter and the Bylaws of the Corporation.====

===Solicitation, Denial, and Termination of Membership===
====Solicitation of Membership====
=====An individual or entity may submit an application for membership in the Corporation online through the official website at '''mwstake.org'''.=====
=====The Board of Directors may prescribe by resolution the information that each application for membership must contain, but at a minimum, an applicant must provide these details in the application:=====
======The name/alias of the applicant;======
======Current email address; and======
======An account of how the applicant has used MediaWiki.======
====Denial and Termination of Membership====
=====Denial of Membership=====
======The Board of Directors may deny an application for membership by resolution that describes the reasons for the denial.======
======An application for membership may be denied for failure to provide the required information in the application.======
======Notice of the denial must be sent to the email or certified mail to the registered address of the applicant within ten (10) calendar days of the denial along with notification of the procedure for appeal that has been established by resolution of the Board of Directors.======

=====These actions or events will terminate membership in the Corporation:=====
======Resignation======
<ol type="a">
:::::: <li>An Ordinary Member or a Corporate Member may submit a resignation of membership in writing or electronically to the Board of Directors.</li>
:::::: <li>Resignation from membership does not entitle an Ordinary Member or a Corporate Member to a refund of any [[Bylaws/Dues|membership dues]] or other payments to the Corporation.</li>
</ol>

======Death or Dissolution======
<ol type="a">
:::::: <li>Membership will terminate on the death of an individual member.</li>
:::::: <li>Membership will terminate on the dissolution of an entity.</li>
:::::: <li>In the event of death or dissolution, a majority of the Board of Directors may, by resolution, approve a refund of a [[Bylaws/Dues|membership dues]] or other payments to the Corporation.</li>
</ol>

======Termination for Cause======
<ol type="a">
:::::: <li>The Board of Directors may, by a majority vote, terminate the membership of an Ordinary Member for failure to pay a [[Bylaws/Dues|membership dues]].</li>
:::::: <li>The Board of Directors may, by a majority vote, terminate the membership of an Ordinary Member or a Corporate Member for failure to observe the Charter and the Bylaws of the Corporation.</li>
:::::: <li>Termination for cause does not entitle an Ordinary Member or a Corporate Member to a refund of any [[Bylaws/Dues|membership dues]] or other payments to the Corporation.</li>
</ol>

=====Appeal of Denial or Termination of Membership=====
======An individual or entity whose application for membership has been denied or whose membership has been terminated may submit an appeal within 180 calendar days from the notification of the cancellation.======

======The Board of Directors must establish by resolution an online process for the submission of an appeal of the denial of an application for membership or the termination of a membership======

======The process for the submission of an appeal must provide for recourse to the Annual Meeting of Members.======
======Membership may be terminated by a majority of the Directors then in office after giving the member at least 15 days’ written notice by email or certified mail of the termination and the reasons for the termination, and (except in the case of termination for non-payment of [[Bylaws/Dues|membership dues]], fees, or assessments in timely fashion) an opportunity for the member to be heard by the Board, orally or in writing, no less than five days before the effective date of the termination. The decision of the Board will be final and may not be reviewed by any court.======

===Meetings of Members===
====Annual Meeting of Members====
=====An Annual Meeting of Members must be held at least once during each fiscal year of the Corporation.=====
=====Agenda=====
======The agenda for the Annual Meeting of Members must include these items:======
<ol type="a">
:::::: <li>Examination and approval of the audit and financial statements of the Corporation;</li>
:::::: <li>Examination and approval of the reports on the activities of the Corporation;</li>
:::::: <li>Election of Directors.</li>
</ol>
======The agenda for the Annual Meeting of Members may also include other items:======
<ol type="a">
:::::: <li>Nomination and acceptance of Ordinary Members and Corporate Members;</li>
:::::: <li>Appeals of denial or cancellation of membership;</li>
:::::: <li>Any other matters that may properly be considered by the Annual Meeting of Members under these Bylaws.</li>
</ol>

====Special Meetings of Members====
=====A majority of the Board of Directors or one-third of the Ordinary Members may call a Special Meeting of Members.=====
=====The agenda for a Special Meeting of Members may include any matter that may properly be considered by the Annual Meeting of Members under these Bylaws.=====

=====The notice for a Special Meeting of Members must specify the nature of the business to be transacted.=====
====Date, Location, and Manner====
=====The Board of Directors must, by resolution, establish the date and location of the Annual Meeting of Members and Special Meetings of Members.=====
=====The Annual Meeting of Members and Special Meetings of Members may be held by means of the Internet or other electronic communications technology in a manner through which the Ordinary Members have the opportunity to read or hear the proceedings substantially concurrently with their occurrence, vote on matters submitted to the Ordinary Members, pose questions to the Directors and members of any other body, make appropriate motions, and comment on the business of the meeting.=====
====Notice of the date, time, and place of the Annual Meeting of Members and Special Meetings of Members must be given to all Directors, Ordinary Members, and Corporate Members at least thirty calendar days prior to the date of the meeting.====

====Conduct of Meetings====
=====The Board of Directors must appoint a Presiding Officer for the Annual Meeting of Members and Special Meetings of Members.=====
=====Subject to the approval of the Board of Directors, the Presiding Officer will have the authority to determine the order of business and establish rules of conduct for the Annual Meeting of Members or a Special Meeting of Members.=====
=====Voting=====
======Each Ordinary Member is entitled to one vote.======
======Proxy voting is not allowed.======
======Voting on all matters may be conducted by electronic mail, wiki software, or similar verifiable means.======
====Anyone with an interest in MediaWiki software may attend the Annual Meeting of Members or a Special Meeting of Members.====

==Board of Directors==
===Composition of the Board of Directors===
====The Board of Directors will consist of eight (8) directors. The number of directors may be set from time to time by resolution of a majority of directors then in office.====

====Directors must be Ordinary Members of the Corporation in good standing and at least 18 years of age.====

===Election===
====Directors must be elected by a majority vote of a quorum of the Ordinary Members during the Annual Meeting of Members.====
====The Board of Directors may appoint a Nominating Committee of three Ordinary Members to select candidates for Director.====
====Ordinary Members may also nominate candidates for Director by motion and second at the Annual Meeting of Members.====

===Terms===
====Each Director will serve for a term of three years except as provided in paragraph 5.3.3 for the initial election of directors.====

====Terms must be established so that one-third of the directors are elected each year based on the highest totals of votes.====

====Initially, two of the Directors will serve one-year terms, three will serve two-year terms, and three will serve three-year terms:====
=====The candidates who receive the three highest totals of votes will serve three-year terms.=====
=====The candidates who receive the fourth-, fifth-, and sixth-highest totals of votes will serve two-year terms.=====
=====The candidates who receive the seventh- and eighth-highest totals of votes will serve one-year terms.=====

===Death, Removal, Resignation, and Vacancies===
====The position of a Director will become vacant upon his or her death.====
====Removal====
=====A Director who has missed three or more consecutive meetings of the Board of Directors may be removed.=====
=====A Director may be removed for any action that violates the Charter or the Bylaws of the Corporation=====
=====The removal of a Director must be confirmed by a two-thirds vote of the remaining Directors.=====
====A Director may resign at any time by giving notice of his or her resignation to any Officer of the Board of Directors by notice.====
====Vacancies====
=====By a majority vote, the remaining Directors may appoint an Interim Director to fill a vacancy on the Board of Directors.=====
=====The Interim Director will serve the remainder of the unexpired term for the vacancy.=====
===General Powers===
====The Board of Directors will constitute the governing body of the Corporation.====
====The Board of Directors will manage the business and affairs of the Corporation and have all powers necessary to carry out the purpose and the activities of the Corporation as set forth in these Bylaws.====
====The Board of Directors may accept, on behalf of the Corporation, any donation, contribution, bequest, or devise.====
===Meetings of the Board of Directors===
====A meeting of the Board of Directors must be held at least once per quarter at a reasonable time and place designated by a majority of the Directors.====
====A majority of the Directors may schedule additional meetings.====
====Notice must be sent to each Director 30 calendar days before a meeting of the Board of Directors.====
====Adjournment====
=====A majority of the Directors present at a meeting of the Board of Directors may adjourn the meeting, whether or not a quorum is present, for up to fourteen calendar days.=====
=====Notice of the adjourned meeting or of the business to be transacted there, other than by announcement at the meeting at which the adjournment is taken, will not be necessary.=====
=====At an adjourned meeting for which a quorum is present, any business may be transacted which could have been transacted at the meeting originally called.=====
====Actions====
=====An action of the majority of the Directors at a meeting in which a quorum is present will constitute an action of the Board of Directors.=====
=====Actions of the Board of Directors must take the form of resolutions and must be included in the records of the Corporation.=====
=====Action without a Meeting=====
======The Board of Directors may, without a meeting, take any action that would be permitted at a meeting if the action receives the affirmative vote of all of the Directors.======
======The action must be supported by the written or electronic consent of all of the Directors individually or collectively.======
======Any action taken under these provisions for action without a meeting is effective when all of the Directors have consented unless a different effective date is specified.======
======Any consent resolution that has not received affirmative votes from all of the Directors must be presented for a vote at the next meeting of the Board of Directors.======
======Neither the Bylaws nor the Charter of the Corporation can be amended without a meeting of the Board of Directors.======
====Voting====
=====Each Director is entitled to one vote.=====
=====Proxy voting is not allowed.=====
=====Voting on all matters may be conducted by electronic mail, wiki software, or similar verifiable means.=====
===Compensation of Directors===
====No Director may receive any salary or compensation for their services as Director or any service or benefit related thereto not provided to the general public.====
====Upon presentation of receipts or other appropriate documentation, Directors may receive reimbursement for out-of-pocket expenses incurred while conducting authorized business on behalf of the Corporation.====
====Directors are entitled to receive reasonable fees for goods or services rendered to the Corporation in capacities other than as Directors.====
===Committees and Reserved Powers===
====By a majority vote, the Board of Directors may appoint any committee it deems necessary to help fulfill its functions.====
====The Board of Directors is empowered to promulgate regulations, rules, policies, user agreements, terms of use, and other such decisions that may be necessary for the continued functioning of the Corporation not inconsistent with these Bylaws.====
===Conflict of Interest Transactions===
====As used in this section, a "conflict of interest transaction" is a transaction with the corporation in which a director of the corporation has a direct or indirect interest. A director has an indirect interest in a transaction if another entity in which the director has a material interest or in which the director is a general partner is a party to the transaction, or if another entity of which the director is a director, officer or trustee is a party to the transaction and the transaction is or should be considered by the board of directors of the corporation.====
====A conflict of interest transaction is not voidable or the basis for imposing liability on the director if the transaction is fair to the corporation at the time it was entered into or is approved either (I) in advance by the vote of the board of directors or a committee of the board of directors if the material facts of the transaction and the director’s interest were disclosed or known to the board of directors or a committee of the board of directors, or (II) if the material facts of the transactions and the director’s interest were disclosed or known to the members and they authorized, approved or ratified the transaction. A conflict of interest transaction is so authorized, approved or ratified as follows:====
=====By the directors, if it receives the affirmative vote of a majority of the directors on the board of directors or on the committee who have no direct or indirect interest in the transaction; provided that a transaction may not be so authorized, approved or ratified by a single director. If a majority of the directors who have no direct or indirect interest in the transaction votes to authorize, approve or ratify the transaction, a quorum is present for the purpose of taking such action. A director may not participate in a vote to authorize a transaction in which the director has a direct or indirect interest.=====

=====By the Ordinary Members, if it receives a majority of the votes entitled to be counted. Votes cast by a director who has a direct or indirect interest in the transaction may not be counted in a vote of members to determine whether to authorize, approve or ratify a conflict of interest transaction hereunder. A majority of the Ordinary Members, whether or not present, that are entitled to be counted in a vote on the transaction hereunder constitutes a quorum for the purpose of taking action hereunder.=====

==Officers==
===The Board of Directors will have a President, a Vice-President, a Secretary, and a Treasurer.===
===Any person may hold two or more offices except that the President may not also be Vice-President, Secretary or Treasurer.===
===Duties of Officers.===
====President====
=====The President or Vice President will preside at all meetings of the Board.=====

=====The President will appoint Ordinary Members to standing and ad hoc committees subject to the approval of a majority of the Board of Directors.=====
=====All staff will be supervised by and accountable to the President of the Corporation until the Corporation employs an Executive Director.=====
=====The President will perform whatever duties the Board of Directors may from time to time assign.=====
====Vice-President====
=====The Vice-President will carry out the duties of the President when the President is absent or incapacitated.=====
=====The Vice-President will have the same power and duties as the President when acting in that capacity.=====
=====The Vice-President will perform whatever duties the Board of Directors may from time to time assign.=====
====Secretary====
=====The Secretary will have charge of such books, documents and papers as the Board of Directors may determine.=====
=====The Secretary must keep, or cause to be kept, a true and complete record of the meetings of the Board of Directors.=====
=====The Secretary must give, or cause to be given, notice of all meetings of the Board of Directors, the Annual Meeting of Members, and Special Meetings of Members.=====
=====The Secretary must keep, or cause to be kept, a record containing the names and contact addresses of all Directors, Ordinary Members, and Corporate Members of the Corporation.=====

=====The Secretary will, in general, perform all the duties incident to the office of Secretary, subject to the control of the Board of Directors, and will perform other duties as the Board of Directors may prescribe.=====
====Treasurer====
=====The Treasurer will have custody of all funds, property, and securities of the Corporation subject to such regulations as the Board of Directors may impose.=====
=====The Treasurer must keep, or cause to be kept, full and accurate accounts of receipts and disbursements and must deposit, or cause to be deposited, all funds and other valuable effects of the Corporation in the name of and to the credit of the Corporation in a depository or depositories designated by resolutions of the Board of Directors.=====
=====Corporate funds may be deposited only in banks or institutions that are insured by the Federal Deposit Insurance Corporation or the Federal Savings and Loan Insurance Corporation.=====
=====The Treasurer must give to the President or the Board of Directors, whenever they require it, an account of transactions as Treasurer and of the financial condition of the Corporation and, subject to the control of the Board of Directors, must perform all duties incident to the office of Treasurer.=====
===Election and Terms===
====The Board of Directors must elect the officers.====
====The term for each officer will be three years or until the expiration of the term of the Director who holds each office.====

==Staff==
===Hiring must be conducted in compliance with the nondiscrimination policy of the Corporation.===
===Immediate Family of Directors and Supervisors===
====The Corporation may not hire any employees who are members of the immediate family (spouse, grandparent, parent, brother or sister, son or daughter) of any Director, or of any person who will supervise the employee, unless the material facts of the relationship are disclosed in advance to the Board of Directors and a majority of the disinterested Directors authorizes the employment by resolution.====
====The terms of the employment must be fair to the Corporation as of the time it is authorized by the Board of Directors.====
===Executive Director===
====A majority of the Directors may authorize, by resolution, the employment of an Executive Director who will be accountable to the Board of Directors.====
====If an Executive Director is to be employed, the Board of Directors must, by resolution, establish his or her compensation, terms of employment, and duties.====
====The Executive Director will be responsible for managing the activities of the Corporation in accordance with the instructions of the Board of Directors.====

==Finance==
===Fiscal Policy, Fiscal Year, Budget, Financial Statements, and Audit===
====The Board of Directors must adopt and, from time to time, review a fiscal policy setting out a formal procedure that governs internal controls; the signing of checks; the obligation of funds; approval of contracts, leases, deeds and mortgages; and other significant aspects of the Corporation's fiscal operation.====
====The fiscal policy must assure that the Corporation will have sound financial controls that are appropriate, under generally accepted accounting principles, to its size and purpose.====
====Unless the Board of Directors resolves otherwise, the fiscal year for the Corporation will begin on first day of January and end on the thirty-first day of December.====
====The Board of Directors must prepare and adopt a budget at its first meeting each year.====
====The accounts of the Corporation must be audited annually by a Certified Public Accountant.====
====The Corporation must prepare an annual financial statement for distribution to the Directors, Ordinary Members, and Corporate Members during the Annual Meeting of Members.====

===Seal===
====The Corporation will not use a common seal.====
====The signature of the name of the Corporation by the President or a person authorized by resolution of the Board of Directors will be legal and binding as provided under Paragraph 8.4 of these bylaws.====

===Dissolution===
====The Corporation may be dissolved upon the approval by a two-thirds vote of the Directors or by a two-thirds vote of the Ordinary Members during the Annual Meeting of Members or a Special Meeting of Members.====
====Any distribution of the assets of the Corporation must be made in a manner consistent with the tax status of the Corporation at the time of dissolution.====
===Contracts, Loans, Checks, and Deposits===
====The Board of Directors may, by resolution, authorize any officer, agent, or employee to enter into any contract or execute and deliver any instrument in the name of and on behalf of the Corporation, unless otherwise restricted by law.====
====No loans may be contracted on behalf of the Corporation and no evidence of indebtedness may be issued in its name unless authorized by a resolution of the Board of Directors.====
====Unless so authorized by the Board of Directors, no officer, agent, or employee has any power or authority to bind the Corporation by any contract or engagement or to pledge its credit or to render it liable for any purpose or in any amount.====
====All checks, drafts, or other orders for the payment of money, notes, or other evidences of indebtedness issued in the name of the Corporation must be signed by the President or a person authorized by resolution of the Board of Directors.====
====All funds of the Corporation not otherwise employed must be deposited from time to time to the credit of the Corporation in such banks or institutions as the Board of Directors may authorize by resolution.====
====Authorization by a resolution of the Board of Directors may be ongoing or confined to a specific period of time or to a specific instance.====
===Fiduciary Duty and Conflicts of Interest===
====The Directors and the Board of Directors are under a fiduciary duty to the Corporation and must observe the relevant standard of care under the laws of Pennsylvania.====
====The Directors and the Board of Directors must make informed financial decisions and act in the best interest of the Corporation rather than in their own financial interests.====
====Conflicts of Interest====
=====The term "conflict-of-interest transaction" refers to a transaction with the Corporation in which a Director has a direct or an indirect interest.=====
=====A Director has an indirect interest in a transaction if another entity in which the Director has a material interest or in which the Director is a general partner is a party to the transaction, or if another entity of which the Director is a director, officer, or trustee is a party to the transaction.=====
=====A conflict of interest transaction is not voidable, or the basis for imposing liability on the interested Director, if the transaction is authorized, approved, or ratified by the Board of Directors or the Ordinary Members of the Corporation:=====
======The Board of Directors may authorize, approve, or ratify the transaction under these circumstances:======
<ol type="a">
:::::: <li>At the time of the transaction, it is, or was, fair to the Corporation;</li>
:::::: <li>The material facts of the transaction and the interest are disclosed or known to the Board of Directors;</li>
:::::: <li>The transaction is authorized, approved, or ratified by a majority vote of the Board of Directors who have no direct or indirect interest in the transaction; and</li>
:::::: <li>More than a single Director participates in the vote to authorize, approve, or ratify transaction.</li>
</ol>
======The Ordinary Members may authorize, approve, or ratify the transaction under these circumstances:======
<ol type="a">
:::::: <li>The material facts of the transaction and the interest of the Directors are disclosed or known to the Ordinary Members when they authorize, approve, or ratify the transaction; and</li>
:::::: <li>The transaction is authorized, approved, or ratified by a majority of the Ordinary Members.</li>
</ol>

==Indemnification==
===The Corporation must, except as provided in or limited by the Charter or these Bylaws, indemnify to the maximum extent permitted by law any person who was or is a party to any proceeding (other than an action by, or in the right of, the Corporation) by reason of the fact that he or she is or was a Director or Officer of the Corporation.===

===Expenses incurred by a Director or Officer in defending a civil or criminal proceeding may be paid by the Corporation in advance of the final disposition of such proceeding upon receipt of an undertaking by or on behalf of the Director or Officer to repay the amount if he or she is ultimately found not to be entitled to indemnification by the Corporation.===

===The Corporation may purchase and maintain insurance on behalf of any person who is or was a Director, Officer, employee, or agent of the Corporation, or who is or was serving at the request of the Corporation as a director, trustee, officer, employee, or agent of another corporation, partnership, joint venture, trust, or other enterprise, against any liability asserted against him or her and incurred by him or her in any such capacity, or arising out of his or her status as such, whether or not the Corporation would have the power to indemnify him or her against such liability under the law of the relevant jurisdiction.===

===The Corporation’s obligation, if any, to indemnify any person who was or is serving at its request as a director, trustee, officer, employee, or agent of another enterprise must be reduced by any amount such person collects as indemnification from the other enterprise.===

Blog Post:51

2017-05-27T00:05:51Z

Markus Glaser:

{{Blog Post
|title=Fantastic MediaWikis all over the place
|tags=Hackathon
|people=Markus Glaser
|author=Markus Glaser
}}
[[File:Wikimedia Hackathon 2017 IMG 4278 (34755875905).jpg|thumb|right|Entrance poster of the track]]

This was a long cherished plan for the MediaWiki Stakeholders: curate a track at a MediaWiki Hackathon which entirely focuses on MediaWiki sites and their maintainers. With the help of [https://www.wikimedia.at/ Wikimedia Austria] we were finally able to realize that plan at the [[mw:Wikimedia_Hackathon_2017|Vienna Hackathon 2017]]. MediaWiki practitioners all over the world followed our call for participation and helped us create a track which covered a wide variety of topics: [[mw:MediaWiki_Stakeholders%27_Group/Fantastic_MediaWikis_Program|Fantastic MediaWikis and how to maintain them]].

== Analytical insights: usage and competitors ==
In his keynote, Mark Hershberger summarized insights from a set of interviews he had conducted with MediaWiki users. Notably, users seem to have a great passion when working with the software. Also, Mark comes to the conclusion that third party users of MediaWiki want knowledge sharing, not knowledge management. By using the software, the values of Wikimedia are brought inside the organisations.

There is no doubt MediaWiki is a great piece of software, but how does it score against other wiki engines? This was explored by Richard Heigl, who compared [https://blog.bluespice.com/2017/05/17/bluespice-mediawiki-vs-confluence-the-wiki-alternatives-1/ MediaWiki and Confluence] in terms of features. Quintessentially, Confluence is better for small teams, as it isolates collaboration spaces, whereas MediaWiki is designed for integration and sharing of knowledge across an organisation.

== Use cases ==
Have you ever wondered what a street or a building looked like some years ago? With [http://baugeschichte.at/Hauptseite baugeschichte.at], introduced by Martin Brunner, you now can do this at least in some cities. Based on Semantic MediaWiki, pictures are displayed in a map and can be ordered chronologically. There is even an app, so you can access the information about the buildings you see when you walk along. The wiki uses movable items in page forms and allows for image uploads from within the form. Developments on the platform are fed back to the community.

The [https://www.wien.gv.at/wiki/index.php/Wien_Geschichte_Wiki Vienna History Wiki] is another great example of successful use of a Semantic MediaWiki instance. Bernhard Krabina is a long standing advocate of MediaWiki and SMW which he thinks supplement each other very well, as you can add structured data but still have your “chaos part”. Interestingly, the wiki is externally audited for security, so any extension you find there is extra approved.

It is even possible to build a quality management system with MediaWiki and SMW that fulfills the requirements of standard norms such as the ISO9001:2015. Michael Barylak has set up a prototype at ESA. While not yet in production, he was already able to show that auditing, reporting and querying his system is easy and comes with almost no extra effort once the data scheme is set up.

== Best practises and tutorials ==
[[File:Wikimedia Hackathon 2017-05-19 Fantastic MediaWikis MG 01.jpg|thumb|right|The audience during Mark Hershberger's keynote speech]] Niklas Laxström from [https://translatewiki.net/ translatewiki.net] shared his substantial experiences in running MediaWikis. In particular, he has developed solutions for safely [deploying changes from a test to production environment and baked this into a software called [https://docs.google.com/presentation/d/1cuKRL2eTZe_XFZbUmXuYwF0EbIhJgQUfv4NE1OZsqfk/edit#slide=id.g16d5b94a3a_1_155 Oregano]. Furthermore, there is a [https://docs.google.com/presentation/d/1cuKRL2eTZe_XFZbUmXuYwF0EbIhJgQUfv4NE1OZsqfk/edit#slide=id.g16d5b94a3a_2_221 solution to run the background jobs] of MediaWiki more stable at a higher frequency by using a service instead of a cron job.

[https://smw-cindykate.com/main/Component_601228 Transferring data schemes] (ontologies) from one MediaWiki to another one can now be done in an automated, reproducible and auditable way thanks to Lex Sulzer. Needless to say this also works for other kinds of content synchronisation between wikis.

Putting on his novice user hat, Markus Glaser from BlueSpice was delighted to see how easy it is to install and configure VisualEditor under Windows. He shared his installation path and showed ways to run VisualEditor in a distributed or local environment.

In a separate session, Renate Nuppenau worked with new MediaWiki developers to enable them to contribute code. Her main intention was to lower the barriers for contribution.

== Promoting MediaWiki ==
How can we promote and strengthen the position of MediaWiki? This question was explored by Sabine Melnicki (WikiAhoi), Brion Vibber (WMF), Richard Heigl (BlueSpice), Bryan Davis (WMF) and Mark Hershberger (Nichework). There were some key findings in the [https://etherpad.wikimedia.org/p/fantastic-mediawikis discussion]: it is vital to make a substantial RoI proposition for the case of supporting MediaWiki by the Foundation. Furthermore, the idea of starting with a community edition of MediaWiki was seen very positive. And finally, 3rd party users need to be more visible in the community. This is something the MediaWiki Stakeholders can take care of.

== Statistics ==
Overall, the experiment to have a MediaWiki maintainers' track at the Hackathon can be considered a success. Over the course of the day, we had 30 individuals participating in the sessions, with a concurrent attendance of 12 to 18 people. There were 11 presenters from 5 different countries.

Special thanks go out to Sonja Fischbauer and Claudia Garad for approaching us and helping to realize this event. Markus and Richi are particularly honored to have received a special mention during the opening ceremony.

== Coverage ==
There are some blog posts mentions of the track:
* [https://blog.bluespice.com/2017/05/23/a-culture-of-knowledge-sharing-impressions-from-the-wikimedia-hackathon-2017/ A culture of knowledge sharing - BlueSpice.com]
* [http://www.wikiahoi.at/kleine-souvenirs-vom-wikimedia-hackathon-in-wien/ Kleine Souvenirs vom Wikimedia Hackathon in Wien (in German) - WikiAhoi.at]
* [https://meta.wikimedia.org/wiki/User:Ziko/Viennese_diary#Fantastic_MediaWikis Viennese Diary - Ziko van Dijk]

== Impressions ==
If you want get some impressions of the hackathon, there's a category at Commons:
[[commons:Wikimedia_Hackathon_Vienna_2017_%E2%80%93_Fantastic_MediaWikis|Wikimedia Hackathon Vienna 2017 - Fantastic MediaWikis]]

Blog Post:51

2017-05-24T08:09:23Z

Markus Glaser: /* Impressions */

{{Blog Post
|title=Fantastic MediaWikis all over the place
|tags=Hackathon
|people=Markus Glaser
|author=Markus Glaser
}}

[[File:Wikimedia Hackathon 2017 IMG 4278 (34755875905).jpg|thumb|right|Entrance poster of the track]]

This was a long cherished plan for the MediaWiki Stakeholders: curate a track at a MediaWiki Hackathon which entirely focuses on MediaWiki sites and their maintainers. With the help of [https://www.wikimedia.at/ Wikimedia Austria] we were finally able to realize that plan at the [[mw:Wikimedia_Hackathon_2017|Vienna Hackathon 2017]]. MediaWiki practitioners all over the world followed our call for participation and helped us create a track which covered a wide variety of topics: [[MediaWiki_Stakeholders%27_Group/Fantastic_MediaWikis_Program|Fantastic MediaWikis and how to maintain them]].

== Analytical insights: usage and competitors ==
In his keynote, Mark Hershberger summarized insights from a set of interviews he had conducted with MediaWiki users. Notably, users seem to have a great passion when working with the software. Also, Mark comes to the conclusion that third party users of MediaWiki want knowledge sharing, not knowledge management. By using the software, the values of Wikimedia are brought inside the organisations.

There is no doubt MediaWiki is a great piece of software, but how does it score against other wiki engines? This was explored by Richard Heigl, who compared [https://blog.bluespice.com/2017/05/17/bluespice-mediawiki-vs-confluence-the-wiki-alternatives-1/ MediaWiki and Confluence] in terms of features. Quintessentially, Confluence is better for small teams, as it isolates collaboration spaces, whereas MediaWiki is designed for integration and sharing of knowledge across an organisation.

== Use cases ==
Have you ever wondered what a street or a building looked like some years ago? With [http://baugeschichte.at/Hauptseite baugeschichte.at], introduced by Martin Brunner, you now can do this at least in some cities. Based on Semantic MediaWiki, pictures are displayed in a map and can be ordered chronologically. There is even an app, so you can access the information about the buildings you see when you walk along. The wiki uses movable items in page forms and allows for image uploads from within the form. Developments on the platform are fed back to the community.

The [https://www.wien.gv.at/wiki/index.php/Wien_Geschichte_Wiki Vienna History Wiki] is another great example of successful use of a Semantic MediaWiki instance. Bernhard Krabina is a long standing advocate of MediaWiki and SMW which he thinks supplement each other very well, as you can add structured data but still have your “chaos part”. Interestingly, the wiki is externally audited for security, so any extension you find there is extra approved.

It is even possible to build a quality management system with MediaWiki and SMW that fulfills the requirements of standard norms such as the ISO9001:2015. Michael Barylak has set up a prototype at ESA. While not yet in production, he was already able to show that auditing, reporting and querying his system is easy and comes with almost no extra effort once the data scheme is set up.

== Best practises and tutorials ==
[[File:Wikimedia Hackathon 2017-05-19 Fantastic MediaWikis MG 01.jpg|thumb|right|The audience during Mark Hershberger's keynote speech]] Niklas Laxström from [https://translatewiki.net/ translatewiki.net] shared his substantial experiences in running MediaWikis. In particular, he has developed solutions for safely [deploying changes from a test to production environment and baked this into a software called [https://docs.google.com/presentation/d/1cuKRL2eTZe_XFZbUmXuYwF0EbIhJgQUfv4NE1OZsqfk/edit#slide=id.g16d5b94a3a_1_155 Oregano]. Furthermore, there is a [https://docs.google.com/presentation/d/1cuKRL2eTZe_XFZbUmXuYwF0EbIhJgQUfv4NE1OZsqfk/edit#slide=id.g16d5b94a3a_2_221 solution to run the background jobs] of MediaWiki more stable at a higher frequency by using a service instead of a cron job.

[https://smw-cindykate.com/main/Component_601228 Transferring data schemes] (ontologies) from one MediaWiki to another one can now be done in an automated, reproducible and auditable way thanks to Lex Sulzer. Needless to say this also works for other kinds of content synchronisation between wikis.

Putting on his novice user hat, Markus Glaser from BlueSpice was delighted to see how easy it is to install and configure VisualEditor under Windows. He shared his installation path and showed ways to run VisualEditor in a distributed or local environment.

In a separate session, Renate Nuppenau worked with new MediaWiki developers to enable them to contribute code. Her main intention was to lower the barriers for contribution.

== Promoting MediaWiki ==
How can we promote and strengthen the position of MediaWiki? This question was explored by Sabine Melnicki (WikiAhoi), Brion Vibber (WMF), Richard Heigl (BlueSpice), Bryan Davis (WMF) and Mark Hershberger (Nichework). There were some key findings in the [https://etherpad.wikimedia.org/p/fantastic-mediawikis discussion]: it is vital to make a substantial RoI proposition for the case of supporting MediaWiki by the Foundation. Furthermore, the idea of starting with a community edition of MediaWiki was seen very positive. And finally, 3rd party users need to be more visible in the community. This is something the MediaWiki Stakeholders can take care of.

== Statistics ==
Overall, the experiment to have a MediaWiki maintainers' track at the Hackathon can be considered a success. Over the course of the day, we had 30 individuals participating in the sessions, with a concurrent attendance of 12 to 18 people. There were 11 presenters from 5 different countries.

Special thanks go out to Sonja Fischbauer and Claudia Garad for approaching us and helping to realize this event. Markus and Richi are particularly honored to have received a special mention during the opening ceremony.

== Impressions ==
If you want get some impressions of the hackathon, there's a category at Commons:
[[commons:Wikimedia_Hackathon_Vienna_2017_%E2%80%93_Fantastic_MediaWikis|Wikimedia Hackathon Vienna 2017 - Fantastic MediaWikis]]

Blog Post:51

2017-05-24T08:06:48Z

Markus Glaser: Added links

{{Blog Post
|title=Fantastic MediaWikis all over the place
|tags=Hackathon
|people=Markus Glaser
|author=Markus Glaser
}}

[[File:Wikimedia Hackathon 2017 IMG 4278 (34755875905).jpg|thumb|right|Entrance poster of the track]]

This was a long cherished plan for the MediaWiki Stakeholders: curate a track at a MediaWiki Hackathon which entirely focuses on MediaWiki sites and their maintainers. With the help of [https://www.wikimedia.at/ Wikimedia Austria] we were finally able to realize that plan at the [[mw:Wikimedia_Hackathon_2017|Vienna Hackathon 2017]]. MediaWiki practitioners all over the world followed our call for participation and helped us create a track which covered a wide variety of topics: [[MediaWiki_Stakeholders%27_Group/Fantastic_MediaWikis_Program|Fantastic MediaWikis and how to maintain them]].

== Analytical insights: usage and competitors ==
In his keynote, Mark Hershberger summarized insights from a set of interviews he had conducted with MediaWiki users. Notably, users seem to have a great passion when working with the software. Also, Mark comes to the conclusion that third party users of MediaWiki want knowledge sharing, not knowledge management. By using the software, the values of Wikimedia are brought inside the organisations.

There is no doubt MediaWiki is a great piece of software, but how does it score against other wiki engines? This was explored by Richard Heigl, who compared [https://blog.bluespice.com/2017/05/17/bluespice-mediawiki-vs-confluence-the-wiki-alternatives-1/ MediaWiki and Confluence] in terms of features. Quintessentially, Confluence is better for small teams, as it isolates collaboration spaces, whereas MediaWiki is designed for integration and sharing of knowledge across an organisation.

== Use cases ==
Have you ever wondered what a street or a building looked like some years ago? With [http://baugeschichte.at/Hauptseite baugeschichte.at], introduced by Martin Brunner, you now can do this at least in some cities. Based on Semantic MediaWiki, pictures are displayed in a map and can be ordered chronologically. There is even an app, so you can access the information about the buildings you see when you walk along. The wiki uses movable items in page forms and allows for image uploads from within the form. Developments on the platform are fed back to the community.

The [https://www.wien.gv.at/wiki/index.php/Wien_Geschichte_Wiki Vienna History Wiki] is another great example of successful use of a Semantic MediaWiki instance. Bernhard Krabina is a long standing advocate of MediaWiki and SMW which he thinks supplement each other very well, as you can add structured data but still have your “chaos part”. Interestingly, the wiki is externally audited for security, so any extension you find there is extra approved.

It is even possible to build a quality management system with MediaWiki and SMW that fulfills the requirements of standard norms such as the ISO9001:2015. Michael Barylak has set up a prototype at ESA. While not yet in production, he was already able to show that auditing, reporting and querying his system is easy and comes with almost no extra effort once the data scheme is set up.

== Best practises and tutorials ==
[[File:Wikimedia Hackathon 2017-05-19 Fantastic MediaWikis MG 01.jpg|thumb|right|The audience during Mark Hershberger's keynote speech]] Niklas Laxström from [https://translatewiki.net/ translatewiki.net] shared his substantial experiences in running MediaWikis. In particular, he has developed solutions for safely [deploying changes from a test to production environment and baked this into a software called [https://docs.google.com/presentation/d/1cuKRL2eTZe_XFZbUmXuYwF0EbIhJgQUfv4NE1OZsqfk/edit#slide=id.g16d5b94a3a_1_155 Oregano]. Furthermore, there is a [https://docs.google.com/presentation/d/1cuKRL2eTZe_XFZbUmXuYwF0EbIhJgQUfv4NE1OZsqfk/edit#slide=id.g16d5b94a3a_2_221 solution to run the background jobs] of MediaWiki more stable at a higher frequency by using a service instead of a cron job.

[https://smw-cindykate.com/main/Component_601228 Transferring data schemes] (ontologies) from one MediaWiki to another one can now be done in an automated, reproducible and auditable way thanks to Lex Sulzer. Needless to say this also works for other kinds of content synchronisation between wikis.

Putting on his novice user hat, Markus Glaser from BlueSpice was delighted to see how easy it is to install and configure VisualEditor under Windows. He shared his installation path and showed ways to run VisualEditor in a distributed or local environment.

In a separate session, Renate Nuppenau worked with new MediaWiki developers to enable them to contribute code. Her main intention was to lower the barriers for contribution.

== Promoting MediaWiki ==
How can we promote and strengthen the position of MediaWiki? This question was explored by Sabine Melnicki (WikiAhoi), Brion Vibber (WMF), Richard Heigl (BlueSpice), Bryan Davis (WMF) and Mark Hershberger (Nichework). There were some key findings in the [https://etherpad.wikimedia.org/p/fantastic-mediawikis discussion]: it is vital to make a substantial RoI proposition for the case of supporting MediaWiki by the Foundation. Furthermore, the idea of starting with a community edition of MediaWiki was seen very positive. And finally, 3rd party users need to be more visible in the community. This is something the MediaWiki Stakeholders can take care of.

== Statistics ==
Overall, the experiment to have a MediaWiki maintainers' track at the Hackathon can be considered a success. Over the course of the day, we had 30 individuals participating in the sessions, with a concurrent attendance of 12 to 18 people. There were 11 presenters from 5 different countries.

Special thanks go out to Sonja Fischbauer and Claudia Garad for approaching us and helping to realize this event. Markus and Richi are particularly honored to have received a special mention during the opening ceremony.

== Impressions ==
If you want get some impressions of the hackathon, there's a category at Commons:
https://commons.wikimedia.org/wiki/Category:Wikimedia_Hackathon_Vienna_2017_%E2%80%93_Fantastic_MediaWikis

File:Wikimedia Hackathon 2017 IMG 4278 (34755875905).jpg

2017-05-24T07:46:53Z

Markus Glaser: Entrance poster for the Fantastic MediaWiki track From [https://commons.wikimedia.org/wiki/File:Wikimedia_Hackathon_2017_IMG_4278_(34755875905).jpg Wikimedia Commons] By Raimund Liebert, CC-BY 2.0

Entrance poster for the Fantastic MediaWiki track

From [https://commons.wikimedia.org/wiki/File:Wikimedia_Hackathon_2017_IMG_4278_(34755875905).jpg Wikimedia Commons]

By Raimund Liebert, CC-BY 2.0

File:Wikimedia Hackathon 2017-05-19 Fantastic MediaWikis MG 01.jpg

2017-05-24T07:42:00Z

Markus Glaser: The audience of "Fantastic MediaWikis" during Mark Hershberger's keynote. Originially from [https://commons.wikimedia.org/wiki/File:Wikimedia_Hackathon_2017-05-19_Fantastic_MediaWikis_MG_01.jpg Wikimedia commons] Author: Markus Glaser CC-BY-SA 4.0

The audience of "Fantastic MediaWikis" during Mark Hershberger's keynote.

Originially from [https://commons.wikimedia.org/wiki/File:Wikimedia_Hackathon_2017-05-19_Fantastic_MediaWikis_MG_01.jpg Wikimedia commons]

Author: Markus Glaser
CC-BY-SA 4.0

Blog Post:51

2017-05-24T06:47:21Z

Markus Glaser: Created page with "{{Blog Post |title=Fantastic MediaWikis all over the place |tags=Hackathon |people=Markus Glaser |author=Markus Glaser }} File:Wikimedia Hackathon 2017-05-19 Fantastic Media..."

{{Blog Post
|title=Fantastic MediaWikis all over the place
|tags=Hackathon
|people=Markus Glaser
|author=Markus Glaser
}}
[[File:Wikimedia Hackathon 2017-05-19 Fantastic MediaWikis MG 01.jpg|Wikimedia Hackathon 2017-05-19 Fantastic MediaWikis MG 01]]

This was a long cherished plan for the MediaWiki Stakeholders: curate a track at a MediaWiki Hackathon which entirely focuses on MediaWiki sites and their maintainers. With the help of Wikimedia Austria we were finally able to realize that plan at the Vienna Hackathon 2017. MediaWiki practitioners all over the world followed our call for participation and helped us create a track which covered a wide variety of topics.

== Analytical insights: usage and competitors ==
In his keynote, Mark Hershberger summarized insights from a set of interviews he had conducted with MediaWiki users. Notably, users seem to have a great passion when working with the software. Also, Mark comes to the conclusion that third party users of MediaWiki want knowledge sharing, not knowledge management.By using the software, the values of Wikimedia are brought inside the organisations.

There is no doubt MediaWiki is a great piece of software, but how does it score against other wiki engines? This was explored by Richard Heigl, who compared MediaWiki and Confluence in terms of features. Quintessentially, Confluence is better for small teams, as it isolates collaboration spaces, whereas MediaWiki is designed for integration and sharing of knowledge across an organisation.

== Use cases ==
Have you ever wondered what a street or a building looked like some years ago? With baugeschichte.at, introduced by Martin Brunner, you now can do this at least in some cities. Based on Semantic MediaWiki, pictures are displayed in a map and can be ordered chronologically. There is even an app, so you can access the information about the buildings you see when you walk along.The wiki uses movable items in page forms and allows for image uploads from within the form. Developments on the platform are fed back to the community.

The Vienna History Wiki is another example of successful use of a Semantic MediaWiki instance. Bernhard Krabina is a long standing advocate of MediaWiki and SMW which he thinks supplement each other very well, as you can add structured data but still have your “chaos part”. Interestingly, the wiki is externally audited for security, so any extension you find there is extra approved.

It is even possible to build a quality management system with MediaWiki and SMW that fulfills the requirements of standard norms such as the ISO9001:2015. Michael Barylak has set up a prototype at ESA. While not yet in production, he was already able to show that auditing, reporting and querying his system is easy and comes with almost no extra effort once the data scheme is set up.

== Best practises and tutorials ==
Niklas Laxström from translate.net shared his substantial experiences in running MediaWikis. In particular, he has developed solutions for safely deploying changes from a test to production environment and baked this into a software called Oregano. Furthermore, there is a solution to run the background jobs of MediaWiki more stable at a higher frequency by using a service instead of a cron job.

Transferring data schemes (ontologies) from one MediaWiki to another one can now be done in an automated, reproducible and auditable way thanks to Lex Sulzer. Needless to say this also works for other kinds of content synchronisation between wikis.

Putting on his novice user hat, Markus Glaser from BlueSpice was delighted to see how easy it is to install and configure VisualEditor under Windows. He shared his installation path and showed ways to run VE in a distributed or local environment.

In a separate session, Renate Nuppenau worked with new MediaWiki developers to enable them to contribute code. Her main intention was to lower the barriers for contribution.

== Promoting MediaWiki ==
How can we promote and strengthen the position of MediaWiki? This question was explored by Sabine Melnicki (WikiAhoi), Brion Vibber (WMF), Richard Heigl (BlueSpice), Bryan Davis (WMF) and Mark Hershberger (Nichework). There were some key findings in the discussion: it is vital to make a substantial RoI proposition for the case of supporting MediaWiki by the Foundation. Furthermore, the idea of starting with a community edition of MediaWiki was seen very positive. And finally, 3rd party users need to be more visible in the community. This is something the MediaWiki Stakeholders can take care of.

== Statistics ==
Overall, the experiment to have a MediaWiki maintainers' track at the Hackathon can be considered a success. Over the course of the day, we had 30 individuals participating in the sessions, with a concurrent attendance of 12 to 18 people. There were 11 presenters.

Special thanks go out to Sonja Fischbauer and Claudia Garad for approaching us and helping to realize this event. Markus and Richi are particularly honored to have received a special mention during the opening ceremony.

== Impressions ==
If you want get some impressions of the hackathon, there's a category at Commons:
https://commons.wikimedia.org/wiki/Category:Wikimedia_Hackathon_Vienna_2017_%E2%80%93_Fantastic_MediaWikis

Blog Post:49

2017-03-20T14:42:44Z

Markus Glaser: Created page with "{{Blog Post |title=Fantastic MediaWikis - Track at Wikimedia Hackathon - CfP |author=Markus Glaser }} "[https://www.wikimedia.at/hackathon/fantastic-mediawikis/ Fantastic Medi..."

{{Blog Post
|title=Fantastic MediaWikis - Track at Wikimedia Hackathon - CfP
|author=Markus Glaser
}}
"[https://www.wikimedia.at/hackathon/fantastic-mediawikis/ Fantastic MediaWikis and How to Maintain Them]" is a one-day conference track designed for people who work with the open source software MediaWiki in their organisation, company or business. The conference track is curated by the MediaWiki Stakeholders Group and hosted by Wikimedia Austria.

The track is part of Wikimedia’s biggest annual tech-event, the [Wikimedia Hackathon https://www.mediawiki.org/wiki/Wikimedia_Hackathon_2017]: For three days each year, about 200 developers come together to improve MediaWiki. Among the participants are coders from the Wikimedia Foundation as well as volunteers from all over the world.

We’re using this opportunity to connect the people who work with MediaWiki in their enterprise, company, or organisation to the people who actually develop the code. We invite all MediaWiki stakeholders – power-users, maintainers, and service providers, who have a professional or semi-professional interest in the software – to join us for a day full of MediaWiki knowledge and networking!

This is a call for participation. We are specifically looking for contributions of your experience in running MediaWikis. These include but are not confined to:

* Use Cases. Tell us how and why you use MediaWiki in a specific area or to solve a specific problem.
* Best Practices. Talk about the most effective way you have found to use particular MediaWiki features.
* Enhancements. Have you improved MediaWiki to fit your needs? Show us your solution.
* Challenges. How can we all add to MediaWiki functionality? Do you have specific ideas you want to collaborate on?

Share your experience and submit a presentation here:

https://www.mediawiki.org/wiki/MediaWiki_Stakeholders%27_Group/Fantastic_MediaWikis_CfP

Important dates:

* 20th March 2017: Call for Participation opens
* 5th April 2017: Submission deadline
* 10th April 2017: Notification of acceptance
* 19th - 21st May 2017: Vienna Hackathon

We are looking forward to your submissions!

Blog Post:46

2016-11-29T22:57:18Z

Markus Glaser:

{{Blog Post
|title=2016 annual report is out
|tags=Report,
|people=Markus Glaser,
|author=Markus Glaser
}}
Once a year, the MediaWiki Stakeholders' Group issues a report on our activities. This report is part of our [https://meta.wikimedia.org/wiki/Wikimedia_user_groups/Agreement_and_code_of_conduct affiliate agreement] with the Wikimedia Foundation. Highlights of this year's activities include:
* '''Continuation and improvement of MediaWiki user experience'''. We are striving to keep user experience of MediaWiki as consistent and integrated as possible for self-installed MediaWiki instances (see output).
* '''Exchange of experience among stakeholders''', i.e. primarily people running MediaWiki as their platform. This was done in regular online and offline meetings as well as through our online platform at [http://mwstake.org mwstake.org].
* '''WikiApiary'''. We took over maintenance of one major existing platform to gather usage statistics for MediaWiki instances and continued to support its editing community.
* '''Incorporation'''. Though we are not incorporated yet, becoming a legal entity is vital to achieving our goals. We have made great steps by clarifying the place and form of incorporation.
* '''Building a MediaWiki organisation'''. We explored the idea of creating a MediaWiki organisation and the path towards this goal.

You can read the full report on [https://www.mediawiki.org/wiki/MediaWiki_Stakeholders%27_Group/Annual_Report_2016 MediaWiki.org].

Blog Post:46

2016-11-29T22:56:52Z

Markus Glaser: Created page with "{{Blog Post |title=2016 annual report is out |tags=Report, |author=Markus Glaser }} Once a year, the MediaWiki Stakeholders' Group issues a report on our activities. This repo..."

{{Blog Post
|title=2016 annual report is out
|tags=Report,
|author=Markus Glaser
}}
Once a year, the MediaWiki Stakeholders' Group issues a report on our activities. This report is part of our [https://meta.wikimedia.org/wiki/Wikimedia_user_groups/Agreement_and_code_of_conduct affiliate agreement] with the Wikimedia Foundation. Highlights of this year's activities include:
* '''Continuation and improvement of MediaWiki user experience'''. We are striving to keep user experience of MediaWiki as consistent and integrated as possible for self-installed MediaWiki instances (see output).
* '''Exchange of experience among stakeholders''', i.e. primarily people running MediaWiki as their platform. This was done in regular online and offline meetings as well as through our online platform at [http://mwstake.org mwstake.org].
* '''WikiApiary'''. We took over maintenance of one major existing platform to gather usage statistics for MediaWiki instances and continued to support its editing community.
* '''Incorporation'''. Though we are not incorporated yet, becoming a legal entity is vital to achieving our goals. We have made great steps by clarifying the place and form of incorporation.
* '''Building a MediaWiki organisation'''. We explored the idea of creating a MediaWiki organisation and the path towards this goal.

You can read the full report on [https://www.mediawiki.org/wiki/MediaWiki_Stakeholders%27_Group/Annual_Report_2016 MediaWiki.org].

Event:42

2016-09-28T09:35:51Z

Markus Glaser: Created page with "{{Event |mwstake-meeting=Yes |start-date=2016/09/28 |start-hour=11 |start-minute=30 |end-date=2016/09/28 |end-hour=13 |end-minute=00 |url=https://etherpad.wikimedia.org/p/mwst..."

{{Event
|mwstake-meeting=Yes
|start-date=2016/09/28
|start-hour=11
|start-minute=30
|end-date=2016/09/28
|end-hour=13
|end-minute=00
|url=https://etherpad.wikimedia.org/p/mwstake20160928
}}
Agenda
* Incorporation
* WikiApiary

Blog Post:43

2016-06-23T11:24:53Z

Markus Glaser: Created page with "{{Blog Post |title=Wikimedia Conference: Takeaways for MWStake |tags=Conference, Wikimedia, |people=Markus Glaser, |author=Markus Glaser }} meta:Wikimedia_Conference_2016|Wi..."

{{Blog Post
|title=Wikimedia Conference: Takeaways for MWStake
|tags=Conference, Wikimedia,
|people=Markus Glaser,
|author=Markus Glaser
}}
[[meta:Wikimedia_Conference_2016|Wikimedia Conference]] is the annual get together of the political sphere of the Wikimedia world. Representatives of the [https://wikimediafoundation.org/wiki/Home Foundation] and [[meta:Wikimedia_movement_affiliates|affiliate organisations]] go there to discuss the future of Wikimedia as well as learn and educate themselves how to organize and lead an organisation. I had the pleasure to be the representative of MediaWiki Stakeholders, and went to Berlin to further our cause.

One of the most helpful takeaways was to hear about the newly built [[meta:Program_Capacity_and_Learning|Program Capacity and Learning]] team. Provided by the Wikimedia Foundation to Affiliates, including us, this team helps them do a lot of tasks they need for their daily work. So there is a person, Edward Galvez, dedicated to conducting surveys, and I had a long chat with him about our upcoming MediaWiki Users Survey. There is also a team working on social media and the offer to help the Affiliates with their social media strategy in general and how to publish on the big Wikimedia channels in particular. And of course, there's the grant team which should be approached when we need money for specific projects.

There were several opportunities to let the Wikimedia world know about our projects and get feedback on them. In the pre-conference, I had a [https://docs.google.com/presentation/d/1oEw07QpjQz_5ZliDeeV1TqEXqkCCMKmxWG-cfdR7ums/edit#slide=id.p lightning talk] about our last year's MediaWiki User Survey and the learnings we took from this, and I had a few conversations afterwards about conducting a survey and exchanged experiences with others.

On the topic of a MediaWiki organisation, the main mission was to spread the idea, get feedback and also get a sense of how well supported any variant of such an organisation would be. To that end, I did another [https://docs.google.com/presentation/d/1oEw07QpjQz_5ZliDeeV1TqEXqkCCMKmxWG-cfdR7ums/edit#slide=id.p lightning talk] on Friday, where I presented a wide (take on responsibility for core) and a narrow (work on 3rd party needs) option. In conversations following the talk, I got the impression that the narrow option in particular has the support of several players in the movement. In a follow-up meetup on the next day, there were a few people who wanted to know more. One question that came up is whether a MediaWiki organisation could also serve as a software developing partner for other Affiliates, such as small chapters. This is an idea we have to think about.

This has been a difficult half a year for the Foundation. I would have loved to see a little bit more of analysis at the conference how it came to the recent leadership crisis. This would have helped in finding ways to prevent such a thing in the future. However, it was inspiring to see how everyone at the conference was constructive and forward-looking. In general, I have the impression that we see a new attitude towards Affiliates and Community. The word "serve" has been used several times in this context. Katherine Maher (interim ED) conveys a sense of conversation on a par with everyone. The Program Capacity among others shows the Foundation is willing to take on its responsibility for the wider movement as a partner. This is definitely the right course. Let's hope they, and we all in the Affiliate world, can keep this up.

Blog Post:42

2016-06-23T10:41:47Z

Markus Glaser:

{{Blog Post
|title=Impressions from the Jerusalem Hackathon 2016
|tags=Hackathon,
|people=Mark Hershberger,
|author=Markus Glaser
}}
This year’s [[mw:Wikimedia_Hackathon_2016|European Hackathon]] took place in Jerusalem, Israel (well, this is not exactly Europe, but only encyclopaedists would insist here). [[meta:Wikimedia_Israel|Wikimedia Israel]] gave us a very sweet welcome, thanks for that!

The main focus of the hackathon was working on the community wishlist and several projects could be completed. I want to share a story of a not completed task, though. So before the conference, I picked a task for myself which was to add an expiry date to watchlist items. This, so it seemed, was reasonably challenging, but not impossible to do when you are at a place where all the MediaWiki hackers are. Add a table column, a few user interface items and some logic to expire and remove watchlist entries. However, when looking at the [https://phabricator.wikimedia.org/T100508 Phabricator ticket], there was a list of 25 blocking tasks which had to be resolved before. Why was that? It turned out that watchlist code is one of the oldest code areas in MediaWiki and no one had touched it for years (except for some necessary adoptions). The watchlist code seems to be spread all over the place and has to be refactored in several ways. The good news is, a team of core developers took on the task and it will be way easier to work on the watchlist in the future. There are several takeaways from this.
* First, never misunderestimate the complexity of code. Even seemingly simple tasks can become a refactoring hell.
* Second, it is not always the experts who trigger a reduction of technical debt. Had the community not voted this task very high, probably the old watchlist code would sit there for another few years.
* Third, a hacky solution might have been possible. However, this is not the way to go unless we want to have even more bad code in the software.I am very delighted to see that the Foundation team has tackled the task even though it is more time consuming than initially thought.
It is a good attitude in our movement to take community wishes very serious.

So instead, I ended up translating some [[mw:How_to_become_a_MediaWiki_hacker/de|entry pages for developers]] into German and hope, this helps someone to get started and find their way into MediaWiki hacking. In that course, Manuel Schneider and I also worked on a [[mw:Template:Developing_extensions|navigation for extension developers]], which should provide them with easy access to all the necessary material about extension development. This is not finished yet, and we appreciate your input on what's important for MediaWiki developers.

Special thanks go out to [[meta:User:Maor_X|Maor Malul]], who took us to the best Kurdish restaurant in Jerusalem and showed us around his very lovely neighbourhood, including the synagogue.

Blog Post:42

2016-06-23T10:41:05Z

Markus Glaser: Created page with "{{Blog Post |title=Impressions from the Jerusalem Hackathon 2016 |tags=Hackathon, |people=Mark Hershberger, |author=Markus Glaser }} This year’s mw:Wikimedia_Hackathon_201..."

{{Blog Post
|title=Impressions from the Jerusalem Hackathon 2016
|tags=Hackathon,
|people=Mark Hershberger,
|author=Markus Glaser
}}
This year’s [[mw:Wikimedia_Hackathon_2016|European Hackathon]] took place in Jerusalem, Israel (well, this is not exactly Europe, but only encyclopaedists would insist here). [[meta:Wikimedia_Israel|Wikimedia Israel]] gave us a very sweet welcome, thanks for that!

The main focus of the hackathon was working on the community wishlist and several projects could be completed. I want to share a story of a not completed task, though. So before the conference, I picked a task for myself which was to add an expiry date to watchlist items. This, so it seemed, was reasonably challenging, but not impossible to do when you are at a place where all the MediaWiki hackers are. Add a table column, a few user interface items and some logic to expire and remove watchlist entries. However, when looking at the [https://phabricator.wikimedia.org/T100508 Phabricator ticket]], there was a list of 25 blocking tasks which had to be resolved before. Why was that? It turned out that watchlist code is one of the oldest code areas in MediaWiki and no one had touched it for years (except for some necessary adoptions). The watchlist code seems to be spread all over the place and has to be refactored in several ways. The good news is, a team of core developers took on the task and it will be way easier to work on the watchlist in the future. There are several takeaways from this.
* First, never misunderestimate the complexity of code. Even seemingly simple tasks can become a refactoring hell.
* Second, it is not always the experts who trigger a reduction of technical debt. Had the community not voted this task very high, probably the old watchlist code would sit there for another few years.
* Third, a hacky solution might have been possible. However, this is not the way to go unless we want to have even more bad code in the software.I am very delighted to see that the Foundation team has tackled the task even though it is more time consuming than initially thought.
It is a good attitude in our movement to take community wishes very serious.

So instead, I ended up translating some [[mw:How_to_become_a_MediaWiki_hacker/de|entry pages for developers]] into German and hope, this helps someone to get started and find their way into MediaWiki hacking. In that course, Manuel Schneider and I also worked on a [[mw:Template:Developing_extensions|navigation for extension developers]], which should provide them with easy access to all the necessary material about extension development. This is not finished yet, and we appreciate your input on what's important for MediaWiki developers.

Special thanks go out to [[meta:User:Maor_X|Maor Malul]], who took us to the best Kurdish restaurant in Jerusalem and showed us around his very lovely neighbourhood, including the synagogue.

MediaWiki Foundation working groups

2016-05-06T17:26:48Z

Markus Glaser: /* Organization of the organization */ +me

Please sign up for working groups you are able to help with:

== Communication to the public ==
This group works on marketing, PR, announcements, and this wiki/website.

* [[User:Matthew Flaschen|Matthew Flaschen]] ([[User talk:Matthew Flaschen|talk]]) 16:00, 6 May 2016 (UTC)

== Communication with Wikimedia ==
This group works on strategy, budget, reports, and collaboration with Wikimedia.

== Technical working group ==
This group does software engineering for MediaWiki Foundation projects (e.g. extension management, extension store, software wishlist.
* [[User:Cindy Cicalese|Cindy Cicalese]] ([[User talk:Cindy Cicalese|talk]]) 16:06, 6 May 2016 (UTC)

== Communication with stakeholders ==
This group communicates with MediaWiki stakeholders about their wishlist and use cases.

== Organization of the organization ==
This group works on planning how MediaWiki Foundation will become an incorporated organization (funding model, working model, non-profit type, incorporation, budget, reports, events, announcements).
* --[[User:Markus Glaser|Markus Glaser]] ([[User talk:Markus Glaser|talk]]) 17:26, 6 May 2016 (UTC)

Main Page

2016-04-23T14:35:20Z

Markus Glaser: added date of renewal

The '''MediaWiki Stakeholders' Group''' is a MediaWiki [[:mw:Groups|user group]] consisting of MediaWiki developers, system administrators, users, consultants, and hosting providers who cooperate in order to improve the software and advocate the needs of MediaWiki users outside the Wikimedia Foundation (WMF), its projects and the traditional Wikimedia movement.

This wiki, MWStake.org, acts as a repository for news and events around our work. To be kept up-to-date on our activities, you can follow the tasks on [https://phabricator.wikimedia.org/tag/mediawiki-stakeholders-group/ our workboard in] Phabricator. You can also follow us on Twitter at [https://twitter.com/@mwstakeholders @mwstakeholders].

Our scope of influence is deliberately broad and meant to be flexible to encompass the needs of our diverse community. Our areas of collaboration are described on our [https://www.mediawiki.org/wiki/MediaWiki_Stakeholders%27_Group user group page on mediawiki.org].

The group was [[:mw:meta:Affiliations_Committee/Resolutions/MediaWiki_Stakeholders%27_Group_-_Liaison_approval,_November_2014|recognized by the Affiliations Committee]] on [[:mw:Thread:Talk:MediaWiki Stakeholder's Group/Congratulations!|November 11, 2014]] and renewed in January 2016.

{| cellspacing="0" cellpadding="0" width=100%
| style="vertical-align: top;width: 30%;" | {{FancyBox
| color = CCA300
| title = Recent blog posts
| icon = [[File:Blog.png|24px|link=]]
| content =
{{#ask:[[Category:Blog Posts]]
|?Page creator
|?Creation date
|format=ul
|template=Blog Post Row
|link=none
|headers=hide
|sort=Creation date
|order=desc
|limit=10
|searchlabel=
}}
}}
| style="vertical-align: top;padding-left: 1.2em; width: 30%;" | {{FancyBox
| color = CCA300
| title = Recent MWstake meetings
| icon = [[File:Meeting.png|24px|link=]]
| content =
{{#ask:[[Category:Events]][[MWstake Meeting::true]][[Start Date::≤{{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY}}]]
|?Date
|?Event URL
|format=ul
|template=Meeting Row
|headers=hide
|link=none
|sort=Start Date
|order=desc
|limit=20
|searchlabel=
}}
}}
| style="vertical-align: top;padding-left: 1.2em; width: 30%;" | {{FancyBox
| color = CCA300
| title = Upcoming events
| icon = [[File:Calendar.png|24px|link=]]
| content =
{{#ask:[[Category:Events]][[Start Date::>{{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY}}]]
|?Start Date
|?End Date
|?Event URL
|?MWstake Meeting
|format=ul
|template=Event Row
|headers=hide
|link=none
|sort=Start Date
|order=asc
|limit=10
|searchlabel=
}}
}}
|-
| {{FancyBox
| color = CCA300
| title = Recent other events
| icon = [[File:Meeting.png|24px|link=]]
| content =
{{#ask:[[Category:Events]][[MWstake Meeting::false]][[Start Date::≤{{CURRENTYEAR}}-{{CURRENTMONTH}}-{{CURRENTDAY}}]]
|?Start Date
|?End Date
|?Event URL
|format=ul
|template=Event Row
|headers=hide
|link=none
|sort=Start Date
|order=desc
|limit=20
|searchlabel=
}}
}}
|}
<div style="display:none;">
{{DISPLAYTITLE:MediaWiki Stakeholders' Group (#MWstake)}}
[[Category:Framework Pages]]
</div>

User:Markus Glaser

2016-04-20T17:52:47Z

Markus Glaser: create user page